Develop Bugs

I can't unlock bootloader

Hi*guys*I*tried*to*unlock*the*bootloader*of*my*cell*phonebut*when*placing*the*bootloader*log*tells*me*that*it*doesnot*qualify*my*device
This*is*the*record*of*get-var*all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.12
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322FQBR2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x1e
(bootloader) uid: E390CDC400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 351864087651315
(bootloader) meid:
(bootloader) date: 03-06-2019
(bootloader) sku: XT1601
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0:51:34 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-16/0400:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.41.15.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: M8937_22.29.02.70R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g2148ea10 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Wed Sep 5 10:00:37 CDT
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.12-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VB8.12-0-gc6ac81e
(bootloader) tz.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) devcfg.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) keymaster.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) cmnlib.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) cmnlib64.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) prov.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) aboot.git: git=MBM-NG-VB8.12-0-gf2e5426
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: retla1st
all: listed above

Gaxo said:
Hi*guys*I*tried*to*unlock*the*bootloader*of*my*cell*phonebut*when*placing*the*bootloader*log*tells*me*that*it*doesnot*qualify*my*device
This*is*the*record*of*get-var*all
Click to expand...
Click to collapse
What did you tried to unlock the bootloader?

lucki1000 said:
What did you tried to unlock the bootloader?
Click to expand...
Click to collapse
I tried from the Motorola page but it gives an error that the device does not qualify to unlock the bootloader

Gaxo said:
Hi*guys*I*tried*to*unlock*the*bootloader*of*my*cell*phonebut*when*placing*the*bootloader*log*tells*me*that*it*doesnot*qualify*my*device
This*is*the*record*of*get-var*all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.12
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY322FQBR2
(bootloader) cid: 0x0000
(bootloader) channelid: 0x1e
(bootloader) uid: E390CDC400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 351864087651315
(bootloader) meid:
(bootloader) date: 03-06-2019
(bootloader) sku: XT1601
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0:51:34 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-16/0400:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.41.15.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: M8937_22.29.02.70R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g2148ea10 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Wed Sep 5 10:00:37 CDT
(bootloader) kernel.version[3]: 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.12-0-g98be833
(bootloader) rpm.git: git=MBM-NG-VB8.12-0-gc6ac81e
(bootloader) tz.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) devcfg.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) keymaster.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) cmnlib.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) cmnlib64.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) prov.git: git=MBM-NG-VB8.12-0-g09f1e7a
(bootloader) aboot.git: git=MBM-NG-VB8.12-0-gf2e5426
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: retla1st
all: listed above
Click to expand...
Click to collapse
I'm confused
Your product device is listed as cedric (moto g5) but your sku is listed as XT1601 (moto g4 play)
Play device or amazon prime devices may not always be eligible for bootloader unlock

Gaxo said:
I tried from the Motorola page but it gives an error that the device does not qualify to unlock the bootloader
Click to expand...
Click to collapse
Did you allowed unlock bootloader in developer options?

Gaxo said:
I tried from the Motorola page but it gives an error that the device does not qualify to unlock the bootloader
Click to expand...
Click to collapse
TheFixItMan said:
I'm confused
Your product device is listed as cedric (moto g5) but your sku is listed as XT1601 (moto g4 play)
Play device or amazon prime devices may not always be eligible for bootloader unlock
Click to expand...
Click to collapse
here you have the solution :victory:

TheFixItMan said:
Hi*guys*I*tried*to*unlock*the*bootloader*of*my*cell*phonebut*when*placing*the*bootloader*log*tells*me*that*it*doesnot*qualify*my*device
This*is*the*record*of*get-var*all
I'm confused
Your product device is listed as cedric (moto g5) but your sku is listed as XT1601 (moto g4 play)
Play device or amazon prime devices may not always be eligible for bootloader unlock
Click to expand...
Click to collapse
Ok, this is weird. When I bought the second-hand device, the cell phone came with the bootloader unlocked. I had a report when I bought it, so I ordered it removed. I guess they changed the sku to unlock it. Is there a solution to change sku? As for example installing the original firmware by fastboot

Gaxo said:
Ok, this is weird. When I bought the second-hand device, the cell phone came with the bootloader unlocked. I had a report when I bought it, so I ordered it removed. I guess they changed the sku to unlock it. Is there a solution to change sku? As for example installing the original firmware by fastboot
Click to expand...
Click to collapse
You could try flashing stock firmware as long as it is actually a moto g5 (check the label under the battery)
You would need to flash gpt & bootloader to repartition
Firmware can be found
https://mirrors.lolinet.com/firmware/moto/cedric/official/
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
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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
If you get security downgrade error when trying to flash gpt/bootloader the firmware you are trying to flash is too old

TheFixItMan said:
You could try flashing stock firmware as long as it is actually a moto g5 (check the label under the battery)
You would need to flash gpt & bootloader to repartition
Firmware can be found
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you get security downgrade error when trying to flash gpt/bootloader the firmware you are trying to flash is too old
Click to expand...
Click to collapse
I will try to flash the stock rom that is here, Since I was in Nougat and update to Oreo with the last published revision Give more details when you unlock it

It did not work, I have tried with the rom that you have given me and with all the stocks in this forum it still does not change the SKU

Gaxo said:
It did not work, I have tried with the rom that you have given me and with all the stocks in this forum it still does not change the SKU
Click to expand...
Click to collapse
Sounds to me like it could have possibly been a bricked phone and they have used some software/hardware to flash an image back onto it giving it that sku (which is odd as I worked with others to make a totally safe way to unbrick this device)
If after enabling adb debugging and enabling oem unlock if available if its saying your device is not eligible for unlock (assuming all codes have been entered correctly on the Motorola website) then there's not anything you can do
If I were you I'd contact the seller and question why your device displays the sku of a moto g4 play & obtain a refund for dodgy practices

I have a small idea, If I try to use the SD method with the Firmware that you have put in another thread and try to fully flash the cell phone including Bootllader (Since this cell phone is updated to 8.1 and I have flashed the bootloader of the rom) I may recover your Original Sku, right?

Gaxo said:
I have a small idea, If I try to use the SD method with the Firmware that you have put in another thread and try to fully flash the cell phone including Bootllader (Since this cell phone is updated to 8.1 and I have flashed the bootloader of the rom) I may recover your Original Sku, right?
Click to expand...
Click to collapse
The image tricks the phone into booting the bootloader from the sd card so a user without an accessable bootloader can then flash gpt which repartitions the device and then flash the bootloader back
I don't know how they changed the sku (probably by JTAG)
So the sd card probably wouldn't help if you have flashed gpt and bootloader from the latest firmware
You could always create the sd card and see if it gives you a different sku when it's inserted

TheFixItMan said:
Sounds to me like it could have possibly been a bricked phone and they have used some software/hardware to flash an image back onto it giving it that sku (which is odd as I worked with others to make a totally safe way to unbrick this device)
If after enabling adb debugging and enabling oem unlock if available if its saying your device is not eligible for unlock (assuming all codes have been entered correctly on the Motorola website) then there's not anything you can do
If I were you I'd contact the seller and question why your device displays the sku of a moto g4 play & obtain a refund for dodgy practices
Click to expand...
Click to collapse
Man, I'm already busting my head to unlock the boorloader of this thing, I'll leave it so I really don't have another G5 to test, It's intregant somehow how the hell they changed the sku to the cell phone Anyway, even so thanks for the help friend

Gaxo said:
Man, I'm already busting my head to unlock the boorloader of this thing, I'll leave it so I really don't have another G5 to test, It's intregant somehow how the hell they changed the sku to the cell phone Anyway, even so thanks for the help friend
Click to expand...
Click to collapse
My best guess is they used a JTAG and modified moto g4 play unbrick files to be able to flash the bootloader back to the G5 but who knows
I take it when you have typed
oem get_unlock_data
It gives you a key and you have copied this key into a text document and then removed all the spaces
The key is normally on about 4 lines so you need to remove all the spaces so it's just on one whole line then copy that very long string into the Motorola website

Fastboot reason: fall-through from normal boot mode

Hey everyone, since i tried updating my moto z2 force att with a faulty cable and then using a working one through lenovo "smart" "assistant", whenever i turn it off or restart i get: Fastboot reason: fall-through from normal boot mode, after trying many things the only way i found to recover my phone was to run this command list from adb command promt:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot reboot​
I know that those commands are for installing a rom, but i was in a hurry and got away with it.
However i found that these commands are the needed to avoid losing all my data.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Please note that this is a temporary solution, if i turn off my phone i will have to run the commands again, which honestly i dont know what are they for .
If this helps someone, use it. If someone has a permanent solution, could you provide it? the bootloader cant be unlocked in the ATT phones as far as i know, couldnt find anything to help me on the internet.

If I understand you correctly, it sounds like whenever you boot or reboot you end up in fastboot. If that is the case then simply run this command in fastboot 'fastboot oem fb_mode_clear' w/o 'quotes'. Then 'fastboot reboot'. That should let you boot normally. If that isn't the problem then you need to explain more.

thanks gotta try that one out.
What happens is that when i restart or turn on my phone, it says that it cant be trusted and wont boot, after a while it goes to the screen that i mention (havent figured out how to upload images here) where it says fastboot reason of the tittle of my post. From there the only way to interact is through adb with the commands that i mention.

41rw4lk said:
If I understand you correctly, it sounds like whenever you boot or reboot you end up in fastboot. If that is the case then simply run this command in fastboot 'fastboot oem fb_mode_clear' w/o 'quotes'. Then 'fastboot reboot'. That should let you boot normally. If that isn't the problem then you need to explain more.
Click to expand...
Click to collapse
Hey i tried that one and no sucess only got this
https:// drive. google. com/ open?id= 1obn 0MW0qLBiMet9 -4oUwZVx X7j5UmT-Z​
but if i turn it off it returns to the screens below
http s:// drive. google. com/ o pen?i d= 1ICNS -p1ZMCzp qJE6wAVM OlMEhO 2UuDVw​and
htt ps: //d rive.go ogle .com/op en?id=1pfwLb JufMHPGS3klFw td6uWl1G gKIole​
From there if i run the commands that i previously said i get this and if i reboot, the phone starts correctly
https ://driv e.goog le.co m/ope n?id=1RS aGOQfbo VkIY4u1 nLAHA9GWib5UK gJg​
The rom that is in the adb folder is XT1789-04_NASH_ATT_8.0.0_OCXS27.109-47-20_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip, and i previously tried to install this before the lenovo smart software wasnt working at all. The results were the same only that i lost all my data.
If i try to run the lenovo smart assistant again and try to recover, it says that my phone is not supported, weird because that software caused all of this and the faulty cable :silly:

Are you sure you have an ATT phone? What is the model no. by the charger port? The thing is, ATT has a locked bootloader so the only thing you should be able to do is flash officially signed firmware that is either the same version or newer. That's it. Run the command 'fastboot getvar all' in bootloader mode and post your output.

41rw4lk said:
Are you sure you have an ATT phone? What is the model no. by the charger port? The thing is, ATT has a locked bootloader so the only thing you should be able to do is flash officially signed firmware that is either the same version or newer. That's it. Run the command 'fastboot getvar all' in bootloader mode and post your output.
Click to expand...
Click to collapse
Yes, its ATT, it has the logo at the back, its the XT1789-04, according to settings.
I ran the command that you said and i get this
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_att-316e620-190110
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224B9BNP
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: 9CF79D1A
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 353311080575347
(bootloader) meid:
(bootloader) date: 07-24-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4077
(bootloader) iccid: 89014103270252580378
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_att/nash:8.0.0/OCXS2
(bootloader) ro.build.fingerprint[1]: 7.109-47-23/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.261.4.nash_att.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NUS_ATT
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g0f8e904 (huds
(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 May 28 02:06:00 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_att-316e620-190110
(bootloader) git:xbl: MBM-3.0-nash_att-9869834-190110
(bootloader) gitmic: MBM-3.0-nash_att-9869834-190110
(bootloader) git:rpm: MBM-3.0-nash_att-b13e14f-190110
(bootloader) git:tz: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:hyp: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:devcfg: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:cmnlib: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:cmnlib64: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:keymaster: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) git:storsec: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) gitrov: MBM-3.0-nash_att-7b81ec45-190110
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (210)
(bootloader) ro.carrier: att
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.750s​
I used this tutorial to install it previously, and got the issue that im mentioning in my post
https://www.getdroidtips.com/att-moto-z2-force-stock-firmware/

Anyone got a solution yet?

Why don't you download the latest firmware for ATT and use the attached zip to manually flash your phone. Just extract your firmware into the utilities zip, make sure you're in bootloader mode, and run the flashall.
Latest firmware for ATT
https://mirrors.lolinet.com/firmwar...29_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip

Awesome! it woked, tanks!

41rw4lk said:
Why don't you download the latest firmware for ATT and use the attached zip to manually flash your phone. Just extract your firmware into the utilities zip, make sure you're in bootloader mode, and run the flashall.
Latest firmware for ATT
https://mirrors.lolinet.com/firmwar...29_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hi, recently the phone reboots and stays at bootloop at night when charging, do you have any idea why?
Also it boots itself and the bootloop happens sometimes, in some bootloops i would get a notification saying "Android System there is an internal problem with your device and may be unstable until you factory data reset" which i did and after sometime it started happening again (didnt do backup restore) the apps start failing without even opening them and google play services also fail.
any clue?
Im really tired of this phone but i want to sell it to afford another phone.

mau22975 said:
Hi, recently the phone reboots and stays at bootloop at night when charging, do you have any idea why?
Also it boots itself and the bootloop happens sometimes, in some bootloops i would get a notification saying "Android System there is an internal problem with your device and may be unstable until you factory data reset" which i did and after sometime it started happening again (didnt do backup restore) the apps start failing without even opening them and google play services also fail.
any clue?
Im really tired of this phone but i want to sell it to afford another phone.
Click to expand...
Click to collapse
Might try hitting bootloader and issuing fastboot -w to format user data. Though the culprit could be a failing battery. Might check your cable and/or power source.

41rw4lk said:
Might try hitting bootloader and issuing fastboot -w to format user data. Though the culprit could be a failing battery. Might check your cable and/or power source.
Click to expand...
Click to collapse
The weird thing is that i bought a turbocharger from amazon and i used it everyday, its supposed to be oem. But after that i started using my regular 1A charger and reboots are not that frequent. Also the moto battery mod may be a cause now that you point it. Today i didnt use it and no reboot...yet.
Could you explain more about hitting the bootloader and issuing fastboot? im not very familiar with those terms
Thank you very much!

mau22975 said:
The weird thing is that i bought a turbocharger from amazon and i used it everyday, its supposed to be oem. But after that i started using my regular 1A charger and reboots are not that frequent. Also the moto battery mod may be a cause now that you point it. Today i didnt use it and no reboot...yet.
Could you explain more about hitting the bootloader and issuing fastboot? im not very familiar with those terms
Thank you very much!
Click to expand...
Click to collapse
Some general moto flashing info
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

Moto G8 stuck on boot screen 'M' but goes no further

So, I have just acquired a secondhand phone Moto G8, sticks at the M boot up screen and goes no further. I can access fastboot and the PC recognises it, and can access stock recovery and factory reset. Just does the same. Tried the moto firmware repair tool but didn't recognise the phone was connected (despite fastboot working). Thought about unlocking the bootloader but I get a failure when I request the unlock info in fastboot, so can't get the unlock code. Ideas? If I could unlock the bootloader I could manually flash the stock firmware.
I downloaded the official firmware from lolinet - which is basically this: XT2045-2_RAV_RETEU_10_QPJS30.63-35-1-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml This is showing as correct on the bootloader screen, but to be sure I ran fastboot getvar: (bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-rav_reteu-dfa2a6b4b2-210101
(bootloader) product: rav
(bootloader) board: rav
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY227BHF38
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: FC48029A
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805259264
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxx
(bootloader) imei2: xxxxx
(bootloader) meid:
(bootloader) date: 04-13-2020
(bootloader) sku: XT2045-2
(bootloader) carrier_sku: XT2045-2
(bootloader) battid: SB18C51711
(bootloader) battery-voltage: 4298
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/rav_reteu/rav:10/QPJS30.6
(bootloader) ro.build.fingerprint[1]: 3-35-1-17/80ecc:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Fri Jan 1 11:0
(bootloader) kernel.version[3]: 2:34 CST 2021
(bootloader) git:abl: MBM-3.0-rav_reteu-dfa2a6b4b2-210101
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C68387
So I know I've got the right firmware.

https://forum.xda-developers.com/t/moto-g-fast-rav-i-bricked-my-device.4247149/post-84657525 would this maybe work?

GitManMatt said:
https://forum.xda-developers.com/t/moto-g-fast-rav-i-bricked-my-device.4247149/post-84657525 would this maybe work?
Click to expand...
Click to collapse
Just tried to flash twrp recovery (different one to listed but probably wouldn't make a difference) got this:
fastboot flash recovery twrp-rav.img target reported max download size of 805259264 bytes
sending 'recovery' (42408 KB)...
OKAY [ 0.912s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.936s
I'll try the suggested one, probably won't be any different

GitManMatt said:
Just tried to flash twrp recovery (different one to listed but probably wouldn't make a difference) got this:
fastboot flash recovery twrp-rav.img target reported max download size of 805259264 bytes
sending 'recovery' (42408 KB)...
OKAY [ 0.912s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.936s
I'll try the suggested one, probably won't be any different
Click to expand...
Click to collapse
nope same message

NVM - I worked it out - used the mfastboot tool rather than fastboot, and plugged these commands in:
.\mfastboot getvar max-sparse-size
.\mfastboot oem fb_mode_set
.\mfastboot flash partition gpt.bin
.\mfastboot flash bootloader bootloader.img
.\mfastboot flash vbmeta vbmeta.img
.\mfastboot flash radio radio.img
.\mfastboot flash bluetooth BTFM.bin
.\mfastboot flash dsp dspso.bin
.\mfastboot flash logo logo.bin
.\mfastboot flash boot boot.img
.\mfastboot flash dtbo dtbo.img
.\mfastboot flash recovery recovery.img
.\mfastboot flash super super.img_sparsechunk.0
.\mfastboot flash super super.img_sparsechunk.1
.\mfastboot flash super super.img_sparsechunk.2
.\mfastboot flash super super.img_sparsechunk.3
.\mfastboot flash super super.img_sparsechunk.4
.\mfastboot flash super super.img_sparsechunk.5
.\mfastboot flash super super.img_sparsechunk.6
.\mfastboot flash super super.img_sparsechunk.7
.\mfastboot flash super super.img_sparsechunk.8
.\mfastboot flash super super.img_sparsechunk.9
.\mfastboot flash super super.img_sparsechunk.10
.\mfastboot flash super super.img_sparsechunk.11
.\mfastboot flash super super.img_sparsechunk.12
.\mfastboot flash super super.img_sparsechunk.13
.\mfastboot erase carrier
.\mfastboot erase userdata
.\mfastboot erase metadata
.\mfastboot erase ddr
.\mfastboot oem fb_mode_clear
I did this manually but you can use the firmware guide elsewhere to run a batch file which will do it for you (I just preferred methodically going through each one by one!)
All back and up and running now. Please ask if you need help, I might be able to suggest something now!

Hello, I have the same moto g8 and I have not been able to solve anything as you could, the command already downloads the mfastboot and it does not recognize anything, we are already in android 11 and change this partition is not there. \ mfastboot flash super super.chunkg.11_sparsechunk.8 and this up to super 15 will you help me?

Adrianbene said:
Hello, I have the same moto g8 and I have not been able to solve anything as you could, the command already downloads the mfastboot and it does not recognize anything, we are already in android 11 and change this partition is not there. \ mfastboot flash super super.chunkg.11_sparsechunk.8 and this up to super 15 will you help me?
Click to expand...
Click to collapse
Hi there, so I figured out how to flash this thing a while back but it can be a nightmare to reset. First, you should try lenovo rescue agent to see if it can fix it, most of the time, the software can fix anything you've done. If that doesn't work, you only have one option left. You have to flash chunks in fasboot to reset, which isn't to hard. Now if you are trying to flash a custom rom to this phone you have to first have android 10 stock flashed with a password in place, with no numbers. I use a simple word like five. The reason is you cant unlock system and decrypt it if it has nothing to decrypt in twrp. You can flash in a custom recovery otherwise though, likes lineages custom recovery thats built for this phone. The other issues you are going to run into are making sure your using the right build, there's like 20 for this phone because it was built out and sold as a bunch of different models so it has a bunch of stock roms. If your phone is unlocked use the retus in lolinet and flash chunks. It's best to flash custom roms ontop of a stock android 10 in fastbootD with this phone, regardless if youve been told to use twrp or not, imo.

XT-1675 with locked bootloader [HELP]

Hi,
I have a cedric xt-1675 with locked bootloader (i have a key to unlock and i tried unlocking it through fastboot it says its disable) and when I try to load into recovery mode it gave me error
FAILED TO PASS VALIDATION. BACKUP TO FASTBOOT
BOOTUP FAILED
I tried flashing firmware through fastboot white doing mfastboot flash partition gpt.bin
C:\Users\Abdul Rafy\Desktop\New folder\ar\boot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.077s
all other flash commands works fine except mfastboot flash partition gpt.bin
Thanks

You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options

TheFixItMan said:
You won't be able to flash gpt on a locked bootloader unless it's the exact same signed image from Motorola that is on your device which I doubt you'll ever find.
If you unlocked your device before and then locked it again you will need either a new motherboard or take it to a repair shop for jtag flashing.
This is why after unlocking you should never lock it again.
If you had the correct unlock key all you would need to do assuming adb debugging and oem unlock is enabled is go into fastboot mode and then in a terminal window on pc type
fastboot oem unlock UNLOCK_KEY
Where UNLOCK_KEY is your key
If you have bricked your device and corrupted the partition information as mentioned you will need a new motherboard or take to repair shop for reimaging with specialist equipment
Else just start the phone normally from the bootloader options
Click to expand...
Click to collapse
thanks for the reply, I never have unlocked my device before it has locked bootloader since start. anyway, I have tried "fastboot oem unlock UNLOCK_KEY" it says enable oem unlocking from developer option and the problem is i couldn't get into phone not even into recovery just fastboot. It used to get stuck at moto logo but now when I try to boot normally it says
Failed to verify hab image boot
failed to validate boot image
Error: Failed to pass validation. backup to fastboot
Boot up failed
and if I try to go into recovery, it says
Failed to verify hab image recovery
failed to validate recovery image
Error: Failed to pass validation. backup to fastboot
Boot up failed
another thing I did try Software repair assistant but it gave me error on 47%

Here the getvar just in case:
(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: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SKHYNIX HAG4a2 RV=08 PV=A4 FV=00000000000000A4
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x4e
(bootloader) uid: 0295944600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 535822336
(bootloader) reason: Last time flashing failed
(bootloader) imei: XXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 03-07-2017
(bootloader) sku: XT1675
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 8: 2: 8 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-19-4-2/3447de:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.301.2.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: M8937_46.42.02.75R CEDRIC_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0001
(bootloader) kernel.version[1]: 6-g6e15bdb ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Mon Mar
(bootloader) kernel.version[3]: 4 18:13:35 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3f87a46
(bootloader) devcfg.git: git=3f87a46
(bootloader) keymaster.git: git=3f87a46
(bootloader) cmnlib.git: git=3f87a46
(bootloader) cmnlib64.git: git=3f87a46
(bootloader) prov.git: git=3f87a46
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tescogb
(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

This is because the boot.img you flashed is not signed by Motorola and its failing to pass verification
If you were trying to unlock the bootloader you should have followed the correct process and enabled adb and oem unlock from the dev options
Never flash firmware on a locked bootloader - if it goes wrong you have no chance of correcting it
You basically have two options now
Try and find firmware that will flash fully on your device
Firmware can be found here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
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
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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
Or take to a repair shop for either a motherboard replacement or if possible flashing with a jtag

Cedric XT-1676 firmware error:

ERROR: This package requires from an Android 8.1 stock ROM build.
Such a bug prevents me from updating the lineage-18.1-20220116-microG-cedric.zip image to a newer version,
e.g. lineage-18.1-20220301-microG-cedric.zip
Code:
fastboot getvar all
(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: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: ZYxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: AADB0F5700000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 06-20-2018
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 1:17:47 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPPS2
(bootloader) ro.build.fingerprint[1]: 8.85-13-6/04442:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.7.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[0]: M8937_22.29.02.69.01u CEDRIC_EMEADSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g6fc7aba (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Feb 7 01:47:04 CST
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=4942431
(bootloader) devcfg.git: git=4942431
(bootloader) keymaster.git: git=4942431
(bootloader) cmnlib.git: git=4942431
(bootloader) cmnlib64.git: git=4942431
(bootloader) prov.git: git=4942431
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(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.061s
I installed the stock rom via fastboot from the image:
CEDRIC_OPPS28.85_13_6_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
using this commands:
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
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
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
Click to expand...
Click to collapse
I installed TWRP, wiped the / system partition, / data, / cache,
then I installed lineage-18.1-20220116-microG-cedric.zip + Magisk.
the system is working fine.
However, the update to lineage-18.1-20220301-microG-cedric.zip stops on a bug with the firmware version.
I download lineage images from here:
cedric
Cheers

Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com

TheFixItMan said:
Answer is already in lineage os thread - your modem in your firmware is outdated
Download the latest retail firmware and flash at least the modem part
fastboot flash modem NON-HLOS.bin
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Click to expand...
Click to collapse
Thank you very much for that firmware link... I was ready to give up.
Oddly, the official Motorola Repair tool does not install a Lineage-friendly version of the stock firmware.
If it helps any other noob, I used this site to install the stock firmware:
Install Stock Firmware on Moto G5 via Fastboot Commands
In this comprehensive tutorial, we will show you how to install stock firmware on Motorola Moto G5 via Fastboot commands and unbrick it.
www.droidwin.com

Hi
I Installed via fastboot:
CEDRIC_RETAIL_8.1.0_OPP28.85-19-4-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
After this operation, my Cedric does not have a unique IMEI number.
As a result, the SIM card does not work at all, I can only make emergency calls.
fastboot getvar all 2>&1| grep -i imei
(bootloader) imei: 356476085352435
I tried to fix IMEI according to this thread:
Moto G5 Cedric - Repair Imei = 0
After being in a LineageOS ROM, I decided to reinstall the Stock Firmware od Moto G5 Cedric through ADB, but after that the phone signal was lost, and both IMEI appear in 0, Has anyone else had that problem, or know the solution?
forum.xda-developers.com
I did several times (after installing stock ROM, after installing LineageOS, after installing LineageOS-microg):
fastboot erase modemst1; fastboot erase modemst2 ; fastboot erase cache
Erasing 'modemst1' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'modemst2' OKAY [ 0.054s]
Finished. Total time: 0.056s
Erasing 'cache' OKAY [ 0.017s]
Finished. Total time: 0.020s
However, to no avail, the phone has no IMEI number on any SIM card.
It seems the XT1676 European version is more resistant to IMEI repair attempts.
Cheers

My IMEI was also zeroed by the stock ROM.
I tried using the recommendations in the following link, but I was ultimately unable to recover the IMEI from within the stock rom. Flashing LOS worked.
Moto g5 plus IMEI 0 after flashing anything? Read on!
After a week of hard troubleshooting, I finally found a quick fix to any IMEI problems you might have, no root, TWRP, Odin, or any nonsense required! Prerequisites: U.S. Moto g5 plus (at least the one I'm using, don't know how well it works on...
forum.xda-developers.com

Same here. Unable to recover IMEI for XT1676. The suggested procedure just does not work in this phone version with latest stock ROM OPP28.85-19-4-2.