HTC ONE M9 Bricked? - One (M9) Q&A, Help & Troubleshooting

Hi there, so I'm having a bit of a problem. I tried to revive my old M9. I remember flashing it with a custom ROM (Android HD Revolution) and everything was fine. I left it since I got a new phone and today wanted to play around with my M9 again.
However, it would be stuck with the HTC Logo while loading, and my TWRP was gone, could no longer boot into it and my download mode was also screwed, as it gave me the error (failed to boot to download mode).
Anyway so I tried restoring to one of my TWRP backups, by mounting a TWRP img file first using my PC. It went fine, after that I booted into system and the HTC logo would be on white background and preventing me from using the screen, although funnily enough the system was functionally normally i.e. the volume keys worked and I could see it change on screen but, it was just as if I had a some kind of overlay and couldn't use the screen itself by touching.
I then tried to flash with the same custom ROM, but after installing it and rebooting the phone it was stuck in a boot loop, where it would shutdown and try to boot again.
So I turned it off using power up and home button, and tried to wipe the partition to install another ROM, using the same TWRP method I did above.
Only this time, I can't do anything: wipe, install, format etc. I get the error "Failed to mount '/data' (Invalid Argument)" "Failed to mount '/cache' (Invalid Argument)" whenever I try doing anything within TWRP. I can't even mount cache, system or Data. It is if they're not there.
And now my phone is back to where it started, i.e. infinite boot screen with HTC Logo and "This build is for etc..." text.
Note: Trying to change file system from ext4 to ext2/3 and back to ext4 does not fix the problem ,as the same errors pop up when trying to change file system.

90% chance the nand is goosed. 10% chance of recovering by flashing a stock firmware in download mode (same version as currently installed, external sd card method).
Twrp has a known issue for bricking devices at random.

Related

[Q] Unable to mount cache, system, data

Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
ericmerl said:
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
Click to expand...
Click to collapse
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Stock ROMs
Larry2999 said:
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
ericmerl said:
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
Click to expand...
Click to collapse
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
ericmerl said:
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
Click to expand...
Click to collapse
To follow up again, I was able to re-flash TWRP using Odin. Once that was done, the phone no longer tried to boot straight to recovery. I was able to three finger into TWRP, though it took a super long time for it to boot.
Here's the console log taken from TWRP once it boots:
Code:
E:Could not mount /data and unable to find crypto folder.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
Running boot script...
Finished running boot script.
E:Unable to mount '/cache'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E:Unable to mount '/data'

Note 2 sudden problem

This happened a few days ago. So first of all what happened was before I went to sleep my phone rebooted by itself for no reason which I thought that maybe my phone died,But the next morning i woke up to a samsung logo on my phone (not blinking) which I thought was rebooting again, but it wasnt booting into the OS. Im running dirty unicorn 4.4.4 (final ver) and the unicorn booting animation wasnt showing up. Before I try to boot/go into recovery/bootloader there is a red blink ( not too sure if that was always there) and I am able to access my recovery and bootloader. I checked my recovery log and it says the following:
E:unable to find partition size for '/boot' '/recovery' '/modem'
E:unable to mount '/efs' '/cache' '/system' '/data' storage /data/media during GUI startup
E:Failed to get default contexts and file mode for storage files
So seeing this I tried going into my bootloader which I was successfully able to go. Therefore I tried flashing stock through odin and resulted in failing or just freezing. *Had notes about being unable to write
I had this phone for 2 years without any problems and I'm with Rogers. Has anyone else gone through this or know a solution?
A similar thing happened to me recently. The battery was part of the problem I believe (for 2 of my Note 2s), as it wasn't holding a charge properly (this was causing problems from charging, to regular freezes, reboots). Finally, the last time the phone just got stuck on the samsung boot logo. By then, I had my new battery, so I swapped that in - but that didn't fix the problem. I booted into Philz recovery and saw the same error messages as you. I wiped dalvik cache 3 times, factory reset, and reset for installation of new rom (which still gave me the same error messages and something about unable to format E. Despite the error message, I proceeded to reinstall the custom Rom (Ditto Note 3) again from an external SD card. Everything loaded up like normal. SMS, chat records, contacts were all in tact (like a dirty flash). That said my wifi was having issues - so I ended up redoing the aforementioned process (clear cache, factory reset, reset for installation of new rom). This time no messages about the E: location. Installation was fresh and all content was wiped clean. The wifi issue was still occurring - but it turned out I just needed to install the AGNI kernal again.
Good luck
Note2Hunter said:
This happened a few days ago. So first of all what happened was before I went to sleep my phone rebooted by itself for no reason which I thought that maybe my phone died,But the next morning i woke up to a samsung logo on my phone (not blinking) which I thought was rebooting again, but it wasnt booting into the OS. Im running dirty unicorn 4.4.4 (final ver) and the unicorn booting animation wasnt showing up. Before I try to boot/go into recovery/bootloader there is a red blink ( not too sure if that was always there) and I am able to access my recovery and bootloader. I checked my recovery log and it says the following:
E:unable to find partition size for '/boot' '/recovery' '/modem'
E:unable to mount '/efs' '/cache' '/system' '/data' storage /data/media during GUI startup
E:Failed to get default contexts and file mode for storage files
So seeing this I tried going into my bootloader which I was successfully able to go. Therefore I tried flashing stock through odin and resulted in failing or just freezing. *Had notes about being unable to write
I had this phone for 2 years without any problems and I'm with Rogers. Has anyone else gone through this or know a solution?
Click to expand...
Click to collapse
jun3280 said:
A similar thing happened to me recently. The battery was part of the problem I believe (for 2 of my Note 2s), as it wasn't holding a charge properly (this was causing problems from charging, to regular freezes, reboots). Finally, the last time the phone just got stuck on the samsung boot logo. By then, I had my new battery, so I swapped that in - but that didn't fix the problem. I booted into Philz recovery and saw the same error messages as you. I wiped dalvik cache 3 times, factory reset, and reset for installation of new rom (which still gave me the same error messages and something about unable to format E. Despite the error message, I proceeded to reinstall the custom Rom (Ditto Note 3) again from an external SD card. Everything loaded up like normal. SMS, chat records, contacts were all in tact (like a dirty flash). That said my wifi was having issues - so I ended up redoing the aforementioned process (clear cache, factory reset, reset for installation of new rom). This time no messages about the E: location. Installation was fresh and all content was wiped clean. The wifi issue was still occurring - but it turned out I just needed to install the AGNI kernal again.
Good luck
Click to expand...
Click to collapse
So did you install it using an external sdcard?

TWRP unable to mount /data /system etc

Hi there,
I'm kind of stuck right now, my HTC One M9 from Sprint, some day I turned it on, and just shows the HTC logo and reboots, I am able to use TWRP (2.8.7.0) but I can't install any zip from Stock Rom or Venom, I even tried to upgrade TWRP with different versions but nothing it always saying the E:Unable to mount '/data' or /system, /cache, etc, I can use the installer from Venom Rom and it seems to be ok, but at the end always the same with the unable to mount legend.
I can't use Download/fastboot mode, shows failure.
I am able to use adb commands from my PC but not for fastboot, just sticks with "< waiting for device >".
I tried to format those folders (data, system, etc) to FAT or eXFAT it shows succesful, but after I reboot remains in EXT4.
I don't really know how to work with this anymore, I believe that the problem is those folders?
if yes, is there a way to fix it?
if not, what can I do then?
Thank you in advance for any suggestions
=========
HTC One M9
TWRP 2.8.7.0
Unlocked
S-ON
Sprint
Those errors are usually caused by a borked twrp. If flashing this one https://drive.google.com/file/d/0B4vTiHTBB629XzliRF9OaTdjZ00/view?usp=drivesdk doesnt work then you'll have to flash back to stock and start over.
Beamed in by telepathy.
shivadow said:
Those errors are usually caused by a borked twrp. If flashing this one https://drive.google.com/file/d/0B4vTiHTBB629XzliRF9OaTdjZ00/view?usp=drivesdk doesnt work then you'll have to flash back to stock and start over.
Beamed in by telepathy.
Click to expand...
Click to collapse
I tried but shows the same (unable to mount e /data etc) could you tell me how to "flash back to stock and star over"?
Thanks @shivadow

Download broken, twrp unable to mount or format data...paperweight?

Hi I was running leedroid m9 with root and s-off. Last night main system processes started in on a crash loop, thinking of my normal methods I rebooted the phone. Cue boot loop. At first I wasn't able to get into recovery but then I miraculously got in...only to be met with being unable to mount, wipe, or format anything (unable to mount /x (invalid argument)) apparently due to encryption that I had never set up (unable to find crypto footer). When I attempt to format data I get something along the lines of "failed to remake data" along with the same slew of mounting errors. Also download mode just doesn't work, stays at the HTC splash. Is there any hope for my phone in this state or is it donezo? Maybe something to be done twrp terminal?

Soft bricked. phone not coming back

Okay so my phone was acting up a little where it was working fine and after a few days apps would start crashing so I would reflash the ROM I was using and it would be fine again for a few days and then it would happen again.
So I decided ill just go back to full stock and I went through the path of using the MSMdownloadtool.
So I put my phone into download mode and restored it. the first strange thing is when it was fully complete the device wouldnt reboot. it would seemingly go off and then default back to download mode and then the software would try and redo the process again even though it succeed.
So anyway I unplugged the device and booted it up. It got to the OOS boot animation and it just kept going and never booted. so I booted to Fastboot and flashed TWRP Blu-Spark and it just shows "Failed to mount '/system' (Invalid Arguement" (It shows it for cache, data etc.. aswell) and it also says "Updater process ended with ERROR: 7" when I try to flash anything.
Ive done this entire process like 5 times and it seems like no matter what i do I just cant get my phone booted into anything. Also whenever I turn my device off it seems to enter download mode as it shows up on my PC under COM connections and it takes holding down the power button for ages for it to come out of it
Am I screwed. thanks
LJAM96 said:
Okay so my phone was acting up a little where it was working fine and after a few days apps would start crashing so I would reflash the ROM I was using and it would be fine again for a few days and then it would happen again.
So I decided ill just go back to full stock and I went through the path of using the MSMdownloadtool.
So I put my phone into download mode and restored it. the first strange thing is when it was fully complete the device wouldnt reboot. it would seemingly go off and then default back to download mode and then the software would try and redo the process again even though it succeed.
So anyway I unplugged the device and booted it up. It got to the OOS boot animation and it just kept going and never booted. so I booted to Fastboot and flashed TWRP Blu-Spark and it just shows "Failed to mount '/system' (Invalid Arguement" (It shows it for cache, data etc.. aswell) and it also says "Updater process ended with ERROR: 7" when I try to flash anything.
Ive done this entire process like 5 times and it seems like no matter what i do I just cant get my phone booted into anything. Also whenever I turn my device off it seems to enter download mode as it shows up on my PC under COM connections and it takes holding down the power button for ages for it to come out of it
Am I screwed. thanks
Click to expand...
Click to collapse
Try the other versions of TWRP too, including the official.
tnsmani said:
Try the other versions of TWRP too, including the official.
Click to expand...
Click to collapse
Ive tried a modified TWRP, Blu-Spark and the latest official TWRP from their website and I still get failed to mount on all of the partitions.
When I look at any of the partitions it says
"/system File system: ext4 . Present: Yes . Removable: No . Size: 2913MB . Used: 4MB . Free: 2909MB . Backup Size: 4MB" I tried to change the file system but cant mount. any of them to even format" I get an ERROR code 8 if I try to repair the partition
If I try to flash anything I get "E1001: Failed to update system image" "Updater: process ended with ERROR: 7"

Categories

Resources