Here's some phone history:
Factory S-Off
Flashed TWRP and permaroot here
Flashed ViperLTE 1.0.0
Ran that for a while, then the RUU came out.
Flashed the RUU.
Unlock comes along, so I unlocked it. Then I flashed ViperLTE 2.0.0, and had the sync and phone process issue so I relocked and changed the CID back.
Been running great up until today.
So I go to unlock my screen to reply to a text, and the LED isn't flashing and the touch seemed unresponsive. So I reboot to hboot, and it tells me "battery low replace battery" then "press power to continue" or something along those lines.
I went into recovery and nothing works, no touch, no LEDs, I just see the recovery.
At this point I got scared. Battery pull, reboot. Boots up into ROM, but no touch. I get texts, email updates, etc in the statusbar showing but when I tried calling the phone, the process stopped and everything looked frozen in the background.
Reboot into recovery, and while sitting there plugged in the battery DROPS
So I turned the phone completely off for an hour, still no charging.
Booted up into the ROM, and as I'm sitting here the battery is charging again.
Heres my post in the viper thread:
jtdogblue said:
It's been plugged in for a while now and no change in the indicated charge in recovery or once booted. Should I go ahead and try flashing the recovery?
EDIT: The phone's been off completely and wasn't charging, as it's sitting in recovery the battery level is.... dropping?
e:\android>fastboot flash recovery recovery.img
sending 'recovery' (9820 KB)...
OKAY [ 1.107s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.144s
e:\android>
e:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.15.0000
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT26JS309742
(bootloader) imei: 990000641796059
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3690mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3321eb88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.082s
Edit: I booted up and the battery is charging again.
Click to expand...
Click to collapse
So, that's where I'm at. Just figured I'd start a new thread instead of spamming the viper one.
Out of curiosity, if you were already s-off, why did you run the Fake CID unlock? With s-off, you should be able to push whatever you want onto the phone, including recovery and ROMs.
You may need to re-lock the bootloader and use the RUU to restore your phone to "factory" (with s-off) and start over. However, I do not know if the latest RUU will affect your s-off status, though, so proceed with great caution. Maybe andybones can confirm if the latest RUU has any negative effect on s-off.
junkmail9 said:
Out of curiosity, if you were already s-off, why did you run the Fake CID unlock? With s-off, you should be able to push whatever you want onto the phone, including recovery and ROMs.
You may need to re-lock the bootloader and use the RUU to restore your phone to "factory" (with s-off) and start over. However, I do not know if the latest RUU will affect your s-off status, though, so proceed with great caution. Maybe andybones can confirm if the latest RUU has any negative effect on s-off.
Click to expand...
Click to collapse
I keep asking myself the same question. The ruu.exe isn't working, it does absolutely nothing for me, so I flashed the individual things through hboot the first time didnt effect soff
jtdogblue said:
I keep asking myself the same question. The ruu.exe isn't working, it does absolutely nothing for me, so I flashed the individual things through hboot the first time didnt effect soff
Click to expand...
Click to collapse
since you decided to do the htc dev-unlock (which idk why, since u were s-off)
in order for you to run an RUU in bootloader, you need to re-lock the bootloader..
here's mine
C:\apktool>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.1111
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-75a5dc7e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
C:\apktool>
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
also you have to run a command to turn it back to S-ON, other than that it's perm.
andybones said:
since you decided to do the htc dev-unlock (which idk why, since u were s-off)
in order for you to run an RUU in bootloader, you need to re-lock the bootloader..
here's mine
C:\apktool>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.1111
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-75a5dc7e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
C:\apktool>
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
also you have to run a command to turn it back to S-ON, other than that it's perm.
Click to expand...
Click to collapse
I left the bootloader relocked. The RUU isn't working. It gets all the way through loading the installshield wizzard then just quits.
I'm about to spike this phone into the ground. $250 out the freaking window
jtdogblue said:
I left the bootloader relocked. The RUU isn't working. It gets all the way through loading the installshield wizzard then just quits.
I'm about to spike this phone into the ground. $250 out the freaking window
Click to expand...
Click to collapse
sounds to me like the bootloader is unlocked man.
andybones said:
sounds to me like the bootloader is unlocked man.
Click to expand...
Click to collapse
It says *RELOCKED* at the top. Also, the ruu doesnt let me click anything, just loads up then quits
PLEASE stay with me. I'm about to die here pressing refresh every 5 seconds
jtdogblue said:
It says *RELOCKED* at the top. Also, the ruu doesnt let me click anything, just loads up then quits
PLEASE stay with me. I'm about to die here pressing refresh every 5 seconds
Click to expand...
Click to collapse
INSTRUCTIONS
1) Download this - MD5 = 55023CC10B59FDEC0AAA6695C4CF83FB
2) rename to PJ53IMG.zip (make sure it's not named PJ53IMG.zip.zip...)
3) put the PJ53IMG.zip on the root of your SD-Card. (not in any folders)
4) reboot to bootloader
5) let the phone do its magic
6) enjoy Sense 4.1
I am VERY appreciative of any help you provide, I didn't mean to come across as pushy in any way. Thank you again
jtdogblue said:
I am VERY appreciative of any help you provide, I didn't mean to come across as pushy in any way. Sorry
Click to expand...
Click to collapse
Thank you. I appreciate that.
Please try this
INSTRUCTIONS
1) Download this - MD5 = 55023CC10B59FDEC0AAA6695C4CF83FB
2) rename to PJ53IMG.zip (make sure it's not named PJ53IMG.zip.zip...)
3) put the PJ53IMG.zip on the root of your SD-Card. (not in any folders)
4) reboot to bootloader
5) let the phone do its magic
6) enjoy Sense 4.1
---------- Post added at 06:34 PM ---------- Previous post was at 06:14 PM ----------
Once you are S-OFF it is permanent. Only way to get back to S-ON is with a fastboot command.
andybones said:
Thank you. I appreciate that.
Please try this
INSTRUCTIONS
1) Download this - MD5 = 55023CC10B59FDEC0AAA6695C4CF83FB
2) rename to PJ53IMG.zip (make sure it's not named PJ53IMG.zip.zip...)
3) put the PJ53IMG.zip on the root of your SD-Card. (not in any folders)
4) reboot to bootloader
5) let the phone do its magic
6) enjoy Sense 4.1
---------- Post added at 06:34 PM ---------- Previous post was at 06:14 PM ----------
Once you are S-OFF it is permanent. Only way to get back to S-ON is with a fastboot command.
Click to expand...
Click to collapse
Didnt work
jtdogblue said:
Didnt work
Click to expand...
Click to collapse
wow really
I'm thinking by unlocking bootloader you may have messed something up?
have you tried setting the phone back to the original CID?
andybones said:
wow really
I'm thinking by unlocking bootloader you may have messed something up?
have you tried setting the phone back to the original CID?
Click to expand...
Click to collapse
Yes, I had to set it to the original CID to get it re locked.
e:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.15.0000
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT26JS309742
(bootloader) imei: 990000641796059
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3639mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3321eb88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
e:\android>
jtdogblue said:
Yes, I had to set it to the original CID to get it re locked.
e:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.15.0000
(bootloader) version-baseband: 1.53.06.0919
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.605.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT26JS309742
(bootloader) imei: 990000641796059
(bootloader) product: fireball
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ5310000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3639mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3321eb88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
e:\android>
Click to expand...
Click to collapse
only other thing I can think of is to try installing RUU using fastboot command
fastboot oem rebootRUU
also just for the heck of it (yes i know you are locked) but just for ****s and gigs, do a relock again, make sure the phone reboots, then try fastboot oem rebootRUU
andybones said:
only other thing I can think of is to try installing RUU using fastboot command
fastboot oem rebootRUU
also just for the heck of it (yes i know you are locked) but just for ****s and gigs, do a relock again, make sure the phone reboots, then try fastboot oem rebootRUU
Click to expand...
Click to collapse
I ran the fastboot oem rebootRUU and now its stuck on the darker black and silver htc screen...
jtdogblue said:
I ran the fastboot oem rebootRUU and now its stuck on the darker black and silver htc screen...
Click to expand...
Click to collapse
I think that is good..
should mean it's installing RUU..
andybones said:
I think that is good..
should mean it's installing RUU..
Click to expand...
Click to collapse
Well the first time I did it, it showed everything being done in hboot. I'll let it sit an hour or so and report back.
ok with it in the black screen, put the PJ53IMG.zip in your sdk folder and then do this command
fastboot flash zip PJ53IMG.zip
*you should now see it flashing things. do not for any reason interupt it during this process. when its finished:
fastboot reboot-bootloader
---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------
jtdogblue said:
Well the first time I did it, it showed everything being done in hboot. I'll let it sit an hour or so and report back.
Click to expand...
Click to collapse
no need for that..
if it's installing in hboot ur good to go.
andybones said:
ok with it in the black screen, put the PJ53IMG.zip in your sdk folder and then do this command
fastboot flash zip PJ53IMG.zip
*you should now see it flashing things. do not for any reason interupt it during this process. when its finished:
fastboot reboot-bootloader
---------- Post added at 07:30 PM ---------- Previous post was at 07:29 PM ----------
no need for that..
if it's installing in hboot ur good to go.
Click to expand...
Click to collapse
NOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
e:\android>fastboot flash zip PJ53IMG.zip
sending 'zip' (583416 KB)...
OKAY [ 19.895s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 23.620s
jtdogblue said:
NOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
e:\android>fastboot flash zip PJ53IMG.zip
sending 'zip' (583416 KB)...
OKAY [ 19.895s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 23.620s
Click to expand...
Click to collapse
whoa, you did this when in the rebootRUU mode right?
the black with silver
Related
On new year's eve, i decided to upgrade GB to HC to have a taste of the new OS.
but then tragedy comes. after downloaded OTA updates and reboot my view, I stuck on the HTC screen till now.
Yet I can boot into bootloader, and now my devices is S-ON with HBOOT 1.130000, I have tried to unlock the bootloader via HTCDEV website, but when I type: fastboot oem get_identifier_token, it give me the error:
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
and when I type--adb devices, it shows--list of devices attached.
I did sucessfully installed htc driver and uninstalled htc sync and even reinstalled win 7 system. but it looks like adb can't identify my view correctly.
and also I tried to unlock my tablet via http://revolutionary.io/, but the tool-revolutionary.exe always shows--waiting for devices.
I have also tried to run RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed, and all my effort was in vain.
So this is the situation. besides,I bought this tablet from local retailer in China, there is no way to turn to HTC for help.
I am looking forward someone here may give me some help.
Thank you in advanced!
Send PM to Globaton.
Hopefully he will be able to help you.
boot the view to fastboot mode and give me a 'fastboot getvar all'
Globatron,thank you for your help.
here is the result:
D:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 1.05.01.1006_3
(bootloader) version-cpld: None
(bootloader) version-microp: 0656
(bootloader) version-main: 2.23.651.1
(bootloader) serialno: HT17EHY01305
(bootloader) imei: 355195000000017
(bootloader) product: express
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4120000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3477mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 37bb05a2
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s
ok, you're in an odd state here, you're caught in no man's land between gingerbread and honeycomb.
download this: http://www.multiupload.com/GAZ67V0VY1
flash it as follows:
boot the view to fastboot mode
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot-bootloader
It won't give you a bootable system, but it will allow you to unlock the bootloader.
At that point you will be able to flash the honeycomb cwm, and either install a custom rom or revert to GB to S-OFF.
Globatron,I did as your instruction,and pls take a look following information of fastboot getvar all, which step should i proceed? sorry,but I am a newbie here.
D:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0005
(bootloader) version-baseband: 1.05.01.1006_3
(bootloader) version-cpld: None
(bootloader) version-microp: 0656
(bootloader) version-main: 2.23.651.1
(bootloader) serialno: HT17EHY01305
(bootloader) imei: 355195000000017
(bootloader) product: express
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4120000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3867mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f821d4db
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.015s
ok, now unlock the bootloader through htcdev.
Globatron, after unlocked bootloader via htcdev, to my surprise, without doing something else, it succssfully boot into HC,you have save my view and save me a lot of hopeless effort. If you don't mind,I will post your method to the local view forum, as far as I know,there are many people have the same problem as I am.
I really appreciate all your help. wish you have a good day!
Link not work
globatron said:
ok, you're in an odd state here, you're caught in no man's land between gingerbread and honeycomb.
download this: ww.multiupload.com/GAZ67V0VY1
flash it as follows:
boot the view to fastboot mode
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot-bootloader
It won't give you a bootable system, but it will allow you to unlock the bootloader.
At that point you will be able to flash the honeycomb cwm, and either install a custom rom or revert to GB to S-OFF.
Click to expand...
Click to collapse
Hello! I have the same situation here, but this link to Multiupload not work now. Can you upload this file to another resourse?
Or send to my mail?
Thank you!
Anybody home?
STILL No any answer and link to multiupload not work.
I think you will find useful files here
http://forum.xda-developers.com/showthread.php?t=1409306
No success
Thanks
But this solution don't work for me. I renamed RUU_Express_B02_RAW.zip to flash.zip
But when I'm trying to flash - always get an error:
C:\sdk\tools>fastboot flash zip flash.zip
sending 'zip' (681830 KB)...
OKAY [ 82.609s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 167.563s
The same situation occures whyle trying to flash by ARUWizard.exe:
Updating signature................. ERROR(132)SIGNATURE ERROR
THe ROM Updat Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Just for incase sending the fastboot getvar all info:
C:\sdk\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 1.05.11.0531
(bootloader) version-cpld: None
(bootloader) version-microp: 0656
(bootloader) version-main: 2.23.651.1
(bootloader) serialno: HT17JHY00252
(bootloader) imei: 355195000000017
(bootloader) product: express
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG4120000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3733mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 37bb05a2
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Bootloader problem
I think something wrong with the bootloader inside. How to flash the bootloader to repair it?
Hi
I have the same issue with diferent bootlader info ( iwas in 1.13.0000 before following the procedure) ,trying to downgrade my HTC Flyer 3g Honercomb to Gingerbread and following all steps to make it S-OFF ( i did it using HTVdev) and loading a ROM, I stuck on the HTC screen till now.My flyer is S-ON RL with HBOOT 1.07.0000-Radio 3809.05.0401.04
using fastboot getvar all here is the info of my Flyer
INFOversion: 0.5
INFOversion-bootloader: 1.07.0000
INFOversion-baseband: 3809.05.0401.04
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 1.36.405.5
INFOserialno: HT14YT401408
INFOimei: 354672040076448
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4040mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader:
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done
I´ll aprecciate all the help,
Thanks
Need help
Very strange that Mr. finalwolf has not answered for the help asking...
...Although...that files maybe unuseless for me now...
Somebody know how to solve it 100%.
Can anybody ask Mr.globatron to visit this thread please! I hope he can help.
sorry buddie,I have been pretty busy these days. unfortunately, I have searched all my drivers but without a tarce of the file globatron provided.
Maybe you should direct PM him for the file.
Were you on the HC OTA? Did you follow the instructions on this thread?
http://forum.xda-developers.com/showthread.php?t=1414137
While trying to get S-Off on about every method I could, and reflashing RUU. I think I bricked it.
What happened was that I attempted to relock the phone. (fastboot oem lock), so I could reflash back to stock.
I'd done this already without any issues. But this time, when I did, it got stuck on booting to the boot loader. It wouldn't boot into recovery nor into the ROM. After about an hour, I finally got it to boot again. However, The only way I could do this was to flash the unlock token.
The issue here is now that when it boots into the fastboot bootloader, it shows some graphical issues and refuse to take the RUU, even when manually flashing it.
D:\One_All-In-One_Kit_v\rumrunner_HTC_0.5.0>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.035s]
finished. total time: 0.035s
D:\One_All-In-One_Kit_v\rumrunner_HTC_0.5.0>fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1180758 KB)...
OKAY [ 42.850s]
writing 'zip'...
(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
FAILED (status read failed (Too many links))
finished. total time: 143.395s
Click to expand...
Click to collapse
I'd done this previosly to revert to stock without issues, not an hour before.
fastboot getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36DW903729
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.056s
Click to expand...
Click to collapse
The phone is currently on Android 4.4.2, Sense 5.5, stock.
The RUU I'm using is:
RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2(2)
I have the OTA zip for 4.4.2, as well as the firmware.zip from it.
None of it works, and all errors up with the above error.
And no, I don't have S-Off.
Additionally, when connecting to fasboot USB, it does some screen tearing, distorting the text. I suspect that I've damaged the firmware and the phone is basically a brick. It does boot, but I cannot reflash the RUU.
I was trying to flash a new ROM and I did 'fastboot oem relock'. Now I only have access to Fastboot and the phone is currently S-ON. My CID is GOOGL001, and HTCDev's bootloader unlock doesn't work.
When I try to flash a new recovery, or bootloader, I get "signature verify fail". I don't know what else to do. I tried everything I could come up with.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
fastboot oem unlock doesn't work either.
Code:
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.543s]
finished. total time: 0.543s
Still need help.
therein2 said:
Still need help.
Click to expand...
Click to collapse
nothing can be done, your phone is bricked.
http://forum.xda-developers.com/showthread.php?t=2547894
hey you need this file it will fix any messed up htc stuck and etc its a complete rewrite Guru_Reset_M7_3.62.401.1 I used it when nothing worked for two days I had a black screen and twrp that was all and twrp wouldn't do jack adb nothing cmd nothing I meen I did everything . after this install you will have to start all over enjoy
alray said:
nothing can be done, your phone is bricked.
http://forum.xda-developers.com/showthread.php?t=2547894
Click to expand...
Click to collapse
lSuperuserl said:
hey you need this file it will fix any messed up htc stuck and etc its a complete rewrite Guru_Reset_M7_3.62.401.1 I used it when nothing worked for two days I had a black screen and twrp that was all and twrp wouldn't do jack adb nothing cmd nothing I meen I did everything . after this install you will have to start all over enjoy
Click to expand...
Click to collapse
Thanks, but this file won't help at all, this a stock guru rom for .401 version (OP is on .1700) that require a custom recovery to be flashed. Op is stuck S-ON with a locked bootloader.
** UPDATE **
Got past the stuck screen by doing this:
http://forum.xda-developers.com/showthread.php?t=2386084 Jeez.
Tried to install the .12 RUU but this failed repeatedly with an error 155. Wasn't sure if this was caused by a newer HBOOT or a different firmware. Downloaded a KK RUU from here:
http://forum.xda-developers.com/showthread.php?t=2428276
Almost back to stock. Now need to get rid of the RELOCKED message in the bootloader. Will attack that later.
I'm trying to get my phone back to stock so I can return it to AT&T due to the purple camera problem. What I was attempting to do was to restore a 4.1.2 JB nandroid backup, then install an RUU as described in post #55 here:
http://forum.xda-developers.com/showthread.php?t=2394155&page=6
I had changed the cid number back to CWS__001 and restored the nandroid backup. When I went to reboot the phone I got the AT&T animation, then the HTC One screen. This is where I'm stuck. I can't reboot into recovery or anything. Is this phone recoverable or am I SOL? Thanks for any help.
These were my settings before I started this.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*************
(bootloader) imei: ********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4103mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s
Stay s-off, lock bootloader with revone -l, then flash 3.17.502.3 RUU. That should do it.
RUU : http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
I'm also trying to revert to stock in order to return to HTC for purple tint issue. I am running an AT&T HTC One.
Originally, I followed the instructions on this thread and basically converted my phone to GPE (http://forum.xda-developers.com/showthread.php?t=2358781).
To revert to stock I followed these instructions (http://www.htc1guru.com/guides/return-stock-guide/) multiple times and kept failing getting the error 155 message. I was using the RUU.exe file. Eventually I got stuck and decided to follow another post on a different site. That post had me re-lock the bootloader and rever to S-ON. Then all went to hell. Bootloop city.
I was able to load TWRP recovery and I side-loaded a different ROM that I had from when I was first tinkering around with custom ROMs (the one described here http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/). It booted but threw tons of errors and was unusable. So, I re-unlocked my bootloader (still S-ON) and this time ran the RUU.exe (named RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe). Only instead of run through the GUI I tried to use fastboot to load the rom.zip that was extracted to a temp folder. It ran but ended up failing with the error "FAILED (status read failed (Too many links))."
I believe I then reinstalled the rom from (http://htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one/) and now it it boots and is "working."
Here is where I am at:
TAMPERED
UNLOCKED
S-ON
hboot 1.54
TWRP 2.6.3.3 recovery (note: when I boot into recovery i see a Google logo with an unlocked padlock)
this ROM, rooted: http://downloadandroidrom.com/file/HTCOne/M7/roms/Sense4.4/One_4.06.1540.2_odexed.zip
When I boot the system from power off I get the htc animation with no other warning text
If I boot the system from TWRP recovery I first get the Google logo with an unlocked padlock, followed by the htc animation with no other warning text.
I assume I need to go back to S-OFF, lock the bootloader and run an RUU, but I'm concerned about the error 155, as well as the "too many links" error.
Here is the log from the RUU.exe that fails:
Code:
<T135636><DEBUG><CMD>htc_fastboot -s H******* -d flash zip C:\Users\o****\AppData\Local\Temp\{A08E6688-8B3D-493C-BEF3-013152BF8F99}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T135636>
<T135844><DEBUG><OUT>sending 'zip'... (1029872 KB) OKAY</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>writing 'zip'... (bootloader) adopting the signature contained in this image...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) signature checking...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) rom parsing start ...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) rom parsing finish ...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) zip header checking...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>(bootloader) zip info parsing...</OUT>
</DEBUG></T135844>
<T135844><DEBUG><OUT>FAILED (status read failed (Too many links))</OUT>
</DEBUG></T135844>
<T135927><DEBUG><CMD>adb kill-server</CMD>
Code:
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
Any help would be greatly appreciated.
cschmitt said:
Stay s-off, lock bootloader with revone -l, then flash 3.17.502.3 RUU. That should do it.
Click to expand...
Click to collapse
The revone switch worked. I wasn't sure if it would since I was on 4.4.2 and what I have READ didn't really say it would work or not since it was for 4.2 ROMs. The RUU in your link just gave me the error 155, so I installed the KK RUU I linked above. Took the phone by AT&T today and got it switched out.
BTW, thanks for the NOOB link, much appreciated, since I spend hours reading through these forums.
ZBell said:
The revone switch worked. I wasn't sure if it would since I was on 4.4.2 and what I have READ didn't really say it would work or not since it was for 4.2 ROMs. The RUU in your link just gave me the error 155, so I installed the KK RUU I linked above. Took the phone by AT&T today and got it switched out.
BTW, thanks for the NOOB link, much appreciated, since I spend hours reading through these forums.
Click to expand...
Click to collapse
If you don't mind, which RUU specifically?
ocieb said:
If you don't mind, which RUU specifically?
Click to expand...
Click to collapse
this is the only kitkat RUU for AT&T
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
this is the only kitkat RUU for AT&T
Click to expand...
Click to collapse
Thanks. Do I need S-OFF to flash this RUU? I am unlocked and rooted but don't have S-OFF and it wouldn't flash. It starts sending 1/5 and then the program freezes up and windows error recovery comes up and I get a 171 error. I'm also running TWRP recovery.
ocieb said:
Thanks. Do I need S-OFF to flash this RUU? I am unlocked and rooted but don't have S-OFF and it wouldn't flash. It starts sending 1/5 and then the program freezes up and windows error recovery comes up and I get a 171 error. I'm also running TWRP recovery.
Click to expand...
Click to collapse
no you don't need s-off .. but your not the first to have an error while trying to flash it. funny it worked fine for me
clsA said:
no you don't need s-off .. but your not the first to have an error while trying to flash it. funny it worked fine for me
Click to expand...
Click to collapse
I just get an error message saying htc_fastboot.exe has stopped working.
I tried extracting the zip from a temp folder and flashing it but I get this back:
Code:
c:\HTCOne\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
In the meantime, I may have screwed myself up even more (or potentially not?).
After the above error messages, I went in search of an alternative method to get myself up and running again. I followed the instructions by OP in this post http://forum.xda-developers.com/showthread.php?t=2283112 and they "worked." However, when the phone boots my touchscreen is unresponsive. I no longer am lock and I have S-ON. Rest of the info should be below.
If you see my post above, I am coming from GPE. Could the baseband/radio be causing this issue?
In the bootloader I see
TAMPERED
RELOCKED
Here is my getvar dump
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
I'm just trying to get to a point where I can send this back to HTC and get my purple tint issue fixed. Any help would be greatly appreciated!
ocieb said:
I just get an error message saying htc_fastboot.exe has stopped working.
I tried extracting the zip from a temp folder and flashing it but I get this back:
Code:
c:\HTCOne\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
Invalid sparse file format at header magi
In the meantime, I may have screwed myself up even more (or potentially not?).
After the above error messages, I went in search of an alternative method to get myself up and running again. I followed the instructions by OP in this post http://forum.xda-developers.com/showthread.php?t=2283112 and they "worked." However, when the phone boots my touchscreen is unresponsive. I no longer am lock and I have S-ON. Rest of the info should be below.
If you see my post above, I am coming from GPE. Could the baseband/radio be causing this issue?
In the bootloader I see
TAMPERED
RELOCKED
Here is my getvar dump
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35GW916488
(bootloader) imei: 354439055183836
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4182mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
I'm just trying to get to a point where I can send this back to HTC and get my purple tint issue fixed. Any help would be greatly appreciated!
Click to expand...
Click to collapse
yeah I knew the rom.zip won't flash but the RUU worked ... try this RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
clsA said:
yeah I knew the rom.zip won't flash but the RUU worked ... try this RUU
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
Click to expand...
Click to collapse
Thanks, I'll try this. Should it matter that I'm relocked and S-ON?
Also, I want to run this exe while my phone is connected to my computer and un fastboot usb, correct?
---------- Post added at 07:14 PM ---------- Previous post was at 06:51 PM ----------
Hi again,
Just failed both using the exe and extracting the rom.zip file. Any advice?
I was thinking of trying to go back to full GPE and either starting over, or just sending the device in like that and keeping my fingers crossed
cschmitt said:
Stay s-off, lock bootloader with revone -l, then flash 3.17.502.3 RUU. That should do it.
RUU : http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
Click to expand...
Click to collapse
Is a locked bootloader needed to run a signed ruu.exe when S-OFF? I thought lock status didn't matter when S-OFF. Or was that to just get rid of the RELOCKED banner the OP had? I may need to run this as well, so just need to make sure. Thanks.
sharksfan7 said:
Is a locked bootloader needed to run a signed ruu.exe when S-OFF? I thought lock status didn't matter when S-OFF. Or was that to just get rid of the RELOCKED banner the OP had? I may need to run this as well, so just need to make sure. Thanks.
Click to expand...
Click to collapse
Locked bootloader is not require to RUU when s-off. OP just wanted to remove relocked.
Hello everyone,
I have a rooted, unlocked, s-on htc m8 with TWRP recovery, which I seem to have messed up pretty badly.
I was trying to follow a guide to convert my phone to GPe. Being a complete noob I stupidly overlooked the step:
"Connect your HTC One to your computer using a USB cable and copy the ROM file to your phone’s SD card root folder."
Actually I don't even know which file that would be since the zip-file I downloaded had a boot.img file but nothing with a .rom extension. Anyway I missed this step and flashed the boot.img file to my phone using fastboot
"Fastboot flash boot boot.img
fastboot reboot"
The phone got stuck in a boot loop hanging at the HTC splash. I managed to get to recovery and, after reading xda-university.com/as-a-user/how-to-recover-from-a-bootloop page I did a factory reset wiping the data cache and dalvik. Now if I try to boot it regularly it doesn't even get to the splash I just get a black screen. I can still get into the bootloader by holding power + vol up and then vol down once it reboots.
I could really use some help on this, I'm way out of my depth and the phone was a present from my gf . All I want now is to get the thing back to being a working phone.
Thanks in advance,
phb07jm said:
Hello everyone,
I have a rooted, unlocked, s-on htc m8 with TWRP recovery, which I seem to have messed up pretty badly.
I was trying to follow a guide to convert my phone to GPe. Being a complete noob I stupidly overlooked the step:
"Connect your HTC One to your computer using a USB cable and copy the ROM file to your phone’s SD card root folder."
Actually I don't even know which file that would be since the zip-file I downloaded had a boot.img file but nothing with a .rom extension. Anyway I missed this step and flashed the boot.img file to my phone using fastboot
"Fastboot flash boot boot.img
fastboot reboot"
The phone got stuck in a boot loop hanging at the HTC splash. I managed to get to recovery and, after reading xda-university.com/as-a-user/how-to-recover-from-a-bootloop page I did a factory reset wiping the data cache and dalvik. Now if I try to boot it regularly it doesn't even get to the splash I just get a black screen. I can still get into the bootloader by holding power + vol up and then vol down once it reboots.
I could really use some help on this, I'm way out of my depth and the phone was a present from my gf . All I want now is to get the thing back to being a working phone.
Thanks in advance,
Click to expand...
Click to collapse
So you have access to fastboot? Good, run this command "fastboot getvar all", remove the serial number and imei, and post the results. Good news? Running the proper RUU will fix this and only take about 15 minutes.
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
bford152 said:
So you have access to fastboot? Good, run this command "fastboot getvar all", remove the serial number and imei, and post the results. Good news? Running the proper RUU will fix his and only take about 15 minutes.
Click to expand...
Click to collapse
BTW, you have to be S-off to convert to GPe
Thanks for the speedy reply!
That is good news! This is the output from getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0
(bootloader) version-baseband: 1.24.21331
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:~~~~~~~~~~~
(bootloader) imei: ~~~~~~~~~~~
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Is it just a question of downloading the stock RUU (presumably from htc) and running it while connected via fastboot USB.
Thanks again,
phb07jm said:
Thanks for the speedy reply!
That is good news! This is the output from getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0
(bootloader) version-baseband: 1.24.21331
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:~~~~~~~~~~~
(bootloader) imei: ~~~~~~~~~~~
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Is it just a question of downloading the stock RUU (presumably from htc) and running it while connected via fastboot USB.
Thanks again,
Click to expand...
Click to collapse
Hey, just download and run this from a PC... It'll update your AT&T device (I'm assuming) to Marshmallow Unlocked/Dev Ed http://www.htc.com/us/support/htc-one-m8/news/
Edit: BTW, make sure the phone is connected to the PC in fastboot mode
That worked perfectly!
Thanks so much for getting me out of trouble, and as a bonus updated to Marshmallow.