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
Related
Hello guys,
As stated in the title, I can not boot into recovery since I flashed CM 14.1. I already tried reflashing TWRP, booting TWRP via fastboot, using another, more recent TWRP image.
This is rather urgent, since, although I can boot CM 14.1 without any problem, I forgot to do a Titanium Backup of two apps, so I have to restore a nandroid backup to get those back, which is kind of hard, without access to TWRP. Using TWRP Explorer is out of question, since that, as far as I know, does not work with encrypted backups.
Flashing via Flashify does not work either.
I just tried with the most recent CM Recovery, that does work, but that does not really help, since that won't restore TWRP Backups..
Greetings
jcgruenhage
delete
Just flash twrp again!?
Flash the twrp in the following link https://www.androidfilehost.com/? using flashify from play store .This helped me
daleski75 said:
Just flash twrp again!?
Click to expand...
Click to collapse
That did not work, at least not with the official TWRP. Flashing this TWRP gave me TWRP back, but now restoring the Backup somehow did not work as expected, the old CM 14.1 unofficial build that is in that backup won't boot.
I'll try only restoring the data part onto the official build, is there anything else you can recommend? Another firmware? Something?
Oh and by the way, thank you, for helping here and for you CM 14.1 builds, somehow I couldn't build CM 14.1 and 14, so having your builds was really helpful.
What version of OOS was you on prior to flashing CM14.1?
daleski75 said:
What version of OOS was you on prior to flashing CM14.1?
Click to expand...
Click to collapse
Directly upon receiving my OP3 I flashed CM13, that was in August, so 3.2.4 I guess, and I flashed the firmware of 3.2.6 before flashing Takers and your CM14 and later 14.1 builds.
TWRP behaves funny, the progress of restoring Data is already at 138%, 6800MB of 4899MB, the calculation is not taking compression into account I guess?
LOOOL, I have booted into the official CM14.1 with the old data, no fc or anything, but my pattern does not work anymore. same pattern as before, won't be accepted.
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
daleski75 said:
Never seen that issue before what happens if you reboot into the bootloader and then connect the phone to your pc and type fastboot boot <name of recovery> does it boot up?
Of course replace the < > with the name of the img file.
Click to expand...
Click to collapse
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
jcgruenhage said:
Yes, TWRP works now, but the backed up unofficial CM 14.1 does not boot.
But, only this TWRP works, booting the official TWRP does not work.
I could probably just use the TWRP file manager to extract the few files from the data partition that I need, but this is a workaround and not a fix, and that is not desired in most cases. Fixing it is hard without someone that still has a broken system.
Click to expand...
Click to collapse
Yup thats the one I am using as well.
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
Do you know how one would debug something like that? I have nothing but the splash screen in the beginning and then a black screen
I will just flash CM 14.1 and manually extract my OTP tokens from the data backup, so I don't really need to debug that, but it would probably help determine the cause and properly fix it for the future.
Ask for the link
daleski75 said:
Yup thats the one I am using as well.
Click to expand...
Click to collapse
May I ask which one? the link is dead ...
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
ChrisDiM said:
I am having the same problem, i can't boot into recovery and cant find a way to flash it.
Can someone explain me how to?
Click to expand...
Click to collapse
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Same issue here. Whenever I try to boot into recovery it just goes straight back to the bootloader/fastboot.
**** me, what do I do?
I try "fastboot format userdata" but after i have the same problem with TWRP-3.0.2-1.28
jackalsin said:
Sorry to hear that. You have to use Qualcomm Drivers to reset your cellphone
Click to expand...
Click to collapse
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
ChrisDiM said:
I just found a guide to reset my phone using Qualcomm but my phone doesn't show up on device manager + since this morning my op3 doesn't start up anymore and doesn't react when i plug the charger in.
Click to expand...
Click to collapse
Hold power button for at least a minute. It's what I did and fixed it.
DevSquad said:
Hold power button for at least a minute. It's what I did and fixed it.
Click to expand...
Click to collapse
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
ChrisDiM said:
after doing this it showed the OP logo for a few seconds and shut off again :/
Its really a bad moment for me because i had to call a lot a people today and now i can't even start up my phone
Click to expand...
Click to collapse
Can you get into fastboot?
If so, you can sideload a working TWRP via there.
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Thanks for the reply.
Are you sure what happened to is exactly what happened to you? Because I tried the ToolKit and it is not working. I tried both the versions of the TWRP and Stock recovery.
If you know anything else about this issue that would help me. I'd love to hear it.
SillyPython said:
Same happened to me also. But somehow I fixed it by installing TWRP again by using OnrPlus 3 toolkit. Here is the toolkit forum.xda-developers.com/oneplus-3/development/tool-tool-one-driversunlocktwrpfactory-t3398993. Can't post links. Don't forget to put http:// front of it
Click to expand...
Click to collapse
Also. Does encryption affect this in anyway, because I did it. I don't want to factory reset my phone because this is my primary phone and I don't have another phone. And I don't want to risk it, at least for a few days.
malachiseelam said:
Hello there,
This is my first XDA thread! This is an issue I ran into.
I just installed CM 14.1 on my OP3. I downloaded the latest TWRP from the official website before flashing it.
Here is the problem. After setting up my ROM, like installing all the required apps, I'm not able to boot into recovery. I tried flashing TWRP again, I downloaded the oneplus recovery from your website and I flashed that one too.
I erased recovery partition and installed both of them again (erasing each time). What happens is, after booting into the bootloader, I select recovery to go to the recovery and it stays blank, unless I reset it by holding the buttons.
Please let me know what I can do.
Click to expand...
Click to collapse
Modified TWRP version should do it
Same, when I flashed cm 14.1 I also got blank TWRP.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Then, what did you do?
LS.xD said:
Modified TWRP version should do it
Click to expand...
Click to collapse
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
michielokt said:
Same, when I flashed cm 14.1 I also got blank TWRP.
Click to expand...
Click to collapse
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
malachiseelam said:
Thanks LS.xD. You are awesome. I completely messed up my old Moto X and I didn't have a smartphone until now. I hesitated a lot before installing all custom stuff until I gave in. And this problem made me worry a lot.
Thanks a lot.
Michielokt, you should try flash the recovery LS.xD gave the link to, it booted.
Click to expand...
Click to collapse
Thanks it worked!
Please try the modified TWRP, 3.0.2-22
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:
I will try to explain what happened as best as possible.
I wanted to install the AKT Profile on my un-rooted one plus 3 and so I decided to root it.'
I looked up on google and used the OP3 All In One ToolKit to unlock bootloader and flash TWRP.
Then I booted up phone to download SuperSu in order to flash it.
This is where the problem began. I went into TWRP recovery mode and it asked for a password and that stopped the nandroid backup too. but I googled and found out that doing a Wipe helps you bypass the password bug, so I did that. Now I went ahead and did a nandroid backup.
This is where I don't understand what's going on. How much ever I try to reboot the device, it ONLY loads me back into TWRP Recovery screen.
I even tried to restore the backup, it completes the restore but I dont see any reboot option right after it is done, So i have to long press power button to reload back into TWRP.
Now I'm confused as to what to do and would REALLY appreciate help, ASAP.
P.S - I'm a noob so I probably wont understand high level jargon
thank you guys in advance :crying:
SOLVED : I flashed TWRP 3.0.3 once again and somehow it got fixed
'' doing a wipe help you bypass the password''... Well yes probably, but depending on what type of wipe, you might have wiped your rom/system. So if that is the case, there is no rom to boot into, and your stuck in twrp recovery. Restoring an empty Nandroid wont do anything either. So my guess is you will have to download stock or custom rom and do a fresh install.
If needed, this method works very well.
I used it to day, with success.
Good luck !
Thank you. but will this work with latest TWRP 3.0.3 or will i have to use old one as mentioned in that post?
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
rshah0429 said:
I will try to explain what happened as best as possible.
I wanted to install the AKT Profile on my un-rooted one plus 3 and so I decided to root it.'
I looked up on google and used the OP3 All In One ToolKit to unlock bootloader and flash TWRP.
Then I booted up phone to download SuperSu in order to flash it.
This is where the problem began. I went into TWRP recovery mode and it asked for a password and that stopped the nandroid backup too. but I googled and found out that doing a Wipe helps you bypass the password bug, so I did that. Now I went ahead and did a nandroid backup.
This is where I don't understand what's going on. How much ever I try to reboot the device, it ONLY loads me back into TWRP Recovery screen.
I even tried to restore the backup, it completes the restore but I dont see any reboot option right after it is done, So i have to long press power button to reload back into TWRP.
Now I'm confused as to what to do and would REALLY appreciate help, ASAP.
P.S - I'm a noob so I probably wont understand high level jargon
thank you guys in advance :crying:
Click to expand...
Click to collapse
Had the same problem and panicked like hell. I just switched a few twrp recoveries (modded and official) and found one that worked and phone booted.
Seagorilla2 said:
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
Click to expand...
Click to collapse
thank you. i will try this
Seagorilla2 said:
Use latest twrp 3.0.4.0. Also for clean install with OOS 4.02 or OB11. Also keep both firmware and supersu/magisk superuser close by. You can find all dl-links on xda.
Click to expand...
Click to collapse
I can't find TWRP 3.0.4.0 Can you please link it?
rshah0429 said:
I can't find TWRP 3.0.4.0 Can you please link it?
Click to expand...
Click to collapse
See Here
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img
Its not official but working for me...
Try flashing the stock recovery. I got stuck in recovery loop after the OTA update got installed over twrp. Flashed the stock recovery and right away it booted me to the rom.
It's a problem of older twrp with nougat so you need to flash twrp new version
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"?