Database Users

need help urgent

hi everyone i am running on nougat stock rom successfully unlock my bootloader and follow this step to root my phone but after installing twrp and flash supersu and i restart my phone it again boots into twrpi am not able to boot into system.
It only boot into fastboot and recovery
plz help me here i have indian moto g4 plus.
this the link which i follow
https://www.youtube.com/watch?v=dK2uacpjGwc&t=64s

Yeah, that Youtube guide is for rooting under Marshmallow - Nougat is more stringent and rooting with the stock kernel, as you've found out, will cause boot issues. A reliable way to root on Nougat is to flash a custom kernel onto your device.
Do you have a backup in TWRP to fall back to?
If so, and you've restored it, or if you don't have a backup of your system, then try rebooting back to TWRP and flash ElementalX v1.04 onto your device (either from a SD card or by plugging your device into your computer and try using 'adb push' to transfer ElementalX v1.04 to your device's internal storage). https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 for ElementalX. Hopefully then, you'll be able to boot.
For rooting under Nougat with SuperSU, have a look at this guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918

I faced the same problem when I unlocked my bootloader because for some reason on some models the phone will wipe the whole system partition instead of just the data. If you want to use a custom rom then you are able to flash that with twrp no problems but if you want the stock rom back you will hava to flash it either with fasboot (will flash stock recovery) or use a twrp backup someone made of the stock rom (nougat) I just did a google search for *moto g4 plus stock rom twrp backup* and clicked on the first link which contains guides for both methods (I cannot post links sorry)
Hope I could help

echo92 said:
Yeah, that Youtube guide is for rooting under Marshmallow - Nougat is more stringent and rooting with the stock kernel, as you've found out, will cause boot issues. A reliable way to root on Nougat is to flash a custom kernel onto your device.
Do you have a backup in TWRP to fall back to?
If so, and you've restored it, or if you don't have a backup of your system, then try rebooting back to TWRP and flash ElementalX v1.04 onto your device (either from a SD card or by plugging your device into your computer and try using 'adb push' to transfer ElementalX v1.04 to your device's internal storage). https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 for ElementalX. Hopefully then, you'll be able to boot.
For rooting under Nougat with SuperSU, have a look at this guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Click to expand...
Click to collapse
Tried element kernel but the results will be same boot into twrp
Can anyone have stock rom for indian dual sim variant of moto g4 plus firmwares?

rakesh595160 said:
Tried element kernel but the results will be same boot into twrp
Can anyone have stock rom for indian dual sim variant of moto g4 plus firmwares?
Click to expand...
Click to collapse
If you're after Nougat v7.0 Dec 2016, NPJ25.93-14 https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Nougat v7.0 March 2017, NPJS25.93-14.4 https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Bear in mind flashing either may wipe your device (and thus your data and internal storage), if you can, try to back up your key files via TWRP to your computer.
If you're downloading the same firmware as the build you have at the moment, you may be able to save your data and restore your system by using these commands, however be prepared to use all the flash commands (including wipes) if it doesn't work:
Code:
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

echo92 said:
If you're after Nougat v7.0 Dec 2016, NPJ25.93-14 https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Nougat v7.0 March 2017, NPJS25.93-14.4 https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Bear in mind flashing either may wipe your device (and thus your data and internal storage), if you can, try to back up your key files via TWRP to your computer.
If you're downloading the same firmware as the build you have at the moment, you may be able to save your data and restore your system by using these commands, however be prepared to use all the flash commands (including wipes) if it doesn't work:
Click to expand...
Click to collapse
I just flash revivour os ut boots my phone well nkw how do i root my devices?

rakesh595160 said:
I just flash revivour os ut boots my phone well nkw how do i root my devices?
Click to expand...
Click to collapse
If you've flashed revivorOS, the rooting instructions are on the opening post of that ROM... https://forum.xda-developers.com/mo...om-npjs25-93-14-4-deodexed-debloated-t3587180

Please help. Not sure what to do next.

Hi all,
I have a Moto G5 Plus that I brought on Amazon Prime day (11/07/17). and after trying to install TWRP I have ran into problems.
Heres what happened and where I'm left.
1) I unlocked the Bootlloader via moto website. No problems I now receive the BS message about the phone being unlocked.
2) Tried flashing twrp_3.1.1-0_potter.zip using "fastboot flash recovery twrp_3.1.1-0_potter.img"
Whenever I performed this command and rebooted in recovery I was never taken into the TWRP screen, but taken a screen showing a droid on it back with a message saying no command. I found how to bring up the command menu, but trying to flash the custom roms from the stock recovery always failed.
3) I used this article https://forum.xda-developers.com/g5-...-plus-t3605667 and found using this did allow me to boot into the TWRP screen. The only difference i noticed was that when i used the article mentioned above to get into TWRP the phone displayed the Moto boot ami before going into TWRP. It never did this when i used the Flash command manually.
4) Once in TWRP i flashed supersu and the RR .img, wiped cache etc..
On exiting TWRP I was asked whether I wanted TWRP installed as a system app, i selected yes to this question and now.....
5) BRICKED!!!
My moto will only boot into fastboot now and I get this message:-
Start up failed:
the bs about software repair assistant etc.
ap fastboot Flash Mode (secure)
Error: failed to load kernel!
Fastboot Reason: Fall-through from charge boot mode
usb....
6) I tried using this article https://forum.xda-developers.com/g5-plus/how-to/npn25-137-33-stock-firmware-t3577081
But I'm unsure of this version to use?
My question is can anyone help me to at least get my phone working again. Thanks will be paid.

JammieB said:
I have a Moto G5 Plus that I brought on Amazon Prime day (11/07/17). and after trying to install TWRP I have ran into problems.
Click to expand...
Click to collapse
Which Amazon Moto G5 Plus did you buy on Prime Day? The cheaper subsidized Amazon Prime version with ads or the more expensive non subsidized version without ads?
Apparently you cannot unlock the bootloader on the subsidized ad based Amazon Prime version. This is well discussed. One such discussion from the Lenovo/Moto support forum:
https://forums.lenovo.com/t5/Moto-G5-Moto-G5-Plus/Is-there-anyway-to-unlock-my-Moto-G5-Plus-from-Amazon/td-p/3638019
If one does a forum search on this site they'll find past discussions indicating the bootloader on Amazon Prime subsided Moto G5 Plus phones cannot be unlocked.

Try the Toolkit.
Once in it flash the TWRP and boot_image and try rebooting. If that doesn't work flash the Stock ROM and then flash the TWRP and boot_image. Once you get those flashed you should be able to flash the latest TWRP using fastboot.
Please let me know if that fixed it.
Thanks,
CP

cyber_prometheus said:
Try the Toolkit.
Once in it flash the TWRP and boot_image and try rebooting. If that doesn't work flash the Stock ROM and then flash the TWRP and boot_image. Once you get those flashed you should be able to flash the latest TWRP using fastboot.
Please let me know if that fixed it.
Thanks,
CP
Click to expand...
Click to collapse
Thanks for the suggestion, however I have tried this toolkit already and when connecting the USB cable, the toolkit only ever says connecting to device, but never manages to actually connect. As such, no command from the toolkit can be run, as when tried I get a "no device" message.
Also when I try to use the toolkit to install Windows 64bit driver, the install stops telling me I have a newer driver installed already.
Do you think I should uninstalled the newer device driver or should the toolkit still connect using the newer driver?

bennor3814 said:
Which Amazon Moto G5 Plus did you buy on Prime Day? The cheaper subsidized Amazon Prime version with ads or the more expensive non subsidized version without ads?
Apparently you cannot unlock the bootloader on the subsidized ad based Amazon Prime version. This is well discussed. One such discussion from the Lenovo/Moto support forum:
https://forums.lenovo.com/t5/Moto-G5-Moto-G5-Plus/Is-there-anyway-to-unlock-my-Moto-G5-Plus-from-Amazon/td-p/3638019
If one does a forum search on this site they'll find past discussions indicating the bootloader on Amazon Prime subsided Moto G5 Plus phones cannot be unlocked.
Click to expand...
Click to collapse
Im 100% confident that my moto has had its bootloader unlocked and that I was not sold a Moto G5 Plus with amazon ads.....
Thanks for your suggestion though.

FIXED back to stock rom. Here's what I did:-
1) Downloaded the stock rom from https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084
Used the mega link it took 5mins (1.4 mbps) to download.
2) Then run these commands:- (thanks to https://forum.xda-developers.com/member.php?u=5033408)
fastboot oem lock begin
fastboot oem lock begin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (gave error about bootloader)
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot oem lock
fastboot reboot
It still see the annoying unlocked bootloader screen, but my moto boots into the stock rom.
I'm not giving up on getting a custom rom onto this device, but thanks to anyone who's helped me to get back to square one.

JammieB said:
Thanks for the suggestion, however I have tried this toolkit already and when connecting the USB cable, the toolkit only ever says connecting to device, but never manages to actually connect. As such, no command from the toolkit can be run, as when tried I get a "no device" message.
Also when I try to use the toolkit to install Windows 64bit driver, the install stops telling me I have a newer driver installed already.
Do you think I should uninstalled the newer device driver or should the toolkit still connect using the newer driver?
Click to expand...
Click to collapse
I didn't install the drivers with the toolkit. Was your phone connected to it in fastboot mode? That's what I had to do to get it to detect mine.
If you can't get the toolkit to work you can still use fastboot to flash the included version of TWRP and the modified boot_image. They're located in TOOLKIT_DIR\resources\app.asar.unpacked\files.
CP

Help getting stock rom

Hi, I'm trying to get my phone back to normal state. It was on Nougat 7.0 I would like to get it on 6.0.1. but I'm so new know where to begin. It's also a Republic Wireless (not a major carrier) so I'm not sure how to start messing with this thing. I ran in to a problem last night trying to put on Magisk because I wanted the option of hiding root and it got stuck in a bootloop. I wasn't sure i could get it back but i did with Lineage OS now I'm trying to get it back to some degree of what I had it. I would like tips putting on Android 7.0 if I choose to upgrade to it again but mostly I want to know a way to put it on A Marshmallow.

1)Rooting on stock Motorola Nougat ROMs is different to rooting on 6.0.1. Due to the stricter anti-rooting measures on stock 7.0 kernels, you need a custom kernel (e.g. ElementalX), else you'll bootloop as you've discovered. If you wish to root in future on stock 7.0, this guide might be useful: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You can use magisk instead of SuperSU.
2)If you want to go back to stock Nougat, are you on the retus software channel (might be under Settings, but I'm not sure if it'll show up on Lineage OS)? If you are, then this NPJ25.93-14.7 firmware might be for your device https://androidfilehost.com/?fid=817906626617945295 Please doublecheck that this is the correct firmware for your device before flashing. Also, be aware that flashing stock ROMs will wipe TWRP, your data and may wipe your internal storage, so back up before flashing. Nougat stock ROM firmware may also offer better compatibility for the custom Nougat/Oreo ROMs out there.
3)If you previously were on stock Nougat, can I ask why you wish to downgrade to Marshmallow (MM)? There's MM (6.0.1) stock ROMs out there (MPJ24.139-64, which should be the latest US build for MM: https://androidfilehost.com/?fid=312978532265364350 ). However, if you were on stock Motorola Nougat previously, especially on the June/September 2017 stock Motorola ROMs, I personally would advise against downgrading, or if you do choose to flash stock Marshmallow, do not accept OTA updates to update (e.g. to Nougat). If you downgraded, then in this case you'll have a Marshmallow system, but a Nougat bootloader - bootloaders typically won't downgrade. By taking a MM to Nougat OTA, you may corrupt your bootloader and hard brick your device (i.e. won't turn on, blinking LED, not recognised by your computer etc, device not usable and data not accessible.). We do have a way to recover a device hardbricked, but it's a last resort really. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Custom MM and Nougat ROMs don't mess with the bootloader, so should be safer.
I leave it up to you about what you wish to do with your device. Good luck whatever you choose.

How do I install the firmware? I tried flashing it in twrp, and it said invalid zip

endleesss said:
How do I install the firmware? I tried flashing it in twrp, and it said invalid zip
Click to expand...
Click to collapse
Stock ROM firmware zips are not flashable in TWRP. You need fastboot to flash stock ROMs (following a procedure like https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ), bear in mind that flashing these stock ROMs will usually replace TWRP with the stock recovery. Also they will revert your device to full stock.
Erasing your data will also happen unless you omit the erase userdata command, but if you're switching from a custom ROM back to stock, you may have to erase data anyways for stability.

Thank you!
Hoping this will help someone, this is what happened to me:
My phone is XT1625 Build # NPJ25.93-14.7
I flashed TWRP, then backed up, then flashed supersu. resulting in bootloop, i restored using the twrp back up, still bootloop.
To fix, download stock firmware: download https://androidfilehost.com/?fid=817906626617945295
Unzip the file, then in In adb run these commands one at a time.:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
Phone is back to stock

Moto G4 only boots in fastboot

Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?

squanch123 said:
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
Click to expand...
Click to collapse
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.

squanch123 said:
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
Click to expand...
Click to collapse
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?

echo92 said:
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
Click to expand...
Click to collapse
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?

squanch123 said:
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
Click to expand...
Click to collapse
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?

echo92 said:
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
Click to expand...
Click to collapse
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.

squanch123 said:
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
Click to expand...
Click to collapse
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).

echo92 said:
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
Click to expand...
Click to collapse
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?

squanch123 said:
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
Click to expand...
Click to collapse
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).

echo92 said:
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
Click to expand...
Click to collapse
Yes that worked
Thank you very much for your help :victory:

Stuck in Bootloop

I'm currently stuck in a bootloop with a rooted (Prime Exclusive) Moto G5 Plus. Every time I turn on the phone or restart the phone, I keep getting sent to TWRP Recovery, and can't boot into the system. What I want to do is just restore this phone to the stock firmware and factory reset my device. Please help me.

FamilyGuy0395 said:
I'm currently stuck in a bootloop with a rooted (Prime Exclusive) Moto G5 Plus. Every time I turn on the phone or restart the phone, I keep getting sent to TWRP Recovery, and can't boot into the system. What I want to do is just restore this phone to the stock firmware and factory reset my device. Please help me.
Click to expand...
Click to collapse
Download your actual firmware, unpack it into your fastboot folder (recommend: Minimal ADB & Fastboot), bring your device in fastboot mode and flash everything one after the other:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Sent from my Moto G5 Plus using XDA Labs

@Wolfcity Can you be more clear as to what you mean by my "actual firmware"? I'm not sure what firmware version my device is on, nor can I find any repository on the Internet to download said firmwares for the (Prime Exclusive) Moto G5 Plus.

FamilyGuy0395 said:
@Wolfcity Can you be more clear as to what you mean by my "actual firmware"? I'm not sure what firmware version my device is on, nor can I find any repository on the Internet to download said firmwares for the (Prime Exclusive) Moto G5 Plus.
Click to expand...
Click to collapse
As you have flashed a TWRP you must have your bootloader unlocked. You need the firmware that your device was on when you did that.
Downgrading i.e. flashing an older firmware can brick your device.
The newer firmwares for reteu/retus are ending on 93-x, like
POTTER_NPNS25.137-93-4 (january security patch)
POTTER_NPNS25.137-93-8 (march security patch)
POTTER_NPNS25.137-93-10 (april security patch)
Earlier ones had another number scheme.
Firmware for India, Brazil and Asia Pacific is ending on 92-x.
I don´t know the Prime exclusive edition but I don´t think that it uses another firmware. But I heard of a Amazon version with ads and an unlockable bootloader?
How did you unlock then? Or are there different versions?

@Wolfcity I really don't know how to respond, but I can't figure this out. I don't know what firmware version to install, I don't know where I can find the firmware version, and whenever I try to run a fastboot command through adb I get stuck on an infinite "waiting for device" message. Can you please help me with step-by-step instructions on how to fix this?

FamilyGuy0395 said:
@Wolfcity I really don't know how to respond, but I can't figure this out. I don't know what firmware version to install, I don't know where I can find the firmware version, and whenever I try to run a fastboot command through adb I get stuck on an infinite "waiting for device" message. Can you please help me with step-by-step instructions on how to fix this?
Click to expand...
Click to collapse
Here are some firmware sources:
https://androidfilehost.com/?a=show&w=files&flid=171014
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1
I can´t tell you on which firmware you were when you unlocked your bootloader. And the next problem is that you can´t run any fastboot commands, you need fastboot to flash the stock firmware with the commands I posted above.
Have you the latest Motorola drivers and something like Minmal ADB & Fastboot installed?

1) from TWRP run "Bootloader reboot"
2) send the command "fastboot devices" receive the serial number of the phone. Once you have obtained the serial download "POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt" and execute the commands as suggested.

@Wolfcity, @antonio52 Thank you guys SO much! I finally got around to doing this, and my device is running perfectly well now! I couldn't have done it without you!

FamilyGuy0395 said:
@Wolfcity, @antonio52 Thank you guys SO much! I finally got around to doing this, and my device is running perfectly well now! I couldn't have done it without you!
Click to expand...
Click to collapse
You're welcome. Nice to hear you got it working again.
Sent from my Moto G5 Plus using XDA Labs