Hi, today I recieved a A510 Tab with a broken Update that came OTA, The device hang on "Booting failed, Starting fastboot USB download protocol"
I cant access any recovery from here, it fall back to "Booting failed, Starting fastboot..."
I tried to unlock the device. It says "unlocked". However I tried to flash a recovery afterwards and fastboot tells me " Bootloader is locked".
So, i can't acess anything from now. Someone has a idea how to solve this?
Nobody has an idea? I was never on a Acer before so.. Is there no way to get into a recovery or something ?, its very frustrating.
I guess i have to trash this tablet. To bad because i've never used it at all.
Related
I have an interesting problem:
I have a tf300t curently running JRO03C.ww_epad-10.4.2.17-20121018
I ended up here after an unsuccessful flash with twrp. Tried to recover my back up with no joy. At this time it would only boot twrp recovery, finally flashed stock via micro sdcard and got it to boot again! Only I had no root anymore, so I tried to boot into recovery and there was none. So next I tried to boot into bootloader and when I select fastboot, the tablet says starting "starting fastboot download protocol" but after nothing else happens. ADB looses it, and it just stops right there.
The good news is that I can still use the tablet, it boots and everything works fine but I have no root. I have searched and read and searched and read. I don't know if the reflash flashes the bootloader but that didn't seam to have any effect. If anybody could point me in the right direction I would sure appriciate the help.
there is a way on the TWRP instructions using terminal when you are in system
nitsuj79 said:
I have an interesting problem:
I have a tf300t curently running JRO03C.ww_epad-10.4.2.17-20121018
I ended up here after an unsuccessful flash with twrp. Tried to recover my back up with no joy. At this time it would only boot twrp recovery, finally flashed stock via micro sdcard and got it to boot again! Only I had no root anymore, so I tried to boot into recovery and there was none. So next I tried to boot into bootloader and when I select fastboot, the tablet says starting "starting fastboot download protocol" but after nothing else happens. ADB looses it, and it just stops right there.
The good news is that I can still use the tablet, it boots and everything works fine but I have no root. I have searched and read and searched and read. I don't know if the reflash flashes the bootloader but that didn't seam to have any effect. If anybody could point me in the right direction I would sure appriciate the help.
Click to expand...
Click to collapse
I saw on another site that with this tablet it will go into fastboot but wont popup as fastboot device on your computer, but you can still use fastboot commands. worked for me
mikaole said:
there is a way on the TWRP instructions using terminal when you are in system
Click to expand...
Click to collapse
You must have root permission for that method
imp3r10 said:
I saw on another site that with this tablet it will go into fastboot but wont popup as fastboot device on your computer, but you can still use fastboot commands. worked for me
Click to expand...
Click to collapse
No when I try to flash recovery it says waiting for device and nothing ever happens.
I seamed to have got it. I down graded to 10.4.2.9 and back to 13. plugged it to the computer and this time it installed drivers and that time I was able to flash recovery. I don't know what happened and it was probably something that I was doing wrong. But just incase that is what did the trick and it helps someone else, i wanted to be sure and follow up.
tf300t
I was using energy rom, I am 90% sure it was the 4.1 version. (the rom folder was labed Energy.TF300.JB.11.30.2012.zip)
Today i tried to revert it back to complete stock. tried to flash the latest blob from asus' website using fastboot, and when it rebooted, i got the dead android logo, and then nothing. I then followed some other guides from here and such to try to recover it, and now I am stuck with it going straight into TWRP v2.3.1.0 recovery. It then asks me for a password. I can use the adb reboot bootlader command to get back to the fastboot screen, but anytime i try to flash anything, it never takes. the command window says it went, but the tablet just freezes up, until I hold down power until it reboots. Is there any fix for this? Or am I completely and utterly screwed? I will reply asap to any posts, so feel free to ask me for more info if neeed, ill answer the best i can.
Basically you have flashed a 4.2 bootloader onto a 4.1 recovery (TWRP 2.3.1.0)
Sorry but that is a brick.
If you had updated TWRP to a compatible version at the same time you may have been able to save this first ......
As far as I'm aware the only fix is to send it back to Asus for repair.
crap LOL. I got into fastboot, used fastboot erase system, and fastboot erase recovery. Now when i try to click any of the 3 icons, i get unrecoverable bootloader error 0x000000. I can still use fastboot tho when i reboot. anytime i try to flash still, the tablet freezes. when on 3 icon screen, it says at top left:
keydriver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.15.3-20130416" A03
It there anything i could do at this point? It is not rebooting into twrp anymore at all. And if i let it boot normally, it just sits at the asus logo. Am i mistaken in assuming it is ready for an OS to be put on it?
rboutin2 said:
crap LOL. I got into fastboot, used fastboot erase system, and fastboot erase recovery. Now when i try to click any of the 3 icons, i get unrecoverable bootloader error 0x000000. I can still use fastboot tho when i reboot. anytime i try to flash still, the tablet freezes. when on 3 icon screen, it says at top left:
keydriver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.15.3-20130416" A03
It there anything i could do at this point? It is not rebooting into twrp anymore at all. And if i let it boot normally, it just sits at the asus logo. Am i mistaken in assuming it is ready for an OS to be put on it?
Click to expand...
Click to collapse
Well any chance you had has now gone as you wiped from the bootloader which has now sent a message to the incompatible recovery to wipe and it doesn't understand the partitions so who knows what state it is in now. Sorry.
ok. well than you for your help anyways. everyone says search LOL, but everytime I try to do the things everyone says to they fail for me LOL.
rboutin2 said:
ok. well than you for your help anyways. everyone says search LOL, but everytime I try to do the things everyone says to they fail for me LOL.
Click to expand...
Click to collapse
Unlucky mate. You never know Asus might fix it for free? It has happened.
hi all, basically title,
got a phone with a smashed screen. can get to recovery but it shows the "error mouting sdcard " message. cant flash a stock image because of it. cant get adb working on my computer either. wont boot into android, but can get into recovery and fastboot
any help appreciated, sorry for lacking detail!
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
thanks for the help, i'll try and work through this soon.
fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).
Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.
Hello,
A few days ago I found my Motorola Moto G Turbo, model MERLIN XT1557 , turned off. When I switched it back on, it did not boot successfully but instead redirected to the bootloader with the message:
"Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant."
"AP Fastboot Flash Mode (Secure)"
"failed to validate boot image"
"ERROR: Failed to pass validation, backup to fastboot"
"Fastboot Reason: Fall-through from normal boot mode"
"CID Read Failure"
"Invalid CID status 0x69"
I have not unlocked the bootloader or tried to install any custom firmware. As far as I can tell, this occurred spontaneously and without warning (my best guess would be an update that went wrong). For this reason, I have not enabled USB debugging either, so the phone doesn't even let me unlock the bootloader.
Recovery mode does not work, this merely gives the message "failed to validate recovery image". Nor do "Factory", "BP Tools" or "QCOM" do anything (barcodes works). Thus even if I wanted to perform a hard reset, I cannot seem to do it.
Strangely, I seem to be able to access two different types of bootloader interfaces, one with just text and another with a picture of an android. Neither seem to be of much help, however interestingly the one with the android picture states "Software Status: Official" while the pure text one sometimes (not always for some reason?) states "Software Status: Modified". Again, just to reiterate, I haven't performed any custom android modifications.
After all i tried to flash stock firmware, it installed successfully without even a single error and then again the same thing starting to happen, firmware installed but didn't solved the problem, same dual bootloaders menu start appearing.
ok, at last i am able to just boot into my phone,
used
fastboot oem config bootmode factory
Click to expand...
Click to collapse
and reboot. Phone opened in factory mode but still recovery is not accessible.
Working on figuring how can i get into recovery. Flashed twrp, didn't booted in recovery, flashed stock recovery, same result..