Database Develop

Having trouble with restoring a soft-bricked XT1068

Hi there,
a friend asked me for help with restoring his german Moto G 2014 (XT1068). The last working software on the device was the Marshmallow update. He was having software issues and softbricked the device when trying to install a custom ROM.
Fastboot mode and stock recovery is accesible, the bootloader is unlocked and the device is stuck on the "WARNING: BOOTLOADER UNLOCKED" screen when trying to boot normally.
I have tried following this guide to revert the phone back to stock firmware with a matching system image. Both the XT1068_TITAN_RETDE_6.0_MPB24.65-34-3_cid7_CFC and XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC images will flash without any error messages. However, the device does not boot the new software. Also, when trying to relock the bootloader, the mfastboot oem lock command failes with the error message Not supported command in current status!. I tried to substitute mfastboot with fastboot, changed USB cables and downloaded new copies the images, with no success.
Digging deeper, I found out that I could not wipe cache or data using the stock recovery. This will fail with the error message blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed. Further troubleshooting attempts lead me to try twrp custom recovery software (Version 3.1.1) which I could only start using the mfastboot boot twrp-3.1.1-0-titan.img command since flashing the image as custom recovery will not fail but the phone instantly and silently reverts to stock recovery - even when not rebooting inbetween. Consequently, any attempts to flash an image using the software will fail with E1001: Failed to update system image.
At this point, I have no idea what else I could try. That's why I turn to you, great community of XDA .
Any help would be greatly appreciated.

Using Lenovo Moto Smart Assistant to restore stock rom (and lock bootloader after)

If you have some difficulties finding fastboot rom for some G5S+ variant, I suggest using Lenovo Moto Smart Assistant (LMSA). You can download it from here and install on your PC.
How to download latest specific stock fastboot rom for your G5S+
You must:
Using stock rom (locked or unlocked bootloader).
Install Lenovo Moto Smart Assistant on your PC.
Restore stock firmware, recovery, and boot image (if you changed it before).
Steps:
Reboot your phone to bootloader.
Open "Lenovo Moto Smart Assistant".
Connect your phone to PC using the USB cable.
Choose "Flash" menu on LMSA.
Choose "Moto Phone".
Choose "Moto G Plus (5th Gen S)".
Choose your phone models.
Wait for a minute while LMSA checking your phone, and then choose "Rescue". It will download the latest 1.5+ GB stock fastboot rom based on your phone model. You can find it on "C:\ProgramData\LMSA\Download\RomFiles".
Click "Rescue" to flash latest rom and accept some confirmations. Your phone will be rebooted after flashing process completed.
Now your phone is back to stock rom. Of course, if you have unlocked it before, those steps wouldn't lock your bootloader. If you want to lock it, I suggest you do it immediately after flashing process completed.
Here to lock your phone after successful stock rom restoration.
You must:
Have ADB fastboot driver installed.
Get extracted fastboot rom from "C:\ProgramData\LMSA\Download\RomFiles".
Steps
Reboot to bootloader.
Open "Command Prompt" on your PC, and go to the location of extracted fastboot rom.
Connect your phone to PC using the USB cable.
Check first that your phone is connected using "fastboot devices" command.
Do all below commands in sequence:
Code:
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
Your phone will be restarted. There will be no unlocked bootloader message anymore. And you'll have your phone locked. Ta-da .
Note:
Check "system.img_sparsechunk.x" files (where "x" is sequential numbers) in extracted fastboot rom folder. Newer rom may have more files than the older one. You must flash ALL those "system.img_sparsechunk.x" files in sequence.
If you have issues, please share here. Thanks are appreciated.

I did all above steps but my G5 plus is still saying it has an unlocked bootloader with a ID: Invalid key error.
My phone simply avoids the bootloader to be relocked... it's just pure garbage...

What is the reason for relocking the bootloader? You don't get the warranty back...

should i setup my devices and come back to bootloader or without setup please clear this
thanks in advance

Will Moto Smart Assistant also work for the G7 (Play)?
Motorola support sais no (and that there is no way at all to restore the images after unlocking the bootloader)... will try to find out myself later today.
And another question, do people have experience with updating Motos via Moto Smart Assistant? Reason is that latest models (G7) do not allow for OTA updates with bootloader unlocked. Am wondering if it will still be possible via the Smart Assistant - provided that works at all

Does it require only stock rom?
Can i flash the stock rom using lenovo smart assistant when the phone is with custom rom?

Tried it all, but no good news.
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802

Install Pixel Experience ROM
voliveira92 said:
Did it all, but my phone is stuck in boot screen. Can enter bootloader and recovery but can't do anything else. Tried everything I could find online (adb flash from twrp, fastboot flash [stock rooms, custom rooms]). Just keep getting kernel errors. If someone could please give me a light I would aprecciate a lot. This started after I installed lineage and tried to restore it back to stock via fastboot flashing (Potter retail 8.1), since fingerprint sensor stoped working on lineage. Mine is XT1802
Click to expand...
Click to collapse
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again

Abhimlv12345 said:
I am on Pixel Experience ROM and this ROM is purely copy of Android Pie of Pixel Devices and most stable rom
Prepare an sd card and copy pixel Experience ROM winrar file then put it in your phone and flash going into the recovery mode
This will work out for your device and will start up again
Click to expand...
Click to collapse
hello i was looking around to fix my revvl xt-1952-t ( motola g 7)
its stuck in boot loop flashing bad key ( always had bad key since unlocking the phone. )
i have done a couple roms on samsung devices and never on any thing else .
fast boot is some what new to me. i love it vr oden installs . so i went to reinstall
stock rom on a extra phone
and didnt not get it to load i have whipped and reinstalled 4 tines checked the models var etc seems like it is all correct . is there any ideas or tricks i could be missing

I think i did it without flashing the sparsechunk

Troubles reinstalling TWRP [Failed to load/authenticate boot image: Load Error]

I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!

Got it to load once, but now back to square one. Throwing same error.

Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.

Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once

Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.

I have the same error. How can I fix this pls?

MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.

Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?

i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?

Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?

DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.

hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp

Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?

iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder

Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method

greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro

Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother

try fastboot set_active a
or fastboot set_active b

Please help! I've bricked my Moto G6!

When I boot my phone, it says:
AP Fastboot Flash Mode (Secure)
Error: failed to load kernel!
Fastboot Reason: Fall-through from normal boot mode
I've tried wiping and flashing several roms on it through TWRP, but keep getting this error. What am I doing wrong? The bootloader is unlocked and the device is rooted, if that helps.
I followed the instructions here: https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292
and the device is now booting. But it said it was encrypting the data which doesn't sound right, I don't want that.

Before you flashed the stock ROM again, was the device encrypted?

Help needed for identifying problem (Stuck in Fastboot)

I have Realme X2 Pro stuck in fastboot mode with bootloader unlocked, unable to access recovery or boot into system. Is there a way to know which variant my phone belongs to, or any details?
Fastboot shows, product name: msmnile, variant: SDM UFS, bootloader and baseband version are empty.
I don't know exactly which variant my phone belongs (EU/IN/CN). Tried flashing three different variants of fastboot flashable images in this order (boot > dtbo > system > vbmeta > vendor), files flashed successfully, but same result. Continious booting into fastboot mode. Also tried booting into recovery directly by using command "fastboot boot twrp.img" which gave an error - command failed (unknown command).
I downloaded the official .ozip file from realme website and extracted the images for flashing through fastboot, but no luck, same scenario.
Tried Realme Flash tool for this file "RMX1931EX_C.27.ofp", after flashing device rebooted into fastboot mode again.
Please help me out, I'm new to this.

I'm in the exact same spot as you. Did you find a fix?

Chromelon said:
I'm in the exact same spot as you. Did you find a fix?
Click to expand...
Click to collapse
Did u find any solution, I have same problem