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.
Related
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
I was on S-off leaked RUU ICS running fine, I downloaded the latest speed rom and it gave me this error while trying to flash
Formatting partitions
(system is unmounted already)
E: Error in /sdcard/Speed Rom ICS 3.1.0.zip
(Status 1)
Installation aborted.
I downloaded it again and got the same error.
When i tried a third time i was no longer able to get into CWM.
I tried flashing CWM again using the all in one tool which pushed it fine but it still does not load CWM, I tried pushing 4ext and TWRP with the same results. 4ext was able to get to a screen where it said 4ext is loading 3..2..1.. but then back to the white HTC screen
is there a way i can push the RUU leak file via ADB so i can flash that again using the built in recovery?
Thanks,
kewlmonk2121 said:
I was on S-off leaked RUU ICS running fine, I downloaded the latest speed rom and it gave me this error while trying to flash
Formatting partitions
(system is unmounted already)
E: Error in /sdcard/Speed Rom ICS 3.1.0.zip
(Status 1)
Installation aborted.
I downloaded it again and got the same error.
When i tried a third time i was no longer able to get into CWM.
I tried flashing CWM again using the all in one tool which pushed it fine but it still does not load CWM, I tried pushing 4ext and TWRP with the same results. 4ext was able to get to a screen where it said 4ext is loading 3..2..1.. but then back to the white HTC screen
is there a way i can push the RUU leak file via ADB so i can flash that again using the built in recovery?
Thanks,
Click to expand...
Click to collapse
Download the ICS leak again, rename it to PH85IMG.zip, put it on your microSD card, boot into bootloader (vol down + power), let it do its thing
Also, may I recommend the 4ext recovery?
kered424 said:
Download the ICS leak again, rename it to PH85IMG.zip, put it on your microSD card, boot into bootloader (vol down + power), let it do its thing
Also, may I recommend the 4ext recovery?
Click to expand...
Click to collapse
Is there a way i can push it through adb?
i tried >adb push PH85IMG.zip /sdcard
but it gave me "failed to copy 'PH85IMG.zip' to '/sdcard': Is a directory"
I don't have a anything i can put my microSD in except my phone till tomorrow
kewlmonk2121 said:
Is there a way i can push it through adb?
i tried >adb push PH85IMG.zip /sdcard
but it gave me "failed to copy 'PH85IMG.zip' to '/sdcard': Is a directory"
I don't have a anything i can put my microSD in except my phone till tomorrow
Click to expand...
Click to collapse
I have no idea. Sorry.
The command should be...(put the PH85IMG.zip in your tools folder first)
Code:
adb push PH85IMG.zip /sdcard2/PH85IMG.zip
If sdcard2 doesn't work try sdext or sd_ext
Don't quote me on this...
Double0EK said:
The command should be...(put the PH85IMG.zip in your tools folder first)
Code:
adb push PH85IMG.zip /sdcard2/PH85IMG.zip
If sdcard2 doesn't work try sdext or sd_ext
Don't quote me on this...
Click to expand...
Click to collapse
I tried that way too later on. It gave me permission denied. I think because my rom was gone debugging was no longer enabled and write permissions to the SD card were gone. I was able to get back up and running by using a card reader.
Thanks everyone
kewlmonk2121 said:
I was on S-off leaked RUU ICS running fine, I downloaded the latest speed rom and it gave me this error while trying to flash
Formatting partitions
(system is unmounted already)
E: Error in /sdcard/Speed Rom ICS 3.1.0.zip
(Status 1)
Installation aborted.
I downloaded it again and got the same error.
When i tried a third time i was no longer able to get into CWM.
I tried flashing CWM again using the all in one tool which pushed it fine but it still does not load CWM, I tried pushing 4ext and TWRP with the same results. 4ext was able to get to a screen where it said 4ext is loading 3..2..1.. but then back to the white HTC screen
is there a way i can push the RUU leak file via ADB so i can flash that again using the built in recovery?
Thanks,
Click to expand...
Click to collapse
I wish I read this earlier...exact same thing happened to me! I'm s-on however , but just unlocked my boot loader to flash this rom.
Now I have to re-lock bootloader and load the stock rom again...so much work for literally no benefit. Disappointed!
amad99 said:
I wish I read this earlier...exact same thing happened to me! I'm s-on however , but just unlocked my boot loader to flash this rom.
Now I have to re-lock bootloader and load the stock rom again...so much work for literally no benefit. Disappointed!
Click to expand...
Click to collapse
Nobody made you flash it you know...just saying
Sent from my HTC_Amaze_4G using XDA
Spastic909 said:
Nobody made you flash it you know...just saying
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Thanks for stating the obvious
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Mcsquizzy said:
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Click to expand...
Click to collapse
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
try this: boot into recovery and plug the device into the computer then try adb devices and see if the device ID pops up if in fact it does do a:
adb push romzip.zip /sdcard/romzip.zip
or
adb push \path\to\romzip.zip /sdcard/romzip.zip
and it will push it to the /sdcard directory, then reboot the recovery and flash the rom and it should just work
.torrented said:
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
Click to expand...
Click to collapse
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Mcsquizzy said:
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Click to expand...
Click to collapse
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Mcsquizzy said:
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Click to expand...
Click to collapse
I flashed Viper 1.3.0 with BeastMode 5.9 and it's running fine no bootloops of any sort
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.
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?