[Q] [RUU] Error: 152. Unable to Restore TMob One M8 - T-Mobile HTC One (M8)

Hi, thanks for reading.
I was running the latest version of CM on my One M8. Decided I wanted to revert to stock ROM to regain HTC camera and wifi calling functionality. Figured an RUU would be the easiest way.
Here's where I probably screwed up. Downloaded and ran the RUU for ver. 2.xxx from HTC. Forgot to relock bootloader, but it rebooted early back into CM no problem. Relocked bootloader. Ran again.
I should have known to pause when I saw that my version was 1.5xx but it seemed fine with updating versions as part of the process.
Then it failed again, error 152. Was able to reboot into CM again this time.
I did some googling and reading and saw one guy say that he was able to fix by simply running the RUU again once it was in the "four exclamation marks in triangles" screen, which is where I was after the next try, so I ran again. Another error 152.
So finally I realized maybe I needed the 1.5xx RUU. DL'd that, tried running, "error, wrong version." Because now it thinks my phone is on ver 2.xxx.
Now I can't get the phone to boot into recovery or into bootloader. No clue where to go from here. I'd really appreciate your help. Gosh I screwed up.
The last lines in the RUU log (1.5xx) are:
Code:
<T205408><DEBUG><OUT>Execution time is 6(s)</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T205408>
<T205408><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
and the prior try, RUU log 2.xx:
Code:
<T202916><DEBUG><OUT>(bootloader) [RUU]WP,system,37</OUT>
</DEBUG></T202916>
<T202917><DEBUG><OUT>(bootloader) [RUU]WP,system,42</OUT>
</DEBUG></T202917>
<T202939><DEBUG><OUT>(bootloader) ...... Failed</OUT>
</DEBUG></T202939>
<T202941><DEBUG><OUT>(bootloader) current_image_number=0</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>Execution time is 216(s)</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAIL51 partition update fail</OUT>
</DEBUG></T202941>
<T202941><DEBUG><OUT>FAILED (remote: 51 partition update fail)</OUT>
</DEBUG></T202941>
<T203947><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T203947>
<T203948><DEBUG><OUT />
</DEBUG></T203948>
</LOG>
Thanks.
Update 1: can recognize device using "fastboot devices" but not "adb devices." haven't tried pushing/pulling anything yet. Saw someone in another thread tried installing via command line. Not sure which .zip I should use, as there are a ton of options on XDA, or if this is what I should try next.
Update 2: there are seemingly two versions of the "four exclamation points" screen: one is dim and has the orange led showing and the other is bright without led. Bright without LED is what I got after "flashboot reboot-bootloader". Worried that the bright one may deplete battery.
3: Since I can't otherwise boot into a recovery, should I try to flash a recovery?
4: Not sure if this is useful but:
Code:
getvar version-main is indeed listed as 2.22.531.5
phone CID T-MOB010
phone MID 0P6B13000
5: Phone was S-ON. Wasn't able to get S-OFF using the free method.
6: Was reading another thread with similar error (but One X), this seemed to be useful to the one guy:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.213311491.03G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.531.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ###
(bootloader) imei: ###
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s
7: Tried to flash a stock recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery Tmo-M8-2
.22.531.5-recovery.img
target reported max download size of 1830612992 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.533s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.430s
8: Tried to create some RUU .zips per this method http://forum.xda-developers.com/showthread.php?t=2534428 but the zips say that archive is corrupted. EDIT: MD5's for the .exe's do check out.
9: Used a zip repair to repair those RUU .zip's. Noticed that their android-info files have "hbootpreupdate:12" but my phone has "hbootpreupdate:11" might that be an issue?
Sad Edit: I tried some stuff, nothing seemed to work. Freshly downloaded from an alternative mirror the 2.2xx RUU and booted into RUU via fastbooth before running it. Everything said it went perfectly "CONGRATULATIONS ROM UPDATED! Rebooting!" etc.
My phone is bricked. Never woke up from that reboot. My computer keeps trying to recognize the device via usb, but nothing.

I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?

grim489 said:
I didn't think you could use unsigned zips with s-on. Also you couldn't flash stock recovery because your boot loader was locked. If your boot loader wasn't locked it would be worked. So it doesn't show anything in fastboot anymore? Have you tried charging it them plugging back up to computer to see if fastboot will recognize it again?
Click to expand...
Click to collapse
Yeah I tried unlocking the bootloader while fastboot was still recognizable, but it wouldn't work.
Not sure about the unsigned zips thing. Would that also go for the RUU? I thought those were signed/straight from HTC.
I'll try it once more, but it should have been fully charged last time I gave it a try. Computer shows an intermittent "QHSUSB_Bulk" but not sure where to go from there. Found threads for other HTC phones and tried their methods, but it got to the point where the one guy was supposed to go through Ubuntu to manually install individual .imgs to the phone, but I think he had somehow managed to get fastboot to work.

Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.

grim489 said:
Ruu is straight from HTC they are .exe files. If it is an ruu.zip I think that only works with s-off. Hm I'm not sure what do to either, I was thinking maybe it just needed to force reboot then press power and volume down for hboot/fastboot I don't understand why it wouldn't just reboot.
Click to expand...
Click to collapse
Yeah it's especially weird because I thought with S-ON it was supposed to be hard/impossible to override ?boot.ini (not sure, don't quote me on that) anyway. But yep, won't boot at all.

Related

Hi, need some help

Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
hope the above info helps.
ajg008 said:
Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
hope the above info helps.
Click to expand...
Click to collapse
Lock your bootloader fastboot oem lock after this run RUU 1.29.401.11 as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back
thanks. Downloading now, will try when i return home from work
Thant said:
Lock your bootloader fastboot oem lock after this run as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back
Click to expand...
Click to collapse
thanks for your help that got the phone back to booting properly
I flashed it and it worked. I got myself back to the latest update. Now i tried various roms again as i'm one for experimenting but some of the newest ones dont seem to want to work.
ones i've tried>
Android_Revolution_HD-One_X_33.1
HTC_One_X_-_MaximusHD_21.0.0
OneX The Next Chapter! v1.2
but none of them worked for me.
So i went lower with
cm-10.1.3-endeavoru which worked
then updated to
cm-10.2.0-endeavoru and flashed the boot.img for it to work.
Now for the other roms, what am i missing? is it the firmware.zip? hboot level?
Am bowing down to Thant, and hoping he can tell a mere minion what he's doing wrong
I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......
Mr Hofs said:
I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......
Click to expand...
Click to collapse
the result is:
version-main: 2.17.401.2
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
http://www.persianhtc.net/index.php...Radio_2.1204.135.20_release_274900_signed.exe
Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]h*tp://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
downloading now, but need sleep now and will report back tomorrow.
thanks very much for your help.
bows to Mr Hofs
Same here.
cyanogenmod stable rom not recognising sim, and not being recognised by htc sync
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21
tekkr said:
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21
Click to expand...
Click to collapse
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install
Thant said:
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install
Click to expand...
Click to collapse
the reason i'm so frustrated is aside from the supposedly stable build of cyanogen mod i downloaded in rommanager not working, the rom doesnt recognise my sim, i dont have access to the internet, so i cant simply download a new rom to flash straight from rom manager...as well as this the wifi doesn't seem to work on this flash...and to make matters worse it's not being recognised by the drivers...i'm using htc sync manager..when i plug in the phone it will open htc sync manager but wont show that a phone is paired to my macbook
...when u say manually can i do this directly from my phone or do i need to connect it to a computer?
You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..
big noob said:
You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..
Click to expand...
Click to collapse
its not being recognised as a device since i flashed the *cyanogen mod stable rom*...i plugged it to my computer though, and put it into fastboot and it says FASTBOOT USB...the options it gives me from here are
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is guide how to use ADB on macbook:
http://forum.xda-developers.com/showthread.php?t=1917237
And then you can use fastboot commands..
Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]ht*p://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
ive tried that but keep getting signature error
ajg008 said:
ive tried that but keep getting signature error
Click to expand...
Click to collapse
Relocked the bootloader ?
Mr Hofs said:
Relocked the bootloader ?
Click to expand...
Click to collapse
yep fastboot oem lock
Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
http://forum.xda-developers.com/showthread.php?t=1957376
Mr Hofs said:
Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
[rl]htp://forum.xda-developers.com/showthread.php?t=1957376[/url]
Click to expand...
Click to collapse
i already had the ota 3.14.401 and got the firmware.zip from there.
its installed fine and i now can put most roms onto it.
:victory: thank you Mr Hofs
So i get this right in my head. The phones firmware.zip needed updated so it would update hboot and other things.
Now to flash roms is the procedure to flash the boot.img contained inside first then install the rom <----which is they way ive being doing it

Boot Loop/No Recovery

Hey all
I tried to flash over a Google Edition Rom from Cyanogen Mod by following a guide and now I am stuck on a google boot loop. Ive tried to enter recovery but it just leads me back to the google boot loop and the same happens when I try to choose factory reset. Ive tried to flash back to cyanogen and I get this error FAILED (remote: 24 parsing android-info fail) I have also tried to flash back to a sense rom and get this error FAILED (remote: 24 parsing android-info fail). So how can I either get my recovery working or getting back to Cyanogen.
Also I changed my model ID when following the guide... So Im guessing that has something to do with it but I am unsure how to change my model ID back without having access to recovery.
Heres what I got from the getvar command
(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: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA37MS910651
(bootloader) imei: 990004281021810
(bootloader) meid: 99000428102181
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4090mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
[Edit] I also tried flashing a recovery and got FAILED (remote: not allowed)
Try flashing twrp using ruu mode. http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
(may fail with flush error just do cmd again)
fastboot reboot
cmlusco said:
Try flashing twrp using ruu mode.
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
(may fail with flush error just do cmd again)
fastboot reboot
Click to expand...
Click to collapse
I do that and get FAILED (remote: 41 model id check fail)
Ok try the same thing only with this file https://www.dropbox.com/s/k52zdjv453isy0h/PN07IMG.zip
cmlusco said:
Ok try the same thing only with this file
Click to expand...
Click to collapse
I got the same FAILED (remote: 42 custom id check fail) error. I reran getvar all and saw that the cidnum changed from GOOGL001 to VZW__001
Ok try this one then https://www.dropbox.com/s/f8vtvu1ahg2uqql/PN07IMG2.zip
That worked! Thank you! I was able to sideload cyanogen back on but now it reboots after a couple minutes of being in the rom...
You may need to flash the latest firmware after changing your mid back if you havent already.
cmlusco said:
You may need to flash the latest firmware after changing your mid back if you havent already.
Click to expand...
Click to collapse
The latest stock firmware? Where would I get that
http://vzw1files.dyndns.org/FIRMWARE/3.11.605.1-NO-BootIMG_firmware.zip
You flash it in ruu mode with fastboot.
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
cmlusco said:
You flash it in ruu mode with fastboot.
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Click to expand...
Click to collapse
When I try to flash over the file in RUU it gives me this FAILED (remote: 42 custom id check fail)
(bootloader) modelid: PN0731000
(bootloader) cidnum: GOOGL001
That is what shows up when I getvar all
Change your cid back to VZW__001
fastboot oem writecid VZW__001
cmlusco said:
Change your cid back to VZW__001
fastboot oem writecid VZW__001
Click to expand...
Click to collapse
When I run that I get
(bootloader) Start Verify: 0
(bootloader) Input CID is not super CID
(bootloader) Start Verify: 0
OKAY [ 0.064s]
finished. total time: 0.064s
And when I getvar all my cid still says GOOG001
Try changing it to super cid 11111111 eight ones
That worked and so far Cyanogen is not randomly rebooting!
Thanks again! You are a life saver
cmlusco said:
http://vzw1files.dyndns.org/FIRMWARE/3.11.605.1-NO-BootIMG_firmware.zip
You flash it in ruu mode with fastboot.
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Click to expand...
Click to collapse
Hey dude why do you keep mirroring Santod's files? Just link him to the OP. The way you're doing this kind of makes it look like you made this. No credits or anything given to the dev.
disconnecktie said:
Hey dude why do you keep mirroring Santod's files? Just link him to the OP. The way you're doing this kind of makes it look like you made this. No credits or anything given to the dev.
Click to expand...
Click to collapse
Not my intention at all. 99.8% of the stuff on that site is not made by me. I do it to make it easier on my self when trying to help others, so i dont have to search all over for links. I also do it as a backup of sorts. I have seen file sharing sites go down (some permanetly), xda members leave or close threads or not maintain them once they move to a new phone or what ever. Then these critical files are lost, or a massive time consuming manhunt insues to find them. It also provides one easy organized place to find the files you need .And just to be clear, the no boot img file you are refering to was not made by santod. It was one i edited my self by pulling the boot img from a firmware zip file. Just because he did it, dosent mean someone else cant do the same. Im not here for credit, im here to help people and to get help. I give santod and any other dev whos files i mirror full credit. If its that big of a freakin deal, i will just shut the site down. I have done the same thing with several other phones i have had, and have never had an issue from anyone like i have had here in the vzw one forums.
Well on several phones I've owned it was rude to mirror devs files without their permission or without them requesting it. It is one thing for the dev to ask for a mirror and someone mirror the file for them. All the links in his op work and they aren't hard to find at all. So other than having a site for your own personal reasons there doesn't seem to be a very good reason to have mirrors of every file that has been posted to this forum.
Well your opinion is yours. I dont see what its hurting. Its not like im mirroring roms or anything. File a complaint with xda if you think its against the rules in some way. Untill they kick me off xda, you can find me here helping others in the best way i can.
cmlusco said:
Well your opinion is yours. I dont see what its hurting. File a complaint with xda if you think its against the rules in some way. Untill they kick me off xda, you can find me here helping others in the best way i can.
Click to expand...
Click to collapse
I'm not at all saying you can't help people but how much more difficult would it be to link back to the op where you got the file from? As far as I know all the links are working.

M8 frozen system

Hello all,
I have an interesting problem with an HTC M8 from AT&T. It is completely stock only with OTA updates.
"fastboot getvar all" returns this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
Now the interesting part. Every time the phone reboots, it is always in the same state as if the partitions were frozen. That is to say for instance if I uninstall an app and then reboot, the app is there again. If I connect to a Wifi network and reboot, it disappears. Every single modification is erased and returns back to the same state. The most annoying thing is that when I connect to a Wifi the apps start synchronizing, crash and the phone reboots.
I tried the following:
- Factory reset from the interface to no avail as it returns to the state it was as well
- Factory reset from HBOOT reboots into recovery with a red triangle with exclamation mark and stays the same
- Downloaded the RUU from HTC, which reboots the phone and then stays the same and reports an error
- Tried "fastboot oem rebootRUU", which simply reboots the phone into android
- Tried to unlock the bootloader, which again reboots the phone into android
- Tried to flash a different recovery and ends up with error: FAILED (remote: signature verify fail)
- Tried to flash only the zip from the RUU and ends up with the same signature error
I simply can't think of anything else to do, and I hope one of the gurus can help me in my quest
Thank you for the time you spent reading my post.
My responses/comment below in red font:
tyraek said:
I have an interesting problem with an HTC M8 from AT&T. It is completely stock only with OTA updates.
(bootloader) version-main: 1.58.502.1
It doesn't appear to have had any OTA updates. Or at most a minor update from 1.54>1.58.
- Factory reset from HBOOT reboots into recovery with a red triangle with exclamation mark and stays the same
Try pressing vol up and power to show the stock recovery menu options. I believe factory reset is one of those options, although if wiping in OS didn't work; I doubt doing so from stock recovery will be any different.
- Downloaded the RUU from HTC, which reboots the phone and then stays the same and reports an error
Which RUU (exact filename)? There are many, and the RUU has to be intended for your CID version.
What error number, and what error message? This is very important, otherwise we have no idea why it failed.
You're on the right track, by trying to run an RUU. I think its your best bet to fix the issue. But we need to make sure you run the right RUU.
- Tried to flash a different recovery and ends up with error: FAILED (remote: signature verify fail)
You can't flash recovery with a locked bootloader.
- Tried to flash only the zip from the RUU and ends up with the same signature error
Again, which RUU specifically is very important. Can't tell if the RUU is the right one based on the info given.
Also, please verify on the hboot screen, near the top, if it says LOCKED (other possibilities being UNLOCKED and RELOCKED)
Click to expand...
Click to collapse
Thank you so much for your reply.
I have tried the factory reset from the recovery and the result is the same.
I downloaded the latest RUU for my model I believe:
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
The update states it will upgrade from 1.58.502.1 to 4.28.502.2. Then I click the next button, the phone reboots and the updater says "waiting for bootloader", however the phone booted into android just like when I issue the command "fastboot oem rebootRUU". The installer then fails with error 171: USB connection error. I attached the RUU log as well.
The HBOOT says *** LOCKED ***. I tried to unlock it through the HTCdev process "fastboot flash unlocktoken Unlock_code.bin" but the bootloader stays in the same state.
bump
tyraek said:
I downloaded the latest RUU for my model I believe:
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
Click to expand...
Click to collapse
Yes, this is for your model (AT&T) and the version number will work.
tyraek said:
Then I click the next button, the phone reboots and the updater says "waiting for bootloader", however the phone booted into android just like when I issue the command "fastboot oem rebootRUU". The installer then fails with error 171: USB connection error. I attached the RUU log as well.
.
Click to expand...
Click to collapse
This is means there is a USB communication issue, usually on the PC side, and there is nothing wrong with the RUU or the phone.
RUU is very finicky, and this issue is common. Try a different cable, different USB port, and try to re-install HTC Sync.
But you may have to resort to using another computer. Win7 and USB 2.0 (USB 3.0 is known to cause issues with RUU) are the best bet to get the RUU to run properly.
tyraek said:
The HBOOT says *** LOCKED ***. I tried to unlock it through the HTCdev process "fastboot flash unlocktoken Unlock_code.bin" but the bootloader stays in the same state.
Click to expand...
Click to collapse
Do not unlock the bootloader if you intend to RUU. Unlocked bootloader will actually cause the RUU to fail, by definition. RUU requires the bootloader by LOCKED or RELOCKED (or else you need s-off to run an RUU with the bootloader UNLOCKED).

Stuck trying to get back to stock ("soft bricked"?)

Preface
- I don't know what half of the dang rooting terms mean (My own fault before getting into all of this :crying
- Verizon HTC One M8
- Had Unlocked, Root, and S-OFF for 2 years
- Had some version of TWRP recovery
- Trying to get it back to stock recovery and "ROM" (correct term?)
- Connecting phone to OSX for adb/fastboot and could successfully run commands for both.
- fastboot getvar all output (with values I believe to be sensitive starred-out)
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.12.20.1211
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.17.605.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) imei2: Not Support
(bootloader) meid: ***********
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f2489bd1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
What I've tried
- I downloaded an RUU 0P6BIMG.zip from a link on some M8 thread in XDA; couldn't even tell you which one (but I make sure the posts I view are related to Verizon M8). My understanding is that an RUU is an all-in-one tool for stock: stock bootloader, recovery, and ROM. My understanding may or may not be correct.
- I connected my phone to the computer (again, OSX), and I could see my device listed with fastboot devices.
- Following Method 1 on this page, I rebooted into "RUU mode" (term?) with fastboot oem rebootRUU. This showed an all-black screen with a white "htc" in the center.
- Then I flashed the RUU I'd downloaded with fastboot flash zip 0P6BIMG.zip
- This started copying files / doing whatever. Took about 5 minutes and seemed to be working, but ultimately it ended with a "FAILURE: something something" (unfortunately, I didn't capture the exact output).
Where I'm at now
- I believe I'm still in "RUU mode" with failure indicators. It's still an all-black screen with the white "htc" in the center, but now each of the 4 corners of the screen also has a white "warning" symbol (triangle with exclamation mark).
- I can still see my device listed on my computer with fastboot devices, but cannot get any adb commands to work. fastboot getvar all gives the same result as it did prior.
- I attempted to re-flash the RUU file, but it again failed, only within a matter of seconds, not minutes.
- I downloaded an hboot.img (again, from a link on some XDA M8 post), and can successfully run fastboot boot hboot.img. Not sure what it actually does.
- I downloaded a new TWRP image file, twrp-3.0.2-0-m8.img from their site. I am able to successfully flash it with fastboot flash recovery twrp-3.0.2-0-m8.img. I assume this means it's "permanently" on the phone, not just some temporary measure.
- I'm also able to boot into it TWRP fastboot boot twrp-3.0.2-0-m8.img.
Now what?
- I cannot boot into the bootloader (white screen with options; I assume -- possibly incorrectly -- that this is hboot) using fastboot reboot-bootloader.
- Where do I go from here? I feel somewhat relieved that I can boot into TWRP, but not sure what to try now. From what I gather, the "RUU mode" with failure indicators stemmed from the failed RUU flash. So I thought to try to find another RUU file from a different source in case the original that I'd used was corrupted. Other than that, I'm pretty lost.
Please help!
Well, I fixed it somehow. I actually found another RUU file and tried flashing it. It initially failed with an error of "failed (remote 90 hboot pre-update please flush image again immediately)". I'm not sure if it actually meant to say "flash" instead of "flush", but I ran the same fastboot command again to see what would happen, and it worked. Perhaps that's what I needed to do the first time.
Anyway, the phone boots up to stock Android 4.4.2. I can boot into the bootloader if necessary, and I'm pretty sure it has custom recovery (if I boot into recovery, I don't get TWRP. It just has a completely black screen with an image of the phone that has a red warning icon on it).
So I don't know if I was actually on the right track in the first place, or if I just happened upon some dumb luck. But anyway it's working.

HTC M8 eye with official rom stuck in fastboot

Hey guys
Last night my phone(HTC m8 eye 5.07.401.1) slowed down badly, after a while it restarted automatically and fastboot screen showed up.
Things I've tried:
1-Restarting the phone after fully charging it for 1 billion times (worked once but the phone was frozen and restarted automatically again)
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
3-Trying to flash the official rom , didn't work
4-removing the SIM and SD card and restarting the phone, didn't work
by the way, usb debugging was not active last time the phone was working normally, Also the phone have not experienced any unusual activity like rooting or flashing custom roms or...
What can I do?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA00000000000
(bootloader) imei: 3580000000000000
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mels_tuhl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B81000
(bootloader) cidnum: HTC__J15
(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: 5c9466dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
------------------------------------------------------------------------------------------- fastboot results----------------------
C:\fastboot>fastboot devices
FA57LY901038 fastboot
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.041s]
finished. total time: 10.041s
C:\fastboot>fastboot flash zip update.zip
target reported max download size of 1826332672 bytes
sending 'zip' (1687274 KB)...
OKAY [ 57.179s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 118.969s
---------------------------------------------------------------------------------------
I don't have the "eye", only the "standard" M8, but I'll try to help as much as I can, as far as anything that I believe is common between the two M8 versions (unlocking bootloader, flash RUU, etc.).
bahmaniq said:
2- Trying to unlock the boot loader(Got the unlock_code.bin file, tried to load it to the phone using adb, it said success or done or something like that but nothing changed)
Click to expand...
Click to collapse
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
bahmaniq said:
3-Trying to flash the official rom , didn't work
Click to expand...
Click to collapse
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.
redpoint73 said:
So the bootloader screen says LOCKED? I assume that is what you mean by "nothing changed", but I want to be clear on this.
Click to expand...
Click to collapse
Yes, *****LOCKED***** it says, I guess it is very serious on this one. Based on knowledge I gathered in these 2 days, I think it should show a black confirmation screen after I try to unlock it (using *.bin file), but it simply does not.
redpoint73 said:
What is the exact file name? It's best to provide specific file name/version info when asking for help. I've seen a lot of cases where the person "thought" they were flashing the right RUU, but in fact, it was not even the right one.
Click to expand...
Click to collapse
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
redpoint73 said:
But based on what you've described so far (bootloader will not unlock, RUU will not run, emmc error) it sounds like a hardware emmc failure.
Click to expand...
Click to collapse
So, that's it, I'm gonna play "One last goodbye" and let the history judge. 2 years of EMERGENCY CALLS ONLY, 2 years of zero antenna...
After a silent peaceful night
You took my heart away
oh I wish, I wish you could have stayed
bahmaniq said:
Yes you are right, RUU is the most important part and I did not elaborate. There is a big chance that the RUU is the Achilles Heel!! Exact file name is: 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed
Click to expand...
Click to collapse
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.
redpoint73 said:
That is not the RUU for the M8 eye. It's the RUU for the "regular" Euro M8. That is why you have signature error. Not sure where you can find the RUU for the "eye".
One more questions, is the phone going to fastbootRUU mode after running the command: fastboot oem rebootRUU
The error "command never completed" would suggest NO. But I'm curious whether the phone actually goes to RUU mode or not. RUU mode is signified by a black screen with large HTC logo. A progress bar will also appear below the logo, when the RUU starts to install. But in your case, you my have not gotten far enough for the progress bar to appear.
If the phone does not in fact even go to RUU mode due to emmc error, then it is probably irrelevant whether you have the right RUU or not. You will not get the RUU to run, if you can't even enter RUU mode.
Click to expand...
Click to collapse
It has been a long time since the last time I was here but the problem is not solved. Sorry for the delay, and No the black screen with HTC logo does not appear.
Is there anything I can do to get rid of this fastboot screen? or the phone is useless

Categories

Resources