Develop Bugs

Help! I cannot unlock the bootloader on my tmo z2 force

I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid

vibraniumdroid said:
I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid
Click to expand...
Click to collapse
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei

41rw4lk said:
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224CQPCT
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 5786D2FB
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed for privacy)
(bootloader) meid:
(bootloader) date: 08-05-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4385
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.01R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g2c64ab8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Apr 20 09:21:37 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.242s

wtf xda turned some of it into emojis

Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.

41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
I have the oem unlock enabled in Dev options

41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
Also can u link the thread u were talking about.

vibraniumdroid said:
I have the oem unlock enabled in Dev options
Click to expand...
Click to collapse
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
Click to expand...
Click to collapse
thnx a lot I really appreciate the help

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Will let u know if I make any progress

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Did not work

vibraniumdroid said:
Did not work
Click to expand...
Click to collapse
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.

41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.

41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
I will try to flash twrp also I have the oem unlock switch checked in Dev options

vibraniumdroid said:
I will try to flash twrp also I have the oem unlock switch checked in Dev options
Click to expand...
Click to collapse
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Sent from my Moto Z2 Force using XDA Labs

vibraniumdroid said:
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.
Click to expand...
Click to collapse
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.

fast69mopar said:
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Click to expand...
Click to collapse
I know. As I mentioned earlier this is my second z2

41rw4lk said:
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.
Click to expand...
Click to collapse
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.

vibraniumdroid said:
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.
Click to expand...
Click to collapse
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.

41rw4lk said:
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.
Click to expand...
Click to collapse
Okay I will try tomorrow

Help with factory resetting Moto g5

I rooted my moto g5 and installed pisxel experience on it back in novemeber and now it's stopped working and won't start past the "device cant be trusted" screen. I have already emailed someone about it but I might get a quicker response on here. This is my email; (it describes what has happened)
I was just using my phone while i was coming back from a grocery store and when i got home, the screen wouldn't turn on, even when i plugged it in to charge it. I took out the battery and put it back in and tried to turn it on, I won't turn on and it will stay in the screen that says "your device has been unlocked and cant be trusted" even though it says it will boot in 5 seconds. I can get into the boot loader and do all of the options. I'm wondering if I can just factory reset it because it is an option in there but I don't want to break my phone even more if it can be salvaged. You're one of the only people out there who make sense and know what to do in a situation like this. I checked your video again and it says do not factory reset as you could lose your imei number. This is my only phone and I kinda need it to work. If you have any ideas that could help me it would be very appreciated if you can. I made a backup but I think it was lost when i changed SD cards because the one kept getting "corrupt" (This was a problem before I installed the ROM). I heard now that the official 8.1 ROM is out on moto g5s and I would like to keep my root but go to the official one. i have no problem rooting it again but I don't want to have Pisxel Experience anymore. If I have to keep it that's fine I guess. I tried to boot into recovery from boot loader but it wont get past the twrp loading screen.
If anyone can help me factory resetting this thing I would be so grateful. Also Someone will say something about me rooting and doing this to my only phone, but I was stupid and did it anyway. I know everyone says they're not responsible for bricked devices and I'm not blaming anyone. But this has happened once before and a battery removal fixed the problem, but now it wont.

shAen123 said:
I rooted my moto g5 and installed pisxel experience on it back in novemeber and now it's stopped working and won't start past the "device cant be trusted" screen. I have already emailed someone about it but I might get a quicker response on here. This is my email; (it describes what has happened)
I was just using my phone while i was coming back from a grocery store and when i got home, the screen wouldn't turn on, even when i plugged it in to charge it. I took out the battery and put it back in and tried to turn it on, I won't turn on and it will stay in the screen that says "your device has been unlocked and cant be trusted" even though it says it will boot in 5 seconds. I can get into the boot loader and do all of the options. I'm wondering if I can just factory reset it because it is an option in there but I don't want to break my phone even more if it can be salvaged. You're one of the only people out there who make sense and know what to do in a situation like this. I checked your video again and it says do not factory reset as you could lose your imei number. This is my only phone and I kinda need it to work. If you have any ideas that could help me it would be very appreciated if you can. I made a backup but I think it was lost when i changed SD cards because the one kept getting "corrupt" (This was a problem before I installed the ROM). I heard now that the official 8.1 ROM is out on moto g5s and I would like to keep my root but go to the official one. i have no problem rooting it again but I don't want to have Pisxel Experience anymore. If I have to keep it that's fine I guess. I tried to boot into recovery from boot loader but it wont get past the twrp loading screen.
If anyone can help me factory resetting this thing I would be so grateful. Also Someone will say something about me rooting and doing this to my only phone, but I was stupid and did it anyway. I know everyone says they're not responsible for bricked devices and I'm not blaming anyone. But this has happened once before and a battery removal fixed the problem, but now it wont.
Click to expand...
Click to collapse
So does your phone actually boot into the TWRP or it doesn't?
If it doesn't, download this 64bit TWRP https://androidfilehost.com/?fid=673956719939821589, copy it into the adb folder and flash it using the command below:
Code:
fastboot flash recovery name_of_file.img
Then, reboot the bootloader using command below and try to boot into the TWRP as you normally would.
Code:
fastboot reboot bootloader
If the TWRP boots, try to wipe cache and dalvik cache at first, then try to boot into the OS. If it won't help, wipe everything except system, microsd and USB-OTG (however, you will loose your data), then try to boot into the OS again.
Let me know the results.
Just few more things to note:
None of the G5s's (montana) ROMs (custom, stock, doesn't matter) won't work with G5 (cedric).
For sure, you can't wipe your IMEI just by factory resetting your phone. It may get wiped if erase modem commands are executed with broken persist or by reverting to stock using fastboot with anything 64bit installed at least once. However, there's already a fix for stock Nougat ROM, which fixes ownership of some persist files and brings back the IMEI. In case of lost IMEI, just flash this zip: https://androidfilehost.com/?fid=3700668719832240875

Andrej_SK said:
So does your phone actually boot into the TWRP or it doesn't?
If it doesn't, download this 64bit TWRP, copy it into the adb folder and flash it using the command below:
Code:
fastboot flash recovery name_of_file.img
Then, reboot the bootloader using command below and try to boot into the TWRP as you normally would.
Code:
fastboot reboot bootloader
If the TWRP boots, try to wipe cache and dalvik cache at first, then try to boot into the OS. If it won't help, wipe everything except system, microsd and USB-OTG (however, you will loose your data), then try to boot into the OS again.
Let me know the results.
Just few more things to note:
None of the G5s's (montana) ROMs (custom, stock, doesn't matter) won't work with G5 (cedric).
For sure, you can't wipe your IMEI just by factory resetting your phone. It may get wiped if erase modem commands are executed with broken persist or by reverting to stock using fastboot with anything 64bit installed at least once. However, there's already a fix for stock Nougat ROM, which fixes ownership of some persist files and brings back the IMEI. In case of lost IMEI, just flash this zip:
Click to expand...
Click to collapse
Yeah sorry if the email thing was confusing, after I read it over a few times it didnt make too much sense. I cannot get into TWRP, also adb is not working for me. I installed it and ran the abd thing and it just opened, spit a lot of code and then quit. I tired to follow the picture guide to get the device n stuff but the phone wont show in device manager. Is there a way I can pm you on discord or something? I think I can be more helpful on there and we can talk at the same time.
EDIT#1: Never mind, i got into adb, i just forgot that you had to do the command window thing.
EDIT#2: I did the command and it sits at waiting for device. It wont go past that, I think i should install moto drivers because i reset my pc which got rid of them. Ill update once done.

shAen123 said:
Yeah sorry if the email thing was confusing, after I read it over a few times it didnt make too much sense. I cannot get into TWRP, also adb is not working for me. I installed it and ran the abd thing and it just opened, spit a lot of code and then quit. I tired to follow the picture guide to get the device n stuff but the phone wont show in device manager. Is there a way I can pm you on discord or something? I think I can be more helpful on there and we can talk at the same time.
Click to expand...
Click to collapse
Where's your adb folder located?
Maybe I might help you using remote access (TeamViewer) tomorrow (it's 11:30 p.m. here actually), if things will be more broken than they seems to be right now.
EDIT: Remember that while the phone is in the bootloader menu, the main word of the each command is "fastboot" (e.g. "fastboot flash...", "fastboot boot..."), not "adb".

Andrej_SK said:
Where's your adb folder located?
Maybe I might help you using remote access (TeamViewer) tomorrow (it's 11:30 p.m. here actually), if things will be more broken than they seems to be right now.
Click to expand...
Click to collapse
Its okay i got it working, heres what happened
PS C:\adb> fastboot flash recovery twrp-3.2.1-0-cedric.img
target reported max download size of 536870912 bytes
sending 'recovery' (14660 KB)...
OKAY [ 0.465s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.564s]
finished. total time: 1.030s
PS C:\adb> fastboot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
PS C:\adb>
I have a feeling that the reboot didnt work, I tried to boot into twrp and it still is being stuck on the loading screen (teamwin)

shAen123 said:
Its okay i got it working, heres what happened
PS C:\adb> fastboot flash recovery twrp-3.2.1-0-cedric.img
target reported max download size of 536870912 bytes
sending 'recovery' (14660 KB)...
OKAY [ 0.465s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.564s]
finished. total time: 1.030s
PS C:\adb> fastboot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
PS C:\adb>
I have a feeling that the reboot didnt work, I tried to boot into twrp and it still is being stuck on the loading screen (teamwin)
Click to expand...
Click to collapse
The only one solutions seems to be flashing the correct stock FW right now, if even TWRP refuses to boot.
Btw, sorry for my mistake, but even the correct command is "fastboot reboot-bootloader" (missing dash between "reboot" and "bootloader" words), I don't think it's gonna help.

Andrej_SK said:
The only one solutions seems to be flashing the correct stock FW right now, if even TWRP refuses to boot.
Click to expand...
Click to collapse
So if i go into the bootloader and factory it, would it erase the imei number? if twrp flashed properly i should be okay? I can try and boot into os normally again
Oops, I didnt see the edit in time Ill do that
I think it worked, screen went black, then back into bootloader, adb said okay. Ill try and boot into twrp

shAen123 said:
So if i go into the bootloader and factory it, would it erase the imei number? if twrp flashed properly i should be okay? I can try and boot into os normally again
Click to expand...
Click to collapse
Yes, give a boot into the OS a try at first.
Your IMEI will get wiped if you decide to flash stock ROM, but fortunately, there's a fix. Just flash stock Nougat (rather don't flash bootloader and gpt), boot into the OS, install TWRP, flash 2 zips (links below) and boot into the OS again.
https://androidfilehost.com/?fid=3700668719832240875 fixes ownership of some persist files and brings IMEI back
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ use the 6.0 version, avoids bootloop on stock ROM

Andrej_SK said:
Yes, give a boot into the OS a try at first.
Your IMEI will get wiped if you decide to flash stock ROM, but fortunately, there's a fix. Just flash stock Nougat (rather don't flash bootloader and gpt), install TWRP and flash 2 zips (links below):
fixes ownership of some persist files and brings IMEI back
use the 6.0 version, avoids bootloop on stock ROM
Click to expand...
Click to collapse
okay, also im kind of a "noob" at this, correct me if im wrong but in the bootloader menu there is an option called factory mode. My guess is that it factory resets the phone. Is this what you mean by "flashing the stock rom"?
(I know how to do things, its just terms I'm not good at)

shAen123 said:
okay, also im kind of a "noob" at this, correct me if im wrong but in the bootloader menu there is an option called factory mode. My guess is that it factory resets the phone. Is this what you mean by "flashing the stock rom"?
Click to expand...
Click to collapse
Nope. You have to flash stock ROM using fastboot commands. Type "fastboot getvar all" while yours phone is in the bootloader mode and copy the entire output into your next reply. I'll have a look at it in the morning (it's halfnight right now here, in the Slovakia) and send you link for an appropriate version of stock ROM which won't brick your phone.

Andrej_SK said:
Nope. You have to flash stock ROM using fastboot commands. Type "fastboot getvar all" while yours phone is in the bootloader mode and copy the entire output into your next reply. I'll have a look at it in the morning (it's halfnight right now) and send you link for an appropriate version of stock ROM which won't brick your phone.
Click to expand...
Click to collapse
okay man will do, thanks for your help tonight, heres the stuff;
PS C:\adb> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.25
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3223TPZK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x81
(bootloader) uid: A33500F600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351871081161092
(bootloader) meid:
(bootloader) date: 04-17-2017
(bootloader) sku: XT1670
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:23 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPPS25.
(bootloader) ro.build.fingerprint[1]: 137-93-14/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.351.21.cedric.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8937_22.29.02.56.01R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4a0c859-0002
(bootloader) kernel.version[1]: 5-g7f05384 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jun
(bootloader) kernel.version[3]: 19 06:51:25 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.25-0-g0cc8007
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=87b19b9-dirty
(bootloader) devcfg.git: git=87b19b9-dirty
(bootloader) keymaster.git: git=87b19b9-dirty
(bootloader) cmnlib.git: git=87b19b9-dirty
(bootloader) cmnlib64.git: git=87b19b9-dirty
(bootloader) prov.git: git=MBM-NG-VB8.0C-0-g283f623
(bootloader) aboot.git: git=MBM-NG-VB8.25-0-gb74f6bf
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: bwaca
all: listed above
finished. total time: 0.071s
Again, thanks for the help

shAen123 said:
okay man will do, thanks for your help tonight, heres the stuff;
PS C:\adb> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.25
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3223TPZK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x81
(bootloader) uid: A33500F600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351871081161092
(bootloader) meid:
(bootloader) date: 04-17-2017
(bootloader) sku: XT1670
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:23 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPPS25.
(bootloader) ro.build.fingerprint[1]: 137-93-14/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.351.21.cedric.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8937_22.29.02.56.01R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4a0c859-0002
(bootloader) kernel.version[1]: 5-g7f05384 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jun
(bootloader) kernel.version[3]: 19 06:51:25 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.25-0-g0cc8007
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=87b19b9-dirty
(bootloader) devcfg.git: git=87b19b9-dirty
(bootloader) keymaster.git: git=87b19b9-dirty
(bootloader) cmnlib.git: git=87b19b9-dirty
(bootloader) cmnlib64.git: git=87b19b9-dirty
(bootloader) prov.git: git=MBM-NG-VB8.0C-0-g283f623
(bootloader) aboot.git: git=MBM-NG-VB8.25-0-gb74f6bf
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: bwaca
all: listed above
finished. total time: 0.071s
Again, thanks for the help
Click to expand...
Click to collapse
As you have the latest Nougat firmware (NPPS25.137-93-14), use Lenovo Moto Smart Assistant (Rescue function, in dropdown menu choose "XT1670") to download it. Make sure, it offers you NPPS25.137-93-14 firmware to download, not an older one, which might brick your phone. If it offers you Oreo firmware (build number starts with letter "O" instead of "N"), you can use it to repair your phone too, but if you want to stay with Nougat one, let me know and I'll upload NPPS25.137-93-14 (which I downloaded through LMSA earlier) somewhere - however, it will take a "while" because my upload speed is quite poor.

Andrej_SK said:
As you have the latest Nougat firmware (NPPS25.137-93-14), use Lenovo Moto Smart Assistant (Rescue function, in dropdown menu choose "XT1670") to download it. Make sure, it offers you NPPS25.137-93-14 firmware to download, not an older one, which might brick your phone. If it offers you Oreo firmware (build number starts with letter "O" instead of "N"), you can use it to repair your phone too, but if you want to stay with Nougat one, let me know and I'll upload NPPS25.137-93-14 (which I downloaded through LMSA earlier) somewhere - however, it will take a "while" because my upload speed is quite poor.
Click to expand...
Click to collapse
Thank you man, Where do I go to get the Lenovo Moto Smart Assistant?(If I'm guessing right it is an online thing) If it has an official Oreo build for the g5, I'd like to use that because Oreo is great. Also is there a way to boot back into what I have now because I need to save some game stuff to their cloud services.
Oh and another thing, in the bootloader there is an option called factory mode. From what I've heard from you and what I know, that option factory resets the phone and I wont get my imei number erased? Because if that's an easier option to do, then install the official updates to Oreo from the android updater or whatever, I might want to do that instead.
And I'll stay with the Nougat for now I guess and I can update it myself later if I want.
EDIT#1: Okay so I went to the Lenovo site and tried to download the Smart Assistant but it downloaded a .7z file? I'm kinda confused about that
EDIT#2: Nevermind, since I reset my pc I never got winzip/rar again (Whups)
EDIT#3: Okay! So I got the rescue working after a few tried as it wouldn't do the target image thing. It's showing me CEDRIC_OPP28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, is this the right image? I know it's oreo because if the O, also I think its newer and it wont work? because the nougat is 25.137-93-13 and this is only 28.85-13. But it's showing that I could download it and use that. I think they would be right and I can try it
EDIT#4: Okay so I did some searching myself. Someone did it and it worked fine, their device structure is XT1676 but still had the name npps as me, and updated to the opp28.85-13. he was having problems installing and he said it wouldn't. People suggested to take out the sd card, he did it and the update worked properly because he had 2 partitions. One adopted memory and one portable. I did the same thing with my sd card and I think i should follow this, it is on the official lenovo forums so I think I will be safe.

Its okay man, I figured it out and I have my backup, so all my games are here and I'm on official 8.1 with a few system updates waiting for me lol

shAen123 said:
Thank you man, Where do I go to get the Lenovo Moto Smart Assistant?(If I'm guessing right it is an online thing) If it has an official Oreo build for the g5, I'd like to use that because Oreo is great. Also is there a way to boot back into what I have now because I need to save some game stuff to their cloud services.
Oh and another thing, in the bootloader there is an option called factory mode. From what I've heard from you and what I know, that option factory resets the phone and I wont get my imei number erased? Because if that's an easier option to do, then install the official updates to Oreo from the android updater or whatever, I might want to do that instead.
And I'll stay with the Nougat for now I guess and I can update it myself later if I want.
EDIT#1: Okay so I went to the Lenovo site and tried to download the Smart Assistant but it downloaded a .7z file? I'm kinda confused about that
EDIT#2: Nevermind, since I reset my pc I never got winzip/rar again (Whups)
EDIT#3: Okay! So I got the rescue working after a few tried as it wouldn't do the target image thing. It's showing me CEDRIC_OPP28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, is this the right image? I know it's oreo because if the O, also I think its newer and it wont work? because the nougat is 25.137-93-13 and this is only 28.85-13. But it's showing that I could download it and use that. I think they would be right and I can try it
EDIT#4: Okay so I did some searching myself. Someone did it and it worked fine, their device structure is XT1676 but still had the name npps as me, and updated to the opp28.85-13. he was having problems installing and he said it wouldn't. People suggested to take out the sd card, he did it and the update worked properly because he had 2 partitions. One adopted memory and one portable. I did the same thing with my sd card and I think i should follow this, it is on the official lenovo forums so I think I will be safe.
Click to expand...
Click to collapse
You can download LMSA from this site https://support.lenovo.com/sk/sk/downloads/ds101291.
"Factory Mode" doesn't factory reset your phone or install stock ROM at all. It just runs CQATest app and deny access to the cellular network (even it asks for PIN at boot, you will get "No signal" in the notification panel). After the normal reboot, CQATest app disappears and the cellular network works.
Oreo is newer than Nougat, so that's why there wasn't any problem flashing it. However, next time, if you're not sure which firmware is newer while comparing by build numbers (e.g. you're comparing two Nougat builds, each with different build number), look at the security patch.
Most probably, the problem what you've been reading about (updating while sdcard inserted) was made by the person, who just installed the update with his sdcard formatted as an adoptable memory (that means the sdcard expands the internal storage and behave as its part).
shAen123 said:
Its okay man, I figured it out and I have my backup, so all my games are here and I'm on official 8.1 with a few system updates waiting for me lol
Click to expand...
Click to collapse
So is your problem fully fixed now?

Andrej_SK said:
You can download LMSA from this site https://support.lenovo.com/sk/sk/downloads/ds101291.
"Factory Mode" doesn't factory reset your phone or install stock ROM at all. It just runs CQATest app and deny access to the cellular network (even it asks for PIN at boot, you will get "No signal" in the notification panel). After the normal reboot, CQATest app disappears and the cellular network works.
Oreo is newer than Nougat, so that's why there wasn't any problem flashing it. However, next time, if you're not sure which firmware is newer while comparing by build numbers (e.g. you're comparing two Nougat builds, each with different build number), look at the security patch.
Most probably, the problem what you've been reading about (updating while sdcard inserted) was made by the person, who just installed the update with his sdcard formatted as an adoptable memory (that means the sdcard expands the internal storage and behave as its part).
So is your problem fully fixed now?
Click to expand...
Click to collapse
Yes it is, I was able to boot and go through an update to give me the lastest security patch. After some downloading/backup retrieving my phone is working normally and I have my iemi and stuff. I might go and root it again at a later date but for now its going to be completely stock. Sorry for the long wait

How to put the Moto Z2 Force (XT1789-05) in Qualcomm 9008

Hello, my Moto Z2 Force, XT1789-5, is with android 8 and I already tried methods to put it in Qualcomm mode, but I did not succeed.
Every time I execute options to activate the mode, it simply restarts and enters the system. As the system is bricked, I can not use the device, the bootloader does not unlock.
I would like to know how it is possible to put it in the Qualcomm 9008 mode?

NewPoow said:
Hello, my Moto Z2 Force, XT1789-5, is with android 8 and I already tried methods to put it in Qualcomm mode, but I did not succeed.
Every time I execute options to activate the mode, it simply restarts and enters the system. As the system is bricked, I can not use the device, the bootloader does not unlock.
I would like to know how it is possible to put it in the Qualcomm 9008 mode?
Click to expand...
Click to collapse
What commands are you running? Does it boot to OS or not? (You said it enters system, then say it's bricked, kind of confusing) Can you enter the bootloader?

Excuse me.
My device is with bricked software after trying a stock recovery, the wifi and mobile network, do not work.
Another problem is that the bootloader is locked.
I access the bootloader, I can send commands using "fastboot.exe", but it does not let you restore a rom because the OEM is locked.
I try to unlock OEM but a message appears asking to enable unlock in: Settings> Development> Unlock OEM.
I do not have access to this option, it always gets gray.
- What commands are you running?
Using Fastboot_edl-v2: "fastboot.exe reboot-edl"
I also used the QFIL, with the device in Qualcomm 9092 mode, so that it can enter automatically.
- Does it boot to OS or not? (You said it enters system, then say it's bricked, kind of confusing)
I enter the OS
- Can you enter the bootloader?
Yes
Thank you

NewPoow said:
Excuse me.
My device is with bricked software after trying a stock recovery, the wifi and mobile network, do not work.
Another problem is that the bootloader is locked.
I access the bootloader, I can send commands using "fastboot.exe", but it does not let you restore a rom because the OEM is locked.
I try to unlock OEM but a message appears asking to enable unlock in: Settings> Development> Unlock OEM.
I do not have access to this option, it always gets gray.
- What commands are you running?
Using Fastboot_edl-v2: "fastboot.exe reboot-edl"
I also used the QFIL, with the device in Qualcomm 9092 mode, so that it can enter automatically.
- Does it boot to OS or not? (You said it enters system, then say it's bricked, kind of confusing)
I enter the OS
- Can you enter the bootloader?
Yes
Thank you
Click to expand...
Click to collapse
If you can enter the bootloader then issue the command 'fastboot oem blankflash' w/o quotes. That will get you to edl mode, optionally if you can boot to system and have adb enabled, you can issue 'adb reboot edl' w/o quotes. Don't use an edl modified fastboot either, just regular fastboot that you use to flash with is fine.

41rw4lk said:
If you can enter the bootloader then issue the command 'fastboot oem blankflash' w/o quotes. That will get you to edl mode, optionally if you can boot to system and have adb enabled, you can issue 'adb reboot edl' w/o quotes. Don't use an edl modified fastboot either, just regular fastboot that you use to flash with is fine.
Click to expand...
Click to collapse
When I try this command, I get this output:
Code:
C:\adb>fastboot.exe oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: -0.000s
C:\adb>

NewPoow said:
When I try this command, I get this output:
Code:
C:\adb>fastboot.exe oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: -0.000s
C:\adb>
Click to expand...
Click to collapse
I'm not sure about what versions of fastboot or adb you're using, so grab the flashall utilities zip from here, unzip it to its own folder, open the folder, hold shift + right click to open a command window here, then try to issue the command. What about adb? Is it enabled? Can you issue that command?

41rw4lk said:
I'm not sure about what versions of fastboot or adb you're using, so grab the flashall utilities zip from here, unzip it to its own folder, open the folder, hold shift + right click to open a command window here, then try to issue the command. What about adb? Is it enabled? Can you issue that command?
Click to expand...
Click to collapse
When I run the command to check a version I get:
Code:
C:\adb>fastboot.exe --version
fastboot version 0.0.1-4500957
Installed as C:\adb\fastboot.exe
I already tried other versions, and it's always the same, the error persists.
- What about adb? Is it enabled? Can you issue that command?
I can not use it, just restart the device.

Were you on a custom rom before? How did you get to the state you're in? Can you run 'fastboot getvar all' and post the output -minus personal info like imei? Might be obvious, but have you tried to factory reset?
The command restricted is a little weird, usually you just get a straight up permission denied. Have you tried flashing the latest flashall for your variant? What about the lenovo smart assistant tool, have you tried to use it to flash a clean build?

41rw4lk said:
Were you on a custom rom before? How did you get to the state you're in? Can you run 'fastboot getvar all' and post the output -minus personal info like imei? Might be obvious, but have you tried to factory reset?
The command restricted is a little weird, usually you just get a straight up permission denied. Have you tried flashing the latest flashall for your variant? What about the lenovo smart assistant tool, have you tried to use it to flash a clean build?
Click to expand...
Click to collapse
I bought the device of a friend, used.
The device was locked, original, netflix did not work, I installed different versions and always the same error message.
Resolving to install another ROM to see if the problem would disappear, was when I unlocked the bootloader, and installed a downloaded version as taught in this post. I downloaded the RETAIL version and installed TWRP, so far everything works.
The problem persisted, resolving to return to stock and send for assistance, here the problem occurred:
- I did not notice my variant.
- I used RETAIL itself to lock and lock the bootloader.
- The TWRP's gone, normal.
- Flash failed to appear.
The wifi was corrupted, it only worked bluetooth, the mobile network also stopped.
Trying to solve the problem:
- I tried to enable the OEM through development.
- always gray, I waited 7 days with the appliance on.
- I tried to use the internet via bluetooth to see if I enabled OEM, nothing.
- I added my Google account, nothing.
- I tried RSD Lite, nothing.
- I tried Lenovo Moto Smart Assistant, it displays "Failed to match the connected device. Please plug it out, and try again." it's nothing.
- reset factory reset, worsened, the device is now disabled with DEBUG in the FRP screen, and it does not go away.
When executing the "getvar all" command:
Code:
C:\adb>fastboot.exe getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (4)
(bootloader) serialno: 0043906802
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 77A0C58E
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 02-13-2018
(bootloader) sku: XT1789-05
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4118
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-15/14:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.331.14.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gb0e8652 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 28 23:46:14 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-180828
(bootloader) git:tz: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:storsec: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:prov: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.158s
I do not know what to try anymore.

This is kind of why it's advised not to relock the bootloader, when things go wrong it leaves you no wiggle room to flash anything. I would remove any screenlocks then do a 'fastboot -w' to format user data, 'fastboot reboot recovery' and do another factory reset. Reboot, connect to internet, sign into google and see if oem unlocking comes back. If not, make sure adb debugging is on and try to issue 'adb reboot edl'. If that doesn't work, make sure you have the latest flashall for your variant (look on the phone by the charge port). Try to flash the flashall, if no go, at least see if you can flash the gpt.bin and the bootloader. Whether it works or not, 'fastboot reboot bootloader' and try to issue the 'fastboot oem blankflash' command again.
If all else fails, the only thing I can think of is to find a way to brick the phone so it throws itself into 9008, then you can at least blankflash and get back to a clean slate. Between the hybrid rom and locked bootloader, you're up against it. Maybe someone else around here can chime in with some suggestions, but this scenario is difficult to recover from.

41rw4lk said:
This is kind of why it's advised not to relock the bootloader, when things go wrong it leaves you no wiggle room to flash anything. I would remove any screenlocks then do a 'fastboot -w' to format user data, 'fastboot reboot recovery' and do another factory reset. Reboot, connect to internet, sign into google and see if oem unlocking comes back. If not, make sure adb debugging is on and try to issue 'adb reboot edl'. If that doesn't work, make sure you have the latest flashall for your variant (look on the phone by the charge port). Try to flash the flashall, if no go, at least see if you can flash the gpt.bin and the bootloader. Whether it works or not, 'fastboot reboot bootloader' and try to issue the 'fastboot oem blankflash' command again.
If all else fails, the only thing I can think of is to find a way to brick the phone so it throws itself into 9008, then you can at least blankflash and get back to a clean slate. Between the hybrid rom and locked bootloader, you're up against it. Maybe someone else around here can chime in with some suggestions, but this scenario is difficult to recover from.
Click to expand...
Click to collapse
The alternatives you said have already been tried.
I wanted to put it in Qualcomm 9008 mode, but I do not know how.
Thanks for the help here.

NewPoow said:
The alternatives you said have already been tried.
I wanted to put it in Qualcomm 9008 mode, but I do not know how.
Thanks for the help here.
Click to expand...
Click to collapse
I have the same problem. I've tried erything, but no sucess. The only solution is wait for next update and flash it.
Amigo, estou com o mesmo problema, alias, pior, porque no meu parou de funcionar o wi-fi, bluetooth e rede de celular. O sistema sobe, porém não consigo fazer absolutamente nada. Já estou pesquisando há um mês e tentei várias coisas. Você está tentando fazer o blankflash, porém aconselho a não fazer, pode danificar permanentemente. A solução é aguardar a próxima atualização, que pode ser o Android Pie ou apenas mais uma atualização de segurança, baixar e fazer o flash em modo fastboot.

andrecesarvieira said:
I have the same problem. I've tried erything, but no sucess. The only solution is wait for next update and flash it.
Amigo, estou com o mesmo problema, alias, pior, porque no meu parou de funcionar o wi-fi, bluetooth e rede de celular. O sistema sobe, porém não consigo fazer absolutamente nada. Já estou pesquisando há um mês e tentei várias coisas. Você está tentando fazer o blankflash, porém aconselho a não fazer, pode danificar permanentemente. A solução é aguardar a próxima atualização, que pode ser o Android Pie ou apenas mais uma atualização de segurança, baixar e fazer o flash em modo fastboot.
Click to expand...
Click to collapse
Do you have any OTA updates? because mine is in an OPXS27.109-34-15 version.
Flash through fastboot does not work with OPXS27.109-34-17

NewPoow said:
Do you have any OTA updates? because mine is in an OPXS27.109-34-15 version.
Flash through fastboot does not work with OPXS27.109-34-17
Click to expand...
Click to collapse
try this
https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/

41rw4lk said:
If you can enter the bootloader then issue the command 'fastboot oem blankflash' w/o quotes. That will get you to edl mode, optionally if you can boot to system and have adb enabled, you can issue 'adb reboot edl' w/o quotes. Don't use an edl modified fastboot either, just regular fastboot that you use to flash with is fine.
Click to expand...
Click to collapse
thank you for the code,i successed puted into edl mode,A new problem has arisen.
[ 0.001] Detecting device
[ 34.008] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.009] qboot version 3.85
[ 34.009] name = "\\.\COM10",
[ 34.009] flags = "0x64",
[ 34.009] addr = "0x28FD74",
[ 34.009] api.bnr = "0x5B2898",
is this driver problem?this is my thread.
https://forum.xda-developers.com/z2-force/help/help-blank-flash-failed-xt1789-3-t4011777

OLDWhite said:
thank you for the code,i successed puted into edl mode,A new problem has arisen.
[ 0.001] Detecting device
[ 34.008] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.009] qboot version 3.85
[ 34.009] name = "\\.\COM10",
[ 34.009] flags = "0x64",
[ 34.009] addr = "0x28FD74",
[ 34.009] api.bnr = "0x5B2898",
is this driver problem?this is my thread.
https://forum.xda-developers.com/z2-force/help/help-blank-flash-failed-xt1789-3-t4011777
Click to expand...
Click to collapse
Your log snippet says IO error, so either you need the qualcomm diag drivers, or you need to use another port on your pc. Win 10 can be finicky since you have to give special permission to everything, so use win 7 if possible. It wouldn't hurt to make sure you're using up to date adb/fastboot files either.

OLDWhite said:
thank you for the code,i successed puted into edl mode,A new problem has arisen.
[ 0.001] Detecting device
[ 34.008] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.009] qboot version 3.85
[ 34.009] name = "\.\COM10",
[ 34.009] flags = "0x64",
[ 34.009] addr = "0x28FD74",
[ 34.009] api.bnr = "0x5B2898",
is this driver problem?this is my thread.
https://forum.xda-developers.com/z2-force/help/help-blank-flash-failed-xt1789-3-t4011777
Click to expand...
Click to collapse
Make sure u r using USB 2.0 ports.

Moto G5s Plus stuck in boot loop - repair or data rescue

Hi,
My personal phone is a Moto G5s Plus, European dual sim version (model "sanders XT1805", retail, unbranded, not from a network) with the latest version of Android available (I think it's 8.0 or 8.1, but not sure). It has rebooted today on its own while being used, and is now stuck in a boot loop. I am trying to either fix the boot loop, or recover personal data from the device (possibly destructively, but I would like to prevent that).
Here are things I have tried:
- I have checked that it's not the contact on the power button stuck in the on position that creates the boot loop. I have experienced this with a previous phone. Cleaning the contact with IPA and engaging it a few times helped this issue.
- I have tried entering recovery mode and formatting the cache partition. This hasn't helped.
I am a developer, but I don't know that much about Android devices. This phone has the stock boot loader and OS image. Is it possible to hook it up via adb, and possibly browse the file system or do something else to debug and fix the boot loop?
The device does boot into recovery mode. Recovery mode contains options for applying an update from an SD card, and via ADB via sideloading. Could this be used to fix this situation somehow?
The battery in this device is somewhat bad. Sometimes it would turn off when on battery power, and not hooked up to a charger, if the battery was on 30%, and recently it did once when it was on 60%. The battery is a 3.8V Motorola HG30. Could it be that the battery is shot, and when the device boots up, after a few seconds of boot time the SoC requests higher current, and then the battery cannot deliver the required voltage, and the device browns out and resets? I tried booting with a charger hooked up (which also supports QC 3.0) but that didn't help.
The boot loader also has the following two options: "BP Tools" and "QCom" but I don't know what they do. Both of them reboot the device, it sits in the boot screen for a longer time and then enters the boot loop again. There is also an option in the boot loader for turning on "tool mode" which sounds like it might be a way of enabling some form of debug tools.
The device contains important personal information that I need to recover. I am very good with micro-soldering (I can solder 01005 without magnification), and I have the right fluxes and ball kits, although at the moment I don't have a hot air station but could possibly get one. In case such physical access could help in rooting this device, how would I do this?
Finally, I am aware that the emmc chip can be read by a Beaglebone Black, but I'm hoping it will not come to that. If I do that, will the file system be encrypted in some way?
I would appreciate any suggestions.
Thanks

One thing... this is my first post here, so if I posted this in the wrong forum, or did something wrong, please let me know! I would like to do things adhering to the rules of this forum. Thank you!

One thing I have tried since is to try to hook up the device via adb, but it only allows sideloading, and it doesn't open a tcp port, so debugging isn't possible.

Researching the issue - Moto G5S Plus boot loop
I thought I'd post what I learn from the forum here and from other places... information that might be relevant to figuring out this issue, plus questions I have regarding those options:
I have tried to let the device discharge completely (I left it running in the boot loop), then I charged it up to 100%, but that did not help.
If your Moto will not boot, and your PC shows it as Qualcomm HS-USB QDLoader 9008 or Qualcomm QHSUSB_Bulk - but if I go into FastBoot mode (by holding power and volume down), and connect via USB, then the device does not show up in Windows 10 at all. If I tell FastBoot to go to Recovery Mode and in there select to download update via ADB, Windows 10 finds the phone and it shows up in the Device Manager under "Universal Serial Bus devices" as "Moto G (5S) Plus". Inside Properties for that item, the "Device description" field says "ADB Device". However, my PC doesn't have fastboot installed, or the Motorola drivers.
Motorola Drivers
How to back up mmcblk0 using terminal - I would like to do that, however I cannot boot the device at all into something that shows a terminal. Also the device is not rooted. Is it possible to boot from SD Card to be able to do this?
How to Unbrick (Debrick) Qualcomm Android Devices Using your SD Card - ArykSTORE - this allows to boot the device from SD card. I am not sure if it will let me boot my device without first unlocking the bootloader. However, the SD card created in this image puts the phone into download mode and I wouldn't like to do that. If the SD Card image boots up, and is able to enter download mode, then I assume it can access mmcblk0. Can I create an image that I can use to run dd in order to image mmcblk0 onto the file system of the SD card? (phone is 32 GB, SD card is 64 GB, so there should be space).
Use Lenovo Motorola Smart Assistant and Skip Data Wipe - this is said to not always work. I am scared to flash the device (even if it says it won't wipe) before I back up mmcblk0. From the post: "Note: This is not guaranteed to work"
[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot - describes how to clear the misc partition using TRWP - is the misc partition different from the cache partition? Could this help with the boot loop? Note that my recovery mode has no option to "boot normally". Fastboot has an option called "START", but using that just enters the boot loop again.
Hacking Hardware With A $10 SD Card Reader (pdf) - worst case scenario, I could try and modify the hardware to use this method of recovering data from eMMC. It uses an SD Card Reader or a BeagleBone Black (use BBB if you also want to read the mmcblkXbootY partitions. Not sure if that's necessary). One of the things I'd like to recover is URLs of tabs open in Google Chrome. Will they be on a boot partition, or the "normal" partitions available via SD Card interface?
Laptop eMMC Data Recovery on a Budget - Andy's Boring Job - shows how to recover data off an eMMC chip. It recommends using a board view (.brd) file to search for signal hook up points. Does anyone have a board view file for the Moto G5S Plus model XT1805?
Stuff I've read that didn't give me any new ideas on how to fix my issue:
Guide: Flashing Motorola Firmware
Using Mfastboot.exe to Flash a Motorola device
[GUIDE][FAQ][KK] How to Root, Boot Unlock & More
RSD Lite
How to use RSD Lite
[Guide]Un/locking Motorola Bootloader - this describes how to get a bootloader unlock code from Motorola via the Official Motorola Bootloader Unlocker Site
Btw if you read this sd_shadow thanks a lot for all the guides. You're a real hero :good::good::good:

@sd_shadow in one of your threads you mentioned one could ping you with issues with debricking Moto devices, so I was wondering if you'd be kind enough to chime in? I'm trying to recover data from this (stock) G5S Plus, and then debrick it. Thanks.

cheater00 said:
@sd_shadow in one of your threads you mentioned one could ping you with issues with debricking Moto devices, so I was wondering if you'd be kind enough to chime in? I'm trying to recover data from this (stock) G5S Plus, and then debrick it. Thanks.
Click to expand...
Click to collapse
Trying to backup data from a locked bootloader device with out usb debugging enabled, is next to impossible, if device will not boot.
Very possible that the battery has failed.
Have you tried a different charger and usb cable?
While it's in fastboot/bootloader mode, connect wall charger and select power off in fastboot options
Does it show charging screen?

sd_shadow said:
Trying to backup data from a locked bootloader device with out usb debugging enabled, is next to impossible, if device will not boot.
Very possible that the battery has failed.
Have you tried a different charger and usb cable?
While it's in fastboot/bootloader mode, connect wall charger and select power off in fastboot options
Does it show charging screen?
Click to expand...
Click to collapse
Thanks for your quick reply. Yes, charging screen is visible. I have been able to charge up to 100%. I have bought a new usb cable from a very good brand and tried several chargers, but all of them do charge the phone, and the phone does recognize QuickCharge 3.0.

cheater00 said:
Hi,
My personal phone is a Moto G5s Plus, European dual sim version (model "sanders XT1805", retail, unbranded, not from a network) with the latest version of Android available (I think it's 8.0 or 8.1, but not sure). It has rebooted today on its own while being used, and is now stuck in a boot loop. I am trying to either fix the boot loop, or recover personal data from the device (possibly destructively, but I would like to prevent that).
Here are things I have tried:
- I have checked that it's not the contact on the power button stuck in the on position that creates the boot loop. I have experienced this with a previous phone. Cleaning the contact with IPA and engaging it a few times helped this issue.
- I have tried entering recovery mode and formatting the cache partition. This hasn't helped.
I am a developer, but I don't know that much about Android devices. This phone has the stock boot loader and OS image. Is it possible to hook it up via adb, and possibly browse the file system or do something else to debug and fix the boot loop?
The device does boot into recovery mode. Recovery mode contains options for applying an update from an SD card, and via ADB via sideloading. Could this be used to fix this situation somehow?
Click to expand...
Click to collapse
I don't think so, Moto updates only update, they don't work for same version they would install.
There would have to be an update for your current version, then you need a copy of it.
Same Model and software channel.
The battery in this device is somewhat bad. Sometimes it would turn off when on battery power, and not hooked up to a charger, if the battery was on 30%, and recently it did once when it was on 60%. The battery is a 3.8V Motorola HG30. Could it be that the battery is shot, and when the device boots up, after a few seconds of boot time the SoC requests higher current, and then the battery cannot deliver the required voltage, and the device browns out and resets? I tried booting with a charger hooked up (which also supports QC 3.0) but that didn't help.
The boot loader also has the following two options: "BP Tools" and "QCom" but I don't know what they do. Both of them reboot the device, it sits in the boot screen for a longer time and then enters the boot loop again. There is also an option in the boot loader for turning on "tool mode" which sounds like it might be a way of enabling some form of debug tools.
Click to expand...
Click to collapse
There is no way to use those modes that I know of.
The device contains important personal information that I need to recover. I am very good with micro-soldering (I can solder 01005 without magnification), and I have the right fluxes and ball kits, although at the moment I don't have a hot air station but could possibly get one. In case such physical access could help in rooting this device, how would I do this?
Click to expand...
Click to collapse
I haven't heard of any modern Motorola devices being rooted with a Locked Bootloader.
Finally, I am aware that the emmc chip can be read by a Beaglebone Black, but I'm hoping it will not come to that. If I do that, will the file system be encrypted in some way?
Click to expand...
Click to collapse
I have no idea.
---------- Post added at 07:04 PM ---------- Previous post was at 06:23 PM ----------
cheater00 said:
I thought I'd post what I learn from the forum here and from other places... information that might be relevant to figuring out this issue, plus questions I have regarding those options:
I have tried to let the device discharge completely (I left it running in the boot loop), then I charged it up to 100%, but that did not help.
If your Moto will not boot, and your PC shows it as Qualcomm HS-USB QDLoader 9008 or Qualcomm QHSUSB_Bulk - but if I go into FastBoot mode (by holding power and volume down), and connect via USB, then the device does not show up in Windows 10 at all. If I tell FastBoot to go to Recovery Mode and in there select to download update via ADB, Windows 10 finds the phone and it shows up in the Device Manager under "Universal Serial Bus devices" as "Moto G (5S) Plus". Inside Properties for that item, the "Device description" field says "ADB Device". However, my PC doesn't have fastboot installed, or the Motorola drivers.
Click to expand...
Click to collapse
If it boots to fastboot mode it is not in EDL mode.
Motorola Drivers
How to back up mmcblk0 using terminal - I would like to do that, however I cannot boot the device at all into something that shows a terminal. Also the device is not rooted. Is it possible to boot from SD Card to be able to do this?
Click to expand...
Click to collapse
Terminal is an app you would install, the whole backup process requires the device can boot normally.
How to Unbrick (Debrick) Qualcomm Android Devices Using your SD Card - ArykSTORE - this allows to boot the device from SD card. I am not sure if it will let me boot my device without first unlocking the bootloader. However, the SD card created in this image puts the phone into download mode and I wouldn't like to do that. If the SD Card image boots up, and is able to enter download mode, then I assume it can access mmcblk0. Can I create an image that I can use to run dd in order to image mmcblk0 onto the file system of the SD card? (phone is 32 GB, SD card is 64 GB, so there should be space).
Click to expand...
Click to collapse
As the device cannot boot normally, someone else with same model would have to create an loader.img
Flashing a full mmcblk0.img would likely overwrite userdata.
Normally after flashing a loader.img, flashing stock firmware is necessary before the device will boot normally.
Use Lenovo Motorola Smart Assistant and Skip Data Wipe - this is said to not always work. I am scared to flash the device (even if it says it won't wipe) before I back up mmcblk0. From the post: "Note: This is not guaranteed to work"
Click to expand...
Click to collapse
I believe this method only works with an unlocked bootloader, I haven't had time to thoroughly tests method.
[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot - describes how to clear the misc partition using TRWP - is the misc partition different from the cache partition? Could this help with the boot loop? Note that my recovery mode has no option to "boot normally". Fastboot has an option called "START", but using that just enters the boot loop again.
Click to expand...
Click to collapse
Most moto devices no longer have a real cache, to was removed with the a/b system partition change from a single system partition.
Misc is used by recovery.
Hacking Hardware With A $10 SD Card Reader (pdf) - worst case scenario, I could try and modify the hardware to use this method of recovering data from eMMC. It uses an SD Card Reader or a BeagleBone Black (use BBB if you also want to read the mmcblkXbootY partitions. Not sure if that's necessary). One of the things I'd like to recover is URLs of tabs open in Google Chrome. Will they be on a boot partition, or the "normal" partitions available via SD Card interface?
Click to expand...
Click to collapse
If you were signed in to a google account, browser history maybe synced. Depending on which browser was being used.
Laptop eMMC Data Recovery on a Budget - Andy's Boring Job - shows how to recover data off an eMMC chip. It recommends using a board view (.brd) file to search for signal hook up points. Does anyone have a board view file for the Moto G5S Plus model XT1805?
Stuff I've read that didn't give me any new ideas on how to fix my issue:
Guide: Flashing Motorola Firmware
Using Mfastboot.exe to Flash a Motorola device
[GUIDE][FAQ][KK] How to Root, Boot Unlock & More
RSD Lite
How to use RSD Lite
Click to expand...
Click to collapse
If you have a Windows pc that originally did not have 10 (7 or XP). You can flash firmware without wiping data.
RSD Lite is your best option.
What does getvar all say?
Code:
fastboot getvar all

sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
Thanks a lot for the reply. I have fastboot.exe from the Android SDK.
Do I need to have the Motorola Drivers installed for this? I can't install them. I got the file from XDA from your link here.
I opened the downloaded file in 7zip and double clicked on Motorola_End_User_Driver_Installation_6.4.0_64bit.msi, clicked "Next", "I agree", and "Next", and I was presented with the image "motorola drivers error 1" in the attachment. Clicking through on those continued what you can see in file 2 and 3.
Or should I just run the device in Fastboot mode, connect it via USB, and then run fastboot.exe like you say above? (when I connect the device via USB in fastboot mode, it doesn't get recognized in the Device Manager on Windows. I guess due to missing drivers, but not sure, so I'm just giving you all the information I know)
If you have a Windows pc that originally did not have 10 (7 or XP). You can flash firmware without wiping data.
RSD Lite is your best option.
Click to expand...
Click to collapse
The PC I am on has Windows 10, but it didn't come with it - I installed it manually. Will that be fine?
I also have an older PC which never had Windows 10 on it (only Linux and maybe XP, not sure). I would run RSD on that too, but it would take a bunch of time to set up.
How would I use RSD Lite for that purpose? Will "without wiping data" also mean photos, as well as Chrome tabs and settings of other apps? (Google Authenticator, Steam Authenticator, Google Keep (notes), WhatsApp, etc)
Chrome on that device is not logged in so the tabs are not in the cloud.
Thanks again for being so nice to help out - that means a lot to me!

cheater00 said:
Thanks a lot for the reply. I have fastboot.exe from the Android SDK.
Do I need to have the Motorola Drivers installed for this? I can't install them. I got the file from XDA from your link here.
I opened the downloaded file in 7zip and double clicked on Motorola_End_User_Driver_Installation_6.4.0_64bit.msi, clicked "Next", "I agree", and "Next", and I was presented with the image "motorola drivers error 1" in the attachment. Clicking through on those continued what you can see in file 2 and 3.
Click to expand...
Click to collapse
Use the newer link
https://mobilesupport.lenovo.com/us/en/solution/MS88481
The PC I am on has Windows 10, but it didn't come with it - I installed it manually. Will that be fine?
I also have an older PC which never had Windows 10 on it (only Linux and maybe XP, not sure). I would run RSD on that too, but it would take a bunch of time to set up.
Click to expand...
Click to collapse
RSD Lite doesn't work with PCs built for windows 10, not sure why exactly.
I know RSD Lite doesn't like usb 3.0.
I have used RSD Lite on a few PCs that have been updated to 10 that worked fine.
How would I use RSD Lite for that purpose? Will "without wiping data" also mean photos, as well as Chrome tabs and settings of other apps? (Google Authenticator, Steam Authenticator, Google Keep (notes), WhatsApp, etc)
Chrome on that device is not logged in so the tabs are not in the cloud.
Thanks again for being so nice to help out - that means a lot to me!
Click to expand...
Click to collapse
see My flashing guide https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
use getvar all to find codename, software channel, and moto blur software version.
You must not downgrade software version.
Downgrade the correct firmware from
https://mirrors.lolinet.com/firmware/moto/
or use LMSA Flash rescue to download firmware
This is the safer option
LMSA will ask to download firmware, after downloading, it will ask to continue with flashing.
Just don't flash with LMSA.
Firmware will be in something like c/program data/lmsa/downloads/romfiles
If you download from Lolinet unzip the file, LMSA shouldn't be zipped.
There should be 2 .xml files in the folder, these contain the flashing commands.
The servicefile.xml does not wipe user data, the flashfile.xml does wipe data.
If you want you can use notepad++ to view the xml file commands.
select the servicefile.xml with RSD Lite and flash.
After flashing with RSD Lite the device should boot, provided there is not a hardware issue.
No guarantees though.

Thanks again. Highly appreciated.
sd_shadow said:
Use the newer link
https://mobilesupport.lenovo.com/us/en/solution/MS88481
Click to expand...
Click to collapse
Unfortunately this results in the same error. I guess RSD Lite and the other software will not work without those drivers. So I might have to build a new windows system for this purpose. I will try to do that asap.
There should be 2 .xml files in the folder, these contain the flashing commands.
The servicefile.xml does not wipe user data, the flashfile.xml does wipe data.
If you want you can use notepad++ to view the xml file commands.
select the servicefile.xml with RSD Lite and flash.
After flashing with RSD Lite the device should boot, provided there is not a hardware issue.
No guarantees though.
Click to expand...
Click to collapse
Thank you. Just to be sure. Using servicefile.xml with RSD Lite will not erase phone logs? Can you tell me about that specifically? The reason is, and I'm not sure if I should be talking about this here, the following. (please let me know and I'll delete this or feel free to edit the post on your own). I'm pretty ill with, well, you can guess what, and I'm quarantined. Since March none the less. So every now and then the police will come checking if I'm home. Apparently last month they couldn't find me on one day. But I did call them back after I woke up. So to prove this I need the phone logs. Otherwise I might go to jail for a month, just because I was sleeping (because after all I'm ill!). So as you can tell this is pretty important... it's not just kitten pictures. I would appreciate if you could let me know.

cheater00 said:
Thanks again. Highly appreciated.
Unfortunately this results in the same error. I guess RSD Lite and the other software will not work without those drivers. So I might have to build a new windows system for this purpose. I will try to do that asap.
Click to expand...
Click to collapse
You could try the google android drivers
https://developer.android.com/studio/run/win-usb
or manually install the old moto drivers.
https://forum.xda-developers.com/showpost.php?p=59139887&postcount=4
Thank you. Just to be sure. Using servicefile.xml with RSD Lite will not erase phone logs? Can you tell me about that specifically? The reason is, and I'm not sure if I should be talking about this here, the following. (please let me know and I'll delete this or feel free to edit the post on your own). I'm pretty ill with, well, you can guess what, and I'm quarantined. Since March none the less. So every now and then the police will come checking if I'm home. Apparently last month they couldn't find me on one day. But I did call them back after I woke up. So to prove this I need the phone logs. Otherwise I might go to jail for a month, just because I was sleeping (because after all I'm ill!). So as you can tell this is pretty important... it's not just kitten pictures. I would appreciate if you could let me know.
Click to expand...
Click to collapse
As long as the .xml doesn't contain the line
Code:
fastboot erase userdata
Call logs, browser history, texts... will still be there.
To be extra safe I would remove the flashfile.xml
Have you tried any fastboot commands?
like fastboot devices, fastboot getvar all ?

sd_shadow said:
You could try the google android drivers
https://developer.android.com/studio/run/win-usb
or manually install the old moto drivers.
https://forum.xda-developers.com/showpost.php?p=59139887&postcount=4
Click to expand...
Click to collapse
Actually I didn't need to install old drivers. I took the latest msi file and extracted it the following way:
Code:
msiexec /a c:\testfile.msi /qb TARGETDIR=c:\temp\test
Note that if the .msi file's file name is too long, msiexec will have issues extracting it. Also, you have to use full path names. If you use relative path names, msiexec will be stupid and think you are using a network file name or something like that. So always start with a drive letter.
The extracted directory structure had a subdir several levels deep called Drivers. I went to the Windows 10 Device Manager, and under "Other devices" (which is stuff that Windows didn't recognize and doesn't have drivers for) there was "fastboot sanders S". I selected "Update Driver" on that item, and pointed the dialog to the Drivers directory, and now the phone is being recognized. It is located under "Android Device" and it's now called "Motorola ADB Interface". The device called "fastboot sanders S" is gone.

sd_shadow said:
As long as the .xml doesn't contain the line
Code:
fastboot erase userdata
Call logs, browser history, texts... will still be there.
To be extra safe I would remove the flashfile.xml
Click to expand...
Click to collapse
Thank you very much for confirming!
Have you tried any fastboot commands?
like fastboot devices, fastboot getvar all ?
Click to expand...
Click to collapse
Thank you, it works now! Here's the output.
Code:
> .\fastboot.exe devices
ZY32283ZDS fastboot
Code:
> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: (removed) (let me know if you need it)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: (removed) (let me know if you need it)
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed) (let me know if you need it)
(bootloader) meid:
(bootloader) date: 08-10-2017
(bootloader) sku: XT1805
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 0:44:35 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=d95e83f
(bootloader) devcfg.git: git=d95e83f
(bootloader) keymaster.git: git=d95e83f
(bootloader) cmnlib.git: git=d95e83f
(bootloader) cmnlib64.git: git=d95e83f
(bootloader) prov.git: git=d95e83f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: protected (1003)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.110s
Please let me know if you see anything interesting here - or what you're looking for - I'd love to learn more about the topic. Thanks.

cheater00 said:
Thank you very much for confirming!
Thank you, it works now! Here's the output.
Code:
> .\fastboot.exe devices
ZY32283ZDS fastboot
Code:
> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: (removed) (let me know if you need it)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: (removed) (let me know if you need it)
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed) (let me know if you need it)
(bootloader) meid:
(bootloader) date: 08-10-2017
(bootloader) sku: XT1805
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 0:44:35 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=d95e83f
(bootloader) devcfg.git: git=d95e83f
(bootloader) keymaster.git: git=d95e83f
(bootloader) cmnlib.git: git=d95e83f
(bootloader) cmnlib64.git: git=d95e83f
(bootloader) prov.git: git=d95e83f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: protected (1003)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.110s
Please let me know if you see anything interesting here - or what you're looking for - I'd love to learn more about the topic. Thanks.
Click to expand...
Click to collapse
codename is sanders
Model is XT1805
Software Channel is reteu
Software Version is 28.65-36-14
so this version should be good.
https://mirrors.lolinet.com/firmware/moto/sanders/official/RETEU/
XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but I would also see which version LMSA selects.

sd_shadow said:
codename is sanders
Model is XT1805
Software Channel is reteu
Software Version is 28.65-36-14
so this version should be good.
https://mirrors.lolinet.com/firmware/moto/sanders/official/RETEU/
XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but I would also see which version LMSA selects.
Click to expand...
Click to collapse
Thank you, I'll check LMSA.
What is the difference between SS/DS and OPS/OPSS?

cheater00 said:
Thank you, I'll check LMSA.
What is the difference between SS/DS and OPS/OPSS?
Click to expand...
Click to collapse
ss should be Single Sim
ds should be Dual Sim
O is android 8 (oreo)
Not sure about the difference between PS and PSS.
But don't think it's anything big.

sd_shadow said:
codename is sanders
Model is XT1805
Software Channel is reteu
Software Version is 28.65-36-14
so this version should be good.
https://mirrors.lolinet.com/firmware/moto/sanders/official/RETEU/
XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but I would also see which version LMSA selects.
Click to expand...
Click to collapse
I tried LMSA and it says the phone is not supported. If I select the model number manually
Model Name: "Moto G Plus (5th Gen S)"
SKU: "XT1805"
then it says it doesn't match.
If I instead click on "Read current device" then it says it was not recognized.
Pictures are attached.
What do you suggest?
Edit: should I just go ahead with XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip?

cheater00 said:
I tried LMSA and it says the phone is not supported.
Click to expand...
Click to collapse
After installing LMSA, it directed me to the Lenovo forums, which I didn't know even existed.
It turns out there are two instances of people's G5S Plus spontaneously developing a boot loop: Thread 1, Thread 2.
In addition to that, the issue with LMSA is known on the Lenovo forums: LMSA not Working for Moto G5s Plus - Motorola Community
Following the advice in that thread, I looked at my LMSA logs. I uploaded them here: LMSA.log.
There are two things that come to mind. Here I quote from the log link above:
Code:
It's clear to me that the error is on these lines:
2020-06-29 09:48:52 [26] [INFO] Current_SoftStatusChanged - match rescue resource params: {"blurVersion":"Blur_Version.28.271.12.sanders.retail.en.US","fingerPrint":"motorola/sanders_n/sanders_n:8.1.0/OPS28.65-36-14/63857:user/release-keys","fsgVersion.qcom":null,"roCarrier":"reteu"}
2020-06-29 09:48:52 [26] [INFO] Match - missing parameter when match rescue resource
I do not have US english selected. I have bought the phone in Europe, in Austria (so the code
would be de_AT or de.AT) and I kept using the phone in British English (code en_GB or en.GB
or en_UK or en.UK). So this could be related. Or maybe fastboot not being able to find the
baseband version is an issue.
2020-06-29 09:49:40 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Failed to read [version-baseband] in fastboot, will try again
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband]: <not found>
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband] finally value:
Note that LMSA also detected OPS28.65-36-14, which is the same version as you suggested. However, the fact that LMSA says the phone is not supported, makes me worried.
If fastboot.exe is not able to detect the baseband, what does that mean? Is that normal, or should I be worried?
Thank you for your help thus far.

cheater00 said:
After installing LMSA, it directed me to the Lenovo forums, which I didn't know even existed.
It turns out there are two instances of people's G5S Plus spontaneously developing a boot loop: Thread 1, Thread 2.
In addition to that, the issue with LMSA is known on the Lenovo forums: LMSA not Working for Moto G5s Plus - Motorola Community
Following the advice in that thread, I looked at my LMSA logs. I uploaded them here: LMSA.log.
There are two things that come to mind. Here I quote from the log link above:
Code:
It's clear to me that the error is on these lines:
2020-06-29 09:48:52 [26] [INFO] Current_SoftStatusChanged - match rescue resource params: {"blurVersion":"Blur_Version.28.271.12.sanders.retail.en.US","fingerPrint":"motorola/sanders_n/sanders_n:8.1.0/OPS28.65-36-14/63857:user/release-keys","fsgVersion.qcom":null,"roCarrier":"reteu"}
2020-06-29 09:48:52 [26] [INFO] Match - missing parameter when match rescue resource
I do not have US english selected. I have bought the phone in Europe, in Austria (so the code
would be de_AT or de.AT) and I kept using the phone in British English (code en_GB or en.GB
or en_UK or en.UK). So this could be related. Or maybe fastboot not being able to find the
baseband version is an issue.
2020-06-29 09:49:40 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Failed to read [version-baseband] in fastboot, will try again
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband]: <not found>
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband] finally value:
Note that LMSA also detected OPS28.65-36-14, which is the same version as you suggested. However, the fact that LMSA says the phone is not supported, makes me worried.
If fastboot.exe is not able to detect the baseband, what does that mean? Is that normal, or should I be worried?
Thank you for your help thus far.
Click to expand...
Click to collapse
@sd_shadow just wanted to update, I have tried contacting Lenovo on multiple fronts (someone even put me in touch of the president of Lenovo for north america!) but silence so far.

Bootloader status is still locked even though it says UNLOCKED in Developer Settings.

I'm getting quite desperate right now. I've almost tried everything.
I have enabled OEM Unlocking and USB Debugging in Developer Settings. Mi Unlock Status says it's Unlocked.
I unlocked it in 2019 using Miflash Unlock Tool application when it was still the one where you need to wait a couple days to get approved.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Then booting to fastboot, running this command: "fastboot oem device-info" shows me this:
Code:
C:\Android\Mi A2 Lite\OTAFlasher fastboot oem device-info
...
[B](bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:[/B]
OKAY [ 0.070s]
finished. total time: 0.071s
I tried using OTAFlasher ADB/Fastboot, Minimal ADB & Fastboot 1.4.3 and using these commands:
Code:
C:\Android\Mi A2 Lite\Minimal fastboot devices
4b09dc1d9905 fastboot
C:\Android\Mi A2 Lite\OTAFlasher fastboot oem edl
...
[B]FAILED (remote: device is locked! no edl)
finished. total time: 0.022s[/B]
C:\Android\Mi A2 Lite\OTAFlasher fastboot flashing unlock
...
[B]FAILED (remote: unknown command)
finished. total time: 0.022s[/B]
C:\Android\Mi A2 Lite\OTAFlasher fastboot oem unlock
...
[B]FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.032s[/B]
C:\Android\Mi A2 Lite\OTAFlasher fastboot oem unlock-go
...
[B]FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.034s
[/B]
Nothing works.
Using MiFlash Unlock application shows me this error: "Couldn't unlock. Please add your account in MIUI's settings Developer options Mi unlock status".
Click to expand...
Click to collapse
And I couldn't add my account because it's only showing this screen (Obviously, because I have unlocked it before):
Click to expand...
Click to collapse
Here's my fastboot getvar all result:
Code:
C:\Android\Mi A2 Lite\OTAFlasher fastboot getvar all
(bootloader) version:0.5
(bootloader) token:VQEBJgEQLS3oiWtLt46mxpFTykTPCAMMc2FrdXJhX2luZGlhAgReP
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3793000
(bootloader) variant:QRD eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:MSM8953_DAISY1.0_20180628013533
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1fe00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5d3bfbe00
(bootloader) partition-type:cust:
(bootloader) partition-size:cust: 0x34000000
(bootloader) partition-type:vendor:
(bootloader) partition-size:vendor: 0x40000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) partition-type:oem:
(bootloader) partition-size:oem: 0x10000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:modem:
(bootloader) partition-size:modem: 0x8000000
(bootloader) partition-type:logdump:
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:recovery:
(bootloader) partition-size:recovery: 0x4000000
(bootloader) partition-type:boot:
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:persistbak:
(bootloader) partition-size:persistbak: 0x2000000
(bootloader) partition-type:persist:
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:mdtp:
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:dsp:
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:splash:
(bootloader) partition-size:splash: 0x1000000
(bootloader) partition-type:bk5:
(bootloader) partition-size:bk5: 0x800000
(bootloader) partition-type:modemst2:
(bootloader) partition-size:modemst2: 0x800000
(bootloader) partition-type:modemst1:
(bootloader) partition-size:modemst1: 0x800000
(bootloader) partition-type:fsg:
(bootloader) partition-size:fsg: 0x800000
(bootloader) partition-type:devinfo:
(bootloader) partition-size:devinfo: 0x800000
(bootloader) partition-type:mcfg:
(bootloader) partition-size:mcfg: 0x400000
(bootloader) partition-type:tzbak:
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:bk4:
(bootloader) partition-size:bk4: 0x100000
(bootloader) partition-type:dip:
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:abootbak:
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:misc:
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:keymasterbak:
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:cmnlib64bak:
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlib64:
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlibbak:
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib:
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-type:syscfg:
(bootloader) partition-size:syscfg: 0x80000
(bootloader) partition-type:keystore:
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:mota:
(bootloader) partition-size:mota: 0x80000
(bootloader) partition-type:rpmbak:
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:sbl1bak:
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:msadp:
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:devcfgbak:
(bootloader) partition-size:devcfgbak: 0x40000
(bootloader) partition-type:devcfg:
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:lksecappbak:
(bootloader) partition-size:lksecappbak: 0x20000
(bootloader) partition-type:lksecapp:
(bootloader) partition-size:lksecapp: 0x20000
(bootloader) partition-type:bk3:
(bootloader) partition-size:bk3: 0x10000
(bootloader) partition-type:config:
(bootloader) partition-size:config: 0x8000
(bootloader) partition-type:limits:
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:DDR:
(bootloader) partition-size:DDR: 0x8000
(bootloader) partition-type:bk2:
(bootloader) partition-size:bk2: 0x5000
(bootloader) partition-type:bk1:
(bootloader) partition-size:bk1: 0x4000
(bootloader) partition-type:sec:
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:dpo:
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:ssd:
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:
(bootloader) partition-size:fsc: 0x2000
(bootloader) rollback_ver:1
(bootloader) serialno:4b09dc1d9905
(bootloader) kernel:lk
(bootloader) product:sakura_india
all:
finished. total time: 1.351s
Any ideas or alternative solutions?
Thank you.

adb, fastboot and "fastboot oem unlock" command

Divolka said:
adb, fastboot and "fastboot oem unlock" command
Click to expand...
Click to collapse
I did. Does not work.

mirzakeehl said:
I did. Does not work.
Click to expand...
Click to collapse
Oh, right didn't see in the post, sorry.
Check if your PC is authorized by your phone, if not sure revoke authorization and authorize again.
Also you might try flashing android one through miflashtool and try to unlock bootloader after that, but I'm pretty sure it requires unlocked bootloader

Divolka said:
Oh, right didn't see in the post, sorry.
Check if your PC is authorized by your phone, if not sure revoke authorization and authorize again.
Also you might try flashing android one through miflashtool and try to unlock bootloader after that, but I'm pretty sure it requires unlocked bootloader
Click to expand...
Click to collapse
Sorry but how do I check if my PC is authorized by my phone?
Using miflashtool doesn't work at all because even though the device is detected, everything results in error. Probably because my bootloader is locked

mirzakeehl said:
Sorry but how do I check if my PC is authorized by my phone?
Using miflashtool doesn't work at all because even though the device is detected, everything results in error. Probably because my bootloader is locked
Click to expand...
Click to collapse
Did you boot to edl? If not you can do that by "adb reboot edl" or "adb oem edl" I never know which one works.
Just revoke all authorization, there option to do that in developer settings, connect to pc and authorize it and try to unlock again

Divolka said:
Did you boot to edl? If not you can do that by "adb reboot edl" or "adb oem edl" I never know which one works.
Just revoke all authorization, there option to do that in developer settings, connect to pc and authorize it and try to unlock again
Click to expand...
Click to collapse
Oh, did you mean USB Debugging authorization? Yeah, I have revoked and authorized it again.
Executing "adb reboot edl" just resets the phone and "adb oem edl" doesn't do anything.
Thanks.

mirzakeehl said:
Oh, did you mean USB Debugging authorization? Yeah, I have revoked and authorized it again.
Executing "adb reboot edl" just resets the phone and "adb oem edl" doesn't do anything.
Thanks.
Click to expand...
Click to collapse
One of those commands, probably first one should make your screen plain black and make notification LED flash

Divolka said:
One of those commands, probably first one should make your screen plain black and make notification LED flash
Click to expand...
Click to collapse
So apparently this phone has a fake UBL and I have to do a flashing by test point to be able to unlock the bootloader. I don't know how to though, do you know how?
Thanks.

mirzakeehl said:
So apparently this phone has a fake UBL and I have to do a flashing by test point to be able to unlock the bootloader. I don't know how to though, do you know how?
Thanks.
Click to expand...
Click to collapse
Sorry but I have no idea, ask on telegram, I'm sure someone will help you on one of all those groups

Divolka said:
Sorry but I have no idea, ask on telegram, I'm sure someone will help you on one of all those groups
Click to expand...
Click to collapse
Will do. Thank you!

mirzakeehl said:
Will do. Thank you!
Click to expand...
Click to collapse
Not sure if this helps but this is how I unlocked my Mi A2 Lite bootloader before then installing Magisk to the phone and a patched boot image:
NB: THe oem unlock and reboot steps where you keep keys pressed BEFORE you enter after the command (this avoids full data wipe of the phone - I can confirm it works!)
USB debug ON
OEm unlock ON
Then connect phone to PC:
adb devices
adb reboot bootloader
fastboot oem unlock - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
fastboot reboot - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
Now you are ready to boot into your system. Either boot by holding power button or typing - fastboot reboot - Press Enter
Install Magisk Manager - APK to phone
You need the original boot.img to patch - After you get the boot.img, copy it to the phone memory (via USB or microSD, or download directly from the phone browser, as you prefer).
Open the Magisk Manager app installed previously, it will ask if you want to install Magisk. Accept by tapping on "Install" > "Patch Boot Image File" and select the boot.img file that you have put on phone.
Wait until the process completes (about 1 minute), then tap on "Close". Now in the phone memory, inside the Download directory, you should have a patched_boot.img file. Copy that file to the PC, adbm folder
The original boot image you can get from the fastboot rom using a tool called payload-dumper-win64 (i found it on one of these forums as a download link) - it extracts the image files from the rom
Alternatively, you should be able to download a patched boot image from the A2 Lite forum
adb reboot bootloader
fastboot boot magisk_patched.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button.
Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
Last step to stay safe when a new OTA update arrives: go to "Settings" > "System" > "Developer options" > and disable "Automatic system updates".
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk.
Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
I'm currently on the 11.0.12.0 ROM and the above method works fine - it has for the last 3 monthly OTA updates
Hope this helps

FOREST37 said:
Not sure if this helps but this is how I unlocked my Mi A2 Lite bootloader before then installing Magisk to the phone and a patched boot image:
NB: THe oem unlock and reboot steps where you keep keys pressed BEFORE you enter after the command (this avoids full data wipe of the phone - I can confirm it works!)
USB debug ON
OEm unlock ON
Then connect phone to PC:
adb devices
adb reboot bootloader
fastboot oem unlock - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
fastboot reboot - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
Now you are ready to boot into your system. Either boot by holding power button or typing - fastboot reboot - Press Enter
Install Magisk Manager - APK to phone
You need the original boot.img to patch - After you get the boot.img, copy it to the phone memory (via USB or microSD, or download directly from the phone browser, as you prefer).
Open the Magisk Manager app installed previously, it will ask if you want to install Magisk. Accept by tapping on "Install" > "Patch Boot Image File" and select the boot.img file that you have put on phone.
Wait until the process completes (about 1 minute), then tap on "Close". Now in the phone memory, inside the Download directory, you should have a patched_boot.img file. Copy that file to the PC, adbm folder
The original boot image you can get from the fastboot rom using a tool called payload-dumper-win64 (i found it on one of these forums as a download link) - it extracts the image files from the rom
Alternatively, you should be able to download a patched boot image from the A2 Lite forum
adb reboot bootloader
fastboot boot magisk_patched.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button.
Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
Last step to stay safe when a new OTA update arrives: go to "Settings" > "System" > "Developer options" > and disable "Automatic system updates".
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk.
Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
I'm currently on the 11.0.12.0 ROM and the above method works fine - it has for the last 3 monthly OTA updates
Hope this helps
Click to expand...
Click to collapse
First of all, thank you very much for the very detailed guide.
Secondly, do you perhaps still remember what shows up in the CMD/Powershell when you did these commands?
Code:
fastboot oem unlock - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
fastboot reboot - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
I assume it showed up as FINISHED without error, right? Unfortunately, mine got stuck right there. Precisely as I've mentioned in the thread's post. So I can't really do the steps after that.
Thanks.

mirzakeehl said:
First of all, thank you very much for the very detailed guide.
Secondly, do you perhaps still remember what shows up in the CMD/Powershell when you did these commands?
Code:
fastboot oem unlock - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
fastboot reboot - start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
I assume it showed up as FINISHED without error, right? Unfortunately, mine got stuck right there. Precisely as I've mentioned in the thread's post. So I can't really do the steps after that.
Thanks.
Click to expand...
Click to collapse
If I remember correctly I just used abdminimal and it was straightforward, simply entered the command, the phone booted into fastboot mode, typed the next command into the command line, did key combination, pressed enter and it did next stage. Dont think i got anything on the powershell/cmd line such as finished. Sorry, I cant offer any more advice. What happens if you were to toggle the OEM unlocking in the developer options? (apart from possibly wipe your data, would that perhaps reset your phone?) Or perhaps reflash the entire ROM to your phone and start again?

Are you sure you have a Mi A2 Lite (daisy) (Android One) device? Mi A2 Lite does'nt have a MIUI.
I think your phone is Redmi 6 Pro (sakura) or fake 6 Pro made from A2L.
Unlocking Mi A2L is easy by simple command "fastboot oem ulock" nothing more No need request permission to unlock BL in Mi Unlock sw.

lars00 said:
Are you sure you have a Mi A2 Lite (daisy) (Android One) device? Mi A2 Lite does'nt have a MIUI.
I think your phone is Redmi 6 Pro (sakura) or fake 6 Pro made from A2L.
Unlocking Mi A2L is easy by simple command "fastboot oem ulock" nothing more No need request permission to unlock BL in Mi Unlock sw.
Click to expand...
Click to collapse
You're correct. My device is sakura_india. It's a China model with India rom, modified for Indonesia customers.
I've given up, should be easier to just bring the phone to a Xiaomi service center nearby.
Thanks.

mirzakeehl said:
You're correct. My device is sakura_india. It's a China model with India rom, modified for Indonesia customers.
I've given up, should be easier to just bring the phone to a Xiaomi service center nearby.
Thanks.
Click to expand...
Click to collapse
Try "sakura" thread on XDA https://forum.xda-developers.com/redmi-6-pro

The developer option of my phone says that it is unlocked.But when i try to install custom recovery, then my pc says that my phone's bootloader is not unlocked.what should i do?
Please help? What is the problem and how i van get rid of it..
My model:redmi 4 prime (markw)