HELP - BRICKED One!

Search This thread

targett

Senior Member
Apr 8, 2009
461
15
I was flashing a new rom onto my HTC One today and my daughter got hold of it (Age 3) whilst my back was turned and has wiped the ROM completely!

I have TWRP v2.7.1.1 touch bootloader but I cant get a ROM installed - fastboot won't recognise that there is a device attached even though I get the 'connected sound' when I connect to my windows 8 laptop. I have searched for all the fastboot and adb solutions but have come to a dead end!

I think its dead! :crying:

Fastboot usb shows on the phone screen when connected though
the OS - on the fastboot screen shows blank too!

*** TAMPERED ***
*** RELOCKED ***
M7_ PVT SHIP S_ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 21 2013,22:50:54.0


Can anyone help?
 

cuyo11

Senior Member
May 26, 2010
204
42
Portland
lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.

It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://xdaforums.com/showthread.php?t=2544146

btw what problem do you have when installing the rom via recovery?
 

targett

Senior Member
Apr 8, 2009
461
15
lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.

It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://xdaforums.com/showthread.php?t=2544146

btw what problem do you have when installing the rom via recovery?

"C:\android-tools>fastboot devices
HT34PW913345 fastboot"​

CID = HTC__001

I can attempt to flash a .zip rom (same recovery number = stock 5.11.401.10) but it fails!
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.432s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 179.412s​

I cant flash a different recovery anymore I presume as my bootloader is "RELOCKED" and I can't work out how to unlock it. HTCDev can't unlock it.

C:\android-tools>fastboot flash recovery recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.187s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.141s​

What is "bootloader signature checking"? How do I resolve that problem of FAILED?

I can access the RUU screen successfully
[INDENTC:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.187s]
finished. total time: 0.234s][/INDENT]

but when I try to flash a .zip it doesn't work still
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 44.000s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 159.127s​

Anyone have any ideas of how to get the signature checking to work?
 

targett

Senior Member
Apr 8, 2009
461
15
I have managed to unlock again using my Unlock_code.bin file but it still fails to load the .zip ROM

C:\android-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.172s

C:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.172s

C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.874s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.203s​
 

targett

Senior Member
Apr 8, 2009
461
15
I have now managed to load ClockworkMod Recovery v6.0.4.6

I have found I can't mount the /sdcard

I guess that's where my problem lies? If my phone has forgotten how to find /sdcard then how can it flash to it?
 

targett

Senior Member
Apr 8, 2009
461
15
Check this http://xdaforums.com/showthread.php?t=2228274&page=3

then let me know if you have any questions.

I have wiped the system and cache just in case and am attempting the sideload but when i do the "adb devices" it doesn't sow my device number, where it does if in fastboot.


G:\adb>adb devices
List of devices attached


And when I attempt at adb sideload I get this

G:\adb>adb sideload One_5.11.401.10_odexed.zip
error: device not found​
Stuck again :crying:

Oh - How important is the USB OTG in the adb sideload
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
Sorry for being so stupid! I feel like a noob on this device (not flashed or rooted in about 3 years!)

Reading it all again I see I need S-Off. My Security is ON. and I can't turn it off as I can't install SuperSU or Superuser or anything at all.
Any thoughts?

sorry, i don't follow. it has nothing to do with s-on or s-off.

you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it
 

targett

Senior Member
Apr 8, 2009
461
15
sorry, i don't follow. it has nothing to do with s-on or s-off.

you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it

Sorry!

I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.

I'm now installing the 'sideload.zip' Wish me luck!


Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
Sorry!

I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.

I'm now installing the 'sideload.zip' Wish me luck!


Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!

Good Luck :good: :good: