I would like to know if there is anyone who knows how to fix the bootloader error on a TF700T with the Unrecoverable bootloader error. I have access to fastboot and the entire device is wiped due to following another tutorial for fastboot to recover from the bootloop error.. there is no more way to enter recovery or cold start android... the device has two options, fastboot mode, or being stuck at the asus logo untill the battery runs out. I don't think i can flash anything with fastboot as the bootloader is locked.
i'm open to any and all critiques and pieces of advice..
Related
So as my friend was sleeping last night apperently his phone was hardbricekd. When he woke up it wouldn't leave the screen: boot up failed. Failed to validate boot image: ret=-1. He texted me from his pc asking for help. I told him to boot into recovery and just reflash stop. When he tried it said: Fastboot demon: failed to initialize partition table. What can he do??? It was stock and hadn't been rooted in a very long time!
Same problem: Stuck in fastboot
I'm having the same issue. After having 6.0 for a few days, my Nexus 6 shutdown while I was using it. It will only boot into Fastboot mode, with the same errors. I finally got adb to recognize it when plugged into my computer, but don't really know how to proceed. The command "fastboot oem unlock" says I need to allow this option on my phone, but I can only get into fastboot so that's impossible. All the guides I see to flash anything require this step.
I've done some digging. http://forum.xda-developers.com/nexus-6/help/stuck-fastboot-flash-to-recovery-t3266921 ... This forum suggests it's not fixable by a home user, but if anyone else has more info please let me know. You guys on xda are infinitely more knowledgeable than I am on this.
Nevermind. A little more reading, and I understand more of the jargon. Locked bootloader, no TWRP = no bueno. RMA is my only option. Guess I'll order a Nexus 5X and take steps to make sure this won't happen again.
I have a Red Magic 3 and im having issues.
Its in fastboot but when i go to boot to recovery it just goes to fast boot. i got to boot it to android and the same thing. Fastboot i can see it with fastboot devices but i cant in adb devices. When i plug it in with fastboot its not in device manager but when i put it into EDL mode it shows in device manager. Tried putting twrp on it and it just goes back to fastboot and relocks the bootloader. I used the recovery tool and its giving me this error.
Any idea on what could be doing this? Or how i can fix this?
Wont let me post a link to a picture. But its saying reset EDL mode and download failed. I got my firewalls all disabled. Running windows 10 pro.
Help me please
Hi guys,
I've a leeco le2, it's in some sort of bootloop. I now have a phone which I hope is not actually bricked.
To cut to the chase:
The phone boot loops - it shows the "Leeco" on the black background for less than a second, then reboots, after 2 seconds, it comes back up with the "Leeco" and reboots, and so on.
I can get into fastboot mode. Interestingly, the status shows "Device is LOCKED"
I cant get to recovery mode. It just goes into the boot loop again.
Using the adb tools, I cant issue the "fastboot flashing unlock" or "fastboot oem unlock" commands because it returns: "FAILED (remote: 'oem unlock is not allowed')"
I am unable to get into the phone OS to change the settings because the phone is boot looping
. I am flashed several time in flashone,qfil and Miracle thunder but problem is same.
Given the fact I am unable to get to recovery, I am unable to sideload an OTA zip. And given the fact that I cant boot into the OS, I cant enable oem unlocking.
Do I have any hope at resurrecting this phone in any way? please help me
Check this : https://forum.xda-developers.com/t/...-le-2-s3-noob-friendly.3515555/#post-69996355
Hi everyone,
I locked my asus rog 3 bootloader with the command "Fastboot oem asus-lock"
after restarting the phone it gave me "your phone is corrupted and cannot be trusted" error.
then I rried to inter recovery mode to do a format but the phone enters CSC Fastboot mode and stuck in it!
Please help me solve this issue.
Darkness191 said:
Hi everyone,
I locked my asus rog 3 bootloader with the command "Fastboot oem asus-lock"
after restarting the phone it gave me "your phone is corrupted and cannot be trusted" error.
then I rried to inter recovery mode to do a format but the phone enters CSC Fastboot mode and stuck in it!
Please help me solve this issue.
Click to expand...
Click to collapse
Use EDL mode to flash a clean firmware - you can find all you need on the forums here. You can also try and flash a clean boot img only first using QFIL and see if that resolves it depending on which ROM you're on.
Hi i have a model XT1921-5. It got stuck in the logo screen and couldnt boot into recovery so i tried a rescue with the RSA, it detected the phone in fastboot and found the firmware but failed flashing it. Now it only boots into fastboot.
When flashing the firmware manually only gpt.bin fails but the phone is still stuck in fastboot (failed to validate hab image - failed to validate boot image. same with recovery image). I tried everything i could but nothing worked out.
I think my only "chance" is to try a blankflash. The problem is that my bootloader is locked (never unlocked) so i cant do fastboot oem edl, i cant find anything about test points for this model.. So im looking for a way to maybe hard brick the phone to force it boot into EDL mode and try the blankflash. Unless there's a way to set the OEM unlock option via fastboot..
I appreciate any help.
Thanks in advance.
I was able to put my phone on QDL mode via test point.
Now i tried to flash the blankflash but it throws the error "XML (0 bytes) not validated"..
Does anyone knows what this error means? If is a version mismatch then i cant find a newer version of this blankflash..
Any help is always appreciated.
For anyone interested this is the test point you need to short to boot into QDL mode