Unable to mount any partition - One (M9) Q&A, Help & Troubleshooting

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...

Related

[SOLVED] Semi-bricked Desire: No SDCard, No USB - Learn Fastboot Ninja Skills?

Hi all,
I have an interesting problem that I have now given up on solving on my own.
I was following this guide (phone was already rooted): t-mod.org/182-2/desire-tutorial/
I got through unrevoked fine, alpharev fine, sd partition fine, radio flash fine and system rom fine - all was going well.
I then got the all-too-familiar boot looping (forgot to clear one of the caches probably?), so I rebooted into recovery, factory reset, wiped cache/dalvik/data, reapplied the ROM and rebooted again.. .same story.
Now this is where it veers off course and becomes like no other rom-flash stuff-up I've ever done before (I re-rom every couple of weeks... I get bored easily). I enter recovery mode again and it can't read my SD card (32gb):
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
Error mounting /sdcard/!
Click to expand...
Click to collapse
Thinking it was a potential SD card formatting ****-up I put the card into my pc and loaded it up - it was perfect, my computer showed me exactly what was on the card (system rom and radio rom). Thinking there could some harm done that the phone dislikes I insert another SD card (16gb only ever used with the Desire) and the same error happens, I get yet another SD card (1gb), same thing.
In between scratching my head and tearing my hair out, I jump into the fastboot command line, reflash my NANDroid backup and start my phone - WIN. My phone boots, I have a working original rom and can place calls etc. Still no SD card functionality though. Not too phased and thinking I can fix it anyway I look into a few more solutions to my problem and one revolves around re-Alphareving. So I reboot the computer, phone attached, Alpharev boots up and then fails to find my phone. I check usb debugging and it's on. I then notice that the phone isn't receiving usb power from the computer. So now I have a phone without a working SD card slot and with no usb functionality except at fastboot... what the hell did I do?
I wanted to go back to my original RUU and start fresh, but without usb debugging access I'm screwed.
Is there a way that I can use fastboot to sort out something like the mtd0.img solution (which requires terminal access form phone and usb / sdcard)?
Am happy to sling over some technical details, but let me begin with the commands that have so far had no effect:
fastboot -c "board_bravo.disable_sdcard=0 board_bravo.disable_uart=0" reboot
fastboot oem enableqxdm 0
fastboot -c board_bravo.usb_h2w_sw=0
fastboot -c board_bravo.disable_uart=3
Click to expand...
Click to collapse
Of note however, is that I ran:
fastboot oem sdtest
Click to expand...
Click to collapse
and the sucker returned:
C:\>fastboot oem sdtest
...
(bootloader) [SD]power_addr=0xB1400000
(bootloader)
(bootloader) [SD]clk_addr=0xB1400004
(bootloader)
(bootloader) [SD]mclk_md_addr=0xA86003DC
(bootloader)
(bootloader) [SD]mclk_ns_addr=0xA86003E0
(bootloader)
(bootloader) [SD]SDC4_BASE_PHYS=0xA0600000
(bootloader)
(bootloader) [SD]SDC4_BASE_virt=0xB1400000
(bootloader)
(bootloader) sdc_ns_reg value=0xFFF60B59
(bootloader) sdc_ns_reg value=0xFF9E0B58
(bootloader) Cmd5 CMD_TIMEOUT
(bootloader) sdcc_poll_status(): status=4 i=1966
(bootloader) Cmd5 polling status timed out
(bootloader) SD: CMD5 fail, rc=2 ..
(bootloader) sdc_ns_reg value=0xFF9E0B58
(bootloader) SD_CMD8.resp[0] =0x1AA
(bootloader) SD_ACMD41.resp[0] =0xFF8000
(bootloader) SD_ACMD41.resp[0] =0xC0FF8000
(bootloader) HC card
(bootloader) SD card mfr_month=2011 mfr_year=2
(bootloader) sdcc_init_memory_device done
(bootloader) sdc_ns_reg value=0xFFF60B59
(bootloader) card_type = 6......................
(bootloader) SD enable 4 bit mode
(bootloader) read/write test:
(bootloader) SD Read/Write Test OK!!
OKAY [ 1.167s]
finished. total time: 1.167s
Click to expand...
Click to collapse
What does all this mean?!
It would seem I sorted it out...
I did a Fastboot recovery flash using the s-off recovery image from here: http://forum.xda-developers.com/showthread.php?t=1039954
fastboot flash recovery recovery-clockwork-3.2.0.1-bravo.img
Click to expand...
Click to collapse
I can use the SD-card again, but for some reason I can't mount it in recovery mode and transfer files - but I suspect this is a Windows driver issue (comes up as unknown device) and doesn't stop me from copying files directly to the SD.
Install hboot and htc sync drivers and you should be able to copy files to sd card.
SwiftKeyed from Oxygen with Transparent XDA App

[Q] Unable to flash some ROMs I think its my internal storage

Hello,
Grab a drink and settle in, this ones lengthy!
My HTC one XL (UK, EE, Evita, CID: ORANG001) has been uber slow recently and I'd been wanting to have a tinker, remove bloatware for a while. So I set about investigating unlocking bootloader, rooting and flashing a funky ROM.
I first created a backup of phone using a couple of apps (to be safe, easy backup & Helium), then I copied all of the phone folders to my PC (to be safe), then I installed CWRom Manager and then from there installed CWM Recovery (6.0.2.8), unlocked the bootloader through HTCdev, no issues, booted back into CWM and made a backup.
Then I rooted my device using "BETA-SuperSU-v2.66-20160103015024" via the command line prompt, no issue there, took another backup in CWM Recovery.
Then I booted my phone, went into CWMRom manager, chose to flash a ROM "CM 10.0.0" and rebooted, phone got stuck at cyanogen mod screen and restarted x2 (realised I hadn't flashed the boot.img)
flashed the boot img via cmd line and phone booted into the initial set up screen (happy as a pig in dirt I was)...then I realised the touch screen wasn't working, bit of googling, found it a common problem, bit too late @ night to resolve, plus I couldn't find the correct file to replace the screen drivers, so I thought I would just revert.
I think (because I can't exactly remember this pattern of choices) that I chose the wipe/factory reset in CWM thinking that I would simply undo all that I'd done, re-do (as I quite enjoyed it) and select a different ROM, so when I booted into bootloader I think I then chose "clear data", the phone rebooted but got stuck at the white HTC quietly brilliant screen.
Realising there was no O/S, into Bootloader again and this time chose fastboot, went onto my PC but it wouldn't recognise the SD card in the phone and wanted me to format it. So I did so, I chose FAT32 and did a quick format.
Looking for a stock 4.2.2 ROM to return to I downloaded this "EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge", then flashed the boot img and it worked fine and got me my phone back to life, albeit T-Mobile and German bloatware.
I then tried to flash CM12.1 via CWM recovery, but it failed due to no file contexts and mounting issues (see attched pic) and at the end of it was status 7 error. I then maually mounted all points in CWM (/system /data /cache etc) and re-run, this time status error 0 message. Bit more googling led me to replacing the "META-INF" file from a working ROM (so I chose the ze German one) into the non-working CM12.1, and it worked. Phone booted, but it was back into the German ROM, not CM12.1.
So today, found my original nandroid backup from CWM recovery and restored to it. Phone back alive and working again. I downloaded CM11 (thinking it was better suited to my bootloader 2.18) but again, I get the mounting issues present with /system /data etc, BUT...when I tried to re-flash the german ROM, that worked. So it can flash something, just not everything.
So it can flash - but it seems that something just isn't right with my storage and I can't place it. I'm not sure of what commands to run to identify what partitions do and don't exist on the damn thing, so I could do with some help there. It feels like if I sort my storage issue out and get over that hurdle, I can flash a ROM. Do I need to re-create any -ext partitions?? I have downloaded an app, retrieved partition and usage info and have posted it also.
My current state as of writing;
Botloader unlocked
rooted with SuperSU
I have installed TWRP App, however I have NOT yet installed recovery, this is because it was asking me to confirm that /dev/block/mmcblk0p22 is the correct something - I just don't know how to confirm this and do not want to cause an irreversable change. I would prefer to resolve with CWM as I am used to using that now.
So many thanks if someone can help me.
Key info:
build number: 5.14.61.2 CL275436 release keys
I am aware of an update to firmware 5.18 (recommended for AT&T users) but I am a UK, EE user and no updates have been pushed to me. So I don't want to upgrade this yet either. I would rather remain at 5.14, get the thing working than risk bricking it with firmware while it's not 100% happy.
CWM recovery 6.0.2.8
Images of useful info I hope + disk usage - (Unable to post an external link to Drop box as I'm new, please PM me for images.)
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0000
(bootloader) version-baseband: 1.34a.32.45.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8311000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4101mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c20bff6f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.135s
[Solved]
So,
An update in case anybody else has this same issue. I solved it myself!
I twigged that CWM Recovery had become stuck/confused/corrupt as when I downloaded CWMROM and tried to reflash to the latest version, it advised me it had completed, but actually when I then booted in CWM recovery, it still showed the old version.
So I reflashed TWRP over CWM
Wiped the SD card
then proceeded to flash CM 12.1 & Gapps - worked first time
Rebooted - nowt, got stuck
Reflashed boot.img
Rebooted - success
it may help somebody else

HTC One M9 stuck on fastboot bootloader

Hi !
One of my friend ask me to try to save his One M9 phone, that seems to be bricked.
Here is the context :
- I absolutely don't know what he did, and it seems he don't either...
- The phone state is : Software status : Modifed, S-ON, and LOCKED
- I can't have another screen that Fastboot bootloader
The only options in the bootloader menu are :
REBOOT : it works
REBOOT TO BOOTLOADER : it works
BOOT TO DOWNLOAD MODE : does not work (Failed to boot to download mode)
BOOT TO RECOVERY MODE : does not work (Failed to boot to recovery mode)
POWER DOWN : it works
I tried a lt of things, and read a lot of threads before posting this one.
What i can say for the moment is :
- RUU flash using exe : does not work, i get an error saying the battery is too low
- RUU flash using SD card (extract rom.zip, renamed 0PJAIMG.zip, and put on the root of SD card) : zip is not detected at boot
- Getting bootloader unlocked : does not work, because fatboot oem get_token_identifier command seems unknown (probably because oem commands only work in download mode for this phone)
- Getting S-OFF : seems impossible without OS, as it needs Sunshine app installed...
- Few fastboot commands are OK (devices, getvar all, ...) but most of it are refused because of S-ON
- No adb commands are working
Here is the output of fastboot getvar all :
Code:
D:\ANDROID\RUU\RUU>htc_fastboot getvar all
(bootloader) version: 0.5
(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: FA56GYJ01267
all:
finished. total time: 0.094s
htc_fastboot finished. total time: 0.718s
So, from your experts point of view, is this phone definitely bricked, or is there a way to save it ?
Thanks for your precious help guys !
Hey! I have the exact same problem. Anyone knows how to fix that?
I unrooted, stocked and relocked the bootloader. Everything went fine first, was using the phone about two days. But after a restart I'm stuck in bootloader and can't boot to download nor recovery mode.
Phone is only working with fastboot commands.
I also tried these steps OP tried and everything is the same.
I tried to flash hosd file and this works, but still not able to boot to download mode.
The HTC One is an unbranded EU model with 3.35.401.12 (<- but I think there's nothing on the phone right now)
i am also facing same problem with 2 htc one m9 which i have, i also have XTC2CLIP box which is professional tool for all htc devices, i can S-off with this box of all htc phone even no os needed, but phone should accept bootloader mode & ftm mode, & in this case where we can only goto fastboot mode, S-off command not working in state... i spend lot of time but no luck... but i still believe its only software bug & can be solve with fastboot commands. because i aslo read about same problem on htc X model. & they use fastboot command for this problem. but these commands not working on m9 case.
no solution for this? I have one m9 here exatly with the same situation, already did all your debuging with the same results
Hi there! I'm new here, created an account specially for replying to this thread:
So I'm having the same problem, phone (EU M9) died on it's own. Everything is stock.
Tried all of the above, also no results...
Here is my log from "fastboot getvar all"
Code:
C:\Android>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
(bootloader) serialno:HT54NYJ04596
all:
finished. total time: 0.147s
If anyone has any ideas left, I'm happy to try them. For now, it's an ugly paperweight
If it died on its own and in a stock state then you can safely assume it's dead. Most likely nand failure.
Ps, dont all m9 serials start with an "F"?.
Beamed in by telepathy.
thank you
My guess is it tried to do an OTA update overnight, don't know exactly where it went wrong.
By the way, I do get some ADB communication:
First reboot to bootloader (so it doesn't say "Security Warning"), then select 'boot to Recovery Mode' and wait for the red triangle.
If it doesn't reach that point, reboot to bootloader once more. If it does reach the red triangle: hold the Power button and press the Volume Up button once. You can then release the Power button and Recovery Mode should become visible. Note that I tried several options in this menu including "Install from ADB" and "Install from SD Card", but both gave errors.
Hope someone can use this information.
I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?
KaiLoi said:
I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?
Click to expand...
Click to collapse
If it's spewing failed to mount errors then yes, dead phone. Only htc will be able to fix it.
Beamed in by telepathy.

Softbrick. No Download mode. Partitions fubar. Recovery works. Help plz?

My HTC One M9 decided to freeze and crash suddenly. I woke up one morning, the phone's alarm didn't go off, and LineageOS did not respond to touch input.
Upon rebooting I'm stuck in a boot loop (HTC boot logo).
I've tried going into recovery and wipe cache, system, data, and every other partition and reflash. No avail, though I can still boot into TWRP recovery:
Code:
Failed to mount /cache (invalid argument)
Failed to mount /data (no such device).
Failed to wipe dalvik.
Unable to mount storage.
I tried resetting to factory by using P98IMG.zip.
It says boot into download mode failed.
I suspect a corrupt internal memory (NAND fried).
Help? How can I get my phone working again?
Just out of curiosity, did you always update your twrp and supersu?.
Beamed in by telepathy.
shivadow said:
Just out of curiosity, did you always update your twrp and supersu?.
Beamed in by telepathy.
Click to expand...
Click to collapse
No, I used TWRP 2.8.7.0 for himaul and I didn't ever update supersu.
Hello, I am in a same situation. Any updates or solutions?
I cant even get CID and MID
\platform-tools>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
(bootloader) serialno:FA5B5YJ02594
all:
Finished. Total time: 0.152s
fastboot getvar cid
cid:
Finished. Total time: 0.011s
fastboot getvar mid
mid:
Finished. Total time: 0.013s
Click to expand...
Click to collapse
The internal NAND chip was fried. The device is irreversibly broken, it needed a new motherboard and at that point you're better off buying a new phone. It's unfixable.
0x80h said:
The internal NAND chip was fried. The device is irreversibly broken, it needed a new motherboard and at that point you're better off buying a new phone. It's unfixable.
Click to expand...
Click to collapse
How do you figure that? Just based on cid and mid?
I'm in a similar situation, trying to troubleshoot a phone that has never been flashed or unlocked. It can now only get to bootloader, no recovery or download mode. Its cid and mid also return blank in fastboot. Does that mean it is fried?
Any help is appreciated
Rakmo said:
How do you figure that? Just based on cid and mid?
I'm in a similar situation, trying to troubleshoot a phone that has never been flashed or unlocked. It can now only get to bootloader, no recovery or download mode. Its cid and mid also return blank in fastboot. Does that mean it is fried?
Any help is appreciated
Click to expand...
Click to collapse
Try to access download mode or recovery from both button combo and via bootloader. The information returned from fastboot is garbage because you need to do the getvar command while the phone is in download mode, not bootloader.
Try holding all 3 buttons and variations of 2 button combos. Sim in, sim out, sd in, sd out. You need download mode regardless. No download mode means dead as because that is the only way to flash any firmware. The os version will be displayed in download mode at the very top, if you get that far.
shivadow said:
Try to access download mode or recovery from both button combo and via bootloader. The information returned from fastboot is garbage because you need to do the getvar command while the phone is in download mode, not bootloader.
Try holding all 3 buttons and variations of 2 button combos. Sim in, sim out, sd in, sd out. You need download mode regardless. No download mode means dead as because that is the only way to flash any firmware. The os version will be displayed in download mode at the very top, if you get that far.
Click to expand...
Click to collapse
Thanks a lot for the tips Okay, here's what happens:
If I hold Volume up and down while starting, I get to the bootloader where I can choose reboot, reboot to bootloader, download mode, recovery mode, and power down.
If I try to just boot (or hold volume up while), it show HTC on white background for ~20 seconds, before rebooting and looping
If I hold volume down while starting, or choose download mode from the bootloader, I get white HTC on black background for ~1 second, before rebooting and looping.
If I choose recovery mode from the bootloader, I get "Failed to boot to recovery mode", and something about the build being for development purposes only (the phone has never been flashed or anything).
It is a family member's phone, so I cannot currently test with SD or SIM, I'm doing everything with those empty. Though, when the problem first appeared, both were present. Should I try to test with those?
Sounds like it's fked. No download mode means no fix.

[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?

Categories

Resources