Develop Bugs

SOLVED___help needed with a friends HTC desire

hi,
I spent last 5 hours reading on XDA, on another forums, testing stuff, searching more on the web but I cant figure out what to do. Also this is not my device so I am little worried to do something wrong.
I am using HD2 so this approach to android and flashing is little new to me so please forgive my desire noobiness.
First here are some info on the device.
It is a Desire GSM (I guess since it does have SIM card).
Baseband 32.56.00.32U_5.17.05.23
Info from hboot:
BRAVO PVT3 SHIP S-ON
HBOOT 0.83.0001
MICROP-051d
TOUCH PANEL-SYNt0101
RADIO-5.17.05.23
While doing some stuff for usb brick I got this info from running "fastboot oem boot". Posting it in case it might be relevant.
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8E07E8CC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x26A0D
(bootloader) TAG:hero panel = 0x3
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT09RPL01076
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =417
(bootloader) active commandline: board_bravo.disable_uart3=1 board_bravo.
(bootloader) usb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=false androidboot.baseband=5.17.05.23 androidboot.cid=1
(bootloader) 1111111 androidboot.carrier=ALL androidboot.mid=PB992**** an
(bootloader) droidboot.keycaps=qwerty androidboot.mode=normal androidboot
(bootloader) .serialno=HT09RPL01076 androidboot.bootloader=0.83.0001 no_c
(bootloader) onsole_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) partition number=6
(bootloader) Valid partition num=6
(bootloader) mpu_nand_acpu_rw A1E 1000
(bootloader) jump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
(bootloader) nel_addr(0x20008000)
(bootloader) -------------------hboot boot time:33155 msec
FAILED (status read failed (Too many links))
finished. total time: 4.823s
Click to expand...
Click to collapse
I got this device from a friend. Symptoms were stuck at boot. It had 2.3 gingerbread installed. At that time adb worked and soon by looking at logcat I realized that something is wrong with sdext and then with sdcard and both werent usable in recovery.
After finding the threads about usb brick I did
fastboot oem enableqxdm 0(unblock your sd-card)
fastboot oem eraseconfig(fix misc partition)
Click to expand...
Click to collapse
and installed some zip through recovery that was on that page and after that
sdcard worked and I succesfully booted into android.
Then I installed latest clockworkmod recovery through rom manager and flashed this rom, a2sd+ version.
After that following problems occured:
I cant get adb to work, and usb mount is not working neither in recovery nor in rom. In recovery when desire is connected windows recognize "unknown device" and when I click on USB mount it stays on "unmount" option but computer doesn't see anything different.
When I connect the device while in android windows recognize 3 devices without drivers named "Qualcomm CDMA Technologies MSM".
I installed htc sync 2.0.33, and uninstalled it so that htc driver remains.
SD card woks fine in external card reader.
And there is also problem with charging. If I disconnect the cable while charging and plug it again phone wont charge. But there is a usb connection since windows still sees 3 devices named above. Then I need to turn off the phone, remove and put back the battery and then when I boot into android and plug the cable again it charges fine. If I disconnect the cable again problem is there again.
Jut so point out that while I am in fastboot or in hboot windows sees the phone, fastboot works fine, no metter if I unplug the phone and plug the cable back.
This somehow looks to me like possible hardware problem, but then again it could be something I did wrong or didnt know what to do.
After that I wanted to put phone to stock 2.2 rom, downloaded RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe but when running it while in fastboot phone hangs after some time. Also I tried renaming this file to PB99IMG.zip and copy it to a freshly formated sdcard (fat32) but when i enter the bootloader it wont do anything.
Any hint or suggestion is most welcome. I am all out of options what to try next.

You did the right steps, and think you fixed it, you just broke it again using ROM MANAGER!! Stay away from that piece of SH*T application!
Have you tried using the USB Brick Fix again? It should do it for you. Once you've done that, return it to stock, S-OFF the phone (much easier to fix), flash 4EXT Recovery (automatic USB un-brick, installed via app from market), backup, full wipe, and flash a rom.
Then never use ROM Manager in your life.

bortak said:
You did the right steps, and think you fixed it, you just broke it again using ROM MANAGER!! Stay away from that piece of SH*T application!
Have you tried using the USB Brick Fix again? It should do it for you. Once you've done that, return it to stock, S-OFF the phone (much easier to fix), flash 4EXT Recovery (automatic USB un-brick, installed via app from market), backup, full wipe, and flash a rom.
Then never use ROM Manager in your life.
Click to expand...
Click to collapse
I did the usb brick thing few more time, althought sdcard work without problems in that time.
But I cant do the s-off because of 0.83.0001 hboot version and dont know how to update the hboot without usb connection. All the ways I tried didnt do anything.
I just saw one thing. This is some errors in logcat that I get after plugging/unplugging the usb cable while in android.
E/BatteryService( 1019): /sys/devices/platform/msm_hsusb/usb_cable_connect (No such file or directory)
E/BatteryService( 1019): read property /sys/devices/platform/msm_hsusb/usb_cable_connect failed
E/BatteryService( 1019): /sys/devices/platform/msm_hsusb/usb_cable_connect (No such file or directory)
E/BatteryService( 1019): read property /sys/devices/platform/msm_hsusb/usb_cable_connect failed
D/BatteryService( 1019): isUsbConnected() = false
D/UsbConnectedReceiver( 1220): action = psclient.intent.action.usb_status
Click to expand...
Click to collapse
So there is a connection between computer and phone but something is not letting the phone start charging again. No metter if its connected to a computer or a wall charger. I need to remove the battery so it can start charging again.
From my point of view and limited experience with the device it can be caused by....anything....maybe faulty hardware...something done wrong by whoever rooted/flashed this device before me.
Thanx for conformation I did good steps.
I would like to install a stock 2.2 or maybe 2.3 rom without s-off, root or anything to see if that will fix this issue. Then I will know that is probably hardware error.
But dont know how to do it.
I tried starting wwe ruu from fastboot, and the phone freezes after I click on update and with renaming that file and try from sd card but nothing also happened. That card had single fat32 partition with only that zip file on it.

Check if you renamed it right. It must be pb99img.zip and not pb99img.zip.zip.
Gesendet von meinem HTC Desire

muellersmattes said:
Check if you renamed it right. It must be pb99img.zip and not pb99img.zip.zip.
Gesendet von meinem HTC Desire
Click to expand...
Click to collapse
At first I named it PB99IMG.zip (uppercase). Just now tried it in lowercase after doing the usb brick thing again and as again when it enters the hboot after about 5 sec it lists some green text and says no image. I tried with 3 different sd cards.

I got another SD card, extracted the rom.zip from ruu, renamed it to PB99IMG.zip and I succesfully flashed 2.2 stock rom, but the usb cable issue still exists.
After I once remove the usb cable, end plug it again, computer only sees three "Qualcomm CDMA Technologies MSM" devices, no driver for it..
Phone doesnt react at all, it is not charging, no usb connection detected other then the errors in logcat I typed before (I got those from aLogcat app).
Meanwhile in fastboot connection works fine, now I have 0.93.001 hboot.
Can I achieve root and s-off without USB connection?
Also now when I go into recovery now I get a black screen with phone picture and red trigle with exclamation sign..

After found this article I did USB brick fix on non-rooted stock 2.2 rom, and after that USB mount and charging works fine.
I just did root and s-off with unvevoked3 app and reflashed newest radio.
I will try now to flash newer 2.3 rom and hopefully it will work...
thanx to everyone
edit:
everything works perfectly.

clyder said:
After found this article I did USB brick fix on non-rooted stock 2.2 rom, and after that USB mount and charging works fine.
I just did root and s-off with unvevoked3 app and reflashed newest radio.
I will try now to flash newer 2.3 rom and hopefully it will work...
thanx to everyone
edit:
everything works perfectly.
Click to expand...
Click to collapse
Glad to hear it, there was no need to update to 2.3 though if your friend will be rooting and using custom ROMs anyway.
For future problems, keep S-OFF and flash 4EXT recovery which has USB brick auto detection and fix, so you won't have to go through this lengthy process again

bortak said:
Glad to hear it, there was no need to update to 2.3 though if your friend will be rooting and using custom ROMs anyway.
For future problems, keep S-OFF and flash 4EXT recovery which has USB brick auto detection and fix, so you won't have to go through this lengthy process again
Click to expand...
Click to collapse
I installed Revolution 4.0 rom on it. This device is used by an older man so if he is used to sense android I dont want to confuse him for now.
Allthough I dont like sense Revolution works very fast and stable.
I did s-off and flashed 4ext allready. Thanx for the tip about that one.

Soft brick, signature error when flashing rom

Hi there ,
I'm having some troubles with flashing a new rom into my HTC M9.
Last week HTC "tried" to install android 7 via the automatic update in my phone. For some reason (might be because I bought my phone abroad) the installation failed and my phone booted back to its OS. I paid no attention to it (Wasn't that eager to upgrade)
a few days later after I tried to restart my phone, it decided to brick (just like that) and now I can only get as far as the boot menu when turning on my phone on.
My phone is S-on , and the bootloader it locked (quite inconveniently as I came to realize) and I am able to get to Download\Recovery\bootloader mode.
I found my CID and MID and double checked that the "androind-info" file in the RUU I downloaded suits them. But I keep receiving the message "footer is wrong signature verification failed".
To add to my enormous sorrow (I'm quite attached to my phone), I am not able to mount my internal SD even after performing "factory reset" and "cache format". At first I suspected the card is damaged but when I write "fastboot getvar all" in bootloader mode I can see that the partitions exist and have an address.
For some reason "adb" doesn't recognize my phone in "adb devices" unless I'm in "sideload mode" and I'm unable to launch "adb shell" or any "adb" function that is not "adb sideload"
Also I'm not able to update my firmware (OTA) because the phone keeps complaining that the firmware version doesn't match (I searched all over the web for "more fitting" firmware but couldn't fine one that would satisfy my phone).
I searched this forum (and the web) for an answer to my problem but couldn't find a solution to my problem.
To sum things up: S-on , bootloader locked + not able to unlock it with HTC's guide , can change to Bootloader\Recovery\Download mode but that's all (No custom recovery mode) , internal sd wouldn't mount though external sd would, "signature verification error" when trying to update my RUU.
Here is what "fastboot getvar all" gives me:
In bootloader mode:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA563YJ00838
in Download mode:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.35.401.32
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__032
And this is the RUU and OTA I tried to flash (via fastboot, adb sideload , external sd):
RUU:
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7_Radio_01.01_U114401011_117.00.61117G_2_F_release_490768_signed_2_4.zip
OTA:
OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.12-2.10.401.180_release_464237

sagros said:
Hi there ,
I'm having some troubles with flashing a new rom into my HTC M9.
Last week HTC "tried" to install android 7 via the automatic update in my phone. For some reason (might be because I bought my phone abroad) the installation failed and my phone booted back to its OS. I paid no attention to it (Wasn't that eager to upgrade)
a few days later after I tried to restart my phone, it decided to brick (just like that) and now I can only get as far as the boot menu when turning on my phone on.
My phone is S-on , and the bootloader it locked (quite inconveniently as I came to realize) and I am able to get to Download\Recovery\bootloader mode.
I found my CID and MID and double checked that the "androind-info" file in the RUU I downloaded suits them. But I keep receiving the message "footer is wrong signature verification failed".
To add to my enormous sorrow (I'm quite attached to my phone), I am not able to mount my internal SD even after performing "factory reset" and "cache format". At first I suspected the card is damaged but when I write "fastboot getvar all" in bootloader mode I can see that the partitions exist and have an address.
For some reason "adb" doesn't recognize my phone in "adb devices" unless I'm in "sideload mode" and I'm unable to launch "adb shell" or any "adb" function that is not "adb sideload"
Also I'm not able to update my firmware (OTA) because the phone keeps complaining that the firmware version doesn't match (I searched all over the web for "more fitting" firmware but couldn't fine one that would satisfy my phone).
I searched this forum (and the web) for an answer to my problem but couldn't find a solution to my problem.
To sum things up: S-on , bootloader locked + not able to unlock it with HTC's guide , can change to Bootloader\Recovery\Download mode but that's all (No custom recovery mode) , internal sd wouldn't mount though external sd would, "signature verification error" when trying to update my RUU.
Here is what "fastboot getvar all" gives me:
In bootloader mode:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA563YJ00838
in Download mode:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.35.401.32
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__032
And this is the RUU and OTA I tried to flash (via fastboot, adb sideload , external sd):
RUU:
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7_Radio_01.01_U114401011_117.00.61117G_2_F_release_490768_signed_2_4.zip
OTA:
OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.12-2.10.401.180_release_464237
Click to expand...
Click to collapse
Download the 4.14.401.7 ota from flappy's thread and drop in on your external sd card.
Reboot your phone in to recovery and choose the option to apply the ota from external.
My missus's m9 wouldn't move from the splash screen after the official ota tried to install and this is how I fixed it.

squ89r97 said:
Download the 4.14.401.7 ota from flappy's thread and drop in on your external sd card.
Reboot your phone in to recovery and choose the option to apply the ota from external.
My missus's m9 wouldn't move from the splash screen after the official ota tried to install and this is how I fixed it.
Click to expand...
Click to collapse
Thanks for the quick reply. When I try to update the OTA from SD card I receive the message
"system partition has unexpected contents"
"E:Error in /sideload/package.zip"
I used the OTA
OTA_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7-3.35.401.32_release_490770.zip
that corresponds to my MID and CID
Any ideas ?

Fastboot is bootloader and download mode. Adb is recovery mode.
Rename the update to 0PJA10000 (zero, p, j, a, one, zero, zero, zero, zero). Transfer it to your phones internal sd via adb while the phone is in recovery mode (not download mode or bootloader), at the very first level of the memory (not in any folders at all, just in the sd itself) and reboot again to recovery.
It should auto flash.
Beamed in by telepathy.

shivadow said:
Fastboot is bootloader and download mode. Adb is recovery mode.
Rename the update to 0PJA10000 (zero, p, j, a, one, zero, zero, zero, zero). Transfer it to your phones internal sd via adb while the phone is in recovery mode (not download mode or bootloader), at the very first level of the memory (not in any folders at all, just in the sd itself) and reboot again to recovery.
It should auto flash.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi, thanks for the reply. I am unable to access my internal memory in "recovery mode" (or in general) and my only indication that it still works is the "fastboot getvar all" I posted in my root comment. adb doesn't recognize my phone in any mode other than "sideload mode" so I cannot "push" the file into my sd card. Renaming the file on my computer doesn't provoke auto flash when entering "recovery mode" but maybe it's because I cannot restart into recovery mode, only boot into "bootloader mode" and there use the "Boot To Recovery Mode" option.
Sorry for being so difficult, kinda tried not to mess up with it but it bricked nevertheless 0_o

Remove the pc adb drivers, put the phone into recovery mode and THEN connect it to the pc. Hopefully it should install the correct drivers. Failing that google "manually adding physical addresses to drivers". This involves editing the .cat file prior to installing the driver.
Your only other option other than that is the ruu.exe and I'm not sure if one exists yet.
Beamed in by telepathy.

shivadow said:
Remove the pc adb drivers, put the phone into recovery mode and THEN connect it to the pc. Hopefully it should install the correct drivers. Failing that google "manually adding physical addresses to drivers". This involves editing the .cat file prior to installing the driver.
Your only other option other than that is the ruu.exe and I'm not sure if one exists yet.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi , thanks for the reply. I tried to do what you suggested but neither my Windows nor my Ubuntu recognize my HTC when in recovery mode (outside "sideload" mode), guessing it's because I never enabled "USB debugging".
Moreover, I searched one more time for any Rom that could fit my phone , unfortunately I cannot find any .exe rom that fits my CID + has a version higher than 2.*
Wrote to HTC (though I doubt it would do anything) ... Are there any motivational words about not throwing out this phone and buying a new one ? I'm am quite convinced that the problem is in the software, but the way I see it now , HTC locked the phone quite strong \=

sagros said:
Thanks for the quick reply. When I try to update the OTA from SD card I receive the message
"system partition has unexpected contents"
"E:Error in /sideload/package.zip"
I used the OTA
OTA_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7-3.35.401.32_release_490770.zip
that corresponds to my MID and CID
Any ideas ?
Click to expand...
Click to collapse
Try taking the sd card out and putting it on the sd card that way?

squ89r97 said:
Try taking the sd card out and putting it on the sd card that way?
Click to expand...
Click to collapse
Hi , thanks for the reply. Not sure what you mean. I don't have any access to my internal sd card , so to apply your suggestion I had to pull out my ext. sd card and move the file to it via my computer, and only after that connect the ext. sd back it. The message I receive from my phone when trying to install the firmware is what I wrote earlier

sagros said:
Hi , thanks for the reply. Not sure what you mean. I don't have any access to my internal sd card , so to apply your suggestion I had to pull out my ext. sd card and move the file to it via my computer, and only after that connect the ext. sd back it. The message I receive from my phone when trying to install the firmware is what I wrote earlier
Click to expand...
Click to collapse
You do have access to an sd card, physically. Apologies if I wasn't clear, but I've not come across any instance of anyone taking out their built in storage! So you did indeed apply my suggestion correctly.
And if that's the message you get, I can't help any further. All the best.

Unable to mount any partition

Hi,
after normally being a consumer on XDA for many years (actually started with the HTC Touch) and always been able to solve my problems by reading, this is the first time I am genuinly stuck and see no way out...
Following details:
- Phone: HTC One M9 International unlocked
- S-off
- Latest Nougat firmware with ICE ROM
All worked fine until today. I was copying Titanium Backup data from internal storage to external SD card and out of nowhere the phone tried to reboot. As of that point it just keeps in a bootloop and will not stop. So...I have tried following:
- Boot to Bootloader: successfull
- Boot to Download: does not work, results in a bootloop
- Boot to Recovery (latest TWRP installed): does not work, results in a bootloop
- From Bootloader tried to fastboot flash recovery. It tells "OKAY" but does not do anything
- Tried all the fastboot erase options: no change
- Fastboot boot twrp recovery: this works allowing me to use TWRP with following symptoms:
- Clean ROM install, stuck at 61.82% and does not continue
- Mount or Wipe fails on any of the partitions: "Unable to mount...." system, cache, data...whatever.....it cannot mount anything
- ADB sideload does not work
- Clean RUU Install does not work, tells me the battery is below 30% where it is charged fully
- Putting RUU zip straight on SD does not trigger install
- Fastboot oem relock does not work
Now I am actually lost for any further ideas. I am afraid there is some hardware corruption or so, but am not sure if there would be any other option to try, or if someone has any further ideas for me.
As I said....reading normally solves all my issues, but I have been reading everything i could find on this topic and tried everything, but all without success....
Thanks for any suggestions...
Cheers
Remko

remko said:
Hi,
after normally being a consumer on XDA for many years (actually started with the HTC Touch) and always been able to solve my problems by reading, this is the first time I am genuinly stuck and see no way out...
Following details:
- Phone: HTC One M9 International unlocked
- S-off
- Latest Nougat firmware with ICE ROM
All worked fine until today. I was copying Titanium Backup data from internal storage to external SD card and out of nowhere the phone tried to reboot. As of that point it just keeps in a bootloop and will not stop. So...I have tried following:
- Boot to Bootloader: successfull
- Boot to Download: does not work, results in a bootloop
- Boot to Recovery (latest TWRP installed): does not work, results in a bootloop
- From Bootloader tried to fastboot flash recovery. It tells "OKAY" but does not do anything
- Tried all the fastboot erase options: no change
- Fastboot boot twrp recovery: this works allowing me to use TWRP with following symptoms:
- Clean ROM install, stuck at 61.82% and does not continue
- Mount or Wipe fails on any of the partitions: "Unable to mount...." system, cache, data...whatever.....it cannot mount anything
- ADB sideload does not work
- Clean RUU Install does not work, tells me the battery is below 30% where it is charged fully
- Putting RUU zip straight on SD does not trigger install
- Fastboot oem relock does not work
Now I am actually lost for any further ideas. I am afraid there is some hardware corruption or so, but am not sure if there would be any other option to try, or if someone has any further ideas for me.
As I said....reading normally solves all my issues, but I have been reading everything i could find on this topic and tried everything, but all without success....
Thanks for any suggestions...
Cheers
Remko
Click to expand...
Click to collapse
Sounds like a chip on your motherboard went bad. Try pulling the system information (fastboot getvar all) and seeing what comes up. I'd bet you get some missing information, which is a sign of the same.

C:\HTC10\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT577YJ00072
all:
finished. total time: 0.156s
That is what getvar gives me. I also have the feeling that fastboot isn't working as it should. Flashing recovery also gives me OK but does not seem to work...

[Solved] Bootloop issue on Stock phone. Possible to fix without loss of data?

Hi Everyone
Newbie here so please be gentle. I have a HTC One M9 that has gone into a permanent bootloop for no apparent reason. It happened yesterday. Noticed that my phone was a bit sluggish so I decided to restart it but it didnt completely restart and went into the boot loop. The only significant change that I can think of was that I updated HTC Senses via the play store a few days ago and this was the first time I have restarted the phone after that update.
I have not modified the phone in any way and has the stock rom installed. I can access the bootloader and recovery mode. Here is a dump of fastboot getvar all command:
With the phone in Bootloader screen
C:\Temp\AndroidApp>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
all:
finished. total time: 0.149s
With the phone in download mode:
C:\Temp\AndroidApp>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
all:
finished. total time: 0.047s
I do not have developer mode or USB debug enabled (wish I had enabled these before this happend!! )
I have tried to install an OTA update via the the 'Apply Update from SD card' method (from recovery mode) and tried to use the OTA_HIMA_UHL_M60_SENSE70_MR_HTC_Europe_3.35.401.32-3.35.401.12_release_487250.zip but I get an error after the 'verifying current system...' message which says:
System partition has unexpected contents E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Considering that I have not modified the phone in anyway, not sure why I am getting this error message as I was hoping that applying the OTA might fix the bootloop issue. If I was able to update using the OTA, would that have solved my issue? Is there any way of overcoming the Status 7 error?
Considering that I dont have developer mode enabled and USB debug enabled, is there any posibility to accessing the system files and flashing the system partition with a stock image without having to wipe personal data or do I have no choice but to do a factory reset, loose all my data and hope for the best? Any advice and step by step guide would be appreciated. Even if I can access my personal data on the internal drive and copy it somewhere else, that would be a result!
Many thanks
Rob

There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.

shivadow said:
There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.
Click to expand...
Click to collapse
Thanks you very much!!!
Phone is alive again thanks to your instructions. I had given up after trying different things. I tried flashing the RUU via fastboot but kept getting an error 9 (something to do with security). Even the factory reset option from the recovery menu wasnt working (it formatted, unpackaged and then rebooted into the boot loop) hence I gave up hope and bought a Nokia 8 as a replacement (Still prefer the M9 but I'll give the Nokia some time). If you had responded towards the begining of the week, you could have saved me £300
Any ideas why the factory reset option did not work considering that I had not modified the phone in any way? (S-ON, bootloader locked, no custom ROMS or recovery mods)
Thanks again for your help. :good:

Unfortunately I don't have time to monitor the forum and answer immediately, even if it saves someone a few quid.
Under the consumer rights act (UK) you can return the phone within the 2 week grace period for a no quibble money back. You don't need a reason. After 2 weeks the device must be faulty.
The factory reset didn't work because android is inherently broken. There is no real valid explanation at this stage but the android developers know about it but do not know how to fix it.
In all circumstances where issues are encountered flashing stock the ruu via zip should be on the cards as it fixes many things on htc phones.

I've got a
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
.... Help ?

shivadow said:
There is a very strong chance the nand has failed and the phone is dead.
How big is the file you're flashing?. It should be at least 2Gb. If it is less than 2Gb then it's the ota.
If the file is 2Gb or more then rename it to 0PJAIMG.ZIP,
copy it to the "external" sdcard,
boot the phone into download mode and you should see "press vol up to flash" in yellow at the bottom of the screen.
Press vol up and it will flash. (make sure your phone is plugged into a charger).
When it is complete it will auto reboot. Do not turn the phone off even if it looks 'frozen'. The process should take 5-10 minutes.
Click to expand...
Click to collapse
Thanks. Do you know any other way to do that without sd card?

bricked htc m9

hi i was given an m9 so im trying to resurrect it first a few stats
soft version modified
locked
s-on
security warning
i can get into recovery mode
android recovery
htc/htc_himauhl/htc_himauhl
6.0/mra58k/buildteam02041257user/release-keys
then menu
reboot sys
reboot to bootloader
apply update from adb
apply update from sd card
wipe data/factory reset
wipe cache partition
power off
them some messages support api3
handle_cota_install install cwpkg to /cache/cota/cwpkg.zip
please any ideas??????????

First, we need to know more about your device.
You need adb and fastboot installed(I recommend Minimal ADB & Fastboot if you don't have already), HTC Drivers.
Put your phone in download mode and do "fastboot getvar all" remove imei/sn from output and post here.

lucyr03 said:
First, we need to know more about your device.
You need adb and fastboot installed(I recommend Minimal ADB & Fastboot if you don't have already), HTC Drivers.
Put your phone in download mode and do "fastboot getvar all" remove imei/sn from output and post here.
Click to expand...
Click to collapse
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
hi yes have adb just downloaded the original rru tyed to install via sd card but it failed

glinjik said:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
hi yes have adb just downloaded the original rru tyed to install via sd card but it failed
Click to expand...
Click to collapse
Do the command again from download mode not bootloader
Sent from my OnePlus 2 using XDA Labs

lucyr03 said:
Do the command again from download mode not bootloader
hi cant get into download mode it comes up in red
failed to boot to download mode press vol
up or down to back to menu
then htc log
then in red
this build is for development purposes only do not distribute outside of htc without htc's written permission failure to comply may lead to legal action
Click to expand...
Click to collapse

No download mode means no way to flash. Dead phone.

hi so i persisted and tryed holding power button vol up down etc and somehow got to this
HTC Download Mode
****locked*****
htc_himauhl pvt s-on
lk-1.0.0.0000
radio-01.01_u11440792_95.00.51130g_f
opendsp-15.6.1.00.522.8994_1026
os-3.35.61.14
feb 4 2016, 13:06:46(670363)
then the following
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
then in yellow
security warning
blah blah
sd card not mounted

glinjik said:
hi so i persisted and tryed holding power button vol up down etc and somehow got to this
HTC Download Mode
****locked*****
htc_himauhl pvt s-on
lk-1.0.0.0000
radio-01.01_u11440792_95.00.51130g_f
opendsp-15.6.1.00.522.8994_1026
os-3.35.61.14
feb 4 2016, 13:06:46(670363)
then the following
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
then in yellow
security warning
blah blah
sd card not mounted
Click to expand...
Click to collapse
I can't find a ruu for your phone.
Try to unlock bootloader, flash twrp and flash any marshmallow based sense custom rom.
Your only way to revert to full stock is s-off.
Sent from my OnePlus 2 using XDA Labs

hi is it possible to unlock bootloader from adb in download mode or twrp? is it possible to get soff in this mode?
i have the correct rru but i tryed to flash from sd
so i renamed the rru to opjaimg.zip
i get to flash menu press vol up to start flash
start ui_updating
it just goes back to bootloader

this is the rru i got
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_Orange_UK_3.35.61.14_Radio_01.01_U11440792_95.00.51130G_F_release_472007_combined_signed.zip

after trying again managed to get to recovery mode
android recovery
htc/htc_himauhl/htc_himauhl
6.0/mra58k/buildteam02041257
user/release-keys
use volume up/down and power
then reboot system now
reeboot to bootloader
apply update from adb
apply update from sd card
wipe data/ factory reset
wipe cache partition
power off
tryed apply update from sd card
gives following
e:failed to set up expected mounts for install aborting
e: failed to mount / devlog (invalid argument) try emmc mount
e: cant find device node for mount point/devlog
the list goes on
the goes back to recovery mode

You need to rename it to 0PJAIMG.zip
The first character it's zero(0) not O
And boot in download mode and follow the on screen instructions
Sent from my OnePlus 2 using XDA Labs

that 0 might b the problem il try that and report back thank you so far

tried the official rom just goes back to bootloader gonna try a custom rom next fingers crossed

tried flashing from sd get
255
255
fail 255

glinjik said:
tried flashing from sd get
255
255
fail 255
Click to expand...
Click to collapse
Fail 255 indicated a broken SD card as far as i know.

il give it a go with a different sd card

Hello,
i have a big problem with my HTC one M9 OS 3.35.161.12( s-on, bootloader locked)
Recovery mode is broken , i'm able to enter into download mode, but when i want to flash a zip file i have problems to enter into RUU Mode because it is in a bootloop after i give the command "htc_fastboot oem rebootRUU" , it means the phone attempts to enter into RUU mode but it keeps just restarting in the black screen with htc Logo for 2 -3 sec.
can annybody pls tell me what can i do to repair the RUU mode?