Database Develop

[Q] HTC One fail big time

I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Pls pls help.Thank You.

erinar88 said:
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Pls pls help.Thank You.
Click to expand...
Click to collapse
Couldn`t work as you are S-On. I think you`re stuck bro afaik. Maybe someone else knows a solution. Good luck.

That's odd. It shouldn't have run at all since you can't downgrade using a RUU without s-off. It should have prompted a RUU error noting that you were on a later version.
Is your phone rooted and unlocked yet? Did you do anything to it besides run the RUU?

Can't you just use fastboot to push a custom recovery and then sideload a custom or stock ROM?

AllAboutTheCore said:
Can't you just use fastboot to push a custom recovery and then sideload a custom or stock ROM?
Click to expand...
Click to collapse
Looks like his only option. Surprised that the RUU wiped his device before getting the error.
There's no way to downgrade hboot with s-on atm.

I'm gonna be 'that guy'... What the heck were you doing flashing an RUU on S-on with 'limited IT knowledge'...
There's a reason RUUs aren't released. It's to prevent this.
On a side note I would try another RUU download. Where are you getting the error at? What's the phone doing?
Sent from my HTC One using Tapatalk 4 Beta

I'm wondering now. Did you actually try to fastboot flash the 1.44 WWE firmware.zip in RUU mode despite being s-on? Because if you really did that, the phone is dead. You're getting a signature error because the phone is s-on and you managed to corrupt something important. Being s-on, I doubt there is any way to fix it.
An expensive lesson, but maybe you'll be more careful next time. Gaining s-off isn't worth bricking your phone.

This is confusing as the official RUU's (exe's and zips) will simply not allow you to downgrade the hboot or to flash an older version of the firmware without having s-off so my thoughts are exactly the same as iElvis.
I cannot see how you managed to do what you did.
So questions....
Are you running a custom recovery?
Is your bootloader locked or unlocked?
Have you tried holding vol down and power for about 15 to 30 seconds to see if you can get into the bootloader?
Did you do something like reboot into bootloader, fastboot oem rebootRUU and then fastboot flash zip firmware.zip?
TELL US the exact steps you went through so we can try to help you and worst case scenario you have bricked your phone.

I am having a similar problem only i have S-off but i cant find the right RUU or the right recovery.img to fastboot it .
If you have rumrunner_HTC_0.5.0.zip you could gain s-off very easy .

erinar88 said:
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
Pls pls help.Thank You.
Click to expand...
Click to collapse
Sorry m8. Hate to break it to you but I accidentally did this too and I've found no solution for it. Ended up buying a new One...... I don't think there is a fix for this at all.
Sent from my HTC One using xda app-developers app

[Q] HTC One US unlocked 32 GB stuck on boot screen after OTA update

I got an OTA update on my HTC One US unlocked 32 GB version. The OTA update installed on the phone but the phone never booted up.
I went into the bootloader and tried factory reset but no success.
Now I want to flash my phone using RUU, but I am not getting correct RUU for my phone. I have unlocked the bootloader from HTCDEV website.
Details are :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.1540.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367W910917
(bootloader) imei: 354439059958431
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4100mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-076e0e17
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I tried many RUU matching the mid and cid number of my phone for example : htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_brightstarus_wwe_4-19-1540-9_radio_4a-23-3263-28_10-38r-1157-04l_release_353887_signed_3-exe/ but it gave image error. Please help

still having trouble
do u have s-off if not when trying to flash a ruu you need to relock bootloader b4 running ruu

s_rupainwar said:
I got an OTA update on my HTC One US unlocked 32 GB version. The OTA update installed on the phone but the phone never booted up.
I went into the bootloader and tried factory reset but no success.
Now I want to flash my phone using RUU, but I am not getting correct RUU for my phone. I have unlocked the bootloader from HTCDEV website.
Details are :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.1540.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367W910917
(bootloader) imei: 354439059958431
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4100mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-076e0e17
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I tried many RUU matching the mid and cid number of my phone for example : htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_brightstarus_wwe_4-19-1540-9_radio_4a-23-3263-28_10-38r-1157-04l_release_353887_signed_3-exe/ but it gave image error. Please help
Click to expand...
Click to collapse
That ruu should work for you but you are s-on, so as stated above you will need to relock to flash it.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Then run the ruu while connected with fastboot usb. :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

[Q] Flashed RUU-HTC_One_GE-2.14.1700.15. Now i am un able to flash any custom ROM's.

Hello,
I recently flashed RUU-HTC_One_GE-2.14.1700.15 to my M7 to see what it was like. Not getting on with it very well i decided to go back to ARHD. When i tried to restore my back up it got stuck in a boot loop.
I then tried a fresh install of ARHD, deleting all data, but this time it will show the splash screen hang for a while and then reboot into recovery.
I have also tried flashing Venom's latest ROM but it dose the same as ARHD.
I am S-OFF and my HBOOT is 1.54
when i do a get getvar all i get the following
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3817mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
Pretty stumped no as i can still use the Google RUU but really want to get back onto ADHD!!
Any help greatly received
Kind regards
Russ

rustyp81 said:
Hello,
I recently flashed RUU-HTC_One_GE-2.14.1700.15 to my M7 to see what it was like. Not getting on with it very well i decided to go back to ARHD. When i tried to restore my back up it got stuck in a boot loop.
I then tried a fresh install of ARHD, deleting all data, but this time it will show the splash screen hang for a while and then reboot into recovery.
I have also tried flashing Venom's latest ROM but it dose the same as ARHD.
I am S-OFF and my HBOOT is 1.54
when i do a get getvar all i get the following
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3817mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
Pretty stumped no as i can still use the Google RUU but really want to get back onto ADHD!!
Any help greatly received
Kind regards
Russ
Click to expand...
Click to collapse
update your recovery to TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
and flash any roms you want... Do Not Go S-on with the GPE Bootloader installed... RUU back to Stock before you consider s-on .. better yet stay s-off forever !!

clsA said:
and flash any roms you want... Do Not Go S-on with the GPE Bootloader installed... RUU back to Stock before you consider s-on .. better yet stay s-off forever !!
Click to expand...
Click to collapse
This worked a treat. Had to load an older version of ARHD first but got up to 71, eventually.

[Q] Best Rom for getting S-Off?

I have a T Mobile M7 with HBOOT 1.56. I've unlocked, rooted it and installed a custom rom on it just fine with S-ON. I'm trying to return it for warranty, and I've spent hours trying to get just a stock recovery and ROM installed. No RUUs, prepackaged AROMA installers, etc. will work so far. I want to try and get everything restored with an RUU after getting S-OFF on the phone. I've tried some of the utilities in the past without any luck, but have run across some threads saying that some some roms work better than others. What Roms have had the best success with Firewater etc. on HBOOT 1.56. No luck currently on Maximus HD 44
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s

cemicolin said:
I have a T Mobile M7 with HBOOT 1.56. I've unlocked, rooted it and installed a custom rom on it just fine with S-ON. I'm trying to return it for warranty, and I've spent hours trying to get just a stock recovery and ROM installed. No RUUs, prepackaged AROMA installers, etc. will work so far. I want to try and get everything restored with an RUU after getting S-OFF on the phone. I've tried some of the utilities in the past without any luck, but have run across some threads saying that some some roms work better than others. What Roms have had the best success with Firewater etc. on HBOOT 1.56. No luck currently on Maximus HD 44
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
try some combination of custom rom with unsecured kernels. ARHD, elementalX for example. You could also try other exploits like Sunshine s-off

Should I be flashing the unsecured kernel separately after the rom?

cemicolin said:
Should I be flashing the unsecured kernel separately after the rom?
Click to expand...
Click to collapse
Some roms already have unsecured kernel so you might want to try using the kernel included with the rom before flashing another kernel.

I tried ARHD and Maximus HD without any luck, so I'm just going to try to find a reset rom. I posted a new Q thread since it was a different question. Thanks!

cant flash RUU need help,

I am working on reverting my m7 to stock out of the box condition and am having some trouble flashing the stock att ruu zips and exe files and I dont know why, just fails ( allot of times after android info... my MID and CID are both stock CWS__001 and PN0712000 respectivly, I read somewhere that that MID is for the GPE, so I checked on the back of my phone and thats my stock MID for my sense phone...
here are my vars...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
also how do I make "dirty" go away in the " commitno-bootloader" section?
When I use ruus matching my config i get this error "Invalid sparse file format at header magi"

THC Butterz said:
I am working on reverting my m7 to stock out of the box condition and am having some trouble flashing the stock att ruu zips and exe files and I dont know why, just fails ( allot of times after android info... my MID and CID are both stock CWS__001 and PN0712000 respectivly, I read somewhere that that MID is for the GPE, so I checked on the back of my phone and thats my stock MID for my sense phone...
here are my vars...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
also how do I make "dirty" go away in the " commitno-bootloader" section?
Click to expand...
Click to collapse
Remove your IMEI number and serial number from your first post.
Just use this to return to stock by @clsA put TWRP recovery on your phone, do a full wipe, push or sideload the zip file to your internal storage and then flash it.
http://www.htc1guru.com/dld/guru_reset_m7_5-12-502-2_clsa-zip/
You don't get rid of dirty, its normal, they all say that.

THC Butterz said:
I am working on reverting my m7 to stock out of the box condition and am having some trouble flashing the stock att ruu zips and exe files and I dont know why, just fails ( allot of times after android info... my MID and CID are both stock CWS__001 and PN0712000 respectivly, I read somewhere that that MID is for the GPE, so I checked on the back of my phone and thats my stock MID for my sense phone...
here are my vars...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT38WW902359
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3985mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
also how do I make "dirty" go away in the " commitno-bootloader" section?
When I use ruus matching my config i get this error "Invalid sparse file format at header magi"
Click to expand...
Click to collapse
Which RUU do you want to flash. A link would be great :good:

I tried to flash every att ruu I could find, but I got it done, had to find a decrypted one, and extract it, then re insert and flash it piece by piece, radio, recovery, hboot, system... etc thanks for the replies, especially the imei/sn comment, forgot that was in the vars, made me check another post i made yesterday too :good:

THC Butterz said:
I tried to flash every att ruu I could find, but I got it done, had to find a decrypted one, and extract it, then re insert and flash it piece by piece, radio, recovery, hboot, system... etc thanks for the replies, especially the imei/sn comment, forgot that was in the vars, made me check another post i made yesterday too :good:
Click to expand...
Click to collapse
in all honesty, you should of just found the firmware matching the RUU you were trying to flash and flashed that first as you are s-off, you've pretty much done that just manually, glad you got it sorted though :good: