EDIT: IT FINALLY WORKED! I just flashed an older version of twrp. Pretty weird how that's working and the newer one isn't. Should I keep this post for people with the same problem?
I know about the problem with cm12s and with the cm recovery thing.
I tried everything. Searched and tried nearly all of the different recovery or root install tutorials. But it's still not working!
Every time I install a recovery (both twrp and cwm) it won't install even though it said it worked. When I do the "remove usb, vol down + power" trick after flashing it just won't boot. It just shows the logo and then it reboots. If I release everything it boots my phone up normally. Even clicking recovery reboot in the reboot menu doesn't work. Then it will bring me to the cyanogen recovery.
My debugging mode is on.
Cyanogen recovery update is OFF.
I'm now using cm12.1s but it didn't work on cm12s either.
ADB and Fastboot are working fine. I tested it and my phone reacts when I give it commands (like fastboot reboot or adb devices)
My bootloader is unlocked (confirmed with fastboot oem device-info)
I just got this phone yesterday. I didn't expect this much trouble with just rooting.
ps: this is one of those "it should work, but it doesn't" moments.
Yes. After cm12 the cyanogenmod is ignoring the cyanogen off recovery mark.
After flashing recovery twrp via fastboot, direct reboot to recovery manually via button. Try look at faq. See q22. http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Always keep a post like this, it's good for future reference (people having the same question will thank you for sure)!
Use Philz recovery. Many are facing same issues with TWRP
realbabilu said:
Yes. After cm12 the cyanogenmod is ignoring the cyanogen off recovery mark.
After flashing recovery twrp via fastboot, direct reboot to recovery manually via button. Try look at faq. See q22. http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Click to expand...
Click to collapse
Just like every other method I've tried, that method doesn't seem to work either.
Hi Benalimarwan,
Thanks for your post. I flashed openrecovery-twrp-2.8.5.0-bacon.img. but, it still didn't work. When I logged into recovery mode it still logged into cynogen recovery. Which version of twrp did you flash? Thanks!
lotherius said:
Just like every other method I've tried, that method doesn't seem to work either.
Click to expand...
Click to collapse
Works for me from latest stable CM12
1. Unlocking Bootloader via fastboot
fastboot oem unlock
fastboot reboot
2. USB Debugging -
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
3. Disable CM Recovery Protection -
On your phone go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.
4. Installing a Custom Recovery
fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img
got it from http://techerrata.com/browse/twrp2/bacon (one recommends don't use 2.8.7)
reboot to system
5. Flash your custom recovery again, but after flashing don't do a normal reboot. (DONT FORGOT TO Disable CM Recovery Protection first in normal boot before)
After the flash has succeeded disconnect the usb cable, then power down the phone by holding the power button down, once it's powered off use the power + volume down button combo to boot directly into recovery. This first forced reboot into recovery somehow subverts what was keeping it from staying flashed and all subsequent normal reboots into recovery will boot into the custom recovery of your choice.
gawd i nearly went out of my mind last night trying to flash TWRP , everything was working fine , fastboot checked out , unlocked the OEM also but it refused to flash TWRP , threw up errors "cannot open recovery' then i remembered the "hide file extensions for known file types" in win7 which was checked and ran
fastboot flash recovery rec[TAB]
Click to expand...
Click to collapse
.i.e hit tab button before hitting enter and it flashed it like a charm !! and i was already to throw this new cell out of my window
Please help me understand Step 5.
Once 'fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img' is completed, I shouldn't do a 'fastboot reboot'. Instead of that disconnect USB, and then Poweroff using power button. Now use Power + Volume down to boot into recovery. This should allow me to use twrp recovery. Is my understanding correct?
Regards,
Kiran
Hi Guys,
Just did step 5 again.
Did 'fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img' and disconnected USB, Powered off the device and powered it on using Volume down + Power button. It logged into twrp recovery. I then selected 'Install' and phone automatically got rebooted. Not sure why. I powered it off and powered on again using volume down + Power buttons. It then logged into CM recovery.
Repeated above step again. Again faced same issue. Any ideas?
I unlocked boot loader 4/5 days back. Since twrp recovery was not working, I continued using phone. Installed several apps. Do you think this might be an issue? Do I have to unlock boot loader again and then do 'fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img'??? Please suggest
Regards,
Kiran
Do it this way with fastboot:
fastboot flash recovery recovery.img (you know the drill...)
when this is completed type in fastboot reboot
BUT MOST IMPORTANT! hold the volume down button on your opo the whole time before you press enter to run the command and keep holding it until TWRP boots up.
This worked on 5 OPO's. (3 were mine, one was my brother's and one is a friend's)
im too on stock 12.1..So which twrp recovery version ll i flash????
1+1
Wug's Bacon Root Toolkit
I had this problem when I tried flashing the custom recovery (TWRP) manually. It didn't matter what I tried, I could never manage to make TWRP persist over CM Recovery after a reboot. After giving up and staying in stock for some time, I decided to try again after getting the OTA to CM 12.1S, but, as no surprise, the same thing still happened. So, as a last try, I downloaded Wug's Bacon Root Toolkit and voila... it finally worked, I had a TWRP that persisted over CM Recovery after a reboot. I don't know what the toolkit did different than me when I did it manually, but it managed to make it work! Hopefully it also works for you...
only used toolkit for Fastboot driver installation...Good step by step instructions...but flashed 2.8.7.0 twrp with adb commands as described by Heisenberb...finally installed recovery n rooted my opo...
1+1
---------- Post added at 11:48 AM ---------- Previous post was at 11:45 AM ----------
Never used cyanogenmod on my N4 N5...Flashing process ws easy on nexus devices
1+1
AcmE85, Your suggestion worked like a charm bro. Finally was able to fix the issue. Thanks much for your help!
Related
And I have no idea why. Before I downloaded the newest update I upgraded my TWRP to the latest version. After the update I tried first to install SuperSU via google store but didnt work so i downloaded the installable zip and tried through TWRP. All I get is : E: failed to verify whole-file signature; E: signature verification failed.
Tried the old SuperSu that always worked (2.02) but I get the same bug.
I think the problem is that instead of TWRP when i start my phone with start button + vol down it gets into CYANOGEN recovery. I just installed TWRP ver 2.8.5.1 but its not working =/ dont know what to do, help please
MrSeler said:
And I have no idea why. Before I downloaded the newest update I upgraded my TWRP to the latest version. After the update I tried first to install SuperSU via google store but didnt work so i downloaded the installable zip and tried through TWRP. All I get is : E: failed to verify whole-file signature; E: signature verification failed.
Tried the old SuperSu that always worked (2.02) but I get the same bug.
I think the problem is that instead of TWRP when i start my phone with start button + vol down it gets into CYANOGEN recovery. I just installed TWRP ver 2.8.5.1 but its not working =/ dont know what to do, help please
Click to expand...
Click to collapse
You need to resinstall TWRP, just after you have done so, reboot back to TWRP instead of rebooting the whole system. Once back in TWRP you can flash SuperSU again, then reboot and you should be fine. Also make sure you have the cyanogen recovery option unticked under developer settings.
gsmyth said:
You need to resinstall TWRP, just after you have done so, reboot back to TWRP instead of rebooting the whole system. Once back in TWRP you can flash SuperSU again, then reboot and you should be fine. Also make sure you have the cyanogen recovery option unticked under developer settings.
Click to expand...
Click to collapse
How do i reinstall TWRP? im pretty sure ive done it already but still when i turn on the phone I have the cyanogen recovery on, tried to do it with TWRP manager (at first i couldnt start it because but later it worked. However, when i click on "Reboot to Recovery" it does not work) I have recovery installed in TWRP manager (ver 2.8.6.0) maybe i can do sth with this ?
Edit: I was able to start TWRP manager, now I'm not again because it says "root is required for this app"
MrSeler said:
How do i reinstall TWRP? im pretty sure ive done it already but still when i turn on the phone I have the cyanogen recovery on, tried to do it with TWRP manager (at first i couldnt start it because but later it worked. However, when i click on "Reboot to Recovery" it does not work) I have recovery installed in TWRP manager (ver 2.8.6.0) maybe i can do sth with this ?
Edit: I was able to start TWRP manager, now I'm not again because it says "root is required for this app"
Click to expand...
Click to collapse
You'll have to install it via PC fastboot or using a Tool, see below.
Install custom recovery via fastboot:
http://forum.xda-developers.com/showthread.php?t=2788632
Toolkit:
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
Make sure the following option is turned off.
Settings>Developer options>Update Cyanogen recovery - Off
gsmyth said:
You'll have to install it via PC fastboot or using a Tool, see below.
Install custom recovery via fastboot:
http://forum.xda-developers.com/showthread.php?t=2788632
Toolkit:
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
Make sure the following option is turned off.
Settings>Developer options>Update Cyanogen recovery - Off
Click to expand...
Click to collapse
Tried via fastboot and seemingly it worked as you can see here http://i.imgur.com/vKTQUQ5.png
But when i turn on the phone i still get cyanogen recovery =/ will try the tool kit and let You know
MrSeler said:
Tried via fastboot and seemingly it worked as you can see here http://i.imgur.com/vKTQUQ5.png
But when i turn on the phone i still get cyanogen recovery =/ will try the tool kit and let You know
Click to expand...
Click to collapse
Once it flashes, are you rebooting back into recovery first (without switching off, fully rebooting, anything else)? You should boot into TWRP and then you can reboot fully, it should be fine. If you just reboot out of TWRP after flashing the it gets overwritten by the stock cyanogen recovery.
After completing the TWRP flash in ABD run the following command.
Code:
adb reboot recovery
gsmyth said:
Once it flashes, are you rebooting back into recovery first (without switching off, fully rebooting, anything else)? You should boot into TWRP and then you can reboot fully, it should be fine. If you just reboot out of TWRP after flashing the it gets overwritten by the stock cyanogen recovery.
After completing the TWRP flash in ABD run the following command.
Code:
adb reboot recovery
Click to expand...
Click to collapse
Im doing what Im told, so - After the phone has booted back up, turn it off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode.
Wish I wasnt so braindead on this field =/ and the cyanogen recovery welcomes me every time
okay so instead of fastboot reboot command i should write the one you gave me? gonna try
EDIT: ERROR, DEVICE NOT FOUND
yeah, i was doing it wrong but i did it right this time and it is still not working. Have my usb debugging on
Is it possible that after the update i dont have the bootloader anymore?
MrSeler said:
yeah, i was doing it wrong but i did it right this time and it is still not working. Have my usb debugging on
Is it possible that after the update i dont have the bootloader anymore?
Click to expand...
Click to collapse
Your boot loader shouldn't be touched.
gsmyth said:
Your boot loader shouldn't be touched.
Click to expand...
Click to collapse
Okay. I tried and tried but failed. I have no idea what to do anymore. Downloaded new drivers for pc and new fastboot, tried like 15times to flash twrp on my phone and seemingly it worked but when I rebooted, turned it off and on again with volume - it's always cyanogen recovery there, never twrp. I downloaded twrp manager but it won't work because it requires root and I can't root because manager won't work. Saw on oneplus forum that some people have exact same problem but there S been no solution so far and I have no idea what to do anymore. The only thing I haven't tried yet is to hold start+volume- keys after I flash twrp and reboot the phone using the code, so instead of having to turn it off and on again maybe I ll be able to get into the twrp instantly and it won't get overwritten by cyanogen recovery.
MrSeler said:
Okay. I tried and tried but failed. I have no idea what to do anymore. Downloaded new drivers for pc and new fastboot, tried like 15times to flash twrp on my phone and seemingly it worked but when I rebooted, turned it off and on again with volume - it's always cyanogen recovery there, never twrp. I downloaded twrp manager but it won't work because it requires root and I can't root because manager won't work. Saw on oneplus forum that some people have exact same problem but there S been no solution so far and I have no idea what to do anymore. The only thing I haven't tried yet is to hold start+volume- keys after I flash twrp and reboot the phone using the code, so instead of having to turn it off and on again maybe I ll be able to get into the twrp instantly and it won't get overwritten by cyanogen recovery.
Click to expand...
Click to collapse
OK so i am experiencing the EXACT same issues. When I go into Fastboot Mode all I get is a small cyanogen head forllowed by the words 'FASTBOOT MODE' I get no menu to navigate or anything. TWRP appears to install but I get Cyanogen recover every time. If I use the toolkit and go to fastboot mode it sees it as an unlocked fastboot device but will not allow me to root the device.
oasisdave said:
OK so i am experiencing the EXACT same issues. When I go into Fastboot Mode all I get is a small cyanogen head forllowed by the words 'FASTBOOT MODE' I get no menu to navigate or anything. TWRP appears to install but I get Cyanogen recover every time. If I use the toolkit and go to fastboot mode it sees it as an unlocked fastboot device but will not allow me to root the device.
Click to expand...
Click to collapse
After flashboot reboot do not let phone turn on again but use the start + volume- combination, it will take you to twrp. Found the solution finally but I still have some issues with graphics and Google account =/
MrSeler said:
After flashboot reboot do not let phone turn on again but use the start + volume- combination, it will take you to twrp. Found the solution finally but I still have some issues with graphics and Google account =/
Click to expand...
Click to collapse
Yeah, that's not working for me, still goes straight to Cyanogen Recovery.
See last question in FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Transmitted via Bacon
Hi all,
I just flashed stock rom (Cyanogen OS 12). It's the first time I installed Cyanogen OS 12 via fastboot. (might be cause of the problems..) . Now I tried to install TWRP as usually. This time... It doesn't work..
Yes, I have disabled the "Cm recovery" setting in developer options and yes my device is bootloader-unlocked.
I have installed the correct drivers and it tells me that the recovery has been installed successfully..
However, when I reboot in recovery, it leads me to Cyanogen recovery.. I don't know how this is possible.
Any ideas? I've tried a lot: plugging in cables in another order, factory reset (+ disable "update cm recovery"), and I tried many many times...
Now I'm thinking about flashing stock Kitkat, and then try to install TWRP successfully and afterwards update firmware via "TWRPable" OTAs....
Do you have any other suggestions?
Thanks in advance!
EDIT:
I've found a way to install it properly.
I flashed TWRP using "fastboot flash recovery recovery.zip"
Then I rebooted the device using "fastboot reboot"
Then I held the power button for about 9 seconds. And then I entered the recovery using the "hardware" way. (power button + volume down). Then it finally entered in TWRP recovery. On Kitkat, I wouldn't have to hold the power button for 9 seconds.
Read the FAQ thread at the top of this section...
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
I have a huge problem. After having a lot of issues rooting my device, I downgraded to COS11s and was finally able to root and install TWRP.
After that I tried to install Sultan's latest build, which failed. I then installed the latest CM12.1 Nightly (which is what he recommends if the installtion failes) and right after that his build, which worked - finally. I installed Gapps and rebooted.
I noticed I hadn't installed supersu and wanted to reboot to recovery to do so - but now it just won't boot into recovery! My phone turns on and boots straight to the lockscreen. I tried the button combination, the advanced reboot menu - everything. It just won't boot into recovery. I even reinstalled the recovery via fastboot (which supposedily was successful), but the problem remains.
Flashify doesn't even show an installed recovery!
HELP!
JanSpatschek said:
I have a huge problem. After having a lot of issues rooting my device, I downgraded to COS11s and was finally able to root and install TWRP.
After that I tried to install Sultan's latest build, which failed. I then installed the latest CM12.1 Nightly (which is what he recommends if the installtion failes) and right after that his build, which worked - finally. I installed Gapps and rebooted.
I noticed I hadn't installed supersu and wanted to reboot to recovery to do so - but now it just won't boot into recovery! My phone turns on and boots straight to the lockscreen. I tried the button combination, the advanced reboot menu - everything. It just won't boot into recovery. I even reinstalled the recovery via fastboot (which supposedily was successful), but the problem remains.
Flashify doesn't even show an installed recovery!
HELP!
Click to expand...
Click to collapse
Tried using adb yet? If you haven't, give it a try. If you don't have it set up, you can find several threads on how to do it, from full installs to small zip files. Considering you have fastboot working I assume abd also. Make sure USB debugging is on, plug your phone up and allow USB debugging when the prompt is displayed on your phone. Then adb reboot recovery.
Not familiar with what build you are on, some require you to enable root access mode from developer options, might check that also.
[deleted]
Ducter said:
Tried using adb yet? If you haven't, give it a try. If you don't have it set up, you can find several threads on how to do it, from full installs to small zip files. Considering you have fastboot working I assume abd also. Make sure USB debugging is on, plug your phone up and allow USB debugging when the prompt is displayed on your phone. Then adb reboot recovery.
Not familiar with what build you are on, some require you to enable root access mode from developer options, might check that also.
Click to expand...
Click to collapse
Thanks for you answer. I have adb set up. USB debugging is on. I will try adb reboot recovery. The weird thing is, it doesn't even boot into stock recovery (My first thought was that the phone replaced twrp with CM recovery somehow).
That's a good point, I will turn on root access and try again.
JanSpatschek said:
Thanks for you answer. I have adb set up. USB debugging is on. I will try adb reboot recovery. The weird thing is, it doesn't even boot into stock recovery (My first thought was that the phone replaced twrp with CM recovery somehow).
That's a good point, I will turn on root access and try again.
Click to expand...
Click to collapse
Another option, if nothing else seems to work is start over. I generally use nexus devices and flash factory images, looks like you can do that also on the one..
Hello,
I have the same problem. I unlocked my OPO, flashed the TWRP 2.8.7.0 and everything went good and smooth. Then I flashed CM12.1 and it worked. Now I wanted to downgrade TWRP to the TWRP 2.8.6.0 because of some issues with the latest version and after flashing the older version it will not boot to recovery at all...
Please help.
Thank you
EDIT: SOLVED!!
Okay, so I managed to get it back working again.
How I proceded:
1. http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and do everything that is said in the 3rd point of the first OP post. (+download the file for your OPO - either for 16GB or 64GB model - after you have it downloaded unpack it)
2. flash all the files listed in the 3rd point of the first OP post
3. boot in the OS, enable developer settings and enable USB debugging and allow it
4. get back in the fastboot mode and flash either TWRP 2.8.6.1 or later versions (because of Lollipop compatibility)
5. enjoy!
God bless you.
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
tirtha2shredder said:
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
Click to expand...
Click to collapse
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
enrique_fire said:
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
Click to expand...
Click to collapse
Thank you! that worked perfect!
Hi which method did you use to root yu50101a? if possible can you share a link as well
:crying:I am also facing the same problem . i also have yu5010a but cannot root it . twrp or cwm not correctly flashing.just tell me if anyone have any solution .
Hello, I bought a OnePlus one (came with CM11 - 4.4.4) and followed the standard steps to root it
1) unlock bootloader - successful, phone got factory reset, checked the status using fastboot
2) Flash custom recovery (TWRP) using fastboot - always "okay" message
3) The phone DOES NOT boot to recovery after this - it gets stuck at the 1+ logo, or remains stuck for a few seconds and goes to normal reboot. -I've tried using fastboot to reboot phone while holding down volume button
Please help! i've look this problem up and haven't found a solution.
I tried 2.7.0.0, and the latest 2.8.5.1, along with 2.8.6.0, along with trying to use the one plus tool kit. Using the toolkit, even flashing the stock recovery, then booting it didn't work.
after you flash recovery in fastboot, do not issue the fastboot reboot command. you need to manually power off the phone by keeping the power button pressed till it powers off
kenboyles72 said:
after you flash recovery in fastboot, do not issue the fastboot reboot command. you need to manually power off the phone by keeping the power button pressed till it powers off
Click to expand...
Click to collapse
I tried this, same result
ak14523 said:
I tried this, same result
Click to expand...
Click to collapse
As the other posted mentioned you have to fastboot flash twrp (2.8.6.0) then power off phone and use volume down + power button combo to get to recovery. Its flashing but if you boot to OS it will be overwritten by CM recovery hence booting directly will alleviate that
Boot into os, enable dev options by tapping the build number a bunch of times in settings-about phone section, go back and go into settings-developer options, make sure "update cyanogen recovery" is unchecked. Flash recovery again, and like people have said, power off the phone and use volume down and power buttons together to boot into recovery.
Thanks for the quick replies guys. I have tried all the above s and none of them have worked
Should I try unlocking the bootloader again?
I recommend going to this guide and following it closely: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
As for which version of TWRP to use, I recommend this version: https://www.androidfilehost.com/?fid=24391638059059048