Related
Before I give up, I thought I'd check in with the pros here to see if I'm missing something. I have read some of the other threads with similar problems, although they seem to not have solutions either. My situation my slightly differ to theirs, who knows, but I thought I should post to be sure I have tried everything before I give up on this.
I have UK Desire, non-branded, which belonged to the wife. We’ve had the phone since April 2010. (I've since bought her a new phone because things look pretty hopeless.)
The phone initially was on stock 2.1, but it was rooted with unrevoked before the jump to 2.2. We then installed leedroid (can’t remember the version) and had been on that since. The issues began shortly after using leedroid, but that’s likely a coincidence. I think it’s more likely that it has a hardware issue.
The issues started with random reboots for the last few months. It only used to happen once a day, then a couple of times a day, and eventually it occurred during calls or soon after enabling 3g/wifi. The random reboot is followed by 7 vibrations and sits on the htc logo, requiring a battery pull. This may happen once or several times before the phone finally boots again.
Problem: After applying a WWE RUU, the Desire is now bricked (stuck in HTC’s RUU recovery mode, with the /!\ alert signs in each corner of the screen. Pulling the battery and switching the phone brings you back to this screen.).
It is only accessible via pc using fastboot. No adb. This obviously reduces the options to recover to almost zero. Obviously no key combinations work. Turning the phone on simply brings you back to HTC's RUU mode.
The initial RUU failed updating partition Radio_V2. It is the same error for each RUU I have flashed since. I believe this may be due to the initial RUU I flashed containing a lower version of radio that what was currently on the phone.
The result of an RUU flash is as follows:
Code:
fastboot oem rebootRUU
fastboot flash zip PB99IMG.zip
sending 'zip' (139552 KB)... OKAY [ 19.153s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
....
....
....****Progress lines****
....
....
....
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
FAILED (remote: 51 partition update fail)
finished. total time: 141.361s
I have attempted a number of WWE RUU's to fix the problem (not in order of use):
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
On occasion (it seems random) that the update will fail early with the following error:
Code:
sending 'zip' (140724 KB)... OKAY [ 19.306s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 45.107s
I am not experienced with fastboot command line commands, so I might be missing something.
I must add that even after a RUU fail, the phone somehow once responded to a 'fastboot oem boot' command and actually booted into android. I should have taken the opportunity to follow one of the usb-brick tutorials, but I stupidly attempted Unrevoked which reboots the phone, which wasted the opportunity (was dumb). An attempt afterwards to repeat the miracle didn't work.
Normally when attempting 'fastboot oem boot', the phone shows the htc logo, and then does 7 vibrations and freezes, requiring a battery pull.
Code:
C:\Temp>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
07D944
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__001
INFOsetting->cid::HTC__001
INFOserial number: HT03VPL09316
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =421
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.14 androidboot.cid=H
INFOTC__001 androidboot.carrier=HTC-WWE androidboot.mid=PB992000
INFO0 androidboot.keycaps=qwerty androidboot.mode=normal android
INFOboot.serialno=HT03VPL09316 androidboot.bootloader=0.80.0000
INFOno_console_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw A1E 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:18616 msec
****Phone freezes
****Unplug and battery pull
FAILED (status read failed (Too many links))
finished. total time: 5.016s
The phone is currently sitting on the following software:
Code:
BRAVO PVT1 SHIP S-ON
HBOOT 0.80.0000
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.14
Mar 29 2010,21:34:33
I have read that it is useful to flash a RUU which has the same radio as your current radio. I have a goldcard and have been using it to flash other RUU's outside the WWE series which have my radio. All that I could find was the Telstra RUU (RUU_Bravo_Froyo_Telstra_WWE_2.26.841.2_Radio_32.48.00.32U_5.11.05.14_release_150162_signed). I haven't tried others for fear of making things worse.
If anyone is able to provide any advice, or things to try, it would be appreciated, but I think this may be a lost battle. If only I had S-OFF or something.
PS. Warranty isn't really an option as the phone is from the UK and I'm situated in Australia, and it's almost run out. I'm just seeing if I can get it back to life somehow.
I read around and found one thread that said that the radio is bricked so you would need to send it to HTC. You could just say that you were performing a firmware upgrade and it went tits up.
If you have access to hboot which you prob don't then you could try putting the zip file from the RUU, rename it PB99IMG and put it on your SD card and let it run like that. But like I said, unlikely.
Meaple said:
I read around and found one thread that said that the radio is bricked so you would need to send it to HTC. You could just say that you were performing a firmware upgrade and it went tits up.
If you have access to hboot which you prob don't then you could try putting the zip file from the RUU, rename it PB99IMG and put it on your SD card and let it run like that. But like I said, unlikely.
Click to expand...
Click to collapse
Much appreciated Meaple. I thought a solid brick might be the case.
I must say that the main thing that confuses me is how I was able to boot the phone once after running through the RUU's. I also find it strange that the RUU refuses to flash the radio.
Perhaps a bad radio flash in the past while allowing the phone to still operate (albeit in a faulty nature) was the cause if the initial issues, and that functionality was finally ended after a RUU (due to the nature whereby it wipes everything).
Is it possible at all to run anything from the sd card from the pc command line through fastboot? Or to run an officially signed ota in PB99IMG.zip format from the command line?
I take it you can access hboot? You might be able to but you'll have to look around.
Sent from InsertCoinHD Data++
I had the same problem last year. Called HTC who said that if you have the four triangles then it is a hardware failure (probably mobo).
Sent it back to them and got it back 7 days later with a new [free] mobo. Worked perfectly ever since. By the way I told them it happened whilst installing an OTA update.
There is a large thread somewhere on the forum about people having this random reboot problem and the consensus seems to be that it is a hardware problem and the only remedy is to return the phone to HTC.
Hope this helps
Um somehow even with a radio flash fail every time I did an RUU, I was still able to fastboot oem boot the device again, after flashing RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed (and after a number of fastboot oem boots and battery pulls later).
Oddly I wasn't able to do it with a sd card inserted though.
While I have it in this booted state, do any of you guys have any suggestions for what I could do next? Considering I have no sd card inserted, and no root access? :S
Obviously this booted state is completely temporary and I'll obviously get stuck in the HTC RUU recovery again if I shut down the device, which may take a while to return to a booted state. (this is the 2nd time in 3 days or so I've actually gotten it to boot out of what's seemed like 100 RUU flashes.)
1. Get the 2.29.405.5 RUU
2. Follow the guide I posted here:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102
This might not work but it might at least get a working ROM on the phone so you can send it back
EddyOS said:
1. Get the 2.29.405.5 RUU
2. Follow the guide I posted here:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102
This might not work but it might at least get a working ROM on the phone so you can send it back
Click to expand...
Click to collapse
Thanks for your response EddyOS. It was actually your guide I used to understand how to extract and start using the PB99IMG.zip's in the first place to get me to this point. However, I don't think doing any more RUU's will help, because don't they just reboot the phone again and bring me back to the problem where I'm on the screen with /!\ alert signs and the radio won't flash?
Currently the phone has 2.1-update1 and HBOOT 0.80 (software version as found in my pic on post #6).
Is there a way of gaining root access to flash anything or to gain root from within android os itself? I remember back on the nexus one you could permanent root the entire thing (with a locked bootloader) from within android using an adb exploit.
I can confirm that the phone appears as a device under adb devices, meaning I can now make use of adb. (if that helps)
Ok, a bit of an update: by using the adb install method I was able to get UniversalAndroot 1.62 on the device and have been successful in getting softroot. Not a huge win by any means, but at least it's something.
EDIT: Through a bit of dodgyness, I was able to insert the memory card into the desire with the battery still in there (it wouldn't boot with the card inserted). Now that I have some internal storage I have been able to install clockworkmod and have flashed clockwork recovery.
Still doesn't fix the problems though, because I've obviously got no way of booting into clockworkmod.
Is there anything I can flash while booted into android to stop the phone from going to the /!\ HTC alert screen every time its powered on?
Desire Stuck at HTC logo, Cant get to Fastboot mode also
Today i was trying to unroot my desire after fed up with bootloop issues...
used RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release_159811_signed
and ran the utility using correct goldcard.....
At the end ERROR [152]: IMAGE UPDATER ERROR poped up and then i tried to recover as per the instructions of RUU package..
Message appeared is as below.
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031D
TOUCH PANEL - SYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
BOOT - OK
BOOTLOADER - OK
RADIO V2 - FAIL - PV
RADIO CUST - OK
RECOVERY - OK
SPLASH1 - OK
SYSTEM - OK
USERDATA - OK
Now i am unable to get Hboot and/or fastboot mode too.....
Desire just stucked up at black HTC screen with 4 triangles at all corners......
pranavd1980 said:
Today i was trying to unroot my desire after fed up with bootloop issues...
used RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release_159811_signed
and ran the utility using correct goldcard.....
At the end ERROR [152]: IMAGE UPDATER ERROR poped up and then i tried to recover as per the instructions of RUU package..
Message appeared is as below.
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031D
TOUCH PANEL - SYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
BOOT - OK
BOOTLOADER - OK
RADIO V2 - FAIL - PV
RADIO CUST - OK
RECOVERY - OK
SPLASH1 - OK
SYSTEM - OK
USERDATA - OK
Now i am unable to get Hboot and/or fastboot mode too.....
Desire just stucked up at black HTC screen with 4 triangles at all corners......
Click to expand...
Click to collapse
Take the battery out for 10-15 mins (30 mins to be safe), then put it back in and flash the ROM using the PB99IMG method. Worked for me when my phone did this
EddyOS said:
Take the battery out for 10-15 mins (30 mins to be safe), then put it back in and flash the ROM using the PB99IMG method. Worked for me when my phone did this
Click to expand...
Click to collapse
Thanks For Quick reply.....
Will try it surly...Phone was in switch off mode since brick last week.....
Buy as i told unable to get HBoot/FastBOot mode.......
What to do then?
pranavd1980 said:
Thanks For Quick reply.....
Will try it surly...Phone was in switch off mode since brick last week.....
Buy as i told unable to get HBoot/FastBOot mode.......
What to do then?
Click to expand...
Click to collapse
I Tried the method by you but fail.....Phone is not booting in Hboot/Fastboot....
Onlt Black HTC screen with 4 triangle in each corner i can see.....
Please help me if any other method is there......
use this it will work so u can finish load new offical rom
http://forum.xda-developers.com/showpost.php?p=12551350&postcount=17
ur phone has goan in to secure mode so just use the link i gave u an do it like in the link then u will get u phone to work again
but after finish update u need to take out the batt again do the same thing again then it will finish the update
janielsen said:
ur phone has goan in to secure mode so just use the link i gave u an do it like in the link then u will get u phone to work again
but after finish update u need to take out the batt again do the same thing again then it will finish the update
Click to expand...
Click to collapse
Strange but will surly try it......and update you further.....
Thanks for help......
janielsen said:
ur phone has goan in to secure mode so just use the link i gave u an do it like in the link then u will get u phone to work again
but after finish update u need to take out the batt again do the same thing again then it will finish the update
Click to expand...
Click to collapse
pranavd1980 said:
Strange but will surly try it......and update you further.....
Thanks for help......
Click to expand...
Click to collapse
Unbeleivable....OMG.....Freezer idea worked.....i got my HTC working......
Few reboots but its in working condition.......WOW
Thanks for help........
Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.
pastyal said:
Hi all, long term lurker first time poster so please go easy on me.
After having many successes on rooting and flashing various device over the years thanks to this forum, I have finally completely knackered my M8 I think.
Awhile ago I rooted and flashed Venom Rom which worked perfectly. I then decided I wanted Revolution HD rom but obviously didn't follow the guide correctly as afterwards I couldn't get wifi. I still used the phone for a few months until yesterday when I finally decided to do something about it. So using Minimal ADB Fastboot I flashed a Lollipop firmware and was going to flash another ROM.
However, the phone won't boot into recovery, just the bootloader. Can anyone please tell me (in simple terms ) where I can go from here or whether I now have a brick?
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.770s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.787s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.431s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1830711296 bytes
sending 'zip' (49565 KB)...
OKAY [ 2.790s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.415s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.706s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.455s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 1830711296 bytes
sending 'recovery' (17034 KB)...
OKAY [ 1.713s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.463s
Click to expand...
Click to collapse
And heres the getvar all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
pastyal said:
Many thanks for the reply. I don't think the Firmware flashed succesfully, I tried three times and each time got the same response:
And heres the getvar all
Click to expand...
Click to collapse
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.
Seanie280672 said:
which firmware did you download ? description or link if possible.
also you cant flash custom recovery as your bootloader is locked, and you need stock recovery and HTC dev unlock token to unlock it.
remove your imei and serial number from your getvar all, also, as you are s-on, you need to make sure that the firmware you flashed is ORANG001 firmware as per your cid, at a guess it will be something like 4.xx.61.x the 61 is the key, this will relate to region / carrier 61 is orange / EE, and the 4 is the latest android version firmware for the HTC one M8, as your version main is missing I cant fully confirm this, this is a fault from flashing earlier versions of TWRP recovery.
alternatively, you can flash a custom rom and get s-off via sunshine s-off @ $25 and convert your phone.
Click to expand...
Click to collapse
Ooops thanks for the heads up on removing the info!
Aaah thats the mistake I made by using the wrong firmware. I will locate the correct firmware and try that later on today. I did look at the Sunshine option but was unsure if it would help me at this moment in time. Think i'll try the correct firmware first.
Will update here later with good news hopefully!
Seanie280672 said:
post your fastboot getvar all please without imei and serial number
did the firmware flash complete successfully ?
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
also forgot to add, if the firmware flash went through fine then you will now have stock recovery on your phone, this will just look like a big red exclamation mark on your phone.
at this point you either need to find a stock RUU for your phone and run it now or unlocked your bootloader again at HTC dev, flash a custom recovery and then flash a custom rom.
if you have anything custom / non stock on your phone right now, it wont boot or load with a relocked bootloader.
Click to expand...
Click to collapse
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?
pastyal said:
Ok, I have now succesfully flashed the correct (I think ) firmware. I flashed twice to be sure. In cmd I rebooted to Fastboot but all I have now is the screen you mentioned with the red exclamation mark within a triangle. Where do I go from here as the phone won't do anything, not even turn off. It does occasionally turn off itself and I try to enter bootloader but it just loads to the red exclamation mark again.?
Click to expand...
Click to collapse
hold volume up, volume down and power button for about 15 to 20 seconds, phone will go off, before it comes back on quickly release all buttons and just hold volume down only, it should boot to the bootloader.
Thank you for that, that gets me into the bootloader but it won't load into fastboot now?
pastyal said:
Thank you for that, that gets me into the bootloader but it won't load into fastboot now?
Click to expand...
Click to collapse
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?
Seanie280672 said:
what do you mean wont load into fastboot ? do you mean your computer just says waiting for device, which firmware did you flash ?
Click to expand...
Click to collapse
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?
pastyal said:
Yes pc says waiting for device. I flashed a firmware from here, not sure which one it was now though http://forum.xda-developers.com/showthread.php?t=2701376
Do I need to flash a stock recovery now? If so do I need to be able to get the phone to load into fastboot?
Click to expand...
Click to collapse
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC
Seanie280672 said:
no you don't need to flash stock recovery, I don't see any firmware files for your phone in that link, and as your s-on, they shouldn't of been successful, nothing should of changed.
waiting for device is generally a driver problem, check device manager whilst your phone is plugged into your computer, should say android devices - MyHTC
Click to expand...
Click to collapse
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.
pastyal said:
I can't see any android devices listed under device manager. I installed HTC Sync yesterday though which I thought loaded the drivers? What should i do now?
Click to expand...
Click to collapse
Also make sure in bootloader it says FASTBOOT USB and not HBOOT
redpoint73 said:
Try to uninstall HTC Sync and any HTC drivers. Then see if the phone shows up in Device Manager. If so, select to manually pick drivers, and pick the generic MTP device.
Might not work for you, but this is what I had to do to get fastboot/adb working on my PC with the M8.
Click to expand...
Click to collapse
ssantos132 said:
Also make sure in bootloader it says FASTBOOT USB and not HBOOT
Click to expand...
Click to collapse
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.
pastyal said:
Sorted it, was a simple matter of swapping USB ports. I have a new laptop and forgot one of the ports was USB 3.0 which the phone was connected with. Evidently it prefers a USB 2.0 port.
Click to expand...
Click to collapse
That's right, USB 3.0 does not play well with this device.
pastyal said:
So I assume now I need to find the correct firmware, of which I'm struggling with a little. Can anyone po8nt me in the right direction? I have been through a lot of threads here and can't seem to find anything.
Click to expand...
Click to collapse
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.
redpoint73 said:
That's right, USB 3.0 does not play well with this device.
I can't find the firmware for your CID either. You may have better luck updating the firmware by OTA.
To do that, you will need to restore the stock ROM and stock recovery, using the files and instructions here: http://forum.xda-developers.com/showthread.php?t=2701376
After restoring stock ROM and stock recovery, you will need to update up to Lollipop, which will probably include a few (3) OTA updates.
Once you've updated to current firmware by OTA, you can install custom recovery again, and run the current custom ROMs.
Click to expand...
Click to collapse
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?
pastyal said:
I'm getting myself in a right mess I think. I've just tried installing the stock recoveries from https://www.androidfilehost.com/?w=files&flid=25064 as linked to from this thread http://forum.xda-developers.com/showthread.php?t=2694994 which I thought woud be perfect for me but I get an error of "FAILED (remote: signature verify fail)" in cmd. If I reboot the phone into recovery I get the red exclamation mark again.
Any ideas on what i'm doing wrong? Am i right in thinking I need to flash a stock recovery and THEN a stock ROM, or should it be the other way around?
Click to expand...
Click to collapse
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5
redpoint73 said:
Multiple mistakes here:
1) You need the stock ROM and recovery that corresponds with your hboot (3.16) which would indicate a 1.x software and corresponding recovery. The files you linked are for software 3.x and 4.x.
2) I'm also not sure why you are stumbling around in threads that aren't even for your CID when I already gave you a link to the proper location for the stock nandroid for your CID version. You want to restore the stock nandroid for ORANG001, which is 1.54.61.5 and the stock recovery 1.54.xx
3) You need to flash the stock ROM (restore stock nandroid) before the stock recovery. Once you've restored stock recovery, you cannot flash a ROM or nandroid. You need custom recovery to do that.
3) Lollipop recoveries for other CID won't work. But a KitKat recovery for another CID will work (as mentioned in item 2 above, you want a 1.54.xx recovery to correspond to the stock ROM 1.54.61.5 since a recovery doesn't seem to be posted for your exact software 1.54.61.5
Click to expand...
Click to collapse
Thanks very much for that, the reason why i was stumbling around is because i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Could you please tell me how to restore the stock Nandroid. i promise you I am going around in circles lol
pastyal said:
i had already tried that Nandroid backup but i think i must have used incorrect instructions. I read I had to open the zip file and flash the boot.img, but I just get the same error as before if I do that.
Click to expand...
Click to collapse
Instruction on restoring a nandroid are in post #3 of the stock nandroid collection thread I linked before. Click where it says Questions & Answers, and you will see the 2nd question is how to restore a stock nandroid: http://forum.xda-developers.com/showpost.php?p=58128936&postcount=3
I think you may have seen these instructions, but you only did one part, not the remaining parts of the process. The boot.img is essentially just the kernel; technically a few other things too, but either way its like 1% of what you need to have a working ROM. Namely, if you only flashed boot.img, you didn't do the steps I've highlighted in orange below:
- Place the nandroid backup unpacked on the sdcard of the phone in the right backup folder
* Philz touch uses - Clockworkmod\Backups\
* TWRP uses - TWRP\Backups\ or TWRP/Backups/serialnum/ (replace serialnum with your device's serial number. To have TWRP create the proper directory structure for you, just do a simple backup of just the boot partition and put the backup files in there) thanks to garyd9 for the additional info
- Flash the boot.img or boot.emmc.win file from the nandroid backup
- Make a full wipe in the recovery
- Restore the nandroid backup and reboot
You need to unzip the downloaded file, then place the entire folder contents to the proper location on the phone. Then boot recovery (probably TWRP) and use the restore function to install the nandroid. I actually do not think you need to extract and flash boot.img separately.
After that, install the stock recovery with the fastboot command: fastboot flash recovery filename.img
Where "filename.img" is the actual name of the desired stock recovery file.
---------- Post added at 11:03 AM ---------- Previous post was at 10:57 AM ----------
pastyal said:
If it helps the phone is "Relocked" and S-ON.
Click to expand...
Click to collapse
Are you currently unlocked again? The above is from your top post, but I don't know if you've changed this (unlocked again).
You can only do the above mentioned steps (restore nandroid, stock recovery, etc.) if you are bootloader unlocked.
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
unlock with fastboot
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
yotamh said:
Sorry to bump but is there any way to unlock it with fastboot maybe since it's the only way I can connect?
any suggestion or idea will be helpful
Thanks
Yotam
Click to expand...
Click to collapse
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
yotamh said:
My current firmware is 5.0.something. To be honest I don't remember and can't check.
I've tired to re-unlock with the unlock_token you got from HTCdev but it didn't work. I've got the token with fastboot but only in download mode an then when I tried to unlock with the file they send you to the mail It gives an error that I can check later when I'm home.
Yotam
Click to expand...
Click to collapse
It seems like you're talking about the android version not the firmware version since there is no 5.0.XXX.X firmware for the M9. For now it might be the best solution to wait until you're home.
yotamh said:
Hi,
Well, as the title said i'm stuck in bootloop after re-locking the bootloader.
Here is the history of what happened:
Unlocked the bootloader
flashed TWERP recovery and rooted.
I saw I can't install OTA updates so I unrooted the phone and flashed back to stock recovery. Still couldn't install OTA updates.
Unlocked the bootloader again and restored system partition back to original "untouched" status (from this thread: http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022). Only to realize i'm not on t-mobile, but the phone worked anyway .
Flashed back to stock recovery but still couldn't install the updates (If I remember correctly I got a massage that my software was tampered).
I'm S-on so I thought before trying the sunshine app I'll relock the bootloader. So I did that and that's it.
Here's were I'm now:
software status: modified
RELOCKED
S-ON
I can access stock recovery and download mode.
ADB devices doesn't recognize the phone (all drivers are ok and up to date and I've tried different cables and usb ports)
On the other hand, fasboot devices does work and recognize my phone.
So I come to you with help after going though tons of pages, guides and what not. I'm at it for a week now and no luck.
Help me XDA-Kanobi, you're my only hope
Thanks
Yotam
Click to expand...
Click to collapse
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
LLegion said:
OK OK dont get frenetic...DO AS EXACTLY AS I SAY OK?.................boot into download MODE Only and follow SAKITECH video on how to root M9, then flash a custom rom or SD Zip-Ruu to allow phone to boot again. =D hope this helps!
Click to expand...
Click to collapse
the problem is I can't unlock the bootloader. ADB devices doesn't work
Flippy498 said:
What's your current firmware? Is the allow OEM unlock option (or how ever it was called in English) activated in the developer options (only important for firmware versions with a 2 or higher at the beginning)? If yes you can re-unlock with the unlock_token you got from HTCdev.
Click to expand...
Click to collapse
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
yotamh said:
how can I check the firmware version from the bootloader?
(under os in download mode I see - 1.32.401.15. is that the firmware?
Click to expand...
Click to collapse
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in my google sheet (link can be found in my signature). Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Flippy498 said:
Yes, that's correct. And with that firmware your problems can be solved without much hassle. Just download either the 1.32.401.15 or the 1.40.401.8 RUU which are both linked in the google sheet in my signature. Follow the instructions and your phone should be usable again in no time. If you choose the 1.40.401.8 RUU there's one OTA less you need to install after you recovered your phone.
And a little advice for the future: If you want to install future OTAs then you don't need to relock your bootloader. If your phone isn't completely stock this will always result in a bootloop.
Click to expand...
Click to collapse
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
yotamh said:
Thanks a lot for the answer. Is it possible to flash the RUU if I'm S-ON??
Click to expand...
Click to collapse
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Flippy498 said:
Of course. The only things you cannot do is downgrading or flashing RUUs that have a different SKU (=the three numbers behind the second dot in the firmware version). RUUs with the same version as your phone or higher versions are fine, though.
Click to expand...
Click to collapse
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
yotamh said:
HI
So i'm trying to flash the RUU and I'm getting this:
C:\Users\Yotam\Desktop\Phone files>fastboot flash zip M9_1.32.401.15_FullStock_rename_to_ROM.zip <----I've tried to change it to ROM.zip as well but I get the same error
target reported max download size of 800000000 bytes
sending 'zip' (111548 KB)...
OKAY [ 7.869s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8: fail to flash via downloadzip)
finished. total time: 12.962s
The ZIP file is fine (i've downloaded it twice just to be sure), phone is with the sd card in it (I though it's worth mentioning), S-ON.
Not sure what else...what seems to be the issue here?
Click to expand...
Click to collapse
yotamh said:
some more info
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.15
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.014s
Click to expand...
Click to collapse
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature.
Click to expand...
Click to collapse
Hi thanks for the top about the IMEI I've changed it.
and sorry, I didn't understood the the original comment and got in to the a wrong line in the comment. I'll try again with the correct file (2gb will take some to download). Again, thank you for your answer and patient. It's nice to see people try to help. :good:
THANK YOU so much! everything is working and even updated! thanks!
it seems i have a strange issue after all.
my phone doesn't detect my htc headphones. It recognize other headphone and the HTC headphones works with other devices.
it looks like a software issue.
Flippy498 said:
For your own safety you should delete your IMEI as it can be used for phone scam by others.
Why are you trying to flash one of Sneakyghosts' firmware packs? They can only be used with S-OFF and do not contain a rom. [REMOVED BECAUSE I'M A NEWBIE]I've already explained earlier that you can find the needed RUUs and instructions in the google sheet in my signature[/URL].
Click to expand...
Click to collapse
Hi I know this is probably old but I was in this exact same predicament and I had "tried everything" and your instructions brought my phone back to life!! I am so grateful after almost a week of adb commands and zip files that got me nowhere! THANK YOU SO MUCH!!!:good:
So today I had issues flashing LeeDroid which I want for some super battery saving where apparently it was good for that. Anyway in the end the sim card wasn't being recognized and it was really buggy and I went and reread the thread on LeeDroid and it said something about updating firmware. So then I stumble upon RUUs and that looked like the way to go to update all firmware and all that lovely jazz so I downloaded the international/developer one (as I got mine in Australia with code himauhl) but it gave me error 132 and said signature error, so I double checked the numbers, my phone has OS-3.38.841.6 where I think I need to match the RUU with the three digit number in that thing so the 841, however, HTC doesn't provide an RUU for the One M9 with 841. I did some research but nothing came up so I was hoping you guys could help me out.
By the way I have S-On but I am not prepared to pay $25 for S-Off, which is why I'm trying to use this method.
Phone is currently running latest version of Lineage OS 14.1
(Quick stat reminder: HTC One M9, himauhl, OS-3.38.841.6)
THANKS IN ADVANCE!
Edit:
So after further research I found: www.androidruu.com
I managed to find an ruu for my phone but a little problem. I'm on version 3.38.841..... and this ruu is on 1.32.841...... that means that I probably need S-Off to do it? I know you can't downgrade firmwares without S-Off so I think now the answer is to try harder to find a later ruu? Just needing some confirmation and hoping someone might know a better way. Thanks!
Edit 2:
My adventure continues. I managed to get S-Off, eventually gave up and paid for Sunshine, oh well. Anyway! I then used the htc_fastboot commands to change my cid to BS_US001 and then my mid to OPJA11000 and I thought all was well and good HOWEVER the RUU.exe for the developer version still returns error 132 and even using the htc_fastboot so flash the 4.30.612.12 zip file returned a ERR Model ID not matched and Model ID Not allowed. I have no idea what I'm doing at this stage, any ideas are truly most welcome. Thanks!
Edit 3:
At this stage I'm still not sure of the problem. My actual device model is the OPJA100 and I changed it to OPJA11000 and tried to flash an RUU with the same MID (11000) but to no success. Then I changed my CID to the super 11111111 but still with no success. I'm going to try to get a ruu.zip and then change the info.txt modlid to OPJA100 to see how that goes.
Edit 4:
I AM A COMPLETE IDIOT!!!!
I am sorry if I have wasted anyone's time, but it was all due to one little typo, turns out the RUU I had was for 0PJA11000 (ALL ZEROS) where I had OPJA11000 (First O was the letter O) hence causing the stuff up.
Hope this helps someone out there too! CHECK YOUR OOOOSSSSSS
So, just to further define the issue a bit more here is an error dump:
D:\Android Platform-Tools>htc_fastboot flash zip 0PJAIMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (92974 KB)...
OKAY [ 5.352s]
writing 'zip'...
(bootloader) HOSD CL#683910
(bootloader) ERR Model ID not matched
(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 10
(bootloader) [email protected]
FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )
finished. total time: 7.473s
htc_fastboot finished. total time: 8.548s
Hi,
I had tried rooting my At&T HTC One M9 using the NOOB friendly guide written by KingInTheNorth. After completing, my phone wouldn't boot up. It got into a bootloop. I then found a guide (from another website) on how to reload the stock RUU. I followed the direction but it looks as if the file was bad. The following is copied from the command prompt.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip C:/Use
Downloads/M9fullstock.zip
target reported max download size of 800000000 bytes
sending 'zip' (79642 KB)...
OKAY [ 5.185s]
writing 'zip'...
(bootloader) HOSD CL#682052
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14 RU_ZIP_INFO_ERROR android-info missing or malformed )
finished. total time: 8.400s
Now my phone is stuck on the screen that shows a phone with a green arrow in a green circle pointing down. I've tried rebooting but it doesn't respond to any button presses. Did I ruin my phone? Can anyone help?
Try to type fastboot reboot in your command prompt. It should reboot your phone. If you're lucky it will reboot your phone normally and it's fully functional. If not, your phone will boot into bootloader which will mean your rom is wiped.
That's not a RUU that you were trying to flash and the guide written by KingInTheNorth is outdated since different firmware versions of the M9 can only get rooted with different versions of SuperSU. Check the ReadMe thread for the guides and files you may need.
@Suurbier91: Never recommend people to reboot if a flash failed unless they know exactly what's going on. There are some flashing errors that can only get fixed if the phone gets flashed immediately, again. A reboot makes those bricks permanent and unrecoverable.
Thanks for the direct to the Read Me. I've found a lot of good information there. After my battery died, I charged the phone and it's coming back on. It still has a boot loop that lasts for between five to ten minutes before booting up. I am going to try following one of the threads I found on here to get back to stock. Hopefully that will take care of the boot loop issue. I was wanted to root it so I could upgrade to Nougat. The phone was originally AT&T but I paid to unlock it and I'm now on Cricket but I don't receive any OTA updates.
That's probably so because the phone is only sim unlocked but still using the AT&T firmware. Don't ask me why they're allowed to do so (it wouldn't be possible in the EU) but AT&T won't let you download OTAs if there isn't an AT&T sim card inserted into your phone.
If you don't need the AT&T branded firmware then I'd get S-OFF and convert my phone to the dev edition if I were you. If you choose to stay on the AT&T firmware then you can update your phone via a RUU. Be aware that it's not possible to update from firmware 3.x or lower to firmware 4.x via RUUs due to new encryption keys.
Sent from my HTC One M9 using XDA Labs