[Q] HTC One M7 Un-mountable partitions - AT&T HTC One (M7)

I have an M7 that gets stuck on the HTC boot screen. I can flash recovery, view files view file manager while in recovery TWRP. However trying to wipe cache/dalvik etc. I get an 'unable to mount /*' error. I have tried the RUU process which was successful but the issue remained unresolved. I have tried the mkfs.ext4 to try and unblock the blocks with issues without success.
I have bootloader unlocked, I tried flashing the SuperUser but it failed due to the mount issue. So I have S-ON and yes... my phone has 30%+ power.
Any help ?

dakimMastamynd said:
I have an M7 that gets stuck on the HTC boot screen. I can flash recovery, view files view file manager while in recovery TWRP. However trying to wipe cache/dalvik etc. I get an 'unable to mount /*' error. I have tried the RUU process which was successful but the issue remained unresolved. I have tried the mkfs.ext4 to try and unblock the blocks with issues without success.
I have bootloader unlocked, I tried flashing the SuperUser but it failed due to the mount issue. So I have S-ON and yes... my phone has 30%+ power.
Any help ?
Click to expand...
Click to collapse
When you flashed recovery did you fastboot erase cache after you flash it and before you rebooted? If not, you need to do that to clear out any thing left from the last recovery.
Which custom recovery are you using with the version number?
What was the RUU version and where did you get it?

Related

[Q] CWM Recovery wont boot with HOX+

Also posted in HOX forum, but should be here... So here again:
I'm trying to install Clockwork recovery mod 5.8.4.0 on my HOX+. I've unlocked etc and flashed it to the device successfully. Now when I go to recovery it shows the HTC screen and then the phone turns itself off. even after multiple attempts, nothing...
Any tips/tricks?
Is it the HBOOT version maybe? I have 1.35.0000
install TWRP from http://www.teamw.in
fastboot erase cache
fastboot flash recovery (name of recovery).img
fastboot erase cache
Gerolamos said:
Also posted in HOX forum, but should be here... So here again:
I'm trying to install Clockwork recovery mod 5.8.4.0 on my HOX+. I've unlocked etc and flashed it to the device successfully. Now when I go to recovery it shows the HTC screen and then the phone turns itself off. even after multiple attempts, nothing...
Any tips/tricks?
Is it the HBOOT version maybe? I have 1.35.0000
Click to expand...
Click to collapse
If your posting in the HOX forum. Does that mean you also flashed CWM for the HOX? Because it's not compatible with the HOX+.
Sent from my HTC One X+ using Tapatalk 2
skdubg said:
install TWRP from http://www.teamw.in
fastboot erase cache
fastboot flash recovery (name of recovery).img
fastboot erase cache
Click to expand...
Click to collapse
Ok done that... Worked like a charm.
Then flashed to InsertCoin and failed, tried to recover, failed. TWRP wouldn't boot.
So I tried installing my RUU again (2nd time in 2 days), but during the signature verification process it suddenly stopped, got an error. Now I'm stuck at the black screen with silver HTC lettering........ Can't reboot nothing! HELP!
which TWRP file do you download and flashed?
to install RUU you need to relock the bootloader
skdubg said:
which TWRP file do you download and flashed?
to install RUU you need to relock the bootloader
Click to expand...
Click to collapse
Got TWRP working finally and managed to restore my backup.
There seems to be something I'm doing wrong here... Every time I flash my device, I keep getting stuck in airplane mode and it wont get out... So, no cell reach or wifi. Does anybody have a suggestion what it might be?

[Q] No Os, reboot resulted in Bootloop Need Help

Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally​
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
clrsri2006 said:
Hi all,
chronological steps to bootloop after rebooting, when no os warning sign appeared.
Successfully Unlocked boot loader.
Successfully install twrp custom recovery
installing root wasn't successful.
Then I tried to check features of TWRP which resulted in always booting to recovery.
I might have deleted some data accidentally​
Then after many attempts to restore to stock rom I flashed RUU 1.26 from guru's website ...
Phone booted but had touch screen issues.
In an attempt to fix I realized that I could only do with s-off and then tried to flash the correct RUU for 3.17.502.3 firmware but wasn't successful.
I realized the present RUU(1.26.X) might be the reason for all(any .zip) failures from twrp.
I tried to format system and push RUU for 3.17.502.3. But I accidentally rebooted when there was no OS warning came up. It got stuck in Bootloop with HTC logo. My attempts to power it down didn't work and when I press power button + volume down or just power button the led back lights on the home and back buttons flash.
firmware version 3.17.502.3
hboot 1.55 s-on
Phone shows up as HTC MTP device because of which adb/fastboot doesn't recognize the phone.
I guess this is what a brick is called. Is there a way to recover from this ?
Few questions:
1. How can I power off the device? Its been in bootloop for 6 hrs now. I'm afraid the screen will go bad
2. How can I use adb/fastboot in mtp modes to get it to power off / reboot to boot loader?
Thanks in advance.
PS: I have tried all these stuff(rooting, flashing custom recovery / kernels) on 3 samsung phones with out any issue, the procedure was much easier than it is for htc devices. After a day long attempt to root my phone I might have bricked it
Sriram
Click to expand...
Click to collapse
UPDATE : The reboot to boot loader via power button + volume down works but it took about 2 mins of holding those buttons, which is unusually long time. So its not a brick As experienced developers say DO NOT PANIC, staying calm and read the forums thoroughly has helped.
I'm trying to see how I can fix the .zip install failures now.
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
TopoX84 said:
Search for adb sideload, adb push or usb-otg
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
clrsri2006 said:
adb sideload isn't working though adb / fastboot work fine.
did try adb push a dirty unicorn rom and tried to install, just to test, it didn't work either
The problem i'm facing now is:
I have installed 1.26 RUU on 3.17.502.3 because that is the only RUU with cid CWS_001 which started all the issues.
From then i'm not able to install any zip files. Now that i deleted the system thinking i can flash another RUU I keep getting error: unable to mount cache. when ever i try to install something.This is one problem the other is for flashing an RUU i need s-off and for getting s-off i need to have ROM that matches with my firmware version(which i'm not able to get) Its kind of deadlock situation i guess.
As I have 1.55 hboot revone doesn't work and tools based on rumrunner fail at second test because when they reboot its going to fastboot usb mode and fails at that point.
Click to expand...
Click to collapse
UPDATE : After many attempts I could work it out by using guru reset .zip file (1.26.502.12). I did this before as well but was not able to get s-off previously. This time I asked to install superuser when resetting using guru reset file. I got the 1.26 one back with disabled touchscreen. Then I used rumrunners and got s-off and then used the ruu for 3.17.502.3 exe file to get the working on.
Now the bootloader just says unlocked but not tampered. I got the twrp recovery again as it was very handy for me.
I was able to get supercid. Now trying for ARHD 51.0.
After I got the RUU for 3.17.502.3 the only issue i noticed is that when phone boots up I just see HTC instead of "HTC quitely brilliant"

[Q] Bricked Phone :(

Hey guys,
Hoping to get some help.
I was updating TRWP 2.7.0.0b and firmware to 4.13.651.4. To update flash Viper's rom. It all flashed correct but when I rebooted to flash the rom, it would error out to "E: Unable to mount \cache, \system." Also I noticed during the boot, I was getting Tampered and Locked notification within Bootloader. So I tried to reflash TWRP http://teamw.in/project/twrp2/98 but the when I goto Recovery, TWRP no longer has touchscreen capabilities; I can't do anything within it. And it's showing TWRP v2.3.1.0 after trying to reflash
Any tips on how to get a rom back on phone?
*** Update ***
Okay back on TRWP 2.7.0.0b // HBoot 2.10 // FW 4.13.651.4 // S-OFF, Locked
When trying to flash any rom, I get the unable to mount messages.
What specifically is recovery saying it's unable to mount? Also, what ROM are you trying to flash?
Sent from my HTC device
FinZ28 said:
What specifically is recovery saying it's unable to mount? Also, what ROM are you trying to flash?
Sent from my HTC device
Click to expand...
Click to collapse
It specifically says:
Updating Partition Details...
E: Unable to Mount '/cache'
E: Unable to Mount '/system'
This is happening any rom that I've tried so far.
Vipers, Liquidkitkat, and even Sense5.
Recovery.log file with the error when trying LiquidKitkat
Go into TWRP and try wiping system and cache (under the advanced wipe tab). May also try a factory reset (from recovery, not the bootloader). I've run across this issue a time or two on the old format.
Sent from my HTC device
preyed said:
Hey guys,
Hoping to get some help.
I was updating TRWP 2.7.0.0b and firmware to 4.13.651.4. To update flash Viper's rom. It all flashed correct but when I rebooted to flash the rom, it would error out to "E: Unable to mount \cache, \system." Also I noticed during the boot, I was getting Tampered and Locked notification within Bootloader. So I tried to reflash TWRP http://teamw.in/project/twrp2/98 but the when I goto Recovery, TWRP no longer has touchscreen capabilities; I can't do anything within it. And it's showing TWRP v2.3.1.0 after trying to reflash
Any tips on how to get a rom back on phone?
*** Update ***
Okay back on TRWP 2.7.0.0b // HBoot 2.10 // FW 4.13.651.4 // S-OFF, Locked
When trying to flash any rom, I get the unable to mount messages.
Click to expand...
Click to collapse
Run the newest RUU, let it boot once, hit fastboot and reflash twrp. should take 15 minutes.

[Q] E: Unable to mount '/system': Bricked after ROM Update

I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Gleichzwei said:
I tried to update my device with the newest ROM (Dirty Unicorns) and somehow bricked it. ...
The device just stuck in the flashing process for over 10 hours. After TWRP and Fastboot were still working, I tried a lot of things to revive the system, but everything I tried went wrong.
First I tried to flash the factory image. The strange thing: that seamed to work well (with Wugfresh toolkit), but the device still stuck in a bootloop.
Everything I try in the recovery mode ends by TWRP with "E: Unable to mount '/system'" (in red letters). So I tried to flash the factory image again and wiped the device in the newly flashed Revovery completely.
No change: "Updating partition details... E: Unable to mount '/system'".
- ABD sideload doesn't work. I tried to flash system.img. No success.
- Bootloader is unlocked. V3.44.1.0123
- Newest TWRP (twrp-2.8.7.0-flounder.img)
Here are the best Android-experts worldwide! So can someone please help me?
Thanks in advance!!
Regards,
Frank
Click to expand...
Click to collapse
Boot to bootloader, and enter the following commands:
fastboot format cache
fastboot format userdata (NOTE THAT THIS WILL WIPE THE CONTENTS OF YOUR SDCARD)
fastboot reboot

Data partition "corrupt" - cant unlock bootloader or factory reset?!

Hey folks,
got a htc one max which says its encrypted upon boot. No matter what you enter it says password is correct but data corrupt and that it needs to factory reset - which always fails.
When I enter bootloader mode and choose factory reset it also fails. Same in the stock recovery.
To manually format the data partition I wanted to unlock the bootloader and flash twrp but the unlock fails too - it accepts the token and shows the unlock screen, but when I click yes is goes into recovery to wipe (which fails again) and then remains locked.
Any ideas? I am very experienced with android and problem fixing but in this case i need some tips please.
Will try to find a fitting ruu and restore that, but I think i still need to manage to format the data partition somehow.
Fastboot format or erase also dont work because of the locked bootloader..
ahh ... somehow the unlock apparently did work, so now i can flash twrp and format data with it!
TWRP can not WIPE or BOOT
I am having the same problem and when I flash TWRP it works and then go into recovery ok
Now is the problem NO matter what ROM I flash it is still ENCRYPTED after flashing a ROM it boots to the password screen.
This phone had a stock ROM on it and when I unlocked the bootloader through HTC everything went fine and it rebooted to desktop
I then proceeded to adb and flash TWRP recovery twrp-3.0.2-0-t6univ.img everything seemed to be ok at this point.
First thing I did after flash TWRP is do a backup of the original image as is
Then proceeded to flash a ROM SPRINT-Y8_5.0.2_Sense7-2016-03-05.zip
After flash then the encrypted screen appeared saying i have 30 chances to guess password and then the phone will wipe data and factory reset.
After first guess since I had never encrypted the phone I just hit enter and it said UNSUCCESSFUL just a RESET button appears
But the name of the encryption says its Chameleon
I have tried many Roms now and still the same thing .
Here are SPECS of phone the way I bought it.
I even did a restore from the original backup and still the encryption screen appears.
T6WHL XA SHIP S-OFF RH
CID-11111111
HBOOT-2.49.0000
RADIO-1.48.50.0109
OpenDSP-V33.120.274_T6.0829
QSC-
OS-2.06.651.1
eMMC-boot 2048
Feb 12 2014,21:03:58.0
I figured it out the only way and very simple way if anyone else runs into this problem.
REMOVE MICRO SD FROM PHONE
Then boot into TWRP recovery and FORMAT DATA ( you will loose everything on the phone ) including the Micro SD card if you leave it in.
Put Micro SDCARD back in with what ever ROM you choose and Flash away
PS:: If you do not have TWRP installed then boot to fastboot and connect to computer and flash twrp image for your phone. This also works on HTC M8 Sprint

Categories

Resources