So I was on my TWRP recovery and I wiped Dalvik cache and all the other things that I was able to wipe while I was on the TWRP recovery and now my phone won't boot up. It is stuck on the white screen that says, "htc powered by android"
I assume that I probably wiped the os and everything. I can't get access to the TWRP recovery now what do I do?
Hold power, vol up, and vol down. Try that, if that does not work try holding the power button down till the phone shuts off, they hold power button and vol down this should get you into recovery.
grneyez said:
Hold power, vol up, and vol down. Try that, if that does not work try holding the power button down till the phone shuts off, they hold power button and vol down this should get you into recovery.
Click to expand...
Click to collapse
Power button + vol down is the button combo for bootloader, not recovery. Bootloader and recovery completely different things, so its important not the confuse them.
Power + vol up will restart the phone (similar to a battery pull on phones with a use accessible battery).
Power+ vol up and vol down is not any button combination for this phone I am familiar with.
Its not clear whether the OP is having trouble accessing bootloader; or if he can access bootloader but not recovery. Again, these are 2 very different issues. You are right, in that failure to access bootloader is almost always a matter of user error in not performing the button combo correctly. If the phone is stuck on the boot splash (which is what it sounds like) the correct sequence would be:
1) Hold power + vol up until the phone reboots.
2) The moment the screen goes black, but before the boot splash screen, let go of the vol up, and press vol down
3) Do not let go of vol down until the bootloader screen appears
Failure to get into bootloader is usually because either the user started pressing vol down to late; or let go of it too early. As long as the screen comes on, bootloader is virtually always accessible.
---------- Post added at 12:20 PM ---------- Previous post was at 12:08 PM ----------
jae2014 said:
So I was on my TWRP recovery and I wiped Dalvik cache and all the other things that I was able to wipe while I was on the TWRP recovery and now my phone won't boot up. It is stuck on the white screen that says, "htc powered by android"
I assume that I probably wiped the os and everything.
Click to expand...
Click to collapse
Of course the phone won't boot. If you wiped /system, the OS is wiped.
If you don't know what it is, you shouldn't be wiping it.
Some folks like to wipe /system before they flash a new ROM for the sake of being thorough, but technically this is not necessary. Flashing a ROM always wipes /system.
But it doesn't sound like you were flashing a ROM. What were you trying to do, and why were you wiping things?
My advice would be to access bootloader as described above, then select recovery. Alternately, use adb to reboot into recovery:
adb reboot recovery
If you still can't get into recovery with either the adb command or from bootloader, its likely that recovery was somehow damaged or otherwise not accessible. Use fastboot to flash it again (boot into bootloader, select fastboot mode):
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual name of the desired the recovery file with no quotes, placed in your fastboot folder on your computer)
Once recovery is working again, either restore your nandroid or flash the stock rooted or custom ROM of your choice.
redpoint73 said:
Power button + vol down is the button combo for bootloader, not recovery. Bootloader and recovery completely different things, so its important not the confuse them.
Power + vol up will restart the phone (similar to a battery pull on phones with a use accessible battery).
Power+ vol up and vol down is not any button combination for this phone I am familiar with.
Its not clear whether the OP is having trouble accessing bootloader; or if he can access bootloader but not recovery. Again, these are 2 very different issues. You are right, in that failure to access bootloader is almost always a matter of user error in not performing the button combo correctly. If the phone is stuck on the boot splash (which is what it sounds like) the correct sequence would be:
1) Hold power + vol up until the phone reboots.
2) The moment the screen goes black, but before the boot splash screen, let go of the vol up, and press vol down
3) Do not let go of vol down until the bootloader screen appears
Failure to get into bootloader is usually because either the user started pressing vol down to late; or let go of it too early. As long as the screen comes on, bootloader is virtually always accessible.
---------- Post added at 12:20 PM ---------- Previous post was at 12:08 PM ----------
Of course the phone won't boot. If you wiped /system, the OS is wiped.
If you don't know what it is, you shouldn't be wiping it.
Some folks like to wipe /system before they flash a new ROM for the sake of being thorough, but technically this is not necessary. Flashing a ROM always wipes /system.
But it doesn't sound like you were flashing a ROM. What were you trying to do, and why were you wiping things?
My advice would be to access bootloader as described above, then select recovery. Alternately, use adb to reboot into recovery:
adb reboot recovery
If you still can't get into recovery with either the adb command or from bootloader, its likely that recovery was somehow damaged or otherwise not accessible. Use fastboot to flash it again (boot into bootloader, select fastboot mode):
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual name of the desired the recovery file with no quotes, placed in your fastboot folder on your computer)
Once recovery is working again, either restore your nandroid or flash the stock rooted or custom ROM of your choice.
Click to expand...
Click to collapse
I appreciate your response I'm not even sure what it is that I did wrong. I was just kind of messing around and clicking things. I've learned my lesson the hard way. lol Anyways, I managed to flash the viper one rom somehow lol and now everything is ok.
I am having the same issues. but wiping the recovery cache and all that is mentioned does not work. I flash newest and or oldest twrp via fastboot commands and nothing works. It gets stuck on the white screen with the pink letters for rebooting to recovery, then after a while it just reboots the phone into the OS.
SonneKonig said:
I am having the same issues. but wiping the recovery cache and all that is mentioned does not work. I flash newest and or oldest twrp via fastboot commands and nothing works. It gets stuck on the white screen with the pink letters for rebooting to recovery, then after a while it just reboots the phone into the OS.
Click to expand...
Click to collapse
What hboot?
Hboot-3.19.0.000
os-4.28.502.1
att
s-off
supercid
twrp
root
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
I got TWRP working but the real issue is no cell service or data. Benn going on for a while now. I RUU to stock flashed 3.16 and then back to 4.28. Then root etc again. Nothing fixes it. Got a new sim card as well.
SonneKonig said:
Hboot-3.19.0.000
os-4.28.502.1
att
s-off
supercid
twrp
root
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
I got TWRP working but the real issue is no cell service or data. Benn going on for a while now. I RUU to stock flashed 3.16 and then back to 4.28. Then root etc again. Nothing fixes it. Got a new sim card as well.
Click to expand...
Click to collapse
You're talking about a completely different issue now, and not enough details and specifics.
Are you on AT&T?
How long is "a while", is it a year, a month, a week?
Did you change anything (new ROM, etc.) that may have stopped cell service from working; or did it just start happening spontaneously?
Does the SIM work properly on another phone (if available)? Did you try a different SIM (your provider's store might be able to help with that).
No service at all, not even emergency calls possible?
Hello Guys,
I have an issue with TWRP recovery. I can't enter in TWRP from bootloader. I have installed ViperOneM8 5.0.1. and used now for more then one year. I also notice that my battery last just for 8 hours and I think it should help to clean my phone. When I decide to clean my phone I try to enter in recovery and when I chose an option recovery in bootloader it is trying to enter but then it goes back to bootloader. I also try to install new TWRP recovery via usb cable (ADB) and issue stay the same. In the past I enter in TWRP recovery with out any problems. Can somebody help regarding this issue?
Thank you and BR...
Basinc said:
I try to enter in recovery and when I chose an option recovery in bootloader it is trying to enter but then it goes back to bootloader. I also try to install new TWRP recovery via usb cable (ADB) and issue stay the same.
Click to expand...
Click to collapse
What are the specific results when you flash TWRP? Any error messages? Or does it say successful?
What version TWRP did you try? Saying "new" is not enough. I've often seen folks say they used "new" or "latest" and when prompted for a version number, it turns out the version is 2 years old.
What firmware (OS number on bootloader screen)?
Also, try fastboot erase cache, and try to flash TWRP again.
redpoint73 said:
What are the specific results when you flash TWRP? Any error messages? Or does it say successful?
What version TWRP did you try? Saying "new" is not enough. I've often seen folks say they used "new" or "latest" and when prompted for a version number, it turns out the version is 2 years old.
What firmware (OS number on bootloader screen)?
Also, try fastboot erase cache, and try to flash TWRP again.
Click to expand...
Click to collapse
When I flash TWRP it say successful. I also try to flash it with TWRP manager.
I try to flash version 2.8.7.0. When I saw I couldn't enter in TWRP, then I also try with TWRP manager and try to flash version 3.0.2.0. But again no luck.
OS number is 4.16.401.13
I try to fastboot erase cache, but when I select fastboot I have no option erase cache in bootloader. Only Hboot, Ramdump, reboot, reboot fastboot & power down.
Do you have any new hints for me and thank you for your time...
BR,
Basinc.
Basinc said:
When I flash TWRP it say successful. I also try to flash it with TWRP manager.
I try to flash version 2.8.7.0. When I saw I couldn't enter in TWRP, then I also try with TWRP manager and try to flash version 3.0.2.0. But again no luck.
OS number is 4.16.401.13
Click to expand...
Click to collapse
I'd stick with flashing by fastboot command. Apps like TWRP Manager just add a layer of needless complication. Something more to go wrong.
Both those TWRP versions should be okay, I think. But for your OS number, I'd be inclined to stick with 2.8.7.0
Basinc said:
I try to fastboot erase cache, but when I select fastboot I have no option erase cache in bootloader. Only Hboot, Ramdump, reboot, reboot fastboot & power down.
Click to expand...
Click to collapse
Its not a bootloader option on the phone, its a fastboot command you issue on your computer, like the one you used to flash TWRP. Connect the phone to PC, boot phone to bootloader-fastboot mode. Then in command prompt:
fastboot erase cache
Then try to flash TWRP 2.8.7 again, and see if you can them boot into TWRP.
Hi Redpoint,
I try to erase cache via usb cable like I would flash recovery. In cmd cache was erased successfully. I also flash recovery successfully in cmd, but then I can't enter in recovery from bootloader. When I chose option recovery I go back to bootloader. The same as before. Do you have any other hint for this problem?
Basinc said:
Do you have any other hint for this problem?
Click to expand...
Click to collapse
Hmm, not sure what the problem might be. All I can think of is relock the bootloader (not needed if s-off) and RUU back to full stock image (basically, "start from scratch"), then try to unlock the bootloader and install TWRP again.
For that matter, you can RUU up to Marshmallow (MM) firmware, to get everything up to date. Although you will need to flash the MM firmware first, then MM RUU as described in the red text under RUUs section of my Index thread: https://forum.xda-developers.com/showthread.php?t=2751432
Also, keep in mind that RUU will wipe all data on the phone.
Related
Hey everyone, I'm brand new to this, and I was told before I start getting into ROMS that I need to run this software:
http://forum.xda-developers.com/showthread.php?t=1182871
So I followed each and every step, and my phone rebooted and it said "Unlocked" like it was supposed to. BUT, when it booted into the OS, it booted into the stock OS as if I had just bought it off the shelf. Additionally, I am seeing a little exclamation point and android character when I go to the Android Recovery option under fastboot (also installed via linked software)
What happened!?
Congratulations, you have just successfully unlocked the bootloader. Obviously you had higher hopes and were expecting bells and whistles, sorry to disappoint but that's it for this step. Next, flash a custom recovery via fastboot (I recommend the RomRacer's version of CWM), and then use that recovery to flash whatever ROM you choose. Instructions for all these steps are available in other threads. Good luck!
ravilov said:
Congratulations, you have just successfully unlocked the bootloader. Obviously you had higher hopes and were expecting bells and whistles, sorry to disappoint but that's it for this step. Next, flash a custom recovery via fastboot (I recommend the RomRacer's version of CWM), and then use that recovery to flash whatever ROM you choose. Instructions for all these steps are available in other threads. Good luck!
Click to expand...
Click to collapse
I thought when the phone rebooted after unlocking bootloader, it would boot back into the system I had before unlocking it? I flashed the "Tenfar recovery" that was in the automated script. However, when I flashboot into "Android Recovery," this is when I get to the exclamation point/ android character. Is this normal?
EDIT: I just reran the script to install recovery, and it seems to have worked the second time. I ran a backup and saved it on my external SD card, but is this backup of MY system, or of whatever its now booting into after being unlocked?
Ok guys, apparently I've somehow managed to screw this up. I swear I am following instructions completely!
I decided to try MIUI first, and so I made the backup, wiped all the data/cache/etc, and flashed the ROM. Upon reboot I discovered I couldnt get past the Dual Core screen. So, I rebooted into recovery and flash my backup, and have now found out that I cant get past the "Rethink Possible" screen.
Since at that point you haven't flashed anything else yet, the backup you made couldn't be anything else but your "normal" system.
No idea what (if anything) might've gone wrong, but here's something that you maybe didn't know - after flashing a new ROM, the following boot will always take MUCH longer than usual. After that the phone should boot at "normal" speed again. So have patience and give it time.
Also, not sure how come you're stuck at "rethink" screen. As far as I know that's the very end of the boot process, it is shown just before the launcher starts. Still, give it more time. If nothing happens after, say, 5 mins, try booting into recovery and wipe data and cache, then try booting normally again.
I think I may have found the problem. When I go to restore, it runs for a while, and then says "Error formatting /data"
What should I do?
Alright, im at a loss here. I've done everything I can think of. I've tried every restore setting possible, I've wiped everything MANY times, I've flashed a few diff ROMS to try to get ANYTHING to work.
I am utterly confused about why none of this is working. I've read so much info on the forums that my head is just swimming. I never thought this would be that hard.
At this point I'd just like to get ANYTHING working so that I have a usable phone tomorrow.
sounds like you're having lots of fun :laugh: try not to worry... we've all been there to varying degrees
If this was me I wouldn't go down the 'fastboot' method but just stick to accessing android recovery by the 'power off/on, hold volume down when powering on, and then selecting android recovery'
After this you should be into the phone's recovery mode with the menu in front of you? scroll down to 'wipe data/factory reset' and select (by pressing the power button) after this select 'wipe cache partition' and repeat the process.
Then go to 'install zip from sd card' and select this... if you have installed the ROM's correctly you should have a list at the bottom of the 'sd card' list? Select the rom you want and install by pressing power button ect.
Once this has been installed you then need to 'go back' to the main recovery page and then select 'reboot system'
Let us know if this helps... and good luck!
i would add wipe all (data & cache) again after installing!
I would try this:
Power down your phone, go to fastboot mode (Power + Vol-, then find Fastboot with Vol- and confirm with Vol+), connect to computer, then on the computer run these commands:
Code:
moto-fastboot erase -w
moto-fastboot reboot-bootloader
Then in the same menu as before, select Android recovery (and confirm with Vol+). When in recovery, try doing restore again.
If that doesn't work either, here's an alternative method to wipe /data from recovery using adb.
When in recovery, connect the phone to the computer and run this:
Code:
adb shell
That should place you in the phone's shell. Now in recovery go to Mounts and storage > Mount /data.
Then in the phone shell (on the computer) run this:
Code:
mount | grep /data
It should print something like:
Code:
[color=red]/dev/block/mmcblk0p[B]XX[/B][/color] on /data type ext3 (rw,nodev,noatime,nodiratime,errors=continue,data=ordered)
Note the first value printed. For me it's /dev/block/mmcblk0p16 but I'm not sure if that goes for all Atrixes out there, so better safe than sorry.
Now go back to recovery and select Mounts and storage > Unmount /data.
Now back to the computer - run this:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p[B]XX[/B]
Where XX is obviously what you got from the previous command.
When it's done (you get your prompt back), type exit and go back to recovery on the phone. Now you can try restoring your backup or flashing a ROM or whatever.
Solved
barry_ said:
sounds like you're having lots of fun :laugh: try not to worry... we've all been there to varying degrees
If this was me I wouldn't go down the 'fastboot' method but just stick to accessing android recovery by the 'power off/on, hold volume down when powering on, and then selecting android recovery'
After this you should be into the phone's recovery mode with the menu in front of you? scroll down to 'wipe data/factory reset' and select (by pressing the power button) after this select 'wipe cache partition' and repeat the process.
Then go to 'install zip from sd card' and select this... if you have installed the ROM's correctly you should have a list at the bottom of the 'sd card' list? Select the rom you want and install by pressing power button ect.
Once this has been installed you then need to 'go back' to the main recovery page and then select 'reboot system'
Let us know if this helps... and good luck!
Click to expand...
Click to collapse
This is EXACTLY the process I had been using. I just tried this again with MIUI, and again I got the screen that said MIUI was successfully installed from the sdcard. I rebooted, and now I've been stuck at the "Dual Core" unlocked screen.
gianluca.tomat said:
i would add wipe all (data & cache) again after installing!
Click to expand...
Click to collapse
No luck im afraid.
ravilov said:
I would try this:
Power down your phone, go to fastboot mode (Power + Vol-, then find Fastboot with Vol- and confirm with Vol+), connect to computer, then on the computer run these commands:
Code:
moto-fastboot erase -w
moto-fastboot reboot-bootloader
Then in the same menu as before, select Android recovery (and confirm with Vol+). When in recovery, try doing restore again.
Click to expand...
Click to collapse
How do I do this on the computer? What do I type it into?
wvcaudill2 said:
This is EXACTLY the process I had been using. I just tried this again with MIUI, and again I got the screen that said MIUI was successfully installed from the sdcard. I rebooted, and now I've been stuck at the "Dual Core" unlocked screen.
Click to expand...
Click to collapse
This is because the recovery you used is an outdated one.Install rom racer recovery, you can install it through fastboot http://forum.xda-developers.com/showthread.php?t=1204500
harishatrix said:
This is because the recovery you used is an outdated one.Install rom racer recovery, you can install it through fastboot http://forum.xda-developers.com/showthread.php?t=1204500
Click to expand...
Click to collapse
How do I enter these flashboot commands into the computer?
wvcaudill2 said:
How do I enter these flashboot commands into the computer?
Click to expand...
Click to collapse
As you don't know about fastboot I would suggest you to download automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named " recovery-clockwork-4.0.1.4" replace it with romracer recovery you downloaded and rename the romracer recovery as " recovery-clockwork-4.0.1.4". Just to be safe even replace the "recovery-en-goapk-0630-1029" with rom racer recovery and rename it as "recovery-en-goapk-0630-1029". Open main and select option 6 and follow the on screen instructions.
harishatrix said:
As you don't know about fastboot I would suggest you to download automatic bootloader unlock from here http://forum.xda-developers.com/showthread.php?t=1182871, unzip it, you will find img file named " recovery-clockwork-4.0.1.4" replace it with romracer recovery you downloaded and rename the romracer recovery as " recovery-clockwork-4.0.1.4". Just to be safe even replace the "recovery-en-goapk-0630-1029" with rom racer recovery and rename it as "recovery-en-goapk-0630-1029". Open main and select option 6 and follow the on screen instructions.
Click to expand...
Click to collapse
Okay, so I did this and then went in and reflashed MIUI and it worked! Of course, now that I think about it, I should've created a new backup or something, but I guess its too late now.
On a side note, where can I find that google apps package?
wvcaudill2 said:
Okay, so I did this and then went in and reflashed MIUI and it worked! Of course, now that I think about it, I should've created a new backup or something, but I guess its too late now.
On a side note, where can I find that google apps package?
Click to expand...
Click to collapse
You will find the link for gapps from thread you downloaded the rom, I would suggest youto flash CWM touch recovery as it will make future flashing easy. Download it from here http://forum.xda-developers.com/showthread.php?t=1475444, and flash it the way you flashed the rom. Try out neutrino Rom if you are looking for fast and battery efficient rom
There are fruitcakes if you want to go back to stock rom.
harishatrix said:
You will find the link for gapps from thread you downloaded the rom, I would suggest youto flash CWM touch recovery as it will make future flashing easy. Download it from here http://forum.xda-developers.com/showthread.php?t=1475444, and flash it the way you flashed the rom. Try out neutrino Rom if you are looking for fast and battery efficient rom
There are fruitcakes if you want to go back to stock rom.
Click to expand...
Click to collapse
Could you link me to these "fruitcakes," and do I flash them like everything else?
wvcaudill2 said:
Could you link me to these "fruitcakes," and do I flash them like everything else?
Click to expand...
Click to collapse
Here you go http://forum.xda-developers.com/showthread.php?t=1163009 and yes you have to flash it like all other roms.
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
JM1084 said:
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
Click to expand...
Click to collapse
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
santod040 said:
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
Click to expand...
Click to collapse
Yeah, there is no PG05IMG.zip in the sd card root. Also I have tried reinstalling the recovery from the 4EXT recovery control app.
Current verson of recovery installed is 4EXT Recovery Touch v1.0.0.5 RC8.
Tried reflashing that, and also the RC9 test build that is out right now.
Still no go on getting into the recovery.
Thanks.
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
santod040 said:
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
Click to expand...
Click to collapse
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
santod040 said:
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
Click to expand...
Click to collapse
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Edit: I confirmed his hboot is 6.04.1002. same as mine
JM1084 said:
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Click to expand...
Click to collapse
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
Alrighty, I will give that a shot. I am at work right now and am about to head out of town so I will be unable to try it until sunday. I'll post the results here asap. Thanks again!
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
zomgalama said:
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
What is your h boot version?
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
No Go, my tbolt will not mount in Win7, it just says the device has malfunctioned. Rebooting into the bootloader with USB in will not show anything in Windows, even in fastboot. It makes the device connection sound but no devices show up. Running the CMD file in the zip you linked does nothing, I'm at 10 minutes now where it just says "Waiting for device". Is my device just done for?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
coltspackers said:
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
Click to expand...
Click to collapse
Thanks for the info, but this didn't work either. I'm also on 6.04.1002 and rooted mine a week after the T-Bolt shipped manually via adb.
This happened about a month ago also, and I thought it was ext4 but managed to get an older TWRP recovery to work after working on it for about a day and a half without a working phone. At least I have a working phone at this point.
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
allo_87 said:
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
Click to expand...
Click to collapse
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
Excellent advice, thanks man.
Sent from my ADR6400L using Tapatalk 2
My thunderbolt's recovery spin mysteriously started working again yesterday, not sure why.
Doesn't matter though since I switched carriers now:/
Sent from my Sprint LG Optimus G
Still nothing for me. Worse yet is the fact that I can't adb because my usb has not worked properly since "the soup incident"
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
After going over the issue with Max and trying several fixes he suggested (he even made me an app that would format my cache), it seems I either need to obtain an RUU and flash the stock software/recovery back on and re-root or try flashing an updated hboot that already has s-off. The thinking is that it is my hboot that is causing the issue. Does anyone know what files I need? I have a couple of things to try at home to see if I can get my usb working again, if not, anything I do will have to be a flashable zip from the bootloader. Thanks!
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Seleren said:
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Click to expand...
Click to collapse
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Lucky Thirteen said:
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
Click to expand...
Click to collapse
I have the International model.
jbharbin said:
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Click to expand...
Click to collapse
Tried that already, nothing changed at all, TWRP logo shows up and then the phone reboots to ROM. CWM works partially as I said, it reboots when I tell it do do anything (backup/wipe/flash) and the phone is unaffected.
Bump. Help please, I tried flashing another kernel but that didn't help. I can't even wipe or flash another ROM in CWM.
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Try redownloading the recovery and rewriting it. It may be a bad download.
Sent from my One X+ using xda premium
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Flash the kernel and then the recovery with fastboot and see what happens.
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
@Seleren I would be interested to know if the above worked for you? Also useful if anyone else gets this problem
Lucky Thirteen said:
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
Click to expand...
Click to collapse
I've already tried that numerous times, I can get to erasing cache etc but once I try to boot into the recovery ... I'm done. TWRP won't boot even after erasing cache. CWM fails at wiping/backuping/flashing and just reboots without any notice at all. I'm really out of ideas now.
Sorry for a bit late answer.
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
Seleren said:
Hello there,
... A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery....
Click to expand...
Click to collapse
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Lucky Thirteen said:
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Click to expand...
Click to collapse
Yes, I am correctly rooted, I've rooted numerous phones, I unlocked using the official HTC method. I could say I'm not a complete noob to Android. I wouldn't even post here if I didn't try all the standard procedures.
I flashed the Non-touch CWM yesterday and nothing changed (not that I expected it to). I decided I'll try flashing the bootloader in the end but I have to back up my whole SDCard before that ...
Bump.
SALVATION
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
hukel56 said:
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
Click to expand...
Click to collapse
wut?! TWRP = Recovery
boot.img = KERNEL
Seleren said:
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Click to expand...
Click to collapse
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Lloir said:
wut?! TWRP = Recovery
boot.img = KERNEL
Click to expand...
Click to collapse
Yea idk. But this happens
Lloir said:
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Click to expand...
Click to collapse
I wish that was the problem, I tried quite a few versions, including the one from ALL IN ONE toolkit, an older version that previously worked, the latest version and the ViperX version. Trust me, that was not the problem.
hukel56 said:
Yea idk. But this happens
Click to expand...
Click to collapse
What Lloir meant to say was that the boot.img has nothing to do with the recovery, so flashing a boot.img will NOT change your recovery to so-said TWRP.
TWRP is being flashed by a different command namely 'flash recovery' instead of 'flash boot' like previously mentioned boot.img
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2252959. This is a stock rooted rom for ATT. If you download and flash this instead of the super user tool, you're done. (This rom includes super user) Or you can download a custom rom such as this one: http://forum.xda-developers.com/showthread.php?t=2183023
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
I feel like this title should be changed to clarify that it's unlocking the bootloader, not the SIM lock.
Just wanted to say this tutorial was 100% dead on and what I used to unlock bootloader and root/rom my One.
Oddity - Did everything, I've got root but I -AM- out of the woods. Was installing bulletproof mod through recovery but it kept failing due to missing a MD5 file or something -- Trying to work that out through that thread atm but anyway, rebooted the phone a couple of times now and I still have root, Tit back up works OR are we talking about things like CPU clocking won't work since it can't rewrite?
Sticking this.
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Does anyone know if this will work on the Rogers HTC One?
Thank you. Followed this last night. Worked flawlessly. The only thing that threw me was rebooting into recovery. It took maybe 3 or 4 reboots for it to say "TAMPERED" at the top. When it didn't say tampered, it would not boot to recovery.
TELUS?
DannySmurf said:
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Click to expand...
Click to collapse
Did you happen do run this tutorial on a TELUS device?
Viceroy_N said:
Does anyone know if this will work on the Rogers HTC One?
Click to expand...
Click to collapse
Yes it does. I have a Rogers phone, and it worked perfectly.
richnanaimo said:
Did you happen do run this tutorial on a TELUS device?
Click to expand...
Click to collapse
No, I have a Rogers device. But the procedure should not be any different.
followed step by step and got an error that says submitted token wrong length
I'm on ubuntu 13.04 and I get stuck at getting the token. I type in fastboot oem get unlock_identifier_token and it says waiting for device. Tried it with sudo and it says error and sudo ./fastboot and it says no such command.
Sent from my HTC One using xda app-developers app
Having a really odd problem. I flash the twrp recovery per instructions. I try to reboot to recovery and it seems to try and then, blam, the att boot.
I have tried this from the bootloader, selecting Recovery, as well as from a booted stated using "adb reboot recovery".
Any hints for me? I originally had a silver One and today got my Black One replacement,. Had no issues on the original one. Hmm. Guess I will try CWM.
FYI: Yes I unlocked the bootloader and it says Unlocked in there
-I also notice that I seem to go right into fastboot, when I boot the bootloader. Now, I believe that is normal if you have the usb cable attached, but this happens regardless.
-flashed stock recovery back and can get into it. trying twrp again, renaming the file to "recovery.img" just because...and it worked on that stock recovery file
-Also, very hard to get into bootloader from powered off state. I may flash RUU_M7_UL_JB_50_Cingular and see if it helps me.
OK, maybe it is the phone or ATT has done something screwy on the latest. I can not even get the RUU install to pass inspection. Wants me to check the connection. I know all my stuff is in order, as I did this all on the previous one. grrr
-Just noticed mine does say Unlocked but it does not say Tampered.
-Crazy. I decided to get a new Unlock token and redo the unlock with it. Now, the bootloader finally says Tampered and I got into TWRP. I have no idea why, since I would think that if the original Unlock token was incorrect, it would not have unlocked the phone.
So, rather than providing worthwhile information for anyone else having problems, I think this post is probably deletable and that is fine by me should the powers so decide.
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
tacotino said:
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot oem lock
but, it will say relocked. nobody cares or seems to check. also, it will say tampered until you restore a stock ruu to flash. I used RUU_M7_UL_JB_50_Cingular.exe for mine when switching from silver to black. it is the right one for att. sorry, don't have the link to the download anymore.
great writeup! quick comment though, just helped my brother unlock his phone. i had a similar issue to @Barsky above so I decided to try to reflash the recovery. The first time I used the line fastboot erase cache after flashing the recovery and I think that's what caused it to not boot into recovery. The second time I flashed TWRP, I didn't enter that line and voila it worked on the first try!
can anyone post a mirror of the dev host files? devhost seems to be down.
nice...
help please
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
mbroch89 said:
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
Click to expand...
Click to collapse
I think the last bit was your problem. You can't factory reset from bootloader. Try to push twrp again in fastboot then load/flash clean romantic, then boot up. It already has root so you don't need to push su.
Sent from my HTC One X using xda app-developers app
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Hello,
It can get a bit confusing sometimes and people generally expect you to just know lol.
You've not missed a step. Getting into recovery is irritating lol. For as long as I've had it if booted into recovery from the power menu lol xD.
Reboot the Google Nexus 9 by holding the Power and the Volume Down buttons at the same time and wait until the tablet display shows a Google splash screen before releasing the buttons.
If you get a android with an exclamation mark then you've made a boo boo. Dw, even us pros muck up ;]
Go back to your fastboot. Flash twrp like you do. But this time once you've flashed it type
Code:
fastboot boot recovery twrp.img
That should boot your device into recovery after flashing it.
There it should be stuck on there nicely of it takes a while Dw. That's just the fun of owning a N9 lol. That should Do it .
Happy Flashing.
Give us a Thanka if I helped
ChrispyChris said:
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Click to expand...
Click to collapse
If you installed TWRP using
Code:
fastboot flash recovery twrp.img
The only ways I know to get into recovery are to reboot to recovery from the Power menu of your ROM
OR
Boot to fastboot, select HBOOT, then select Recovery. If TWRP is installed as your recovery this will boot TWRP. If it goes to the dead droid screen then you need to install TWRP properly, using the fastboot flash command above.
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Mephisto_POA said:
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Click to expand...
Click to collapse
Are you using the newest TWRP? 3.1.0.0? It's not working for me either, can't boot to recovery. Use 3.0.2.2 or whatever the last version was
I used the 3.1.0.0
the trick was, after installing it, reboot straight back into recovery, so it doesn't get overwritten