Database Info

How to fix MOTO G7 / xt1962-1 stuck in Bootloader (stuck in fastboot) unable to boot

I do not have 10 posts yet, remove underscores from urls. I will edit this when I have 10 posts, I'm sorry for the slight inconvience.
Hi, new here! I recently acquired a Motorola G7 (xt1962-1/river_amz) from my sister. The device did not boot. It mentioned that the device did not start-up successfully, something in relation to slot/a and slot/b, and that I needed to utilize a Software Repair Assistant.
Non-Verizon devices cannot utilize this Software Repair Assistant, I tried and it hung at Processing Device Info. For Non-Verizon devices there's a piece of software called Lenovo MOTO Smart Assistant which can be found: https://support.lenovo.com/us/en/downloads/ds101291
This option did not work for me as the Bootloader did not for some reason allow the device to overwrite some of the content (permission was denied device side.)
The MOTO Smart assistant was good for downloading the devices software. So you do the following:
Download and install the smart assistant software
Click the flash option and then the rescue option
Click moto phone
Select moto g (7th gen)
Select xt1962-1 and then next to target and firmware name there's a download button press that and the firmware will start downloading
You can follow the onscreen instructions for that program, like I said however, it didn't work for me so I'm just going to tell you the steps I went through to get the device working. If you have other solutions, I, as well as the rest of the MOTO G7 users will be happy to hear what worked for you I'm sure.
I tried downloading the files from /moto-g7/development/moto-g7-river-xt1962-1-firmware-29-114-t3913673 on this site and flashing those with some of the below mentioned methods but, no dice.
The default firmware download directory is C:\ProgramData\LMSA\Download\RomFiles btw.
I didn't want to fuss with trying to get RSDlite working on Windows 10. I found that an older PC with a 32-bit install of Windows 7 was far easier to manage, so, that's what I went with.
To follow what I did:
Download RSDlite 6.2.4 from rootjunky's site via: http://rootjunkysdl.com/files/?dir=Android Programs
Download 32-bit drivers from: http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola if LMSA did not install them already
Copy the firmware folder to your desktop or somewhere easy to work from
Ensure your device is in bootloader mode
Open RSDlite and your device should be detected
Select the firmware folder and open flashfile.xml with RSDlite and press start
Let the process finish and don't interupt or you will have to do it all over again
The phone should boot, you will more than likely have to sign into an google account that's already been in use on that device (due to FRP)
You can also use the XML to BAT method, that didn't work for me (remote permission denied/device side)
I hope this helps some people who struggled like I did. Also, sorry if some things are badly worded if at all. I'm autistic and have trouble explaining and expressing things.
Check out my stock resources thread: https://forum.xda-developers.com/moto-g7/development/riveramz-stock-resources-t3917937/

Worked perfectly!
Thanks! I had the same issue (my wife's Moto G7 stuck at the bootloader) and was able to follow your directions, so much appreciated.
The only change I made was to follow the directions at this video (go to youtube/watch?v=njXQYn53SPc) to perform the XML to BAT instead of using RSDlite (since I was on Windows 10).
It worked perfectly and fixed the issue--and the great thing was that by converting the servicefile.xml instead of flashfile.xml, I was able to retain all the data on the phone.
The overall sequence of steps (listed in detail, since this was my first time flashing. Remove underscores from URLs):
Download Lenovo Assistant from your link
In Lenovo Assistant, go to Flash, then Rescue, then select model of phone. Click to download the firmware (but do not actually click the "rescue" button).
Download Google's Platform Tools (to get fastboot and ADB)
Make a folder to hold everything (called "flash")
Copy the downloaded firmware folder from C:\ProgramData\LMSA\Download\RomFiles to flash folder. Copy the fastboot, adb, and adb dll's from the Platform Tools to the firmware folder (per the video).
Copy and edit commands from servicefile.xml to a new servicefile.bat, as described in the video. Place this file in the firmware folder.
Run batch file in command prompt from the firmware folder.
That got the phone running again, with all data intact.

Thank you so much, worked like a charm.

Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Sent from my Samsung SM-G973U1 using XDA Labs

mattmsr82 said:
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Click to expand...
Click to collapse
May need to use a
Loader file or blankflash
See
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342.
Sent from my mata using XDA Labs

I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
start up failed
your device didn't start up successfully.
use the software repair assistant on computer
to repair your device
connect your device to your computer to get
the software repair assistant.
AP fastboot flash mode (secure)
no bootable a/b slot
failed to boot Linus.falling back to fastboot
Fastboot reason: fall-through from normal boot mode
USB connected
Click to expand...
Click to collapse

MrCabana said:
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
Click to expand...
Click to collapse
I ended up sending my phone back to Motorola, they they fixed it and sent it back overnight...
Sent from my Samsung SM-G973U1 using XDA Labs

Quote:
Originally Posted by NetrixX13
I had exactly the same problem. The Lineage OS installation instructions are missing an important point.
The Moto G7 has two slots, A and B. However, it seems they only come with a bootloader pre-installed on slot A, slot B seems to be completely blank.
When slot A is active and you flash Lineage OS using TWRP, it writes to slot B and switches to slot B.
When you reboot, you cannot boot anymore, because on slot B there is no bootloader.
To mitigate this issue, you have to flash a "copypartitions" zip before rebooting.
My phone also was in 9008 mode and I revived my Moto G7 using the blankflash method, see here:
https://forum.xda-developers.com/mot...reteu-t4020263
I can also confirm saving my Hard bricked, non booting black screen, no life moto g7 with the above blank flash app from above link. then i used the lenovo recovery program to put the original rom back on the phone downloadable here: https://support.lenovo.com/us/en/downloads/ds101291
if you have a black screen hard brick, no life but windows 10 sees it at an unknown or 9008 device then you can bring your moto g7 back to life again. follow all the above links and youre good!

I don't have a Windows 10 PC...plus, if I screw up my phone, I'll catch hell from the wife...lol
SO...that being said, if someone has an XT1962-6 'River' RETIN phone running Android 10 w/June Sec. Patch....I'd be willing to 'donate' to their paypal for a copy of my phones fw! Anyone interested plz pm me. Thx!

Good day, your post was very useful for me, bring back my phone, Im very grateful, thanks, sorry for my english

switch off your phones and connect usb.
first install drives to your pc by searching where to find device drivers motorola
then download lenovo smart assistant and press rescue

Hi. Im new here too. Well been for a while just my second post and the first time iv actually been able to flash a rom. I have the same problem. No bootable slots. I know exactly what i did wrong. I knew it the moment i hit the reboot button. However, i run zorin 15 on my pc and the levono assistant don't support linux. Anyone know where i can acquire the assistant running linux? Greatly appreciated in advance.

Thank you very much sd86 and chi2 for your research and help
Sadly my phone can't boot after flashing clean OS
I don't want to erase UserData partition, but it seems error is there (as it's only left partition untouched).
As I still would like to keep my data (this is the most important thing on our mobile devices) the only one hope is to unlock bootloader, flash recovery partition (eg. with TWRP) and then perform a backup from recovery software.

Blackview Tab 8 unlocked Bootloader, but how to magisk?

Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo

Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards

I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?

nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.

I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.

Alcatel Joy Tab 1/3T 8 - "System UI has stopped"

Hi all, I have an Alcatel Joy Tab that's all of a sudden decided to keep looping this error.
Error only pops up outside of the lock screen: on the lock screen, I'm able to swipe down the notifications bar and enter settings from there. Additionally, UI seems to be functional in the Camera app as well.
I've already factory reset once, and it was back to normal for a little while, but then it came back again. Any suggestions?
Specs:
Alcatel Joy Tab 1
Model 9027W
Android 8.1.0
Baseband version MT6739
Kernel Version 4.4.95

Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.

jwoegerbauer said:
Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.
Click to expand...
Click to collapse
Thanks for the reply, I've been looking for a stock ROM since I first had the issue. However I haven't been able to have any luck finding one. Do you have any suggestions on where to look? If I ultimately still can't find one am I SOL?
I've heard that you can just return to stock by using Alcatel's official Mobile Upgrade tool here but it keeps giving me a message saying that the version I'm using is the most updated version.
Software Drivers - Alcatel
Software Drivers
www.alcatelmobile.com

I would like to know more about this too. Same issue with poster. Any custom roms or anything out there for this?

No custom ROMs. There is one out there that is unlocked. But, I've lost the post about it. Used it to carrier unlock mine. Haven't had the time to see if it unlocked more.

This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Edit: "SystemUI has stopped working" is solved with the latest firmware. If you can't get latest firmware (The alcatel mobile upgrade tool kept telling me I was on the latest or it would just crash) Do a google search for MTK Sugar Tool. Versions after 2018 will force the latest updates to the device over usb
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)

cheger32 said:
This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)
Click to expand...
Click to collapse
Bootloader Unlock failed. Is there any solution?

Azukegi said:
Bootloader Unlock failed. Is there any solution?
Click to expand...
Click to collapse
Did you enable OEM unlock in developer settings first?

cheger32 said:
Did you enable OEM unlock in developer settings first?
Click to expand...
Click to collapse
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/

Azukegi said:
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/
Click to expand...
Click to collapse
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.

cheger32 said:
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.
Click to expand...
Click to collapse
Dude no way, I would love to get that TWRP from you if possible

Azukegi said:
Dude no way, I would love to get that TWRP from you if possible
Click to expand...
Click to collapse
TWRP 3.6.1 for Alcatel 3T 8 (Maybe also generic Joytab 1?)
I built this last night, seems to work well. Let me know if there are any issues. This will be my last post in this thread as I've gotten off topic. I'll create a new thread with a guide if I find the time.
This is built from a twrp compatible device tree generated from a recovery image with a few modifcations and corrections. The kernel was built from sources released by alcatel (it took me nearly a year and some legal threats to get them to release it to me.)
just flash that to recovery in fastboot mode:
Code:
fastboot flash recovery <img filename>
Be sure to make a backup of your original if possible.
I just remembered that there's a bypass method and a useful utility in existence (located here: http://www.mediafire.com/file/qtmkilaimympapf/mtk_bypass_rev4.7z/file) for enabling the use of spflashtool to make backups and even flash images without fastboot with this device. Sorry, I'm still dusting the cobwebs off of this project.
EDIT: 23 builds later and I fixed /data decryption. As I said this will be my last post here but in case I never make a formal thread, here is a fully working twrp.
Edit again: I realized adb push and sideload wasn't working so I fixed it. Here's the latest build

I've got a 3T that I use rarely and it seems if I leave it for a while I get the same lock screen issue. I've discovered mention of a T-Mobile update that might resolve this:
Does anyone know where I can get this build and if I can force it on to my 3T. My carrier has no updates available.
Android 8.1.0
Build number: 1AWKUMK0May 14, 2021Resolves issue preventing device unlockAvailable May 14, 2021
Devices that meet the update requirements can be upgraded to the current software version.

So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?

mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
If it's too late to return it you can put it in recovery mode and try to restore it that way if that doesn't work then you can reflash it with SUGAR MTK SP

mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
You can try SUGAR MTK SP

Xiaomi device bricked after reboot

My Xiaomi Redmi Note 8 Pro isn't booting anymore.
I'm stuck in the fastboot screen, I don't even reach the redmi logo in the boot, I need to recover the data on the phone but I have no idea about how to do that.
Any suggestions?
(Already tried going to recovery with power down + volume up, isn't working)

I'm stuck in the fastboot screen
Click to expand...
Click to collapse
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.

OldNoobOne said:
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.
Click to expand...
Click to collapse
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.

BrickedXiaomi said:
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.
Click to expand...
Click to collapse
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok

OldNoobOne said:
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok
Click to expand...
Click to collapse
I'll try tomorrow, thanks for all the precious details btw!

Just a question, shouldn't I unlock the phone with mi unlocker before that?

BrickedXiaomi said:
Just a question, shouldn't I unlock the phone with mi unlocker before that?
Click to expand...
Click to collapse
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.

OldNoobOne said:
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.
Click to expand...
Click to collapse
As said, I never modified this phone, is basically as if it was brand new, OS side.

Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?

BrickedXiaomi said:
Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?
Click to expand...
Click to collapse
Wow thats great link, I hope it works so you don't lose data.
The link is fresh so you can also ask there. All the Best

Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?

BrickedXiaomi said:
Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?
Click to expand...
Click to collapse
Is your phone In-Warranty? If yes or no i would suggest go your own way, once purchased an used any device, don't connect with OEM servers ever again for any OTA update coz lots of recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates and after that the phone doesnt boot, no recovery no fastboot too, so careful with contacting/updating through OEMs if out -of-warranty specially. Once out-of-warranty always use ROM channels to upgrade to new handroid versions instead of direct OTA upgrade/update, that way you may still be able to roll back the OS to previous version in case you don't like the new handroid version, lots of people don't like handroid 12 but they cant roll back to handroid 11 .

> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.

BrickedXiaomi said:
> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.
Click to expand...
Click to collapse
Yes they might not try doing that with uropean customers but they might try in other countries where there no proper legal system for things like these, also they wont do it with everyone in a particular country to avoid suspicion, theyre smart enough to know what theyre doing, but unofficially speaking many retailers have told me about such a thing (OTA Kill Device) happening in Weaker-Law-N-Order countries, so just saying precaution is always good.

BTW i've put my Retmi Noat 10 up for sale, its still in warranty & I havent used it in the last 10 months, no sim card, unused totally, just once I loaded Gcam to check how the camera is, shamshung is always better than chyneez phones mainly coz better build and component-life, chyneez devices only look shiny from outside but it doesnt last beyond 3-5 yrs, not built to last, just use-n-throw devices u knw. Such devices are only made for mass-surveillance in mind not with customers-focus. This A/B partition thing and super partition thing is adding more bad than good.

I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded* to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup off your device in preloader mode (SLA/DAA bypass and VCOM drivers needed)
After that important step you can unlock bootloader with mtkclient, install TWRP and *proof me wrong (xiaomi devices are hackable/have weak security implementations). In any case do not perform factory reset, your backup is always only backup of android OS and therefore incomplete (there are several OS on every device)
btw fastboot doesn't require usb-debugging (that's adb, not fastboot)

Do you have a tutorial about it?
aIecxs said:
I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup of your device in EDL mode (patched firehose programmer and deep flash cable needed)
Click to expand...
Click to collapse

Xiaomi Mi5 linageos 19.1 bricked after fastboot oem lock ?

Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan

congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?

Fytdyh said:
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Click to expand...
Click to collapse
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?

jever2k said:
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
Click to expand...
Click to collapse
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.

Tawsif999 said:
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Click to expand...
Click to collapse
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan

jever2k said:
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
Click to expand...
Click to collapse
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl

jever2k said:
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
Click to expand...
Click to collapse
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.

Droidriven said:
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Click to expand...
Click to collapse
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing something from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied

Tawsif999 said:
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
Click to expand...
Click to collapse
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole procedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!

jever2k said:
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole prcedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
Click to expand...
Click to collapse
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount

Tawsif999 said:
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing psomething from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Click to expand...
Click to collapse
Yeah, I jumped the gun and posted before seeing all the replies in the thread describing their whole scenario, should've known better.
They obviously need a hardware approach, i.e. JTAG/RIFF/Octoplus or replace motherboard.

Tawsif999 said:
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Click to expand...
Click to collapse
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan

jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less

Tawsif999 said:
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Click to expand...
Click to collapse
Thanks Tawsif for the good hints and links.
I don't really depend on the phone, so i will keep trying.
It's not wasted time, it's mainly learning new stuff and improving skills.
I believe, i'm not too far away and if it works, it's the best satisfaction.
If not, i bricked an old Mi 5.
All the best,
Jan