What you guys recommend better option I'm torn between oxy or lineage ROM with magisk for one plus 9 pro. Lmk thoughts Ty.
I used lineage for awhile and can say that battery life will be better, device will perform well, and background apps are more reliable, but I just prefer other ROMs over lineage, it's too basic in terms of customization and OOS is better in some ways. You'll give up the OnePlus camera app and it's optimizations and post-processing. If you're okay using gcam instead of OnePlus cam, then lineage is ok, but I'd recommend crDroid over it most definitely. Its equally stable but felt snappier and more complete feature set in my use. Plus the maintainer updates frequently and does a good job.
Yeah? Alright ... Thank you for your response I appreciate that, so you definitely reccommend using a custom ROM oppose to oxygen? And what is best for one plus 9 pro , CR? And do I use TWRP recovery ?! Thank you appreciate it .
Anonymous-Ciphers said:
Yeah? Alright ... Thank you for your response I appreciate that, so you definitely reccommend using a custom ROM oppose to oxygen? And what is best for one plus 9 pro , CR? And do I use TWRP recovery ?! Thank you appreciate it .
Click to expand...
Click to collapse
crDroid is the best I've used in terms of reliability, though I've been hearing EvolutionX is just as stable and on similar update schedule, and has even better customization, but I can't give full recommendation as I've only used on an older phone. But definitely had better experience with custom ROMs than OOS, so if you can unlock the bootloader, I'd go for it. You'll want TWRP recovery, but don't technically need it. You'll also want to have the newest OOS installed to avoid vendor driver issues (I haven't heard of a real problem except for T-Mobile model needing the vendor modem reflashed every time you update a custom ROM, better safe than sorry though)
Best way to flash would be to download TWRP (found in the development tab here on XDA) and get phone booted into bootloader. Then run
fastboot boot /location/of/twrp.img
Factory reset inside twrp
Then enter adb sideload mode and run
adb sideload /location/of/rom.zip
It WILL get stuck at 47% but will complete successfully if you wait 2-3 min. once finished, I'd repeat the exact same process once more as that will write your other boot slot to assure they're the same and prevent issues (lineage has a script for it, but doing the install process twice works just fine for me). From there, if you want TWRP installed permanently, in the advanced tab, you'll find "install current TWRP" and do that, reboot back into recovery to flash the magisk.apk as a zip file, and it will modify the boot to be running magisk.
You will find other ways of installing if you look at guides and such but what I've outlined works for every ROM and TWRP version I've used on my OP9p. You might see to flash the zip directly in TWRP instead of adb sideload, but some ROMs don't install that way, while adb sideload pretty much always works
Edited: forgot to add info that it's best to flash both A/B slots, added steps
thats_the_guy said:
crDroid is the best I've used in terms of reliability, though I've been hearing EvolutionX is just as stable and on similar update schedule, and has even better customization, but I can't give full recommendation as I've only used on an older phone. But definitely had better experience with custom ROMs than OOS, so if you can unlock the bootloader, I'd go for it. You'll want TWRP recovery, but don't technically need it. You'll also want to have the newest OOS installed to avoid vendor driver issues (I haven't heard of a real problem except for T-Mobile model needing the vendor modem reflashed every time you update a custom ROM, better safe than sorry though)
Best way to flash would be to download TWRP (found in the development tab here on XDA) and get phone booted into bootloader. Then run
fastboot boot /location/of/twrp.img
Factory reset inside twrp
Then enter adb sideload mode and run
adb sideload /location/of/rom.zip
It WILL get stuck at 47% but will complete successfully if you wait 2-3 min. once finished, I'd repeat the exact same process once more as that will write your other boot slot to assure they're the same and prevent issues (lineage has a script for it, but doing the install process twice works just fine for me). From there, if you want TWRP installed permanently, in the advanced tab, you'll find "install current TWRP" and do that, reboot back into recovery to flash the magisk.apk as a zip file, and it will modify the boot to be running magisk.
You will find other ways of installing if you look at guides and such but what I've outlined works for every ROM and TWRP version I've used on my OP9p. You might see to flash the zip directly in TWRP instead of adb sideload, but some ROMs don't install that way, while adb sideload pretty much always works
Edited: forgot to add info that it's best to flash both A/B slots, added steps
Click to expand...
Click to collapse
Thank you kindly I still can't get it. I tried doing cr android but it said I cant downgrade not allowed and twrp won't work, then when sideload cr android and it boots but my screen touch doesn't work and really liked the ROM would appreciate someone help
I return to OOS from Lineage OS last month, after using Lineage for a long time. Just because camera on Lineage just can't fit my needs. I tried Google Camera, but there are some bugs and still OOS camera is the best.
Anonymous-Ciphers said:
Thank you kindly I still can't get it. I tried doing cr android but it said I cant downgrade not allowed and twrp won't work, then when sideload cr android and it boots but my screen touch doesn't work and really liked the ROM would appreciate someone help
Click to expand...
Click to collapse
Haven't seen a no touch issue before. Well I'd try another factory reset inside TWRP and flash again, I believe 9 and 9 pro are unified for cr but also make sure you got the right zip. If that doesn't work, OOS 11.2.7 is the newest full zip file you can download from OnePlus, maybe try flashing that, and try installing crDroid without updating to 11.2.8 or 11.2.9. If that doesn't work, might be at a loss.
How come twrp I can't get going
Related
So, I think I had all my bases covered to install lineage OS.
I unlocked bootloaders from htcdev
I turned S-off with sunshine
I installed twrp
I didn't seem to have any issues doing these (installed root during)
But when I go to install the latest lineage os from twrp, then gaps it seems to work fine. I wipe cache then reboot.
When I reboot it gets stuck in a loop at the android logo where it shines back and forth.
I checked my download screen and it says OS-1.80.651.30, which I understand is android 6. Lineage is 7, is that where the hangup is... if so what do I do to fix that? In my previous rom experiences I just flashed the zip and was good.
I feel like I'm missing a step or missed something. Any help would be appreciated. Thanks!
Well in general it is always better if your firmware matches the ROMs base to make sure everything is working as expected. There are some ROMs booting on MM firmware and even fingerprint scanner works on them due to modifications by their developers. Best would be to ask if you need a more recent firmware - and if so which one - on the respective ROM thread.
A second possibility could be the TWRP version you're using. To flash N ROMs successfully make sure you got TWRP 3.0.3-0 unofficial installed. If not head over to the TWRP thread and get it from download tab.
I always try to run the latest firmware just to make sure.
Sent from my htc_pmeuhl using XDA Labs
Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance
So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.
jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app
SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.
i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.
so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?
aaaaand it booted!
I just flashed Resurrection Remix GSI by phhusson and it works. With EMUI 8 beta you can now flash a treble ROM. Still, this requires further testing so be careful. I'm not responsible for bricked phones. Here are the steps:
1. Make sure your device is on EMUI 8 beta with unlocked bootloader (guide: https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601)
2. Download GSI from this thread https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688 and move it to the folder where you installed ADB
Note: Honor 6x doesn't support seamless update so you want the A-only image, not the A/B one. Just in case you don't know already, Honor 6x has arm64 architecture.
3. Open cmd and navigate to your ADB folder
4. Reboot your phone to fastboot mode and type 'fastboot flash system name-of-the-image.img' where name-of-the-image.img is your downloaded GSI.
5. Hit enter and wait for it to finish installing
6. Famous words: "Reboot and pray"
Problems:
1. Since we don't have a treble-compatable TWRP build yet, there is no way to install gapps for now. I will try to find an image that includes them.
2. All the problems present on the actual ROM (check ROM thread)
3. There are likely others. (There always are some)
I'd like it if others tried to flash this and share their experiences here.
Thanks to @phhusson, @vovan1982, @HassanMirza01, Huawei, RR team and everybody else I forgot to mention.
How's the battery life?
Amirk365 said:
How's the battery life?
Click to expand...
Click to collapse
I'm flashing AOSP right now. It has gapps preloaded so I'll update when I've tested enough.
TheParallelOne said:
I'm flashing AOSP right now. It has gapps preloaded so I'll update when I've tested enough.
Click to expand...
Click to collapse
Thanks,in the mean time I'm looking for a proper cable to root my phone lol
UPDATE:
I flashed AOSP GSI and it boots normally as well. Has gapps and root as well, but you'll need the og supersu (phh's). Chainfire's su doesn't work. Also, you can't give adb root access via dev options so you cant pull boot image to patch it with magisk right away. I'm also unable to get stock camera to work but will experiment with that in the future. Battery life seems a bit better than on nougat roms but then again I'm running pure AOSP with no major battery consumer app on it for now. That's it for now.
@TheParallelOne
Did you try to use stock camera app from there?
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/huawei-stock-camera-app-treble-roms-t3735169
Cool that you already tried to flash a GSI image :good:
TheParallelOne said:
aaaaand it booted!
I just flashed Resurrection Remix GSI by phhusson and it works. With EMUI 8 beta you can now flash a treble ROM. Still, this requires further testing so be careful. I'm not responsible for bricked phones. Here are the steps:
1. Make sure your device is on EMUI 8 beta with unlocked bootloader (guide: https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601)
2. Download GSI from this thread https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688 and move it to the folder where you installed ADB
Note: Honor 6x doesn't support seamless update so you want the A-only image, not the A/B one. Just in case you don't know already, Honor 6x has arm64 architecture.
3. Open cmd and navigate to your ADB folder
4. Reboot your phone to fastboot mode and type 'fastboot flash system name-of-the-image.img' where name-of-the-image.img is your downloaded GSI.
5. Hit enter and wait for it to finish installing
6. Famous words: "Reboot and pray"
Problems:
1. Since we don't have a treble-compatable TWRP build yet, there is no way to install gapps for now. I will try to find an image that includes them.
2. All the problems present on the actual ROM (check ROM thread)
3. There are likely others. (There always are some)
I'd like it if others tried to flash this and share their experiences here.
Thanks to @phhusson, @vovan1982, @HassanMirza01, Huawei, RR team and everybody else I forgot to mention.
Click to expand...
Click to collapse
Bro do complete research first. we have fully working twrp. use twrp on elemental Rom. and installation procedure is also completely wrong. first flash twrp from fastboot using command fastboot flash recovery_ramdisk RECOVERY V2.img then check the recovery and reboot to boot loader then flash system image then reboot to recovery do formats data then install gapps then again reboot to boot loader then flash stockrecovery from dot os thread which is also treble rom then reboot to stock recovery do factory reset now device will boot fine.
Also there are some bugs like mtp,battery drain,heating issues on normal usage and slow charging in some rims. I have tried 4 roms and decided go back to elemental Rom. but these treble roms much better than nougat custom roms comparing to them these can be used as daily driver. pure Android 8.1 roms with all latest features.
Can you provide screenshots please
That's great news. TFS bro.
Edwin Davis said:
Can you provide screenshots please
Click to expand...
Click to collapse
mtp working on some roms and battery drain is not that much compared to emui 8 stock now im gonna try more roms.
Treble roms are much faster and more stable you can't find any bugs. even I was surprised honor 6x can run stock android with this much stability.
Battery drain comparison
on stock emui 5 5% drain for hour while watching movie in mx player no apps running in background all freezed.
on emui 8/treble roms 7-8% while watching movie on mx player but didn't freezed any apps only apps running telegram and whatsapp.
conclusion if u r in emui8 go for treble roms for complete pixel experience
4G VoLTE
it got volte?
What about the volte and gcam ?
I'll have my new OP7T by Friday, coming from OP5T. I've been reading through some of the threads. Is it correct that TWRP doesn't survive a reboot? Or is that old news?
That might be fine for me. I don't flash roms nearly as much as I used to and I think stock rooted is the way I'll go from now on.
So if I unlock the bootloader, install TWRP and root... can I then receive Ota updates?
That'd be pretty awesome.
***Also I'm tempted to flash a custom rom despite what I said . So if anyone knows of a stable one that performs well as a daily driver, please respond. Thanks
KLit75 said:
I'll have my new OP7T by Friday, coming from OP5T. I've been reading through some of the threads. Is it correct that TWRP doesn't survive a reboot? Or is that old news?
That might be fine for me. I don't flash roms nearly as much as I used to and I think stock rooted is the way I'll go from now on.
So if I unlock the bootloader, install TWRP and root... can I then receive Ota updates?
That'd be pretty awesome.
***Also I'm tempted to flash a custom rom despite what I said . So if anyone knows of a stable one that performs well as a daily driver, please respond. Thanks
Click to expand...
Click to collapse
Hi! If you BOOT twrp it will not survive a reboot, if you FLASH twrp it will still there till you reflash stock recovery or rom update. You can't receive OTA "upgrade" package with root, only full rom, maybe through oxygen updater.
And last, i've flashed Resurrection Remix this saturday, and it's amazing. Battery performance like stock oos (about 5/5:30h sot against the 4h sot of my previous op6), 90hz display and infinity customization to choose from. You're not going wrong if you try RR, trust me. RR on my "old" oneplus 6 was not like this. Here there's no bug at all and you can customize everything. Only thing that i miss is Dolby Atmos (it's still there but you can't personalize sound effect WIP in next release) and per-app lock with FP (not really a great miss).
I hope to be proved helpful
Hitman478™ said:
Hi! If you BOOT twrp it will not survive a reboot, if you FLASH twrp it will still there till you reflash stock recovery or rom update. You can't receive OTA "upgrade" package with root, only full rom, maybe through oxygen updater.
And last, i've flashed Resurrection Remix this saturday, and it's amazing. Battery performance like stock oos (about 5/5:30h sot against the 4h sot of my previous op6), 90hz display and infinity customization to choose from. You're not going wrong if you try RR, trust me. RR on my "old" oneplus 6 was not like this. Here there's no bug at all and you can customize everything. Only thing that i miss is Dolby Atmos (it's still there but you can't personalize sound effect WIP in next release) and per-app lock with FP (not really a great miss).
I hope to be proved helpful
Click to expand...
Click to collapse
Thanks for the explanation!
Sorry I'm still unclear on TWRP. I remember years ago I had a device that would not allow TWRP to stick. If you needed to flash a rom or make changes to system, you'd hook it up to your computer and use adb to boot TWRP one time.
But that was because twrp wouldn't stick. Why would you boot TWRP if you are able to make it permanent by flashing it?
I'm sure there's a simple explanation but I can't think of it...
Ideally I think I'd keep the stock recovery with root, then remove root for an update and root again. But pretty sure the only way to root is to have TWRP installed.
Thanks again for the info!
KLit75 said:
Thanks for the explanation!
Sorry I'm still unclear on TWRP. I remember years ago I had a device that would not allow TWRP to stick. If you needed to flash a rom or make changes to system, you'd hook it up to your computer and use adb to boot TWRP one time.
But that was because twrp wouldn't stick. Why would you boot TWRP if you are able to make it permanent by flashing it?
I'm sure there's a simple explanation but I can't think of it...
Ideally I think I'd keep the stock recovery with root, then remove root for an update and root again. But pretty sure the only way to root is to have TWRP installed.
Thanks again for the info!
Click to expand...
Click to collapse
With oos I was usually boot with twrp only for flashing magisk, in that case i don't really need it beside for flashing root. With RR I keep twrp flashed only "to have it" not really useful. I understand what you said, with old partition system root gone away without twrp because recovery.img was inside boot.img (magisk destination partition, and for decryption things) but with Android 10 these partitions are separated again, like old times.
Hitman478™ said:
With oos I was usually boot with twrp only for flashing magisk, in that case i don't really need it beside for flashing root. With RR I keep twrp flashed only "to have it" not really useful. I understand what you said, with old partition system root gone away without twrp because recovery.img was inside boot.img (magisk destination partition, and for decryption things) but with Android 10 these partitions are separated again, like old times.
Click to expand...
Click to collapse
I think I'm following you. So if I want to remain stock but rooted, I would just boot twrp, root it, then repeat that if I want to take a stock update?
To simplify, I guess, is it possible to run a rooted stock with a stock recovery?
Sorry. I've been tinkering with my phones less and less, and some things have changed in that time.
Take the update, DO NOT REBOOT YET! Then install Magisk from the Magisk manager. When it says to select method, choose to "Install to Inactive Slot (After OTA)" , then reboot.
No TWRP needed after an update to install root.
KLit75 said:
I think I'm following you. So if I want to remain stock but rooted, I would just boot twrp, root it, then repeat that if I want to take a stock update?
To simplify, I guess, is it possible to run a rooted stock with a stock recovery?
Sorry. I've been tinkering with my phones less and less, and some things have changed in that time.
Click to expand...
Click to collapse
Yes it's possible to run rooted stock without twrp, I was like that before flashing RR
If you want to root still after ota don't reboot when it had finished to install, instead go to magisk and choose "install on inactive slot after ota" then reboot.. But with this process I highly suggest you to disable and uninstall all module first, because sometimes, when you reboot you got problems if you don't remove modules, and for "problems" I mean like instant reboot after phone boot up, forcing you to uninstall magisk via recovery or reflashing stock boot.img
Btw, twrp is useful on custom because if you go in boot loop you can access your internal storage through it and eventually make a backup of all your files
Hitman478™ said:
Yes it's possible to run rooted stock without twrp, I was like that before flashing RR
If you want to root still after ota don't reboot when it had finished to install, instead go to magisk and choose "install on inactive slot after ota" then reboot.. But with this process I highly suggest you to disable and uninstall all module first, because sometimes, when you reboot you got problems if you don't remove modules, and for "problems" I mean like instant reboot after phone boot up, forcing you to uninstall magisk via recovery or reflashing stock boot.img
Btw, twrp is useful on custom because if you go in boot loop you can access your internal storage through it and eventually make a backup of all your files
Click to expand...
Click to collapse
Thanks. I used to change roms constantly a few years back. Now my phone has become something I can't get by without, for even a matter of hours on some days. So as much as I love trying things out, I just want a stable driver with little fuss. But I don't think I can go without root. I haven't since 2013.
OOS was good enough for me, though I heard theyre becoming more bloated and I hate the gestures in Android 10. It's those little things that I want to be able to change.
Do you use the modified magisk boot image to root?
KLit75 said:
Thanks. I used to change roms constantly a few years back. Now my phone has become something I can't get by without, for even a matter of hours on some days. So as much as I love trying things out, I just want a stable driver with little fuss. But I don't think I can go without root. I haven't since 2013.
OOS was good enough for me, though I heard theyre becoming more bloated and I hate the gestures in Android 10. It's those little things that I want to be able to change.
Do you use the modified magisk boot image to root?
Click to expand...
Click to collapse
Yes I'm just like you, I use my phone constantly for work, I can't accept a rom with FC and other bugs.. I need that things working properly and RR it's exceptional.
Yes I was using modified boot.img for rooting OOS, selfmade with guide in the thread because my phone is the BA version (europe) and everytime no one post boot.img ready for this. But it's not really complicated to DIY
Hitman478™ said:
Yes it's possible to run rooted stock without twrp, I was like that before flashing RR
If you want to root still after ota don't reboot when it had finished to install, instead go to magisk and choose "install on inactive slot after ota" then reboot.. But with this process I highly suggest you to disable and uninstall all module first, because sometimes, when you reboot you got problems if you don't remove modules, and for "problems" I mean like instant reboot after phone boot up, forcing you to uninstall magisk via recovery or reflashing stock boot.img
Btw, twrp is useful on custom because if you go in boot loop you can access your internal storage through it and eventually make a backup of all your files
Click to expand...
Click to collapse
I do not disable or uninstall modules with this method. But I will in the future, it only takes one OH SH!T moment, before you wish you did. My luck is bound to run out.
Droid_Nut said:
I do not disable or uninstall modules with this method. But I will in the future, it only takes one OH SH!T moment, before you wish you did. My luck is bound to run out.
Click to expand...
Click to collapse
:laugh: I've passed too much "bad moments" with update and magisk, so now prevention is my cure
So I've long been had PE (Pixel Experience) installed on my phone and I've never had any issues flashing recovery, not even in the CFW days. But I noticed there was an update to PE last month and decided I should update it. The instructions are clean, you must start fresh (format data, system, dalvik, etc..) so prior to attempting to install PE, first order of business is to get a newer recovery. Simple right? I tried flashing the twrp that was listed in the instrucitons, I tried Orange Fox, which worked only once but hasn't since. So if figured, ok, too many issues, let me start from scratch. I fastboot flashed my phone using the last Miui firmware I had on my phone. Didn't wan't the newer firmware getting in the way with whatever new locks they may have installed. Flashing to factory using fastboot went without a hitch. I first opted to save my data, but that failed at boot, so I did a flash-all.bat and that got me to a pristine factory from Miui 11 Android 9. Enabled USB Debug and Relaxed USB App upload secruity settings and now I should be able to boot into the bootloader and Flash any recovery right? No such luck. Flashed the latest and even a version prior of TWRP and Orange fox and they just don't boot. When I hold the Vol Up + Power it boots showing the Redmi logo and just when it's suppoed to show the splash screen of whatever recovery I'm trying, it simply reboots and I'm sure the miui os already restored the original factory so I try flashing again and no dice. I've flashed and tried to boot probably 50 times by now. Only once did I get a little ray of hope when I flashed Orange fox after doing a clean fastboot rom flash and I simply got 3 menu choices asking to boot to recovery, bootloader ,or system. I of course chose recovery and FAIL it just went black screen and rebooted to system! OK, so frustrated, I went and downloaded the latest firmware from Mi and for sure, whever it has that's preventing booting into recovery for sure will get erased and started from scratch, especially cuz I'm going from Miui11 Android 9 all the way up to Miui 12.5 Android 11 right? After re-enableing the developer setting and adjusting the settings and making sure my computer is authorized on the phone I rebooted to the bootloader, flashed Orange Fox and FAIL! still no joy. WTF?!? This is getting frustrating. What am I doing wrong? What can I do to try and fix this?
Tin_Man_0 said:
So I've long been had PE (Pixel Experience) installed on my phone and I've never had any issues flashing recovery, not even in the CFW days. But I noticed there was an update to PE last month and decided I should update it. The instructions are clean, you must start fresh (format data, system, dalvik, etc..) so prior to attempting to install PE, first order of business is to get a newer recovery. Simple right? I tried flashing the twrp that was listed in the instrucitons, I tried Orange Fox, which worked only once but hasn't since. So if figured, ok, too many issues, let me start from scratch. I fastboot flashed my phone using the last Miui firmware I had on my phone. Didn't wan't the newer firmware getting in the way with whatever new locks they may have installed. Flashing to factory using fastboot went without a hitch. I first opted to save my data, but that failed at boot, so I did a flash-all.bat and that got me to a pristine factory from Miui 11 Android 9. Enabled USB Debug and Relaxed USB App upload secruity settings and now I should be able to boot into the bootloader and Flash any recovery right? No such luck. Flashed the latest and even a version prior of TWRP and Orange fox and they just don't boot. When I hold the Vol Up + Power it boots showing the Redmi logo and just when it's suppoed to show the splash screen of whatever recovery I'm trying, it simply reboots and I'm sure the miui os already restored the original factory so I try flashing again and no dice. I've flashed and tried to boot probably 50 times by now. Only once did I get a little ray of hope when I flashed Orange fox after doing a clean fastboot rom flash and I simply got 3 menu choices asking to boot to recovery, bootloader ,or system. I of course chose recovery and FAIL it just went black screen and rebooted to system! OK, so frustrated, I went and downloaded the latest firmware from Mi and for sure, whever it has that's preventing booting into recovery for sure will get erased and started from scratch, especially cuz I'm going from Miui11 Android 9 all the way up to Miui 12.5 Android 11 right? After re-enableing the developer setting and adjusting the settings and making sure my computer is authorized on the phone I rebooted to the bootloader, flashed Orange Fox and FAIL! still no joy. WTF?!? This is getting frustrating. What am I doing wrong? What can I do to try and fix this?
Click to expand...
Click to collapse
OK, your one sentence text is a bit difficult to read but I'll try to explain the best I can (there might be errors).
You can split the custom recoveries into two types. CFW and non-CFW.
You can split the custom ROMs into two types. CFW and non-CFW.
CFW recoveries have to go hand in hand with CFW custom ROMs.
non-CFW recoveries have to go hand in hand with non-CFW custom ROMs.
What about stock MIUI? That depends on the custom recovery. The developer usually states which ROMs the recovery is designed for (if CFW or non-CFW; if stock MIUI 12.0.x or stock MIUI 12.5.x; etc). If you mix a CFW recovery with a non-CFW custom ROM you'll probably have issues.
If you install a compatible recovery for MIUI 12.5.x and simply let MIUI boot into system it erases the custom recovery, which means you have to install the custom recovery again and boot straight into it. That's why some recoveries have extras to prevent its erasure (you'll have to research this).
This video below should contain everything you need.
Compass.
Compass Linux said:
OK, your one sentence text is a bit difficult to read but I'll try to explain the best I can (there might be errors).
You can split the custom recoveries into two types. CFW and non-CFW.
You can split the custom ROMs into two types. CFW and non-CFW.
CFW recoveries have to go hand in hand with CFW custom ROMs.
non-CFW recoveries have to go hand in hand with non-CFW custom ROMs.
What about stock MIUI? That depends on the custom recovery. The developer usually states which ROMs the recovery is designed for (if CFW or non-CFW; if stock MIUI 12.0.x or stock MIUI 12.5.x; etc). If you mix a CFW recovery with a non-CFW custom ROM you'll probably have issues.
If you install a compatible recovery for MIUI 12.5.x and simply let MIUI boot into system it erases the custom recovery, which means you have to install the custom recovery again and boot straight into it. That's why some recoveries have extras to prevent its erasure (you'll have to research this).
This video below should contain everything you need.
Compass.
Click to expand...
Click to collapse
Way ahead of you my friend. I got off of CFW roms several versions ago. BUT I think I found what the problem may have been. The official TWRP gives instructions to disable AVB via fastboot flashing vbmeta with the following command. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. I'm guessing the custom TWRP or Orange fox are supposed to have that command built into it or something cuz they didn't mention it in their instructions to flash the roms. Unfortuately I upgraded to MIUI 12.5 Android 11 and Xaiomi appears to have added some new locks because I'm reading reports from other users that attempting to flash custom recovery roms on MIUI 12.5 is resulting in bootloops. Sigh, just my luck. Stuck until further notice. BTW, once upgraded to 12.5 there's no flashing previous versions either. Exactly what I was originally trying to avoid, but I needed a working phone, so I'm on stock again for the time being.
Tin_Man_0 said:
Way ahead of you my friend. I got off of CFW roms several versions ago. BUT I think I found what the problem may have been. The official TWRP gives instructions to disable AVB via fastboot flashing vbmeta with the following command. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. I'm guessing the custom TWRP or Orange fox are supposed to have that command built into it or something cuz they didn't mention it in their instructions to flash the roms. Unfortuately I upgraded to MIUI 12.5 Android 11 and Xaiomi appears to have added some new locks because I'm reading reports from other users that attempting to flash custom recovery roms on MIUI 12.5 is resulting in bootloops. Sigh, just my luck. Stuck until further notice. BTW, once upgraded to 12.5 there's no flashing previous versions either. Exactly what I was originally trying to avoid, but I needed a working phone, so I'm on stock again for the time being.
Click to expand...
Click to collapse
You might like this MIUI 12.5.x mod:
Updated version of the mod (11/08/2021): MOD EDIT: Link Removed
Downgrade MIUI 12.5.x to MIUI 12.0.x via TWRP:
Good luck!
Compass.
Compass Linux said:
You might like this MIUI 12.5.x mod:
Updated version of the mod (11/08/2021): MOD EDIT: Link Removed
Downgrade MIUI 12.5.x to MIUI 12.0.x via TWRP:
Good luck!
Compass.
Click to expand...
Click to collapse
Thanks! I'll give these a try, but what I was looking for and don't see where exactly to download is that batch file and version of twrp that was show on the video. They launched a batch file and adb waited for the phone and then off it went. I assume that these some extra little steps added to the batch file besides the "fastboot flash recovery recovery.img" routine? Also, the moded ROM looks intresting from the pling page. Can if just copy the "flash_all.bat" from Miui's fastboot firmware installer and drop it in santosh's moded firmware files list? That would be just way to convenient, but keeping my fingers crossed lol.
Tin_Man_0 said:
Thanks! I'll give these a try, but what I was looking for and don't see where exactly to download is that batch file and version of twrp that was show on the video. They launched a batch file and adb waited for the phone and then off it went. I assume that these some extra little steps added to the batch file besides the "fastboot flash recovery recovery.img" routine? Also, the moded ROM looks intresting from the pling page. Can if just copy the "flash_all.bat" from Miui's fastboot firmware installer and drop it in santosh's moded firmware files list? That would be just way to convenient, but keeping my fingers crossed lol.
Click to expand...
Click to collapse
On MIUI 12 Android 10: MOD EDIT: Link Removed
On MIUI 12.5 Android 11: MOD EDIT: Link Removed
The batch and twrp are inside each fastboot zip.
Yeah, don't mix flash_all.bat from a stock MIUI with any custom ROM.
Compass.
Yes! You are the man! Finally. It took every try too ciz I had even found a BRP Twrp, just one version prior to the link you provied Ver 2.7 and that still failed. Tried it a couple dozen which ways too. But this last one finally did the trick. I noticed they went and hid all the files and left only the batch files to launch. I'm guessing people were trying to use the files the wrong way lol. So one last question, cuz I got TWRP running now on my phone and I'm wondering if it'll still be there if I reboot it? I assume this twrp automatically kills the MIUI recovery restore from attempting to take back the recovery?
Tin_Man_0 said:
Yes! You are the man! Finally. It took every try too ciz I had even found a BRP Twrp, just one version prior to the link you provied Ver 2.7 and that still failed. Tried it a couple dozen which ways too. But this last one finally did the trick. I noticed they went and hid all the files and left only the batch files to launch. I'm guessing people were trying to use the files the wrong way lol. So one last question, cuz I got TWRP running now on my phone and I'm wondering if it'll still be there if I reboot it? I assume this twrp automatically kills the MIUI recovery restore from attempting to take back the recovery?
Click to expand...
Click to collapse
I haven't tested either of those recoveries myself but both should survive a MIUI reboot (I've downloaded both recoveries and looking at the files inside they should stay).
The first video I posted covers TWRP for both MIUI 12.0.x and MIUI 12.5.x.
User Alice! got TWRP to be permanent (she's on stock MIUI): https://forum.xda-developers.com/t/cant-flash-custom-recovery.4318347/
Compass.