[SOLVED] HTC M7 Bricked, Stuck in bootloader (?)

Helllooo

I think i bricked my HTC One.

The only thing i can acces is the Bootloader (or atleast I think its the bootloader, where you can get fastboot and such).

I tried several RUU's but got some errors, neither do I see an Image version when i try too update. (see attachment RUUnon)


Some info:

C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT368W904335
(bootloader) imei: ********************
(bootloader) meid: 00000000000000 (?) I don't think this is correct?
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.051s

in the bootloader i see

*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.22.3263.03
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Nov 27 2013, 19:12:38. 9505

RUU's i tried :

RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1 I get ERRO R[131]: Customer-ID False

RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed Installer won't work. installer error

RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4 When i open this one, nothing happens..

RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2 Getting error 155 Means something with relocking.. but its already relocked.

RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2 error 155...

nkk71 said:

there is no ruu for your version (MID + CID), so unlock your bootloader again (using HTCdev), then flash a custom recovery, and install a ROM

check the Frequently Asked Question sticky page 3
for details of flashing custom recovery and pushing a ROM.zip to your phone

Click to expand...

Click to collapse

Hey,

Thanks for the answer, but can i do this from the bootloader? As i cant do anything else then watch the beautifull bootloader screen.

Yesterday i tried to push a RUU.zip trough fastboot but got an error not sure which one. Could that be because of my relocked bootloader?

Thanks again, gonna try it a.s.ap.

Got custom recovery working. Now im trying to push the rom to sdcard.

First tried ADB Sideload got an error ;
C:\adb\platform-tools>adb sideload Android_Revolution_HD-One_71.1.zip
* failed to write data 'protocol fault (no status)' *

Now trying with ; C:\adb\platform-tools>adb push Android_Revolution_HD-One_71.1.zip /sdcard gave me Protocol Failure great!...

now trying some stuff with the HTC One Toolkit v3.1.2.

Sideload > nope
Now pushing

sending: 'sideload' 84%
* failed to write data 'protocol fault (no status)' *

Every f*ckng time ffs ...

majmoz said:

When you are using these commands is the phone in Recovery? ADB commands work in Recovery! For sideload to work while in TWRP select Advance then Select ADB Sideload. If your PC is commicating with your phone, you can copy the file from the PC to phone.

Click to expand...

Click to collapse

Yeah adb commands work in recovery, and sideload commands work in the sideload menu.. but cant sideload nor push anything to phone.

I pushed the rom to my mobile overnight on accident, fell asleep. And when i woke up. It was still sending but no errors rofl.

And again

C:\adb\platform-tools>adb sideload rom.zip
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *

this is getting frustrating af

nateboi81 said:

Why dont you adb push the file to your phone in recovery

Click to expand...

Click to collapse

Because that doesnt work as i said..

I have just wiped some stuff trough TWRP Advanced wipe. I can mount /data now again but cant get in the sd card trough pc unfortunately.


Pushing the rom again trough adb.

Could it be a corrupted zip ?

FINALLY ITS INSTALLING!

Guess formatting data was doing the trick ! But didn't read that anywhere tho

Ok got it working again, thanks all

Sent from my HTC One using XDA Free mobile app

Didn't know it wouldn't till I tried to wipe everything



Sent from my HTC One using XDA Free mobile app