Related
I attempted to place a ROM on the phone using CWM recovery and something messed up. Now, I can boot into screen that says fastboot, recovery, etc. However, when I select recovery, nothing happens. Anyone point me in the right direction...im back to using my Blackberry!
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
E.Cadro said:
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
This is where I am stuck. Unfortunately, I'm not all that familiar with Fastboot. When connecting the phone to the PC with a USB, I see that the phone says Fatboot USB. From there I'm lost. I've not been able to find a guide that describes how to install a ROM using fastboot. Lots of posts says that it can be done, but none describing how its done. Anyone pointing me in the right direction?
http://forum.xda-developers.com/showthread.php?t=1754018
gunnyman said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
rpritch said:
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
Click to expand...
Click to collapse
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
rpritch said:
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
Click to expand...
Click to collapse
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
veritas2884 said:
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
Click to expand...
Click to collapse
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
E.Cadro said:
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Our devices will not boot. All we can get is either the white HTC Screen or get into the menu that allows fastboot/recover/ect...
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
c5satellite2 said:
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Recommended process for fixing strange issues like what you were experiencing. Glad it helped you guys out!
Sent from my HTC One XL using xda app-developers app
veritas2884 said:
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Click to expand...
Click to collapse
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
rpritch said:
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
Click to expand...
Click to collapse
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
veritas2884 said:
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
Click to expand...
Click to collapse
I cant seem to find a stock Rogers Ruu...will continue searching. Anyone out there have it?
http://http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Finally got it working...the above link is what worked. Here is the summary...
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!
Berserk87 said:
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Click to expand...
Click to collapse
do this:
1.Put Rogers stock zip (keep it in zip form) in your platform-tools folder (you need to download Android SDK). This is the rogers file I downloaded...http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html
2. Boot phone into fastboot (hold power button and volume down key)
3. Used command window to relock bootloader by doing the following:
use command window to get to location on your computer where you have saved SDK stuff, continue with command window to the platform-tools folder then enter the following commands:
fastboot devices <enter>
fastboot oem lock <enter>
Phone will restart and reboot into fastboot again
4. type 'fastboot oem rebootRUU'.
5. Next, make sure you have the .zip RUU file in the same folder (see step 1) and type 'fastboot flash zip XXX.zip' (replace XXX with whatever the rogers stock zip is called, I changed it to "rogersstock.zip")
Phone will reboot to a HTC screen. If you see "re-flush image immediately", repeat fastboot flash zip XXX.zip command. You may have to do this 2 or 3 times.
After doing this, I was able to download and install the Rogers firmware update
BTW...I didn't discover any of this stuff on my own...I researched a bunch of different posts and put it together. Hopefully, someone else finds have all this in one post useful.
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
slash178 said:
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
Click to expand...
Click to collapse
What you are doing wrong is flashing the recovery for the wrong phone. Any file with "enveavoru" in it is for the international (Tegra3) version. Our phone is "evita".
Only install things in our Dev forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
To see everything in an organized list, go to my index: http://forum.xda-developers.com/showthread.php?t=1671237
Also, TWRP is recommended. CWM does not officially support our device, and therefore is just a port, and buggy. TWRP officially supports our device.
im getting the same error and im using the recovery ending on evita
Rooting- error: cannot load "flashboot flash recovery r1-modaco-reco... .img"
I'm rooting my HTC One S the first time. And I was stupid and thought that HTC One X Clockworkmod flash would work.
Now I know how flashing and clockworkmod installing works but before that I accidentally flashed the One X command: "fastboot flash recovery recovery-clockwork-touch-5.8.2.7-endeavoru.img" and now when I go to recovery it gives me a red text and nothing works.
I searched everywhere for a guide to remove it and did not found. So I thought I could flash it over with an One S flash, but then when I entered the command: "fastboot flash recovery r1-modaco-recovery-clockwork-touch-ville.img" It gave me this: "error: cannot load 'recovery r1-modaco-recovery-clockwork-touch-ville.img'. My phone is connected perfectly, when I type 'fastboot devices' it shows me my phone is there.
So I think this is not a big problem for developers. Can anyone tell me what to flash or do to get rid of the One X recovery? Otherwise I just have to live with a phone with unlocked Bootloader and no access to root
Do you have the IMG I the directory from which you are running fast boot?
edscholl said:
Do you have the IMG I the directory from which you are running fast boot?
Click to expand...
Click to collapse
Ofcourse
rixrasta said:
Ofcourse
Click to expand...
Click to collapse
mabey I should just do a factory reset :/
Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
http://www.clockworkmod.com/rommanager
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--
rugmankc said:
Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--
Click to expand...
Click to collapse
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.
rixrasta said:
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.
Click to expand...
Click to collapse
Try this twrp .img
http://teamw.in/project/twrp2/100
The red text will stay till you relock, I believe, or flash stock recovery--
twrp recovery is the way to go. Me too I couldn't install the clockwork one!
rugmankc said:
Try this twrp .img
h ttp://team w. in/projec t/twrp 2/100
The red text will stay till you relock, I believe, or flash stock recovery--
Click to expand...
Click to collapse
I flashed the "openrecovery-twrp-2.2.2.0-ville.img". Didnnt change anything :/
sorry to hear that, not sure what else to do, so you still have onex recovery?
even if you run an ruu, i think you still have to flash the stock recovery first. haven't read up on that much, as never needed to run one
Don't know if trying to flash the stock recovery will help. I have the original one at home, but not sure if that is what they still call stock recovery with new ota's having come out
If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)
usaff22 said:
If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)
Click to expand...
Click to collapse
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img
the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2
stunner2002 said:
the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
fastboot ->reboot bootloader ->bootloader ->recovery. Absolutely no change, It took half a second to bring up the "HTC quietly brilliant" logo and about two seconds for the red text to appear under it. No buttons work after that and I just have to hold the power button down to shut it down.
And by bootloader is unlocked!
As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".
If this is the thing where you go int recovery for a millisecond and then back to the 'red text' screen (you have to watch carefully to notice), you should try erasing your cache in fastboot mode.
fastboot erase cache
Click to expand...
Click to collapse
-Jobo
It's gotten a little confusing and some suggestions are being repeated. I wonder if the android icon you are describing is the stock recovery symbol. At that screen have you tried to press vol+ or maybe volume-. I forget which one takes you to stock recovery. May want to check on that.
Also, have you tried typing "fastboot boot recovery" to go straight to recovery, bypassing htc restrictions
Here is very early stock recovery--not sure if it is still considered "stock" with new versions out now--I did mention that earlier--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
I did have issues fastbooting recovery before. You can as mentioned try fastboot erase cache before fastbooting recovery. And change the name of your recovery to just recovery.img before you fastboot.
I assume you have nandroid backup on phone and copies of it and sdcard backup on pc.
I think when I had issues with recovery sticking it was my N1 and I typed "fastboot erase system" first, then fastbooted recovery. Then wiped all and restored nandroid. I am not sure we can do that on the 1s with no s-off. Someone else may know.
Can you access sdcard where you could reformat it fat32 thru a windows formatter program. Of course copy all to pc first. Sometimes sdcard formats help things you wouldn't expect it to.
Some folks have reported formatting works better thru phone on the 1s, maybe because it is an internal card. I did it once and think I had to redo it thru phone. But, if it gets recovery working, no big deal.
All these are suggestions and as the devs say--at your own risk--
I thought you said you said in first post, phone works, just no root capabilty. If that is true it should be fixable--I hope.
---------- Post added at 05:06 PM ---------- Previous post was at 04:32 PM ----------
rixrasta said:
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img
Click to expand...
Click to collapse
you should also have adb.exe if you are using adb--
frdd said:
As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".
Click to expand...
Click to collapse
Okay I waited for 10 minutes, nothing happens. I've even tried to hold down all the button combinations(with the three buttons) for a few minutes.
I've tried flashing everything and fastboot boot just takes me directly to the recovery with the red text. I flashed both the recoveries in the all-in-one tool.
As I know absolutely nothing about RUU(only what the letters stand for) then I'd rather not do that because I read from some threads that RUU has quite a high chance to mess up your phone. Or if you direct me to a tutorial that u insure me that is 100% good then I could give it a go : D
[
I think I have made the same mistake of flash recovery, but I can not get into cwm recovery, I only appear for 1 second the recovery, then restarts and returns to the operating system. SD card, all changes are discarded when you restart the phone, which is also only if I try to install or remove some utility. Can not install any recovery, even if fastboot works well and looks real mind install the recovery but when I reboot, it returns to its previous behavior, with recovery not working. I tried to install the recovery in every way, from fastboot, from All in one with quickroot, but none of these operations has changed the state of the system.
Unfortunately you can not install a Stock RUU because the bootloader unlocked and the recovery is not the stock, and especially not when there is no tutorial to follow to bring this situation to the ONE S, to its original state
Hopefully someone will be able to find a solution to your and my problem.
One option you guys may need to entertain, if applicable, would be to exchange phones with Carrier. Worth a shot--
I have not heard of this exact issue, but most comments say if you can't boot to recovery you are bricked--
Has anyone tried "fastboot boot recovery" command in terminal window?
I've followed the rooting instruction for 2.20 and got confirmation that my CID is at 11111111. I got an unlock token and followed the instructions at htcdev.com I chose "unlock bootloader" and the phone rebooted. I installed a terminal app to see if I was rooted, and I'm not. No "su" command was available. So, I went through the root process again, from the beginning, generating a new code. This time, when I ran "fastboot flash unlocktoken Unlock_code.bin" I got confirmation in the command prompt that it worked, but nothing happened on my phone, i.e. there's no "Unlock bootloader?" screen. I can still use the volume rocker to highlight options, but I don't know what to do from here.
Does anyone have any ideas?
ctennenh said:
I've followed the rooting instruction for 2.20 and got confirmation that my CID is at 11111111. I got an unlock token and followed the instructions at htcdev.com I chose "unlock bootloader" and the phone rebooted. I installed a terminal app to see if I was rooted, and I'm not. No "su" command was available. So, I went through the root process again, from the beginning, generating a new code. This time, when I ran "fastboot flash unlocktoken Unlock_code.bin" I got confirmation in the command prompt that it worked, but nothing happened on my phone, i.e. there's no "Unlock bootloader?" screen. I can still use the volume rocker to highlight options, but I don't know what to do from here.
Does anyone have any ideas?
Click to expand...
Click to collapse
You need to flash a rooted Rom. you were on 2.20, it is a temp.root to change your cid so you can unlock your boot loader.
Did you flash teamwin recovery yet?
Sent from my HTC One XL using xda app-developers app
Not yet. I was following the instruction here: http://forum.xda-developers.com/showthread.php?t=1952038 and in this thread: http://forum.xda-developers.com/showthread.php?t=1954458 which say to get the unlock token and proceed to htcdev right after changing the CID. I thought that teamwin recovery got installed after that. Did I do something out of order? What should I do differently? Thanks.
ctennenh said:
Not yet. I was following the instruction here: http://forum.xda-developers.com/showthread.php?t=1952038 and in this thread: http://forum.xda-developers.com/showthread.php?t=1954458 which say to get the unlock token and proceed to htcdev right after changing the CID. I thought that teamwin recovery got installed after that. Did I do something out of order? What should I do differently? Thanks.
Click to expand...
Click to collapse
After you unlock your bootloader you need to flash TWRP from ADB, since you don't have SU installed.
You have to flash TWRP before doing anything on 2.20
Is your bootloader not unlocked? Retry it, make sure the unlock token is in the PRECISE format that they ask for
absolutelygrim said:
After you unlock your bootloader you need to flash TWRP from ADB, since you don't have SU installed.
You have to flash TWRP before doing anything on 2.20
Is your bootloader not unlocked? Retry it, make sure the unlock token is in the PRECISE format that they ask for
Click to expand...
Click to collapse
Retry what part? I'm sorry. Do you mean I should do the whole process from the start, or just part of it? It actually says "unlocked" at the top of the bootloader screen right now. Should I just go ahead and flash the TW openrecovery?
I downloaded the latest CM10 and ran fastboot on the boot.img. After flashing openrecovery should I be good to flash the ROM and gapps? Thanks for your help.
ctennenh said:
Retry what part? I'm sorry. Do you mean I should generate a new token?
Click to expand...
Click to collapse
Use the same token, but retry the process
Ok, I re-ran "fastboot flash unlocktoken Unlock_code.bin" with the same file. It still says "unlocked" at the top. Then I ran "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img". According to the instructions in the thread on installing custom ROMs I should do a "fastboot reboot" now before installing the ROM, but I don't want to reboot yet if it will undo the root.
ctennenh said:
Ok, I re-ran "fastboot flash unlocktoken Unlock_code.bin" with the same file. It still says "unlocked" at the top. Then I ran "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img". According to the instructions in the thread on installing custom ROMs I should do a "fastboot reboot" now before installing the ROM, but I don't want to reboot yet if it will undo the root.
Click to expand...
Click to collapse
go into adb and type "adb reboot recovery" if TWRP shows up, mount your SD and drag a ROM into your SD and the boot.img from the ROM, and then unmount your SD card. Full Wipe, flash the boot.img and the ROM and reboot.
you never really *had* root.
The 2.20 exploit is a temporary root to change your CID to 1111111, so you can permanently unlock your boot loader at anytime.
absolutelygrim said:
go into adb and type "adb reboot recovery" if TWRP shows up, mount your SD and drag a ROM into your SD and the boot.img from the ROM, and then unmount your SD card. Full Wipe, flash the boot.img and the ROM and reboot.
you never really *had* root.
The 2.20 exploit is a temporary root to change your CID to 1111111, so you can permanently unlock your boot loader at anytime.
Click to expand...
Click to collapse
I'm getting "error: device not found". Can I do the same thing through bootloader-recovery on the phone itself?
ctennenh said:
I'm getting "error: device not found". Can I do the same thing through bootloader-recovery on the phone itself?
Click to expand...
Click to collapse
Yea, you don't have to do it through adb. You know how to get into recovery?
Power off the phone, power it on, then continue to hold Volume Down and you will be at the hboot screen, then go to recovery from there
Edit: If you are already at the hboot screen you don't need to turn off your phone, just go to recovery
absolutelygrim said:
Yea, you don't have to do it through adb. You know how to get into recovery?
Power off the phone, power it on, then continue to hold Volume Down and you will be at the hboot screen, then go to recovery from there
Edit: If you are already at the hboot screen you don't need to turn off your phone, just go to recovery
Click to expand...
Click to collapse
Ok, so this is where I am on the instructions for installing a new ROM.
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
I've flashed twrp. Should I run "fastboot reboot" from the command line, or choose "recovery"? I appreciate your patience with me!
ctennenh said:
Ok, so this is where I am on the instructions for installing a new ROM.
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
I've flashed twrp. Should I run "fastboot reboot" from the command line, or choose "recovery"? I appreciate your patience with me!
Click to expand...
Click to collapse
Recovery. if you can't use adb reboot recovery use fastboot reboot instead and hold volume down until you get into the boot loader, then scroll down to reboot, hit the power button, scroll down to recovery and hit the power button again. That should put you in TWRP
After choosing recovery I get the HTC loading screen with "This build is for development purposes only..." It's rebooted a couple times on its own to this screen, so I'm concerned I'm on a reboot loop.
ctennenh said:
After choosing recovery I get the HTC loading screen with "This build is for development purposes only..." It's rebooted a couple times on its own to this screen, so I'm concerned I'm on a reboot loop.
Click to expand...
Click to collapse
Hold the power button and volume down until the phone turns off. When the screen turns off let go of the power button but not volume down. Continue holding volume down until you see your bootloader screen. It will say UNLOCKED at the top
edit: btw, when flashing boot.img, use the following command fastboot flash boot boot.img so put the boot.img in the folder with fasboot.exe and use that command. When it flashes, then you can flash your ROM
Sent from my HTC One XL using xda app-developers app
Awesome. So I've mounted my SD card and copied my gapps.zip, the ROM zip, and the flashed boot.img into the Download folder. Then I unmount, wipe, and flash the boot.img and the ROM?
ctennenh said:
Awesome. So I've mounted my SD card and copied my gapps.zip, the ROM zip, and the flashed boot.img into the Download folder. Then I unmount, wipe, and flash the boot.img and the ROM?
Click to expand...
Click to collapse
Unmount.
Wipe System
Factory Reset (wipes /data and /cache)
Flash your boot.img from fastboot using "fastboot flash boot boot.img"
Flash your ROM
Flash gapps
Reboot and enjoy
Gah! I've wiped and factory reset, and now it's "waiting for device" when I try to fastboot the boot.img. Is there some option I need to choose on TW recovery in order to run fastboot on the boot.img? I don't see a "flash" option anywhere, but the instruction on flashing new ROMs doesn't say what to do to actually flash something.
ctennenh said:
Gah! I've wiped and factory reset, and now it's "waiting for device" when I try to fastboot the boot.img. Is there some option I need to choose on TW recovery in order to run fastboot on the boot.img? I don't see a "flash" option anywhere, but the instruction on flashing new ROMs doesn't say what to do to actually flash something.
Click to expand...
Click to collapse
Reboot back into bootloader. and then boot into fastboot from your boot loader, then try the command again.
You are a fabulous human being. Thanks so much for being patient with me and helping me through this. It's been a lot tougher than I expected. Now to get to bed. I have to get up early in the morning
ctennenh said:
You are a fabulous human being. Thanks so much for being patient with me and helping me through this. It's been a lot tougher than I expected. Now to get to bed. I have to get up early in the morning
Click to expand...
Click to collapse
You got everything working? Enjoy your root, unlock, and ROM, and good night
Hello,
I have a big problem with my old HTC Sensation.
I tried nearly everything out of other topics, but nothing worked....
The story: Suddenly my Sensation rebooted and from then on it is stuck in an endless bootloop.
The bad thing is, that it was stock/S-ON at this moment.
Informations about the phone:
***UNLOCKED***
Pyramid PVT Ship S-ON RL
HBOOT: 1.27.0000
Radio: 11.24A.3504.31_M
-> I am able to install RUUs (3.33), but after installation i am still in the bootloop
-> I am able to unlock/relock the bootloader
-> I can install a recovery via fastboot, but can't boot into it => bootloop
Maybe you have got a hint to bring the Sensation back to life.
Thank you!
Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!
kevinspl2000 said:
Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!
Click to expand...
Click to collapse
actually he can't even boot to the recovery in order to flash any rom
so what's the point of flashing the boot.img manually?
You can use Sensation all in one kit v3 to unlock boot loader, read this thread for more detail
http://forum.xda-developers.com/showthread.php?t=1497404
after unlocking boot loader, then go to this thread to download 4EXT recovery then use kit to flash recovery, remember to download image file, not zip file
http://forum.xda-developers.com/showthread.php?t=1377759
boot to recovery, then enable smart flash and flash any cook ROM you want. Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck
stripeqn said:
Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck
Click to expand...
Click to collapse
actually first has to wipe and then enable smartflash
Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again
BrainyTheKing said:
Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again
Click to expand...
Click to collapse
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...
kevinspl2000 said:
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...
Click to expand...
Click to collapse
I erased the cache before and after flashing recovery.
No success ...
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Can you load a rom to the internal memory or on the SD card and then flash and install a new rom?
Same Here
droidmark said:
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Click to expand...
Click to collapse
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
edited to fix all my auto-correct typing mistakes.
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Click to expand...
Click to collapse
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
cntryby429 said:
edited to fix all my auto-correct typing mistakes.
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
Click to expand...
Click to collapse
I didn't use fastboot load TWRP, I used the adb method shown on TeamWin's project page for the Verizon M8:
***********
Download - ADB / Terminal method:
Download the newest .img file from here
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
***********
Thanks all for the other suggestions which I am about to attempt!
I had this happen to me on my Asus EeePad TF101. It seems that TWRP has a bug that prevents it from setting a "boot to system" flag on some devices, causing it to always boot to recovery.
The solution for the TF101 was to reinstall the stock boot image, which appears to align with the instructions already given. Good luck! I know the terrible feeling I had when this happened to my tablet...
Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
Whew! Thanks!!
Not only did that save my bacon, it had the added benefit of getting me the insecure kernel which I had forgotten about since going through the whole root/S-off/unlock bootloader/insecure kernel routine with my Droid DNA quite a while back.
Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
I was soft bricked and only able to boot into bootloader and recovery and this write up worked for me. Just wanted to say thanks.
Don't use adv/terminal way. It's writing recovery to wrong partition..
Sent from my HTC6525LVW using XDA Premium 4 mobile app
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
hanginwithdaddo said:
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
Click to expand...
Click to collapse
if you flash to anything but the recovery partition your in some trouble.
same goes for anything like this, make sure you know what that .img is and you trust it. someone could have renamed an hboot to recovery and you end up flashing an hboot to your recovery partition because someone was careless with naming of files.
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
tim.ton said:
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
Click to expand...
Click to collapse
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
additionally, since you can boot into TWRP, have you tried sideloading a rom?
(in TWRP, go to ADVANCED, click SIDELOAD... i think you need to swipe to activate... then from terminal: adb sideload nameofROM.zip)
RBThompsonV said:
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Oh yeah! Lol I knew it was something like that. Thanks!
Sent from my HTC6525LVW using Tapatalk