Develop Bugs

My HTC Desire HD stuck at HTC logo after AAHK

Hello All,
I tried to root my HTC Desire HD device using AAHK tool,
AAHK tried to downgrade and then its stuck at HTC logo.
Below are my phone details..
c:\mini-adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.85.0024
INFOversion-baseband: 26.10.04.03_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.31.405.6
INFOserialno: HT11XTZ04358
INFOimei: xxxxxxxxxxxxxxxx
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9814000
INFOcidnum: TELUS001
INFObattery-status: good
INFObattery-voltage: 4160mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: a3d4fa0f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.014s
I want to use my phone back with orignial ROM.
I tried all the possible ways that i can..
Please help.

someone please help

avanam said:
Hello All,
I tried to root my HTC Desire HD device using AAHK tool,
AAHK tried to downgrade and then its stuck at HTC logo.
Below are my phone details..
c:\mini-adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.85.0024
INFOversion-baseband: 26.10.04.03_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 1.31.405.6
INFOserialno: HT11XTZ04358
INFOimei: XXXXXXXXXXX
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9814000
INFOcidnum: TELUS001
INFObattery-status: good
INFObattery-voltage: 4160mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: a3d4fa0f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.014s
I want to use my phone back with orignial ROM.
I tried all the possible ways that i can..
Please help.
Click to expand...
Click to collapse
Ok, have you tried to re run the hack kit from the white screen?? please delete your IMEI number, it is not necessary.

glevitan said:
Ok, have you tried to re run the hack kit from the white screen?? please delete your IMEI number, it is not necessary.
Click to expand...
Click to collapse
Hello glevitan, thanks for your reply.
Yes, when i tried to run Hack kit from white screen, I am getting below error.
Check adb connectivity
shad0wfox 04/2011
***ERROR ERROR ERROR***
Phone not plugged in
OR
Driver not installed
OR
USB Debugging not enabled.
***ERROR ERROR ERROR***
Press any key to continue . . .

avanam said:
Hello glevitan, thanks for your reply.
Yes, when i tried to run Hack kit from white screen, I am getting below error.
Check adb connectivity
shad0wfox 04/2011
***ERROR ERROR ERROR***
Phone not plugged in
OR
Driver not installed
OR
USB Debugging not enabled.
***ERROR ERROR ERROR***
Press any key to continue . . .
Click to expand...
Click to collapse
Seems that you factory reseted the phone. Did you?

glevitan said:
Seems that you factory reseted the phone. Did you?
Click to expand...
Click to collapse
Yes, I did.

avanam said:
Yes, I did.
Click to expand...
Click to collapse
Hi all,
anyone please suggest. Im stuck .
anone ???

avanam said:
Hi all,
anyone please suggest. Im stuck .
anone ???
Click to expand...
Click to collapse
You need to flash a RUU. Do you mind if I have a look at it over teamviewer??

brick ahead?
glevitan said:
You need to flash a RUU. Do you mind if I have a look at it over teamviewer??
Click to expand...
Click to collapse
Hi,
Have the same phone with same settings and was about to start using this AAHK. Luckily I didn't yet.
Pls let me know how it ended up as I am very interested in not finding myself in the same situation.
Naive question: Does this kit have to perform a downgrade from GB 2.3.5 in the process?
Thanks for your precious help

pgradone said:
Hi,
Have the same phone with same settings and was about to start using this AAHK. Luckily I didn't yet.
Pls let me know how it ended up as I am very interested in not finding myself in the same situation.
Naive question: Does this kit have to perform a downgrade from GB 2.3.5 in the process?
Thanks for your precious help
Click to expand...
Click to collapse
Just try NOT to factory reset during the proces... I did that and was foced to flash RUU - it solved the problem easily.
Since I had GB 2.3.5. stock I had to downgade first, and AAHK did that. Just read and carefully folow the manual...

pgradone said:
Hi,
Have the same phone with same settings and was about to start using this AAHK. Luckily I didn't yet.
Pls let me know how it ended up as I am very interested in not finding myself in the same situation.
Naive question: Does this kit have to perform a downgrade from GB 2.3.5 in the process?
Thanks for your precious help
Click to expand...
Click to collapse
ok, you don't have to worry. The Kit works flawlessly if you follow the manual. As you were told, factory reseting the phone is a huge mistake and might get you into troubles. Getting stuck in the splash screen means that the kit failed due to connectivity issues. You just need to re run it from that white screen....
Downgrade is almost automatically, but you need to follow some instructions on screen. As long as you read carefully and follow commands nothing has to worry you. If you get stuck, you can just hit the Hack Kit IRC channel or post a question in here (I am in both places) and I will lend you a hand. :good:

aahk-11092012 + Win7 x64 works OK
glevitan said:
ok, you don't have to worry. The Kit works flawlessly if you follow the manual. As you were told, factory reseting the phone is a huge mistake and might get you into troubles. Getting stuck in the splash screen means that the kit failed due to connectivity issues. You just need to re run it from that white screen....
Downgrade is almost automatically, but you need to follow some instructions on screen. As long as you read carefully and follow commands nothing has to worry you. If you get stuck, you can just hit the Hack Kit IRC channel or post a question in here (I am in both places) and I will lend you a hand. :good:
Click to expand...
Click to collapse
Thanks very very much glevitan for your help. I finally made it alone (after a few difficulties). See other forum (comment 6402 redips.net - root-htc-desire-hd) where I posted my adventure

glevitan said:
ok, you don't have to worry. The Kit works flawlessly if you follow the manual. As you were told, factory reseting the phone is a huge mistake and might get you into troubles. Getting stuck in the splash screen means that the kit failed due to connectivity issues. You just need to re run it from that white screen....
Downgrade is almost automatically, but you need to follow some instructions on screen. As long as you read carefully and follow commands nothing has to worry you. If you get stuck, you can just hit the Hack Kit IRC channel or post a question in here (I am in both places) and I will lend you a hand. :good:
Click to expand...
Click to collapse
hi there,,i have an DHD given by customer and i dont have phone history (what he did with the phone) now phone stuck on logo and i can goto bootloader with s-off and this is the version on the phone :
RUU_Ace_Sense30_S_hTC_Asia_WWE_3.13.707.4_R_Radio_12.65.60.29_26.14.04.28_M_release_234022_signed
i tried to install it but im getting error : MODEL ID ERROR..plz help me how to solve it...thnx in adv

mobileplazza said:
hi there,,i have an DHD given by customer and i dont have phone history (what he did with the phone) now phone stuck on logo and i can goto bootloader with s-off and this is the version on the phone :
RUU_Ace_Sense30_S_hTC_Asia_WWE_3.13.707.4_R_Radio_12.65.60.29_26.14.04.28_M_release_234022_signed
i tried to install it but im getting error : MODEL ID ERROR..plz help me how to solve it...thnx in adv
Click to expand...
Click to collapse
you are S-OFF, the RUU should be flashing fine. Get me a getvar all from fastboot usb.
Boot in hboot and plug the phone to the pc, if you see HBOOT USB PLUG in the phone press power button to toggle to fastboot usb and then in a cmd in the PC type:
Code:
fastboot getvar all
Delete the IMEI and paste the outcome in here.

glevitan said:
you are S-OFF, the RUU should be flashing fine. Get me a getvar all from fastboot usb.
Boot in hboot and plug the phone to the pc, if you see HBOOT USB PLUG in the phone press power button to toggle to fastboot usb and then in a cmd in the PC type:
Code:
fastboot getvar all
Delete the IMEI and paste the outcome in here.
Click to expand...
Click to collapse
C:\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.707.4
(bootloader) serialno: HT14VT211743
(bootloader) imei: 357814043009813
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9812000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3830mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.007s

mobileplazza said:
C:\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.13.707.4
(bootloader) serialno: HT14VT211743
(bootloader) imei: 357814043009813
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9812000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3830mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.007s
Click to expand...
Click to collapse
You are S-OFF, however your CID number is the AT&T one. Anyway, you can flash a custom recovery and then a custom rom to see what happens.
Follow the guide in my signature to find out how to do that. It is easy and you shouldn't have issue unless there is a hardware issue.

glevitan said:
You are S-OFF, however your CID number is the AT&T one. Anyway, you can flash a custom recovery and then a custom rom to see what happens.
Follow the guide in my signature to find out how to do that. It is easy and you shouldn't have issue unless there is a hardware issue.
Click to expand...
Click to collapse
for this process do i need to unlock the bootloader or simply flash the custom recovery and rom ? and any suggestion for gud custom rom plz.

mobileplazza said:
for this process do i need to unlock the bootloader or simply flash the custom recovery and rom ? and any suggestion for gud custom rom plz.
Click to expand...
Click to collapse
Just recovery and ROM.

bananagranola said:
Just recovery and ROM.
Click to expand...
Click to collapse
if i tried to flash recovery im getting this error...
C:\android-sdk\platform-tools>fastboot flash recovery recovery-clockwork-touch-5
.8.0.0-ace.img
sending 'recovery' (3554 KB)...
OKAY [ 0.586s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.589s
if i tried to unlock bootloader with htcdev.com im getting this erro
C:\android-sdk\platform-tools>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
plz help needed...

Like I said, you don't need to unlock the bootloader. You actually can't with S-Off. Is your phone in fastboot mode when you try to flash the recovery?

[Q] Cannot unlock bootloader, rumrunner fails!

Ive tried so many different methods. Currently running HTC Sense 6, KitKat 4.4.3, hboot 1.55
Rumrunner goes through the first 3 steps but when it tries to connect to ADB again it just says the following:
Code:
Rebooting into bootloader <again>
Waiting for fastboot <7/120>
Waiting for adb <43/120>
Waiting for device
Waiting for device
really dumb issues you have. you suck..
ERROR: run rumrunner again..
Press ENTER to exit
If anyone could help me please achieve S-OFF so I may flash CM12 to my device.
All help is welcome. Thanks!

charmon96 said:
Ive tried so many different methods. Currently running HTC Sense 6, KitKat 4.4.3, hboot 1.55
Rumrunner goes through the first 3 steps but when it tries to connect to ADB again it just says the following:
Code:
Rebooting into bootloader <again>
Waiting for fastboot <7/120>
Waiting for adb <43/120>
Waiting for device
Waiting for device
really dumb issues you have. you suck..
ERROR: run rumrunner again..
Press ENTER to exit
If anyone could help me please achieve S-OFF so I may flash CM12 to my device.
All help is welcome. Thanks!
Click to expand...
Click to collapse
Only method you can use is sunshine.
Http://Theroot.ninja

There has to be another way, I do not have $25 to spend on a simple tweak.....

charmon96 said:
There has to be another way, I do not have $25 to spend on a simple tweak.....
Click to expand...
Click to collapse
There is not. Sorry. If it was such a simple tweak there would be.
But again there is not.

So there is absolutely no other method for this phone right now other then paying $25?

charmon96 said:
So there is absolutely no other method for this phone right now other then paying $25?
Click to expand...
Click to collapse
Not on the vzw m7 running the latest os.
Sorry.
Was this phone unlocked previously? For 4.4.3 you should have a newer hboot?

dottat said:
Not on the vzw m7 running the latest os.
Sorry.
Was this phone unlocked previously? For 4.4.3 you should have a newer hboot?
Click to expand...
Click to collapse
Does rumrunner just not work? I dont understand how it can get adb the first time but after the second attempt it fails. That is the only error I get..

charmon96 said:
Does rumrunner just not work? I dont understand how it can get adb the first time but after the second attempt it fails. That is the only error I get..
Click to expand...
Click to collapse
Rumrunner stopped working after 2.x.x.x firmware iirc.

Firewater has supposedly worked for some on 443. They had to of tried many many times for it to work though.

charmon96 said:
Does rumrunner just not work? I dont understand how it can get adb the first time but after the second attempt it fails. That is the only error I get..
Click to expand...
Click to collapse
Can you still doublecheck that hboot version? Shouldn't be 1.55 on the latest. If it is, are you sure you aren't unlocked or s-off?
Can you run the command
Fastboot getvar all
While in fastboot and paste the output into your reply here. Blank out your serial number and imei

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4139mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s

charmon96 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4139mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Click to expand...
Click to collapse
Ok. That makes more sense.
Weaksauce won't enable you temp root on this version. See the below post.
http://forum.xda-developers.com/showthread.php?p=55477245
See if the steps detailed on the last page of the following thread enable you to temp root at all..
http://forum.xda-developers.com/showthread.php?t=2795746

Verizon HTC One M7 Not Able To Boot Anything

So this is my last resort.. I have been trying everything for like a week to try and fix this thing. It all started after I tried flashing a custom Viper rom. I had S-OFF through sunshine i bought a license for 25$. After I installed custom rom I got a boot loop which I couldn't fix and have tried RUU's and all and still can't get anything to boot other then CWM Recovery. I have root and the phone still says S-OFF but for some reason it says RELOCKED which I didn't do. Anyways, I just want the phone to boot up normal STOCK I've tried downloading a few of the files across the forums and nothing will flash. If anyone could help me out I would greatly appreciate it.
Here is my fastboot getvar:
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA3ARS900814
(bootloader) imei: ***
(bootloader) meid: ***
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: vzw__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.424s

yahdeeez said:
So this is my last resort.. I have been trying everything for like a week to try and fix this thing. It all started after I tried flashing a custom Viper rom. I had S-OFF through sunshine i bought a license for 25$. After I installed custom rom I got a boot loop which I couldn't fix and have tried RUU's and all and still can't get anything to boot other then CWM Recovery. I have root and the phone still says S-OFF but for some reason it says RELOCKED which I didn't do. Anyways, I just want the phone to boot up normal STOCK I've tried downloading a few of the files across the forums and nothing will flash. If anyone could help me out I would greatly appreciate it.
Here is my fastboot getvar:
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA3ARS900814
(bootloader) imei: ***
(bootloader) meid: ***
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: vzw__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.424s
Click to expand...
Click to collapse
You are not on a verizon software **(bootloader)version-main: 1.29.401.12** . The most recent is 5.28.605.2. Change your cid to supercid 11111111 using fastboot command >fastboot oem writecid 11111111
Then to htcdev.com. register or login. Run the unlock bootloader program following the directions exactly. Then you will get an unlock token. Use that unlock token while super cid (11111111) to unlock bootloader.
There is also a tutorial on here using adb shell commands to lock and unlock

aaronpw0621 said:
You are not on a verizon software **(bootloader)version-main: 1.29.401.12** . The most recent is 5.28.605.2. Change your cid to supercid 11111111 using fastboot command >fastboot oem writecid 11111111
Then to htcdev.com. register or login. Run the unlock bootloader program following the directions exactly. Then you will get an unlock token. Use that unlock token while super cid (11111111) to unlock bootloader.
There is also a tutorial on here using adb shell commands to lock and unlock
Click to expand...
Click to collapse
That's weird, I tried using the htcdev method to unlock the bootloader when I first got the phone and it gave an error that it wouldn't work for some reason, and alot of others online had the same issue. Well I'm so glad my bootloader says unlocked again now hopefully I can flash a ROM and get this phone working again, its been about 2 weeks!
How do I find the right bootloader I need and which one do I need to download?
Thanks alot aaronpw

yahdeeez said:
That's weird, I tried using the htcdev method to unlock the bootloader when I first got the phone and it gave an error that it wouldn't work for some reason, and alot of others online had the same issue. Well I'm so glad my bootloader says unlocked again now hopefully I can flash a ROM and get this phone working again, its been about 2 weeks!
How do I find the right bootloader I need and which one do I need to download?
Thanks alot aaronpw
Click to expand...
Click to collapse
So it worked??
 @santod040 has a thread with latest VZW firmware. Follow his instructions exactly. Also be sure to go back to non-Supercid BEFORE flashing firmware. Fastboot command>fastboot oem writecid VZW__001

aaronpw0621 said:
So it worked??
@santod040 has a thread with latest VZW firmware. Follow his instructions exactly. Also be sure to go back to non-Supercid BEFORE flashing firmware. Fastboot command>fastboot oem writecid VZW__001
Click to expand...
Click to collapse
Im about to try to flash a ruu file i believe it is the correct one... I have been messing with this all morning and haven't been able to get any roms to flash at all... thank you again ill let you know what happens

yahdeeez said:
Im about to try to flash a ruu file i believe it is the correct one... I have been messing with this all morning and haven't been able to get any roms to flash at all... thank you again ill let you know what happens
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=56302410

Softbricked my HTC One M8, any advice is much appriciated

Well its been some time since was rooting and romming phones (so please give advice step by step) but just the other day I soft bricked my One M8 and I am at wit's end trying to fix it.
Scenario was I was happy running gpe 4.4.2 on my phone awhile now until I saw the GPE rom was getting an OTA update with Lollipop. To avoid the hassle of installing an ota updat the dirty way I thought to just re-lock my bootloader, flash recovery and just update. Well it went like this.
1. Had 4.4.2
2.Flashed stock recovery (I forgot to do fastboot oem lock)
3.Booted back into 4.4.2, ran update checker, downloaded 4.4.3
4.Phone updated to 4.4.3 with no issue.
5. Ran update checker again to grab 4.4.4
6.Rebooted to install and bam on boot I just got the white "HTC" boot screen for about an hour
OS is broke.
I do still have access via fastboot and have since re flashed recovery to twrp. However I am unable to flash a new rom, I keep getting "E error executing updater binary in zip" in twrp and "status 7" in clockwork.
Sideloads fail with the same error.
I've also tried re-locking the phone and flashing stock recovery and trying HTC's RUU app however that fails as well with Error 553.
Any help is much appreciated! My goal is just to have clean lollipop gpe rom installed.
What can I do to fix this?
Current Bootloader screen:
++Tamperered++
++ Unlocked ++
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
Radio - 1.16.21331931.LA24G
Open-DSP-v38.2.2-00542-M8974.0311
OS-*blank* ----------something to note this was previously red with a 2.12 number
eMMC-boot 2048MB
fastboot getvar version-main yeilds:
version-main:
finished. total time: 0.001s
fastboot oem readcid yeilds:
(bootloader) cid: T-MOB010
OKAY [ 0.003s]
finsihed.
fastboot getvar all yeilds:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(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: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s

tin_can_ said:
Well its been some time since was rooting and romming phones (so please give advice step by step) but just the other day I soft bricked my One M8 and I am at wit's end trying to fix it.
Scenario was I was happy running gpe 4.4.2 on my phone awhile now until I saw the GPE rom was getting an OTA update with Lollipop. To avoid the hassle of installing an ota updat the dirty way I thought to just re-lock my bootloader, flash recovery and just update. Well it went like this.
1. Had 4.4.2
2.Flashed stock recovery (I forgot to do fastboot oem lock)
3.Booted back into 4.4.2, ran update checker, downloaded 4.4.3
4.Phone updated to 4.4.3 with no issue.
5. Ran update checker again to grab 4.4.4
6.Rebooted to install and bam on boot I just got the white "HTC" boot screen for about an hour
OS is broke.
I do still have access via fastboot and have since re flashed recovery to twrp. However I am unable to flash a new rom, I keep getting "E error executing updater binary in zip" in twrp and "status 7" in clockwork.
Sideloads fail with the same error.
I've also tried re-locking the phone and flashing stock recovery and trying HTC's RUU app however that fails as well with Error 553.
Any help is much appreciated! My goal is just to have clean lollipop gpe rom installed.
What can I do to fix this?
Current Bootloader screen:
++Tamperered++
++ Unlocked ++
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
Radio - 1.16.21331931.LA24G
Open-DSP-v38.2.2-00542-M8974.0311
OS-*blank* ----------something to note this was previously red with a 2.12 number
eMMC-boot 2048MB
fastboot getvar version-main yeilds:
version-main:
finished. total time: 0.001s
fastboot oem readcid yeilds:
(bootloader) cid: T-MOB010
OKAY [ 0.003s]
finsihed.
fastboot getvar all yeilds:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(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: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
Click to expand...
Click to collapse
I'm at work rt now but I'm 95% I can fix this for you say after work today..do u use hangouts?
---------- Post added at 11:28 AM ---------- Previous post was at 11:24 AM ----------
Something you can try now....you still get stuck at splash screen try fastboot the boot.IMG from the ROM you r running.

Yeah I use hangouts. And I'll be available at 7pm est today. I left the phone at home today just out of frustration of fiddling with it all night. Message me your gmail account and we'll take a look.

tin_can_ said:
Yeah I use hangouts. And I'll be available at 7pm est today. I left the phone at home today just out of frustration of fiddling with it all night. Message me your gmail account and we'll take a look.
Click to expand...
Click to collapse
Sent you a pm with gmail

all better now
thanks for the assist @Tigerstown

What was the fix for this? I am having the same problem
dottat said:
all better now
thanks for the assist @Tigerstown
Click to expand...
Click to collapse

joelmi12 said:
What was the fix for this? I am having the same problem
Click to expand...
Click to collapse
You tried to convert to gpe??? Cause that's what he did to begin with.

joelmi12 said:
What was the fix for this? I am having the same problem
Click to expand...
Click to collapse
I doubt you are having the same exact problem. I would be willing to take a look at it if you wanted though.

dottat said:
I doubt you are having the same exact problem. I would be willing to take a look at it if you wanted though.
Click to expand...
Click to collapse
I might be in a similar situation. I was running blisspop 5.0 just to see how it feels. I started having problems so i went to wipe and go back to CM11 only to find out Philz E: could not mount/data to setup . Now I have no ROM and a broken recovery.. any thoughts?

tommyamo said:
I might be in a similar situation. I was running blisspop 5.0 just to see how it feels. I started having problems so i went to wipe and go back to CM11 only to find out Philz E: could not mount/data to setup . Now I have no ROM and a broken recovery.. any thoughts?
Click to expand...
Click to collapse
Did you flash a different radio/baseband as part of this?
Are you S-OFF?

I am S off. I hadn't flashed a new radio. I found my fix. I think i inadvertantly wiped my data from the internal sd. That was throwing me off. I managed to get back to CM11. I still can't read any data on my ext SD, but at least my phone is on and stabilized. Thanks for replying!! Happy holidays!
Sent from my One M8 using XDA Free mobile app

So kinda messed up my wife's m8 :/ well I was running cm12 withe 500 gpe, she's trying to return it back so i decided to go back to stock I flashed the stock gpe and boom I get the e: data not mounted and it won't do a side load or nothing also was able to flash a recovery 2 different Recovery's but nothing is flashing or pushing any help would be appreciated thank you...
Sent from my Nexus 6 using Tapatalk

Sunshine

I'm having a problem being able to launch apps on my One M8 ATT... I Don't have any apps on my home page and ATT Ready2Go keeps crashing on me. Can someone give me a command line so I can launch SunShine on my device through ADB, that way I can S-Off and go back to a different ROM.

Why would you need s-off to install a different rom ?

Mr Hofs said:
Why would you need s-off to install a different rom ?
Click to expand...
Click to collapse
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.

isutke1287 said:
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.
Click to expand...
Click to collapse
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.

xunholyx said:
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.
Click to expand...
Click to collapse
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *tsk tsk*
(bootloader) imei: *tsk tsk*
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)

isutke1287 said:
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *tsk tsk*
(bootloader) imei: *tsk tsk*
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)
Click to expand...
Click to collapse
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.

xunholyx said:
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.
Click to expand...
Click to collapse
I can NOT appreciate and thank you for your assistance in this! I went ahead and locked the bootloader and restored the original image with the RUU you linked me to, yesterday. Couldn't wait to try, haha. I had to sweet talk the HTC Live Chat person to tell me if I could use the RUU for the same software version as I had. Phone has been working like a champ. I'm gonna give it another day or two to settle in, do a few backups just in-case the flash doesn't go well.
I will definitely unlock the bootloader again and flash TWRP and SuperSU. But I imagine going S-OFF is just off the table right now since I'm a bit stripped of funds. I can afford it, haha, but my funds are already allocated towards adulting and such.
Again, THANK you for the support! This has been a learning experience.:good::good::good::good::good: