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
Related
A couple of days ago, I got an error on my phone (Motorola XT1033) saying that it cannot load the home screen. So, I restarted it in order to resolve the issue. However, it didn't reboot and since then it has been stuck in the Motorola logo.
I tried to do recovery or factory reset, but all the options lead to the same Motorola logo with no luck.
The only option that is working is AP Fastboot. I managed to unlock the bootloader by getting an unlock code from Motorola's website and using the mfastboot command. So I assume that the fastboot command is working since it detects the devices; however, I couldn't make ADB command to work since it give the error: 'device not found'.
Anyway, the second step is to flash the phone. According to this question, I should be able to do that. However, when I am running the command fastboot flash partition gpt.bin, I am getting the following result:
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.154s
I have been searching for days to solve this problem, but nothing yet! I don't know which part I am doing wrong.
First off, I received this phone from a friend of mine who received it brand new from textnow through the mail. I went through the steps to unlock the bootloader and errors came of that, but on the device it says "Device is UNLOCKED. Status Code: 3" so i assumed the bootloader was already unlocked based on what i have already researched and found. If this is incorrect, let me know and i will answer accordingly.
Assuming that my assumption is right, I keep getting errors when i try to install twrp. either that, or it appears to do nothing.
Going by the instructions on the cyanogenmod wiki for flashing twrp, fastboot returns this when i enter the "fastboot flash recovery your_recovery_image.img" command where "twrp.img" was my image name and then does nothing:
C:\Users\Me\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 268435456 bytes
sending 'recovery' (6808 KB)...
OKAY [ 0.219s]
writing 'recovery'...
OKAY [ 0.302s]
finished. total time: 0.524s
I did the same with mfastboot and there are no errors, but it still does nothing:
C:\Users\Me\Downloads\mfastboot-v2>mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (10270 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.448s]
finished. total time: 0.779s
I tried each of these a few times to no avail. Ive tried waiting at each step, tried the "fastboot reboot" and "mfastboot reboot" commands after the flash commands to where it booted straight up to android, tried the "fastboot reboot" and "mfastboot reboot" commands after the flash commands where i held the buttons to go back to fastboot mode and nothing.
Other things to note:
-Power+Volume down boots to a screen that has "AP Fastboot Flash Mode (Secure)" in red letters where there is device information at the bottom and I can only cycle through one option at a time at the top (if that makes sense).
-Selecting "Restart Bootloader" and "Recovery Mode" brings me back to this same screen mentioned.
Thank you in advance for your replies. I am completely new to this and appreciate the help.
I am only able to boot into fastboot mode and not the bootloader if that was not clear previously. I was up until 6am last night (or this morning) trying to figure it out and it didnt cross my mind this may be my actual issue. Thanks.
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!
I have been trying for the past few days to try to recover my CMR-W09(C00) device with no luck.
What it looks like now?
At the moment there is nothing showing on the screen regardless of what button combinations I've tried (Vol Up+Vol Down+Pwr/Vol Up + Pwr/Vol Down + Pwr, and each with USB power cable plugged in and without). The phone is able to get into fastboot mode (detected by running fastboot devices) automatically, fastboot reboot would get it to fastboot again (i.e., doesn't go to any other mode). The screen is completely dark with nothing at all.
From fastboot I can even see the current firmware version is 195. (CMR-W09C00B195 (8.0.0.195))
What did I do?
Flashed the 160 (CMR-W09C00E160R1P160B160 (9.0.1.160)) firmware which I found on firmware finder, and used EMUI Flasher to flash the firmware. (Found here: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171) Flash seems to have worked and at 100% it said something along the line of checksum failed, rebooted, and never came back to life again.
What I have tried?
1. No eRecovery (that would be easy)
2. Use HiSuite to repair devices, received unsupported device error.
3. Flashed recovery-ramdis, recovery-vbmeta and recovery-vendor and ramdisk that were extracted from 195 OTA (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v225819/f1/full/update.zip) and 160 OTA(http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v234512/f1/full/update.zip). Nothing happened. In Fastboot I can flash these three partitions and system, anything else would return command not allowed.
4. Tried DC Unlocker, when flashing xloader I got command not allowed error, in the end DC Unlocker refunded me.
5. Tried dload method with UPDATE.APP in dload folder only as well as the entire contents (META-INF/tags files and mbn files together with UPDATE.APP) in dload file, reboot using three button combo
6. In desperation I even tried to buy some "factory flash" image which was supposedly to be used by Huawei repair centres internally (with two zip files) to extract to dload folder. Again didn't do anything.
7. Tried to contacted FH to see if they support unbricking this and didn't hear a response.
8. Went to local Huawei authorized repair centre and they don't seem to have seen this device. They told me they can only fix devices bought locally.
9. Tried to flash in TWRP by flash the recovery_ramdisk partition.
All of above leads to nothing (i.e., it goes back to the blank screen with fastboot, however I can hear the USB connected and disconnected sound and HiSuite popped up again which tells me the reboot actually took place).
Some output from fastboot command:
E:\Android\M5>fastboot devices
HYY6R189********** fastboot
E:\Android\M5>fastboot oem get-product-model
...
(bootloader) CMR-W09
OKAY [ 0.013s]
finished. total time: 0.013s
E:\Android\M5>fastboot getvar vendorcountry
vendorcountry: all/cn
finished. total time: 0.013s
E:\Android\M5>fastboot oem get-build-number
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.014s]
finished. total time: 0.015s
E:\Android\M5>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.027s
E:\Android\M5>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.015s]
finished. total time: 0.016s
Click to expand...
Click to collapse
I think I am pretty much out of options right now, but if there is anything
Just wondering if there is anything else I haven't tried that I should?
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
thref23 said:
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Click to expand...
Click to collapse
Thanks for your input, I am able to write to recovery_ramdisk, recovery_vbmeta and recovery_vendor, as well as system partitions, however XLOADER and ERECOVERY* and FASTBOOT partitions seems to be out of touch.
Here are some more output from fastboot:
fastboot oem check-rootinfo
...
(bootloader) status : RISK
(bootloader) version : v1.1
(bootloader) current status: SAFE
(bootloader) old status : SAFE
(bootloader) change_time : 0
(bootloader) item: root-prop, status: SAFE, credible: Y
(bootloader) item: setids, status: SAFE, credible: Y
(bootloader) item: verifyboot, status: SAFE, credible: N
(bootloader) item: verity-enable, status: SAFE, credible: Y
(bootloader) item: fblock, status: locked, credible: Y
(bootloader) item: userlock, status: unlocked, credible: Y
OKAY [ 0.031s]
finished. total time: 0.032s
fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Are there multiple lock? What is the fblock? Would unlock that allow me to write to the XLOADER partition?
THE MAXIMUM POWER said:
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
Click to expand...
Click to collapse
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
zhuanyi said:
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
Click to expand...
Click to collapse
Im sorry about that, try to send it to china huawei service as they might repair it their for free because yours is C00
So my buddy has a Moto E7 that randomly started crashing and then got stuck in Fastboot mode. I tried LMSA and it won't detect the phone. I have tried manually flashing, RSDlite, followed a video to turn the XML file into a bat file, and it won't let me flash anything. I've spent hours googling different methods and even looking on these forums at other devices and following those steps and have had no luck. The phone is oem locked, when I use the command fastboot getvar all almost every field is blank. The ones that aren't are just the information about the components inside and serial number. Values like imei are blank, but I have the number. When I try a command like fastboot flash logo logo.bin I get:
Sending 'logo_a' (1292 KB) OKAY [ 0.034s]
Writing 'logo_a' (bootloader) Failed to erase partition
as a response. This is the same response I get for every situation of trying to flash something and when I try to erase I get met with:
\fastboot erase userdata
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
What am I missing? I just get a failed response from everything. I'm guessing the internal storage isn't formatted but I can't find a solution to format it from this state, and like most things I've search it gives me what to do when I can access the phone but not what to do when the phone is stuck here.
if the bootloader is not unlocked you can't flash a rom via fastboot...
Korokyblin said:
So my buddy has a Moto E7 that randomly started crashing and then got stuck in Fastboot mode. I tried LMSA and it won't detect the phone. I have tried manually flashing, RSDlite, followed a video to turn the XML file into a bat file, and it won't let me flash anything. I've spent hours googling different methods and even looking on these forums at other devices and following those steps and have had no luck. The phone is oem locked, when I use the command fastboot getvar all almost every field is blank. The ones that aren't are just the information about the components inside and serial number. Values like imei are blank, but I have the number. When I try a command like fastboot flash logo logo.bin I get:
Sending 'logo_a' (1292 KB) OKAY [ 0.034s]
Writing 'logo_a' (bootloader) Failed to erase partition
as a response. This is the same response I get for every situation of trying to flash something and when I try to erase I get met with:
\fastboot erase userdata
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
What am I missing? I just get a failed response from everything. I'm guessing the internal storage isn't formatted but I can't find a solution to format it from this state, and like most things I've search it gives me what to do when I can access the phone but not what to do when the phone is stuck here.
Click to expand...
Click to collapse
Hi, Have you already tried flashing using SP FlashTool?
Check the version of FlashTool and the ROM that LMSA downloads are correct.
In theory you should be able to flash the ROM without unlocking the bootleader. ^^'
FlashTool must be set to "Download Only" or "Firmware-Update"
"Format and flash", or something similar, delete the IMEI, which I would not want.