When my phone was running, it turned to black screen somehow. I was like "hmm, what is going on?" So i thought its time to install new cm, new rom.
I installed new CM13 by using TWRPv2.8.6.0, and it said "Successful". But when I reboot, it automatically goes to TWRP screen and cannot boot OS.
I did try to install different cm, rom, but its not working at all. Still keep going to TWRP screen.
Please help me out!
Try reflash twrp and clean flash of rom
Be sure boatlaoder is unlock
memooo_shakal said:
Be sure boatlaoder is unlock
Click to expand...
Click to collapse
It's not a problem of bootloader
As for OP: side load another zip from PC
I don't know if twrp is working. Because accourding to the CM download page, they have their own recovery.
Try their CMRecovery.
Download: cm-13.0-20160402-NIGHTLY-bacon-recovery.img
sha1: ec635a224e90049b085e7adbe0d0ed0b2fe6266f
Click to expand...
Click to collapse
You can always flash twrp back.
verde90 said:
When my phone was running, it turned to black screen somehow. I was like "hmm, what is going on?" So i thought its time to install new cm, new rom.
I installed new CM13 by using TWRPv2.8.6.0, and it said "Successful". But when I reboot, it automatically goes to TWRP screen and cannot boot OS.
I did try to install different cm, rom, but its not working at all. Still keep going to TWRP screen.
Please help me out!
Click to expand...
Click to collapse
Make sure that your volume button is not broken
Can you boot to fastboot? With buttons combination?
Related
Hey,
Im on nexus i9023 with NSCollab rom and netarchy
Today i decided i wanted to try Cyanogen mod and downloaded it throug rommanager, al good up until that point!
Download was complete and i selected to contineu with the rom, it asked me if i wanted to backup my current rom and wipe cache/dalvik wich i said yes to!
Then it shutdown and stayed on the Google logo with the unlocked lock , i left it hanging to see what would happen but it just remained like it was stuck, so i decided to pull the battery and fired up again, all seems back to normal still running NSCollab!
But i cant get into Clockwork recovery anymore, it always shows the Google logo as said before, as we all need CWR, can you guys tell me what to do or what is going on?
Thnx!
If you can't get into CWR through the bootloader, just flash it again using fastboot like you did the first time.
deejaylobo said:
If you can't get into CWR through the bootloader, just flash it again using fastboot like you did the first time.
Click to expand...
Click to collapse
or just flash the recovery in rom manager again
bringonblink said:
or just flash the recovery in rom manager again
Click to expand...
Click to collapse
did this, didnt help, still stuck on logo!
ROM Manager has never worked right for me when I try updating CWR.
Can you explain exactly what happens when you try to get into recovery from the bootloader? Your phone reboots and is stuck on the Google logo? Or do you get a message along the lines of "no recovery img"? or what?
deejaylobo said:
ROM Manager has never worked right for me when I try updating CWR.
Can you explain exactly what happens when you try to get into recovery from the bootloader? Your phone reboots and is stuck on the Google logo? Or do you get a message along the lines of "no recovery img"? or what?
Click to expand...
Click to collapse
Yeah stuck on google logo without message!
I reflashed the recovery image through command, like when first setting up CWR, and it worked, i have recovery back!
Thnx!
When I select to reboot to recovery the phone attempts to reboot and never shows the google screen. I have to enter the bootloader and enter recovery from there. After i install what I need to install and click "reboot to system" in the recovery, the phone does the same thing. It just goes to a black screen. I have to re-enter the bootloader again and select "Start" to boot into the ROM.
What could be the issue here? Do I need to reflash the bootloader?
What rom are you on. Stock doesn't give you an option to boot into recovery. I'd try and re-flash the rom
jd1639 said:
What rom are you on. Stock doesn't give you an option to boot into recovery. I'd try and re-flash the rom
Click to expand...
Click to collapse
PSX. This started to happen after I flashed CWM so I switched back to TWRP but it seems like clockwork might of screwed something up. Might have to flash the factory img.
biggiephat said:
PSX. This started to happen after I flashed CWM so I switched back to TWRP but it seems like clockwork might of screwed something up. Might have to flash the factory img.
Click to expand...
Click to collapse
I would try flashing the recovery image in fastboot. That should fix up the recovery issue. Cwm seems to have some issues right now.
jd1639 said:
I would try flashing the recovery image in fastboot. That should fix up the recovery issue. Cwm seems to have some issues right now.
Click to expand...
Click to collapse
That did not work. Still cant turn on the phone unless i go into the bootloader when attached to AC adapter and click start from there.
biggiephat said:
That did not work. Still cant turn on the phone unless i go into the bootloader when attached to AC adapter and click start from there.
Click to expand...
Click to collapse
I would try flashing the entire factory image then. But i think you have something else going on if you need to have it plugged in to start it up
Just used TWRP manager to flash the new 2.8.0.1 wlv build to my m8 and now it just bootloops into recovery everytime I reboot. What do I need to do to resolve this issue. thanks
jwt98 said:
Just used TWRP manager to flash the new 2.8.0.1 wlv build to my m8 and now it just bootloops into recovery everytime I reboot. What do I need to do to resolve this issue. thanks
Click to expand...
Click to collapse
Reflash the previous version you were running.
jwt98 said:
Just used TWRP manager to flash the new 2.8.0.1 wlv build to my m8 and now it just bootloops into recovery everytime I reboot. What do I need to do to resolve this issue. thanks
Click to expand...
Click to collapse
Do not use TWRP manager to install recovery. Use Flashify.
TWRP manager flashes to the wrong block. It flashes to mmcblk0p43 where as you need to have it on mmcblk0p44.
What version of firmware are you on. You will need to update your boot image.
To get out on the bootloop I had to install a Rom which was viper Rom 2.4. When I boot my phone, it still shows the twrp splash screen with the red text at the bottom. Doesn't even show boot animation. Seems like it freezes then home screen pops up like nothing's wrong. Any way I can get my HTC splash and aninmation back. Tried flashing a new boot animation but won't take. Is it still trying to boot to twrp.
jwt98 said:
To get out on the bootloop I had to install a Rom which was viper Rom 2.4. When I boot my phone, it still shows the twrp splash screen with the red text at the bottom. Doesn't even show boot animation. Seems like it freezes then home screen pops up like nothing's wrong. Any way I can get my HTC splash and aninmation back. Tried flashing a new boot animation but won't take. Is it still trying to boot to twrp.
Click to expand...
Click to collapse
Like other person said. You flashed your recovery to your system. You need to go to boot loader an fastboot recovery so it goes where it is supposed to. Then enter recovery via bootloader so you r really in recovery then flash your ROM an it will take care of your issue. Always fastboot recovery to avoid these problems.
I did the same thing through TWRP manager, and reflashed recovery through fastboot, restored, works fine. Thanks for the fix
greydelta38 said:
I did the same thing through TWRP manager, and reflashed recovery through fastboot, restored, works fine. Thanks for the fix
Click to expand...
Click to collapse
Glad to hear I could help.
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.
recently got a hard brick oneplus one (A0001) from my friend.
After trying several times I finally installed the correct driver on win 10 pc and save it out of the hardbrick status using the Color OS method.
but now it won't boot into any os at all. It won't even boot into recovery. Everytime I boot it up, it just stays at the black screen with white 1+ logo there.
I have tried to install TWRP, or reflash cm11s, cm13 on the phone... none of them could get it out of the 1+ logo.
I can't get into recovery at all even after flash twrp successfully via fastboot.
Please let me know if there is other way to get out of the soft brick, no recovery, no os status.
Thank you.
Is the bootloader unlocked properly. If so and its still not working I would try a complete factory reset as there is an image on the forums for it. The if that works look at twrp after. I suggest the tuga version though.
Shinobi_warrior said:
Is the bootloader unlocked properly. If so and its still not working I would try a complete factory reset as there is an image on the forums for it. The if that works look at twrp after. I suggest the tuga version though.
Click to expand...
Click to collapse
Yes, both line on bootloader show "ture ".
I have flash several cm builds via fastboot but none of them works for me.
I also flash twrp but still can't boot into twrp either.
Would you mind point me to the TUGA version? I have been hanging around xda and oneplus forum last couple days but still no luck.
https://www.androidfilehost.com/?w=files&flid=50417
Should use the -5 version it could possibly be your computer have you tried a different one? Maybe its a driver related issue?
":TWRP_3.1.1-5-TugaPower.img"
laofan said:
recently got a hard brick oneplus one (A0001) from my friend.
After trying several times I finally installed the correct driver on win 10 pc and save it out of the hardbrick status using the Color OS method.
but now it won't boot into any os at all. It won't even boot into recovery. Everytime I boot it up, it just stays at the black screen with white 1+ logo there.
I have tried to install TWRP, or reflash cm11s, cm13 on the phone... none of them could get it out of the 1+ logo.
I can't get into recovery at all even after flash twrp successfully via fastboot.
Please let me know if there is other way to get out of the soft brick, no recovery, no os status.
Thank you.
Click to expand...
Click to collapse
The TWRP which you tried is latest official one,right?
Shinobi_warrior said:
https://www.androidfilehost.com/?w=files&flid=50417
Should use the -5 version it could possibly be your computer have you tried a different one? Maybe its a driver related issue?
":TWRP_3.1.1-5-TugaPower.img"
Click to expand...
Click to collapse
thanks, let me try this one.
Mr.Ak said:
The TWRP which you tried is latest official one,right?
Click to expand...
Click to collapse
I was using twrp 3.1.1.0 bacon.img. No luck.
laofan said:
I was using twrp 3.1.1.0 bacon.img. No luck.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Did you try using this? Although,it is based on colour os restore tool,it flashes cm11s instead of colour os through usb-debugging port method(ofcourse,not fastboot).
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Did you try using this? Although,it is based on colour os restore tool,it flashes cm11s instead of colour os through usb-debugging port method(ofcourse,not fastboot).
Click to expand...
Click to collapse
I did that already.. No luck. Still on 1+ logo
laofan said:
I did that already.. No luck. Still on 1+ logo
Click to expand...
Click to collapse
I'm afraid it's hardware issue then.