Develop Bugs

Soft-bricked when going back to factory

I have bricked my Pixel C :crying: when I was trying to restore it back to how it was when I got it from the factory, because my girlfriend has been using it lately and complained about the message when booting. I thought maybe all I have to do is a factory reset, but that only wiped the data, so I foolishly :silly: figured this would be extremely easy, all I would have to do is pull down the newest factory image and flash it using the included script. That failed when trying to flash the bootloader saying something like "unknown command" sorry, didn't capture the exact wording, but that is pretty close. After that I rebooted the device and it wouldn't boot, as you could've guessed from me posting, instead it sat at the google screen. I left it for the night because for all I know, it was encrypting stuff or something.
I can still get to the custom recovery(TWRP) and fastboot, but I can't get into actual android. I tried applying an OTA update through TWRP after that figuring it will have access, but now instead of hanging at the google logo, I get bounced over to the recovery system.
At this point, I decided I need to slow down and do some more research, maybe even reach out for help. Could you guys help me troubleshoot my/soon to be my girlfriend's tablet? You can find the output of fastboot getvar all below, I can see mismatched versions and secure set to yes, but unlocked set to yes. I don't know what to be concerned about or what to do(I was about to research how to set the secure flag to no, but I realized how deep this hole is becoming.)
Code:
(bootloader) version: 0.3
(bootloader) version-bootloader: Google_Smaug.7900.27.0
(bootloader) version-baseband: N/A
(bootloader) product: dragon
(bootloader) secure: yes
(bootloader) max-download-size: 0x10000000
(bootloader) partition-type:boot: ext4
(bootloader) partition-type:kernel-a: ext4
(bootloader) partition-type:kernel-b: ext4
(bootloader) partition-type:recovery: ext4
(bootloader) partition-type:kernel: ext4
(bootloader) partition-type:system: ext4
(bootloader) partition-type:system-a: ext4
(bootloader) partition-type:vendor: ext4
(bootloader) partition-type:vendor-a: ext4
(bootloader) partition-type:cache: ext4
(bootloader) partition-type:data: ext4
(bootloader) partition-type:userdata: ext4
(bootloader) partition-type:metadata: ext4
(bootloader) partition-type:lnx: ext4
(bootloader) partition-type:misc: ext4
(bootloader) partition-type:persistent: ext4
(bootloader) partition-type:system-b: ext4
(bootloader) partition-type:vendor-b: ext4
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-size:kernel-a: 0x2000000
(bootloader) partition-size:kernel-b: 0x2000000
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-size:kernel: 0x2000000
(bootloader) partition-size:system: 0xe0000000
(bootloader) partition-size:system-a: 0xe0000000
(bootloader) partition-size:vendor: 0x13000000
(bootloader) partition-size:vendor-a: 0x13000000
(bootloader) partition-size:cache: 0x19000000
(bootloader) partition-size:data: 0xd76b00000
(bootloader) partition-size:userdata: 0xd76b00000
(bootloader) partition-size:metadata: 0x4000000
(bootloader) partition-size:lnx: 0x2000000
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-size:persistent: 0x80000
(bootloader) partition-size:chromeos: 0xe8f800000
(bootloader) partition-size:mbr: 0x200
(bootloader) partition-size:gpt: 0x4200
(bootloader) partition-size:RO_SECTION: 0x3f0000
(bootloader) partition-size:RO_VPD: 0x10000
(bootloader) partition-size:RW_SECTION_A: 0x580000
(bootloader) partition-size:RW_SECTION_B: 0x580000
(bootloader) partition-size:bootloader: 0x1000000
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
(bootloader) battery-voltage: 4319 mV
(bootloader) variant:
(bootloader) battery-soc-ok: yes
(bootloader) Bdev-size:mmc: 62537072640
(bootloader) Bdev-size:flash: 16777216
(bootloader) Gbb-flags: 0x0
(bootloader) Oem-version:RO: Google_Smaug.7132.226.0
(bootloader) Oem-version:RW_A: Google_Smaug.7900.27.0
(bootloader) Oem-version:RW_B: Google_Smaug.7900.27.0
all: Done!
finished. total time: 0.460s

Try "fastboot continue"

Just tried that, it booted me back to the recovery. The only thing that it said on my computer's side is "resuming boot..." and some time statistics. Any commands I can run to help you guys help me?

techy121592 said:
Just tried that, it booted me back to the recovery. The only thing that it said on my computer's side is "resuming boot..." and some time statistics. Any commands I can run to help you guys help me?
Click to expand...
Click to collapse
Format data, not wipe, inside twrp.
If you still have problems, Install system vendor and boot.img again.

followmsi said:
Format data, not wipe, inside twrp.
If you still have problems, Install system vendor and boot.img again.
Click to expand...
Click to collapse
Ok, will try that and come back to you. Thank you.

I tried formatting the data partition, which didn't seem to make much of a difference, also I tried installing the boot and vendor images through twrp last night. Then vendor image applied without any problems, but the boot image didn't get installed, it looked like it was trying to reference the boot image like it is a directory.
Would I want to extract the image and then reference the directory? Though I don't know if twrp will let me point at a directory rather than a file.
Whenever I flashed roms, I tend to use fastboot, and then root it with twrp. Instead of that, would I be able to install the factory image zip from google? Or could I safely install all of the images(except recovery) through twrp individually? Do you think there is a flag or setting that I need to set in android, if so do you think I could install a custom rom and set the setting?
Sorry if these questions make me sound like a noob, but I am trying to be thorough.

Just use wugs or skipsoft toolkit to flash to stock or if you know how together around in fastboot flash stock. You could just download pure nexus and flash it via twrp. These are just suggestions, attempt at your own risk.

techy121592 said:
I tried formatting the data partition, which didn't seem to make much of a difference, also I tried installing the boot and vendor images through twrp last night. Then vendor image applied without any problems, but the boot image didn't get installed, it looked like it was trying to reference the boot image like it is a directory.
Would I want to extract the image and then reference the directory? Though I don't know if twrp will let me point at a directory rather than a file.
Whenever I flashed roms, I tend to use fastboot, and then root it with twrp. Instead of that, would I be able to install the factory image zip from google? Or could I safely install all of the images(except recovery) through twrp individually? Do you think there is a flag or setting that I need to set in android, if so do you think I could install a custom rom and set the setting?
Sorry if these questions make me sound like a noob, but I am trying to be thorough.
Click to expand...
Click to collapse
As we don't know the full story and we want to get your Pixel C back to normal ..
Pls install all partitions from latest google factory image via fastboot .. start with the bootloader.
Code:
fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
fastboot reboot-bootloader
Pls delete boot first - before you flash it.
Code:
fastboot erase boot
fastboot flash boot boot.img
Do this for all partitions except recovery .. keep TRWP.
Do not boot into system and boot directly into TWRP and flash SuperSU.zip.
Reboot into system ..

Clockcycle - after I failed to use Google flash-all script, I swapped to using wugs. When I tried skipsoft like 8+ months ago it didn't support the final release of Android Nougat, only the rc's. Nowadays, is skipsoft better than wugs?
Clockcycle & followingmsi - Thank you for your suggestions, I'm out and about, so I'll try it once I get back home tonight; I didn't want you to think I was being unresponsive.

I got the results that I was expecting, it doesn't mean anything to me, but maybe you guys will know. I typed, "fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img" and got the following.
Code:
target reported max download size of 268435456 bytes
sending 'bootloader'...
OKAY [ 0.624s]
FAILED (remote: unsupported command)
finished. total time: 0.640s
and when I typed, "fastboot erase boot" I got the following.
Code:
******** Did you mean format this ext4 partition?
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.016s
Because of that, I tried formatting also, it gave me some output that looked like it was formatting it(showed me the inodes and everything,) but that was followed by the same "FAILED" message that you can see above.
When I was going through the menu to get to fastboot, I noticed that the bootloader must've got applied successfully the first time, when I was originally using the flash-all script, which is when this whole "adventure" began, because I saw that I had bootloader 7900.27.
I really feel like I am missing something that is staring me right in the face.

Found the solution...
https://forum.xda-developers.com/pixel-c/help/flashing-to-stock-android-npd90g-twrp-t3424863
In short running the following from the adb shell fixes it.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1

techy121592 said:
I got the results that I was expecting, it doesn't mean anything to me, but maybe you guys will know. I typed, "fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img" and got the following.
Code:
target reported max download size of 268435456 bytes
sending 'bootloader'...
OKAY [ 0.624s]
FAILED (remote: unsupported command)
finished. total time: 0.640s
and when I typed, "fastboot erase boot" I got the following.
Code:
******** Did you mean format this ext4 partition?
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.016s
Because of that, I tried formatting also, it gave me some output that looked like it was formatting it(showed me the inodes and everything,) but that was followed by the same "FAILED" message that you can see above.
When I was going through the menu to get to fastboot, I noticed that the bootloader must've got applied successfully the first time, when I was originally using the flash-all script, which is when this whole "adventure" began, because I saw that I had bootloader 7900.27.
I really feel like I am missing something that is staring me right in the face.
Click to expand...
Click to collapse
Looks like you need to update your SDK.

So literally yesterday i had my Pixel C doing same thing after i unlocked bootloader and it got stuck on Erasing screen and then after hard reboot got stuck on google Splash screen. contacted google for help they didnt know crap. haha go figure. Of course this was after i tried a few things myself. They were sending me a new device which i canceled cause i fixed it later.
i was returning same crap for fastboot everytime couldnt do anything, from what i understand we messed up the Partitions somehow. So how to fix it, what might work for you as it worked for me.
I was on 7.1.1 Build number not important. I booted into Bootloader fastboot then to android recovery (stock), press PWR+VOL up to see menu for it as least for my pixel for other devices to each is own. Do a cache wipe and factory reset. when complete hold power and vol down to reboot.
Update system to latest firmware. somehow by letting OTA updates i did like 4 of them to get to 7.1.2 and then rebooted into Bootloader Fastboot Magically worked again so i preceded with root and what have you. all working Perfect now. Guess the OTA 7.1.2 update fixed all the partitions. Forget what specifically was missing from the partition but yeah. fastboot wouldn't let me do anything myself. IE flash all bat flash or boot anything. and ADB wouldn't flash anything.
of course i had to relock the bootloader in order for all this to work. Something about 7.1.2 just seemed to let me do what i want. on 7.1.1 it did not like unlocked bootloader not sure why. But im not a expert. =)
Back in day just used Odin to get back to factory not sure if thats a possiblity these days if someone knows let me know i would like to understand better.

Endless bootloop. Can't get into recovery even with fastboot commands

Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.

kt006 said:
Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.
Click to expand...
Click to collapse
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.

When trying to enter recovery mode, either with Fastboot command or button press, the phone just restarts and bootloops. I'll try your method later tonight.

TheSt33v said:
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.
Click to expand...
Click to collapse
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.

kt006 said:
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.
Click to expand...
Click to collapse
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?

TheSt33v said:
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?
Click to expand...
Click to collapse
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s

kt006 said:
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s
Click to expand...
Click to collapse
My readout looks exactly the same except in fields where one would expect it to be different (serial number, mac addresses). The only exception is that I'm on bootloader version 4.2. I'm currently running the most recent official firmware version (the post-preview version is an older version than the most recent. I took several OTAs after I flashed it when I decided I didn't like the wear 2.0 preview), but I don't see why that would matter or cause the problem you're having since your bootloader is unlocked and should therefore not be enforcing anything. When you flash the wear 2.0 preview, does your bootloader version change?

Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere

kt006 said:
Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere
Click to expand...
Click to collapse
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.

TheSt33v said:
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.
Click to expand...
Click to collapse
The strangest thing happened. I disconnected the internal battery overnight. When I reconnected it the watch booted into the system perfectly fine. Then after restarting the watch because of a pairing error, I'm back to square one again.

Need help with very weird soft brick

Hey everybody, here's my story: I bought earlier today a second-hand G5, it was already soft bricked when I purchased it. It was already unlocked (had the warning message when turned on), so I first proceeded to install TWRP, try and flash a custom ROM.
Everything was working fine on bootloader mode, phone was snappy (more on that in a bit) and not lagging.
Then the issues started: on TWRP, it took ages to do anything. The phone's boot logo lasted almost a minute, then TWRP's splash screen stood there for over another minute, and each action I made in it (like touching options on menus and stuff like that) needed a good 10+ seconds to be processed. Tried formatting data, changing FS to from F2FS to EXT4, and other stuff like that, nothing solved the tremendous lag. I also faced some random reboots and many USB disconnecting/reconnecting episodes (like one per second, sometimes) at TWRP as well. Getting the phone to boot TWRP is also a pain, because it keeps switching between a bootlogo with "N/A" (as if there is a custom ROM/recovery installed) and a bootlogo with "bad key" (as if bootloader is unlocked, but ROM and recovery are stock), remains a few minutes in each, and eventually it decides to boot up on TWRP.
Eventually I just gave up and flashed a stock firmware using both RSDLite and fastboot. Flashing times were just about alright, as was everything done via bootloader mode, no stuttering here. Stock recovery (which is operated via volume/power keys, not touch) seemed to work without speed issues as well.
At some point (after many failed efforts, reboots that went straight to recovery, wiping everything multiple times using both TWRP and stock recovery, and so on) I managed to start booting it and... It was sluggish as hell. The boot animation took around 10 minutes to complete (not looping through the animation multiple times, it was just really slow, and it actually just showed about 2 or 3 frames from different moments of the animation and stuck in these frames for several minutes each), the "Hello Moto" tone also played very slowly (as if I were streaming it in 1080p using a 256kbps modem), and when it reached the Lenovo logo (which I presume is the last stage in the boot animation), it bootlooped back to the first frame (Motorola's logo, same as the splash screen but without the "bad key" or "N/A" warning - I had changed from that annoying "bootloader unlocked, device can't be trusted" screen by flashing a modified logo.bin, thus the only difference between splash screen and bootanimation's first frame was the abscence of the text), did so a few times (I think I let it run that way for about 40 minutes) before battery got depleted. Never got into OS.
I did run into a few secondary issues (tried to relock bootloader then unlock again just to find that I couldn't get an unlock code from Motorola's site; had it booting straight into recovery; couldn't wipe data and cache, had TWRP ask for encryption key; etc), but managed to solve all of them.
The point is that right now I have a phone that I can boot either TWRP or stock recovery, or go into bootloader (or sometimes bootloop whilst taking 10 minutes to display the boot animation), but TWRP is slower than a Celeron rendering GTA V, barely usable. Flashing custom (through TWRP) or stock (through fastboot or RSDLite) ROMs seem to complete successfully, but they never get to boot.
If there's any difference, I don't know which version the phone was when I purchased it, but right now bootloader is B8.31, and I tried flashing both 16-2 then 16-4 Oreo versions. Phone model is 1672.
Any help is appreciated, I bought this phone as a gift to my girlfriend and it's specially frustrating I didn't manage to fix it for her.

K3n H1mur4 said:
Hey everybody, here's my story
Click to expand...
Click to collapse
Bro Try To Flash No verity opt zip
it might help you boot

Sonisudhanshu said:
Bro Try To Flash No verity opt zip
it might help you boot
Click to expand...
Click to collapse
Device seems to be unable to get into recovery, now. Just goes into a bootloop with "bad key" (even though TWRP has been flashed). When I try to boot TWRP straight from fastboot (like boot twrp.img instead of flash recovery twrp.img), it shows the usual splash screen (also with neither "bad key" nor "N/A"), but then bootloops into "bad key" again. Will try flashing a different firmware (tried with a random RETBR Nougat and the latest, 16-4, RETBR Oreo) to see if I get any luck.

this sounds like a severe case of very faulty hardware, or some sort of bl corruption. either get the phone checked out in a repair shop or hope for a blank flash?

Exanneon said:
this sounds like a severe case of very faulty hardware, or some sort of bl corruption. either get the phone checked out in a repair shop or hope for a blank flash?
Click to expand...
Click to collapse
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?

K3n H1mur4 said:
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
Click to expand...
Click to collapse
there isn't one yet, but that seems to be your only option atm

Exanneon said:
there isn't one yet, but that seems to be your only option atm
Click to expand...
Click to collapse
K3n H1mur4 said:
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
Click to expand...
Click to collapse
Why would he need a blank flash? There's nothing wrong with his bootloader
Also we can already revive hard bricked devices with mmcblk0 image but that's not the issue here
Also you obviously won't get another unlock code from Motorola - your device is already unlocked - just because you locked it again doesn't actually lock it the same way
You can just unlock it via fastboot with an unlock command
Anyway moving on
Goto https://mirrors.lolinet.com/firmware/moto/cedric/official/
And downloaded the latest firmware for your device
Flash it via fastboot - note that the firmware must be the same or later version than what is already there
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5 (only oreo firmware)
fastboot flash system system.img_sparsechunk.6 (only oreo firmware)
fastboot flash system system.img_sparsechunk.7 (only oreo firmware)
fastboot flash system system.img_sparsechunk.8 (only oreo firmware)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Make sure gpt and Bootloader flash successfully - a pre flash validation error means that the firmware is too old
Post the output if you get errors

K3n H1mur4 said:
I'm not sure about hardware fault, isn't the BL stored in the same NAND chip as everything else? Because on BL everything works as it should.
Also, about blank flash, there isn't one for Cedric yet, right?
Click to expand...
Click to collapse
Did you try a clean flash or a dirty flash, sometimes dirty flash can result this so I prefer you to clean the data inside first by using twrp advance wipe select all and the format yes and again do a advance wipe after boot into bootloader and flash the latest firmware with bootloader and gpt codes also so bootloader also can reflash. Once you are clean without any other software in Device. the device will work like a champ, and please post the flashing command you get in fastboot as well as getvar also by removing the IMEI and serial number.
Here is the link for latest firmware:-
https://mirrors.lolinet.com/firmware/moto/cedric/official/

TheFixItMan said:
-
Click to expand...
Click to collapse
Hey pal, I appreciate your advice and understand you're a very helpful member in the G5 forums, but I have around 10 years on the modding community (even before Android), and am pretty familiar with flashing via recovery, fastboot or vendors' flashing tools. I've already tried, so, the steps you suggested, to no result either.
Just as a sideline, I've actually managed to get an unlock code from Motorola's online support, but that doesn't make a difference anyway.
I gave a shot on three of the RETBR versions (Oreo 16-2 and 16-4, and Nougat 93-8, this last one obviously without flashing bootloader and gpt). In all of the attempts I got either one of two results: it gets to recovery (TWRP runs slow as hell, stock recovery seems fine) or it keeps bootlooping when I try to get to recovery.
Just tried a RETAIL 16-4 firmware (with gpt and bootloader from RETBR being flashed instead of RETAIL's files), the only error messages I got in fastboot were the expected "Image signed with key bad key when flashing boot and recovery .imgs, but they both flashed just as expected. Same result as before: bootlogo with unlocked warning (showing bad key), then a "boot animation" that was really just the first frame from each part (Motorola logo same as boot logo, the first frame of the animation that plays with the "Hello Moto" sound - also, only some parts of the tone played, like it was lagging too much; then Lenovo Logo; then Motorola logo with "Motorola, a Lenovo company" below; then Lenovo logo again - I really suspect that, if one pulls a bootanimation.zip from a stock firmware, each of the "0", "1", "2" etc parts will have as their first frame exeactly the frames I just described, as if the phone was unable to properly display the animation) displaying for a few minutes each, then it jumps back to bootlogo. It's definitely in bootloop even though I just flashed just per instructions, and also with this issue of being veeeeeeeryyyyyy sloooooooooowwww... After that, it just keeps going into bootlogo for several minutes, than screen off for a few seconds, then bootlogo again for several minutes.
riyan65 said:
-
Click to expand...
Click to collapse
There's no dirty flashing via fastboot AFAIK. When I managed to get into TWRP, I had an issue with /data being encrypted and in F2FS, and some issue with /cache, too (but /cache was in EXT4), both of them were showing as 0B in size at that "repair or change file system" screen.
I read somewhere that F2FS can make TWRP very slow, so I though it could be that, but I formatted /data to EXT4 as well and the phone was still very slow. I also was having issues with TWRP not being able to mount /data and /cache, formatting solved that as well.
After formatting, I managed to flash Bootleggers. It took a good 30-40 minutes to flash, and TWRP restarted right after that so I couldn't flash GApps. It went again into a bootlogo-only bootloop (no frames from boot animation appeared before it restarted into bootlogo again). Then I just gave up on TWRP and tried finding some stock firmware that could boot, but, as stated on the answer above, I still didn't manage to do so.
Right now I'm suspecting either a hardware fault or something very messed with GPT (but I can't really tell for the second one since I've already flashed both RETBR's GPTs and both of them gave me the same result).
What I'd like to try now before just giving up are both very unlikely options to find: first, a custom ROM that's fastboot flashable (Iif I remember well some files in fastboot must be signed by Motorola else they won't flash, so there's no way to create a fastboot-flashable custom firmware, am I right?); second, to find out if the bootloader is stored in the same NAND/eMMC as the other partitions, or if it is a separate chip. If it's the same chip, I could easily rule out a hardware fault and try to find other possible solutions. If it's stored separately, than it explains why bootloader works without stuttering and the other modes (except for stock recovery, but that's kinda slow by itself so I could simply be unable to tell the difference) like TWRP and normal booting are so slow and failing everytime.

New information: can't get official TWRP to boot, but 64 bits version seems to work. MTP also works while on TWRP, and surprisingly at normal transfer rates. Tried both copying a file to and from internal storage using Windows Explorer, both did a 640MB zip in about a minute or so. ADB push, on the other hand, is very slow: got just 78 MB (of a 807MB zip file) transferred in 10 minutes. After some time TWRP rebooted (before completing ADB push), and I was only able to get to TWRP again after re-flashing it. Probably I just messed up with allowing TWRP to write in /system and not flashing anything before it restarted.
Also, here's a photo of the dm-verity zip flash log and a video showing bootloader working normally but TWRP very slow (note the transitions).
Last, but not least, I'd like to check if all the usual partitions are in ext4 (and formatting to ext4 those who aren't), I saw just yesterday some thread where someone pointed how to list partitions in adb shell and format them, but I can't find this thread anymore. Could anyone help me with this?

K3n H1mur4 said:
New information: can't get official TWRP to boot, but 64 bits version seems to work. MTP also works while on TWRP, and surprisingly at normal transfer rates. Tried both copying a file to and from internal storage using Windows Explorer, both did a 640MB zip in about a minute or so. ADB push, on the other hand, is very slow: got just 78 MB (of a 807MB zip file) transferred in 10 minutes. After some time TWRP rebooted (before completing ADB push), and I was only able to get to TWRP again after re-flashing it. Probably I just messed up with allowing TWRP to write in /system and not flashing anything before it restarted.
Also, here's a photo of the dm-verity zip flash log and a video showing bootloader working normally but TWRP very slow (note the transitions).
Last, but not least, I'd like to check if all the usual partitions are in ext4 (and formatting to ext4 those who aren't), I saw just yesterday some thread where someone pointed how to list partitions in adb shell and format them, but I can't find this thread anymore. Could anyone help me with this?
Click to expand...
Click to collapse
I want you to do a format which is beside the advance format you can see in the image as it will decrypt the data and if anything is makeing the mess it will also remove so that you can flash the firmware and restore the format to default so everything should fine.

riyan65 said:
I want you to do a format which is beside the advance format you can see in the image as it will decrypt the data and if anything is makeing the mess it will also remove so that you can flash the firmware and restore the format to default so everything should fine.
Click to expand...
Click to collapse
I have tried it as well, no success whatsoever
I managed to flash Bootleggers again last night, took a couple hours to complete but at least TWRP didn't reboot during the process. Differently from stock ROM, however, phone didn't even get to the sluggish boot animation. It just stays in bootlogo, then eventually reboots (again to bootlogo).
Later tonight I'll try your suggestion again, I plan to do a Format Data, then changing it to ext4 again (if I remember well, Format Data puts the partition into f2fs), perhaps reflashing the no-verity zip and then Bootleggers again. I'm not hoping to get it working anymore, though.

Just out of curiosity, I tried a fastboot getvar all and it returned some peculiar info, specifically that MEID is empty and baseband is marked as "not found". Could this be related to the sluggishness and inability to complete a boot? Does anyone know how to gat a baseband and flash it to the phone? Or is it related to the physical BB IC? @TheFixItMan @riyan65
Also, it's carrier is listed as TIMBR, I've already downloaded a TIMBR firmware but didn't try to flash it yet, could this be of any help? I tried flashing just the modem from this TIMBR firmware but it didn't do any good.
I also saw someone on the G4 Plus forum solve a similar issue (though his IMEI wasn't showing and mine is) by replacing the battery, and if I remember well (it has been 7 years since and my memory isn't very good) I had a similar problem with baseband (I think it was mobile signal not showing) in a Motorola Defy I had because of a faulty (or counterfeit, can't remember now) battery.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 8
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB 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:[B][REDACTED][/B]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x17
(bootloader) uid: [B][REDACTED][/B]
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: [B][REDACTED][/B]
(bootloader) meid:
(bootloader) date: 05-08-2017
(bootloader) sku: XT1672
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 11:39:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-16-4/9ef8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.251.4.cedric.reta
(bootloader) ro.build.version.full[1]: il.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-g35a8502 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Fri Dec 14 09:10:59 CST
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=ff20bf6
(bootloader) devcfg.git: git=ff20bf6
(bootloader) keymaster.git: git=ff20bf6
(bootloader) cmnlib.git: git=ff20bf6
(bootloader) cmnlib64.git: git=ff20bf6
(bootloader) prov.git: git=ff20bf6
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: timbr
(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

K3n H1mur4 said:
Just out of curiosity, I tried a fastboot getvar all and it returned some peculiar info, specifically that MEID is empty and baseband is marked as "not found". Could this be related to the sluggishness and inability to complete a boot? Does anyone know how to gat a baseband and flash it to the phone? Or is it related to the physical BB IC?
@TheFixItMan @riyan65
Also, it's carrier is listed as TIMBR, I've already downloaded a TIMBR firmware but didn't try to flash it yet, could this be of any help? I tried flashing just the modem from this TIMBR firmware but it didn't do any good.
I also saw someone on the G4 Plus forum solve a similar issue (though his IMEI wasn't showing and mine is) by replacing the battery, and if I remember well (it has been 7 years since and my memory isn't very good) I had a similar problem with baseband (I think it was mobile signal not showing) in a Motorola Defy I had because of a faulty (or counterfeit, can't remember now) battery.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 8
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB 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:[B][REDACTED][/B]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x17
(bootloader) uid: [B][REDACTED][/B]
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Volume down key pressed
(bootloader) imei: [B][REDACTED][/B]
(bootloader) meid:
(bootloader) date: 05-08-2017
(bootloader) sku: XT1672
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 11:39:55 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-16-4/9ef8:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.251.4.cedric.reta
(bootloader) ro.build.version.full[1]: il.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-g35a8502 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Fri Dec 14 09:10:59 CST
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=ff20bf6
(bootloader) devcfg.git: git=ff20bf6
(bootloader) keymaster.git: git=ff20bf6
(bootloader) cmnlib.git: git=ff20bf6
(bootloader) cmnlib64.git: git=ff20bf6
(bootloader) prov.git: git=ff20bf6
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: timbr
(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
Click to expand...
Click to collapse
MIED is an alternative to imei - its a phone identification number and if the phone has an imei number it doesn't need MIED as well
Having no baseband would probably just mean the phone won't have any network unless it's a modem issue that is stopping the phone booting
The firmware you need for timber is
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You can also try generic firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And Brazilian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Now I'm assuming your device is actually a xt1672 and you haven't tried to flash wrong firmware or otas not designed for your phone in the past
If flashing the firmware using all the commands I previously posted doesn't work you may have to replace the motherboard

TheFixItMan said:
MIED is an alternative to imei - its a phone identification number and if the phone has an imei number it doesn't need MIED as well
Having no baseband would probably just mean the phone won't have any network unless it's a modem issue that is stopping the phone booting
Click to expand...
Click to collapse
Well, if the phone gets no signal it'll sure be an issue. But first I need to get it to boot before I can worry with that.
TheFixItMan said:
The firmware you need for timber is
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
You can also try generic firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And Brazilian firmware
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Now I'm assuming your device is actually a xt1672 and you haven't tried to flash wrong firmware or otas not designed for your phone in the past
If flashing the firmware using all the commands I previously posted doesn't work you may have to replace the motherboard
Click to expand...
Click to collapse
Already tried RETBR and RETAIL, neither worked (they flashed just fine via either via fastboot or RSD, but got on bootloop with sluggish bootanimation and/or just bootlogo bootlooping). I'm trying with TIMBR right now, but I doubt it will make any difference. Device is a 1672, since I bought it second-hand and already bricked can't tell if the previous owner flashed anything wrong on it. If it did so, I think the device would be hardbricked, not with this weird slowness on TWRP and boot animation, and bootloops would be solved by reflashing stuff on fastboot.

(SOLVED)Need somebody really expert on unlock bootloader on this phone, please halp

So i brough this weird phone, and i guess i will need somebody really expert on this unlock bootloader thing this time.
0 - Locked bootloader, but in motorola software says it have root
1 - I can boot to system normaly, use sim, imeis are all ok (but there is no gapps and no way to flash it)
2 - LineageOS Pie rom
3 - i can acess fastboot (that says is locked)
4- i cannot acess recovery (when select this option, returns to fastboot)
5 - there is no "oem unlock" option in "developer options"
6 - my phone is elegible to unlock, so i already got the motorola code through the site (to use with "fastboot oem unlock CODE", but when i do the command line, says that i need to turn on the oem unlock option that doesnt exist in "developer options"
7 - If i try to boot any twrp img in fastboot mode (to flash twrp zip), the phone reboot to fastboot again (as i said, i have no acess to recovery)
8- If i update the magisk (comes with lineageOS), the system wont boot anymore, and says its corrupt, shows a recovery red window but only with "factory format" option (and if i do, the phone just format as it was in the beginning)
9 - if i try to flash anything in fastboot, i will fail coz of couse, its locked.
10- i have the box, original items, papers and documents (but its out of warranty).
11 - tried Lenovo Moto Smart Assistant, but when i put my model and awaits to fastboot, says that cannot do nothing.
I just want to use stock oreo, nothing more, is too much to ask? :crying: :crying: :crying:
Please dont ask me what the previous owner did to this phone, i dont know(he neighter, said only that after trying to install custom rom, bricked the phone, but somehow could install this lineageOS :crying: :crying:
Any help to this poor soul? Thanks already :crying: :crying:

What is the model, what does it say by the charger port? XT1789-??
In fastboot issue 'fastboot getvar all' w/o quotes and post that info here -minus your imei# that will give an idea of what firmware you need to flash to get back to stock and unlock.

41rw4lk said:
What is the model, what does it say by the charger port? XT1789-??
In fastboot issue 'fastboot getvar all' w/o quotes and post that info here -minus your imei# that will give an idea of what firmware you need to flash to get back to stock and unlock.
Click to expand...
Click to collapse
Thanks thanks for comment <3
its a XT1789-05, and the info you asked:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190608
(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: 0049486108
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 5291F1FC
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 03-22-2019
(bootloader) sku: XT1789-05
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) battery-voltage: 4051
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-19/
(bootloader) ro.build.fingerprint[1]: 02844:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.19.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: M8998_50.71.02.95R NRD
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf9e16d5 (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]: Sat Jun 8 12:34:38 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190608
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190608
(bootloader) gitmic: MBM-3.0-nash_retail-4fc2afc-190608
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190608
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190608
(bootloader) gitrov: MBM-3.0-nash_retail-3537781-190608
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(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.453s

From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that.
So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there.
https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72

41rw4lk said:
From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that.
So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there.
https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72
Click to expand...
Click to collapse
Yes all works fine, sim cards, wifi, etc. But i already tried to flash stock oreo but the phone dont even allow any file flash because of locked bootloader. The pie files will bypass that? Anyways thanks thanks again to your answer, i will try what you said and follow the link (since i fix my notebook psu that screew up just now )

41rw4lk said:
From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that.
So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there.
https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72
Click to expand...
Click to collapse
not worked :crying:
did all he said : Unzip the 2 files (flashall ... and firm ...) and place them in a folder
Click on "Preparation.bat", you must generate a "flash.bat file", double click with the phone in download mode
It's all, really clean installation
It was what I did, I am not responsible for damage to your equipment
but nothing can be flashed because of bootloader locked:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.229s]
finished. total time: 0.281s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.384s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.546s
target reported max download size of 536870912 bytes
sending 'modem_a' (78412 KB)...
OKAY [ 4.390s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.417s
any more ideas ? :crying: :crying: :crying:

brunojborges said:
not worked :crying:
did all he said : Unzip the 2 files (flashall ... and firm ...) and place them in a folder
Click on "Preparation.bat", you must generate a "flash.bat file", double click with the phone in download mode
It's all, really clean installation
It was what I did, I am not responsible for damage to your equipment
but nothing can be flashed because of bootloader locked:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.229s]
finished. total time: 0.281s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.384s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.546s
target reported max download size of 536870912 bytes
sending 'modem_a' (78412 KB)...
OKAY [ 4.390s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.417s
any more ideas ? :crying: :crying: :crying:
Click to expand...
Click to collapse
well, I recommend that you download the Lenovo moto application, something like that is the name, after installing it, connect the terminal in Lenovo moto app in fastboot mode, click on the Flash option and then where it says to recover, complete the information that asks you wait for it to finish, an official ROM flashed, and from there you can start with the bootloader unlock

Have you signed into a google account on the phone? Do you see developer options in settings? I know you said you didn't see oem unlocking so that's why I ask. We'll try to tackle those and get you unlocked. It's possible that you pbl and trust zone is messed up so a blankflash might be needed to sort that.
With a locked bootloader you should able to flash the same firmware version or newer, but if your chain of trust is compromised it's a little difficult, but not impossible.

41rw4lk said:
Have you signed into a google account on the phone? Do you see developer options in settings? I know you said you didn't see oem unlocking so that's why I ask. We'll try to tackle those and get you unlocked. It's possible that you pbl and trust zone is messed up so a blankflash might be needed to sort that.
With a locked bootloader you should able to flash the same firmware version or newer, but if your chain of trust is compromised it's a little difficult, but not impossible.
Click to expand...
Click to collapse
i cant sign into google accouts because there is no gapps pre installed on LineageOS, and i cant flash anything because the bootloader locked. There is developer options but only the adb debbug option, there is no "oem unlock" option (thats why when i try to fastboot oem unlock "CODE", the prompt says that i need to first activate the "oem unlock" option into the system, but as i said, there is no OEM option inside developer options. Maybe could be this "chain of thrust" thing. What should i do? thanks

brunojborges said:
i cant sign into google accouts because there is no gapps pre installed on LineageOS, and i cant flash anything because the bootloader locked. There is developer options but only the adb debbug option, there is no "oem unlock" option (thats why when i try to fastboot oem unlock "CODE", the prompt says that i need to first activate the "oem unlock" option into the system, but as i said, there is no OEM option inside developer options. Maybe could be this "chain of thrust" thing. What should i do? thanks
Click to expand...
Click to collapse
Can you not sign into google from accounts in settings? Also, you can download the playstore apk and install it manually. Usually to enable oem unlocking you have to be signed into google. So check accounts and see if you can sign in there, and/or d/l the apk and sign in there. Reboot and check dev options again for oem unlocking once you've signed in.

Heridg said:
well, I recommend that you download the Lenovo moto application, something like that is the name, after installing it, connect the terminal in Lenovo moto app in fastboot mode, click on the Flash option and then where it says to recover, complete the information that asks you wait for it to finish, an official ROM flashed, and from there you can start with the bootloader unlock
Click to expand...
Click to collapse
i need unlock bootloader just to revert to stock. I dont want to keep unlocked, or install custom stuff. If i just had the "oem unlock" option in developer options, i could fix that. And about moto smart assistant, when i put my phone and do this steps, after choosing my phone number and model, after the program detect my phone in fastboot mode, it shows a message, "this device is not supported".

41rw4lk said:
Can you not sign into google from accounts in settings? Also, you can download the playstore apk and install it manually. Usually to enable oem unlocking you have to be signed into google. So check accounts and see if you can sign in there, and/or d/l the apk and sign in there. Reboot and check dev options again for oem unlocking once you've signed in.
Click to expand...
Click to collapse
installed both, play store and services apk's from different sites. Tried clean cache, and anything else, but there is always a message forcing to close app. Cant open them.

(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
maybe isnt this messing this phone ?

Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess.
First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out.
If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.

41rw4lk said:
Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess.
First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out.
If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.
Click to expand...
Click to collapse
Please sr teach me how to do this blankflash thing, in the truth, i could bring back imeis erased from a axon 7 i had, making A LOT of crazy and dangerous moves (deleting partitions, backup binary files, editing and return back, etc), but im new with this motorola. Please teach me :crying: :crying:

41rw4lk said:
Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess.
First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out.
If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.
Click to expand...
Click to collapse
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.012s
didnt worked. I have to do this blankflash.

brunojborges said:
Please sr teach me how to do this blankflash thing, in the truth, i could bring back imeis erased from a axon 7 i had, making A LOT of crazy and dangerous moves (deleting partitions, backup binary files, editing and return back, etc), but im new with this motorola. Please teach me :crying: :crying:
Click to expand...
Click to collapse
If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of).
Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5

41rw4lk said:
If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of).
Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
thanks, i will read 10x before do anytyhing, and will do carefully. i had nothing else to do. This will fix my phone or it will turn a paper weight. Im warned. Thank you sir, wish me luck and i will tell u if i have any sucess.

41rw4lk said:
If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of).
Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
if i click on .bat file:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>.\qboot.exe blank-flash
< waiting for device >
and if i do manually "fastboot oem blankflash":
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.012s
:crying: :crying: :crying: :crying: :crying: :crying: :crying:
there is any way to force hard brick and them enter in Qualcomm HS-USB QDLoader 900 mode? Maybe this way will be easier
:crying: :crying:

brunojborges said:
if i click on .bat file:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>.\qboot.exe blank-flash
< waiting for device >
and if i do manually "fastboot oem blankflash":
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.012s
:crying: :crying: :crying: :crying: :crying: :crying: :crying:
there is any way to force hard brick and them enter in Qualcomm HS-USB QDLoader 900 mode? Maybe this way will be easier
:crying: :crying:
Click to expand...
Click to collapse
boot to os, make sure adb debugging is enabled, then open a cmd prompt and enter 'adb reboot edl' w/o quotes

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.