I made the mistake of choosing clockwork recovery for my Rezound only to find out that when the phone dies, YOU CAN'T CHARGE IT.
So now I'm in fast boot (I don't know if the phone is charging or not), but I'm trying to figure out if I can change the phones battery percentage. Right now, I can't flash a different recovery because it fails because my battery is too low. Well I can't charge it if I can't change the recovery and I have no other way to charge the battery.
Can this be done with ADB? Is there some sort of work around?
Thanks
C:\Rezound_All-In-One_Kit_V1.0\Data>fastboot flash recovery recovery-ra-vigor-3.
14-gnm.img
sending 'recovery' (7074 KB)... OKAY [ 1.697s]
writing 'recovery'... FAILED (remote: battery low)
finished. total time: 2.015s
Click to expand...
Click to collapse
Try fastboot reboot or adb reboot. I can't remember which command, but that should get you back to having the phone up and charging.
Sent from my Vizio tablet using xda premium
I have come across several posts the are identical or very similar to my issue. However, I am having an additional issue which seems to be the cause of my not being able to unbrick. I'll try to provide enough details, but let me know if I missed something important.
My prime appears to be completely bricked, because I tried to fix another problem. When I tried to upgrade a stock ICS prime to JellyBean, I had many problems because the recovery kept error out with the droid guy with the red triangle and ! symbol. Somehow, I ended up actually do it and ended up with the US_epad-user-10.4.2.15.zip rom (US_epad-10.4.2.15-20120917). Because I am overseas, I had problems installing some things in the market and was considering root or a custom rom. At some point, I unlocked the device, which still displays clearly every time I boot. While look through several things that appeared very straight-forward, I ultimately ended up with a brick. The device is stuck on the splash screen. I have access to fastboot. However, adb doesn't recognize the device.
When trying to RCK (or wipe data) from the bootloader, I get:
Code:
Booting Recovery kernel image
Booting failed
[COLOR="Red"]Unrecoverable bootloader error (0x00000000).[/COLOR]
This post:
[Q] Transformer Prime possibly bricked. Help?
appeared identical to my current problem. The suggested use of universal drivers has not helped, however.
This post:
[SOLVED] Can access fastboot but can't get past splash screen
also appears identical...
These two also appears to provide hope:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
...but ultimately, continue to evade my tablet.
Why? you may ask...
Well, it seems that I can boot into fastboot. When I manually run any command, it seems to work fine. But the prime becomes unresponsive to all subsequent commands. It requires that I force reboot and re-enter fastboot. When I try to run Urkel's Fresh Start, the wiping all runs smoothly, and the staging command
Code:
fastboot -i 0x0b05 flash staging system.blob
run smoothly. From that point, it becomes unresponsive again. It appears that although the flashing completes without errors, it doesn't take...or perhaps is inaccessible because the bootloader is jacked. Here's the output from Urkel's Fresh Start, for example:
Code:
Press any key to continue . . .
.: Now cleaning the TF201 partitions :.
erasing 'cache'...
OKAY [ 2.160s]
finished. total time: 2.160s
******************************
erasing 'userdata'...
OKAY [ 39.644s]
finished. total time: 39.645s
******************************
erasing 'recovery'...
OKAY [ 1.953s]
finished. total time: 1.954s
******************************
erasing 'staging'...
OKAY [ 0.948s]
finished. total time: 0.948s
******************************
erasing 'system'...
OKAY [ 2.208s]
finished. total time: 2.209s
******************************
.: Partitions now clean, continuing to reboot back into bootloader. Do not miss
selecting FASTBOOT with VOL+D and then VOL+U on the USB Icon. If you miss it no
big deal reboot back into FASTBOOT before continuing :.
Press any key to continue . . .
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
.: Confirm you are in FASTBOOT before continuing to flash a fresh image/blob. Th
is will take 3-5 minutes because of the size of the image :.
Press any key to continue . . .
sending 'staging' (537604 KB)...
OKAY [ 94.723s]
writing 'staging'...
OKAY [ 1.329s]
finished. total time: 96.054s
rebooting...
finished. total time: 0.548s
.: No need to set up the tablet but let the tablet fully boot to welcome screen
then hold down the power to shut if off. When off turn it back on and enter FAST
BOOT. Once at FASTBOOT then continue :.
Press any key to continue . . .
It appears fine...however, it doesn't reboot, even thought the command said it was successful. So, I try manually rebooting and get stuck at the welcome screen again. It's a vicious cycle... Anyhow, this type of situation is the same for all of the other workarounds that I have found to this problem.
It seems that fastboot is semi-responsive, but no actions that I take are recognized upon reboot. I would love to try and figure out why fastboot is having these issues... and unbrick my tablet. So, please let me know if I have missed any threads that have exactly this solution (ie. fastboot works...but not really).
Thanks in advance, and let me know if I missed details that are necessary.
flueterflam said:
I have come across several posts the are identical or very similar to my issue. However, I am having an additional issue which seems to be the cause of my not being able to unbrick. I'll try to provide enough details, but let me know if I missed something important.
My prime appears to be completely bricked, because I tried to fix another problem. When I tried to upgrade a stock ICS prime to JellyBean, I had many problems because the recovery kept error out with the droid guy with the red triangle and ! symbol. Somehow, I ended up actually do it and ended up with the US_epad-user-10.4.2.15.zip rom (US_epad-10.4.2.15-20120917). Because I am overseas, I had problems installing some things in the market and was considering root or a custom rom. At some point, I unlocked the device, which still displays clearly every time I boot. While look through several things that appeared very straight-forward, I ultimately ended up with a brick. The device is stuck on the splash screen. I have access to fastboot. However, adb doesn't recognize the device.
When trying to RCK (or wipe data) from the bootloader, I get:
Code:
Booting Recovery kernel image
Booting failed
[COLOR="Red"]Unrecoverable bootloader error (0x00000000).[/COLOR]
This post:
[Q] Transformer Prime possibly bricked. Help?
appeared identical to my current problem. The suggested use of universal drivers has not helped, however.
This post:
[SOLVED] Can access fastboot but can't get past splash screen
also appears identical...
These two also appears to provide hope:
[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
...but ultimately, continue to evade my tablet.
Why? you may ask...
Well, it seems that I can boot into fastboot. When I manually run any command, it seems to work fine. But the prime becomes unresponsive to all subsequent commands. It requires that I force reboot and re-enter fastboot. When I try to run Urkel's Fresh Start, the wiping all runs smoothly, and the staging command
Code:
fastboot -i 0x0b05 flash staging system.blob
run smoothly. From that point, it becomes unresponsive again. It appears that although the flashing completes without errors, it doesn't take...or perhaps is inaccessible because the bootloader is jacked. Here's the output from Urkel's Fresh Start, for example:
Code:
Press any key to continue . . .
.: Now cleaning the TF201 partitions :.
erasing 'cache'...
OKAY [ 2.160s]
finished. total time: 2.160s
******************************
erasing 'userdata'...
OKAY [ 39.644s]
finished. total time: 39.645s
******************************
erasing 'recovery'...
OKAY [ 1.953s]
finished. total time: 1.954s
******************************
erasing 'staging'...
OKAY [ 0.948s]
finished. total time: 0.948s
******************************
erasing 'system'...
OKAY [ 2.208s]
finished. total time: 2.209s
******************************
.: Partitions now clean, continuing to reboot back into bootloader. Do not miss
selecting FASTBOOT with VOL+D and then VOL+U on the USB Icon. If you miss it no
big deal reboot back into FASTBOOT before continuing :.
Press any key to continue . . .
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
.: Confirm you are in FASTBOOT before continuing to flash a fresh image/blob. Th
is will take 3-5 minutes because of the size of the image :.
Press any key to continue . . .
sending 'staging' (537604 KB)...
OKAY [ 94.723s]
writing 'staging'...
OKAY [ 1.329s]
finished. total time: 96.054s
rebooting...
finished. total time: 0.548s
.: No need to set up the tablet but let the tablet fully boot to welcome screen
then hold down the power to shut if off. When off turn it back on and enter FAST
BOOT. Once at FASTBOOT then continue :.
Press any key to continue . . .
It appears fine...however, it doesn't reboot, even thought the command said it was successful. So, I try manually rebooting and get stuck at the welcome screen again. It's a vicious cycle... Anyhow, this type of situation is the same for all of the other workarounds that I have found to this problem.
It seems that fastboot is semi-responsive, but no actions that I take are recognized upon reboot. I would love to try and figure out why fastboot is having these issues... and unbrick my tablet. So, please let me know if I have missed any threads that have exactly this solution (ie. fastboot works...but not really).
Thanks in advance, and let me know if I missed details that are necessary.
Click to expand...
Click to collapse
If you don't have universal naked drivers downloaded and installed, do that.... also you should install twrp as your recovery, just make sure you get the right one.... I think I read at the top you installed JB so your bootloader is probably JB...... don't install the ics twrp over the jb bootloader or you will have a unrecoverable mess I think.....
Gage_Hero said:
If you don't have universal naked drivers downloaded and installed, do that.... also you should install twrp as your recovery, just make sure you get the right one.... I think I read at the top you installed JB so your bootloader is probably JB...... don't install the ics twrp over the jb bootloader or you will have a unrecoverable mess I think.....
Click to expand...
Click to collapse
Hey thanks for the help. Unfortunately, as I mentioned, I already tried the naked drivers to no avail. Just to be safe, I tried once more, removed/deleted/uninstalled the drivers and even force turned off driver installation for good measure to make sure. I have the same behavior with both the ASUS drivers and the Universal Naked drivers.
I think I forgot to mention explicitly that I tried installing twrp as recovery. I was careful to get the JB bootloader. It hasn't helped. I tried it again today after the re-install of naked drivers. Same behavior as before. Fastboot appears to flash the blob successfully,, but then the prime becomes unresponsive, will not reboot via fastboot, and sticks at flash screen and no RCK.
Any other things that I could have missed or done incorrectly?
Bootloader Error
Hi,
any solution to this yet? I do have the exact same problem!
It seems to me the procedure is locked and it accepts only one comand (maybe the key) then rejects al subsequent comands.
.
From everything I have seen "Unrecoverable bootloader error" means exactly what it says. its unrecoverable. You need a new motherboard
Bootloader Error
Well, that's exactly what Asus wants us to think. My logical thinking tells me there is no defect other than a software failure in connection with Asus locking down bootloaders in order to torture their customers.
I can still access Fastboot, it is just locked down. I guess the first comand (which it always accepts should be a key to unlock the fastboot procedure, without that key nothing is possible. Why can they not recover it at the service center? Maybe they do not want the key to get public.
It's all business after all.
Still, they use open source software for free and then neglect warranty...
I just cannot understand. Well, not Asus for me again I guess...
whycali said:
From everything I have seen "Unrecoverable bootloader error" means exactly what it says. its unrecoverable. You need a new motherboard
Click to expand...
Click to collapse
Same problem, posted http://forum.xda-developers.com/showthread.php?t=2154851
Guys, I'm really in need of the superpowers of XDA community in this one, as I'm gonna lose my mind.
(PD: Not native english speaker here, pls be gentle )
Let's get into it:
I'm experienced in tweaking androids so I was just doing routine stuff in this one by unlocking bootloader, but it got bricked (still dont know why)
It astounds me the incredibly lack of documentation about this device in the entire interweb, given that is not soooo bad device actually, so the current situation is: device bricked, bootloop on huawei mediapad start logo and only access to fastboot mode (Volume down+Power).
1) Approach number 1: got the official firmware and tried to flash it by the official way, according to Huawei web,
httpxxx://consumer.huawei.com/en/tablets/support/manuals/s10-231l-en.htm
copied dload folder with update.app and stuff to the root of an 8GB fat-32'd MicroSD card hoping to get it installed but absolutely nothing happens. Volume UP+Volume Down+Power falls in bootloop again. No recovery no nothing apart fastboot mode.
2) Approach number 2: ADB drivers installed, combo ADB, Fastboot does NOT detect my device properly
Code:
C:\...\fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\...\fastboot>fastboot devices
? fastboot
Strange enough, it allows me to flash almost anything, so i flashed official boot, recovery and system images based on the official firmware:
Code:
C:\...\fastboot>fastboot flash boot boot.img
sending 'boot' (6708 KB)...
OKAY [ 0.260s]
writing 'boot'...
OKAY [ 0.917s]
finished. total time: 1.178s
C:\...\fastboot>fastboot flash recovery recovery.im
g
sending 'recovery' (9660 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 1.332s]
finished. total time: 1.706s
C:\...\fastboot>fastboot flash system system.img
sending 'system' (738258 KB)...
OKAY [ 28.472s]
writing 'system'...
OKAY [ 43.332s]
finished. total time: 71.804
after reboot nothing happens, still in bootloop with no options to enter recovery mode, only fastboot working.
As said before, have browsed almost the entire interned but no luck by this time. Maybe i'm too focused on it.
Any XDA Gurú wants to get involved by giving advice? Will be greatly appreciated.
Anyone
Anyone?
Was hoping to find a solution here as like you I have searched the whole Internet and.... Nothing.
Exactly the same problem.
Would like to try flashing the official boot, but not sure how you did it, because Flash Tools needs a Scatterfile and Boot.img and the official boot is an Update.app
What program did you use?
Cheers,
Joe!
Still no solution for this? Got same problem.
Hi guys,
after flashing original recovery from Rashr, I have a hard bricked Meizu M1 Note. I can only boot into fastboot or VCOM (for SP Tool), no recovery, not normal boot.
Hope you can help me,
Thank you
Same story, even worse! I wanted to downgrade from LP to KK. I followed step by step guide posted in other forum. Everything works, but after 2 or 3 days, phone started to act very strange. Volume keys did not react properly (cant switch in recovery and made an screen shot for example), phone started to loose network coverage . I tried to reset it, but unfortunately no fastboot and recovery modes were present. The only way to switch in recovery was rashr tool. I decided to reflash recovery again and everything went wrong! The result was permanent restart, no recovery and fastboot modes. Maybe this method should be avoided. I know that everything I made is at my own risk, dont blame me.
Need advice to unbrick it. I was thinking to disassemble it and disconnect battery and try to resurrect it with adb?! The bad thing is that it wont turn into fastboot...pfuu.
Have some progress - phone can go into fastboot mode, but when I try to flash stock recovery, it reports error:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (16384 KB)
OKAY [ 0.616s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017 because it is locked
)
finished. total time: 0.665s
Click to expand...
Click to collapse
Will appreciate any help. Thanks!
Any help?
Help
I have the same problem. Could anyone help us?
any help?
I have more or less the same problem but my cellular conects disconects preloader usb driver and don't see nothing in the screen, not logo, not recovery, not fastboot mode, any help?
SOLVED
SOLVED
I've just flashed the current Le Max 2 TWRP package, but when I reboot into recovery mode the right half of the screen crashes, and the left half freezes.
The right half is covered in a multicoloured static, not dissimilar to when a ZIP cable isn't properly plugged in.
I'm unable to do anything at this point besides rebooting the phone.
I've tried flashing it again, to no avail.
Any suggestions? EUi is painful.
Okay, I've just tried it again and noticed that I missed the following in the cmd line.
C:\adb>fastboot flash resovery twrp-3.0.2-1-gemini.img
target reported max download size of 536870912 bytes
sending 'resovery' (57500 KB)...
OKAY [ 1.286s]
writing 'resovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.305s
I can't find anyone who's managed to solve this issue.
EDIT
Okay, saw my spelling mistake, fixed it and the issue persists - though I've noticed it is actually in the LeEco Recovery tool, not the TWRP one.
Okay, I've fixed it by using the most recent TWRP.