GSI tiem? 🤔

Or back to hyperos hell?

Nope, PixelOS wins in the end

There are 2 A15 GSIs I'm attempting to flash
A. The A15 Beta 3 Pixel 8 Pro port from mysticgsi
B. Official A15 AOSP GSI from Google
I'll attempt both, see which one has successfully booted, and what I've done to get it working

And also proper flash guide via fastbootD (don't be afraid)

Scratch all I have said, tried all vendor QPR3, QPR2 and MIUI vendor and none boot for either gsi

As punishment, back to A14 HyperOS hell

#ResurrectedOS #HyperOS #Port #U #Sweet
ResurrectedOS Beta - PORT | Android 14.
Updated: 12/07/‘24

▪️Download
▪️Screenshot
▪️Support
▪️Flashing Steps
▪️Changelog
▪️Credits

Notes:
• First port and many bug fixes have been attempted
• Preferred recovery
• For any issues please use the linked support group available in post rather than PM.
• Get instructions from the support group to fix the camera issue

By @BdrcnAYYDIN
Follow @RedmiNote10ProChannel
Join @RedmiNote10ProDiscussion

ROM review:
Fastest and smoothest A14 HyperOS I've used, fastest one to boot too!
And selinux is enforcing! Although, it's based on xiaomi.eu and that ahh whole other story

Pros:
- Fast and responsive
- Smooth
- Decent chunk of customisations
- Phone is cool and doesn't get heated very quickly/consistently heated

Cons:
- As usual with all A14 HyperOS ports I've tested so far, do not expect the best BB out of it.
- Based on xiaomi.eu; it was shipped with an outdated xiaomi.eu PIF apk, solution to that is to update it to pass device integrity

Overall, I'm feeling a solid 8 on this one!

Next ROM to flash ↓

#SomethingOS #Unofficial #CLO #OSS #ROM #U #Sweet
SomethingOS 1.4- UNOFFICIAL | Android 14.
Updated: 17/07/‘24

▪️Download
▪️Screenshots
▪️Channel
▪️Support

Notes:
• CAF/CLO build
• Miui Camera is included
• Signed build with private keys
• Device integrity passes
• Shipped with July security patch
• JamesDSP is included by default
• Use only this recovery for flashing rom

Credits:
• To all my testers for supporting me
• Clhex, Mayur for the help :D
• Jevesh for the banner <3

By @aarav_x
Follow @RedmiNote10ProChannel
Join @RedmiNote10ProDiscussion

Also, don't expect to consistently do ROM reviews like this, me no Zarya with a team of testers and shites

So if you'd like to use old ROMs that are signed with test keys, now you can pass device integrity on them once again

And I've now lost 90% of my apps data 😭😭
adb has failed to fully backup Swiftbackup data, where it is supposed to backup 11 gigs of that, only backed up 1 gig
I should've verified that it has successfully backed up the entire data before formatting data, now that's gone
Oh well, sometimes you learn it the hard way 🫠

And only not verify on pc, also verify on phone too

Now released as 16.7
https://t.me/playintegrityfix/126

Hey uhm
So, this SomethingOS, is not good

Key Attestation app errors with a java exception: null and both native test and native detector are detecting "Found Injection" WHILE BEING UNROOTED!
This indicates that the ROM has a very faulty ROM-side LBL spoof

And weird permission issues too, like swift backup loses it permission to access storage and the only way to grant it ever again is to clear app data!!

Needless to say, I'm definitely scrambling around to flash anything stable now

Also updates regarding me dealing with cooking EROFS ROMs:
So
1. I've discovered that the reason why it fails when attempting to flash via the original install script that came with ROM is because the partitions need to be resized to the minimum to fit. The problem however, is that you cannot resize EROFS images! Thus, I have absolutely no choice but to pack all partitions in one super.img and nuke the original install script that came with ROM and make MIO generate one instead. That is because only through super.img can partitions be resized correctly during flash time
2. EROFS is apparently to be very sensitive to file timestamps, so I'll be now using the epoch timestamp 1230768000 (Thanks @TheRealModder)
3. I am no longer bound to older versions of MIO Kitchen, the reason for that was because I was packing EROFS with lz4hc, until came along Jan who've let me know that EROFS ROMs are originally packed with lz4! Sure enough, I packed EROFS with lz4 + Support for Old Kernel option checked + Point 1 and 2, and to my surprise, it boots! So I owe @mio_rom an apology, EROFS packing with support for old kernel works as intended in latest versions of MIO Kitchen

Very nerdy post I know but I had to get it out there