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
Related
After I rooted my phone with LGPwn, I was attempting to set partitions on my sd card so that I would be able to use Link2SD. However, after I partitioned my phone, link2sd did not recognize my second partition, saying that it wasn't mounted, so I decided to reboot. After my phone shut off, It never turned back on. I have tried home, vol down, power, taken out battery, etc. When it is plugged into my pc, the computer seems to recognize it for a few seconds, and then disconnects. How do I fix this?
Have the same problem. Please HELP !
1pan1 said:
After I rooted my phone with LGPwn, I was attempting to set partitions on my sd card so that I would be able to use Link2SD. However, after I partitioned my phone, link2sd did not recognize my second partition, saying that it wasn't mounted, so I decided to reboot. After my phone shut off, It never turned back on. I have tried home, vol down, power, taken out battery, etc. When it is plugged into my pc, the computer seems to recognize it for a few seconds, and then disconnects. How do I fix this?
Click to expand...
Click to collapse
I have the exact same problem. Was using an app to create an ext2 partittion on my SD card, to use Link2sd. Ended up formating my phone. Now it wont do anything, it does not turn on in any way. My computer recognizes the phone when I connect it ( had to install some drivers). Im able to boot into fastboot mode. Now my question is how do i fix my partions. I have tried the following comands and this is what I get.
C:\fastboot\yours>fastboot erase system
erasing 'system'...
OKAY [ 0.173s]
finished. total time: 0.176s
C:\fastboot\yours>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.007s
C:\fastboot\yours>fastboot erase boot
erasing 'boot'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.011s
C:\fastboot\yours>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.289s]
finished. total time: 0.292s
C:\fastboot\yours>fastboot erase splash
erasing 'splash'...
FAILED (remote: : partition doesn't exist)
finished. total time: 0.007s
C:\fastboot\yours>fastboot erase cache
erasing 'cache'...
OKAY [ 0.127s]
finished. total time: 0.130s
I guess my question is, what are the command to reformat and fix my partition . Please Help, This is my first brick.
Simply try to restore it through LG official tool :
http://forum.xda-developers.com/showpost.php?p=40423549&postcount=2
OperationNT said:
Simply try to restore it through LG official tool :
http://forum.xda-developers.com/showpost.php?p=40423549&postcount=2
Click to expand...
Click to collapse
I would.... but the thing is that to use the LG Software you need to put the phone in " S/W mode" and like I said before the phone does not turn on in any way (not even in S/W mode) because i formated the partitions. All I'm able to do is put on the phone in fastboot mode (the screen with the inverted LG logo, that says fastboot v5.0 on the top).
Thank for the suggestion though.
Are you sure ?
For example, if you remove the battery, then plug your phone in your computer USB without battery and finally maintain the Vol+ button while it's plugged, the device doesn't turn on in "S/W Upgrade" ?
I always thought "S/W Upgrade" mode was a very low level feature but maybe I am wrong.
OperationNT said:
Are you sure ?
For example, if you remove the battery, then plug your phone in your computer USB without battery and finally maintain the Vol+ button while it's plugged, the device doesn't turn on in "S/W Upgrade" ?
I always thought "S/W Upgrade" mode was a very low level feature but maybe I am wrong.
Click to expand...
Click to collapse
Nope, already tried it. I think I formatted the partition that had the img file for S/W Update .......
The only solution I have found is to boot into fastboot mode... All I need is the command or way to reformat or fix the partitions using fastboot.
Bump .. Found I guy who had the same problem and created a guide on how to fix it, here is a link http://forum.cyanogenmod.com/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/.... Now if we can just find a way to apply the same method to our LG L9, then maybe we could fix the phone.
I hope you can find a solution to your issue. But, while I was reading the solution for E730, I see one issue : when you extract KDZ files from P760 firmware, you only get ".bin" and ".fls" files.
I don't know how those files can be extracted again to get the real final files. I saw this issue with V20I_00.kdz, maybe you could try an older version such as V10A_00.kdz.
Good luck !
EDIT : Did you try this solution ?
http://forum.xda-developers.com/showthread.php?t=2612356
Try flashing ics x and u in fastboot. See if you're able to get a boot to s/w upgrade mode.
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?
Hi,
I got my Oneplus X three days back and when booted, the first thing it showed was to update the phone. When I clicked on download, it did download and asked me to install. When I clicked install, it restarted the phone and stayed at "1+" logo for ever without updating or restarting the phone. When I force restarted it (10 seconds power hold), it started, but the update was not applied. I did not have any other option, but to return the phone for a replacement.
Yesterday I received the replacement and to my surprise, it still does not update and stays on the same "1+" icon. To set things right, I thought of installing TWRP and reflash the bootloader, or better install any custom ROM's. While installing TWRP, I unlocked the bootloader and the result was:
Code:
J:\Mobile\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.011s]
finished. total time: 0.012s
Once unlocked, it goes back into its own weird "1+" icon and stays there (exiting from fastboot mode). Then when I try to boot into twrp, it says:
Code:
J:\Mobile\Minimal ADB and Fastboot>fastboot boot twrp-2.8.7.0-onyx.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.498s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.498s
Should I now send this device back assuming that this is also a buggy phone, or is there solution to this? Kindly help.
I too have the same device but never came across this prob. Better you replace asap!
Just flash TWRP Recovery and install full 2.1.3 ROM. Do not try to boot it.
bioan said:
Just flash TWRP Recovery and install full 2.1.3 ROM. Do not try to boot it.
Click to expand...
Click to collapse
Thanks for the response guys. Problem solved!
For those of you who are in any case facing this problem, the issue was with SD Card. I removed the SD card (which was formatted using my previous Galaxy S3) and tried updating it and it worked. Now, I formatted the SD card and tried again and I was able to get into bootloader mode.
Hello! I have been trying to flash a LineageOS rom to my tablet (model SGP311).
I'm using a Mac to do this but I also have access to Windows and Linux.
Had been stuck on this step for unknown reasons.
Code:
sudo ./fastboot flash recovery ../twrp-3.0.2-0-pollux.img
target didn't report max-download-size
sending 'recovery' (10694 KB)...
OKAY [ 0.381s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
Eventually, I found someone using this command to get past the problem. Seemed to work! Except now my tablet doesn't boot at all. So, I guess something was corrupted?
Code:
sudo ./fastboot flash boot ../twrp-3.0.2-0-pollux.img
target didn't report max-download-size
sending 'boot' (10694 KB)...
OKAY [ 0.379s]
writing 'boot'...
OKAY [ 0.516s]
finished. total time: 0.895s
So now the only reaction I can get out of the tablet is by holding vol. up + power. It'll flash white once and then again thrice. Vol. down + power will also produce one flash.
According to what I've found that means something still works... presumably flashing capability?
So, any advice on how I can get this working again? (Preferably with LineageOS on it, haha. But just so long as it works!)
Huh... the tablet is plugged in and I just noticed that the charging light is on...
unplugs the cable
...It's still on...
Ehh???
messes with it a while
...Fixed it!
(Somehow.)
Okay, I don't know why it worked this time but I'm using Sony Mobile Flasher by Androxyde. Connecting via bootmode flashed the LED. (That was new... it wouldn't flash before! Flashed green, I think?)
So then, since it was apparently being detected, I tried flashing the LineageOS ROM. It completed (good sign) and I rebooted the tablet. The screen came on! And now it's going through a boot process... actually, I think it's looping. Well, I'll have to fix that next, then. At least I know this isn't bricked! (Not sure how to turn it off, though...)
Edit: I think, maybe, I didn't know what I was talking about, haha. Sounds like I was entering flashmode. It truly wasn't reacting at all before, though. Must've been on but unresponsive when I thought it was off. And when I noticed it charging, it was because it'd somehow gotten turned back off for real.
Anyway, I'm good now as far as this problem goes. As for installing TWRP, I've gotten some help from elsewhere.