Database Develop

[Q] "Phone bricked, stuck at loading" after attempting to install busybox

Hi guys,
My phone bricked after I rooted my htc one 801e and attempted to install busybox. When I entered twrp recovery, most of the actions I did resulted in "unable to mount system"
Browsing around online, I came across some guides to restore stock ruu. i went and fastbot oem locked my phone and now I'm stuck. Lost recovery, (any attempt to access recovery only resulted in returning to fastboot menu) re-flashing recovery and/or ruu results in "FAILED (remote: 12 signature verify fail)"
Does anyone have any solution(s) to this?
my info is as follows:-
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxcxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: xxxxxxxxx
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4294mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2a2b2444da
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s

You need to unlock bootloader. What RUU you tried? Sounds like it was not official.

SaHiLzZ said:
You need to unlock bootloader. What RUU you tried? Sounds like it was not official.
Click to expand...
Click to collapse
I tried to re-unlock bootloader but it doesnt work. Gave me signature error. as for the ruu, i tried both http: //www .androidruu .com/index.php?developer=M7 and Guru Reset versions. Both gave signature errors. Basically, trying anything seems to give signature error. Hence I cant install recovery nor can I unlock bootloader.

s-on hboot 1.54, no access to OS

I think I messed up big time:
c:\droid\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I was trying to factory reset to remove device encryption and I am just dumb, really really dumb...
I typed in: fastboot oem writesecureflag 3
So now my device is on 1.54 with S-ON. I can't run rumrunner as it wants access to ADB, my ATT HTC One was the latest GPE and encrypted and now for some reason will not boot into the OS. I've tried unlocking via htcdev and I get a success message in fastboot but nothing changes. Factory reset does nothing, and I can't install the RUU.zip or use the RUU.exe, I get an error stating the signature verification failed. I get that sig verification failed with an insertcoin ROM as well. Can anyone help me?

badgcoupe said:
I think I messed up big time:
c:\droid\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I was trying to factory reset to remove device encryption and I am just dumb, really really dumb...
I typed in: fastboot oem writesecureflag 3
So now my device is on 1.54 with S-ON. I can't run rumrunner as it wants access to ADB, my ATT HTC One was the latest GPE and encrypted and now for some reason will not boot into the OS. I've tried unlocking via htcdev and I get a success message in fastboot but nothing changes. Factory reset does nothing, and I can't install the RUU.zip or use the RUU.exe, I get an error stating the signature verification failed. I get that sig verification failed with an insertcoin ROM as well. Can anyone help me?
Click to expand...
Click to collapse
Do you have stock or custom recovery installed?

I had TWRP installed but now it will not boot to it via the recovery option in hboot, it just goes back into the loading google boot loop. I just tried to repush TWRP to the device but got FAILED (remote: signature verify fail)

Brought the phone to ATT and they actually gave me another one. Lesson learned.

[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:

Tampered, Re locked and security Warning

Hello
I was just doing the trail and error to install custom rom by reading some articals. may be i was stupid not paying much attention to what exactly it says. i was happy that i was able to unlock the bootloader and installed the twrp custom recovery everything works fine till now, phone booted to Android too. and when i wanted the recovery its taken me to twrp recovery. here here i have done something and now i have completely lost the phone. now i ended up with tampered relocked and security warning and more over my phone always boots in to fastboot mode only. i can't either go twrp or Android just the fast boot. how can i come out of this mess.
my phone is HTC one bought in India no network lock. any help will be appreciated greatly.
Device details
bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.707.151
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA*******5
(bootloader) imei: 354********5
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3796mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
and it always stuck in fast boot

Device details
bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.707.151
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA*******5
(bootloader) imei: 354********5
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3796mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
and it always stuck in fast boot

vaspraveen said:
Hello
I was just doing the trail and error to install custom rom by reading some articals. may be i was stupid not paying much attention to what exactly it says. i was happy that i was able to unlock the bootloader and installed the twrp custom recovery everything works fine till now, phone booted to Android too. and when i wanted the recovery its taken me to twrp recovery. here here i have done something and now i have completely lost the phone. now i ended up with tampered relocked and security warning and more over my phone always boots in to fastboot mode only. i can't either go twrp or Android just the fast boot. how can i come out of this mess.
my phone is HTC one bought in India no network lock. any help will be appreciated greatly.
Device details
bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.707.151
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA*******5
(bootloader) imei: 354********5
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 3796mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
and it always stuck in fast boot
Click to expand...
Click to collapse
You either wiped /system or formatted /data hence why you can't boot in your OS anymore...
Flashing custom software (recovery, roms, kernels) requires an unlocked bootloader (like you already know) but booting custom softwares also requires an unlocked bootloader, that's why you can't access twrp anymore now that it'S relocked, even if it's still there on your phone.
Flash the 7.19.707.151 RUU, your phone will be back to 100% stock and from there you'll be able to unlock your bootloader again, flash twrp and a rom. There is a sticky thread in the general section (lolliopop ruu collection), you'll find instructions how to flash the ruu there.

alray said:
You either wiped /system or formatted /data hence why you can't boot in your OS anymore...
Flashing custom software (recovery, roms, kernels) requires an unlocked bootloader (like you already know) but booting custom softwares also requires an unlocked bootloader, that's why you can't access twrp anymore now that it'S relocked, even if it's still there on your phone.
Flash the 7.19.707.151 RUU, your phone will be back to 100% stock and from there you'll be able to unlock your bootloader again, flash twrp and a rom. There is a sticky thread in the general section (lolliopop ruu collection), you'll find instructions how to flash the ruu there.
Click to expand...
Click to collapse
Hello Alray
Thank you for the suggestion, the problem is i can only use fastboot USB and nothing else as it is not allowing me. any suggestions how i can flash .zip ruu. some times it says signature error. and also am getting this ROM 7.21.707.105 is this not good, i am new to this post and was unable to find the one you suggested.

Need help.. Bricked after firmware flash only fastboot with black screen

I need help with my old HTC One 802w which was kept in dark for long time, picked 2 days ago to just play with and bricked after may be wrong firmware flash, I attempted flash due to network signals issue (This was the reason to retire it earlier.) Below are the details of what happened, hope someone guide me to revive it or is it just a paper weight now..?
getvar all, when phone was working.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: T3.16.1229.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.15.1403.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: 123456789012
(bootloader) imei: xxxxxxx (sensored)
(bootloader) meid: 00000000000000
(bootloader) product: m7cdtu
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN078****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(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!
This is what i did with this in attempt to update...
1: Changed the mid from PN078**** to PN071000
Tried to flash following which failed everytime with "wrong device id" even before changing mid as well as after changing.
PN07IMG_M7C_DUG_K443_SENSE60_MR_HTC_Europe_6.13.401.3_Radio_1237.28.35.0516_release_391892_signed.zip
PN07IMG_M7C_DTU_L50_SENSE60_MR_HTCCN_CHS_CMCC_7.19.1403.31_Radio_1237.29.35.0903_release_426134_signed.zip
This what I flashed and phone bricked..
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Phone now is with blacked out display in fastboot mode.
fastboot can only pull this info...getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: (Sensored) I noticed that phone imei is changed too, not the same when it was working.)
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3489mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Note: I unlocked bootloader from HTCdev 2 days ago and re-locked to flash stock firmware.
with TWRP recovery twrp-3.0.2-0-m7cdtu, S-OFF, bootloder re-locked.
I was unable to unlock re-locked bootloader with "fastboot oem unlock".
Phone is showing in fastboot as "????????????? fastboot"
Any chance to get it back to life..? Appreciate any help. Thanks.

shahper1 said:
I need help with my old HTC One 802w which was kept in dark for long time, picked 2 days ago to just play with and bricked after may be wrong firmware flash, I attempted flash due to network signals issue (This was the reason to retire it earlier.) Below are the details of what happened, hope someone guide me to revive it or is it just a paper weight now..?
getvar all, when phone was working.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: T3.16.1229.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.15.1403.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: 123456789012
(bootloader) imei: xxxxxxx (sensored)
(bootloader) meid: 00000000000000
(bootloader) product: m7cdtu
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN078****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(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!
This is what i did with this in attempt to update...
1: Changed the mid from PN078**** to PN071000
Tried to flash following which failed everytime with "wrong device id" even before changing mid as well as after changing.
PN07IMG_M7C_DUG_K443_SENSE60_MR_HTC_Europe_6.13.401.3_Radio_1237.28.35.0516_release_391892_signed.zip
PN07IMG_M7C_DTU_L50_SENSE60_MR_HTCCN_CHS_CMCC_7.19.1403.31_Radio_1237.29.35.0903_release_426134_signed.zip
This what I flashed and phone bricked..
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Phone now is with blacked out display in fastboot mode.
fastboot can only pull this info...getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: (Sensored) I noticed that phone imei is changed too, not the same when it was working.)
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3489mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any chance to get it back to life..? Appreciate any help. Thanks.
Click to expand...
Click to collapse
The RUU you were able to flash is not for compatible with your phone. Your phone, the dual-sim variant ''M7CTDU', despite having the same commercial ''HTC One'' name and similar product code ID is a completely different phone from the ''M7_UL'' .
The M7_UL RUU was accepted by your phone as a valid firmware because it passed CID check (because your phone having superCID 11111111) and MID check because the PN0710000 is the correct MID for that version. Your case is unfortunately a good example why S-OFF isn't for everyone.
You now have an incompatible bootloader on your phone, maybe corrupt partitions as well. Now you wont be able to flash the correct ruu using fastboot. Maybe jtag is an option but probably won't worth the money for a 6+ years old phone.
Note: I unlocked bootloader from HTCdev 2 days ago and re-locked to flash stock firmware.
with TWRP recovery twrp-3.0.2-0-m7cdtu, S-OFF, bootloder re-locked.
I was unable to unlock re-locked bootloader with "fastboot oem unlock".
Phone is showing in fastboot as "????????????? fastboot"
Click to expand...
Click to collapse
-You don't need to re-lock the bootloader to flash stock firmware if your phone is s-off, only if it's s-on.
-fastboot oem unlock can't be used to unlock the bootloader, you have to pull your identifier_token, submit it to htcdev.com and flash the Unlock_code received from htcdev

alray said:
The RUU you were able to flash is not for compatible with your phone. Your phone, the dual-sim variant ''M7CTDU', despite having the same commercial ''HTC One'' name and similar product code ID is a completely different phone from the ''M7_UL'' .
The M7_UL RUU was accepted by your phone as a valid firmware because it passed CID check (because your phone having superCID 11111111) and MID check because the PN0710000 is the correct MID for that version. Your case is unfortunately a good example why S-OFF isn't for everyone.
You now have an incompatible bootloader on your phone, maybe corrupt partitions as well. Now you wont be able to flash the correct ruu using fastboot. Maybe jtag is an option but probably won't worth the money for a 6+ years old phone.
-You don't need to re-lock the bootloader to flash stock firmware if your phone is s-off, only if it's s-on.
-fastboot oem unlock can't be used to unlock the bootloader, you have to pull your identifier_token, submit it to htcdev.com and flash the Unlock_code received from htcdev
Click to expand...
Click to collapse
Thanks alot for the detailed reply, I never used HTC phones that much so didn't have much of info to be at safe side while flashing.
You are right its not worth it to spend that much effort for 6 years old phone and this was the reason only for me to be so careless and there is also not much support anymore online for One M7.
Anyway, appreciate your time and support.
By the way, I relocked the unlocked bootloader which I did from HTCDev only. So oem unlock should work on re-locked bootloader..?