TWRP temporary? - OnePlus 7T Questions & Answers

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

Related

[HELP] Pixel 2XL first time owner needing help with custom ROMs

First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
kismetmookz said:
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks, I have been using this and used it as I was wring the article, I'm just trying to see how we flash the ROMs on this puppy.
i use to do these steps
wipe caches
install rom
install twrp.zip for taimen
reboot
setup phone
if you want root then reboot on recovery again then install magisk.
I do these steps and have no failure when flashing; after I wipe the Caches, I flash the ROM and then the TWRP partition flasher and reboot the system. I've waited 15 minutes to have the device boot with no luck and I don't want to risk any longer due to the Pixel 2/ XL having burn-in issues.
thowersome said:
First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
Click to expand...
Click to collapse
Probably because there's not a full OS on the slot your flashing to. If you know your fastboot, it's relatively easy going forward. The Dueces scrip it's great tool for sure to help out. If you want to do it manually, fastboot the factory image to both slots with the -w removed from the flash-all.bat file.
Once that's done, go back to fastboot, and boot into twrp. Then do a twrp factory reset with the swipe bar. Flash the rom, then the twrp.zip and let it boot up. Once in the OS, keep lock screen set to swipe, and do a minimal setup. Then go back to twrp and flash your custom kernel(optional) then flash magisk. And that should do it :good:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
thowersome said:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
Click to expand...
Click to collapse
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Badger50 said:
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Click to expand...
Click to collapse
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
thowersome said:
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
Click to expand...
Click to collapse
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend! ??
Badger50 said:
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend!
Click to expand...
Click to collapse
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
thowersome said:
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
Click to expand...
Click to collapse
Outstanding! Well done :good::good:

Nexus 5X bricked trying to root via TWRP (SuperSu)

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"?

What is the CORRECT way to gain ROOT in PDP3?

I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
AndroidDevices said:
I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
Click to expand...
Click to collapse
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
EvilDobe said:
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
Click to expand...
Click to collapse
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Tulsadiver said:
If he wants recovery, he needs to flash twrp-3.2.1-2-taimen.zip before flashing magisk 16.4
Click to expand...
Click to collapse
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
He did mention that he would want to go back because he had root and recovery.....
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
I'll take TWRP as well, wasnt sure if there was an unofficial version for P or not...
Tulsadiver said:
He did mention that he would want to go back because he had root and recovery.....
Click to expand...
Click to collapse
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Tulsadiver said:
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Click to expand...
Click to collapse
After i flash the TWRP Installer, do i reboot and change slots, or no?
EvilDobe said:
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Click to expand...
Click to collapse
I appreciate BOTH of your help, no need to get all technical!
AndroidDevices said:
After i flash the TWRP Installer, do i reboot and change slots, or no?
Click to expand...
Click to collapse
No, flash Magisk unless you want to try a custom kernel. If so, flash it before Magisk, flash Magisk, then reboot.
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Jameswebb97 said:
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Click to expand...
Click to collapse
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
all43 said:
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
Click to expand...
Click to collapse
Hey,
I was installing from P (9.0 DP3)
I installed TWRP first by flashing the image and then installing the zip file on to the phone.
Next i installed magisk, the installation all went through absolutely fine.
When i hit reboot, it goes onto the white splash screen, then brings up a small progress bar that goes across. This lasts for a minute or two, then dumps me back into TWRP.
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Tulsadiver said:
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Click to expand...
Click to collapse
Thanks, i'll give it a try again with a Factory Reset 1st...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
EvilDobe said:
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
Click to expand...
Click to collapse
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
Don't reboot, TWRP installer installs to both slots.
Flash installer, hit back button, find magisk.zip, flash it.
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
What happens when you just do this:
Get DP flashed & configured. No passwords/patterns/security features.
fastboot boot TWRP3212.img
Flash your magisk 16.4 file.
Reboot.

Question Magisk Update doesn't run very well :(

Hello guys.
Unfortunately the today Magsik Update doesn't run very well on my Device. I did update to the available slot then reboot but the bootsplash now runs since 1H without being able to land on OOS. I'm on 11.2.5.5.LE15 BA + Omega Kernel latest build
Fastboot mode doesn't report any bootloader version nor baseband version.
What's the best way to repair that ? What was the mistake I did to prevent further error while I'm updating magisk or the Kernel ?
Ty @avid_droid but that's what I tried first. It leads me to the exact same type of Boot where nothing happens for 30 minutes excepts the bootsplash logo animation.
I did try to boot from the vanilla boot.img ... but that sent me directly to crashdump mode.
I then boot one last time to magisk_boot.img and .... it worked.
For some reasons everything was wiped on the device even if I never wipe anything from fastboot but no matter ... I'm now back in OOs and try to set it up completly
It's not Magisk, I updated to version 23 with no issues at all.
Also flashed the new Omega kernel afterward, no issues with that either, Magisk was still retained.
I would see if you can get into recovery, if you can then do a system reset and see if the phone will let you set it up again.
For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^
Fre$h said:
For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^
Click to expand...
Click to collapse
I did it the other way round, updated Magisk app, then Magisk itself, rebooted the phone. Installed the latest kernel using EX Kernel manager, it noted that Magisk was there so re-applied it on the new kernel, then rebooted and it was fine after that.
I'm not using any Magisk modules though, not going to risk that until we have a good recovery.
avid_droid said:
Same here. I keep magisk modules to a minimum. I am however playing with substratum and we know how that usually ends up haha. Giving it a go. Trying to remember the signal icons I used to use
Click to expand...
Click to collapse
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either
djsubterrain said:
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either
Click to expand...
Click to collapse
Liv dark works now on op9pro OS11.. I'm using several different themes from livDark now
All I need to do here just hit "install"?
Ive never done it before so I just don't want to screw up.
First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update
Fre$h said:
First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update
Click to expand...
Click to collapse
Thx bro...all good
This is particularly here we miss TWRP to flash magisk uninstaller properly. I like the way we can temporary boot from rooted boot.img but the disadventage is that we need a computer just near us to do that.
Hope everything is now fixed

Question Standard oxygen OS or magisk and lineage ROM?

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

Categories

Resources