Hi all
i have asus memo pad fd10, model: me302KL with soft bricked problem ( stuck at fastboot mode and show ERROR: invalid boot image )
i try to flash with fastboot flash recovery from image files but failed..
below are the message:
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)...
OKAY [ 0.188s]
writing 'recovery'...
FAILED (remote: Invalid input Image. Cannot flash before unlock)
finished. total time: 0.219s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.188s]
booting...
FAILED (remote: Bootloader is locked)
finished. total time: 0.203s
i think bootloader is locked. How to unlock boot loader? i don't have any os to install apk and unlock/root the me302kl.
i try
fastboot oem unlock
FAILED (remote: unknown command)
What should i do now? Please help and provide me any advice.
Many thanks !!
please help
try fastboot oem unlock-go. On fastboot help:
flashing unlock_critical (this enables flashing bootloader-related partitions)
flashing unlock (this enables flashing except bootloader-related partitions)
fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: -0.000s
Any method to unlock the bootloader in fastboot mode?
Any one know how to save my soft bricked pad me302kl??
thanks!
I have the same problem, please help!
push
I have the same issue. Bad flash wiped out the partition table so i cant fastboot flash the oem zip.
push
push
push
no one know how to save my pad T_T
up ...
up ...
Same here
I guess all the unlock info is here:
http://dlcdnet.asus.com/pub/ASUS/Ee...73.649178616.1498070896-1875799990.1498070896
but this is an apk and we need a fastboot method to do it.
Can any1 help!
Thanks!
can you boot your device normally? you need to allow OEM unlocking under developer options before using the code.
Me too, I have the same problem, please help us!
Related
Hi guys,
So I have made the mistake of relocking the bootloader after unlocking it. Now my phone is bricked, and the bootloader is locked.
I have downloaded the stock rom XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml, the cid and product reference are matching, also my phone was on 5.0.2.
But my phone won't flash, for example, I get :
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (254911 KB)...
OKAY [ 8.012s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.072s"
when I input some of the commands for flashing.
My bootloader logs show :
"failed to validate system image"
I don't understand why it would be doing that as the stock is matching, I have checked on several threads and I can't find any concrete solution for fixing this.
Please help.
Thanks,
No one has a clue ?
Having the same prolem with my XT1521 please somebody helppppppppppp
up..
try to use mfastboot, its included in my modem flash zip (https://mega.nz/#!pglHWQ6B!zYNHtO9qERuFqrbv40M62kgpULS2TK53m_vB3msCC6g ), Windows only.
also there is a guide here: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
and flash in order as shown in the guide
Is Your Fastboot working or your phone completely bricked ?
Hi Gentlemen,
Thanks for the replies.
Sorry, all the above I've tried with mfastboot. It just won't flash it. Probably cause the phone is locked now.
The above is what it's returning.
Also I cannot unlock the phone anymore, it returns "FAILED (remote failure)"
"Check 'Allow OEM unlock' in Developper options"
Mine its also bricked, same situation, same problems :c
OnePlus X (Onyx) - Soft bricked
Boots into Fastboot mode, gets detected by PC.
No OS, No Recovery.
Problem: Recovery gets flashed successfully using adb and fastboot. But when trying to boot into recovery using commands, it says FAILED (remote:dtb not found); and when trying to boot into recovery using physical buttons, then it just stays on the OnePlus boot logo till eternity.
I tried using a flash tool as well(got from XDA), but the result is same.
Here is a look from cmd:
C:\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\platform-tools>fastboot flash recovery twrp-3.0.2-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 0.260s]
finished. total time: 0.728s
C:\platform-tools>fastboot boot twrp-3.0.2-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.465s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.505s
I tried flashing twrp 2.8.7.0(onyx) but still I got the same error. (remote:dtb not found). No matter what, but it just won't boot into recovery.
How it happened:
Long back, I unlocked my bootloader, installed twrp recovery and also achieved root access. Then I flashed CM13. It was working quite fine. But then OOS 3(Official) came out for OnePlus X, so I decided to download it and flash it too. It was working all fine. But then I realised that I lost my root access and my recovery was changed back to stock OnePlus recovery. After that I tried for 2 days to flash twrp back, but I continued to get that (remote:dtb not found) error. It was quite desperate; then I thought to lock the bootloader back and unlocking it back again. But the moment I used the command "fastboot oem unlock", my phone didn't ask me for a yes or no, so I tried restarting it. But it was too late, my phone got soft-bricked till then. I am trying to fix this since days, PLEASE SOMEONE HELP!!
Hi Guys
I'm trying to root my device "Sony Xperia XZ (F8332)", and I have followed the steps in the develpoer.sonymobile.com, in the last step I faced this error:
..
..
C:..\sdk\platform-tools> fastboot devices
CB512CF1A4 fastboot
C:..\sdk\platform-tools> fastboot -i 0x0fce oem unlock 0x**********************
...
FAILED (remote: Not necessary)
finished. total time: 0.023s
Then turned on the device and then it did a reset factory, and I found the status for the OEM unlocking in the developer option says that the bootloader is already unlocked.
What does this error mean?
What I have to do to complete the root ?
I want to flash new version of TWRP to my Jiayu S3. In order to flash a new recovery, I have to unlock the bootloader. Normally this is done in Android Settings > Developer options > OEM Unlocking. I can't do this, because my boot process hangs and I can't access the Android user interface at all. However, I have access to command line via adb shell and TWRP Terminal.
Can I unlock the boot partition using the command line? For example, can I use a command such as flash_unlock?
How to allow download for partition 'recovery' via command line?
Here is the actual error messages that I get:
Code:
[[email protected] ~]# fastboot flash recovery /home/Big/Download/twrp_20180417.img
target reported max download size of 134217728 bytes
sending 'recovery' (13198 KB)...
OKAY [ 1.002s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.005s
The following fails as well:
Code:
[[email protected] ~]# fastboot flashing unlock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.003s
[[email protected] ~]# fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 64.993s
So my question is, is there any command that I could enter in adb shell or TWRP Terminal Command that would allow me the flash a new recovery? Now the Android user interface for this phone does not work, but fastboot, adb and TWRP still work.
Now I have TWRP version 2.8.7.0 but in order to flash madOS Android 8.1 I should upgrade to their version of TWRP.
The usual command is fastboot oem unlock. If your phone supports this, it will wipe your phone as it unlocks the bootloader. If not, you get that error message. Not all phones support bootloader unlocking, as many ZTE owners have found out.
hello , having the same problem any soloutions ?
I would also like to know. I toggled the OEM Unlocking option thinking I was done flashing roms, but then an update happened updating my phone from android 10 to 11. Now my phone is stuck in a bootloader loop. I was able to boot OrangeFox recovery and access the terminal and I was wondering if you can navigate to that "OEM Unlocking" setting and change it to "on" somehow. My phone is the Moto G Stylus (2021) XT2115-4
Hello there , i get my device recognised with : adb devices .
Then i restart to bootloader with adb reboot bootloader .
then i try to unlock the bootloader using this : sudo fastboot oem unlock
but the error i get is this : fastboot oem unlock
...
FAILED (command write failed (Protocol error))
finished. total time: 0.004s
any idea what i should do?
no ideas?