Develop Bugs

[Q] CWM not replacing Android Recovery after newest OTA update / Lost Root

I recently purchased this SGS3, installed CWM and rooted it. Everything was going great - but then i was offered the most recent OTA update, so i reflashed the stock recovery via Odin, did the update which is:
4.0.4
T999EVLH2
same kernel
bld #: IMM76D.T999EVALH2
now, its saying the phone is no longer rooted (yet superSU is still there) but checkroot is saying that it isnt rooted, and no matter what i do, flashing CWM via Odin passes, but will not stick (as in, i boot into recovery mode and that damned stock recovery is STILL THERE, wtf?)
can anyone offer any assistance or insight into my issue.
Thanks
~Wikkid

Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.

Aerowinder said:
Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.
Click to expand...
Click to collapse
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.

mikewikkid said:
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.
Click to expand...
Click to collapse
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.

Aerowinder said:
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.
Click to expand...
Click to collapse
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.

mikewikkid said:
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.
Click to expand...
Click to collapse
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/jv6pHg8b

Aerowinder said:
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/sUJixYID
Click to expand...
Click to collapse
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!

mikewikkid said:
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!
Click to expand...
Click to collapse
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.

Aerowinder said:
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.
Click to expand...
Click to collapse
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."

mikewikkid said:
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."
Click to expand...
Click to collapse
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.

You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.

xanderman said:
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.
Click to expand...
Click to collapse
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
Aerowinder said:
You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.
Click to expand...
Click to collapse
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/

Thistleknot said:
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
Click to expand...
Click to collapse
Umm, 2 things....
You realize this thread is over a year old and the last post was over 9 months ago?
And those links look like they are for the S4....
Sent from my SGH-T999V using Tapatalk 4

[Q] Can't boot after failed root attempt

SOLVED
So today I decided I would try to install a custom OS/ROM whatever it's called on my HTC One X. I unlocked the bootloader successfully without any problems. Then I went on to root the phone, and this is where it all went wrong. I found a tutorial and followed it to the tiniest detail. I am unable to link to it because I am a new user. When my phone rebooted it went to the "HTC Quietly Brilliant" boot screen. I left it there for 30 minutes and it still didn't move on. What do I do now? I am a super noob at this, and I admit that I am an idiot for not reading more up on it first, it just all seems so super complicated.
Thanks in advance for any help and guidance.

well, pm me the link so i can check the instructions you followed and maybe help you

lukes91 said:
well, pm me the link so i can check the instructions you followed and maybe help you
Click to expand...
Click to collapse
I sent you the link. Thanks for your help.

http://rootmyandroid.org/root-htc-one-x-windows-linux-mac-osx.html
Here is the link, so everybody can help you.
Sent from Somewhere Over The Rainbow...
---------- Post added at 08:17 PM ---------- Previous post was at 07:28 PM ----------
so it hanged just after you run the script to root device, right? after you ran the script in the shell, did it return any error?

lukes91 said:
http://rootmyandroid.org/root-htc-one-x-windows-linux-mac-osx.html
Here is the link, so everybody can help you.
Sent from Somewhere Over The Rainbow...
---------- Post added at 08:17 PM ---------- Previous post was at 07:28 PM ----------
so it hanged just after you run the script to root device, right? after you ran the script in the shell, did it return any error?
Click to expand...
Click to collapse
No, no error, it said "Daemon launched successfully" or something along those lines, my phone turned off and turned back on to the HTC boot screen.

Ok, try this: if the phone is still on keep the power button pressed till it restarts and press also vol down button until you arenin the bootloader; if the device is off, enter bootloader keeping power and vol down button pressed... Now my suggestion is to flash a custom recovery and a custom rom, you will get root privileges and the phone will work again...
Sent from Somewhere Over The Rainbow...

If you are unlocked (you see it in bootloader) you can flash a custom recovery and a custom rom. Look up for your favorite Recovery and flash it.
Download the img File to directory where you have the fastboot files and run this code in command prompt
Code:
fastboot flash recovery name_of_recovery.img
After it you can boot into Bootloader and turn to recovery to get access to phone and SD Card/flash Rom

Did you flash boot.img and erased the cache?
Sent from my HTC One X using Tapatalk 2

Okay, so I successfully flashed TWRP and launched into recovery mode with it. How I get the custom ROM files on my SD card, when I plug my phone into my computer with USB it doesn't show up in the drives section, so I can't open up the SD card.
Another thing is that with the latest version of TWRP for my phone touch doesn't work in the recovery mode. There's a version that does, but it says it doesn't have USB mount or something like that. What's the next step?

You need to mount sd card via recovery, and having the touchscreen working is better as it will be easier to move inside aroma installer... Use philz recovery (if you want a sense rom use 5.15.9, if you want kitkat use the last version), enter the recovery, plug the phone into pc, mount sdcard via recovery, copy the zip over it and follow the instructions to install rom... You can find the instructions in every rom thread op... Ask if you need more help
Sent from Somewhere Over The Rainbow...

Thanks for all the help, I am really starting to get a better understanding of how this actually works. I flashed Philz recovery and went into recovery with it. Then I went to mount and mounted USB Storage. Is this the right thing? It still doesn't show up on my PC

ChaosDuck said:
Thanks for all the help, I am really starting to get a better understanding of how this actually works. I flashed Philz recovery and went into recovery with it. Then I went to mount and mounted USB Storage. Is this the right thing? It still doesn't show up on my PC
Click to expand...
Click to collapse
which version did you flash? sometimes it keeps a couple of minutes before popping up the sdcard in pc, but i ensure you that 5.15.9 usb mout feature works fine... some users (me too) faced some issues with some 6.x.y version (sorry, i don't remember which one as i still use sense rom and so philz 5.15.9)

lukes91 said:
which version did you flash? sometimes it keeps a couple of minutes before popping up the sdcard in pc, but i ensure you that 5.15.9 usb mout feature works fine... some users (me too) faced some issues with some 6.x.y version (sorry, i don't remember which one as i still use sense rom and so philz 5.15.9)
Click to expand...
Click to collapse
I flashed latest version 6.19.3. There are only 3 versions available as far as I can see. They are:
6.19.3
6.12.8
6.07.9
I'll try flashing the two other versions and see what happens.

ChaosDuck said:
I flashed latest version 6.19.3. There are only 3 versions available as far as I can see. They are:
6.19.3
6.12.8
6.07.9
I'll try flashing the two other versions and see what happens.
Click to expand...
Click to collapse
you can find 5.15.9 here

lukes91 said:
you can find 5.15.9 here
Click to expand...
Click to collapse
Thank you! It finally showed up on my PC after a minute. I wanted to try Android 4.4.2 KitKat custom ROM "Carbon" so I want to ask a bit of an off-topic question. What are the GApps thing that I am told to install with the ROM? Why are they so important, what do they do?

ChaosDuck said:
Thank you! It finally showed up on my PC after a minute. I wanted to try Android 4.4.2 KitKat custom ROM "Carbon" so I want to ask a bit of an off-topic question. What are the GApps thing that I am told to install with the ROM? Why are they so important, what do they do?
Click to expand...
Click to collapse
those are google apps (i bet you understood what they are for just reading the full name ) i'm sorry to tell you that philz 5.15.9 can't flash 4.4.2 android, so you should update it... but now you have the zip on sdcard at least... give a look at latest TWRP you can find here in the OP #2 (everyhing should work with this version, but i still didn't test it, so i can't ensure it... i told you to use Philz 5.15.9 because i was 100% sure USB mount works with that recovery, and we needed to put a rom zip on sdcard ) now that you understood how things work, you can choose the recovery you want according to your reqirements have a nice flash man, and feel free to ask me if you need any further help

lukes91 said:
those are google apps (i bet you understood what they are for just reading the full name ) i'm sorry to tell you that philz 5.15.9 can't flash 4.4.2 android, so you should update it... but now you have the zip on sdcard at least... give a look at latest TWRP you can find here in the OP #2 (everyhing should work with this version, but i still didn't test it, so i can't ensure it... i told you to use Philz 5.15.9 because i was 100% sure USB mount works with that recovery, and we needed to put a rom zip on sdcard ) now that you understood how things work, you can choose the recovery you want according to your reqirements have a nice flash man, and feel free to ask me if you need any further help
Click to expand...
Click to collapse
I flashed to the newest Philz recovery again and successfully installed both ROM and GApps. Rebooting phone now, I hope it works... Been on HTC screen for a while though.

ChaosDuck said:
I flashed to the newest Philz recovery again and successfully installed both ROM and GApps. Rebooting phone now, I hope it works... Been on HTC screen for a while though.
Click to expand...
Click to collapse
have you flashed boot.img via fastboot and erased cache via fastboot? the commands are
fastboot flash boot boot.img
fastboot erase cache
remember that first boot can take a while (in some cases up to ten minutes)

lukes91 said:
have you flashed boot.img via fastboot and erased cache via fastboot? the commands are
fastboot flash boot boot.img
fastboot erase cache
remember that first boot can take a while (in some cases up to ten minutes)
Click to expand...
Click to collapse
Ahhh yes, it seems that was the only thing I still needed to do. It's on the Carbon launch screen now. Thanks a bunch man, I literally love you! :laugh:

ChaosDuck said:
Ahhh yes, it seems that was the only thing I still needed to do. It's on the Carbon launch screen now. Thanks a bunch man, I literally love you! :laugh:
Click to expand...
Click to collapse
lol, you're welcome, happy i've helped you

how do I root 3.28.1540.6

I just updated to 4.4.4 3.28.1540.6 firmware on my Developer Edition HTC One and now whenever I try to run the recovery from fastboot, my phone freezes! what am I doing wrong? this is what I do:
boot into fastboot and then type "fastboot boot TWRP.img" I also tried with Philz.img but no luck.

samanbabah said:
I just updated to 4.4.4 3.28.1540.6 firmware on my Developer Edition HTC One and now whenever I try to run the recovery from fastboot, my phone freezes! what am I doing wrong? this is what I do:
boot into fastboot and then type "fastboot boot TWRP.img" I also tried with Philz.img but no luck.
Click to expand...
Click to collapse
Recoveries are having problems booting from fastboot right now. You will actually have to flash a recovery, then install a superuser zip. Unfortunately, this means overwriting the new stock recovery, but it's the only way to re-root right now.
Either that, or wait until the devs for one of the recoveries figures out why booting from fastboot is failing.

samanbabah said:
I just updated to 4.4.4 3.28.1540.6 firmware on my Developer Edition HTC One and now whenever I try to run the recovery from fastboot, my phone freezes! what am I doing wrong? this is what I do:
boot into fastboot and then type "fastboot boot TWRP.img" I also tried with Philz.img but no luck.
Click to expand...
Click to collapse
Try "adb reboot fastboot", and understand what you're doing before you mod your phone. I've seen you with issues lately that you wouldn't have if you read all of the instructions for what you are trying to do and followed then exactly. You are going to end up with a brick of you don't.

jshamlet said:
Recoveries are having problems booting from fastboot right now. You will actually have to flash a recovery, then install a superuser zip. Unfortunately, this means overwriting the new stock recovery, but it's the only way to re-root right now.
Either that, or wait until the devs for one of the recoveries figures out why booting from fastboot is failing.
Click to expand...
Click to collapse
yeah I just don't want to write over the stock recovery so I can get OTA updates in the future. I guess I'll wait for devs to update their recoveries.

samanbabah said:
yeah I just don't want to write over the stock recovery so I can get OTA updates in the future. I guess I'll wait for devs to update their recoveries.
Click to expand...
Click to collapse
Yeah, I failed to realize there was a way to get around that, and blew my stock recovery away.
That said, I think that you could use Sunshine, assuming it's temp-root feature still works, and abort before running the compatibility test. Then, use a local terminal to backup the stock recovery. There is a dd command to pull the recovery block to a file around here somewhere. Unfortunately, I didn't think of that in time to back mine up.
I have posted a request for the new Developer Edition recovery in another thread, though, so hopefully someone can extract it and post it.

jshamlet said:
Recoveries are having problems booting from fastboot right now. You will actually have to flash a recovery, then install a superuser zip. Unfortunately, this means overwriting the new stock recovery, but it's the only way to re-root right now.
Either that, or wait until the devs for one of the recoveries figures out why booting from fastboot is failing.
Click to expand...
Click to collapse
This has to be Dev Ed specific, because I have no problems, and I really haven't heard of many others having problems either.
Plus, "recoveries are having problems booting from fastboot *right now*"? It isn't like an online service where the website is down.
Flash a backup and fix your sh*t.

xunholyx said:
This has to be Dev Ed specific, because I have no problems, and I really haven't heard of many others having problems either.
Plus, "recoveries are having problems booting from fastboot *right now*"? It isn't like an online service where the website is down.
Flash a backup and fix your sh*t.
Click to expand...
Click to collapse
Dude, seriously, there are many brands of decaf on the market that are just as tasty as the real thing.
The issue with recoveries not booting correctly is a noted issue, and started with WWE users. I got a hard lock on TWRP 2.8.0.3, and Philz seemed to running, but with no video. It is interesting that not everyone is having that issue, though. Right now, the only "workaround" is to actually flash. When I say "not working right now", I mean that the developers haven't found/fixed the issue yet, but you knew that, so I'll move on.
Also, it's not like I don't know how to get a stock recovery. It's just I'd rather not have to go through the hassle if I don't have to, especially since it's not exactly time-critical. There probably won't be another OTA for a while, and I have no doubt someone will post a copy of the updated recovery before then.

jshamlet said:
Dude, seriously, there are many brands of decaf on the market that are just as tasty as the real thing.
The issue with recoveries not booting correctly is a noted issue, and started with WWE users. I got a hard lock on TWRP 2.8.0.3, and Philz seemed to running, but with no video. It is interesting that not everyone is having that issue, though. Right now, the only "workaround" is to actually flash. When I say "not working right now", I mean that the developers haven't found/fixed the issue yet, but you knew that, so I'll move on.
Also, it's not like I don't know how to get a stock recovery. It's just I'd rather not have to go through the hassle if I don't have to, especially since it's not exactly time-critical. There probably won't be another OTA for a while, and I have no doubt someone will post a copy of the updated recovery before then.
Click to expand...
Click to collapse
I actually have heard of problems with CWM and Philz (CWM based)on the ViperOne thread. They state in OP and several times in the thread when screw ups happen to only use TWRP. I always thought it was ROM specific, and because of all the USE TWRP! posts, I haven't heard of recovery problems like this.
Maybe a switch to TWRP will fix his problem?

I'm not really seeing the issue here....you just can't boot the custom recovery from a command prompt(temporarily most likely). You can still flash twrp, do what you need to do(i.e. root,etc), then flash the stock recovery back in less than 5 minutes. You could probably just extract the recovery from the OTA or the rom you flashed. It literally took you more time to post your replies here than it would have taken you to do that....just saying.

Here's the stock recovery image that was posted in another thread: http://goo.gl/KsKQvk
I went through the same thing yesterday being unable to temporary boot to trwp. Sunshine didn't work giving me temp root and Weaksauce and Towelroot didn't do it either.
Custom recovery and Supersu flash worked as always.
HTC One M8

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

After flashing CM14.1 Nightly, I can't boot into recovery.

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.