Heya,
I had KA Sspeed ROM running on my device with XSX kernel. I wanted to try the Sspeed kernel so i've flashed it through recovery. The kernel caused bootloops so I've decided to go back to my old kernel, XSX. I've flashed it through recovery and it was stuck (for few miniutes) on "wiping boot partition". Looking back it was very stupid, but I've force reset the device (power+volume up).
Since then the device won't power up. When I push power and volume up it vibrates and nothing happens. I tried to go in fastboot mode and simply re-flash the xsx kernel with no luck. When I connect the USB and the blue led is appearing the computer says it can't recognize the device and after few seconds the blue led is gone. Furthermore, I've tried to try and put the command in cmd fast enough and it says that it is "waiting for the device"..
Do you have any ideas? I'm hopeless.
Thanks in advance
EDIT: I've also tried to re-install fastboot drivers with no luck.
Have you tried re-flashing the stock firmware via flashmode?
rhogz said:
Have you tried re-flashing the stock firmware via flashmode?
Click to expand...
Click to collapse
I will.
Although somehow I've managed to quickly trigger the flash command in cmd and this was written:
Code:
C:\Users\Yaniv\Desktop\Itamar\fastboot\fastboot>fastboot flash boot xsxkernel.elf
< waiting for device >
sending 'boot' (14251 KB)...
(bootloader) USB download speed was 14492kB/s
OKAY [ 1.022s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00002000-0x0000bfff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
FAILED (status read failed (Too many links))
finished. total time: 2.657s
:/
EDIT: Okay although the error it is okay again thanks. can close the thread
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
Okay, so after nearly a whole day of not getting any work done trying to revive my effed-up RAZR, reading through the forums and beyond, I think it's just time to buckle down and ask for some help.
So I'm trying to revert to stock ICS on my RAZR after going through a bunch of custom ROMs. Downloaded a bunch of Fastboot files and tried both the Eternity Project batch file and flashing through RSD Lite (I'm on 6.14), and no go. Results are as follows:
1. Eternity Project flashes successfully(?) albeit with several error prompts, specifically:
a. writing 'boot'... INFOPreflash validation failure
b. writing 'cdrom'... INFOPreflash validation failure
c. writing 'recovery'... INFOPreflash validation failure
d. writing 'devtree'... INFOPreflash validation failure
End result for this is that it boots into the green Android with its chest open and a red exclamation mark and then into the Motorola Dual Core logo for a couple of seconds then goes to a blank screen. From there, it's unresponsive, but no "Failure" prompts reflected on AB Fastboot Flash Mode.
2. RSD Lite fails much earlier on. It stops at flashing cdt.bin, phone returns FAILED and then stops. Afterwards, phone only boots into Fastboot mode and shoes a "Flash Failure" prmopt next to AB Fastboot Flash Mode. I read that cdt.bin is usually linked to flashing a wrong region image onto my phone. Thing is, this phone was given to me by my aunt, and she only gave me the phone itself. No box, no nothing, and she doesn't remember where she bought it from, as it in turn was given to her by a former boyfriend who she no longer has contact with. Do I have any alternatives aside from downloading every single file on the SBF repository and trying them all one-by-one?
Any help?
Other info is that I used to be on stock Motorola ICS on System_1 partition with AOKP Unofficial Jelly Bean on System_2 partition. Bootloader is 0A.6C, RAZR XT910 GSM.
Hi @all!
I just 'tried' to root my ASUS Memopad FHD 10 16GB (WW-version).
I post here because I simply think that you guys at XDA are certainly the ones who know the solution, if there is one.
It seems as if the userdata+cache partitions are "destroyed" or something like that.
Having Android 4.3 it was not possible to flash the rooted system-image, so I first wanted to "downgrade fastboot" to the version from the "WW_ME302C-V4.7.3-0-ota-user.zip" firmware and then try again flashing the 4-7-3 firmware. But after flashing fastboot, when I tried wiping all data I got this:
-----------------------
fastboot erase system
fastboot erase cache
fastboot flash fastboot fastboot.img
fastboot -w
erasing 'userdata'...
OKAY [ 15.292s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 1.634s]
erasing 'cache'...
OKAY [ 3.607s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 1.186s]
finished. total time: 21.729s
-----------------------
Since then I cannot format the partitions or userdata. Flashing the firmware 'supposedly' works (console output on PC says 'finished').
But after "fastboot flash update WW_ME302C-V4.7.3-0-ota-user.zip" is done the device restarts immediately, then
1. shows the android figure with opened hatch and a green progress bar
2. figure changes to one having a red triangle inside
3. reboot and then showing the ASUS bootscreen for like 10min.
4. The last step repeats like 4 times, then the android figure with red triangle appears again, then bootscreens again ... (endless loop)
So as you can see I cannot boot into android again. I think the problem lies with the "File system type not supported" but.
When I try to format directly I get:
-----------------------
fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 2.303s
-----------------------
Does anyone know how I can fix this and reinstall any firmware?
My ideas were
- format the partitions to ext2/ext3 directly (there should be a way to specify the filesystem, right?)
- flash the userdata/cache partition with someone else's partition content
- use a custom-recovery for the tablet which does this - though I cannot find one anywhere
Thanks XDA! =)
-------------------------------------------------------------------------------------------
SOLVED
-------------------------------------------------------------------------------------------
Thanks to perpe and wakatu the problem has been solved by flashing the original recovery, as specified here:
http://www.android-hilfe.de/asus-me...0-9-4-3-fehlgeschlagen-brick.html#post7005266
Plzzzzzzzzz help meee
hi guys
i have asus memo pad fhd 10 302KL with soft bricked problem ( stuck at asus logo ) i try to use Volume UP + Power to go to recovery but nothing at all only asus logo...
so i try Volume Down + Power i got fast boot screen i use fastboot devices got answer from fastboot i try to flash with fastboot from original aSUS image files but nothing...
i think boot loader is locked only way to unlocking boot loader is apk from asus website? i don't have any os to install apk what should i do now plzzzzz help me.
About 2 days back i received new android update from google. My phone was already rooted.
After installing new software phone was not starting.
When click poer button i launch on screen with options as Normal Powerup, Recovery, Factory etc..
I tried to recover but nothing happens when i click on recover.
Select Normal Powerup then also nothing happens.
Select Factory nothing happens. I am stuck on same page when starting phone.
I try to flash and install again using steps mentioned on xda but receive error when below command is entered:
mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.095s]
writing 'partition'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.266s
On mobile i see below messages:
cmd: getvar:max-download-size
cmd: download:0008000
cmd: flash: partition
hab check failed for primary_gpt
Failed to verify hab image primary.gpt
I am stuck and unable to start my phone (moto e 2).
Help Help !!
I am not sure if I have posted on correct forum..
Did you unlock the bootloader of your phone before trying to flash something?
Or
You were on the stock ROM and they shipped you a update, and it upgraded, but the update failed to work?
i can fix this error
hi guys if any one facing this error message me ill help you :good:
bodboy8042 said:
hi guys if any one facing this error message me ill help you :good:
Click to expand...
Click to collapse
dude if u can that would be amazing. Please respond as soon as possible
Help brick moto e 2015
bodboy8042 said:
hi guys if any one facing this error message me ill help you :good:
Click to expand...
Click to collapse
I have the same problem with my XT1527 , if anyone knows unlock the bootloader would be grateful ...