Hello, I am having issues with TWRP recovery. I have been running mean rom since I got the phone when it was new. I have been thinking of trying a new rom and wanted to update TWRP. I mad a nandroid back up with TWRP, also backed up my apps with Titanium, no issues with either. Now the fun begins, I used goomanager to updated TWRP to 2.6.1 and now when i boot into recovery nothing happens, the phone gets the splash screen with the white bar on the upper right then instead of opening recovery it reboots to the phone.
I cannot get into recovery, I have tried battery disconnect, rebooting multiple times using bootloader to reset to fasctory and nothing happened. It didnt even reset factory defaults. The phone works, everything works jut cant get into recovery. any ideas?
thanks
You're saying you can boot into Android but not to recovery, right? Have you tried pushing the recovery to the phone via fastboot? If that doesn't work, sounds like you need to RUU and re-root.
Sent from my HTC EVO 4G LTE
recovery
I dont trust the goomanager app for recovery images.
http://teamw.in/project/twrp2/98
read the instructions and flash that one instead. there are instructions for multiple situations.
---------- Post added at 11:07 PM ---------- Previous post was at 11:03 PM ----------
jimbo4822 said:
I have tried battery disconnect
That is no easy task on an evo lte
Click to expand...
Click to collapse
Related
I flashed my Atrix with CWM from RomManager. Everything worked fine. I loaded CM7 on no problem. I had some issues with it (Pre beta 4) so i recovered back to stock backup i had made. Recently the CM7 beta came out so i wanted to try that. I tried restarting and holding the volume down key and got the normal menu. I went to Android Recovery, but it didn't appear to be CWM anymore. It was a little android guy with a yellow exclamation point? I was able to figure out that if you click both volume up and down together you can get to a wipe/load/ or reboot menu. However this was a bit strange. I went ahead and did a wipe from that menu (I pry shouldn't have - oh well). Anyway. I can't seem to get back into CwM. Does anyone know what could be going on. Do i have to re-root the phone and download rom manager again? It doesn't seem like that should be neccassary. Any help you guys can give would be great. Thanks!
Yes you need root for a custom recovery.
there is one click root now look in general
OP, did you make a nandroid backup with stock + rooted + bootloader unlocked? And it successfully restored with that while you were on CM7?
I have the latest version of Rom manager from the market place (v4.4.0.7) and I flashed what i think is the latest version of CWM (5.0.2.0).
---------- Post added at 09:02 PM ---------- Previous post was at 08:58 PM ----------
I made a back up when i got into cwm the first time i was loading cm7 prebeta 4. I just went under backup/restore section of CWM and made a back up. So what i have done since is redid root. Then i downloaded Titatnium and got back to stock with my apps. Then i opened rom manager, (i flashed cwm again - even though it said i was on latest recovery). I restarted and tried to manual go into "Android Recovery" same thing (little android dude with yellow exclamation point). Then i rebooted normally and from rom manger i clicked "Reboot with Recovery" (thought since maybe it was a command from Rom manager it might work). My phone rebooted into that stupid little android guy again. It seems like i can't get into CWM? Any ideas guys?
I don't know much about this, but is there any way you could uninstall the CWM Recovery? Once that's done, try installing it again and hope for the best.
I don't think you can uninstall cwm. Anyone else got any ideas? Please? ?
Sent from my MB860 using XDA App
Have you deleted the 'install-recovery.sh' file at /system/etc?
no, i didn't know i had to delete that? How did i ever get into that custom recovery then?
Beats me mate, have you tried deleting it and trying again? Let me know how it goes on. If you cant delete it for whatever reason, use ADB and the command
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
Click to expand...
Click to collapse
tried deleting it, but nothing. I don't know what the heck is going on here?
Hi all. My Droid x2 is stuck on the boot screen with the Motorola logo and won't go past that. I attempted to flash Speedy v6, and this caused this. I also tried fastbooting by going into Android Recovery and wiping cache/format data, and it still does not work. Please help me with this situation. Thanks
Try sbf if you can't get back into bootstrap recovery.
Sent from my DROID X2 using Tapatalk
itskevin94 said:
Hi all. My Droid x2 is stuck on the boot screen with the Motorola logo and won't go past that. I attempted to flash Speedy v6, and this caused this. I also tried fastbooting by going into Android Recovery and wiping cache/format data, and it still does not work. Please help me with this situation. Thanks
Click to expand...
Click to collapse
If you made a nandroid backup before you broke it, turn phone off and plug it in, hope it boots into bootstrap recovery, then restore backup. If no backup or doesn't boot into bootstrap, you will have to sbf
Sent from my DROID X2 using XDA App
Ihad the same problem but turned phone back on with power and down volume button on at same time until you get into the point where you can get into your android recovery. Remember to hit both volume buttons at same time when you get to the android and triangle. Wipe data factory reset and re boot and it worked for me. If not then you will have to sbf again. I was ready to sbf but this worked instead and saved some time.
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
EvilTim said:
If you made a nandroid backup before you broke it, turn phone off and plug it in, hope it boots into bootstrap recovery, then restore backup. If no backup or doesn't boot into bootstrap, you will have to sbf
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
If you have a backup you can get to it with the stock recovery.
Travisdroidx2 said:
Ihad the same problem but turned phone back on with power and down volume button on at same time until you get into the point where you can get into your android recovery. Remember to hit both volume buttons at same time when you get to the android and triangle. Wipe data factory reset and re boot and it worked for me. If not then you will have to sbf again. I was ready to sbf but this worked instead and saved some time.
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
If you have a backup you can get to it with the stock recovery.
Click to expand...
Click to collapse
How do u get to a backup using stock recovery?
Travisdroidx2 said:
If you have a backup you can get to it with the stock recovery.
Click to expand...
Click to collapse
Really now?
That would be nice.
Sorry must be a noob mistake. I thought while I was in there to clear data/factory thought I also seen a spot to load zip from SD. Guess I was wrong you all know more than I do I have only been at it now for a couple of months
Pretty sure there is an option to apply update zip but my backups aren't named update and they aren't zips so that poses a problem __
I see I never tried I just figure that yo ucould get to it like you do with recovery app. I did get bootloop when flashing to 2.3.4 and thought I was going to have to sbf again. However starting up in backup recovery and clearing data and factory reset again fixed the issue. Eclipse went smooth and is looking good! Just concerned on my battery life as I need a strong battery for work.
Yes u will have to clear data/cache from stock almost every time u sbf. I know I have.
i sbf back to 2.3.3 and reflashed the script and worked perfectly. thanks for all your help!
OK, I think it is "sort of fixed" but, here goes...
I booted into recovery to do a fresh wipe/install of CleanRom 1.3 (odexed version).
Wife got me side tracked and after wiping dalvik and then system, I accidently rebooted before flashing the ROM.
Phone was stuck at the "Samsung Galaxy S4" screen.
Tried booting into Recovery (twrp 2.5.0.2) but, apparently I wasn't holding the Volume Up button long enough and the phone would just reboot to the normal "Samsung Galaxy S4" screen again and hang.
So I went into Download mode, and tried re-rooting the phone using the instructions here, Odin said "PASS" but, after waiting about 10 minutes, the phone still hung at the same screen.
I was then able to successfully boot into recovery, reflashed the Scotts Cleanrom 1.3 odexed (found here) and everything seems to be fine.
Question is, I never was able to flash, using Odin, the stock kernel again but, in the "about phone" menu, it shoes me as being on the 3.4.0-562219 kernel version.
Is this OK?
How would I do a fresh wipe (I'm talking EVERY MO****IN THING) and start again from stock, everything stock except SD card?
http://www.sxtpdevelopers.com/showthread.php?t=237
but you might wanna try http://forum.xda-developers.com/showthread.php?t=2301259&highlight=factory+reset first if you have any data you want
---------- Post added at 08:21 PM ---------- Previous post was at 08:17 PM ----------
tgumina said:
http://www.sxtpdevelopers.com/showthread.php?t=237
but you might wanna try http://forum.xda-developers.com/showthread.php?t=2301259&highlight=factory+reset first if you have any data you want
Click to expand...
Click to collapse
edit: http://forum.xda-developers.com/showthread.php?t=2289325&highlight=one+click might be better or easier. for full wipe
Thank you, the weird thing is, I am not bricked at all, once I was able to boot into recovery and reflash the rom mentioned in OP, phone is acting like normal, tried several normal reboots and all is well.
Should I do an unroot flash and start from scratch or is this one of those "if it ain't broke, don't fix it" sort of situations?
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
Did you boot system after unlocking boot loader? or did you flash twrp right away. also 2.7.0.4 is out. Did you use the UL_CA twrp and not the WHL? Need more info, has it booted since you installed twrp?
an0ther said:
Did you boot system after unlocking boot loader? or did you flash twrp right away. also 2.7.0.4 is out. Did you use the UL_CA twrp and not the WHL? Need more info, has it booted since you installed twrp?
Click to expand...
Click to collapse
Yes, I remember booting back into the phone after unlocking the boot loader. I made some calls, sent some texts, then flashed twrp.
I used the UL-CA version after following these instructions. androidcentral.us/2014/04/root-att-htc-one-m8/ (ugh, won't let me link)
I'm not sure what the difference between that and the WHL is.
Also, not sure what you mean by "has it booted since you installed twrp", I've tried rebooting it numerous times, but it just goes back into twrp.
Thanks!!
PirateP3t3 said:
Yes, I remember booting back into the phone after unlocking the boot loader. I made some calls, sent some texts, then flashed twrp.
I used the UL-CA version after following these instructions. androidcentral.us/2014/04/root-att-htc-one-m8/ (ugh, won't let me link)
I'm not sure what the difference between that and the WHL is.
Also, not sure what you mean by "has it booted since you installed twrp", I've tried rebooting it numerous times, but it just goes back into twrp.
Thanks!!
Click to expand...
Click to collapse
Well i'm not actually sure what happened there but I ended up just flashing a custom rom. I was really trying to stick with stock for now but whatever. Anyways, thanks for the reply and I have much to learn
PirateP3t3 said:
Well i'm not actually sure what happened there but I ended up just flashing a custom rom. I was really trying to stick with stock for now but whatever. Anyways, thanks for the reply and I have much to learn
Click to expand...
Click to collapse
The stock nandroid for twrp is available to download. Stock is super bloated anyway. Make sure you get newer version of twrp.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 10:24 PM ---------- Previous post was at 10:23 PM ----------
Whl is for Sprint.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Dear XDA,
I have an att one m8, I was running cyanogenmod and tried to install the viper rom which bricked my phone. I then flashed TWRP and the install didn't work either and now I have a bricked phone. I re-flashed CWM and tried to install my nandriod but it didn't work. Now I am stuck with a phone that is stuck on the HTC screen with the this build is for development purposes only message. I have no idea what to do now and am completely stuck as I am kinda screwed since my nandriod doesn't work. What do I do to get back to stock and it would be nice if I could get back to stock and not see any bloatware waiting for me also!
ng4 said:
Dear XDA,
I have an att one m8, I was running cyanogenmod and tried to install the viper rom which bricked my phone. I then flashed TWRP and the install didn't work either and now I have a bricked phone. I re-flashed CWM and tried to install my nandriod but it didn't work. Now I am stuck with a phone that is stuck on the HTC screen with the this build is for development purposes only message. I have no idea what to do now and am completely stuck as I am kinda screwed since my nandriod doesn't work. What do I do to get back to stock and it would be nice if I could get back to stock and not see any bloatware waiting for me also!
Click to expand...
Click to collapse
Run bootable ruu as long as you are AT&T. This should be in questions and answers btw.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
ng4 said:
Dear XDA,
I have an att one m8, I was running cyanogenmod and tried to install the viper rom which bricked my phone. I then flashed TWRP and the install didn't work either and now I have a bricked phone. I re-flashed CWM and tried to install my nandriod but it didn't work. Now I am stuck with a phone that is stuck on the HTC screen with the this build is for development purposes only message. I have no idea what to do now and am completely stuck as I am kinda screwed since my nandriod doesn't work. What do I do to get back to stock and it would be nice if I could get back to stock and not see any bloatware waiting for me also!
Click to expand...
Click to collapse
First off, this isn't a brick. You just got yourself into a state where the phone won't boot, and just don't know the steps to recover from this particular state. A brick requires the phone to be taken apart in order to recovery, and it would pretty much mean you are screwed.
1) Why did you flash TWRP again after flashing Viper rendered the phone unbootable? Why not just restore your CWM nandroid (not sure, but it seems your nandroid is from CWM, not TWRP)
2) Did you factory reset in bootloader (not advised, will corrupt internal memory)?
3) S-on or S-off?
Suggestion by an0ther to RUU (relocking bootloader required if s-on) will certainly get you up and running. But it might be as simple as getting a custom or stock rooted ROM on the phone, and flashing with CWM/TWRP
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
an0ther said:
This should be in questions and answers btw.
Click to expand...
Click to collapse
I've reported to mods to move the thread to the correct section.
redpoint73 said:
First off, this isn't a brick. You just got yourself into a state where the phone won't boot, and just don't know the steps to recover from this particular state. A brick requires the phone to be taken apart in order to recovery, and it would pretty much mean you are screwed.
1) Why did you flash TWRP again after flashing Viper rendered the phone unbootable? Why not just restore your CWM nandroid (not sure, but it seems your nandroid is from CWM, not TWRP)
2) Did you factory reset in bootloader (not advised, will corrupt internal memory)?
3) S-on or S-off?
Suggestion by an0ther to RUU (relocking bootloader required if s-on) will certainly get you up and running. But it might be as simple as getting a custom or stock rooted ROM on the phone, and flashing with CWM/TWRP
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
I've reported to mods to move the thread to the correct section.
Click to expand...
Click to collapse
Beacause my nandriod was corrupted and I thought that it was a CWM bug that bricked my phone so I switched to TWRP. I ended up going back to CWM and flashed a stock rom that worked.