[Q] HTC One M7 disaster - One (M7) Q&A, Help & Troubleshooting

Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
Here informations you might need
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4138mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.

Rave201 said:
Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
Here informations you might need
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Click to expand...
Click to collapse
usb debugging has nothing to do with the bootloader, adb or fastboot, it is only required to be on when you want to mod something or control your phone using adb commands inside a booted rom, as you cant boot, then that's not an option.
if your bootloader is locked and you have warranty, send it back, because if you unlock your bootloader then your warranty will be void and you'll have to pay for repairs.

Hi there & thnx for your concern,
The warranty is not an option , cause I bought it in another country and have no service support here.
For the usb debugging mode , as far as I know , it needs to be "on" so the smartphone can be connected to adb.
I looked on the net how to turn it on without having access to android I got some command but I need an android command-line shell to make it work , wich is not an option right now.
I'm all open for suggestions.

Is there a way to get out of fastboot and try load the android again ?
I tried turn power down but it opens fastboot automaticly,
I tried
Code:
fastboot reboot
same result as above .

Rave201 said:
Is there a way to get out of fastboot and try load the android again ?
I tried turn power down but it opens fastboot automaticly,
I tried
Code:
fastboot reboot
same result as above .
Click to expand...
Click to collapse
only thing you can do is unlock your bootloader, try again, get a new unlock token from HTC Dev.
by the way, adb commands are only for in a rom or in recovery, use fastboot commands only in the bootloader, if you cant unlock the bootloader then theres not a lot you can do.
could you post your fastboot getvar all please, remove imei and serial number information before posting, maybe there is an RUU we can run.

Rave201 said:
Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Click to expand...
Click to collapse
boot the phone to the bootloader / Fastboot USB
plug the phone to the PC and Flash this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
If you get an Error flashing 155 etc)
flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/4.19.401.8.zip
place the file in your fastboot folder on your PC and rename it firmware.zip and flash it with a command prompt
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Now try the RUU again

clsA said:
boot the phone to the bootloader / Fastboot USB
plug the phone to the PC and Flash this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
If you get an Error flashing 155 etc)
flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/4.19.401.8.zip
place the file in your fastboot folder on your PC and rename it firmware.zip and flash it with a command prompt
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
lol how I missed that I don't know

Thanks ! : downloading , I'll leave answer after I test.

Hi again ;
So I downloaded and followed the steps I got errors :/
on the RUU flash I got Error 171 at "Bootloader waiting" and later saying that it couldn't connect to the device . It did connect to it in the first place though and device rebooted and so .
So I followed the second parts and I got errors aswell :
Code:
c:\mini-sdk>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(862): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.016s]
finished. total time: 0.016s
c:\mini-sdk>fastboot flash zip firmware.zip
sending 'zip' (43508 KB)...
OKAY [ 2.870s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 6.538s
Any help please

anyone ?

Rave201 said:
anyone ?
Click to expand...
Click to collapse
bootloader needs to be locked / relocked to flash the RUU or firmware as your s-on.
"fastboot oem lock" is the command without quotes.

Hi there, I did it already , it says device already locked.

Rave201 said:
Hi there, I did it already , it says device already locked.
Click to expand...
Click to collapse
soz about that, just realised, had a read back through the whole thread to catch up, right, 171 is a USB connection error, so when your phone is in the bootloader, plugged into the computer with fastboot usb showing, have a look in device manager and make sure your computer can see your phone and that you dont have anything like "One" with a yellow exclamation mark.
sounds like a driver problem to me, but are you using the original HTC cable too ?

Seanie280672 said:
soz about that, just realised, had a read back through the whole thread to catch up, right, 171 is a USB connection error, so when your phone is in the bootloader, plugged into the computer with fastboot usb showing, have a look in device manager and make sure your computer can see your phone and that you dont have anything like "One" with a yellow exclamation mark.
sounds like a driver problem to me, but are you using the original HTC cable too ?
Click to expand...
Click to collapse
Yeah , well I tried like 4 drivers already , fastboot usb is indeed showing, and the RUU does restart the device , but when waiting for bootloader nothing shows =/
Tried with different pc too with different compatiblities.
Only thing left to try is another cable.
Thnx for following up

Rave201 said:
Yeah , well I tried like 4 drivers already , fastboot usb is indeed showing, and the RUU does restart the device , but when waiting for bootloader nothing shows =/
Tried with different pc too with different compatiblities.
Only thing left to try is another cable.
Thnx for following up
Click to expand...
Click to collapse
what I meant was when fastboot usb is showing, have a look in windows device manager and make sure it see's your phone, should say MyHTC.
only drivers you need which have never let me down, even on Windows 10 is HTC sync manager, just download and install the latest version from the HTC site, I would uninstall all current phone drivers first, then run a cleaner like CCleaner to remove old files, reboot computer then install HTC sync manager, after the install, un-install HTC sync, just leaving HTC driver package above it alone.
make sure your phone is unplugged when doing the above, leave your phone in the bootloader, and when you have finished the last step of un-installing HTC sync, then plug your phone into the computer and let it load the fastboot driver, thats the main one you need right now.

Hi again , So I tried everything above and nothing , took the device to a guy who's good in repairing and flashing devices and couldn't flash it neither.
for a radical solution , should I change the whole mainboard or there is a specific part ?

Rave201 said:
Hi again , So I tried everything above and nothing , took the device to a guy who's good in repairing and flashing devices and couldn't flash it neither.
for a radical solution , should I change the whole mainboard or there is a specific part ?
Click to expand...
Click to collapse
It's a 2 year old phone, it's really only worth fixing if you already have the parts for free.
This phone sells for $149 New in the US, and even cheaper used on eBay.

Thanks for the advice , but more objectively Motherboard or a specific part ?
Parts here are pretty cheap compared. And I can't afford a new one actually.

Rave201 said:
Thanks for the advice , but more objectively Motherboard or a specific part ?
Parts here are pretty cheap compared. And I can't afford a new one actually.
Click to expand...
Click to collapse
SD_HW_ERROR = probably a defective emmc. You can't replace the emmc chip, its soldered directly on the Motherboard so you will indeed need to replace the motherboard but like clsA said it really doesnt worth it. You can get a new M7 for 150$. HTC sells their Motherboard around 100$ + you'll probably need to replace the body like many users who tried to open the phone themselves (very fragile around the volume rockers). Even if I love my M7, I wouldn't spent 100$ to replace the MB.
And buying a used motherboard is not a good idea. You don't know if its working good + you don't know if the IMEI is blacklisted.

Thanks for the explanation alray, I excpected the fail in the emmc too cause read_mmc emmc didn't work.
Anway I don't live in the us . Here though, a new one cost roughly 300 $ and the motherboard is about 80$ or less.
Thanks again

Related

Can not write anything via Fastboot and Phone is in Bootloop :( kindly Help!

I am unable to write any thing via bootloaders (i.e. recovery, zip, ruu etc) i have also tried to restore my phone via RUU...setup is shutting down the device but do not boot it up again in bootloader so the setup could proceed with flashing the RUU (as it suppose to)... i m uploading the cmd screen shot for your kind perusal, kindly help me out as well please...
these steps i have tried as yet:
tried (fastboot flash recovery twrp.img)
Tried Flashing OTA firmware (fastboot update firmware.zip)
Tried RUU.exe setup
i can not even flash recovery... whenever i attempt to do so it gives an error as attached!
seems like some sort of security has been activated but can be a hardware issue as well... Please HELP!
Please advise what should i do or what can be done in this matter
Have you tried fastboot erase cache
Sent from my HTC One using XDA Premium 4 mobile app
Try going s off
Sent from my GT-I9305 using xda app-developers app
bored_stupid said:
Have you tried fastboot erase cache
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did... command is not implementing... giving out same error as on recovery flsah!
Thanks... will appreciate more help...
nateboi81 said:
Try going s off
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
i have tried that...
my set is only responding to informational commands like getvar info, device info etc but its not implementing the commands which will write something on internal memory...
s-off = Security off right?
i believe some sort of security has been triggered!
?
Any One please....
Just a couple of shots in the dark.. disable any antivirus also check you have latest fastboot maybe download latest android sdk which will have it and try again.
Try another pc or cable.
Sent from my HTC One using Tapatalk
Mortal Eternity said:
Any One please....
Click to expand...
Click to collapse
are you using USB 3 port/hub, check Device Manager connections... if the "main" (internal) port-structure is USB 3 based, then that could be the problem.
PS: and what version does adb devices give?
nkk71 said:
are you using USB 3 port/hub, check Device Manager connections... if the "main" (internal) port-structure is USB 3 based, then that could be the problem.
PS: and what version does adb devices give?
Click to expand...
Click to collapse
I can offer 20$ for who ever can help me fix my set please...(i know its too low but its all i have for now and i need my cellphone fixed to sale it)
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35FW902658
(bootloader) imei: 355972054420881
(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: 4157mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.342s
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>
Mortal Eternity said:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.342s
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>
Click to expand...
Click to collapse
what was the last thing the phone had on it ? I see the bootloader is unlocked so did it already have a custom recovery ? custom rom ? Rooted ?
have you turned the phone completely OFF holding the powerbutton and volume up and down for 2 min ?
did you try a factory reset with stock recovery ?
when you tried the RUU.exe what was the error and what file did you try ?
clsA said:
what was the last thing the phone had on it ? I see the bootloader is unlocked so did it already have a custom recovery ? custom rom ? Rooted ?
have you turned the phone completely OFF holding the powerbutton and volume up and down for 2 min ?
did you try a factory reset with stock recovery ?
when you tried the RUU.exe what was the error and what file did you try ?
Click to expand...
Click to collapse
thats how i messed my set up: i was on TWRP 2.6.3.3 which was working perfectly fine then i thought it would be better if i'd flash a latest recovery so flashed 2.7.0.4 then i tried to flash latest build of insertcoin with that messed up recovery which got me stuck on 7% while flashing the rom, so i restarted by set after waiting for 5 minutes or so... then i tried going in to recovery again and tried to do a factory data reset to reflash the rom... recovery stuck on factory data rest n made me reboot my set... since then the situation is same for me
i did the 2 minutes trick, since my phone is not hard bricked so its just making the set booting again and again in fastboot mode thats it!
yes i did factory reset but with twrp then i got stuck at where i m now... plus i m unable to flash anything on emmc since then...
when i tried RUU.exe the setup shut my phone down but do not restart it in fastboot mode (how it should) i tried to boot my phone manually but didnt help...
Please advice any thing else
2.7.0.4 is for Sprint
Can you force the phone into fastboot oem rebootRUU and try and flash from their?
you can extract the signed Rom.zip from the RUU and flash it that way
the Rom.zip will be in c:\users\yourusername\appdata\local\temp\somerandomfolderthatwasjustcreated (sort by date)(also you have to view hidden folders to see appdata in the user folder)
mine was here "C:\Users\Cliff\AppData\Local\Temp\{A3096E6D-C55A-4EA1-B6B1-1E95174B190C}"
clsA said:
2.7.0.4 is for Sprint
Can you force the phone into fastboot oem rebootRUU and try and flash from their?
you can extract the signed Rom.zip from the RUU and flash it that way
the Rom.zip will be in c:\users\yourusername\appdata\local\temp\somerandomfolderthatwasjustcreated (sort by date)(also you have to view hidden folders to see appdata in the user folder)
mine was here "C:\Users\Cliff\AppData\Local\Temp\{A3096E6D-C55A-4EA1-B6B1-1E95174B190C}"
Click to expand...
Click to collapse
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
No i can't bro... it says this when i tried to run the command:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.060s]
finished. total time: 1.061s
Thank you for helping me...
Mortal Eternity said:
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
No i can't bro... it says this when i tried to run the command:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.060s]
finished. total time: 1.061s
Thank you for helping me...
Click to expand...
Click to collapse
I think your emmc has bad sectors. Whats wrong with htc one? So many bricks because of bad dmmc chip. Jesus
Mortal Eternity said:
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
No i can't bro... it says this when i tried to run the command:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.060s]
finished. total time: 1.061s
Thank you for helping me...
Click to expand...
Click to collapse
Have you at least tried a different PC and/or OS? I remember one guy having tonnes of problems (and we spent hours on teamviewer too), not being able to get anything to work, until we found out that even his USB2 port is based on an internal USB3 connection... he then used a different PC and was up and running again!
Mortal Eternity said:
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
...
Click to expand...
Click to collapse
Thanks for posting the link .. i was not aware of that file.
I think I would still try and flashback to 2.6.3.3 ... if you can get back in TWRP
try this file >> https://www.dropbox.com/s/n49t43thctnl02a/TWRP_2.6.3.3_m7.zip
clsA said:
Thanks for posting the link .. i was not aware of that file.
I think I would still try and flashback to 2.6.3.3 ... if you can get back in TWRP
try this file >> https://www.dropbox.com/s/n49t43thctnl02a/TWRP_2.6.3.3_m7.zip
Click to expand...
Click to collapse
recovery is not accessible... when ever i select the recovery option the set gets unresponsive
can't even factory data reset my phone... sent an email to htc saying if they can replace my set i will pay 100$ t has been 2 days, still waiting for their reply...
lets hope for best :fingers-crossed:
nkk71 said:
Have you at least tried a different PC and/or OS? I remember one guy having tonnes of problems (and we spent hours on teamviewer too), not being able to get anything to work, until we found out that even his USB2 port is based on an internal USB3 connection... he then used a different PC and was up and running again!
Click to expand...
Click to collapse
thanks for your suggestion but its not the cable or port issue i have tried 5 different pcs... i have even visited local market for solution... no one has any solutions for this as yet... but there are many phones with same case... it seems like a hardware flaw at htc's end.
p.s. i m really very thankfull to people who are trying to help me!
darksnoopy said:
I think your emmc has bad sectors. Whats wrong with htc one? So many bricks because of bad dmmc chip. Jesus
Click to expand...
Click to collapse
yes it seems like a common issue to me now... lets hope htc will take some precaution while making such expensive phones...
Mortal Eternity said:
yes it seems like a common issue to me now... lets hope htc will take some precaution while making such expensive phones...
Click to expand...
Click to collapse
Tell me about it! I got an new m7 again (i hate m8 design) but this time i am not going to unlock boot loader not going to s-off and not going to install custom recovery!
This is the thread with the problem i had with my first m7. I haven't quit, still trying to fix it and give it away. Maybe we should make a sticky thread with all those people with problem like this!
http://forum.xda-developers.com/showthread.php?t=2685024&page=3

[Q] Seemingly strange soft brick happening to my phone

Hey guys, I've tried searching everywhere for info related to my situation, but couldn't find any...hopefully someone here will be able to help.
This all started earlier today, when I was using my phone (AT&T, m7, converted to GPE) as normal. I was at work, browsing Facebook or whatever, when suddenly I got a quick notification that Gapps had force closed. A few seconds after that, the phone suddenly restarted.
From there, I noticed the Google splash logo had a strange pixelated band across it, as shown in the attached photo.
Then it proceeded to bootloop.
After trying a couple basic things, none of them succeeded, and I decided to just wait until I got home, at which point I tried to enter recovery. It took me to the bootloader, which looked pretty weird, as it had a bunch of jumbled letters in the options, also shown in the attached photo.
From there, all I could get to was stock recovery. I tried flashing TWRP, but it wouldn't recognize ADB, and then I tried to flash using fastboot. Fastboot would accept the commands "./fastboot devices" (which recognized that my phone was connected) and "./fastboot getvar all." Any other command, including "./fastboot flash recovery" would give me the error "FAILED (remote: not allowed)".
I'm now at a loss. As you can see in the photos, my bootloader is unlocked, with S-OFF. I have no idea how to recover from this.
Any suggestions? Thanks.
Oh, also, I'm on a Mac, with Yosemite.
jon_marfrag said:
Hey guys, I've tried searching everywhere for info related to my situation, but couldn't find any...hopefully someone here will be able to help.
This all started earlier today, when I was using my phone (AT&T, m7, converted to GPE) as normal. I was at work, browsing Facebook or whatever, when suddenly I got a quick notification that Gapps had force closed. A few seconds after that, the phone suddenly restarted.
From there, I noticed the Google splash logo had a strange pixelated band across it, as shown in the attached photo.
Then it proceeded to bootloop.
After trying a couple basic things, none of them succeeded, and I decided to just wait until I got home, at which point I tried to enter recovery. It took me to the bootloader, which looked pretty weird, as it had a bunch of jumbled letters in the options, also shown in the attached photo.
From there, all I could get to was stock recovery. I tried flashing TWRP, but it wouldn't recognize ADB, and then I tried to flash using fastboot. Fastboot would accept the commands "./fastboot devices" (which recognized that my phone was connected) and "./fastboot getvar all." Any other command, including "./fastboot flash recovery" would give me the error "FAILED (remote: not allowed)".
I'm now at a loss. As you can see in the photos, my bootloader is unlocked, with S-OFF. I have no idea how to recover from this.
Any suggestions? Thanks.
Oh, also, I'm on a Mac, with Yosemite.
Click to expand...
Click to collapse
Ouch, that doesn't look nice at all!!!
are you able to get to RUU mode? "fastboot oem rebootRUU"
if yes then you should flash a full ruu.zip to try and restore your messed up partitions (obviously this will wipe your phone)
nkk71 said:
Ouch, that doesn't look nice at all!!!
are you able to get to RUU mode? "fastboot oem rebootRUU"
if yes then you should flash a full ruu.zip to try and restore your messed up partitions (obviously this will wipe your phone)
Click to expand...
Click to collapse
Nope, getting the same error:
FAILED (remote: not allowed)
finished. total time: 0.002s
Not sure if it helps, but here's the ./fastboot getvar all info it spits back.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.07.154
(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: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4289mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b296905a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Click to expand...
Click to collapse
jon_marfrag said:
Nope, getting the same error:
FAILED (remote: not allowed)
finished. total time: 0.002s
Not sure if it helps, but here's the ./fastboot getvar all info it spits back.
Click to expand...
Click to collapse
yep, doesnt look nice at all in here :crying:
could be a hardware problem... i'll check in tomorrow, can't do this tonight sorry
PS: recommend you also try a different pc (mac, Win7, linux), with up to date adb/fastboot (and if needed [ie Win7] drivers), stay away from USB3 ports or any hubs.... seems hboot is corrupt, and only way to flash that is using ruu mode, or using a custom recovery (TWRP or CWM... even rooted ROM would do)
nkk71 said:
yep, doesnt look nice at all in here :crying:
could be a hardware problem... i'll check in tomorrow, can't do this tonight sorry
PS: recommend you also try a different pc (mac, Win7, linux), with up to date adb/fastboot (and if needed [ie Win7] drivers), stay away from USB3 ports or any hubs.... seems hboot is corrupt, and only way to flash that is using ruu mode, or using a custom recovery (TWRP or CWM... even rooted ROM would do)
Click to expand...
Click to collapse
Great, I appreciate your help!
Yeah, looking like it could be a hardware issue, huh? That's what I was afraid of, especially since it seemed to happen randomly without me doing anything to directly cause it.
I'll try using a different mac tonight (no PCs around me I can borrow that I can think of).
If hboot is corrupted, but I can't do anything but access flashboot and I can't even flash from fastboot, it looks like I might be a little screwed?
jon_marfrag said:
Great, I appreciate your help!
Yeah, looking like it could be a hardware issue, huh? That's what I was afraid of, especially since it seemed to happen randomly without me doing anything to directly cause it.
I'll try using a different mac tonight (no PCs around me I can borrow that I can think of).
If hboot is corrupted, but I can't do anything but access flashboot and I can't even flash from fastboot, it looks like I might be a little screwed?
Click to expand...
Click to collapse
yes, unfortunately, i'm inclined to believe it's a hardware fault (not of your doing!!)
there are only two ways i know of, of "messing"/"fixing" partitions (including hboot <only when s-off>), and those would be
1) ruu mode flash <- highly preferred
2) "dd" <-very bad, if you mistype a single character... boom
and yes,
3) given you current firmware, there may be a way to get somewhere even "worse" or "better" ....
but in all likelihood it's probably a hardware fault, nothing you did wrong
nkk71 said:
yes, unfortunately, i'm inclined to believe it's a hardware fault (not of your doing!!)
there are only two ways i know of, of "messing"/"fixing" partitions (including hboot <only when s-off>), and those would be
1) ruu mode flash <- highly preferred
2) "dd" <-very bad, if you mistype a single character... boom
and yes,
3) given you current firmware, there may be a way to get somewhere even "worse" or "better" ....
but in all likelihood it's probably a hardware fault, nothing you did wrong
Click to expand...
Click to collapse
Okay, here's one little thing I hadn't thought of yet. As I said in my first post, I could get into the Stock Recovery (Android system recovery <3e> KOT49H.H1 release-keys). Also, a few weeks ago I finally bought a USB OTG cable.
Don't know why it took me this long to think about trying it, but I finally realized I should see if the stock recovery could detect a USB drive plugged into the OTG cable when "apply from an SD card" is selected. Of course, it could.
So! That seems like it might be a possible way to flash what I need to flash, correct? If so, what exactly should I try flashing? I'm worried that I'm in a really precarious spot here and I don't want to flash the wrong thing and lose the ability to use even stock android recovery.
Should I try reflashing the bootloader? TWRP? (if it screws up the TWRP flash will I lose stock recovery?) Something else?

"Active cmdline overflow!"

Hi there, I must have flashed the wrong sense ROM. I am extremely noobish, so bare with me.
I tried following this amazing guide: http://forum.xda-developers.com/showthread.php?t=2739126 but have had no luck when it comes to flashing the recovery indicated.
"C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
error: cannot load 'twrp-recovery-2.7-m7-nobcb.img'"
It looks like I entered it right...
My phone will power on and function OK with data and text, but cannot make calls. Sometimes it'll reboot into hboot when I plug it into USB/AC. I have access to fastboot, but not adb, nor recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: `
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35...
(bootloader) imei: 3559...
(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: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time, XDA!
Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk
cyrusct82 said:
Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes and it shows under "fastboot devices"
It's now managed to have gotten worse and will only boot into the spash screen, then Fastboot (not Hboot).
If I remove the sim card, it will boot up normally (unless it's plugged into USB/AC). If I insert the sim, or plug in the microUSB, it will shortly thereafter crash into fastboot.
1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted
nkk71 said:
1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted
Click to expand...
Click to collapse
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!
Enigmatic Fart said:
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!
Click to expand...
Click to collapse
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy
nkk71 said:
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy
Click to expand...
Click to collapse
Cool man, I'll run through and try to flash it again in the meantime and edit this post with results.
Thanks again for your help! Peace!
EDIT: OK, I see what the issue was, but a new one popped up. So I was attempting to flash the recovery I placed in my phone's storage. I now have "TWRP.img" (latest TWRP) and "TWRPnbcb.img" (the no bcb one from that guide) in my adb folder (where fastboot is) on my PC and have attempted to flash both recoveries for S&Gs.
Here are the results:
"C:\Windows\system32>cd C:\adb
C:\adb>fastboot devices
HT35xxxxxx... fastboot
C:\adb>fastboot flash recovery TWRPnbcb.img
sending 'recovery' (11278 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
C:\adb>fastboot flash recovery TWRP.img
sending 'recovery' (12534 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s"
Last ditch bump! I don't want my phone retire in a junk drawer!
Enigmatic Fart said:
Last ditch bump! I don't want my phone retire in a junk drawer!
Click to expand...
Click to collapse
please post a "fastboot oem last_dmesg", after trying to flash something
@alray, might be able to decipher that
(sorry for the ping)

802W China Unicom hard bricked

With my Htc One M7 802w, I tried to flash the stock google edition using this tutorial but I think i've bricked my device - it's almost completely dead - only fastboot is working but it also seems to be unrecognized :
F:\Android\ADB>fastboot devices
???????????? fastboot
Click to expand...
Click to collapse
Not able to go to "fastboot oem rebootRUU" ... the device is not found when sending this command.
Is there anyway to flash the stock ROM without fastboot mode - like some software or brushtool or whatever.
GETVAR:
F:\Android\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.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: 3551*********10 (hide for security)
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3385mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
F:\Android\ADB>fastboot flash hboot hboot_signedbyaa.img
target reported max download size of 452980736 bytes
sending 'hboot' (2047 KB)...
OKAY [ 0.109s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.109s
Click to expand...
Click to collapse
F:\Android\ADB>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
NEED HELP!!!:silly:
hruaiapunte said:
With my Htc One M7 802w, I tried to flash the stock google edition using this tutorial but I think i've bricked my device - it's almost completely dead - only fastboot is working but it also seems to be unrecognized :
Not able to go to "fastboot oem rebootRUU" ... the device is not found when sending this command.
Is there anyway to flash the stock ROM without fastboot mode - like some software or brushtool or whatever.
GETVAR:
NEED HELP!!!:silly:
Click to expand...
Click to collapse
omg looks like you did everything possible to brick your phone. Yuu can't use RUU for the M7_UL on a dual sim phone. Now you have the wrong bootloader, an incorrect MID and a missing CID. You must restore your original MID and CID and flas the correct dual sim RUU.
btw it looks like you missed the last step of your guide:
Step 8: Enjoy S-OFF! But Be Careful...
Having S-OFF will let you trick your HTC One into installing other phones' RUU files. As long as you only install compatible RUUs, you should be fine, but make sure to double check. This is how real bricks happen.
Click to expand...
Click to collapse
alray said:
omg looks like you did everything possible to brick your phone. Yuu can't use RUU for the M7_UL on a dual sim phone. Now you have the wrong bootloader, an incorrect MID and a missing CID. You must restore your orinial MID and CID and flas the correct dual sim RUU.
btw it looks like you missed the last step of your guide:
Click to expand...
Click to collapse
How to flash those original MID and CID? Is there a way to flash via software like ODIN or whatever...not just a fastboot mode? Thanks for your reply
hruaiapunte said:
How to flash those original MID and CID? Is there a way to flash via software like ODIN or whatever...not just a fastboot mode? Thanks for your reply
Click to expand...
Click to collapse
Odin is for samsung not htc. The corrupted CID/MID is probably caused by having the wrong bootloader on the phone. Normally you can change the CID using "fastboot oem writecid" command. The MID can be modified using a custom recovery. The MID might not be a problem for now since its all * but you'll definitively need to access RUU mode to flash the correct RUU
alray said:
Odin is for samsung not htc. corrupted CID/MID is probably caused by having the wrong bootloader on the phone. Normally you can change the CID using "fastboot oem writecid" command. The MID can be modified using a custom recovery. The MID might not be a problem for now since its all * but you'll definitively need to access RUU mode to flash the correct RUU
Click to expand...
Click to collapse
Yes, i know odin is for samsung, what i tried to say is that are there any flash tool, not through fastboot because as i already mentioned, computer cannot detect the device when
fastboot oem rebootRUU
Click to expand...
Click to collapse
command was given. It says
<waiting for device>
Click to expand...
Click to collapse
and i have to disconnect the USB cable. And then press a volume down+power button to enter fastboot mode again (when i perform this, the device does not power up, it for l goes directly to fastboot mode when pressing the key combination). And after plugin, the result was
*i didn't remember some* remote not allowed something like that
Click to expand...
Click to collapse
Anyway thanks for your response. Please give solution.
hruaiapunte said:
Yes, i know odin is for samsung, what i tried to say is that are there any flash tool, not through fastboot because as i already mentioned, computer cannot detect the device when
command was given. It says
and i have to disconnect the USB cable. And then press a volume down+power button to enter fastboot mode again (when i perform this, the device does not power up, it for l goes directly to fastboot mode when pressing the key combination). And after plugin, the result was
Anyway thanks for your response. Please give solution.
Click to expand...
Click to collapse
Theres no such tool for HTC phones, you must use fastboot. <waiting for device> when using fastboot commands means the computer doesn't detect the phone so even if there was a tool like Odin for HTC phones, it wouldn't work without being able to detect the phone. (there are actually some custom tools but they are only doing the fastboot commands for you by clicking a button instead of writing the commands yourself, they won't work if your phone isn't detected)
Usually, these fastboot connectivity issues are caused by using the wrong drivers, a bad usb cable, bad usb port etc. But i'm afraid that in your particular situation, your connectivity issue might be related to having the wrong bootloader installed on your phone variant. If this is the case, there is nothing you can do yourself. It might be recoverable using Jtag/ riffbox.
Still worth trying the usual troubleshooting (drivers, cables, ports(use only usb 2.0 btw). If you can get fastboot connectivity back, there are some (slim) chances to recover the phone, but without fastboot connectivity, like I said, there is nothing we can do.
alray said:
There no such tool for HTC phones, you must use fastboot. <waiting for device> when using fastboot commands means the computer doesn't detect the phone so even if there were a tool like Odin for HTC phones, it wouldn't work without being able to detect the phone. (there are actually some custom tools but they are only doing the fastboot commands for you by clicking a button instead of writing the commands yourself, they won't work if your phone isn't detected)
Usually, these fastboot connectivity issues are caused by using the wrong drivers, a bad usb cable, bad usb port etc. But i'm afraid that in your particular situation, your connectivity issue might be related to having the wrong bootloader installed on your phone variant. If this is the case, there is nothing you can do yourself. It might be recoverable using Jtag/ riffbox.
Still worth trying the usual troubleshooting (drivers, cables, ports(use only usb 2.0 btw). If you can get fastboot connectivity back, there are some (slim) chances to recover the phone, but without fastboot connectivity, like I said, there is nothing we can do.
Click to expand...
Click to collapse
Thanks for the clarification. I now have only one choice that is to send to the service center.

Trying to load an RUU to my soft-bricked VZW htc one

I've been looking for all over google for a signed RUU that I can flash to my phone through ADB. The phone goes to a bootloop when I try to boot normally. It got water damaged and recently I've been able to get back into the bootloader and have the device communicate with my pc, so I have hope. Here is my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA441S903495
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
My bootloader is locked and USB debugging is off and the phone is S-ON, so I keep getting signature verify failures when I try to flash TWRP recovery or any RUU package. HTC doesn't seem to have an official RUU for the Verizon version of the phone for some reason. I did try to run the package I found here: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442 but the ARUwizard always gets a failure message that says the side-by-side configuration is incorrect, despite having updated my C++ visual packages. I've cleared my cache and the RUU's I've tried have failed, so I think I just need an official firmware that matches my phone, but I don't know where to find that.
Williamck said:
I've been looking for all over google for a signed RUU that I can flash to my phone through ADB. The phone goes to a bootloop when I try to boot normally. It got water damaged and recently I've been able to get back into the bootloader and have the device communicate with my pc, so I have hope. Here is my phone:
My bootloader is locked and USB debugging is off and the phone is S-ON, so I keep getting signature verify failures when I try to flash TWRP recovery or any RUU package. HTC doesn't seem to have an official RUU for the Verizon version of the phone for some reason. I did try to run the package I found here: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442 but the ARUwizard always gets a failure message that says the side-by-side configuration is incorrect, despite having updated my C++ visual packages. I've cleared my cache and the RUU's I've tried have failed, so I think I just need an official firmware that matches my phone, but I don't know where to find that.
Click to expand...
Click to collapse
Just a quick FYI. TWRP signature fail is because your bootloader is locked. You must unlock the bootloader to flash any custom software. Never mind TWRP for now. You need the bootloader locked to flash an ruu.
Try this RUU. https://www.androidfilehost.com/?fid=24052804347761412 It's in zip form so you'll need to manually flash it with htc_fastboot which you can download here https://www.androidfilehost.com/?fid=95916177934550031.
Download both files. Rename the ruu zip file to "ruu" then copy both htc_fastboot and the ruu to your fastboot folder.
Boot the phone to fastboot usb mode in the bootloader. Then flash the ruu with the following commands.
Code:
fastboot erase cache
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
The progress bar on the phone screen won't quite reach 100% that's normal. As long as the command window has finished it's output with a successful message your good.
Code:
fastboot reboot-bootloader
Select reboot from the bootloader menu :fingers-crossed:
Obviously with water damage there's no telling if it will still boot but let me know how it goes. :good:
Sent from my HTC One M9 using Tapatalk
Thanks for the quick reply! I followed your steps and something went wrong. The first flash failed due to an h-boot pre-update, but the process restarted immediately and seemed to be going well. The progress bar was almost completely full when I got this error:
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
(bootloader) start image[emmc_fw32] unzipping & flushing...
FAILED (status read failed (Too many links))
Execution time is 71(s)
Click to expand...
Click to collapse
I got an error message from my pc saying that htc_fastboot stopped working and needed to close. My phone shut off for a second and then restarted in rebootRUU mode like before, with a black background and silver htc logo, but now it has small caution symbols in all four corners.
Williamck said:
Thanks for the quick reply! I followed your steps and something went wrong. The first flash failed due to an h-boot pre-update, but the process restarted immediately and seemed to be going well. The progress bar was almost completely full when I got this error:
I got an error message from my pc saying that htc_fastboot stopped working and needed to close. My phone shut off for a second and then restarted in rebootRUU mode like before, with a black background and silver htc logo, but now it has small caution symbols in all four corners.
Click to expand...
Click to collapse
OK well the pre-update fail is normal. This is the bootloader being updated before the firmware is flashed.
The caution symbols in ruu mode are because the RUU did not complete. Strange that it stopped where it did though.
It may be that emmc is damaged and not writable. Try flashing the ruu again. Hopefully it will complete. If not check to see if it ends at the same point.
Also make sure your using a USB port at the back of your PC not the front ones. :good:
Sent from my HTC One M9 using Tapatalk
The flash worked completely this time, but the phone is still stuck in a bootloop. The phone has new variables from the flashed RUU, so at least there's that. I still can't boot normally or into recovery. I tried a factory reset from the bootloader menu to try to clear caches and this just leads back to a bootloop
Williamck said:
The flash worked completely this time, but the phone is still stuck in a bootloop. The phone has new variables from the flashed RUU, so at least there's that. I still can't boot normally or into recovery. I tried a factory reset from the bootloader menu to try to clear caches and this just leads back to a bootloop
Click to expand...
Click to collapse
Well as I said with water damage there's always the possibility there is hardware damage inside the phone.
If the ruu has flashed then all the software is restored to stock condition. Which only leaves hardware.
What method did you use to dry the phone? And for how long?
Sent from my HTC One M9 using Tapatalk
Danny201281 said:
Well as I said with water damage there's always the possibility there is hardware damage inside the phone.
If the ruu has flashed then all the software is restored to stock condition. Which only leaves hardware.
What method did you use to dry the phone? And for how long?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I dried it in a tub of rice for about a month. It took a while to even turn on at all.
Could you go into a little more specifics, if you know, as to what exactly got damaged? I mean the bootloader can run, a zip can be flashed, the battery can be charged, and adb can report the internal partitions of the phone. So what is damaged, and can it be repaired or replaced?
I'm in the same boat. However does the "htc_fastboot" really differ from the one supplied by the android SDK? When I try to go into RUU mode, it simply reboots, could this be attributed to the wrong fastboot?
hansbogert said:
I'm in the same boat. However does the "htc_fastboot" really differ from the one supplied by the android SDK? When I try to go into RUU mode, it simply reboots, could this be attributed to the wrong fastboot?
Click to expand...
Click to collapse
The difference is Google's generic fastboot can't handle zip files larger than 1.5gb.
Most HTC lollipop and Marshmallow ruu's are all 1.6gb up-to 2.2gb. So you have to use htc_fastboot to flash them because it's designed to flash larger files.
Sent from my HTC One M9 using Tapatalk
Williamck said:
I dried it in a tub of rice for about a month. It took a while to even turn on at all.
Could you go into a little more specifics, if you know, as to what exactly got damaged? I mean the bootloader can run, a zip can be flashed, the battery can be charged, and adb can report the internal partitions of the phone. So what is damaged, and can it be repaired or replaced?
Click to expand...
Click to collapse
Yeah in rice is the best way normally for a day or two is enough. I guess it for quite wet?
To be honest it could be anything. A spot of corrosion in the right place could do it.
But without opening the phone it's impossible to know exactly what damage if any the water has caused.
The ruu you've flashed is officially signed from HTC. The same package the service center would use to restore the device. That's why I say it's unlikely to be a software issue.
Out of interest how long did you wait for the phone to boot, it can take up-to 20mins for first boot after flashing an ruu. The phone will hang on the HTC logo for 20mins+ before starting the app optimization.
Sent from my HTC One M9 using Tapatalk
It wouldn't give any indication of working at all, on the order of a week maybe. After that it started to show a generic charging symbol on the screen when plugged in, although no progression bar for charge, and the light would turn green but that's it. Only after several weeks would the screen start to show that the battery actually was charging, with a percentage, and turn on into bootloader.
So yeah, I think it must be pretty damaged. Now when I try to turn it on, like I said, it's a bootloop. the htc logo stays for a while but eventually it turns itself off and back on, again to the logo.
I think I'll try to open the back and see what it looks like...I've read that cleaning the logic board with alcohol will clear the buildup of contaminants from the river water, which could be causing this weird stuff to happen.

Categories

Resources