Related
Since, the release of the Android M. Google make it hard to root your device. On MIUI 8 with marshmallow I have been trying to figure out a way to root my device. In almost every case I found myself in a boot loop. So after a long work i finally succeed to root my redmi note 3 with no error and bootloop.
I am not responsible for any damage to your devices,loss or damage caused, or alleged to have been caused, directly or indirectly, by the informations or ideas suggested or referenced, etc. If you get a boot loop you can get back to booting by simply flashing the stock "M" system image via fastboot. or Mi flash tool.
Please try at your own risk. Your warranty is now void.
PRE-REQUIREMENTS
1. redmi note 3 ( SD only) with official MiUI 8 6.9.9 developers rom (marshmallow update) :good:
2. officially unlocked bootloader.
3. TWRP recovery ( alka twrp recommended ).
4. patched boot image given below.
5.brain
METHOD RECOVERY METHOD.
1. Download boot.zip and SuperSu.zip
superSu.zip -https://www.androidfilehost.com/?fid=24727369092694142
boot.img - https://www.androidfilehost.com/?fid=24727369092694141
2. copy both the files (boot.img and SuperSu.zip) to your external SD card.
3. now reboot the device in recovery and go to mount section and mount all the partitions.
4. now go to install and go to SD card and flash SuperSu.zip.
5. as the super su is installed go back in install section and select install image.
6. now you will see only .img files so locate to boot.img and select it.
7. In next window you may see two option as " select partition to flash image:" select the first one option BOOT partition and slide the installation slider and reboot your redmi note 3 SD
boot up may take 5-10 mins so don't we panic. and please mention in the comment was it worked for you or not so I can edit boot image for you..
if i help you give me a thanks, by clicking on thanks button
I am on Miui8 6.9.15 Marshmallow, used supersu.zip, boot.img for rooting..., successfully rooted but some times when I restart the device network gone, sometimes bootloop is occurring.. So I need to flash boot.img again and again.. This is taking a lot of time.. What to do?
Just flash supersu stable using ZCX twrp. Head over supersu xda thread for latest stable flashable zip. Worked for me without any issue.
ubaid137 said:
I am on Miui8 6.9.15 Marshmallow, used supersu.zip, boot.img for rooting..., successfully rooted but some times when I restart the device network gone, sometimes bootloop is occurring.. So I need to flash boot.img again and again.. This is taking a lot of time.. What to do?
Click to expand...
Click to collapse
this boot image is only stable with MIUI 8 6.9.9. i am currently working on a universal boot image so no encryption problem occurred... please wait thanks
tsrajput said:
this boot image is only stable with MIUI 8 6.9.9. i am currently working on a universal boot image so no encryption problem occurred... please wait thanks
Click to expand...
Click to collapse
Also my wifi is not working after root..
Does AUX issue resolved in this ROM?
Yet nobody have solution on it hence; i asked.
Headphones work but AUX cable is not working.
Satav said:
Yet nobody have solution on it hence; i asked.
Headphones work but AUX cable is not working.
Click to expand...
Click to collapse
This is not a rom, its a rooting guide.
any news on this ? any new boot.img. I'm on 6.9.22 beta. thanks
Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?
hexahive said:
Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?
Click to expand...
Click to collapse
http://www.meticulus.co.vu/p/hi6250-custom-rom-installation.html
Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?
hexahive said:
Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?
Click to expand...
Click to collapse
You must already be on EMUI 5 to install EMUI5 based ROMs.
i had to find out if it will work followed this guide (https://www.xda-developers.com/flash-generic-system-image-project-treble-device) and it booted will try other project treble roms and report back here also eveything worked i didnt have a apk crash or force close the little time i used it also the camera apk worked great not as good as stock but not as bad as rros:laugh::laugh::laugh::laugh:
You flashed RR ph Treble or Lineage 15.1. How's the battery ? SOT? Does it support VOLTE?
Please Report
Honor 7x project treble
I flashed the Resurrection Remix phh-Treble and the LineageOS 15.1 phh-Treble will try the third and report back so far the battery life is normal haven't notice any abnormal drain and I can't confirm about the volte
dcraffam said:
i had to find out if it will work followed this guide (https://www.xda-developers.com/flash-generic-system-image-project-treble-device) and it booted will try other project treble roms and report back here also eveything worked i didnt have a apk crash or force close the little time i used it also the camera apk worked great not as good as stock but not as bad as rros:laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
Hi Dude, After seeing your message, I tried this on the Honor 7X BND AL10 with EMUI 8 (Manually updated) with the Lineage OS (ARM 64 A-ONLY DEVICE) using the fastboot method. I wiped everything including system and I tried with both stock recovery installed and Twrp recovery installed and I also tried wiping using fastboot "fastboot -w" command. After that I installed using the fastboot and it went well and shows as finished but when I tried to boot, it just doesn't boot at all. I don't even see the lineage OS boot logo or something and eventually it goes to Huawei E recovery.
Could you please tell me which version exactly you flashed like aosp or RR or Lineage and Arm 64 A-only device or AB-device etc... A lot of people would really appreciate that.
Thetpcguy said:
Hi Dude, After seeing your message, I tried this on the Honor 7X BND AL10 with EMUI 8 (Manually updated) with the Lineage OS (ARM 64 A-ONLY DEVICE) using the fastboot method. I wiped everything including system and I tried with both stock recovery installed and Twrp recovery installed and I also tried wiping using fastboot "fastboot -w" command. After that I installed using the fastboot and it went well and shows as finished but when I tried to boot, it just doesn't boot at all. I don't even see the lineage OS boot logo or something and eventually it goes to Huawei E recovery.
Could you please tell me which version exactly you flashed like aosp or RR or Lineage and Arm 64 A-only device or AB-device etc... A lot of people would really appreciate that.
Click to expand...
Click to collapse
im going to write a quick lil guide on how im doing this for you right now
.................................................HOW TO FLASH GSI ON HONOR 7X ................................
DO SO AT OWN RISK I HOLD NO LIABLILTY
LETS BEGIN
1 you must be on stock emui 8 you must not have a pin set or device encrypted or frp lock and boot loader must be unlocked
2 download one of the 3 images listed here ( https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ )
( i personally only tried the ( LineageOS 15.1 phh-Treble Thread) and the (Resurrection Remix phh-Treble Thread) ((((((download the a only arm64image))))))))
3 download the 8.1 pico gaapps package for arm64 found here ( http://opengapps.org/ )
4 now you must download this twrp i know it works from the honor 7x oreo twrp ill upload it or you can download it from the thread
5 flash the twrp twrp_ramdisk_oreo_7-4-18.img linked in fastboot then reboot recovery (note) there will be two recoverys i upload one needed to flash the (gsi) and the other twrpimgmount_ramdisk.img is used to flash (((twrp backup)) to go back to stock oreo as the first one wont boot once the (gsi) is flashed only the mount twrp.img will the( twrp_ramdisk_oreo_7-4-18.img) will boot with the stock emui beta for some reason
6 create full backup with the twrp_ramdisk_oreo_7-4-18.img flashed in step 5 (personally i backed up everything i could )
7 factory reset data using twrp
8 flash the (gsi) image u downloaded in step 2 to system image .......... tap install change the type from zip to image select the (gsi) and flash to system image partion
9 flash pico gapps 8.1 arm 64 ( the rest are to big o flash ))
reboot device tada you booted a stock (gsi)
i couldnt upload recoveries but they can be found here https://forum.xda-developers.com/devdb/project/?id=25826#downloads
to go back to stock emui fastboot recovery flash the twrpimgmount.img factory reset and restore backup some partions will fail like bdm image,, data,, the partions that do uncheck those and restore backup agin flash stock recovery (RECOVERY_RAMDIS.img) and factory reset and you will be on emui8 agin
let me know if you have any problems im going t ry the phh treble aosp (gsi) now
Thetpcguy said:
Hi Dude, After seeing your message, I tried this on the Honor 7X BND AL10 with EMUI 8 (Manually updated) with the Lineage OS (ARM 64 A-ONLY DEVICE) using the fastboot method. I wiped everything including system and I tried with both stock recovery installed and Twrp recovery installed and I also tried wiping using fastboot "fastboot -w" command. After that I installed using the fastboot and it went well and shows as finished but when I tried to boot, it just doesn't boot at all. I don't even see the lineage OS boot logo or something and eventually it goes to Huawei E recovery.
Could you please tell me which version exactly you flashed like aosp or RR or Lineage and Arm 64 A-only device or AB-device etc... A lot of people would really appreciate that.
Click to expand...
Click to collapse
Try Flashing AOSP 8.1 ARM64 A-Only device system.img as its more updated than lineage or RROS.
Only, A-Only system.img should work on our device as per treble wiki on github.
TrainerRed said:
Try Flashing AOSP 8.1 ARM64 A-Only device system.img as its more updated than lineage or RROS.
Only, A-Only system.img should work on our device as per treble wiki on github.
Click to expand...
Click to collapse
Hi, I already flashed the AOSP version and it's booted up and working fine but I wanted the lineageOS as it has all the built in customisations. I just don't know why the lineage os didn't work as it was reported above the it's working. Maybe it's the variant thing? I have BND AL-10. I don't know Anyway thanks!!
Thetpcguy said:
Hi, I already flashed the AOSP version and it's booted up and working fine but I wanted the lineageOS as it has all the built in customisations. I just don't know why the lineage os didn't work as it was reported above the it's working. Maybe it's the variant thing? I have BND AL-10. I don't know Anyway thanks!!
Click to expand...
Click to collapse
How is the rom ? Is it can be used as daily driver ?
You still using AOSP or back to EMUI already ?
If you don't mind can you write review of Whats working and Whats Not?
TrainerRed said:
How is the rom ? Is it can be used as daily driver ?
You still using AOSP or back to EMUI already ?
If you don't mind can you write review of Whats working and Whats Not?
Click to expand...
Click to collapse
I installed it without any gapps or anything just bare minimum just to see if it boots or not. Here is what I observed during my short stay:laugh:
1. There is no VOLTE
2. The camera is working
3. I can't talk much about battery but there is no crazy drain as such so yeah
4. I don't know why you said it's the latest but the security patch is the same based on March, 2018 and it's android 8.1
5. The launcher seemed like the ice cream sandwich (Took me back to good ol days)
6. It felt smooth and unusual lag
I can't say much and suggest whether or not you can use it as a daily driver when I never used it as a daily driver. It's your call.
Hit the "Thanks" button if you really feel like thanking me:good:
dcraffam said:
.................................................HOW TO FLASH GSI ON HONOR 7X ................................
DO SO AT OWN RISK I HOLD NO LIABLILTY
LETS BEGIN
1 you must be on stock emui 8 you must not have a pin set or device encrypted or frp lock and boot loader must be unlocked
2 download one of the 3 images listed here ( https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ )
( i personally only tried the ( LineageOS 15.1 phh-Treble Thread) and the (Resurrection Remix phh-Treble Thread) ((((((download the a only arm64image))))))))
3 download the 8.1 pico gaapps package for arm64 found here ( http://opengapps.org/ )
4 now you must download this twrp i know it works from the honor 7x oreo twrp ill upload it or you can download it from the thread
5 flash the twrp twrp_ramdisk_oreo_7-4-18.img linked in fastboot then reboot recovery (note) there will be two recoverys i upload one needed to flash the (gsi) and the other twrpimgmount_ramdisk.img is used to flash (((twrp backup)) to go back to stock oreo as the first one wont boot once the (gsi) is flashed only the mount twrp.img will the( twrp_ramdisk_oreo_7-4-18.img) will boot with the stock emui beta for some reason
6 create full backup with the twrp_ramdisk_oreo_7-4-18.img flashed in step 5 (personally i backed up everything i could )
7 factory reset data using twrp
8 flash the (gsi) image u downloaded in step 2 to system image .......... tap install change the type from zip to image select the (gsi) and flash to system image partion
9 flash pico gapps 8.1 arm 64 ( the rest are to big o flash ))
reboot device tada you booted a stock (gsi)
i couldnt upload recoveries but they can be found here https://forum.xda-developers.com/devdb/project/?id=25826#downloads
to go back to stock emui fastboot recovery flash the twrpimgmount.img factory reset and restore backup some partions will fail like bdm image,, data,, the partions that do uncheck those and restore backup agin flash stock recovery (RECOVERY_RAMDIS.img) and factory reset and you will be on emui8 agin
let me know if you have any problems im going t ry the phh treble aosp (gsi) now
Click to expand...
Click to collapse
Thanks for your detailed steps you documented.
But I did much simpiler. (but i did not flash gapps- so that would need to add some steps)
1. starting from stock EmUI 8 with stock recovery
2. Reboot to recovery perform factory reset.
3. when reset is done, while still in recovery plug in usb to phone and pc
4. select reboot, When screen goes off press and hold volume down. You will boot to fastboot
5. fastboot flash system C:\Users\Mr\Downloads\system-arm64-aonly.img
(your path to file will be different, unless you are also user "mr")
To return to stock do same steps but point fastboot flash to the stock emui system.img
Huawei camera works?
Which will you think better? Aosp lineages rr?
Thx
I tried flashing treble and lineage from twrp but neither worked on my bnd-l24. After flashing it just boots to the fastboot screen.
eskimowarrior7 said:
I tried flashing treble and lineage from twrp but neither worked on my bnd-l24. After flashing it just boots to the fastboot screen.
Click to expand...
Click to collapse
I have flashed to L24-- PHH RRos. It worked ok, gave a verdor image miss-match error.
did you factory reset before booting,
mrmazak said:
I have flashed to L24-- PHH RRos. It worked ok, gave a verdor image miss-match error.
did you factory reset before booting,
Click to expand...
Click to collapse
Yes, even tried the process a few more times. No luck.
eskimowarrior7 said:
Yes, even tried the process a few more times. No luck.
Click to expand...
Click to collapse
each time I started with flash stock recovery, then did factory reset
then from recovery reboot directly to fastboot
and fastboot flash system
mrmazak said:
Thanks for your detailed steps you documented.
But I did much simpiler. (but i did not flash gapps- so that would need to add some steps)
1. starting from stock EmUI 8 with stock recovery
2. Reboot to recovery perform factory reset.
3. when reset is done, while still in recovery plug in usb to phone and pc
4. select reboot, When screen goes off press and hold volume down. You will boot to fastboot
5. fastboot flash system C:\Users\Mr\Downloads\system-arm64-aonly.img
(your path to file will be different, unless you are also user "mr")
To return to stock do same steps but point fastboot flash to the stock emui system.img
Click to expand...
Click to collapse
Hi, Could you tell me which model and variant of Honor 7x you are using. I tried this on BND AL10 and it doesn't boot with all the stuff above. However, I could boot into AOSP GSI.
For BND AL10 users, Only the AOSP GSI is working but both the RR and the Lineage are not working. I tried all three with same method.
1. Wiped/ Factory reset
2. Installed using "fastboot flash system system.img"
I posted this message because I wasted a lot of time & data LOL so maybe this would be helpful to others. However, if somehow you manage to do it on AL10, please post it here.
Thetpcguy said:
Hi, Could you tell me which model and variant of Honor 7x you are using. I tried this on BND AL10 and it doesn't boot with all the stuff above. However, I could boot into AOSP GSI.
Click to expand...
Click to collapse
I'm using the L24
Thetpcguy said:
For BND AL10 users, Only the AOSP GSI is working but both the RR and the Lineage are not working. I tried all three with same method.
1. Wiped/ Factory reset
2. Installed using "fastboot flash system system.img"
I posted this message because I wasted a lot of time & data LOL so maybe this would be helpful to others. However, if somehow you manage to do it on AL10, please post it here.
Click to expand...
Click to collapse
Any updates if I can use it as my daily driver?
DISCLAIMER: YOU ARE RESPONSIBLE FOR WHAT YOU DOThe only reason behind posting this guide is because now we have a way to fix device if any unusual things happen after flashing beta builds. Beginners & noobs who doesn't have any idea about flashing stuff should stay away.
PREREQUISITES:
1. Bootloader Unlocked Device
2. OrangeFox
3. Stable OZIP (Android 10 | realmeUI 1.0 | C35)
4. Beta ZIP (Android 11 | realmeUI 2.0 | F06)
5. Unofficial OrangeFox beta build (For realmeUI 2.0 A11 FW only)
6. realmeUI 2.0 stock recovery
7. A11 VBMETA
8. Patched VBMETA
PROCESS TO FLASH:
1. Just to be on safer side we are going to make sure everything is stock & all partitions are unmodified. So reflash latest Stable OZIP (C35) via OrangeFox.
2. Format data & reboot to System (This is optional but better to do it, we never know what might happen with realme device)
3. Reboot back to Bootloader if realmeUI 1.0 boots fine
4. Flash OrangeFox build which you used previously & also flash patched vbmeta (fastboot flash vbmeta patched_vbmeta.img)otherwise you get "Boot is destroyed........"
5. Boot into custom recovery & copy downloaded Beta ZIP
6. Flash the Beta ZIP & format data.
7. Reboot to System. realmeUI 2.0 should boot now.
COMMON ISSUES & FIXES:
1. Device stuck at white realme splash logo
Sol. Few people reported it booted when they flashed patched vbmeta so you can first try that. If doesn't work then you can flash A11 vbmeta (fastboot flash vbmeta vbmeta.img) attached here & reboot to system
2. Device stuck at Yellow realme boot animation
Sol. If it's stuck for more than 2-3mins then reboot to bootloader & format data by executing fastboot erase userdata ., never do fastboot -w it's messing up data partition in A11 due to new changes introduced by realme
3. Stuck in bootloader (fastboot)
Sol. Flash the unofficial OrangeFox rescue build & boot into it, copy C35 OZIP to internal storage. Flash it & format data. Reboot to System. Wait for public realmeUI 2.0 release.
4. Unofficial OrangeFox beta build stuck at Ofox splash & display keeps blinking
Sol. This happens because Ofox can't decrypt realmeUI 2.0 data, only way to boot this ofox build properly is by formatting data, reboot back to bootloader. fastboot erase userdata
5. Device doesn't have realmeUI 2.0 Stock Recovery
Sol. Flash the attached stock recovery
reserved
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
bharatgsp said:
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
Click to expand...
Click to collapse
na it doesn't work
ChromiumPD said:
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Click to expand...
Click to collapse
Right will update guide, thank you
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
kurtextrem said:
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
Click to expand...
Click to collapse
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Zippka224 said:
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Click to expand...
Click to collapse
edited guide, use ofox only. TWRP doesn't seem to work for everyone.
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
4j17h said:
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
Click to expand...
Click to collapse
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Tierri said:
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
Click to expand...
Click to collapse
Well there are two ways, we can use stock recovery to downgrade from beta builds to C34
Another way would be to flash unofficial Ofox build, copy C34 OZIP to internal storage & flash it.
kurtextrem said:
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Click to expand...
Click to collapse
OTA updater app is verifying the update & rebooting to stock recovery, so if we can figure out the same way we can install custom ozips via stock recovery too
How would you recommend to bring over apps & their settings to A11? After formatting data they'll be lost. Which backup method is able to restore them? Have you rooted it already?
Magisk?
Cool ! It works fine thank you.
but I noticed that the "Unofficial OrangeFox beta build" cant mount internal storage issue with following error : "could not mount /data and unable to find crypto footer"
So is there another way to Root my device without wiping data?
Hi
First Thank you for this post .
I want to restore a stock recovery UI 1.0 now i am using orangefox recovery on C.34
can i restore without format data or waiting UI 2.0 stable ??
Many Thanks
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
tuga49 said:
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
Click to expand...
Click to collapse
try to install patched vbmeta its work form me
So for me I dirty flashed the f06.zip beta on c.35 in official [email protected]_1 release and flashed vbmetaA11 but it failed to then i flashed patched_vbmeta.img and voila it booted just fine and optimizing apps appeared.
Thanks very much to Original Poster we can now use Realme UI 2.0 because of him.
Thanks a lot once again
Hi there,
I am using a OnePlus 8 Pro on Oxygen OS 11, Global variant. I have been working on this for at least 10 hours now. I bought the OnePlus 8 Pro orginally running Oxygen OS 12, and when I flashed the recovery (TWRP) for the first time to two slots via this explanation
, I bricked the phone so the only tool accessible to me was fastboot.
Hmm okay, I'll just use MSM tool (https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/) to revert back to oxygen OS so I can continue my mission.
I am trying to install the latest CRDROID from their official website after follow their instructions on here. I get as far as being in fastboot mode with the OEM unlocked, and then I try to flash the recovery they provided. It doesn't work. When I select boot into recovery, I get sent back to fastboot, however, when I flashed the original recovery img for Oxygen OS 11 I took from the payload dumper, it loads fine.
OKAY so now I am thinking that perhaps there is a problem with the recovery provided. That is fine so I choose to use TWRP to flash the custom ROM. Thankfully, it does work, and I am able to load into it through recovery, however when I tried to flash the rom through ABD sideload, from the PC whilst in TWRP, it doesn't load! It gets halfway and stops. I tried this several times to no avail.
I choose to then (after having bricked the phone several times by now and having to revert to factory settings with MSM tool), try to flash the custom ROM from the internal storage of the phone via TWRP. That still does not work. I have also tried this with Project Elixir. No success.
I don't know what to do guys. I have followed the instructions provided, but I don't understand why the phone is not accepting other custom recoveries or allowing me to flash a custom ROM.
All help is very much appreciate.
You have to make sure that you are on OOS11 on BOTH slots.
What i would do now:
Use MSM Tool to go to 11.0.4.4.
Boot the phone and flash 11.0.11.11 via local upgrade TWICE (to ensure its on both slots)
Follow the instructions of CRDROID etc.
Edit: Dont use TWRP on Android12 now.
Read this carefully before you do anything: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/
josephxdaForum said:
Hi there,
I am using a OnePlus 8 Pro on Oxygen OS 11, Global variant. I have been working on this for at least 10 hours now. I bought the OnePlus 8 Pro orginally running Oxygen OS 12, and when I flashed the recovery (TWRP) for the first time to two slots via this explanation
, I bricked the phone so the only tool accessible to me was fastboot.
Hmm okay, I'll just use MSM tool (https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/) to revert back to oxygen OS so I can continue my mission.
I am trying to install the latest CRDROID from their official website after follow their instructions on here. I get as far as being in fastboot mode with the OEM unlocked, and then I try to flash the recovery they provided. It doesn't work. When I select boot into recovery, I get sent back to fastboot, however, when I flashed the original recovery img for Oxygen OS 11 I took from the payload dumper, it loads fine.
OKAY so now I am thinking that perhaps there is a problem with the recovery provided. That is fine so I choose to use TWRP to flash the custom ROM. Thankfully, it does work, and I am able to load into it through recovery, however when I tried to flash the rom through ABD sideload, from the PC whilst in TWRP, it doesn't load! It gets halfway and stops. I tried this several times to no avail.
I choose to then (after having bricked the phone several times by now and having to revert to factory settings with MSM tool), try to flash the custom ROM from the internal storage of the phone via TWRP. That still does not work. I have also tried this with Project Elixir. No success.
I don't know what to do guys. I have followed the instructions provided, but I don't understand why the phone is not accepting other custom recoveries or allowing me to flash a custom ROM.
All help is very much appreciate.
Click to expand...
Click to collapse
And just do payload dump and flash .img in fastboot ROM installer