Temporary TRPW Recovery and working permanent ROOT for [zircon]


Hi follwoing your method after getting mi logo stuck in bootloop, where can i find these files
fastboot flash vendor_boot_ab hyperos_orig_vendor_boot.imgfastboot flash vbmeta_ab hyperos_orig_vbmeta.img
Is there a way you could send those to me.
In the first steps of the post it is mentioned:
- Download: HyperOS 1.0.1.0.UNOMIXM
- Extract the .tgz file and pick out the vendor_boot.img and the vbmeta.img. Rename them to hyperos_orig_vendor_boot.img and hyperos_orig_vbmeta.img
 
  • Like
Reactions: luzzija
how to flash original hyperos i downloaded both recovery and fastboot rom what are the commands, and

How do i reboot in custom recovery(do you mean twrp) after doing all the steps

Flash via fastboot by downloading fastboot image from link (.tgz file) and extracting it, then simply run flash_all.bat when connected in fastboot mode.
To reboot into recovery, simply hold down power and Up buttons.

this is too much for me, is there a way to restore my phone to original miui or hyper os
Exactly same as above, download fastboot image, extract, then flash_all.bat when in fastboot mode
 
Flash via fastboot by downloading fastboot image from link (.tgz file) and extracting it, then simply run flash_all.bat when connected in fastboot mode.
To reboot into recovery, simply hold down power and Up buttons.


Exactly same as above, download fastboot image, extract, then flash_all.bat when in fastboot mode
So i just run that file from folder, or do i need to run it from platform tools folder and then flash it inside cmd

Dude im sorry for stupid questions but i cant really fix this, nothing works. I just want my phone back :emoji_cry:
 
For HyperOS is better to patch init_boot with magisk and flash it on fastboot.
No need to install non usable recovery.
 
Forgot to disble AVB while flashing TWRP ?
Code:
fastboot --disable-verity --disable-verification flash vbmeta_ab vbmeta.img
?
 
  • Like
Reactions: luzzija
But not boot.img !

Our device - Devices with Vendor Boot as Recovery (A/B):

To root hyperOS systems it's necessary to patch init_boot to gain root without flashing new recovery !
Patch a original rom init_boot with magisk and flash it.



Flash original boot and vendor_boot also before reboot !

and use the *_ab to flash both slots !

Step1=Download the hyperos firmware which you are currently using

Step2= Extract it

Step3=Open Extracted Folder / Images Folder

Step4=Find init_boot.img and copy it to the internal storage

Step5=Patch the copied init_boot.img in Magisk

Step6=Move the patched init_boot.img to pc and open Platform tool folder (cmd prompt)

Step7=Enable USB Debugging from Developer Option then switch off the device and put the device into fastboot mode(press power +volume down button)

Step8= After pc detect the device , type this command
fastboot flash init_boot_ab magiskpatch.img

Step9=Reboot the device

Step10=Open Magisk (if the required additional setup promp come , click on ok and reboot the device)


Step 8.1 (only for you) : Flash original boot and vendor_boot :
fastboot flash init_boot_ab originalboot.img
fastboot flash vendor_boot_ab originalvendorboot.img
fastboot oem cdms
 
Last edited:
  • Like
Reactions: luzzija
Two days of working finnaly managed to do it, thanks all for your time and help.
Any predictions on custom rom, are there some active communities on this topic.
 
Last edited:
[EDIT] Added od 1.5.2024 only for HyperOS, Root without flashing non usefull recovery !

ROOT For HyperOS :

Step1=Download the hyperos firmware which you are currently using
Step2= Extract the ROM
Step3=Open Extracted Folder / Images Folder
Step4=Find init_boot.img and copy it to the internal storage
Step5=Patch the copied init_boot.img in Magisk
Step6=Move the patched init_boot.img to pc and open Platform tool folder (cmd prompt)
Step7=Enable USB Debugging from Developer Option then switch off the device and put the device into fastboot mode(press power +volume down button)
Step8= After pc detect the device , type this command
fastboot flash init_boot_ab patchedmagiskfile
Step9=Reboot the device
Step10=Open Magisk (if the required additional setup promp come , click on ok and reboot the device)

Root Sucessfully installed

What is the correct way to apply an ota update to the smartphone without losing root or without causing any damage to the device?
 
[EDIT] Added od 1.5.2024 only for HyperOS, Root without flashing non usefull recovery !

ROOT For HyperOS :

Step1=Download the hyperos firmware which you are currently using
Step2= Extract the ROM
Step3=Open Extracted Folder / Images Folder
Step4=Find init_boot.img and copy it to the internal storage
Step5=Patch the copied init_boot.img in Magisk
Step6=Move the patched init_boot.img to pc and open Platform tool folder (cmd prompt)
Step7=Enable USB Debugging from Developer Option then switch off the device and put the device into fastboot mode(press power +volume down button)
Step8= After pc detect the device , type this command
fastboot flash init_boot_ab patchedmagiskfile
Step9=Reboot the device
Step10=Open Magisk (if the required additional setup promp come , click on ok and reboot the device)

Root Sucessfully installed

Active magisk "root" is gained by patched init_boot and further on by magisk persist.img ... !
Root can be also obtained by apatch by our device !

[/EDIT]

Full tested with 1.0.2.0.UNOMIXM HyperOS version, It remains to be clarified in the steps that you have to unlock the bootloader, with MiUnlockTool python the process is made easier than with the official tool, and it is not paid

Thanks
 
Anyone knows if the ( fastboot flash init_boot_ab init_boot.img ) method works on MIUI 14 (I found a matching fastboot rom.) ? Or an update to HyperOS is required?
 
View attachment 52387
View attachment 52388
View attachment 52389
I replaced the vendor_boot.img with the original vendor_boot.img and got the HyperOs Recovery working.
but I have no luck flashing the original boot.img ( do I need to have already made a pached boot.img in magisk before running the script mabe?)
I am giving up for the night.
Not the init_boot were unable to patch, because the boot ramdisk has the invalid cpio magic and there is a raw ASN1.DER (certificate involved) and also vbmeta AVB is somekind strange. It's for the global MIUI ROM's.

The new version of twrp is out so guess there will be no problems with it.

Hope now we know what I've been talking about, don't worry ...
A lot of zircon phones went in forewer bootloop just because of this problem.
Currently no help to flash out, Only full UFS flash can make a good resoult.
MTK 6886 is a pain in the ass ... Looking to rent an apartment in Hamra? Discover a range of options in this vibrant Beirut neighborhood, known for its lively atmosphere and central location. From modern studios to spacious multi-bedroom units, Hamra offers something for everyone. Enjoy easy access to cafes, shops, and cultural sites. Contact local real estate agents or browse online listings to find your ideal home today!
I’m exploring the process of using Temporary TRWP Recovery for my Android device and am curious about the transition to a permanent ROOT. Can anyone share their experiences or tips on effectively managing this process? Specifically, how do you ensure the stability of your device when shifting from a temporary TRWP Recovery to a permanent ROOT setup? Any advice on best practices, potential pitfalls, or recommended tools would be greatly appreciated. I’m aiming for a balance between functionality and security. Thanks in advance for your insights!