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.
Related
Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!
I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.
Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English
Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..
Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.
I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App
Ok...I've searched all over the internet and these forums and can't find an answer to my problem so here it goes:
I recently purchased the TF300T pre-owned. I had no idea if the device was rooted or not, but assumed not. I assume correctly so, as I do with all my Android devices, I proceed to look up the root method.
This device has never been able to boot into any type of recovery, stock or otherwise. I get the "Android on his back with the red triangle" error and holding the power button only reboots the device.
So far I have used fastboot to flash CWM recovery and have unlocked the bootloader. (I know the device is unlocked because it tells me so)
After all this, I proceed to enter CWM to root my device and the same error pops up. What am I doing wrong? How do I fix this? And is there any hope for me to root this device from this point?
I appreciate any input given or being directed to the correct answer.
Thanks
P.S. BTW....I did do the JB OTA Update right after I first got it and I did flash a JB Recovery Version....just so you know.
[A] Boot to Recovery
jdcrowell99 said:
Ok...I've searched all over the internet and these forums and can't find an answer to my problem so here it goes:
I recently purchased the TF300T pre-owned. I had no idea if the device was rooted or not, but assumed not. I assume correctly so, as I do with all my Android devices, I proceed to look up the root method.
This device has never been able to boot into any type of recovery, stock or otherwise. I get the "Android on his back with the red triangle" error and holding the power button only reboots the device.
So far I have used fastboot to flash CWM recovery and have unlocked the bootloader. (I know the device is unlocked because it tells me so)
After all this, I proceed to enter CWM to root my device and the same error pops up. What am I doing wrong? How do I fix this? And is there any hope for me to root this device from this point?
I appreciate any input given or being directed to the correct answer.
Thanks
P.S. BTW....I did do the JB OTA Update right after I first got it and I did flash a JB Recovery Version....just so you know.
Click to expand...
Click to collapse
hi JDCrowell99! It is possible that your installation of CWM may be causing you issues. I too had unlocked the bootloader after updating to JB OTA stock ROM. I used fastboot to install CWM. I continually got invalid signature failures whenever I tried to flash a new ROM (Stock or modified). I finally ran across a thread that stated the invalid signature problem appears on an occasion with CWM and to install TWRP. I did so using the instructions in thread:
http://forum.xda-developers.com/showthread.php?t=1672108
After upgrading to TWRP I can now flash ROMs without getting an invalid signature error.
Hope that helps and good luck!
- Mike
I'm with you, Mike. I tried CWM when I first got my tablet and it wouldn't make backups properly. I flashed TWRP with fastboot and haven't had any issues since. :good:
Sent from my LG-LG855 using Xparent Green Tapatalk 2
Mike_SattyEng said:
hi JDCrowell99! It is possible that your installation of CWM may be causing you issues. I too had unlocked the bootloader after updating to JB OTA stock ROM. I used fastboot to install CWM. I continually got invalid signature failures whenever I tried to flash a new ROM (Stock or modified). I finally ran across a thread that stated the invalid signature problem appears on an occasion with CWM and to install TWRP. I did so using the instructions in thread:
http://forum.xda-developers.com/showthread.php?t=1672108
After upgrading to TWRP I can now flash ROMs without getting an invalid signature error.
Hope that helps and good luck!
- Mike
Click to expand...
Click to collapse
Mike, that worked perfectly!
Thanks for the advice. Much appreciated
Awesome!
jdcrowell99 said:
Mike, that worked perfectly!
Thanks for the advice. Much appreciated
Click to expand...
Click to collapse
Glad to hear it worked for you!
TF300T Bricked with bootloader unlocked, HELP PLEASE!!!!
Hi guys, I'm from Brazil, sorry about my english!! I have a TF300T, I unlock the bootloader and when I was trying to root the device I made something very very wrong and I didn´t know how to fix it!!! I execute the fastboot commands but I can´t enter in CMW menu after it, so I enter in the system menu (RCK, Android, USB, Wipe Data) and unfortunatly I click on Wipe Data icon!!! Now i can´t enter on system menu and the device don´t turn off!!!! When I push the power button plus Vol Down nothing happens. Please somebody HELP ME!!!!!
Hey guys, I installed CWM on my buddies HTC one S (ville) and I keep getting a weird problem with CWM. I have successfully flashed CM10 multiple times and have made only one back up. Every time his phone dies and he plugs it in and tries to power it on it boots straight to recovery and after you press reboot phone it boots right back to recovery again and again... The only way it fixes itself is when you restore the back up and then it sets him back to that date. I'm wondering if this is a problem with CWM or something else... I'm new to HTC devices because I have always been on the Galaxy line from Samsung so some of this is a little new to me...
Thanks in advance!!
This is a known glitch with CWM. If you plug it in when its off and try to turn it on, it'll automatically Boot into CWM Recovery. I prefer TWRP personally, had too many problems with CWM and getting into the same exact pain-in-the-neck Bootloop as you're referring to.
As far as I am aware, there isn't a way to get out of the CWM Bootloop unless you just let the phone run out of Battery, get into the Bootloader (Which is somewhat of a challenge with the CWM Bootloop), and then flash a different Recovery from Fastboot. Correct me if i'm wrong on there not being any other way around this.
It's happened to me once, I flashed the.stock boot.img and it worked fine.after that. Not sure if its a fix but it got me outta of it.
echo en Android
Thanks guys I think I'll try TWRP but just to check does CM10 work with TWRP and if so how do I flash a new recovery?
yes cm10 worx with twrp. For flashing recovery, download d appropriate recovery.img for ur device. place this in the fastboot folder or the platform-tools folder.
now, boot into bootloader and enter fastboot then connect phone to PC , it should say fastboot USB .
Now open a command window and use this command---
fastboot flash recovery recoveryname.img.
Sent from my One V
mattytom87 said:
Thanks guys I think I'll try TWRP but just to check does CM10 work with TWRP and if so how do I flash a new recovery?
Click to expand...
Click to collapse
Cyanogenmod 10 does indeed work with TWRP as far as I know. Along with mihirengg19's Reply above, there is also an Alternative way to flashing a new Recovery, and that is to use the HTC One S All-In-One Toolkit. Its the easiest/safest way, if you don't know what you're doing.
yes toolkit is great but manually is best...
Sent from my One V
Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!
DaiMinzz said:
Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!
Click to expand...
Click to collapse
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!
stevekind said:
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!
Click to expand...
Click to collapse
Still the same problem didn't work
Im sure everthing on the pc went ok, but my Oneplus has recovery bug
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.