[Help] Moto G5 won't turn on and restarts constantly

[Help] Moto G5 won't turn on and restarts constantly - Moto G5 Questions & Answers

Hello people! I hope you are well
First of all, sorry if the English I write with is not good, I am using Google translator (I am from Argentina)
I want to ask for your help (and I apologize in advance if this is not the correct section, it is my first post)
I have a motorola moto G5 xt1670 which restarts without stopping. I tell you; Friday it started with constant reboots and it did not allow me to use the device correctly. On Saturday morning I reinstalled the operating system (android 8.1 stock) using ADB and fastboot commands, so far so great. I walked for a couple of hours correctly, however, after a few hours the phone restarts and stays in a kind of Bootloop which I can NOT remove. It restarts 5 or 6 times in a row, once it is turned on, I can use it for no more than 5 minutes and it restarts again and so on.
I tried installing the operating system through fastboot, through recovery, I did a thousand wipes, from the same recovery I tried to repair the files, I deleted the original rom and I tried installing an alternative rom (lineage OS and pixel experience), and I can swear that the phone does not rips me off.
In fact, after installing pixel experience, the cell phone sends me a message that says the following: "Android system, there is an internal problem with your device, contact the manufacturer for instructions"
The truth is that I don't know what to try now, reinstall the stock firmware more than 5 times, try to downgrade, and the same thing happens. The phone passes the initial configuration, I move it for two minutes on the desktop and it restarts without end.
If anyone has an idea what it might be, I would greatly appreciate your help!
Thank you!

The message you get on pixel experience about an internal problem contact the manufacturer is normal - this is because the system and vendor fingerprint do not match in a hack to pass safetynet
Anyway going back to your problem
If you have downloaded firmware from
https://mirrors.lolinet.com/firmware/moto/cedric/official/
I recommend using the latest retail version
And installed it using these commands in order
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
Without any errors (eg validation error security downgrade error etc)
Then you may have a hardware fault - anything from the battery to the main board or other components
Take it to a repair shop for testing
You can also run an adb logcat but this has to be running at the exact moment the reboot happens & it may show why the phone the restarted
And remove the sdcard if you have one inserted or format it to make sure it's not causing any issues

Related

Guide to restoring factory Image that works?

There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.

I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.

uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
I appreciate the reply. RSD doesn't detect, but ADB can. I can send fastboot commands via the bootloader, so I think drivers are OK. What got me in this mess was flashing the Chinese TWRP posted on the root guide here on XDA so I think the drivers are installed ok. I think it's a Windows thing.
I found that page you're referring to last night and read up on it. I found the retail US stock firmware image posted by another here on XDA and proceeded to go through the steps. After looking, the batch file immediately closed and did nothing. Then I went into the XML file and removed the m in mfastboot. After runnng manually, I found that it kept saying mfastboot.exe is not found. Then it went through every step as I've seen before, but every time a command was finished it would say "Image not signed or corrupt". I believe if I could somehow get RSD lite to work that I would be OK. I'd love to get this thing booting again.

uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...ng-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.

- You are restoring the firmware without wiping the device, i'd try fastboot erase userdata first before flashing the rest, could be worth a try.
- I get "Image not signed or corrupt" when flashing a modified kernel too, but it is flashed regardless.
- I got root with the chinese twrp, the others gave me bootloop.
Good luck.

I too have a freshly-bricked EU dual-SIM Z Play that gives "Image not signed or corrupt" errors when I try to flash recovery and boot. Seen by fastboot, but not by RSD.
edit: more of my saga is here http://forum.xda-developers.com/moto-z-play/help/identifying-firmware-required-phone-t3517360/

yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy

joesee said:
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
Click to expand...
Click to collapse
joesee said:
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...g-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.
Click to expand...
Click to collapse
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin

Milly7 said:
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
Click to expand...
Click to collapse
You just saved my phone. Can I buy you a beer or something?

theodric said:
You just saved my phone. Can I buy you a beer or something?
Click to expand...
Click to collapse
It's all good. Just helping out. Glad it helped.

well i forgot to boot and set up a pin before installing TWRP, soft bricked myself for hours, this thread helped me return to stock so i could set a pin so TWRP would work, THANK YOU!
also if anyone else ends up here, and is having trouble finding the US retail stock image, i used the one from https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/

Is that an official signed image?
Can i use it to relock bootloader?
Thanks!

dyonissos said:
Is that an official signed image?
Can i use it to relock bootloader?
Thanks!
Click to expand...
Click to collapse
None of the images are signed and won't relock the bootloader.

Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.

IncendiaryPyro said:
Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.
Click to expand...
Click to collapse
Yep if you have the right factory image for your device.

Leraeniesh said:
Yep if you have the right factory image for your device.
Click to expand...
Click to collapse
Thank you. I've never had issues doing stuff like this before, but for some reason it scares the hell out of me with this phone. Maybe because I haven't had it for very long, lol. Downgraded to Marshmallow successfully. Hopefully I don't run into any issues in the future that would require an RMA, but out of all the phones I've had over the years, I've only had to RMA a Nexus 5 due to a problem with the screen.

Hi everyone. Is this guide is okay for reteu dual sim? And please point me if there is a firmware for reteu nougat. I softbrick my device and my imei is 0. I want to restore it please guide me as i am a noob in fastboot commands and steps. Thanks in advance

Vitxlss said:
yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy
Click to expand...
Click to collapse
do you have rooted device with twrp (maybe) ?
also, is the boot.img you got from Android 7 or 6.xx ?
Thanks

I use the DOWNGRADE script found here :
https://drive.google.com/file/d/0B134drJ4-Ed0MHQ5aE1wUmp5eFk/view
The original discussion here :
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Note that the original script is not ideal. The actual script came from @-=MoRpH=- on comment #4

How do I relock bootloader and go back to stock on moto G5s?

A friend unlocked its bootloader and tried to root it with no success.
The phone works but only boots through fastboot, because when I press the power button it enters fastboot mode instead of booting.
I don't know what happened, as I was not the one who tried to root, so I just wanted to know how to revert back to stock and relock the bootloader, since the phone works normally.

freeZbies said:
A friend unlocked its bootloader and tried to root it with no success.
The phone works but only boots through fastboot, because when I press the power button it enters fastboot mode instead of booting.
I don't know what happened, as I was not the one who tried to root, so I just wanted to know how to revert back to stock and relock the bootloader, since the phone works normally.
Click to expand...
Click to collapse
If they flashed twrp and your phone can only be started normally through the bootloader see
https://forum.xda-developers.com/g5/how-to/fix-phone-reboots-recovery-mode-started-t3705325
If you want to root the phone stock can only be rooted with a system root
Most roots now use a systemless root which is not compatible with the stock kernel
You either need a custom rom to use the latest magisk root or if you want to stick with stock use an old version of magisk (can't remember which really old version works) or use supersu but flash the config zip first and set to system as default will be systemless
With regards to flashing stock download firmware and run these fastboot commands assuming you have fastboot set up on your pc
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (do not flash unless you want to repartition the phone)
fastboot flash bootloader bootloader.img (do not flash unless you really need to replace the bootloader)
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (ignore any error)
fastboot erase clogo (ignore any error)
fastboot oem fb_mode_clear
fastboot reboot
To lock the bootloader do the above and then go back to the bootloader mode & enter these fastboot commands
fastboot oem lock
fastboot oem lock (yes type it again)
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 boot boot.img
fastboot oem lock
Then once restarted refresh all the firmware again with the commands from earlier
I have seen though that some boot.img are not officially signed so it may not lock

TheFixItMan said:
If they flashed twrp and your phone can only be started normally through the bootloader see
https://forum.xda-developers.com/g5/how-to/fix-phone-reboots-recovery-mode-started-t3705325
If you want to root the phone stock can only be rooted with a system root
Most roots now use a systemless root which is not compatible with the stock kernel
You either need a custom rom to use the latest magisk root or if you want to stick with stock use an old version of magisk (can't remember which really old version works) or use supersu but flash the config zip first and set to system as default will be systemless
With regards to flashing stock download firmware and run these fastboot commands assuming you have fastboot set up on your pc
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (do not flash unless you want to repartition the phone)
fastboot flash bootloader bootloader.img (do not flash unless you really need to replace the bootloader)
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (ignore any error)
fastboot erase clogo (ignore any error)
fastboot oem fb_mode_clear
fastboot reboot
To lock the bootloader do the above and then go back to the bootloader mode & enter these fastboot commands
fastboot oem lock
fastboot oem lock (yes type it again)
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 boot boot.img
fastboot oem lock
Then once restarted refresh all the firmware again with the commands from the first post
I have seen though that some boot.img are not officially signed so it may not lock
Click to expand...
Click to collapse
Yes, thank you.
I was checking the relocking guides here in xda and seems signed boot images are the problem. Anyways, I'll check to see if it works.

freeZbies said:
Yes, thank you.
I was checking the relocking guides here in xda and seems signed boot images are the problem. Anyways, I'll check to see if it works.
Click to expand...
Click to collapse
Also just noticed you are talking about the Moto G5s - this is the Moto G5 Cedric forum
The Moto G5s forum is located
https://forum.xda-developers.com/moto-g5s

TheFixItMan said:
Also just noticed you are talking about the Moto G5s - this is the Moto G5 Cedric forum
The Moto G5s forum is located
https://forum.xda-developers.com/moto-g5s
Click to expand...
Click to collapse
Oh thanks, I'm gonna check it there, because it's indeed a Moto G5S.
Only thing I'd like to say is that on the XDA Labs app the only forum shown when I search for Moto G5S is the Moto G5 forum, no variants are presented, whom should I report this to, so that it can be fixed?

freeZbies said:
Oh thanks, I'm gonna check it there, because it's indeed a Moto G5S.
Only thing I'd like to say is that on the XDA Labs app the only forum shown when I search for Moto G5S is the Moto G5 forum, no variants are presented, whom should I report this to, so that it can be fixed?
Click to expand...
Click to collapse
No idea - don't use the app
The email on the Google play listing says
[email protected]
The thread for the app is
https://forum.xda-developers.com/android/apps-games/labs-t3241866

XT1670 with audio issue

Ohayo!
The phone has problems with audio. However, I think it can be more or less determined what it is due to. Two days ago the music started to be heard as if it were escaping from The Matrix. If you locked the device, the music would stop. Then the bootloop started, constant bootloop. The only way the phone works is in total silence mode. If the phone is started with sound, it is necessary to clean the cache so that it starts again in total silence mode. Sometimes it doesn't even start the audio, directly without sound engine. If any application tries to access the sound, bootloop starts. If you want to record a video, the phone goes into bootloop. If you get a notification with sound, the phone restarts. If you want to listen to music, the phone will play it for 10 seconds. Then the music will be distorted as if it were a horror movie. Finally the phone will stop responding and after 5 seconds it will enter bootloop. I'll try to use a rom here, but I guess the problem is hardware.
What do you think? I would like to know your opinions.
Thank you for reading this short summary.
Have a nice day

The phone was already formatted with official firmware (Motorola LMSA) without positive results. In Windows manager it appears as 'MPT Device' instead of its normal ID.

If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
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
Note backup any personal files from internal storage to your pc first

TheFixItMan said:
If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
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
Note backup any personal files from internal storage to your pc first
Click to expand...
Click to collapse
Yep, it was a hardware problem.

momentarily I bought a Haylou GT1 to solve the problem. The bluetooth codec works well in terms of audio, and even lets you listen to WhatsApp conversation. However the phone has random reboots and each time it does it it tries to start the audio. The results are clearly appalling. The phone reboots 16 (or more) times before achieving stability. I want to root the phone and prevent it from starting the audio hardware, until I can get it for service. Which line should I delete so that the audio service does not start?

He.Art said:
momentarily I bought a Haylou GT1 to solve the problem. The bluetooth codec works well in terms of audio, and even lets you listen to WhatsApp conversation. However the phone has random reboots and each time it does it it tries to start the audio. The results are clearly appalling. The phone reboots 16 (or more) times before achieving stability. I want to root the phone and prevent it from starting the audio hardware, until I can get it for service. Which line should I delete so that the audio service does not start?
Click to expand...
Click to collapse
Probably in your build prop somewhere

Okay. I guess it will be trial and error

Help. The smartphone does not see the USB

Sorry for my english, translated by google
Hi. Can someone help or at least tell you in which direction to look. Moto (lenovo) G5 XT1675 cedric RETGB device. CEDRIC_OPP28.85_19_4_2_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml (the latest firm on Android 8.1.0) and over it via tvrp lightweight stock on 7.0 android was flashed. In search of a problem, I went through a lot: I replaced the board with yusb, flashed the Rescue and Smart Assistant program from Lenovo (with the firmware that the program told me), unlocked the bootloader + tvrp and root. I tried a lot of custom, but I didn’t solve the problem. The essence is the phone in the included state. does not see usb (in any way, neither charging nor connecting to a computer) but it is worth rebooting the device with the cable connected and everything works. But if you disconnect the phone cable. It no longer sees it until the next reboot. If the menu is loaded into Factory mode through the fastboot without connecting. cable, then when the bodies are connected, it sees it but only the first time. comp. the bodies are normally charged, stitched, etc., the TVRP also does not see the cable (also resolves with a reboot) I personally think about the bootloader, but having the latest version, there is nothing to update and it is risky to roll back to a version below (you can get a brick that cannot be cured with a simple firmware)

I say the same to most people with these types of issue
If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
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
Note backup any personal files from internal storage to your pc first

TheFixItMan said:
I say the same to most people with these types of issue
If flashing stock firmware via fastboot doesn't solve the problem then it's a hardware issue & not software
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you don't know what to choose then choose the latest retail image
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
Note backup any personal files from internal storage to your pc first
Click to expand...
Click to collapse
Thank you. I know about all this. I made the backup first of all after unlocking the bootloader and the TVRP firmware. The first time I stitched with Rescue and Smart Assistant https://www.motorola.com/us/rescue-and-smart-assistant/p. I think that this program knows exactly what firmware I need. But it did not help In the off state, the device responds normally to the cable (it charges, connects to the PC where all the drivers are installed, I flashed it many times and tried various factory firmware) but if you connect the cable after the logo image (logo.bin) , until you reboot the device with the cable connected and if you turn it off. That is, when the android system is loaded, the device stubbornly does not want to see the connection. I think that the problem is not in the hardware type because with the firmware I would get a bunch of errors or just could not connect the device but everything works

Smartphone Killer said:
Thank you. I know about all this. I made the backup first of all after unlocking the bootloader and the TVRP firmware. The first time I stitched with Rescue and Smart Assistant https://www.motorola.com/us/rescue-and-smart-assistant/p. I think that this program knows exactly what firmware I need. But it did not help In the off state, the device responds normally to the cable (it charges, connects to the PC where all the drivers are installed, I flashed it many times and tried various factory firmware) but if you connect the cable after the logo image (logo.bin) , until you reboot the device with the cable connected and if you turn it off. That is, when the android system is loaded, the device stubbornly does not want to see the connection. I think that the problem is not in the hardware type because with the firmware I would get a bunch of errors or just could not connect the device but everything works
Click to expand...
Click to collapse
Like I said - if you flashed stock firmware exactly like I posted above with the latest retail firmware from the site in the link and you still have issues it's a hardware problem - either the board or the USB cable you are using

Downgrade Z2 play pie to oreo

Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?

Anything below Pie is vulnerable to the X-helper rootkit... we were just talking about it in another thread. It's a real nasty little bugger.

But its posible? I just want to get all the features back, even, i dont know what is that thing, if they have some to hack me i dont have to much to lose anyways, just want to downgrate to fix the fingerprint bug from oreo

Don't know. Hopefully someone with this device can help you.

iMaxwell said:
Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?
Click to expand...
Click to collapse
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running

marcost22 said:
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running
Click to expand...
Click to collapse
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat

iMaxwell said:
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat
Click to expand...
Click to collapse
that's probably the worst available way to do it. If your phone didn't originally receive it via OTA, then you are forcing it the wrong way.
If you want to go back to nougat all you need to do is download the official N firmware, then flash everything but bootloader and gpt

What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that

I follow the steps on this video

iMaxwell said:
I follow the steps on this video
Click to expand...
Click to collapse
Yeah that is just terrible
iMaxwell said:
What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that
Click to expand...
Click to collapse
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice

marcost22 said:
Yeah that is just terrible
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice
Click to expand...
Click to collapse
The issues begin on official oreo, i upgrade nougat to oreo then, fingerprint option dissapear, then i upgrade to pie from oficial firmware but issues still remain

It really works? I didnt find any video or post about downgrade like that

Yes it does work, but it's not recommended, that's why you don't find much info
iMaxwell said:
It really works? I didnt find any video or post about downgrade like that
Click to expand...
Click to collapse

Develop Bugs

welcome