Develop Bugs

Computer won't connect to phone with updated drivers.

So yeah I think I really screwed the pooch on this one.
Here's what's going on.
-My stupid self tried to flash CM10 with a HBOOT v 1.14. Yeah... save it. I know.
-Now I've gotten so far into this thing that my computer won't recognize my phone in order to utilize fastboot to total wipe and retry to run the RUU.
-Computer has been updated with current drivers. I can get into bootloader, but anything I try after that is unable to be done. Cannot get into recovery, if it's even still there. I tried to reflash TWRP, unsuccessfully. When I try to even boot into recovery, it gets stuck on HTC's boot splash screen.
CID: 1111111
HBOOT: 1.14
Relocked
I am totally lost on this. I just want to get it back working ASAP.

do you have a nandroid backup?

robchongke said:
do you have a nandroid backup?
Click to expand...
Click to collapse
I don't. My dumbass self didn't make one.
And anytime I use the toolkit, to do ANYTHING, *device not found*. So i've royally screwed something up. Even after getting all the drivers. I think.
More info: version: 0.5
version-bootloader: 1.14.0002
version-baseband: 0.19as.32.09.11_
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT29TW302342
imei: 359691048634839
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4107mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 1a7fdca3
hbootpreupdate: 11
gencheckpt: 0

KMiracle1984 said:
I don't. My dumbass self didn't make one.
Click to expand...
Click to collapse
if TWRP dont work maybe try CWM.
maybe you flash the wrong custom rom. this thread is for endeavour(international version) yours is evita, that's htc one xl.

robchongke said:
if TWRP dont work maybe try CWM.
Click to expand...
Click to collapse
I would, if I could get it to respond. I get notihing in either fastboot or through the toolkit.
The computer does it's beeping when you connect, but nothing happens.

Attempting to force a boot.img to the phone....
sending 'boot' (5248 KB)...
OKAY [ 0.889s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.274s

You are in the wrong forum mate, go to the HTC one XL forum. This is all for the endevouru !

Blaine999 said:
Click to expand...
Click to collapse
What's the matter mate.....trying to gather posts or what ?
Please bring something to the table other than a rolleyes !!! :thumbdown:
This is the second thread already ......

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

[Q] [RUU] Error: 152. Unable to Restore TMob 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.

[Q] AT&T M8. Worst case scenario, basically. Phone recoverable?

****ed up and didn't read things properly. I was trying to revert my phone to stock with an HTC RUU, that didn't work, and in haste and anger I set S-ON. On a device running CyanogenMod.
The threads I found on the subject weren't entirely helpful, so I'm here now, hoping I don't have to explain to HTC why I'm dumb. My device boots immediately to fastboot:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVD SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Here's the output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45P
(bootloader) imei: 35871
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
If anyone has advice, I'd appreciate it. Thanks!

Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.

redpoint73 said:
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
Click to expand...
Click to collapse
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work.
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.

BaconSupreme said:
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
Click to expand...
Click to collapse
That's because I reported to the mods to delete the personal data.
BaconSupreme said:
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work..
Click to expand...
Click to collapse
Your CID and MID are the correct one for AT&T.
BaconSupreme said:
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
Click to expand...
Click to collapse
That RUU will fail, since it corresponds to hboot 3.16; and with s-on you can't run an RUU with a lower number hboot than is installed on the phone (3.18 in your case). Any other RUU except that one should work. You can find the other RUUs on my AT&T specific Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432

Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Thanks for the help, redpoint.

BaconSupreme said:
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Click to expand...
Click to collapse
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
BaconSupreme said:
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Click to expand...
Click to collapse
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.

redpoint73 said:
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
Click to expand...
Click to collapse
Yeah, I couldn't boot into CWM. Fastboot > HBoot > Recovery... poof, back into Fastboot.

[Q] HTC One m8 fingerprint update error

Helllo there!
I'm making a new thread because I couldn't find anyone with the exact same problem and don't want to brick my phone or such.
Now to the problem: every time I try to update my HTC one m8 (Europe) it stops when installling and tells me this:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.101.007
Package expects build fingerprint of htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.9:user/release-keys
or htc/htc_europe/htc_m8:5.0.1/LRX22C/448934.10:user/release-keys;
this device has htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.6:user/release-keys.
Installation aborted.
Write host_mode 0 done
getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(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: 0P6B10000
(bootloader) cidnum: HTC__102
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone is rooted, the bootloader unlocked, it has the stock recovery, it's s-on and it says "software status: modified".
The only thing I can see in the error is that this nine:
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]9[/U][/B]:user/release-keys
is a six
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]6[/U][/B]:user/release-keys
on mine.
I am pretty new here still, so i don't know how to fix it, and i don't want to break it.
Best regards
Schmix

Root phone

vinayluck said:
Root phone
Click to expand...
Click to collapse
What are you trying to say?

Schmix said:
What are you trying to say?
Click to expand...
Click to collapse
You should post your getvar all (deleting your imei number and S./N ) there is a post here but it is in german with the same problem which points to an incorrect recovery!
http://www.android-hilfe.de/wiederh...ge-expects-build-fingerprint-fingerprint.html
Shepps

vinayluck said:
Root phone
Click to expand...
Click to collapse
Being rooted or not has no bearing on OTA update.
Also, it seems that you are trying to tell the OP to root (not completely clear, with the 2 word post), when he clearly states he is already rooted.

Getvar info added!
By the way, the other guy had a different problem.
Has anyone got an idea of whats wrong?

Schmix said:
Helllo there!
I'm making a new thread because I couldn't find anyone with the exact same problem and don't want to brick my phone or such.
Now to the problem: every time I try to update my HTC one m8 (Europe) it stops when installling and tells me this:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.101.007
Package expects build fingerprint of htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.9:user/release-keys
or htc/htc_europe/htc_m8:5.0.1/LRX22C/448934.10:user/release-keys;
this device has htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.6:user/release-keys.
Installation aborted.
Write host_mode 0 done
getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(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: 0P6B10000
(bootloader) cidnum: HTC__102
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone is rooted, the bootloader unlocked, it has the stock recovery, it's s-on and it says "software status: modified".
The only thing I can see in the error is that this nine:
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]9[/U][/B]:user/release-keys
is a six
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]6[/U][/B]:user/release-keys
on mine.
I am pretty new here still, so i don't know how to fix it, and i don't want to break it.
Best regards
Schmix
Click to expand...
Click to collapse
Download and run the 3.28.401.10 RUU first (a quick search here and you'll find it), then run this one.

Schmix said:
Getvar info added!
By the way, the other guy had a different problem.
Has anyone got an idea of whats wrong?
Click to expand...
Click to collapse
Wrong stock recovery image.
OTA needs stock recovery 3.28.401.9 (389838.9) or 4.16.401.10 (448934.10)
but you installed 3.28.401.6 (389838.6)
Get the right recovery image, OTA will proceed.
I have one here - 3.28.401.9_recovery.img : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.401.9_recovery.img/download

ckpv5 said:
Wrong stock recovery image.
OTA needs stock recovery 3.28.401.9 (389838.9) or 4.16.401.10 (448934.10)
but you installed 3.28.401.6 (389838.6)
Get the right recovery image, OTA will proceed.
I have one here - 3.28.401.9_recovery.img : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.401.9_recovery.img/download
Click to expand...
Click to collapse
Okay thank you so far!
But now it comes up with a different error; It says "/system/xbin/nc has unexpected contents".
Let me tell you the whole story:
Some time ago i installed busybox, xposed and xprivacy (and luckypatcher) and used it normaly.
Then the Lollipop update came around and since it wasnt working (giving out the unexpected contend error) i thought it would be a good idea to just do a factory reset.
It didnt work afterwards either, so i went here to ask what the problem was, and i was told it was because of xposed.
However, xposed wasn't installed anymore (the app), and (i think) the newer versions installed it somewhere else, so installing and then uninstalling (the button in the app) it didnt delete the old directory. (Btw. in an last attempt i tried installing the stick recovery and got the wrong one apparently)
So yeah, i have no idea on how to fix this problem, but i would be okay with having to reset my phone.

Schmix said:
But now it comes up with a different error; It says "/system/xbin/nc has unexpected contents".
So yeah, i have no idea on how to fix this problem, but i would be okay with having to reset my phone.
Click to expand...
Click to collapse
That's expected
There are a few methods to solve your problem.
The easiest one is RUU it back to stock.
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2735235
You need to relock bootloader and also make a backup of your internal storage files/pic/music or whatever you like to keep.
The RUU will update your device to the latest

ckpv5 said:
That's expected
There are a few methods to solve your problem.
The easiest one is RUU it back to stock.
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2735235
You need to relock bootloader and also make a backup of your internal storage files/pic/music or whatever you like to keep.
The RUU will update your device to the latest
Click to expand...
Click to collapse
But i don't have S-Off... is that a problem?
And are the files correct?

Schmix said:
But i don't have S-Off... is that a problem?
And are the files correct?
Click to expand...
Click to collapse
You don't have S-Off - that's why you need to relock bootloader
That's the only difference - read the thread thoroughly.
First step - relock bootloader with command fastboot oem lock
then follow the step 3 onwards
Also note you need to use htc_fastboot.exe not the usual fastboot.exe
Anything you need to ask, you can ask there. I believe @EddyOS will gladly help you

ckpv5 said:
You don't have S-Off - that's why you need to relock bootloader
That's the only difference - read the thread thoroughly.
First step - relock bootloader with command fastboot oem lock
then follow the step 3 onwards
Also note you need to use htc_fastboot.exe not the usual fastboot.exe
Anything you need to ask, you can ask there. I believe @EddyOS will gladly help you
Click to expand...
Click to collapse
Keep meaning to add a few bits that can be done with S-ON, been super busy of late!

ckpv5 said:
You don't have S-Off - that's why you need to relock bootloader
That's the only difference - read the thread thoroughly.
First step - relock bootloader with command fastboot oem lock
then follow the step 3 onwards
Also note you need to use htc_fastboot.exe not the usual fastboot.exe
Anything you need to ask, you can ask there. I believe @EddyOS will gladly help you
Click to expand...
Click to collapse
Thank you very much, I got it to work now!
Have a good day!

ckpv5 said:
Wrong stock recovery image.
OTA needs stock recovery 3.28.401.9 (389838.9) or 4.16.401.10 (448934.10)
but you installed 3.28.401.6 (389838.6)
Get the right recovery image, OTA will proceed.
I have one here - 3.28.401.9_recovery.img : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.401.9_recovery.img/download
Click to expand...
Click to collapse
I have the same issue with my htc desire 820n can you help me pleas

ammarhigh said:
I have the same issue with my htc desire 820n can you help me pleas
Click to expand...
Click to collapse
I believe you do know this is M8 thread and not HTC Desire 820n
But .. this is what you can do to fix your problem ...
Check for OTA as usual, download OTA then select install later.
Connect your device to PC then copy the OTA zip from internal storage\download folder to PC
Open the OTA zip with 7-zip, you'll see firmware.zip. Open firmware.zip and extract out recovery.img <--- this is the one that you need.
Boot your device to bootloader
Fastboot flash this extracted recovery.img
Reboot, check for OTA again, this time select install now
Done

I'm sorry for posting here but i did it and it's not working when i'm flashing the recovery i tooked it from the OTA it's give me error when flashing it the update is lollipop and i'm on kitkat 4.4.4
Sent from my HTC Desire 820 using XDA Free mobile app