(Urgent Help!) bootloop after normal update, bootloader locked. no ADB, no OEM unlock

[Rush]

I recently found a moto g5 in one of my fellow "old tech" drawers and decided to turn it on, it was on the
1. May 2018
Security patch on nougat, I decided to use the inbuilt system updater to go to Oreo, and now....it crashes during flashing process after about 25-30% completion,
Now im guessing boot or System is not properly installed due to the zip file having aborted mid-flash
Recovery doesn't properly boot as that is used to install the update and thus imidiately goes to doing that

Also, it hang up during installation on random times, it basically has a record of 2mins of not crashing whilst still being stuck on 30%

I got it to "boot" when trying factory mode, yeah it crashed mid boot animation...not a help

Any suggestions? EDL mode maybe?

 

[TheFixItMan]

Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/

You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778

If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop

 

[Rush]

Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/

You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778

If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop

SOMEHOW it just decided to boot, I have never seen such behaviour, even on my g5s which I had for a while, (and am currently daily driving to school if it wasn't closed....NEVER
Maybe I'll unlock it and try somehow recreating it? Well it's in physically rough shape but all components inside are fine...so that can't be the reason....?

 

[anonymous724]

My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?

 

[riyan65]

My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?

Flash the stock rom and boot the device. But this will format the device.

To save data, remove the command fastboot erase userdata

Fastboot erase customisation.

Apps may be gone, but files In internal storage will be safe, like download,photos, music.

 

[anonymous724]

Flash the stock rom and boot the device. But this will format the device.

To save data, remove the command fastboot erase userdata

Fastboot erase customisation.

Apps may be gone, but files In internal storage will be safe, like download,photos, music.

no luck on this front, gets to the passcode screen, write in passcode then motorola logo shows and screen keeps on turning off and on.

Thanks for the effort though, much appreciated

 

[Powdered Toast Man]

Mine is similar to yours. Initially was on permanent loop of the following:

1. Boot to moto g splash screen... Repeat

2. Boot to lock screen then usually a few loops of 1. (after entering the patter or left Idle)

The phone initially didnt have any developer options enabled.

I wiped cache using recovery mode. Restarted and pretty much the same thing except that it would on rare occasions actually fully boot up usually only last a few minutes before cycling between steps 1 and 2 above.

I used those rare boot ups to backup all files and enable any USB debugging /oem unlock (incase I need to use a solution dependent on these being enabled.)

Factory resetted it and its still the same with the random successful boot amongst the numerous failed ones.

I managed to hook it up to Lenovo's Lmsa and flash the latest ROM. Now I get a lot more successful boots but still loops every so often. The downside is that I can no longer do any functions that make use of the audio/ mic/ video (can take pictures). If I do then it will crash and loop.

The hardware test on the LMSA passed for every component before flashing to the latest version. Post update it predictably fails on the audio/ mic components.

I guess I'll have to go back to the old version to see I get the audio back.