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.
Related
Got my Evo 3D (UK GSM version) today, what a great phone! Rooted it and flashed a few roms to see what worked best for me, not a problem. Found one that worked and left that running all afternoon customising it all, checking everything worked: sms, phone calls etc.. all fine, again no problems.
Picked up the phone again, flicked through the homescreens, tapped on an icon and it froze, tried pressing home, holding power nothing so I popped the case off and pulled the battery.
I put the battery back in to boot up but it just stuck at the HTC logo so I thought "right, this must be a dodgy rom, i'll do a nandroid restore from recovery" booted into bootloader, hit recovery, took it's time loading then gave me some errors along the lines of:
Can't mount cache/recovery/whatever a few times
Thought that was strange, never seen that before, I'll try clearing the cache before doing anything. Tried that and the recovery menu froze up. Rebooted and tried flashing a rom, that froze too so now I'm thinking "Oh no, i've cocked this one up"
Tried flashing the recovery again through fastboot but that always fails and now I can't even get into the recovery menu.
So anyway, at the current moment in time what I've got is:
Can't boot OS
Can't get into recovery
Trying to flash a recovery through fastboot fails
Trying to flash an RUU rom through either running the .exe fails to restart into bootlader
Trying to flash an RUU (or anything else for that matter) via .zip on the sd card fails with " - Fail-PU" on every line then "Partition update fail! Update fail!" at the end
Factory reset doesn't seem to do anything
Some details
-Revolutionary-
SHHOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.1107
RADIO 10.13.9020.08_2M
eMMC-boot
Jul 12 2011, 15:29:51
I just don't understand how it's managed to get into this state, I've flashed previous android phones before without a problem, I had the rom running fine for hours before it died on me, so confused, feel like crying
I read somewhere something about re-creating partitions on the internal memory but I've no idea how to do that. Is that what I need to do?
Has anyone else cocked their phone up like this?
Any help at all to get this working would be amazing, thanks guys!
so you can't get to recovery? If not find the sticky that has all the stock RUU and push that through adb. maybe that will work. if you can get to recovery try to install the stock rom's .zip.
I think you might be flashing/using the wrong ruu. More than likely the radio that the ruu has isn't compatible with your specific hboot. Try a different ruu with a different radio. But no your phone shouldn't be bricked.
""Shooter on Deck""
Ok I can now get into a recovery image by using "fastboot boot whatever_image.img"
The exact errors I get are
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also tried flashing parts of my nandroid backup via hboot and they all fail with the error "Failed (remote? image update error)"
But there was one very interesting error when trying to flash data.img it said "Failed (remote: partition does not exist!)"
Still no luck with flashing ruu roms
Just tried a few more ruu packages, it reboots into bootloader this time and starts sending files across, looks like it's doing something (I got excited and thought I'd fixed it) then it failed again, it told me to unplug USB so I did and it was at the hboot screen and listed all the different parts of the rom with "Fail-PU" on every line
So again this makes me think the partitions on the internal flash are messed up, is there an image I can use to re-create (or even just check) the partitions properly?
Ok, I've got adb working now through clockworkmod recovery image after doing "fastboot boot recovery.img"
Give me some commands I can type to check and fix the partitions table
Just tried a different recovery image, 4ext recovery http://forum.xda-developers.com/showthread.php?t=1378193 and it prints out the partition table when it boots
partition | fs | size | free
system ext4 800 MiB B
data ext4 1195 MiB B
cache ext4 120MiB B
sdcard fat32 30531MiB 27.0Gb
Does that look ok? What does the B mean under free? Buggered up?
So I'm getting this error when booting into recovery:
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount cache: recovery/command
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36
(file exists)
I can't flash any zips, or restore my nandroid. I think something happened in the process of trying to revert to the stock OTA kernel so I could restore my GB nandroid from ICS.
I'm basically stuck, not sure what to do. Tried reflashing recovery through fastboot. No good.
TeamSPD said:
So I'm getting this error when booting into recovery:
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount cache: recovery/command
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36
(file exists)
I can't flash any zips, or restore my nandroid. I think something happened in the process of trying to revert to the stock OTA kernel so I could restore my GB nandroid from ICS.
I'm basically stuck, not sure what to do. Tried reflashing recovery through fastboot. No good.
Click to expand...
Click to collapse
Did you relock the bootloader before trying this stuff?
No but I think I may have figured it out. Still not sure what happened but the recovery seems to be working now. Trying to flash the stock OTA ROM for now.
Edit: Back in action. So I was finally able to flash the stock rooted OTA and boot up. Must have messed something up when I was flashing a kernel or something.
TeamSPD said:
No but I think I may have figured it out. Still not sure what happened but the recovery seems to be working now. Trying to flash the stock OTA ROM for now.
Edit: Back in action. So I was finally able to flash the stock rooted OTA and boot up. Must have messed something up when I was flashing a kernel or something.
Click to expand...
Click to collapse
I am having this same issue. And, when I try to run the RUU executable, I get an error, wrong bootloader version. How did you resolve this issue? Thanks in advance.
HELP
Could you please share how to fix? I have reflashed boot.img and recovery.img and nothing seems to work. my phone is basically bricked until I figure this out. Thanks
salesrep2189 said:
Could you please share how to fix? I have reflashed boot.img and recovery.img and nothing seems to work. my phone is basically bricked until I figure this out. Thanks
Click to expand...
Click to collapse
what are u trying to fix?
salesrep2189 said:
Could you please share how to fix? I have reflashed boot.img and recovery.img and nothing seems to work. my phone is basically bricked until I figure this out. Thanks
Click to expand...
Click to collapse
What happens if you use the boot image (PH98IMG.zip) from your current rom that you're running and flash it in hboot and then reboot?
disregard
I used this guide and it worked. http://forum.xda-developers.com/showthread.php?t=1486220
thank god.
I'm the same, I can't restore or back up. I'm on the ICS HBoot and clean 4.3 Rom. I have the v1.4 recovery. I can see my sd card on my phone with es explore and I can see my back ups in recovery. But I get the oops every time when I try to use restore or back up.
Sent from my ADR6425LVW using XDA
salesrep2189 said:
Could you please share how to fix? I have reflashed boot.img and recovery.img and nothing seems to work. my phone is basically bricked until I figure this out. Thanks
Click to expand...
Click to collapse
This will sound bruteforceish, but after some time in a similar spot, I did this and had 100% fixage:
- Flash the latest leaked ICS RUU
- After that, download the PH98IMG version of AmonRa
Assuming you're s-off'd, this will completely wipe your phone, but it should fix your boot issue, any lingering SD issues, and had AmonRa recovery up and running w/o issue.
If need be i uploaded the 2.01.605.11 RUU here http://d-h.st/Ju5
I had the same issue when i obtained s-off and ran that ruu then all was well
Instructions:
1. Download
2. Rename file to PH98IMG
3. Check MD5
4. Load onto root of SDCard
5. Boot into HBOOT
6. Wait for it to finish
Remember you must be S-Off if you're trying to downgrade from the Leaked ICS firmware
Having all kinds of issues with AR. cant nandroid back up, says it fails, cant mount the SD card, cant look at error logs, or move them...
However after beating my brains out for hours with this issue i tried CWM touch ( hope it don't have charging error ), and it works just fine.... hmmmmm
looks like AR cant handle whatever s-off did maybe?
IrvChynaman said:
If need be i uploaded the 2.01.605.11 RUU here http://d-h.st/Ju5
I had the same issue when i obtained s-off and ran that ruu then all was well
Instructions:
1. Download
2. Rename file to PH98IMG
3. Check MD5
4. Load onto root of SDCard
5. Boot into HBOOT
6. Wait for it to finish
Remember you must be S-Off if you're trying to downgrade from the Leaked ICS firmware
Click to expand...
Click to collapse
Is this the GB ruu and if so I follow your instructions flash the ruu in hboot and re-down load the recovery right. I have tried every thing that is a fix for the newest firmware with no luck. When I did the s-off thing I used the ICS hboot. Since we have s-off I could down grade back to GB right. I just would like my sd card and recovery back. I just need some help with this, like I said I tried all the ICS sd card fix with no luck. The only thing I have not done yet is the adb busy box command thing yet. I tried to do it, but it's not working for me. I typed adb shall in cmd and only get a list of adb commands. I've also tried adb devices and it wont list my phone, but if I do a fastboot devices my phone is listed. I'm in fastboot when I try the adb devices. I'll keep reading and learning, something has to work. I learned to unlock, install recovery, install a rom and flash the kernel, s-off my phone and just about every other thing likes mod and how to move files in es explorer. I just need to find a way to fix my recovery... But thanks for every ones help and thanks to the dev for making all the great roms and for getting us s-off.
NAU420 said:
Is this the GB ruu and if so I follow your instructions flash the ruu in hboot and re-down load the recovery right. I have tried every thing that is a fix for the newest firmware with no luck. When I did the s-off thing I used the ICS hboot. Since we have s-off I could down grade back to GB right. I just would like my sd card and recovery back. I just need some help with this, like I said I tried all the ICS sd card fix with no luck. The only thing I have not done yet is the adb busy box command thing yet. I tried to do it, but it's not working for me. I typed adb shall in cmd and only get a list of adb commands. I've also tried adb devices and it wont list my phone, but if I do a fastboot devices my phone is listed. I'm in fastboot when I try the adb devices. I'll keep reading and learning, something has to work. I learned to unlock, install recovery, install a rom and flash the kernel, s-off my phone and just about every other thing likes mod and how to move files in es explorer. I just need to find a way to fix my recovery... But thanks for every ones help and thanks to the dev for making all the great roms and for getting us s-off.
Click to expand...
Click to collapse
Yeah this is the gb ruu. Your firmware and hboot will downgrade but you will keep s-off. I'm not sure if flashing the leaked ics ruu will work but I wouldn't be surprised if it would.
Sent from my ADR6425LVW using XDA
Heya, just flashed the [ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13 and was stuck at the 4G screen for about 20 minutes. Went back to bootloader and wiped cache and dalvik. Now stuck at HTC screen. Suggestions?
I can get to recovery or bootloader, but I am not sure what to do from here. I can also get into TWRP, but sideload fails.
S-on or S-off? If you're s-on, need to flash the kernel separately still...
S-on. I went and downloaded a kernel also, but when I flash, it says E: Unable to mount '/cache'
Edit: Any kernel that I try to flash fails, it says E: Error executing updater binary in zip '/sdcard'
In hboot, go to fastboot. On your PC, type "fastboot boot recovery" this should give you temp s-off to flash kernel in recovery. Try reflashing the ROM after giving that command and your phone boots into recovery.
Sent from my Infected Rezound using xda app-developers app
Flashed dbinstaller-JB-v2.3.9 and I am back in business. I will work on other ROMs and getting where I need to be this weekend. I can't thank you enough for putting me on the trail of the kernel.
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?
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