I have long been a user of CM11 on my OPO, but today I wanted to install a custom ROM. As the guide says here I was required to update to CM12.1 beforehand. The updates seem to have overwritten TWRP with Cyanogen Recovery, but whenever I try to flash TWRP back onto my device it always boots back to CM recovery when I boot recovery.
I have followed this guide to attempt to re-flash custom recovery and re-root my device but I seem to have hit a brick wall.
I used the following commands:
*fastboot flash recovery recovery.img
*fastboot reboot
Click to expand...
Click to collapse
I have disabled CM recovery protection in developer options with no luck. I have also tried older versions of TWRP to no avail.
Can anyone advise me how to get around this problem? Any help is appreciated.
I had this problem when I first tried rooting the phone. Some said that you had to reboot directly to recovery after you had flashed TWRP and then it should presist, but that didn't work for me. The solution that worked (at least for me) was flashing it with a toolkit.
LittleConfucy said:
I had this problem when I first tried rooting the phone. Some said that you had to reboot directly to recovery after you had flashed TWRP and then it should presist, but that didn't work for me. The solution that worked (at least for me) was flashing it with a toolkit.
Click to expand...
Click to collapse
Thanks for your reply. Sorry, I'm a bit out of the loop these days. Could you elaborate on what toolkits I could use?
jayalex said:
Thanks for your reply. Sorry, I'm a bit out of the loop these days. Could you elaborate on what toolkits I could use?
Click to expand...
Click to collapse
http://www.wugfresh.com/brt/
LittleConfucy said:
I had this problem when I first tried rooting the phone. Some said that you had to reboot directly to recovery after you had flashed TWRP and then it should presist, but that didn't work for me. The solution that worked (at least for me) was flashing it with a toolkit.
Click to expand...
Click to collapse
this is true, i had to do that... when done flashing TWRP reboot to recovery, no OS
jayalex said:
I have long been a user of CM11 on my OPO, but today I wanted to install a custom ROM. As the guide says here I was required to update to CM12.1 beforehand. The updates seem to have overwritten TWRP with Cyanogen Recovery, but whenever I try to flash TWRP back onto my device it always boots back to CM recovery when I boot recovery.
I have followed this guide to attempt to re-flash custom recovery and re-root my device but I seem to have hit a brick wall.
I used the following commands:
I have disabled CM recovery protection in developer options with no luck. I have also tried older versions of TWRP to no avail.
Can anyone advise me how to get around this problem? Any help is appreciated.
Click to expand...
Click to collapse
A quick search would have uncovered a dozen or so threads detailing how to overcome this problem in the very q&a section that you've posted in. Then there's the FAQ thread that's stuck at the top:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Then there's my guide stuck in the general section:
http://forum.xda-developers.com/showthread.php?t=2839471
I have the same problem, unfortunately most of the suggested fixes in the Q/A sections and all the threads do not help me.
Here is a detailed explanation of what is going on:
http://forum.xda-developers.com/oneplus-one/help/installing-custom-recovery-cm12-1-5-1-1-t3232611
If I power down the phone, after flashing recovery, and boot it with power+volume it stays on the OPO logo, screen goes black and reboots again - and if I do not hold the volume button it boots into the normal OS. If i keep holding the volume button the OPO logo keeps appearing and it keeps going to black and reboots again and again.
Michiel0211 said:
I have the same problem, unfortunately most of the suggested fixes in the Q/A sections and all the threads do not help me.
Here is a detailed explanation of what is going on:
http://forum.xda-developers.com/oneplus-one/help/installing-custom-recovery-cm12-1-5-1-1-t3232611
If I power down the phone, after flashing recovery, and boot it with power+volume it stays on the OPO logo, screen goes black and reboots again - and if I do not hold the volume button it boots into the normal OS. If i keep holding the volume button the OPO logo keeps appearing and it keeps going to black and reboots again and again.
Click to expand...
Click to collapse
Have you tried flashing a different version of TWRP or another recovery?
Heisenberg said:
Have you tried flashing a different version of TWRP or another recovery?
Click to expand...
Click to collapse
Thank you for all your responses. I made a thread over on /r/cyanogenmod too and found a solution.
I run the following commands instead:
fastboot flash recovery twrp-2.7.6.0-bacon.img
fastboot boot twrp-2.7.6.0-bacon.img
Click to expand...
Click to collapse
This booted into TWRP. Reboot prompted me to install SuperSU. Recovery now boots to TWRP. I'd link the thread but can't as a new user. Hopefully this method works for others too.
Heisenberg said:
Have you tried flashing a different version of TWRP or another recovery?
Click to expand...
Click to collapse
jayalex said:
Thank you for all your responses. I made a thread over on /r/cyanogenmod too and found a solution.
I run the following commands instead:
This booted into TWRP. Reboot prompted me to install SuperSU. Recovery now boots to TWRP. I'd link the thread but can't as a new user. Hopefully this method works for others too.
Click to expand...
Click to collapse
I have tried multiple versions of TWRP and different recoveries - all to no avail. I have no idea what I am doing wrong and I'm certainly not green at this!
Michiel0211 said:
I have tried multiple versions of TWRP and different recoveries - all to no avail. I have no idea what I am doing wrong and I'm certainly not green at this!
Click to expand...
Click to collapse
Did you try using the fastboot boot command instead like I did above?
I'll give it a shot next time I get. Hope it works.
Michiel0211 said:
I'll give it a shot next time I get. Hope it works.
Click to expand...
Click to collapse
Cool, let us know how it goes :good:
Michiel0211 said:
I have tried multiple versions of TWRP and different recoveries - all to no avail. I have no idea what I am doing wrong and I'm certainly not green at this!
Click to expand...
Click to collapse
Try doing what the poster directly above you did.
I finally managed to get it working by downloading the latest version of TWRP (2.8.3.0) and (if it helped) using the command 'format cache'.
It doesnt stick, but atleast it works.
Related
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1
CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.
agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..
HTC One M7 GSM Recovery Update Problems]
So I flashed TWRP 2.6.3.0 through adb fastboot on my HTC One M7 International version and it worked but when trying to install a custom ROM it had the status 7 error. So I thought updating TWRP to the latest version 2.8.5.0 would help but here is where the problem is, I update and flash it using adb fastboot and when I try to enter recovery mode it shows "entering recovery" in pink letters at the top then the screen goes black for a few seconds then back to the same "entering recovery" screen again, I've tried clearing the cache before and after flashing and also tried not clearing it at all with the same result. I've also tried flashing different versions of it and still the same, the funny thing is I can flash TWRP 2.6.3.0 again and it works fine just when I try to update it that's when the problems begin, the exact same thing happens with CWM 6.0.3.1 it works fine but when I try to update I get the same results, this also happens when trying to update through flashify and Rom manager. if someone could help me out with this it would be much appreciated :good:
JacobHaze24 said:
HTC One M7 GSM Recovery Update Problems]
So I flashed TWRP 2.6.3.0 through adb fastboot on my HTC One M7 International version and it worked but when trying to install a custom ROM it had the status 7 error. So I thought updating TWRP to the latest version 2.8.5.0 would help but here is where the problem is, I update and flash it using adb fastboot and when I try to enter recovery mode it shows "entering recovery" in pink letters at the top then the screen goes black for a few seconds then back to the same "entering recovery" screen again, I've tried clearing the cache before and after flashing and also tried not clearing it at all with the same result. I've also tried flashing different versions of it and still the same, the funny thing is I can flash TWRP 2.6.3.0 again and it works fine just when I try to update it that's when the problems begin, the exact same thing happens with CWM 6.0.3.1 it works fine but when I try to update I get the same results, this also happens when trying to update through flashify and Rom manager. if someone could help me out with this it would be much appreciated :good:
Click to expand...
Click to collapse
I assume you have unlocked your bootloader from HTCDev.
Sometimes, flashing recovery after rebooting from from adb fastboot may fail to write recovery. My advice would be to boot manually into bootloader with power and volume down buttons, enter fastboot usb from there and then flash recovery.img.
Lemme know if that worked.
Best of luck.
enigmaamit said:
I assume you have unlocked your bootloader from HTCDev.
Sometimes, flashing recovery after rebooting from from adb fastboot may fail to write recovery. My advice would be to boot manually into bootloader with power and volume down buttons, enter fastboot usb from there and then flash recovery.img.
Lemme know if that worked.
Best of luck.
Click to expand...
Click to collapse
yes I have already unlocked the bootloader through the htcdev site and adb never fails to write the recoveries its just only the TWRP and CWM recoveries i mentioned seem to work on my device i cant update to a newer one because it gets stuck on the "entering recovery" screen when i try to boot into recovery, im not quite sure why its happening
Okay I just tried what you said and the result is the same, I cant be the only one with this problem
JacobHaze24 said:
I cant be the only one with this problem
Click to expand...
Click to collapse
Hi Jacob. Sorry that you seem to be stuck at that step.
However, what you said above could be true and I would recommend asking this question in your device specific thread to get more accurate answers regarding your particular device. http://forum.xda-developers.com/htc-one/help
Best of luck!
enigmaamit said:
Hi Jacob. Sorry that you seem to be stuck at that step.
However, what you said above could be true and I would recommend asking this question in your device specific thread to get more accurate answers regarding your particular device. http://forum.xda-developers.com/htc-one/help
Best of luck!
Click to expand...
Click to collapse
Thank you for your help, I finally figured it out and am now running ViperOne 7.0.2 :good:
JacobHaze24 said:
Thank you for your help, I finally figured it out and am now running ViperOne 7.0.2 :good:
Click to expand...
Click to collapse
Glad you made it, and learnt some valuable skills along the way.
Thread closed.
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
benzso63 said:
I already make sure the phone "update Cyanogen Recovery" is unchecked.
Click to expand...
Click to collapse
Well, you should have checked that BEFORE the update, not after.
benzso63 said:
IS there a way I can use TWRP instead?
Click to expand...
Click to collapse
Yes, there are many ways. Check custom recovery installation.
benzso63 said:
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
Click to expand...
Click to collapse
Use fastboot or a toolkit to reinstall TWRP, after it installs reboot back into TWRP, dont reboot the whole system and TWRP will stick. Otherwise TWRP will be overwritten with the stock recovery.
benzso63 said:
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
Click to expand...
Click to collapse
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
Bro, I followed this instructions. Did everything I could but still boot up with stock recovery. It is stuck. I don't know what to do .
As you can see the screen shot when I tried push the superSu to it, it saids error: device not found.
All previous steps I followed without error.
But end up still showing stock recovery.
Heisenberg said:
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I did but it saids device not found.
gsmyth said:
Use fastboot or a toolkit to reinstall TWRP, after it installs reboot back into TWRP, dont reboot the whole system and TWRP will stick. Otherwise TWRP will be overwritten with the stock recovery.
Click to expand...
Click to collapse
benzso63 said:
Bro, I followed this instructions. Did everything I could but still boot up with stock recovery. It is stuck. I don't know what to do .
As you can see the screen shot when I tried push the superSu to it, it saids error: device not found.
All previous steps I followed without error.
But end up still showing stock recovery.
Click to expand...
Click to collapse
You haven't followed the instructions there, from what I can see you've issued the "fastboot reboot" command after flashing the recovery, which you're not meant to do, you're meant to force a reboot directly into recovery with the power + volume down combo.
Hi Heisenberg, I got the problem solved by using the toolkit. Now I got my TWRP back and rooted. Thanks for the info.
Heisenberg said:
You haven't followed the instructions there, from what I can see you've issued the "fastboot reboot" command after flashing the recovery, which you're not meant to do, you're meant to force a reboot directly into recovery with the power + volume down combo.
Click to expand...
Click to collapse
I have a nexus 5.
16GB model.
5.1.1
Rooted.
TWRP 2.8.6.1
I was about to flash CM 12.1 .
I pressed wipe but it froze, I left it that way for about an hour and decided to research about what is happening. A lot of comments on some thread I read said that turning it off and then on worked for them and I did the same. Now all I get is a flashing Teamwin logo. The only accessible feature of the phone is the Power off/Start/Bootloader/Restart Bootloader thing-y. Whichever of them I press I get the flashing Teamwin logo.
Just wait it takes awhile
@bigglongruler
bigglongruler said:
I have a nexus 5.
16GB model.
5.1.1
Rooted.
TWRP 2.8.6.1
I was about to flash CM 12.1 .
I pressed wipe but it froze, I left it that way for about an hour and decided to research about what is happening. A lot of comments on some thread I read said that turning it off and then on worked for them and I did the same. Now all I get is a flashing Teamwin logo. The only accessible feature of the phone is the Power off/Start/Bootloader/Restart Bootloader thing-y. Whichever of them I press I get the flashing Teamwin logo.
Click to expand...
Click to collapse
Well you still have access to the bootloader luckily. Best part about a Nexus is that they're difficult to actually brick. Boot your phone into the bootloader and either fastboot flash recovery to reinstall twrp or use fastboot to reflash the stock system images.
davehasninjas said:
Well you still have access to the bootloader luckily. Best part about a Nexus is that they're difficult to actually brick. Boot your phone into the bootloader and either fastboot flash recovery to reinstall twrp or use fastboot to reflash the stock system images.
Click to expand...
Click to collapse
Thanks man, that's exactly what I needed. I tried to re-flash TWRP but had the same problem but when I flashed the stock system images everything went back to normal.
bigglongruler said:
Thanks man, that's exactly what I needed. I tried to re-flash TWRP but had the same problem but when I flashed the stock system images everything went back to normal.
Click to expand...
Click to collapse
Glad I could help, and that your phone is up and running again.
Take care.
Hey friends, just bought the One last week and want to root it already. Unlocked Bootloader following THIS guide. Tried to install TWRP from the same guide. Now the device wont enter recovery by holding Vol Down + Power. Entering recovery via Reboot options takes me to default Cyanogen Recovery.
Tried following THIS guide also, but again not going anywhere. Can't understand what the problem is. Can anyone please help?
Also if resetting the device (locking bootloader again, and trying all over) helps, Can someone please guide me?
omega_warrior said:
Hey friends, just bought the One last week and want to root it already. Unlocked Bootloader following THIS guide. Tried to install TWRP from the same guide. Now the device wont enter recovery by holding Vol Down + Power. Entering recovery via Reboot options takes me to default Cyanogen Recovery.
Tried following THIS guide also, but again not going anywhere. Can't understand what the problem is. Can anyone please help?
Also if resetting the device (locking bootloader again, and trying all over) helps, Can someone please guide me?
Click to expand...
Click to collapse
Those guides aren't up to date, it's changed slightly since Lollipop. My guide here is up to date. Basically you need to flash TWRP again, but instead of rebooting normally afterwards you need to force a reboot directly into recovery. Full instructions are in the guide.
Heisenberg said:
Those guides aren't up to date, it's changed slightly since Lollipop. My guide here is up to date. Basically you need to flash TWRP again, but instead of rebooting normally afterwards you need to force a reboot directly into recovery. Full instructions are in the guide.
Click to expand...
Click to collapse
Thanx a lot, i'll try and keep you posted.
@Heisenberg Thanx a ton sir. Your guide worked like a charm.