Develop Bugs

TWRP bootloops

I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk

Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu

You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !

Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk

I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks

badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.

followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks

badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.

followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!

That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.

badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..

``

tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers

Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk

I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.

Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.

Thanks a lot guys, that did the trick, and done with flashify

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk

Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.

Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!

HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.

GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...

m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time

http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me

This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!

gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..

After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.

Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse

Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

Help. Stuck in TWRP boot loop after downloading latest update OTA

Hi guys,
As soon as I got the OP3 in July, I somehow managed to successfully perform all the steps to get it rooted. I was running OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
OnePlus has been showing me a "new version available" since September, but I very patiently and calmly didn't install it OTA because I didn't want to lose the root.
Finally had a bit of time today, decided I'd finally upgrade. Looked around for the "most recent stable version" and picked this one: OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Followed the steps for flashing using TWRP (twrp-3.0.2-1.28-oneplus3) here:
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
It worked. Yay. Then (god dammit **** ****) I still saw this "new version available" and couldn't swipe it away... I accidentally clicked it and it downloaded the OTA. Fine.
Now I'm stuck in a TWRP boot loop. I tried re-installing the OTA_035.zip from TWRP -- I tried restoring my Nandroid Backup (only had enough room to save "Boot / Recovery / System" partitions, NOT data) -- and I tried ADB Sideloading 16_OTA_013.zip.
I'm stuck rebooting in TWRP 3.0.2-1.
Is there anything I can try before going ballistic and wiping my data?
Thanks.
Marc

Have you tried the newest blu-spark twrp? https://forum.xda-developers.com/devdb/project/?id=15934#downloads

Puddi_Puddin said:
Have you tried the newest blu-spark twrp? https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?

Zingapuro said:
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Click to expand...
Click to collapse
After you've flashed the full zip, flash also the latest stable version of SuperSu (2.79) and latest TWRP from @eng.stk (the v11, it solves the dm-verity error). Then reboot to recovery, it should appear TWRP and the error should't appear.

Zingapuro said:
Hey Puddi_Puddin, thanks for replying.
I never heard of blu-spark, but gave it a shot. Even though the guide seems to apply only to OP3T: https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Anyways I flashed blu-spark with ADB. Booted into blu-spark. Wiped Dalvik/Cache, re-installed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip, wiped Dalvik/Cache, rebooted -- keeps booting into blu-spark TWRP.
Get the "device unlocked" error screen, then the dm-verity error screen, then the OnePlus logo for about 2 seconds, and then back to blu-spark. Repeat ad nauseum.
What state is my device even in? I wouldn't call it bricked... I assume it's still rooted, bootloader works, I can flash different TWRP versions, ...
Any other ideas ... ?
Click to expand...
Click to collapse
There are quite a few versions of TWRP from eng.stk (bluspark). Which one did you install? Try version 11 which is supposedly for N or 3.0.2-19 or 23.

Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:

Zingapuro said:
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Click to expand...
Click to collapse
Try the other two given by me.

Zingapuro said:
Thanks for your help everyone.
I downloaded SuperSU-v2.79 here http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
I flashed both ZIPs OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2 and UPDATE-SuperSU-v2.79-20161211114519.zip
I confirm I'm using twrp-3.0.2-0_blu_spark_v11-op3.img (from the link provided by Puddi_Puddin)
Still see dm-verity error ... still keeps booting into blu_spark TWRP. :crying:
Click to expand...
Click to collapse
From where have you dowloaded the OTA? XDA or OnePlus forum?
I saw a thread regarding the OnePlus 3T update some post above, if you've downloaded from there you've made a mistake if you own a OnePlus 3.

tnsmani said:
Try the other two given by me.
Click to expand...
Click to collapse
You mean 3.0.2-19 or 23. Not blu_spark, right? Ok I tried twrp-3.0.2-23-oneplus3.img from here (https://www.androidfilehost.com/?fid=529152257862684308)
I tried flashing my old images I used last year (I just wanted the phone to boot into *something*) Oxygen_16_OTA_013 & SuperSU-v2.74. Managed to boot. Updated 4 Apps (??) But as soon as the login screen came up, it would reboot ... and keep looping. So I couldn't use the phone, but at least I managed to boot into something other than TWRP.
Next I tried to reinstall OOS4, 16_OTA_035 with SuperSU-v2.79 SR2. Still get the verity error, but at least I managed to boot! But - the phone is *super* buggy/unusable... SIM cards aren't working - I can't access my options screen - and "Developer options are not available for this user".
Now from my "About" screen I have OOS 4.0, Android 7.0, Kernel version 3.18.31-perf+ [email protected] <-- (that's from my TWRP version. right?)
Did the OTA I install from OnePlus directly screw everything up? For that brief moment before I installed it, I tasted a seemingly properly working OOS 4, so I know it's possible...
A few lessons I've learned are -- I can use any recovery (TWRP) to use MTP and flash files and stuff... but in order for the phone to work properly, I have to a) flash the SuperSU (not just the ROM) and b) make sure I have the "correct/proper" TWRP (kernel?) matched with each ROM. Is that kind of right? That's where I'm stuck I guess.
let92 said:
From where have you dowloaded the OTA? XDA or OnePlus forum?
I saw a thread regarding the OnePlus 3T update some post above, if you've downloaded from there you've made a mistake if you own a OnePlus 3.
Click to expand...
Click to collapse
I downloaded from here
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
I'm sure I'm making a ton of mistakes -- that's why I'm here
(I read here https://forum.xda-developers.com/on...mple-trick-t3530685/post70415499#post70415499 that .28 shouldn't be used)
This post mentions a procedure to get rid of verity https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
I'm currently backing up my data, and I'll attempt to follow these instructions to switch to f2fs (hopefully get rid of the verity error) and install OxygenOS 4.0.1 (http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip)
I'm also a bit confused about the best version of SuperSU-v2.79 to use, because blu_spark was writing somewhere (can't find where) that SR1 and SR2 were the cause of battery issues ... So yeah, I've got other things to try, but should the ROM from OOS4.0.1 work with any of them?
THANKS.

Zingapuro said:
You mean 3.0.2-19 or 23. Not blu_spark, right? Ok I tried twrp-3.0.2-23-oneplus3.img from here (https://www.androidfilehost.com/?fid=529152257862684308)
I tried flashing my old images I used last year (I just wanted the phone to boot into *something*) Oxygen_16_OTA_013 & SuperSU-v2.74. Managed to boot. Updated 4 Apps (??) But as soon as the login screen came up, it would reboot ... and keep looping. So I couldn't use the phone, but at least I managed to boot into something other than TWRP.
Next I tried to reinstall OOS4, 16_OTA_035 with SuperSU-v2.79 SR2. Still get the verity error, but at least I managed to boot! But - the phone is *super* buggy/unusable... SIM cards aren't working - I can't access my options screen - and "Developer options are not available for this user".
Now from my "About" screen I have OOS 4.0, Android 7.0, Kernel version 3.18.31-perf+ [email protected] <-- (that's from my TWRP version. right?)
Did the OTA I install from OnePlus directly screw everything up? For that brief moment before I installed it, I tasted a seemingly properly working OOS 4, so I know it's possible...
A few lessons I've learned are -- I can use any recovery (TWRP) to use MTP and flash files and stuff... but in order for the phone to work properly, I have to a) flash the SuperSU (not just the ROM) and b) make sure I have the "correct/proper" TWRP (kernel?) matched with each ROM. Is that kind of right? That's where I'm stuck I guess.
I downloaded from here
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
I'm sure I'm making a ton of mistakes -- that's why I'm here
(I read here https://forum.xda-developers.com/on...mple-trick-t3530685/post70415499#post70415499 that .28 shouldn't be used)
This post mentions a procedure to get rid of verity https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
I'm currently backing up my data, and I'll attempt to follow these instructions to switch to f2fs (hopefully get rid of the verity error) and install OxygenOS 4.0.1 (http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip)
I'm also a bit confused about the best version of SuperSU-v2.79 to use, because blu_spark was writing somewhere (can't find where) that SR1 and SR2 were the cause of battery issues ... So yeah, I've got other things to try, but should the ROM from OOS4.0.1 work with any of them?
THANKS.
Click to expand...
Click to collapse
Unfortunately I haven't tried to update the phone yet, so I don't know what else you can do. But you can also follow the guide posted by @Viper The Ripper here:
https://forum.xda-developers.com/showpost.php?p=70499899&postcount=5
I think that it's simpler and I'll follow that one this weekend when trying to updating my phone

Zingapuro said:
Hi guys,
As soon as I got the OP3 in July, I somehow managed to successfully perform all the steps to get it rooted. I was running OnePlus3Oxygen_16_OTA_013_all_1608061823_765c081a5c8e4dad.zip
OnePlus has been showing me a "new version available" since September, but I very patiently and calmly didn't install it OTA because I didn't want to lose the root.
Finally had a bit of time today, decided I'd finally upgrade. Looked around for the "most recent stable version" and picked this one: OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Followed the steps for flashing using TWRP (twrp-3.0.2-1.28-oneplus3) here:
https://forum.xda-developers.com/oneplus-3/how-to/oxygenos-4-0-android-nougut-official-t3529684
It worked. Yay. Then (god dammit **** ****) I still saw this "new version available" and couldn't swipe it away... I accidentally clicked it and it downloaded the OTA. Fine.
Now I'm stuck in a TWRP boot loop. I tried re-installing the OTA_035.zip from TWRP -- I tried restoring my Nandroid Backup (only had enough room to save "Boot / Recovery / System" partitions, NOT data) -- and I tried ADB Sideloading 16_OTA_013.zip.
I'm stuck rebooting in TWRP 3.0.2-1.
Is there anything I can try before going ballistic and wiping my data?
Thanks.
Marc
Click to expand...
Click to collapse
In my opinion, the only thing you can try is to make a data backup from recovery to any external storage (like a pendrive) by Otg, but it takes some risks. In case this partition has been damaged, you can get issues when you install the rom.
The safest you can do is clean installation in spite of you lose data so, full wipes and a new full rom.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk

You have to install stock recovery, and then reboot into recovery, you will have a instalation error, reboot and loop solved Then, you can flash your twrp and su without loosing data
I discovered following this threath desesperate and going to do a clean install, dowload the files and try to do it steap by steap: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Good luck :good:
P.D.: I have formated system partition, so I lost the android configuration

satisastur said:
You have to install stock recovery, and then reboot into recovery, you will have a instalation error, reboot and loop solved Then, you can flash your twrp and su without loosing data
I discovered following this threath desesperate and going to do a clean install, dowload the files and try to do it steap by steap: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
P.D.: I have formated system partition, so I lost the android configuration
Click to expand...
Click to collapse
Hey Satisastur,
Thanks for taking the time to comment. Yes, actually that's exactly the guide I wanted to follow. But I'm stuck before even starting -- if I make Nandroid Backup now (in ext4) I can't load it back once filesystem changes to f2fs -- isn't that right?
(I also asked the question in that thread: https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page8#post70525818 )
And uh... sorry... what exactly do you mean "android configuration"... like ringtones and stuff?

Zingapuro said:
Hey Satisastur,
Thanks for taking the time to comment. Yes, actually that's exactly the guide I wanted to follow. But I'm stuck before even starting -- if I make Nandroid Backup now (in ext4) I can't load it back once filesystem changes to f2fs -- isn't that right?
(I also asked the question in that thread: https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page8#post70525818 )
And uh... sorry... what exactly do you mean "android configuration"... like ringtones and stuff?
Click to expand...
Click to collapse
Yes, I was on f2fs before this happens, so I only have to install all without formating data. You should do a manual backup to do that, once on recovery, you be able to enter phone data partition from windows. Copy all folders you want to save before formating to f2fs in recovery. Other setup and configuration like ringtones and stuff, all cache and configuration of apps, wallpaper, led, colors and themes... you will lost it. I don't know how to backup that, but its the worst part of formating data... google backup doesn't save all the config
You will start with the android phone start menu, like new, with new dactilar and patron security, etc...

@Zingapuro
Try TWRP 3.0.2_19 and Supersu 2.79 stable. For some people this works and according to eng. stk, only Supersu 2.79 stable is compatible with N.

tnsmani said:
Try TWRP 3.0.2_19 and Supersu 2.79 stable. For some people this works and according to eng. stk, only Supersu 2.79 stable is compatible with N.
Click to expand...
Click to collapse
Tried flashing twrp-3.0.2-19-oneplus3.img and from TWRP installing:
OnePlus3Oxygen_16_OTA_037_all_1701041839_aa64b084a40a4.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
Same issues as described above: boots into 4.0.1, but buggy, SIM cards don't work, no Dev options, etc...
satisastur said:
Copy all folders you want to save before formating to f2fs in recovery.
Click to expand...
Click to collapse
Yeah, I have a feeling this is my only choice. This is the next thing I'll try.

Zingapuro said:
Tried flashing twrp-3.0.2-19-oneplus3.img and from TWRP installing:
OnePlus3Oxygen_16_OTA_037_all_1701041839_aa64b084a40a4.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
Same issues as described above: boots into 4.0.1, but buggy, SIM cards don't work, no Dev options, etc...
Yeah, I have a feeling this is my only choice. This is the next thing I'll try.
Click to expand...
Click to collapse
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
It will fix most of your issues.
For going back to full stock use this guide: https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/
I hope everything will go back to normal.

Hi everyone,
Just want to update that my phone is back up and running. Thanks for your all your help.
More details here:
https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page9#post70588707
Is there any way to update this thread to [SOLVED] ?

Zingapuro said:
Hi everyone,
Just want to update that my phone is back up and running. Thanks for your all your help.
More details here:
https://forum.xda-developers.com/on...rity-simple-trick-t3530685/page9#post70588707
Is there any way to update this thread to [SOLVED] ?
Click to expand...
Click to collapse
Great!
I think you can edit the thread title

Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:

NEED HELP

I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!

bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242

1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.

SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.

bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.

Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?

bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1

All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!

You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.

TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!

bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?

have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.

bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.

noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!

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.