Hi, I was wondering if anyone could please help. I have a gear live, always running on stock firmware. Randomly without me doing anything to the device, it got stuck on the boot logo. So I decided to see if I could boot into recovery mode, but I get the error
"mmc_read fail" and "movinand checksum confirmation fail"
The bootloader also seems to be locked, so is there any way I can recover this device?
EDIT: The only thing I can do is boot into Fastboot, can't enable USB Debugging for adb to work
Thanks
Please help, i can only access fastboot with a locked bootloader
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 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.
I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?
protatocrisp said:
I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?
Click to expand...
Click to collapse
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.
AsItLies said:
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.
Click to expand...
Click to collapse
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.
protatocrisp said:
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.
Click to expand...
Click to collapse
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.
AsItLies said:
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.
Click to expand...
Click to collapse
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.
protatocrisp said:
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.
Click to expand...
Click to collapse
well if there's a lesson here it's that it's exceptionally important to pay attention to exactly what you're doing. Double check everything; that you're flashing the correct files, that you back up the correct files and name them appropriately, read directions over and over to be sure u understand.
it sounds like if you keep going back to fastboot when trying to start system, then you're probably re-flashing the engineering abl and not the original abl, which yer suppose to save off first.
yeah, maybe start over again by flashing a stock rom.
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..