So I was trying to flash recovery 3.0 again (i've successfully done it before) via terminal, it didn't work. Kept saying flash_image doesn't exist, or something like that. So I wrote in the cm7 thread and a guy told me to just use fastboot, which I tried by following a tutorial.
Now I tried this on two seperate computers, the first computer said access denied when I tried flashing. The second computer doesn't recognize my phone. However, the second computer is the one I used to do root and s-off with adb and I haven't changed anything on my computer relating to those files (i.e moved them or deleted them) any ideas?
Sent from my HTC Vision using Tapatalk
Palingenesis said:
So I was trying to flash recovery 3.0 again (I've successfully done it before) via terminal, it didn't work. Kept saying flash_image doesn't exist, or something like that. So I wrote in the cm7 thread and a guy told me to just use fastboot, which I tried by following a tutorial.
Now I tried this on two separate computers, the first computer said access denied when I tried flashing. The second computer doesn't recognize my phone. However, the second computer is the one I used to do root and s-off with adb and I haven't changed anything on my computer relating to those files (i.e moved them or deleted them) any ideas?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
First you need Flash_image script on your phone to use the flash_image command, if you dont have it you can go HERE to get it. Which rom are you currently on?
Second you need ENG HBoot to use fastboot. Do you have an ENG. Hboot? If you do have the ENG. Hboot your computer might see the phone as a different device when its in fastboot mode and you will have to load a separate driver for fastboot mode, this happened to me.
joemm said:
First you need Flash_image script on your phone to use the flash_image command, if you dont have it you can go HERE to get it. Which rom are you currently on?
Second you need ENG HBoot to use fastboot. Do you have an ENG. Hboot? If you do have the ENG. Hboot your computer might see the phone as a different device when its in fastboot mode and you will have to load a separate driver for fastboot mode, this happened to me.
Click to expand...
Click to collapse
Yes, unless it was erased somehow, I have flash_image. I went from CM6.1 to CM7 rc0 awhile back. Used it for a few weeks then went to try new roms. So I installed the old recovery and used virtuous sense rom. Then from there, I went to MIUI, then back to CM7. Then a new MIUI came out and I went to that and that's what I'm currently on. Also, somewhere in that time I used gingervillain 1.4 rom which also requires recovery 3.0. So I've installed it a few times before. I don't think it's the rom that's causing me problems, I tried the terminal in MIUI, CM6.1.1 and Virtuous, none work.
I do have hboot aswell. Just to be clear, since I'm not, hboot is the 'bootloader' thing, right? The menu that opens when you hold the volume and power button?
On the current computer I'm using, I get the following error:
sending 'recovery' ...FAILED (remove: not allowed)
finished. total time: 1.358s
To check if you have an ENG Hboot, first power off then hold volume down+power on , once its boots into HBoot the page with the skateboarding andriods on the bottom, the first line will say " VISION PVT ENG S-OFF" if it says this you have the ENG Hboot and your problem is gonna be your driver, but if it says "VISION PVT SHIP S-OFF" you do not have an ENG HBoot and that is why fastboot doesn't work.
Sent from my HTC Vision
Palingenesis said:
Yes, unless it was erased somehow, I have flash_image. I went from CM6.1 to CM7 rc0 awhile back. Used it for a few weeks then went to try new roms. So I installed the old recovery and used virtuous sense rom. Then from there, I went to MIUI, then back to CM7. Then a new MIUI came out and I went to that and that's what I'm currently on. Also, somewhere in that time I used gingervillain 1.4 rom which also requires recovery 3.0. So I've installed it a few times before. I don't think it's the rom that's causing me problems, I tried the terminal in MIUI, CM6.1.1 and Virtuous, none work.
I do have hboot aswell. Just to be clear, since I'm not, hboot is the 'bootloader' thing, right? The menu that opens when you hold the volume and power button?
On the current computer I'm using, I get the following error:
sending 'recovery' ...FAILED (remove: not allowed)
finished. total time: 1.358s
Click to expand...
Click to collapse
Each time you flash a new ROM, it erases your phone, so even if you had installed flash_image before, it would have gotten wiped unless the ROM you are using had it built-in. Of the ones you listed, I believe only CM and GingerVillian has it built-in (not positive though). I have no idea why flash_image didn't work for you on CM6.1.1 (are you sure you got a doesn't exist error with that instead of some syntax error), but for the other ROMs, you will need to get the binary yourself (the guide linked to earlier has it).
ianmcquinn said:
Each time you flash a new ROM, it erases your phone, so even if you had installed flash_image before, it would have gotten wiped unless the ROM you are using had it built-in. Of the ones you listed, I believe only CM and GingerVillian has it built-in (not positive though). I have no idea why flash_image didn't work for you on CM6.1.1 (are you sure you got a doesn't exist error with that instead of some syntax error), but for the other ROMs, you will need to get the binary yourself (the guide linked to earlier has it).
Click to expand...
Click to collapse
I've never had any rom wipe cwm off my phone - must be a G1 thing
Anyway, he could just use rom manager to flash it. Just rename the cwm3 recovery.img to the same name as the latest 'official' recovery.img, flash it in rom manager and he'll be done. No need for the ENG hboot at all doing it that way.
KCRic said:
I've never had any rom wipe cwm off my phone - must be a G1 thing
Click to expand...
Click to collapse
Ha, fair. To clarify, I meant that each time you flash a ROM, it wipes your system partition and ramdisk. I also assumed since he was flashing among entirely different ROMs, he was erasing his data partition as well. You are right in that flashing a new ROM should not touch your recovery, hboot, radio, etc.
Regardless, flash_image is stored on the system partition, so it would have been blown away on each ROM flash.
Thanks for all the replies. So I just rename the 3.0 recovery to "clockworkmod 2.5xxxx" and leave it on the root of my sdcard? Where do I put it?
Last night I tried following some tutorials. One tutorial showed how to put flash_image on your phone,using adb, I ended up getting an error (error reading partitions) I don't have the links handy or ideas tell you what it said to do. I followed it step-by-step. Now when I try to flash recovery with terminal on my phone, I get the same error. Thanks.
Sent from my HTC Vision using Tapatalk
Palingenesis said:
Thanks for all the replies. So I just rename the 3.0 recovery to "clockworkmod 2.5xxxx" and leave it on the root of my sdcard? Where do I put it?
Last night I tried following some tutorials. One tutorial showed how to put flash_image on your phone,using adb, I ended up getting an error (error reading partitions) I don't have the links handy or ideas tell you what it said to do. I followed it step-by-step. Now when I try to flash recovery with terminal on my phone, I get the same error. Thanks.
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Guide on flash_image (linked to earlier):
http://forum.xda-developers.com/showthread.php?t=902493
Guide to the ROM Manager/renaming file process (stickied in this forum):
http://forum.xda-developers.com/showthread.php?t=900460
ianmcquinn said:
Guide on flash_image (linked to earlier):
http://forum.xda-developers.com/showthread.php?t=902493
Guide to the ROM Manager/renaming file process (stickied in this forum):
http://forum.xda-developers.com/showthread.php?t=900460
Click to expand...
Click to collapse
Awesome, ill have a look when I get back to my computer. Thanks.
Sent from my HTC Vision using Tapatalk
ianmcquinn said:
Guide on flash_image (linked to earlier):
http://forum.xda-developers.com/showthread.php?t=902493
Guide to the ROM Manager/renaming file process (stickied in this forum):
http://forum.xda-developers.com/showthread.php?t=900460
Click to expand...
Click to collapse
So the second option worked. I didn't try the first. Thanks!
Sent from my HTC Vision using Tapatalk
Related
Ola,
I tried to use the following instructions to root my desire, which is using android 2.1 and bootloader .83.
I used the easy method in a linux live cd. from the htcdesire site.
It hung on the screen that said "Checking for root files" and stayed there for about an hour. I never got the success message.
I had the recovery manager on the phone screen, so I selected reboot, and the phone came back fine.
I tried using unrevoked again and had the same issue.
So I am not entirely sure if I am rooted or not. I am assuming not, since I do not have a superuser app in my listing of phone applications.
Anyone have a solution to this issue?
Thanks!
MW
MisterWolfe said:
Ola,
I tried to use the following instructions to root my desire, which is using android 2.1 and bootloader .83.
I used the easy method in a linux live cd. from the htcdesire site.
It hung on the screen that said "Checking for root files" and stayed there for about an hour. I never got the success message.
I had the recovery manager on the phone screen, so I selected reboot, and the phone came back fine.
I tried using unrevoked again and had the same issue.
So I am not entirely sure if I am rooted or not. I am assuming not, since I do not have a superuser app in my listing of phone applications.
Anyone have a solution to this issue?
Thanks!
MW
Click to expand...
Click to collapse
I think you missed root permissions. A 100% safe way:
Get an Ubuntu live cd (you can use any as long as sudo or su works there), extract unrevoked, then run the following commands in the terminal:
cd /path/to/unrevoked
chmod +x reflash
sudo ./reflash
If it asks you for a password, use "ubuntu" or "root". Unrevoked should start working.
This happened to me with my Desire as well. It turns out I was rooted.
Try turning your phone off, then hold the power and volume down buttons, then once you reach the boot screen, go ahead and select recovery. If you've successfully rooted your device, you should now be in whichever recovery mod you used unrEVOked to flash. For me, it was ClockWorkMod.
Go ahead and start following some custom ROM guides!
I do have the clockwork recovery mod on the phone, but when I tried to install titanium backup, it told me I do not have root permissions.
The tip with chmod'ing the flash file also did not work. I still get the same error.
Thanks
MisterWolfe said:
I do have the clockwork recovery mod on the phone, but when I tried to install titanium backup, it told me I do not have root permissions.
The tip with chmod'ing the flash file also did not work. I still get the same error.
Thanks
Click to expand...
Click to collapse
If you have clockwork mod, then flash any rooted rom from here. I recommend Pinky Desire, Neophyte mod or LeeDroid. These are my favorites, though, you can choose any you like
Sent from my HTC Desire using XDA App
K900 said:
If you have clockwork mod, then flash any rooted rom from here. I recommend Pinky Desire, Neophyte mod or LeeDroid. These are my favorites, though, you can choose any you like
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I tried what you suggested, but the install failed due to not having root permissions, which hearkens back to unrevoked not working correctly.
MisterWolfe said:
I tried what you suggested, but the install failed due to not having root permissions, which hearkens back to unrevoked not working correctly.
Click to expand...
Click to collapse
Then try running unrevoked under Linux, as I suggested in post #2
Sent from my HTC Desire using XDA App
K900 said:
Then try running unrevoked under Linux, as I suggested in post #2
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I ran it in linux the first, second, third, fourth, and fifth time I attempted to root the phone. Each time the process gets stuck on 'checking for root files', and hangs indefinitely.
Clockwork mod was installed, but the phone was not rooted.
Clockwork requires the phone to be rooted in order to flash roms.
I'll try unrevoked again tonight, but I am not expecting a different result.
Maybe this is a bug that will be dealt with in a future release.
This is very strange. If it has written ClockworkMod to your recovery partition, wether the ROM currently installed is rooted or not shouldnt have anything to say. You ARE trying to flash the zip from Clockwork Recovery by entering the bootloader when booting the phone, and not trough ROM Manager or similar? Sory for asking, but the thing some people does...
It would help to know what guide you have followed "the htcdesire site" isnæt really telling me anything.
MisterWolfe said:
I ran it in linux the first, second, third, fourth, and fifth time I attempted to root the phone. Each time the process gets stuck on 'checking for root files', and hangs indefinitely.
Clockwork mod was installed, but the phone was not rooted.
Clockwork requires the phone to be rooted in order to flash roms.
I'll try unrevoked again tonight, but I am not expecting a different result.
Maybe this is a bug that will be dealt with in a future release.
Click to expand...
Click to collapse
Have you tried re-downloading it? Maybe the files inside are corrupt
Sent from my HTC Desire using XDA App
Thanks for the assistance.
I haven't had a chance to re-do the unrevoked again yet. if it should work with clockwork on, then it is likely a file corruption issue as you mentioned. I'll try again and report back.
myhtcdesire.com/modding/how-to-root-your-desire-easily-method-1 is the rooting method I used and will try using the same method again.
Success.
Looks like it was a corrupted clockworkmod issue.
Thanks for all your help
K900 said:
I think you missed root permissions. A 100% safe way:
Get an Ubuntu live cd (you can use any as long as sudo or su works there), extract unrevoked, then run the following commands in the terminal:
cd /path/to/unrevoked
chmod +x reflash
sudo ./reflash
If it asks you for a password, use "ubuntu" or "root". Unrevoked should start working.
Click to expand...
Click to collapse
I've juste used your method and it worked, thank you very much!
Error: failed to get root. Is your firmware too new?
I am on the original HTC_Desire_Android_2.3_Upgrade rom downloaded from HTC development
I have tried the Windows method to root my phone with unrevoked.
When I run unrevoked it follows the following cycle:
unrevoked3 app: Pushing recovery
unrevoked3 app: Installing unrevoked services
Phone: Rebooting phone...
unrevoked3 app: Wait for bootloader
unrevoked3 app: Running pre-boot sequence
Phone: Reboot phone
unrevoked3 app: Waiting for reboot
Phone: Phone reboots to normal, not to bootloader. I do not know if this is correct
unrevoked3 app: Waiting for system to settle (might be a minute)
unrevoked3 app: Running root...
After awhile (on screen I have to enter pin for sim card but I do nothing)
unrevoked3 app: Error: failed to get root. Is yuor firmware too new?
Phone: Reboot phone
Could somebody tell me what is wrong and how to solve it?
jjplayground said:
I am on the original HTC_Desire_Android_2.3_Upgrade rom downloaded from HTC development
I have tried the Windows method to root my phone with unrevoked.
When I run unrevoked it follows the following cycle:
unrevoked3 app: Pushing recovery
unrevoked3 app: Installing unrevoked services
Phone: Rebooting phone...
unrevoked3 app: Wait for bootloader
unrevoked3 app: Running pre-boot sequence
Phone: Reboot phone
unrevoked3 app: Waiting for reboot
Phone: Phone reboots to normal, not to bootloader. I do not know if this is correct
unrevoked3 app: Waiting for system to settle (might be a minute)
unrevoked3 app: Running root...
After awhile (on screen I have to enter pin for sim card but I do nothing)
unrevoked3 app: Error: failed to get root. Is yuor firmware too new?
Phone: Reboot phone
Could somebody tell me what is wrong and how to solve it?
Click to expand...
Click to collapse
with the gingerbread ruu u need http://revolutionary.io/ to make it s-off and then allow root
here a complete guide http://wiki.rootzwiki.com/index.php/HTC_Desire
So first I have to s-off the device first and after that run the unrevoked app?
jjplayground said:
So first I have to s-off the device first and after that run the unrevoked app?
Click to expand...
Click to collapse
After s-off it will also install a CWM recovery, so u can simply flash from the recovery the super user zip contained in the guide above (or alternative if u want change ur rom, directly flash one of the rooted roms from the dev section )
Unrevoked is not needed anymore, run revolutionary is very simple, fast and stable
Will try that! Keep you posted.
andQlimax said:
After s-off it will also install a CWM recovery, so u can simply flash from the recovery the super user zip contained in the guide above (or alternative if u want change ur rom, directly flash one of the rooted roms from the dev section )
Unrevoked is not needed anymore, run revolutionary is very simple, fast and stable
Click to expand...
Click to collapse
Thank you it worked very well!!!!
One question left: Now I can install ClockWork again so I can download roms and install them. ClockWorks has it's own bootloader right? Will this be a problem? Do I have to flash the clockwork mod?
As far as I know ckockworkmod (cwm) does not have its own bootloader, because it's a recovery. After running revolutionary successfully, you can just boot into cwm from bootloader. Or flash every you want from fastboot.
SwiftKeyed from Oxygen with Transparent XDA App
Hi everyone, I'm hoping someone can help me out here because I've screwed up somehow and would like to un-do whatever it is I've done. I'm trying to think straight so I hope what I type out ends up making sense .
1. Right now, my phone works. I'm stuck on a rooted pre-OTA stock rom. I unrooted once, but was not able to flash the OTA update via the stock recovery. I still have a use-able phone so I'm doing better than some people in threads I've read about.
2. I tried to root it with gfree. I don't think it worked, and some errors came up during the process. I used the first method then skipped to 0.2 per the wiki. Using g-free verify tells me everything is alright. supercid, sim lock, etc.
3. I am s-off, but earlier I couldn't get gfree verify to work (my own error I'm certain) and assumed I screwed up. Rom manager and root explorer never gave me prompts for superuser permissions, but I was s-off. I didn't think I rooted correctly and used the rage against the cage method.
4. Right now, I'm apparently s-off and rooted. I can't flash any roms though. I use rom manager to flash the latest recovery, it says it works and then when I reboot to recovery it stays stuck on the HTC splash screen. Battery pull takes me back to the pre-OTA rom. Recovery only recently stopped working though.
Ultimately, I need to get recovery back somehow, and then I'd return my phone back to an unrooted state with the stock 2.2 rom since I can't seem to handle rooting to well. Since I have no clockwork mod recovery, not really sure what to do to get this process rolling. If someone can help me get recovery back, and then help me flash roms again I'd definitely appreciate it. I have noone to blame but myself here.
If it ends up mattering, I do have adb installed and can use that if need be, and like I said my phone still boots up. I don't have a brick but something crazy is going on.
tjmarchand said:
Hi everyone, I'm hoping someone can help me out here because I've screwed up somehow and would like to un-do whatever it is I've done. I'm trying to think straight so I hope what I type out ends up making sense .
1. Right now, my phone works. I'm stuck on a rooted pre-OTA stock rom. I unrooted once, but was not able to flash the OTA update via the stock recovery. I still have a use-able phone so I'm doing better than some people in threads I've read about.
2. I tried to root it with gfree. I don't think it worked, and some errors came up during the process. I used the first method then skipped to 0.2 per the wiki. Using g-free verify tells me everything is alright. supercid, sim lock, etc.
3. I am s-off, but earlier I couldn't get gfree verify to work (my own error I'm certain) and assumed I screwed up. Rom manager and root explorer never gave me prompts for superuser permissions, but I was s-off. I didn't think I rooted correctly and used the rage against the cage method.
4. Right now, I'm apparently s-off and rooted. I can't flash any roms though. I use rom manager to flash the latest recovery, it says it works and then when I reboot to recovery it stays stuck on the HTC splash screen. Battery pull takes me back to the pre-OTA rom. Recovery only recently stopped working though.
Ultimately, I need to get recovery back somehow, and then I'd return my phone back to an unrooted state with the stock 2.2 rom since I can't seem to handle rooting to well. Since I have no clockwork mod recovery, not really sure what to do to get this process rolling. If someone can help me get recovery back, and then help me flash roms again I'd definitely appreciate it. I have noone to blame but myself here.
If it ends up mattering, I do have adb installed and can use that if need be, and like I said my phone still boots up. I don't have a brick but something crazy is going on.
Click to expand...
Click to collapse
Download ClockworkMod Recovery straight from Koushik's page and put it on the root of your SD card. Open up Terminal Emulator on your phone and type in the following:
su
flash_image recovery recovery-clockwork-3.0.2.4-vision.img
reboot recovery
Click to expand...
Click to collapse
Post the results in here.
blackknightavalon said:
Download ClockworkMod Recovery straight from Koushik's page and put it on the root of your SD card. Open up Terminal Emulator on your phone and type in the following:
Post the results in here.
Click to expand...
Click to collapse
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.
tjmarchand said:
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.
Click to expand...
Click to collapse
Do you have the engineering bootloader? If not, you may have to try it with ADB.
blackknightavalon said:
Do you have the engineering bootloader? If not, you may have to try it with ADB.
Click to expand...
Click to collapse
Im fairly certain I had to flash it to root with the rage method, vol + pwr screen says "vision pvt eng s-off hboot 0.76.2000 (pc1010000)"
With adb it gives me the same error, but I used rom manager to flash 2.5.1.3 so I have a recovery again. I have one good nandroid of the rom im stuck on.
My next issue is that I tried to flash the stock rom with root from http://forum.xda-developers.com/showthread.php?t=836042 and something isn't right. I wipe data/cache and then go to install zip from sdcard (manual recovery) and select the rom. What happens after is it tells me the normal messages it gives when flashing and "welcome to vision" but when the flash is done instead of giving me the option of "reboot system now" it goes back to the install zip for sd card menu like the flash never happened (and it will not boot past the htc screen)
tjmarchand said:
Im fairly certain I had to flash it to root with the rage method, vol + pwr screen says "vision pvt eng s-off hboot 0.76.2000 (pc1010000)"
With adb it gives me the same error, but I used rom manager to flash 2.5.1.3 so I have a recovery again. I have one good nandroid of the rom im stuck on.
My next issue is that I tried to flash the stock rom with root from http://forum.xda-developers.com/showthread.php?t=836042 and something isn't right. I wipe data/cache and then go to install zip from sdcard (manual recovery) and select the rom. What happens after is it tells me the normal messages it gives when flashing and "welcome to vision" but when the flash is done instead of giving me the option of "reboot system now" it goes back to the install zip for sd card menu like the flash never happened (and it will not boot past the htc screen)
Click to expand...
Click to collapse
Maybe it's a bad recovery. You said you flashed 2.5.1.3, so ROM Manager should work. Try flashing 3.0.2.4 through there now. If not, I suggest downloading Fastboot.
tjmarchand said:
Hey thank you so much for a response! I tried this with two sd cards because I didn't have any luck. I tried that exact command and flash_image recovery /sdcard/recovery-clockwork-3.0.2.4-vision.img and each time it returns flash_image: not found
It definately is on my sd card.
Click to expand...
Click to collapse
flash_image isn't part of the stock ROM, I made a guide for using it: http://forum.xda-developers.com/showthread.php?t=902493
raitchison said:
flash_image isn't part of the stock ROM, I made a guide for using it: http://forum.xda-developers.com/showthread.php?t=902493
Click to expand...
Click to collapse
Thanks for the guide! I followed it with no issue, I rebooted into recovery; it first hung on the HTC screen, rebooted, vibrated and then booted back into the OS. So anyway, instead of 2.5.1.3, I'm on 3.0.0.5 now.
I went down to 2.5.1.3 and downloaded cm6.1 via rom manager. It told me this : E: can't open '/sdcard/..location (bad) installation aborted. tmp/recovery.log was copied to sdcard
I tried enom's froyo themed rom next, heres what recovery tells me:
Installing update...
Formatting cache
Copying files
Formatting SYSTEM
Copying files...
E Can't symlink /system/bin/su
E Failure at line 19:
symlink /system/xbin/su SYSTEM: bin/su
Installation aborted.
I also tried to download an updated superuser from the market, it says installation unsuccessful package file was not signed correctly.
Use Titanium to update your Superuser.apk
Sent from a Western Union telegram.
blackknightavalon said:
Use Titanium to update your Superuser.apk
Sent from a Western Union telegram.
Click to expand...
Click to collapse
That worked, so thank you. I ended up unrooting and putting s back on so I can retry. Now, I can't flash the OTA update via stock recovery. Any ideas for that one? Thank you so much for all the other help as well.
"E:Can't open /cache/recovery/command" -when I first enter recovery
--Install from sdcard...
Finding update pacakge...
Opening update pacakge...
Verifying update package...
E:failed to verify whole file signature
E: signature verification failed
Installation aborted. -after trying the OTA (named update.zip of course)
tjmarchand said:
That worked, so thank you. I ended up unrooting and putting s back on so I can retry. Now, I can't flash the OTA update via stock recovery. Any ideas for that one? Thank you so much for all the other help as well.
"E:Can't open /cache/recovery/command" -when I first enter recovery
--Install from sdcard...
Finding update pacakge...
Opening update pacakge...
Verifying update package...
E:failed to verify whole file signature
E: signature verification failed
Installation aborted. -after trying the OTA (named update.zip of course)
Click to expand...
Click to collapse
If this is the Gingerbread OTA, you'll need everything as stock. If it's the "OTA" with Superuser thrown in, you'll need CWM Recovery 3+ (2.5* formats the system in yaffs, 3+ formats it in EXT).
This is just the ota update with wifi calling still 2.2, Im unrooted and stock recovery again
Sent from my T-Mobile G2 using XDA Premium App
Hi guys,
After spending a couple of days on reading up, I just rooted my Desire Z. The problem is that I can't make backups using Rom Manager because Recovery from the Hboot screen won't even load, it gets stuck on the white HTC screen. Although I can open the fastboot/Hboot menu's.
So now the problem is that I'm too scared (too cautious?) to load a different ROM onto my device which was the whole point of rooting it.
The device is rooted, S-off.
Hboot 0.85.0005
Microp-0425
Radio-26.03.02.26_M
eMMC-boot
Oct 11 2010
I used the wiki method for rooting (goldcard (HTC_11), downgrade from 1.82 to 1,34, adb, gfree, Rom manager.
But before I did the above, I tried visionary to no avail (which could have caused the problem).
Should I try to up or downgrade a stock Hboot? Or is there any other way to fix a similiar issue? Might it be a better option to try the Eng Hboot, even though I don't need its functions?
The reason for not just trying a new Hboot is that the current recovery option in Hboot is not working.. Updating to a new version could perhaps ruin its entire functioning (as right now my device will still just boot into froyo 2.2, 1.32).
Any advice or help is greatly appreciated!
TL,DR:
HBoot recovery does not open (white screen hangs for an hour+). Should I try the Eng Hboot, a different stock Hboot or reflash PC10IMG.zip and count on it to work and give me a working Hboot? Rooted with wiki method, S-off. Thanks.
Do you still have the PC10IMG.zip on the root of your sdcard?
Hi! First of all, thanks for replying,
The pc10img.zip is not on my SD card any more. Nor has it been there since 1.34 booted.
Perhaps its useful to add that my hboot has had trouble loading img.zip's, after trying 10 times it took my current rom (perhaps due to the messed up hboot)
Should i put the img.zip back? Is there a possibilty of my 32GB card screwing things up? (Sorry again for asking these testable things, but I don't have a working recovery yet..)
Beat regards
theSpam said:
Do you still have the PC10IMG.zip on the root of your sdcard?
Click to expand...
Click to collapse
Hi !
Can you boot into recovery using:
Code:
adb reboot recovery
If not then your recovery is broken and not your hboot.
You could reinstall the cmw recovery using flash_image and the recovery.img in a similar procedure as described in the wiki at http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
The steps would be:
Code:
adb push flash_image /data/local/tmp/
adb shell chmod 755 /data/local/tmp/*
adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
adb shell
and the in the # shell:
Code:
# cd /data/local/tmp
# ./flash_image recovery recovery.img
# sync
This would reinstall the recovery.
Have fun - Guhl
Hi,
'adb reboot recovery' indeed made my phone get stuck on the white boot screen.
I reinstalled the recovery using the steps you gave me (thanks for quickly writing the code down btw!) which worked, but only after uninstalling CWM and rebooting. So now the recovery is reinstalled. I tested this by going into fastboot and running it - it works!
The first thing I did is run a backup of course.
But where do I go from here; first I install the clockwork rom manager from the market. But when I use the upper button (flashing), my recovery will break again. Is the manual recovery installation I just did a replacement for the rom manager flashing method and should I stay away from it?
A quick confirmation would be awesome; I do see the backup I just made in the manage and restore backups section.
Thanks for the help!
Noboo said:
Hi,
'adb reboot recovery' indeed made my phone get stuck on the white boot screen.
I reinstalled the recovery using the steps you gave me (thanks for quickly writing the code down btw!) which worked, but only after uninstalling CWM and rebooting. So now the recovery is reinstalled. I tested this by going into fastboot and running it - it works!
The first thing I did is run a backup of course.
But where do I go from here; first I install the clockwork rom manager from the market. But when I use the upper button (flashing), my recovery will break again. Is the manual recovery installation I just did a replacement for the rom manager flashing method and should I stay away from it?
A quick confirmation would be awesome; I do see the backup I just made in the manage and restore backups section.
Thanks for the help!
Click to expand...
Click to collapse
Hi !
The effect that flashing the recovery from rom manager sometimes breaks recovery is known since the first days of the G2. Sometimes one had to do it 2 or 3 times and then it worked.
The method using flash_image is a replacement for the rom manager flashing method that always works for me. So i'd always flash recoveries like this.
Have fun - Guhl
Allright sounds like I'm good to go!
Thanks again, did not expect my problems to be solved so easily
Have a nice day
Same problem, Please help
Hi,
I have this same problem on a HTC mini one 2. I was using TWRP recovery which worked at first and now wont load. I have now relocked the phone and can't even unlock it again because it gets stuck at entering recovery.
Could you give me the same steps for my phone if possible please.
Thanks in advance for any help.
I cannot upgrade to a newer version of Clockworkmod recovery !
I have tried everything, fastboot flash returns failed signature verification, rom manger also cannot update to a newer version.
Also tried Unrevoked but it fails.
the phone is rooted and I have flashed several ROMs in the past without any problem.
Any idea?
Fastboot flash doesn't return verification failed error.
You need to be s-off to change recover using fastboot. Before you do anything, read some tutorials, you need to differentiate among most basic terms.
Sent from my HTC Desire using Tapatalk
erklat said:
Fastboot flash doesn't return verification failed error.
Click to expand...
Click to collapse
It can do if you try to fastboot flash connected in hboot or are s-on
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I get this error from fastboot
< waiting for device >
sending 'recovery' (3256 KB)... OKAY [ 0.468s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.952s
I have tried to flash clockworkmod 5 and also tried the touch version, but with no luck.
Maybe the S-OFF is messed up, but only if rom manager did something wrong, because last time when I have upgraded the recovery it was from ROM Manager.
Fail on my part...
That seems like there is no device tho. My money is on broken drivers. There is a guide how to do in development so search for it as it works 100%.
unrevoked connects to phone, sends the file to phone then at the end it fails.
I have tried revolutionary for S-OFF the program connects to phone then displays the phone serial number, asks for the key then after I enter the key, the connection is lost.
So I really don't know what to do anymore, and I need a newer recovery since the one which I have does not have options to partition the SD Card and ICS is eating a lot of memory without SDExt.
The phone is ok, it's not broken, I flash every 2-3 days a newer ICS ROM and it works.
why dont you try a different recovery.i have been using ext4 recovery for a while and imo it is way better than cwm....
I use clockworkmod because I have purchased the ROM manager tool and it works with their recovery.
I finally managed to flash a newer clockworkmod recovery and very strange after reboot it has reverted back to the old 2.5.0.7 version !!! At least I was able to partition my sd-ext...
I have tried the boot CD with alpha-rev it freezes in the final stage, but after that I was able to flash the new recovery using the recovery itself, but as I said after reboot the new recovery has gone !
Now I have tried to flash again a newer recovery from ROM manager it says it finished successful, but the recovery still remains 2.5.0.7
evolution_x said:
I use clockworkmod because I have purchased the ROM manager tool and it works with their recovery.
I finally managed to flash a newer clockworkmod recovery and very strange after reboot it has reverted back to the old 2.5.0.7 version !!! At least I was able to partition my sd-ext...
I have tried the boot CD with alpha-rev it freezes in the final stage, but after that I was able to flash the new recovery using the recovery itself, but as I said after reboot the new recovery has gone !
Now I have tried to flash again a newer recovery from ROM manager it says it finished successful, but the recovery still remains 2.5.0.7
Click to expand...
Click to collapse
Because all you are doing is a fake flash. You need to flash it from fastboot in order to stick.
Ditch the Rom manager. That pos app is guilty of more usb bricks than most of us can count.
And how can I flash it from HBOOT ?
evolution_x said:
And how can I flash it from HBOOT ?
Click to expand...
Click to collapse
You need to read ADB for dummies guide to gain knowledge how to set ADB up.
Then you go into hboot by pressing vol- and power button.
Select fastboot.
Download your recovery.img and place it in the same folder your fastboot.exe is, then type in cmd:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache.
Return to hboot and boot in the recovery.
erklat said:
You need to read ADB for dummies guide to gain knowledge how to set ADB up.
Then you go into hboot by pressing vol- and power button.
Select fastboot.
Download your recovery.img and place it in the same folder your fastboot.exe is, then type in cmd:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache.
Return to hboot and boot in the recovery.
Click to expand...
Click to collapse
Erklat, thanks for this - I have the same problem.
i have finally got round to get adb, etc, working..and it kinda works, except that when flash a newer version of CWM (v5.0.2) on fastboot it still doesn't work. I tried using the Rom manager, which failed straight away, and I followed your steps above. But still didn't work.
So my story's background:
I rooted my Desire with Unrevoked so I could install ICS (sandvold) - and it has been working beautifully. But now I want to create an ext3 partition and the GParted method is far too complex for me to follow through.
CWM i have installed doens't partition, and so I though I'd update the recovery tool so I could use it to partition.
Any suggestions on what I could do?
KitkatKlub said:
Erklat, thanks for this - I have the same problem.
i have finally got round to get adb, etc, working..and it kinda works, except that when flash a newer version of CWM (v5.0.2) on fastboot it still doesn't work. I tried using the Rom manager, which failed straight away, and I followed your steps above. But still didn't work.
So my story's background:
I rooted my Desire with Unrevoked so I could install ICS (sandvold) - and it has been working beautifully. But now I want to create an ext3 partition and the GParted method is far too complex for me to follow through.
CWM i have installed doens't partition, and so I though I'd update the recovery tool so I could use it to partition.
Any suggestions on what I could do?
Click to expand...
Click to collapse
Do you get an error when you flash a new recovery via fastboot or does it say it successfully flashed the recovery.img file? If you didn't get an error, do you always go to Rom Manager to access recovery? If yes, I say ditch rom manager. Try vol down + power like on erklat's instruction, this time select Recovery. See if the recovery you flashed is booted.
If you are s-off it's better you flash 4ext recovery. It's by far the best recovery you can use for Desire.
stankyou said:
Do you get an error when you flash a new recovery via fastboot or does it say it successfully flashed the recovery.img file? If you didn't get an error, do you always go to Rom Manager to access recovery? If yes, I say ditch rom manager. Try vol down + power like on erklat's instruction, this time select Recovery. See if the recovery you flashed is booted.
If you are s-off it's better you flash 4ext recovery. It's by far the best recovery you can use for Desire.
Click to expand...
Click to collapse
Hey thanks sthankyou.
This is what i get on fastboot:
sending recovery...
OKAY
writing recovery
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.054s
I also tried flashing RA, just to see if it would work (and also heard its better). But nothing. It's quite bizarre.
My phone is not S-OFF - I used the HTC official software and I dont' think it does it - I have no problems in doing it if it will resolve this problem.
I have also tried this flashing using the terminal, Which I found in the Q&A's but i get several error messages, and then finally:
"error writing recovery: No space left on device"
So I uninstalled a couple of apps (freeing some 10mb+) but still the same issue.
As you are not s-off you can't flash recovery, get s-off and flash any you like
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App
KitkatKlub said:
I also tried flashing RA, just to see if it would work (and also heard its better). But nothing. It's quite bizarre.
Click to expand...
Click to collapse
RA has not been maintained for quite some time. 4EXT is probably the best and it's developer is very devoted to his project.
KitkatKlub said:
My phone is not S-OFF - I used the HTC official software and I dont' think it does it - I have no problems in doing it if it will resolve this problem.
Click to expand...
Click to collapse
You made your life a whole lot complicated by using that official tool.
Sent from my HTC Desire using Tapatalk
erklat said:
RA has not been maintained for quite some time. 4EXT is probably the best and it's developer is very devoted to his project.
You made your life a whole lot complicated by using that official tool.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Ah that really sucks. Will I be able to gain S-Off by using AlphaRev? Revolution doesn't work because my HBoot is 1.0.3... and thus not supported.
Once I get it to be S-Off I'll switch to 4EXT.
Thanks, for the help so far!
KitkatKlub said:
Ah that really sucks. Will I be able to gain S-Off by using AlphaRev? Revolution doesn't work because my HBoot is 1.0.3... and thus not supported.
Once I get it to be S-Off I'll switch to 4EXT.
Thanks, for the help so far!
Click to expand...
Click to collapse
theresa way to downgrade. check resources on my guide.
i had the same problem. s-off solved everything.
i had problems with s-off. i had ISC 4.0.3. and i couldn't get it to s-off and i installed some stable rom. cant remember which one, but i'm sure it was on of stable ones. and then tried to s-off again and it was over in few minutes.
and then i flashed recovery with adb
I've tried to flash a custom ROM on my DHD. Read a lot about it and tried to make it step by step but I'm already stuck at the first step because I can't unlock the bootloader. Tried through HTCDev, and with the Desire HD toolkit as well but no success. Basically I can't get the token ID in the command prompt. It either says can't find the device or telling me to wait but nothing happens. And I also couldn't find a working RUU
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0007
RADIO-26.03.02.15_M3
eMMC-boot
software no.: 2.36.405.8
Where can be the problem?
Thanks any help in advance.
You are already s-off, which means your your bootloader is already unlocked...
You may also already even have a custom recovery installed so you can flash a custom rom. boot into bootloader, wait and then select recovery.
If you don't have a recovery flash one using fastboot
And in the future, search then post over here http://forum.xda-developers.com/htc-desire-hd
I don't think it is because the ROM Manager asking me to root it for cwm
tharrha said:
I don't think it is because the ROM Manager asking me to root it for cwm
Click to expand...
Click to collapse
Ur phone is s-off so u can go ahead and flash recovery through fastboot commands, then u can flash a custom rom if u like or just root the stock rom thats already on ur phone. So what is ur main goal here? What do u want to do?
flashing a custom ROM like the KINGCOBRA DHD Sense 4.1. what made me confused that the process should be unlock bootloader - rooting - cwm on - rom on. I know that S-OFF means it's rooted but I thought I still have to put on cwm or something because I can't figure out if there is any recovery on or if it would work if something goes wrong.... or am I just over-combining things
so you say I should just factory reset, wipe everything and then flash the ROM?!?!
tharrha said:
flashing a custom ROM like the KINGCOBRA DHD Sense 4.1. what made me confused that the process should be unlock bootloader - rooting - cwm on - rom on. I know that S-OFF means it's rooted but I thought I still have to put on cwm or something because I can't figure out if there is any recovery on or if it would work if something goes wrong.... or am I just over-combining things
so you say I should just factory reset, wipe everything and then flash the ROM?!?!
Click to expand...
Click to collapse
Download this:
http://goo.im/devs/OpenRecovery/ace/openrecovery-twrp-2.6.3.0-ace.img
And put it on your C drive
Set up fastboot with this:
http://forum.xda-developers.com/showthread.php?t=2588979
Connect your phone is fastboot mode to your pc.
Open a CMD window and write the following command
fastboot flash recovery C://openrecovery-twrp-2.6.3.0-ace.img
tharrha said:
flashing a custom ROM like the KINGCOBRA DHD Sense 4.1. what made me confused that the process should be unlock bootloader - rooting - cwm on - rom on. I know that S-OFF means it's rooted but I thought I still have to put on cwm or something because I can't figure out if there is any recovery on or if it would work if something goes wrong.... or am I just over-combining things
so you say I should just factory reset, wipe everything and then flash the ROM?!?!
Click to expand...
Click to collapse
Ok so what u need to do is setup adb & fastboot on ur pc, plenty of guides here on xda. Once that is done ul need to flash 4ext recovery using fastboot commands. Click the link and download the 4ext recovery.img. 4ext recovery
Then if u managed that, to flash a rom u need to boot into recovery, go to wipe/format then format all partitions except sdcard then u can flash/install a rom.
---------- Post added at 08:16 PM ---------- Previous post was at 08:14 PM ----------
abaaaabbbb63 said:
Download this:
http://goo.im/devs/OpenRecovery/ace/openrecovery-twrp-2.6.3.0-ace.img
And put it on your C drive
Set up fastboot with this:
http://forum.xda-developers.com/showthread.php?t=2588979
Connect your phone is fastboot mode to your pc.
Open a CMD window and write the following command
fastboot flash recovery C://openrecovery-twrp-2.6.3.0-ace.img
Click to expand...
Click to collapse
hehe beat me too it :silly: u went for twrp over 4ext? tut tut
jmcclue said:
hehe beat me too it :silly: u went for twrp over 4ext? tut tut
Click to expand...
Click to collapse
Yup. I find it a bit more noob proof
abaaaabbbb63 said:
Download this:
http://goo.im/devs/OpenRecovery/ace/openrecovery-twrp-2.6.3.0-ace.img
And put it on your C drive
Set up fastboot with this:
http://forum.xda-developers.com/showthread.php?t=2588979
Connect your phone is fastboot mode to your pc.
Open a CMD window and write the following command
fastboot flash recovery C://openrecovery-twrp-2.6.3.0-ace.img
Click to expand...
Click to collapse
thanks but unfortunately a previous problem came up. in the cmd <waiting for device>, but nothing happens
tharrha said:
thanks but unfortunately a previous problem came up. in the cmd <waiting for device>, but nothing happens
Click to expand...
Click to collapse
Did you boot your phone in fastboot?
In hboot, select "fastboot".
tharrha said:
thanks but unfortunately a previous problem came up. in the cmd <waiting for device>, but nothing happens
Click to expand...
Click to collapse
did u install the drivers??
yep I've did how you've explained.... and then I tried a different usb slot aaaand it's done
now I spend the next ten minutes swearing. hope from here everything goes fine and thanks again
@tharrha have you tried searching/asking in your actual device thread as well? You're never the only person with the same error message...
We're helping here because we're nice . The instructions will be similar but things like drivers will require a device specific guide.
A few clarifications though. S-OFF does not mean you are rooted, it means that the bootloader is unlocked like we first told you.
Root is separate, any custom rom will likely already be rooted.
Flash a recovery, backup, full wipe then install the rom, thousands of guides will have told you this
EDIT: also please don't install a ROM from this forum...find one from the desire hd section....
eddiehk6 said:
@tharrha have you tried searching/asking in your actual device thread as well? You're never the only person with the same error message...
We're helping here because we're nice . The instructions will be similar but things like drivers will require a device specific guide.
A few clarifications though. S-OFF does not mean you are rooted, it means that the bootloader is unlocked like we first told you.
Root is separate, any custom rom will likely already be rooted.
Flash a recovery, backup, full wipe then install the rom, thousands of guides will have told you this
EDIT: also please don't install a ROM from this forum...find one from the desire hd section....
Click to expand...
Click to collapse
yep I'm trying to find proper description for the method. I don't wanted to post it to somewhere where I shouldn't so sorry for it.
although second look for the cmd it says writing failed <remote not allowed> (same with cwm)
really sorry for causing too much trouble but trying to follow what is written but nothing goes right. don't know what I'm doing wrong
Confused, your previous post said it's done? Thought you finally flashed the recovery. If not, what have you done?
Which guide are you following?
It's ok, you haven't posted in development section at least, however have you searched / posted in the correct desire hd forum? They will much likely have better answers...
eddiehk6 said:
Confused, your previous post said it's done? Thought you finally flashed the recovery. If not, what have you done?
Which guide are you following?
It's ok, you haven't posted in development section at least, however have you searched / posted in the correct desire hd forum? They will much likely have better answers...
Click to expand...
Click to collapse
sorry I'm confused as well.
trying to get information from here and there. the more I read the more I realize why I'm confused. some guide says I need to root some says I don't have to. why I became uncertain is because a couple of guides said to use htcdev although it seems I don't have to neither rooting. so basically if I can put a recovery on the phone then everything is fine. the phone finally being recognised but the flash failed. isn't it because my hboot is quite old (0.85.0007)?
I know it don't seems so but I'm reading constantly the forum (in the dhd forum) and following the instructions... probably just skipping something
tharrha said:
sorry I'm confused as well.
trying to get information from here and there. the more I read the more I realize why I'm confused. some guide says I need to root some says I don't have to. why I became uncertain is because a couple of guides said to use htcdev although it seems I don't have to neither rooting. so basically if I can put a recovery on the phone then everything is fine. the phone finally being recognised but the flash failed. isn't it because my hboot is quite old (0.85.0007)?
I know it don't seems so but I'm reading constantly the forum (in the dhd forum) and following the instructions... probably just skipping something
Click to expand...
Click to collapse
download the recovery.img below, put it inside the fastboot folder on ur pc that u created earlier, boot ur phone into fastboot mode and plug it into pc then open command window from inside fastboot folder (hold shift and right click, choose open cmd window) and type
fastboot flash recovery recovery.img
and see what happens
Everyone else do NOT use recovery.img below, its for the Desire HD
jmcclue said:
download the recovery.img below, put it inside the fastboot folder on ur pc that u created earlier, boot ur phone into fastboot mode and plug it into pc then open command window from inside fastboot folder (hold shift and right click, choose open cmd window) and type
fastboot flash recovery recovery.img
and see what happens
Click to expand...
Click to collapse
same
sending 'recovery' (6092 KB)...
OKAY [ 1.020s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.023s
(I give up for today. I will carry on with the possibilities in the morning)
tharrha said:
sorry I'm confused as well.
trying to get information from here and there. the more I read the more I realize why I'm confused. some guide says I need to root some says I don't have to. why I became uncertain is because a couple of guides said to use htcdev although it seems I don't have to neither rooting. so basically if I can put a recovery on the phone then everything is fine. the phone finally being recognised but the flash failed. isn't it because my hboot is quite old (0.85.0007)?
I know it don't seems so but I'm reading constantly the forum (in the dhd forum) and following the instructions... probably just skipping something
Click to expand...
Click to collapse
It's understandable you're confused to be honest, it's partly because your phone has already been tampered with and a lot of the guides start from scratch. It's already s-off, which is actually a good thing, saves you the hassle of doing this part yourself.
Root is not required to install a custom ROM, you only require a custom recovery.
You can root your existing firmware before you wipe and install a custom ROM. This will enable you to do things like install and use root apps. This may be useful if for instance you would like to backup your apps (e.g. saved games) using something like Titanium Backup, which requires root. You can then install it on the custom rom and restore all your apps (very handy). However if there are no real apps you need to transfer, not much point in rooting when your overall aim is a custom ROM.
So like I said you're s-off, among other things this enables you to flash a custom recovery. Follow the instructions as above.
Before you flash anything using fastboot, always try 'fastboot devices' to see if you get a response first, then flash the recovery.img
If you get errors, please post them exactly.
I still recommend asking in the dhd section properly, as it sounds like a driver issue.
tharrha said:
same
sending 'recovery' (6092 KB)...
OKAY [ 1.020s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.023s
(I give up for today. I will carry on with the possibilities in the morning)
Click to expand...
Click to collapse
Ok, this happened to me before with my sensation. What u need to do is try unlock the bootloader via htcdev. u should be able to get unlock code now that u have fastboot drivers installed. that was the problem before when it said waiting for device r whatever.