Hey folks, just softbricked a device(XT1521 surnia) while rooting. And while flashing stock firmeware mistakenly flashed bootloader.When ever i try to flash a twrp, it strucks on sending via mfastboot. I have downloaded a cynogen adn want to flash a custom recovery, but due to ruiened bootloader no able to send any flash files.though i have unlocked bootloader.Please help me. This is indian version device previously running on 6.0. now flashed 5.1.1 and ruined the bootloader.
In the cmd :
D:\Mfastboot\Mfastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
It just struck there only. I am not saying about gpt.bin but also recovery, bootloader, boot,etc.
On bootloader logs:
Fastboot Reason: UTAG "bootmode" configured as fastboot
USB connected
cmd: oem fb_mode_set
cmd: getvar:max-sparse-size
cmd: download:00008000
Nothing happens. Please help me.
I also emailed moto technical support for the same.
Related
I am not a developer, but would like to consider myself an advanced user.
After unlocking the bootloader, I have installed custom ROMs on three different devices at different times. I have also installed the stock ROM. But have never locked the bootloader back.
However, on the current device (that was looping through the bootloader), I installed the stock ROM (RETAILDSDSALL_XT1022_4.4.4_KXC21.5-40_cid7_CFC.xml) and locked the bootloader. Successfully updated it to the official OTA Lollipop 5.1.
After that, I just tried my luck to install Ubuntu Touch (ported actually for Moto G [falcon] by h2o64, based on this thread). I unlocked the bootloader again for this. The install was 'successful' (there were no errors surprisingly), but the device obviously did not boot.
Now, I wanted to reinstall the stock firmware on the device. This time however, it fails at this command:
sudo fastboot flash partition gpt.bin
Here's the result >
target reported max download size of 299892736 bytes
sending 'partition' (32 KB)...
OKAY [ 0.087s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.667s
I have used fastboot in Linux all the other times I said I installed custom and stock ROMs.
However, I tested with mfastboot on Windows 10 as well, with no luck.
I am also able to successfully install TWRP recovery on the device and erase "system", "cache" and "userdata" using fastboot. However, cache and dalvik cache removal fails on TWRP.
Finally, although the partition flash command (which I personally understand as creating the partition table - correct me here please) and the motoboot.img flash command failed, I ran the rest of the commands and successfully installed the stock ROM mentioned above. However, this time, the "fastboot oem lock" command fails.
Any suggestions would be of great help... (it's not my phone)
I made a bootlogo with Moto Boot Logo Maker (http://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667).
But when I tried to install the bootlogo via fastboot, I did the mistake of try to flash 'boot' instead of 'logo'.
I tried to flash bootlogo in 'boot' partition 3 times, and now I don't know what to do.
Please help, what to do now?
I don't know if I can turn off my phone or try to restart, I don't know if it'll start again or if it'll hard brick because I tried to flash 'boot' partition.
What can I do? Will I need to download original firmware and flash boot with its correct image?
Computer Logs
Code:
fastboot flash boot bootlogotest.bin
target reported max download size of 299892736
sending 'boot' (597 KB)...
OKAY [0.047s]
writing 'boot'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.094s
fastboot flash boot bootlogotest.bin
target reported max download size of 299892736
sending 'boot' (597 KB)...
OKAY [0.062s]
writing 'boot'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.094s
fastboot flash boot logo.bin
target reported max download size of 299892736
sending 'boot' (421 KB)...
OKAY [0.078s]
writing 'boot'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.094s
Phone Logs
Code:
Fastboot Reason: Reboot mode set to fastboot
USB connected
cmd: getvar:partition-type:boot
cmd: getvar: max-download-size
cmd: download:000954e8
cmd: flash:boot
Mismatched partition size (boot)
cmd: getvar:partition-type:boot
cmd: getvar: max-download-size
cmd: download:000954e8
cmd: flash:boot
Mismatched partition size (boot)
cmd: getvar:partition-type:boot
cmd: getvar: max-download-size
cmd: download:000696e8
cmd: flash:boot
Mismatched partition size (boot)
Phone Info
Code:
Model: XT1025 Dual Sim w/ TV - Brazillian Retail
Updated to first 5.1 Official OTA on July 23rd
Then installed Resurrection Remix
So is your phone booting now?
It wouldn't have done any harm imo.
I haven't came across it before so nothing can be said for sure.
Chances are, fastboot formatted your boot partition and when tried to flash the IMG, throws that error. In that case, your boot partition is empty and system is without a kernel. You will need to flash stock IMG in that case.
However, it might be the case that fastboot performed the check before formatting partition and your kernel might be residing there safely.. But no way of knowing that without booting.
So if you want to be on safe side, flash the stock img.
If you want to try and check , try rebooting once. You might be able to boot into bootlaoder mode after.
Tapped from my Moto X
neo.ank said:
I haven't came across it before so nothing can be said for sure.
Chances are, fastboot formatted your boot partition and when tried to flash the IMG, throws that error. In that case, your boot partition is empty and system is without a kernel. You will need to flash stock IMG in that case.
However, it might be the case that fastboot performed the check before formatting partition and your kernel might be residing there safely.. But no way of knowing that without booting.
So if you want to be on safe side, flash the stock img.
If you want to try and check , try rebooting once. You might be able to boot into bootlaoder mode after.
Tapped from my Moto X
Click to expand...
Click to collapse
I thought boot partition was important as motoboot's bootloader partition or gpt, forgot 'boot' is kernel.
fastboot formatted my boot partition, phone was stuck at bootlogo.
Downloaded official XT1025 firmware and flashed only boot partition.
Went to TWRP, installed my old custom kernel and now the phone is fine.
Thanks
Glad u solved it..
Tapped from my Moto X
The custom logo's doesn't flash on the boot partition, flash on the logo partition
Example: mfastboot flash logo nameoflogo.bin
Hi guys, a friend of mine had a problem with his Moto E XT1021 and I'm trying to help him. I'm stuck on this screen and i don't know what to do:
AP Fastboot Flash Mode (S)
...
Battery OK
Devis is LOCKED. Status Code: 0
Connect USB Data Cable
...
failet to validate system image
Fastboot Reason: Fall-through from not charger-boot mode
He told me that he started to have problems after updating his phone. Whatever I do, I get:
failed to validate system image
Boot up failed
I tried to unlock the bootloader, but when I type fastboot oem get_unlock_data I get this error:
(bootloader) Could not get unlock data! OKAY [ 0.166s] finished. total time: 0.173s
...any suggestions? Thanks.
Anyone who can help me?
Here's the link of stock firmware, flash it (guide included) :
http://forum.xda-developers.com/showthread.php?t=2755857
It doesn't require unlocked bootloader.
I tried but I get this error when i type the flash boot command:
C:\...\XT1021_CONDOR_RETEU_5.1_LPC23.13-34.8_cid7_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.398s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.463s
The smartphone shows: "hab check failed for boot"
...it is possible that I downloaded the wrong version ?
I'm assuming you're using Indian variant. So according to that you're using correct image.
Did these commands returned okay?
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
-z3r0- said:
I'm assuming you're using Indian variant. So according to that you're using correct image.
Did these commands returned okay?
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
Click to expand...
Click to collapse
Yes, they returned okay. When I type mfastboot flash boot boot.img, I get "failed".
-z3r0- said:
I'm assuming you're using Indian variant. So according to that you're using correct image.
Did these commands returned okay?
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
Click to expand...
Click to collapse
Why are you assuming that I'm using the Indian version ? The phone was purchased from Amazon in Italy and I was trying to flash the stock retail EU 5.1
I tried the 4. KitKat but i got some error about downgrading.
What you actually did, before this problem was caused?
Were you using the same rom(that you're trying flash) ??
It's not my phone, but he said that after an updating (was a normal update. I suppose it was the 5.1 update) he started receiving this problem.
Can you help me?
Okay skip the boot.img step and execute the rest of the commands.
Okay I will try
So i tried but this commands failed:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
...Remaining commands returned okay, so i don't know.
rafapp said:
So i tried but this commands failed:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk1
mfastboot.exe flash system system.img_sparsechunk2
mfastboot.exe flash system system.img_sparsechunk3
...Remaining commands returned okay, so i don't know.
Click to expand...
Click to collapse
That's not done dude.
It shouldn't have fixed your device the main part was this
mfastboot.exe flash system system.img_sparsechunk*
and that returned Failed too. Since the bootloader isn't unlocked so flashing custom recovery isn't possible too.
There's no other way I can see but device is bricked.
So is it impossibile to unbrick it?
rafapp said:
So is it impossibile to unbrick it?
Click to expand...
Click to collapse
Okay there might be this issue (Check out this post) :
http://forum.xda-developers.com/showpost.php?p=55176859&postcount=60
So for once try downgrading to this "RETEUALL_XT1021_4.4.4_KXC21.5-40_cid7"
https://www.androidfilehost.com/?fid=24052804347796738
-z3r0- said:
Okay there might be this issue (Check out this post) :
http://forum.xda-developers.com/showpost.php?p=55176859&postcount=60
So for once try downgrading to this "RETEUALL_XT1021_4.4.4_KXC21.5-40_cid7"
https://www.androidfilehost.com/?fid=24052804347796738
Click to expand...
Click to collapse
I tried and it didn't work. All the commands failed.
hello,
i follwd the procedure u said but all are unsuccssfull and even i tried by skipping the boot.img step and executed the rest of the commands.
but i found
prevalidtion failed for
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
-z3r0- said:
Okay skip the boot.img step and execute the rest of the commands.
Click to expand...
Click to collapse
Hi, did this get resolved? I have the same problem. My XT1021 (UK Tesco variant) had been switched off for some time. When I turned back on it was looping in fastboot. Could not even turn it off. I tried flashing with a number of stock ROMs using usb to PC and mfastboot commands. Many stock ROMS caused errors on various commands, the 5.1 UK Tesco variant seemed to work perfectly - no errors displayed on phone or PC. But hone now boots too fastboot and shows the failed to validate system image error. Battery is apparently OK .. is something else likely to be toasted?
Its an old phone but would be good for my son as he starts senior school until he has proved he won't lose it
Similar Problem with Moto XT1225
Hi there, I've similar problem with XT1225.
I tried to lock the oem and it is locked with status code 2. I forgot to enable OEM unlocking from the Developer options and now I have no way to boot my device it always end up loading into fastboot mode.
Any help would be appreciated.
So straight to it, when I am trying to flash twrp recovery img with adb I keep getting failed (remote:unknown command) .
Process I have done;
Turned on oem unlock and debugging in developer otions
Unlocked boot loader via adb with fastboot oem unlock
Rebooted and got corruption msg but thats due to bootloader unlock
Put twrp in adb folder
Rebooted into fastboot
attempted to flash twrp recovery img via fastboot flash recovery twrp.img
Then thats when I get my error as follows;
target reported max download size of 536870912 bytes
sending 'recovery' (19412 kb) ...
okay [0.443s]
writing 'recovery' ...
failed (remote: unkown command)
finished. total time: 0.469s
Did I miss a step? I was reading something about a "fake" bootloader unlock besides h850?? I did achieve root with a tot file and lg up that did have already twrp baked in, but I need to get a stock rom so I can go ahead and switch between root and non root, cause I use an application for work that doesn't like root
i know this is an old post but i'm having the same issue. is it not possible to flash recovery with latest firmware?
same
I am new here and this was my first time actually trying any of this. I have my bootloader code, if that helps.
Phone turns on to erecovery mode if powered on normally. Running erecovery downloaded and installed RNE-L21 8.0.0.355(C185). It then asked me to Factory reset, after which it booted back in to erecovery. I can put phone in FASTBOOT&RESCUE MODE by plugging it in to PC and holding power + vol. down.
About Phone
-code
DC-unlocker:
manufacturer - Huawei phones
model - Huawei phone in fastboot mode
Found Phone : RNE-L21
Model : Huawei phone in fastboot mode
IMEI : 868859036054492
Serial NR. : FFY5T18224032295
Firmware : RNE-L21 8.0.0.355(C185
IMEI1:868859036074508
FB LockState: LOCKED
I wanted to downgrade from Oreo to Nougat.
To unlock bootloader, I used Potatonv:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
I installed the TWRP in this post:
TWRP For Mate 10 lite 8.0 Oreo Version For RNE-L21C185
Here is twrp for HUAWEI MATE 10 LITE. Who want? Comment Here. :p
forum.xda-developers.com
I booted in to TWRP with
-code
adb reboot recovery
I made a backup using TWRP but I lost it and couldn't make another one because of some error in TWRP.
I then installed magisk .zip file through TWRP.
The phone would boot in TWRP no matter which option I chose in the Reboot menu of TWRP. Being really impatient, I decided to flash another version of TWRP on recovery partition, with SD card, through TWRP itself. I got this 2nd TWRP from:
How to Install TWRP Recovery and Root Huawei Mate 10 Lite
In this article, we will guide you on how to root Huawei Mate 10 Lite and Install TWRP Recovery.
clickitornot.com
The new TWRP doesn't work and phone does not show bootloader unlocked warning anymore. Upon rebooting after new TWRP, phone showed this error first few times.
I'm not really sure what to do but I figured I'd run some commands that might help someone figure out what I should do.
fastbootoem get-product-model:
(bootloader) RNE-L21
OKAY [ 0.025s]
finished. total time: 0.026s
fastboot getvar vendorcountry:
vendorcountry: hw/meafnaf
finished. total time: 0.025s
fastboot oem get-build-number:
(bootloader) :RNE-L21 8.0.0.355(C185)
OKAY [ 0.026s]
finished. total time: 0.027s
fastboot getvar rescue_enter_recovery:
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.063s
fastboot oem oeminforead-SYSTEM_VERSION:
(bootloader) :RNE-L21 8.0.0.348(C185CUSTC185D1)
OKAY [ 0.031s]
finished. total time: 0.031s
I believe the rom for my phone is
RNE-L21 8.0.0.348(C185CUSTC185D1)I have downloaded it from https://gsmfreehelperteam.blogspot.com/2020/04/rne-l21-800348c185custc185d1-file-by.html but I really don't know what to do with it and I don't want to mess it up any further. Sorry for the long read, any help would be great.
brokenpotato said:
Upon rebooting after new TWRP, phone showed this error first few times.
Click to expand...
Click to collapse
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
brokenpotato said:
I wanted to downgrade from Oreo to Nougat
Click to expand...
Click to collapse
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
-Alf- said:
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
Click to expand...
Click to collapse
"fastboot flash recovery RECOVERY_RAMDISK330.img" gives:
target reported max download size of 471859200 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.055s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.067s
brokenpotato said:
Command not allowed
Click to expand...
Click to collapse
= Locked bootloader or FRP lock
-Alf- said:
= Locked bootloader or FRP lock
Click to expand...
Click to collapse
IT does say "FRP Unlock" in red on fastboot&rescue screen. Should i try fastboot oem unlock?
brokenpotato said:
Should i try fastboot oem unlock?
Click to expand...
Click to collapse
Why not?
Fastboot oem unlock *************** worked, the phone booted up in to android and is working normally. Thank you so much!!
brokenpotato said:
Fastboot oem unlock *************** worked, the phone booted up in to android and is working normally. Thank you so much!!
Click to expand...
Click to collapse
No problem.
-Alf- said:
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
Click to expand...
Click to collapse
When trying to flash the TWRP, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'recovery' (24790 KB)...
OKAY [ 0.794s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.809s
brokenpotato said:
fastboot flash recovery TWRP-oreo-smart.img
Click to expand...
Click to collapse
Read carefully.
brokenpotato said:
When trying to flash the TWRP, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'recovery' (24790 KB)...
OKAY [ 0.794s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.809s
Click to expand...
Click to collapse
Just realized I had to flash twrp on recovery_ramdisk and not on recovery. It works like a charm