Unable to mount /system/, /data/, or internal storage. Was attempting to switch to GPE. Can not flash roms due to the mounting errors and i can get into recovery, and hboot. I am s-off. If you need anymore info please ask.
Edit: When trying to boot i get HTC logo with a unlocked pad lock at the bottom.
Related
Hi All,
I got a problem with my HTC desire. Whenever i've tried to boot, it just goes under Hboot. When I try to get into recovery, the white screen with HTC logo appears and then just stucks right there. Is there anyway to solve it? Before that, I tried to mount sd card, but it say Error Mounting sd card and later I also tried to mount USB storage, but it didn't work. But now, I can't even go under recovery.
Flash a ruu in fastboot or reflash a recovery...
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
nodnarb said:
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
Click to expand...
Click to collapse
Try this, reformat your sdcard fat32 with a pc. Then place only this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip on the sd in no folders (Do not rename). Boot to hboot (vol down + power), it should find the file and prompt you to press vol up to install. I think your issue with the ruu before was that you were trying to flash an older version than you already have installed. If that dosent work try fastboot flashing cwm again, and see if it can mount the sd then.
Thread moved. Please post all questions here in the correct section of the forum.
Thanks
AvRS
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
shivaagarwal1 said:
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
You'll probably get better help in the Incredible S section. This is for just the plain olé Incredible.
Hey guys,
I need help pretty bad with my HTC One M8 on T-Mobile.
I am able to access recovery (currently TWRP) but all attempts to restore my phone have been unsuccessful. I cannot Wipe, Restore (from backup on SD) or Sideload any new images. And I constantly receive the error "E: Unable to mount 'data'" and "E: Unable to mount internal storage".
I unfortunately have S-On (I wasn't able to get to S-Off via firewater), and I am able to unlock and relock my bootloader but attempting to flash with RUU fails from "Signature Verification error" and the desktop RUU installer constantly fails!
Is there anything I should still try? Or am I screwed, I cannot seem to find a way out of this one.
Thanks everyone!
Use sunshine to s-off
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
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.