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
Related
Bricked my HTC Rezound trying to root it today. Need help installing stock RUU, but how do i do this. Push it to my phone with ADB while in fastboot? And if thats how, how is this accomplished? I can only access the bootloader/fastboot.
What exactly were you doing when this happened?
I was in aman ra recovery and i thought i was rooted. I also thought i had done a nandroid backup earlier, but apparently not. I flashed cleanrom, and when i rebooted, it got stuck on the white htc screen
If you are unlocked then just flash the kernel in fastboot.
If you are trying to install cleanrom 4.0 you need to run the leaked ruu first.
Sent from my ADR6425LVW using xda premium
Its literally too late for any of that. I can only access the bootloader or fastboot. There is no recovery installed now because it was only the temp one. If i had a way to get the stock ruu on the storage so it installs in the bootloader, then i may be able to fix my rezound, correct?
do you understand what brick means???
you are simply having user error.
Please re-name this thread!
andybones said:
do you understand what brick means???
you are simply having user error.
Please re-name this thread!
Click to expand...
Click to collapse
I apologize, but last time i checked a phone that doesnt boot is a bricked phone, whether it was user error or a problem with the device that caused it?
mdunn1066 said:
I apologize, but last time i checked a phone that doesnt boot is a bricked phone, whether it was user error or a problem with the device that caused it?
Click to expand...
Click to collapse
When your phone is bricked it literally means its a brick that won't bee good for anything than a paper weight
Your case, all you need to do is flash a new kernel
Sent from my ADR6425LVW using Tapatalk
superchilpil said:
When your phone is bricked it literally means its a brick that won't bee good for anything than a paper weight
Your case, all you need to do is flash a new kernel
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Thank you for clarifying. Can you help me do this?
Also. Wouldn't it be possible to just fastboot oem lock, then put the RUU on an sd card using an sd card reader, and enter hboot and install that way?
Why do that? If you can fastboot oem lock, why not put the boot image that is in the PH98IMG.zip file, in the same directory as fastboot then type fastboot flash boot boot.img. Now you have your kernel installed.
EmerikL said:
Why do that? If you can fastboot oem lock, why not put the boot image that is in the PH98IMG.zip file, in the same directory as fastboot then type fastboot flash boot boot.img. Now you have your kernel installed.
Click to expand...
Click to collapse
Because I am inexperienced with ADB still and did not know i could, or how, to do that.
So far it looks to be working as its booting up, thanks a million. I feel sheepishly inexperienced but i guess we all start and learn somehow, right?
Yes we all start somewhere. It isn't the end of the world, live and learn.
Am having the same issue here
jmalone1187 said:
Am having the same issue here
Click to expand...
Click to collapse
I was able to fix mine by going to fastboot on the phone, going into the actual zip file that was the rom i flashed on my pc, and extracting the file named boot.img into my adb folder and then in the command window with the phone connected to the pc and in fastboot mode typing fastboot flash boot boot.img
Can you explain this process in a bit more detail?
I'm kind of new to HTC and not familiar with all the terms yet. Same thing happened to me trying to get the ICS leak on my phone.
I'm not familiar with ADB, and have minimal familiarity with ADB.
Am also having the same issue here
---------- Post added at 05:05 AM ---------- Previous post was at 04:38 AM ----------
my steps:
1 anlock from htcdev.com
2 re-lock bootloader
3 flash leaked RUU 3.11.605.22
4 unlock again
5 flash Amon Ra recovery
6 flash Scott's CleanROM ICS Edition Version 4.0
- enjoyed the week
- wanted to flash another rom
I put on the SD card RezROM_ICS_v3.1.zip and began to flash, forgetting the first re-lock, flash leaked RUU 3.11.605.22, unlock and then flash RezROM. (isn't it?)
Phone rebooted and there was a white HTC screen and nothing more.
Then I tried to fix it and flash leaked RUU 3.11.605.22 again (re-lock, put on the SD card PH98IMG.zip, flash, but after reboot I got the same white HTC screen and nothing)
pls someone could instruct me on the right path?
which means in Amon Ra 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)
and so after each attempt to flash any ROM
I can not understand what I do? pls help
Try pulling the battery & SD card, power up without SD. Do a factory reset. Are you currently in an unlocked state with a fresh .22 RUU installed?
Snuzzo said:
Try pulling the battery & SD card, power up without SD. Do a factory reset. Are you currently in an unlocked state with a fresh .22 RUU installed?
Click to expand...
Click to collapse
now I can not really answer, because that I have tried many options to fix this.
I tried it, power up without sd card and battery - factory reset. but in recovery still:
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)
in fastboot following info:
TAMPERED
RELOCKED
Security Warning
VIGOR PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.10.0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0101
eMMC-boot
Mar 11 2012
I also tried to flash original RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00 .1123r_3161E_9K_QMR_release_233635_signed.exe, but when I click the button to proceed and I get an error message stating it failed due to an invalid signature.
You can't RUU backwards and you need to re-unlock before attempting to flash another rom.
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 folks,
I seemed to have really bollixed up my HTC Flyer (BS_US001, HTC__055, U.S. Best Buy WiFi only) in the process of trying to get a custom ROM, any customer ROM, on it.
This device was OTA updated to the official HTC HC release and did work apart from some of the flakiness people have reported with random apps launching (didn't believe it when my daughter told me so but then found confirmation here).
I unlocked the boot loader via the HTC web site. I'm at HBOOT 1.11.0011.
In the process of trying various things I seem to really have clobbered something.
I am now at the point that I cannot flash via fastboot.
For example, I tried to reflash the recovery partition with the stock image from RUU_Flyer_BrightstarUS_WWE_2_27_1540_31_R_Radio_20_3504_30_089BU_3809_07_04_06_M_release_204116_signed.
Here's what I see:
C:\Users\John\Desktop\rom>fastboot flash recovery recovery_signed.img
sending 'recovery' (4156 KB)...
OKAY [ 0.686s]
writing 'recovery'...
I never get past this regardless of whether I'm trying to flash a single image or the entire rom.zip. I cancel with Ctrl-C but HBOOT is locked up at this point and I need to cycle power.
I can boot into CWM via fastboot boot recovery.img. I cannot do the same with the recovery_signed.img from the stock RRU nor with the boot_signed.img. When I try these, I get:
FAILED (remote: reproduce boot image with on-flash ramdisk error)
Even though I can boot into CWM, I cannot apply an update.zip, and I consistently see these messages:
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
When I look at the CWM log, I have the following additional error:
W:failed to mount /dev/block/mmcblk0p30
and occasionally:
W:failed to mount /dev/block/mmcblk0p29
BTW, this device does obviously not boot into HC anymore. I get the white HTC start-up screen, the the screen goes black, sits there for a while, then buzzes, and loops through this again.
Any ideas?
I actually work at a chip company that does Android work and am quite familiar with much of this terminology, just not HTC's specific implementation. I'm getting the impression that I hosed up the image in a particular partition or possibly even the GPTs in the eMMC itself.
I noticed that HBOOT says "eMMC boot" when it starts up? Is there any way to boot from microSD? I know our devices can do so, but, of course, we have to pass the necessary parameters to U-Boot to do as much, and I figure the same would be required with HBOOT.
Is there anyway to get serial console access on this device without actually taking it all apart?
At this point, I'm tempted to just snag another beater tablet from the office (we buy most of them at some point for competitive benchmarking) and let my daughter use that one until she enters middle school, at which point my wife and I will allow her to have a phone. I just wanted to exhaust every last possibility on this device before consigning it to our next E-Waste pickup.
Thanks for any help or insight.
I don't understand why you are trying to flash stock recovery, or update.zip.
Did you try to just flash the zip for a custom ROM in CWM, then flash boot.img for that ROM using fastboot?
redpoint73 said:
I don't understand why you are trying to flash stock recovery, or update.zip.
Did you try to just flash the zip for a custom ROM in CWM, then flash boot.img for that ROM using fastboot?
Click to expand...
Click to collapse
Well, that's the kicker. I couldn't flash any custom ROM, so I figured I at least ought to try to get back to the stock ROM.
For example, if I try ARUwizard.exe, I downloads and tells me it's working then comes back that it could not flash anything.
I see the same errors if I try to flash an entire ROM image with "fastboot flash zip filename.zip".
This is why I attempted to flash individual img files manually.
BTW, I talked with one of my co-workers and have a plan of action. Since I can download and run a recovery image, it means I can run a Linux kernel. His suggestion was to boot a kernel that has the USB Ethernet gadget driver compiled in and runs telnetd/inetd. Then, I could get to the shell prompt on the device, check out the individual partitions to see what's going on, and, update these partitions manually with their respective img files.
So, anyone have a kernel compiled to do this with a root file system either on SD card or via initramfs? I can definitely build one, but it'll be an afternoon project to pull it all together. Maybe not too much of an afternoon since I've more or less just done the same thing for one of the SoCs I work on that does not have much in the way of expandability, e.g. no microSD slot so it's Bluetooth all the way for anything.
Thanks again.
Is your bootloader still unlocked?
You have to relock the bootloader to run the RUU. It might be as simple as that (just relock and run RUU).
But don't know why you can't flash a custom ROM. What happens when you try? The flash fails, or is it successful, but fails to boot?
redpoint73 said:
Is your bootloader still unlocked?
You have to relock the bootloader to run the RUU. It might be as simple as that (just relock and run RUU).
But don't know why you can't flash a custom ROM. What happens when you try? The flash fails, or is it successful, but fails to boot?
Click to expand...
Click to collapse
Yeah, my bootloader is still unlocked. I can try RUU again after relocking. I'll have to get you the specific messages it outputs when it fails, but it is consistent, and I think I got them the one time I tried with the bootloader locked.
fails to boot
Hi redpoint, my flyer flashes ok but still fails to boot, or enter recovery, where am i going wrong?
redpoint73 said:
Is your bootloader still unlocked?
You have to relock the bootloader to run the RUU. It might be as simple as that (just relock and run RUU).
But don't know why you can't flash a custom ROM. What happens when you try? The flash fails, or is it successful, but fails to boot?
Click to expand...
Click to collapse
After I installed EnergyRom I have been having issues with TWRP (not blaming EnergyRom). I was trying to make a backup and I kept getting an error stating my SDcard did not have enough space (tried both internal and external, both had plenty of space). I tried another SD card, even reformatted it, but to no avail.
I then upgraded TWRP 2.2 to 2.4 and then TWRP got really funky. It no longer recognizes or lists any files, keep getting unable to mount errors, and will not let me reboot, giving an error message 'No OS found'. But when I manually reboot everything seems to work just fine.
Just updated to 2.5 and same exact issue(s). It also wont let me save the log file, so I am writing here:
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/staging'
E: Unable to find partition size for '/data'
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E: Unable to set emmc bootloader message.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
Any help would be greatly appreciated.
SS823 said:
After I installed EnergyRom I have been having issues with TWRP (not blaming EnergyRom). I was trying to make a backup and I kept getting an error stating my SDcard did not have enough space (tried both internal and external, both had plenty of space). I tried another SD card, even reformatted it, but to no avail.
I then upgraded TWRP 2.2 to 2.4 and then TWRP got really funky. It no longer recognizes or lists any files, keep getting unable to mount errors, and will not let me reboot, giving an error message 'No OS found'. But when I manually reboot everything seems to work just fine.
Just updated to 2.5 and same exact issue(s). It also wont let me save the log file, so I am writing here:
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/staging'
E: Unable to find partition size for '/data'
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E: Unable to set emmc bootloader message.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Please tell me you didn't flash a normal twrp on the new 4.2.1 bootloader.
It would appear that you're recovery isn't compatible with your bootloader, or device all together. It also may be worth asking how you arrived at your new rom -
1. Initial steps, flashing recovery, etc
2. Clearing caches, factory resets, wiping x3, etc
3. Flash new rom, reboot let settle.
If you've just moved to the custom rom, and the recovery was working fine prior to the new rom, list what you were coming from and going to, maybe I can help. I'm not intimately familiar with the Eee Pad but hopefully we can figure this out.
milestoneiii said:
It would appear that you're recovery isn't compatible with your bootloader, or device all together. It also may be worth asking how you arrived at your new rom -
1. Initial steps, flashing recovery, etc
2. Clearing caches, factory resets, wiping x3, etc
3. Flash new rom, reboot let settle.
If you've just moved to the custom rom, and the recovery was working fine prior to the new rom, list what you were coming from and going to, maybe I can help. I'm not intimately familiar with the Eee Pad but hopefully we can figure this out.
Click to expand...
Click to collapse
You don't need to figure it out mate.. I know exactly what he has done.
My post above wasn't really a question. That is what he has done.
JB TWRP
flumpster said:
You don't need to figure it out mate.. I know exactly what he has done.
My post above wasn't really a question. That is what he has done.
Click to expand...
Click to collapse
I upgraded the bootloader to 4.2 when I updated to Energy ROM. It was working just fine (the ROM is still working just fine), I was able to make a back-up. A few days later I wanted to flash another ROM, went to make a backup and then (see initial post). All the TWRP updates I did (2.4 and 2.5) are the JB blobs. When you say 'normal' bootloader what exactly do you mean, ICS?
SS823 said:
I upgraded the bootloader to 4.2 when I updated to Energy ROM. It was working just fine (the ROM is still working just fine), I was able to make a back-up. A few days later I wanted to flash another ROM, went to make a backup and then (see initial post). All the TWRP updates I did (2.4 and 2.5) are the JB blobs. When you say 'normal' bootloader what exactly do you mean, ICS?
Click to expand...
Click to collapse
When you had the first problem that would have been some silly problem. What came next is the problem.
Energy and Hairybeans new versions are using the 4.2.1 bootloader. The versions of TWRP for ICS and Jellybean are not compatible with the 4.2.1 bootloader and gives the error you describe where nothing can mount.
There are loads of people over on the TF300 forums who have done the same and bricked.
In the 4.2.1 upgrade zips that NRG and myself provide there is a custom version of TWRP included that will work on the new 4.2.1 bootloader.
On my thread (Hairybean) I have warnings all over the first post telling people not to install a "normal" version of TWRP onto the 4.2.1 bootloader and to use the downgrade zip if they want to go back to 4.1.1 bootloader and normal TWRP.
Have a read of my last few posts on here and see if any of the ways will fix you. http://forum.xda-developers.com/showthread.php?p=40141480#post40141480
I will probably have to supply you with the Modded TWRP for 4.2.1 in blob file format also. If you need it let me know.
Thanks Flumpster. I was careful to use the Energy update but obviously lacked some common sense when updating the TWRP. If you wouldn't mind passing the modded TWRP blob I'd appreciate it. Can I extract it from your hairybean update zip?
SS823 said:
Thanks Flumpster. I was careful to use the Energy update but obviously lacked some common sense when updating the TWRP. If you wouldn't mind passing the modded TWRP blob I'd appreciate it. Can I extract it from your hairybean update zip?
Click to expand...
Click to collapse
No because that blob file contains the bootloader, recovery and partition table all in one.
I will be at my computer in 20 mins and will upload it here.
---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ----------
Here is the blob recovery file for 4.2.1 bootloader.
http://flumpster.lolcakes.com/android/twrp.blob
Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread.
fastboot -i 0x0b05 flash recovery twrp.blob
If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android.
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Flumpster, thanks TWRP works fine and am backing up now. I still have the same issue of it saying I do not have enough room on my external, though I have over a gig of extra room, I am just going to save to the internal and then transfer it.
Any idea why it reads only part of my external?
Anyway, thanks again!
Wow Flumpster, I'm impressed with your helpfulness and willingness to lend your development skills! It's hard to find people willing to simply explain where someone goes wrong and provide them with the tools to correct it so efficiently. Hats off to you sir!
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2
milestoneiii said:
Wow Flumpster, I'm impressed with your helpfulness and willingness to lend your development skills! It's hard to find people willing to simply explain where someone goes wrong and provide them with the tools to correct it so efficiently. Hats off to you sir!
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, Flumpster, big thank you!
Cheers
SS823 said:
Yeah, Flumpster, big thank you!
Cheers
Click to expand...
Click to collapse
You're welcome mate.. Glad it's all sorted.
flumpster said:
No because that blob file contains the bootloader, recovery and partition table all in one.
I will be at my computer in 20 mins and will upload it here.
---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ----------
Here is the blob recovery file for 4.2.1 bootloader.
http://flumpster.lolcakes.com/android/twrp.blob
Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread.
fastboot -i 0x0b05 flash recovery twrp.blob
If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android.
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Click to expand...
Click to collapse
The 2nd solution works for me.... You are the man flumpster... !! :good::good:
Thank you
flumpster said:
No because that blob file contains the bootloader, recovery and partition table all in one.
I will be at my computer in 20 mins and will upload it here.
---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ----------
Here is the blob recovery file for 4.2.1 bootloader.
http://flumpster.lolcakes.com/android/twrp.blob
Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread.
fastboot -i 0x0b05 flash recovery twrp.blob
If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android.
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Click to expand...
Click to collapse
Thanks for this flumpster it saved my aaaaaaasssss! The 2nd method worked for me.
alfalvarez81 said:
Thanks for this flumpster it saved my aaaaaaasssss! The 2nd method worked for me.
Click to expand...
Click to collapse
Flumpster - YOU ARE THE MAN! Your first solution worked like a charm for me. I have been stumped as to how to fix this problem and now I am able to create a backup, root, and flash CM 10.1!
Cheers!
same issue, cant work around it
I did the same thing, installing a newer generic twrp and get the same password prompt. I have one more wrinkle though that fastboot isnt working normally. I get twrp 2.6 on every boot. I cant do anything with the partitions, it cant enumerate the partition size or it cant mount them. I can push things to tmp and it sees them, but it wont flash them successfully.
When i force it into fastboot, if i try to flash something, the command line appears like everything is ok, but the prime has hung at some point. Thats what happened when i tried method 1.
If i force it into fastboot and then load android, the system boots. I then tried the second method i get no errors and it looks like it all succeeded. After it tries to reboot, it dumps back into twrp.
I was thinking of trying rom manager to flash the recovery back, but havent used it before and i dont know if i can pick the recovery you've given out here.
anyone have a tip to help?
thanks
same issue, some progress (sorta)
I erased my recovery partition through fastboot and tried to flash the trwp.blob here to it. My prime hung. On reboot though it booted into android just fine, my fastboot was fine as well. I can get into fastboot through the normal process, but i have no recovery. when i try to load recovery i get a unrecoverable boot error.
So next is i am going to try to verify i have or have no recovery partition and then recreate it and try to flash twrp back into it.
help
I am having same problem with prime. Every time I reboot it goes to twrp. 2.6 asking for password, and does not recognize any internal memory or sd card. how ever I can use adb reboot-bootloader, and do a cold boot to Linux and everything works just fine..I would like clarification on your instructions on how to repair. I'm just a novice. Any help will be greatly appreciated.
carlkelly176 said:
I am having same problem with prime. Every time I reboot it goes to twrp. 2.6 asking for password, and does not recognize any internal memory or sd card. how ever I can use adb reboot-bootloader, and do a cold boot to Linux and everything works just fine..I would like clarification on your instructions on how to repair. I'm just a novice. Any help will be greatly appreciated.
Click to expand...
Click to collapse
I dont know that i've actually fixed anything or just traded one problem for another. I cannot get a recovery flashed onto my device. My system boots normally and fastboot works, but nothing ive come up with will flash a recovery.
On a brighter note, my system is faster, it hasnt bogged down and lagged like it always has. That may be just because of the wiping caches and such though.
What i did was erase my recovery partition from fastboot.I've recreated it, i can see it in root explorer. Its about 420mb in size, i dont know if that size is correct. The only things in it are a couple of log files.
my whole point in messing with this again was to try to flash the newest CM on it. bluetooth is a bit wonky on mine and i hoped a newer stack would help.
good luck. If i get a working recovery, i will post.
I've got the same issue here, except i have a TF300T. I've downloaded the right blob now (4.2 for the TF300)
the adb devices command shows my TF300T.
Im just wondering now, how do I transfer the file to the 'internal sd card' of the tablet and access it if all i can do is entering the twrp recovery?
thanks in advance.
EDIT: Found a way to delete the wrong recovery and now im able to access the fastboot mode ok. However, the tablet freezes everytime I use the flash command on fastboot...
flumpster said:
No because that blob file contains the bootloader, recovery and partition table all in one.
I will be at my computer in 20 mins and will upload it here.
---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ----------
Here is the blob recovery file for 4.2.1 bootloader.
http://flumpster.lolcakes.com/android/twrp.blob
Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread.
fastboot -i 0x0b05 flash recovery twrp.blob
If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android.
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Click to expand...
Click to collapse
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