I think I should first tell what happend and then what I did so far.
I got the phone from HTC and got a OTA update to 1.72. For the rooting process (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) I first downgraded the phone (http://forum.xda-developers.com/showthread.php?t=886023). After the rooting process I installed the Ginger Villain 1.5 rom and everything worked fine until my phone decided to turn off one night.
What I now got is a phone which is stucked in the white screen with green HTC logo. Nothing happens even after 10, 20, 30 minutes waiting. Starting the phones bootloader works. Here are the Version information:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 20:10:38
I have no adb access. Drivers are installed and (normally) working on my 32-bit windows 7 laptop. If I enter fastboot, I can use fastboot commands.
I try to remember all things I tried recovering the phone:
1) recovery from fastboot (v1)
- phone into fastboot
- >fastboot devices --> phone shows up
- >fastboot flash recovery c:\...\recovery.img --> Error: FAILED: remote not allowed
2) recovery from fastboot (v2)
- phone into fastboot
- >fastboot devices --> phone shows up
- >fastboot erase cache--> works
- >fastboot oem rebootRUU --> now the phone tries to boot normally or just boots the normal bootloader again
- same problem as in 1)
3) recovery from fastboot (v3)
- downloaded another fastboot version form here: http://loadbalancing.modaco.com/download.php?url=paul/fastboot.zip
- tried 1) and 2) again -> same error
4) PC10IMG.zip recovery
- I downloaded the PC10IMG.zip from the downgrading process again (http://forum.xda-developers.com/showthread.php?t=905261)
- put it on the sdcard
- bootloaded reads file and processes it correctly
- nothing happend > same boot loop
5) PC10IMG.zip recovery with custom recovery.img
- took the PC10IMG.zip from downgrading
- replaced the recovery.img with a GV1.5 recovery.img from a friends Desire Z
- same as in 4)
I hope i did not forget something. Please help to recover the phone.
I am in the exact same situation. No ADB, No Recovery, fastboot but no ENG HBoot, and stuck at the HTC screen. I was hoping there was a way to flash clockworkmod recovery using a PC10IMG or something so I can run a nandroid restore and have ADB access back.
EDIT: I found a modified PC10IMG.zip that restored CWM and a stock android build. From there it was simple to get back to CM7. You can find the file in this post: http://forum.xda-developers.com/showpost.php?p=10583834&postcount=33
Thanks for your reply. I did not get it to work again. But maybe your link will help many other people.
Sent from my HTC Vision using XDA App
I have some problem . no adb, no recovery...
I had the same problem. I eventually just found a stock 2.2 PC10IMG.zip, flashed it, then rerooted, reinstalled recovery, then recovered my backup.
I have a desire hd that has decided to die, it boot only until vodafone logo and after that bootloop
S-ON
HBOOT-2.00.0027
RADIO-26.14.04.28_M
Sep 7 2011
I tried to flash a custom recovery (CWM) with fastboot so i can install the system again but i get the error:
FAILED (remote: signature verify fail)
It doesn't detect ADB ( or i don't know how to use it well ):
used adb devices -> nothing
used adb push -> nothing
used adb wati-for-device -> waits till the end of days
Tryed useing RUU -> Error at updateing signature
Tryed entering in recovery to reflash, i get a red exclamation.
Can i resurrect this phone or is it dead forever ?
You can't flash a custom recovery till its S-OFF. First S-OFF your phone and then flash a custom recovery.
It's not dead and you completely recoverable.
This post will help : http://forum.xda-developers.com/showpost.php?p=30007264&postcount=2
Read the Nood starter guide for S-OFFing your device.
if4ct0r said:
You can't flash a custom recovery till its S-OFF. First S-OFF your phone and then flash a custom recovery.
It's not dead and you completely recoverable.
This post will help : http://forum.xda-developers.com/showpost.php?p=30007264&postcount=2
Read the Nood starter guide for S-OFFing your device.
Click to expand...
Click to collapse
I cannot do the S-OFF (htcdev) when I type fastboot oem get_identifier_token it says [ERR] Command error !!!
Ok found the solution, had to update the HBOOT.
Now i have it *** UNLOCKED *** but still S-ON for the moment
Here is my phone detail:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Here is what I did:
Root with AAHK after that it reboot and stuck at white HTC screen
I boot the phone into booloader and make a factory reset, but it still stuck
I format my sdcard by a Nokia N8
Retried the first 2 steps, but still the same
Here is what I tried to do
I boot the phone into bootloader and go into fastboot, then run the correct RUU version (I see the same software version). However, it said customer error id #131. I use the this file RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed
I boot the phone into bootloader and go into fastboot, and do these step below, but it said something about "signature verification fail".
1) Download recovery above and place it in your fastboot directory
2) Boot into Hboot
3) Connect your phone to your PC
4) Select fastboot
5) Open up command prompt and CD to your Fastboot directory
6) Run the command fastboot erase cache
7) After the OK run fastboot oem rebootRUU
8) You'll see a new screen with HTC logo and a progress bar. here you need to run fastboot flash zip PD98IMG.zip
9) Once it completes (should say ok,finished, or complete) run fastboot reboot bootloader
10) Go into Recovery and flash a rom
Click to expand...
Click to collapse
Any suggestion to help me unbrick? I read somewhere about customer error id and it is related to goldcard. I am trying to borrow a card reader to do that.
cruel91 said:
Here is my phone detail:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Here is what I did:
Root with AAHK after that it reboot and stuck at white HTC screen
I boot the phone into booloader and make a factory reset, but it still stuck
I format my sdcard by a Nokia N8
Retried the first 2 steps, but still the same
Here is what I tried to do
I boot the phone into bootloader and go into fastboot, then run the correct RUU version (I see the same software version). However, it said customer error id #131. I use the this file RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed
I boot the phone into bootloader and go into fastboot, and do these step below, but it said something about "signature verification fail".
Any suggestion to help me unbrick? I read somewhere about customer error id and it is related to goldcard. I am trying to borrow a card reader to do that.
Click to expand...
Click to collapse
AAHK would have created your goldcard for you its one of the options when running, also AAHK needs to run twice, and during said runs attend to any errors or requests it makes.
As you can see in the picture the phone boots up to this screen. A friend of mine bought an HTC One on ebay and he found out it was rooted/unlocked so he went to put it back to stock and may have bricked the device while doing so.
EDIT: so I am able to use fastboot, but not adb because I can't get into Windows. Flashing the stock Verizon RUU I found still doesn't get me anywhere though.
Is there any hope for this device? Thanks in advance!
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
cmlusco said:
You have to select bootloader to get to the recovery option. What kind of computer are you using and whats it running?
Click to expand...
Click to collapse
Yea I saw that after messing around with it some more. It is Windows 7 x64.
I tried the one at the bottom of the page as I can't find one anywhere else. I also used the commands at the bottom to try and flash it.
http://www.htc1guru.com/downloads/ruu-zip-downloads/
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
cmlusco said:
When you go to device manager on your pc with the phone pluged in and in fastboot mode, does it show android phone or unknown device? Try using these drivers http://vzw1files.dyndns.org/ADB/ADB_Drivers.zip
You need a signed ruu which you can get here http://vzw1files.dyndns.org/RUUs/2....2_NV_VZW_3.71_002_release_341019_signed_2.zip
fastboot oem rebootRUU
fastboot flash zip file.zip
May fail with flush error do above command again.
fastboot reboot
Click to expand...
Click to collapse
OK cool I will try that once it downloads. It shows "My HTC" in the device manager. Also with the fastboot devices command it does give me the device ID.
EDIT: That worked! Thanks a lot for the RUU file, as I could not find that anywhere.
Hello. A friend of mine has the same problem. She tried to flash this RUU: "RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted" but the phone doesn't boot. Here is more info about the problem: http://forum.xda-developers.com/showthread.php?t=2688936
Can she flash the RUU posted here?
This is what the hboot says:
Unlocked
m7_wlv pvt ship s-off rh
cid-11111111
hboot 1.54.0000
radio 1.12.42.0906
opendsp v31.120.274.0617
os 1.10.605.10
Thank you very much.
She can, but since she is s-off, its better to flash the decrypted one. http://vzw1files.dyndns.org/RUUs/2.10.605.1/PN07IMG_M7_WL_JB_50_VZW_2.10.605.1_DECRYPT.zip
cmlusco said:
She can, but since she is s-off, its better to flash the decrypted one.
Click to expand...
Click to collapse
First, thank you very much. She changed the CID to VZW__001. That's not a problem, right?
Does the CID and MID have to be compatible with the RUU? She has this MID: PN0731000.
Downloading this RUU, will report back.
Again, thank you.
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
cmlusco said:
Yes the cid and mid need to match the ruu. What you have now are the correct ones. However 11111111 is super cid, which would have also worked.
Click to expand...
Click to collapse
Hello again. Before we try to flash the RUU, I would like to ask you the steps to do it. This is what we gonna do:
1. Download RUU
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
And that's it? Nothing else is needed, right?
EDIT: we flashed the RUU. Now the phone boots always in fastboot. No matter what option we choose, the phone does nothing and goes back to fastboot. On the bottom of hboot there is a new line in red: "Active cmdline overflow! (1073 Bytes)"
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
cmlusco said:
Ok try changing the cid back to 11111111 super cid, then run the ruu again and see what happens. Before doing both, use the cmd
fastboot erase cache
Click to expand...
Click to collapse
Hello. We just did it, and still the same problem. We were reading that some people solved this by doing a downgrade to hboot 1.44. But I don't want to make this problem worse.
You can try it, its worth a shot. Just flash an older ruu. http://vzw1files.dyndns.org/RUUs/. Dont remember which one goes with 1.44
cmlusco said:
You can try it, its worth a shot. Just flash an older ruu. Dont remember which one goes with 1.44
Click to expand...
Click to collapse
You can't be more kind. We made a downgrade, and now we can use CWM again. (We did the downgrade before reading your post, so we didn't use an older RUU) Now thinking hwat should be the next step: flashing a ROM (custom or stock, mounting a pendrive) or flashing an older RUU or anything else. Again, dude, you're awesome.
I'm stuck in a similar situation and any help would be appreciated so I don't screw this up. I can get into the bootloader but not into recovery (gets to the first TWRP screen then reboots). Safe mode works fine too.
Win7 64bit
S-off
Rooted
Stock ROM
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW-001
HBOOT-1.54.0000
RADIO-1.12.42.0731
OS-1.10.605.8
I can get into ADB. Would just like to know if I need to flash a new RUU or should I flash updated TWRP first? And the proper commands so I don't botch this.
Any help would be greatly appreciated.
Thanks
I would try reflashing twrp first. http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img
fastboot erase cache
fastboot flash recovery recovery.img
cmlusco said:
I would try reflashing twrp first.
fastboot erase cache
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Didn't work. Got to the TWRP splash screen and back into the bootloop again.
Ok then i would do an ruu. http://vzw1files.dyndns.org/RUUs/
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip (may fail with flush error, just do the cmd again)
fastboot reboot
Hi,
Similar problem here.
This is my situation:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
CID: VZW__001
MID: PN0731000
Only fastboot. Can't access to recovey (CWM). Can't access to OS, so no adb.
Every time I try to RUU it gives the "Signature verify fail" message.
So, I tried encrypted ROMs (those at vzw1files. dyndns. org), and I could go a step forward; but the flashing hungs up after giving this messages:
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
Thanks in advance, I hope I didn't screw it up.
The problem is nicouy that you are s-on, and on the newest kk firmware. An s-on phone will not allow you to "downgrade" firmware, and we do not yet have the latest ruu available, at least to my knowledge. So your kind of screwed right now untill we get our hands on a kk ruu.
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
architsheth said:
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
Click to expand...
Click to collapse
Don't ever s on again
The command is "fastboot oem rebootRUU"
Use this ruu... http://click.xda-developers.com/api...TC One | XDA Forum&txt=1.10.605.10 Signed RUU
Try It
First you need to do is s-off it and then flash the ruu that is given in #2 i used the same and i had no problems at all . I am form India as well
Unlock your bootloader later on but soff it first.
https://www.youtube.com/watch?v=e4zBk2m1FPU
architsheth said:
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
Click to expand...
Click to collapse
Here is how to fix it
Download this RUU file which matches your hboot
http://bit.ly/vzwone10
then put the file in your fastboot / adb directory, and rename it to Rom.zip
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip Rom.zip (rename file to Rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip Rom.zip
Then when it finishes, type "fastboot reboot"
Enjoy.
PS - NEVER s-on your phone. You do not to be s-on for ANYTHING. But being s-on will stop you from doing pretty much everything. The only reason to EVER revert to S-on is to send your phone in for a warranty replacement.
As soon as you finish those steps, go ahead and use rumrunner for your hboot version to get s-off again. Once you are s-off, you can take all your ota updates to get the newest firmware / stock rom, then flash a custom recovery through fastboot, and flash superuser or a custom rom from your recovery. You NEED s-off though. If you were s-off now this would be a simple fix, just flash firmware / recovery and a rom, but since you are s-on you are going to have to go to the matching stock RUU for your bootloader, and start from scratch. Hope i helped.