Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,768,772 Members 52,820 Now Online
XDA Developers Android and Mobile Development Forum

HTC One M7 brick got even worse!

Tip us?
 
ciyomh
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: May 2014
Default HTC One M7 brick got even worse!

I have posted a thread about bricking my HTC One a few days ago and actually , I got it finally fixed today with the help of SaHiLzZ!
First of all , thanks man for helping me.
Here's the first thread that I have opened if anyone is interested:
http://forum.xda-developers.com/show...php?p=52747826

I was finally able to get past the HTC boot logo and use the phone but I also wanted to update the ROM to KitKat 4.4.
I have changed my CID to HTC__001 from HTC__K18 with no effort , however , I failed to change my MID to PN0710000.
I followed this tutorial step by step (http://forum.xda-developers.com/show....php?t=2322820) , but when I applied the fastboot oem writemid command , there was an unknown error and when I rebooted the phone I got the exact same screen as this:


Now , I'm unable to access anything!!! I can't even get to the bootloader or recovery which was possible with the soft brick. The only 2 screens that I am able to get now is the gray screen as in the picture above , or a complete black screen (and the device still stays on).
I'm unable to use any adb commands , but fastboot commands still work. However , I'm unable to flash any RUU , rom , CWM , TWRP , boot...
Is there's anything I can do about it?
Here's an output of the fastboot getvar all:


Anyone have any idea what can I possibly do to fix this?
 
SaHiLzZ
Old
#2  
Senior Member
Thanks Meter 409
Posts: 1,703
Join Date: Jan 2011
You are on eng hboot. And your device is responding in ruu mode. Run the ruu as long as your fastboot is working.
The Following User Says Thank You to SaHiLzZ For This Useful Post: [ Click to Expand ]
 
ciyomh
Old
#3  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: May 2014
Quote:
Originally Posted by SaHiLzZ View Post
You are on eng hboot. And your device is responding in ruu mode. Run the ruu as long as your fastboot is working.
I tried it , I used the RUU that fixed the soft brick but it didn't work this time.
It can't get past the bootloader stage because it tries to access the bootloader but with no success.
 
nkk71
Old
#4  
nkk71's Avatar
Recognized Contributor
Thanks Meter 2782
Posts: 5,619
Join Date: May 2010
Location: Beirut
Quote:
Originally Posted by ciyomh View Post
I tried it , I used the RUU that fixed the soft brick but it didn't work this time.
It can't get past the bootloader stage because it tries to access the bootloader but with no success.
I didn't understand, is this a continuation of the other thread, or did you get any further? a bit more details please.
 
ciyomh
Old
#5  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: May 2014
Quote:
Originally Posted by nkk71 View Post
I didn't understand, is this a continuation of the other thread, or did you get any further? a bit more details please.
It got worse but I was finally able to change my MID and fix it. After that I reinstalled RUU 1.29.401.2 (I tried to install anything newer but nothing worked , only this one).
I can use my device regullary now.
I have supercid , mid PN0710000 and JB 4.1.2 on my device.
But the problem now is that I'm unable to update the device using any newer RUU (that match the new mid of my device).
I also don't have superuser or working recovery , when I try to flash recovery , I get this error:
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8758 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s

I've tried to flash a few different recoveries but I get this same Unknown error everytime.
How is it possible for me to update from 4.1.2 to 4.4.2/4.4 if I get this same error every time and with no superuser access when every .exe RUU install fails too?
 
nkk71
Old
#6  
nkk71's Avatar
Recognized Contributor
Thanks Meter 2782
Posts: 5,619
Join Date: May 2010
Location: Beirut
Quote:
Originally Posted by ciyomh View Post
It got worse but I was finally able to change my MID and fix it. After that I reinstalled RUU 1.29.401.2 (I tried to install anything newer but nothing worked , only this one).
I can use my device regullary now.
I have supercid , mid PN0710000 and JB 4.1.2 on my device.
But the problem now is that I'm unable to update the device using any newer RUU (that match the new mid of my device).
I also don't have superuser or working recovery , when I try to flash recovery , I get this error:
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8758 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s

I've tried to flash a few different recoveries but I get this same Unknown error everytime.
How is it possible for me to update from 4.1.2 to 4.4.2/4.4 if I get this same error every time and with no superuser access when every .exe RUU install fails too?
Can you
1- post an updated "fastboot getvar all" (copy/paste would be better than screenshot),
2- a screenshot of your bootloader screen
3- what recovery are you flashing above? have you checked MD5, cause the filesize looks a bit small,
4- try using a different USB port / PC.
Attached Thumbnails
Click image for larger version

Name:	Screenshot Command Prompt.jpg
Views:	27
Size:	54.9 KB
ID:	2753594  
The Following User Says Thank You to nkk71 For This Useful Post: [ Click to Expand ]
 
ciyomh
Old
#7  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: May 2014
Quote:
Originally Posted by nkk71 View Post
Can you
1- post an updated "fastboot getvar all" (copy/paste would be better than screenshot),
2- a screenshot of your bootloader screen
3- what recovery are you flashing above? have you checked MD5, cause the filesize looks a bit small,
4- try using a different USB port / PC.
Thank you mate! I tried using a different USB port and it actually worked!
Although I have no idea why should it work but haha it doesn't matter to me.
I have recovery and superuser as well now but I'm still stuck in JB 4.1.2.
I've tried flashing One_4.19.401.11_odexed.zip through recovery and it failed , then I got a mini brick and the phone didn't turn off no matter what I did for a few hours.
Then I see this craziest fix ever , I stuck it in front of a lightbub while holding power + Vol down for about 15 seconds and it worked! lol!
I'm now able to use it , but can't update it in any possible way.
I tried using an .exe RUU of KK4.4 but it didn't work as well (and it was compatible with my mid + cid).
Any idea what can I do to update my device to 4.4.2/4.4 from 4.1.2? I have access now to everything , the android , recovery , supersu , adb ,fastboot..

Thank you!
 
nkk71
Old
#8  
nkk71's Avatar
Recognized Contributor
Thanks Meter 2782
Posts: 5,619
Join Date: May 2010
Location: Beirut
Quote:
Originally Posted by ciyomh View Post
Thank you mate! I tried using a different USB port and it actually worked!
Although I have no idea why should it work but haha it doesn't matter to me.
I have recovery and superuser as well now but I'm still stuck in JB 4.1.2.
I've tried flashing One_4.19.401.11_odexed.zip through recovery and it failed , then I got a mini brick and the phone didn't turn off no matter what I did for a few hours.
Then I see this craziest fix ever , I stuck it in front of a lightbub while holding power + Vol down for about 15 seconds and it worked! lol!
I'm now able to use it , but can't update it in any possible way.
I tried using an .exe RUU of KK4.4 but it didn't work as well (and it was compatible with my mid + cid).
Any idea what can I do to update my device to 4.4.2/4.4 from 4.1.2? I have access now to everything , the android , recovery , supersu , adb ,fastboot..

Thank you!
Those 4.4 RUUs are very "sensitive", no idea why sometimes they work, and other times give people a hard time (could be anything OS, antivirus, bad download, USB port, etc)

Why didnt you just take the OTAs to 4.4, before installing custom recovery and root? just reflash the 1.28.401.7 ruu.zip, and take OTAs to 4.4.2 then install custom recovery and root

with S-Off, you can keep bootloader unlocked, no need to relock it or anything; as mentioned in the "Not so FAQ #2" here: http://forum.xda-developers.com/show...24&postcount=2

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes