Database Users

Nexus 7 Bricked??/Broken

Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks

download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.

Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!

MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance

You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app

dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.

YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!

dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app

Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?

Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.

jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk

[GUIDE] Return to stock and "Official status" - Moto X 2014

Return to stock - Moto X 2014​
What you need:
Minimal ADB and Fastboot
Stock ROM Alternative 1 (Faster option)
Stock ROM Alternative 2 (Downloads speed are super slow if you are not premium)
Moto fastboot (mfastboot.exe) (This one is only needed if the file system.img is too big to flash (More than 500MB))
Steps:
Connect your phone to your computer and make sure to have "USB Debugging" enabled (About phone > Tap several times "Build number" > Go back > Developer options > Enable USB debugging)
Make sure your phone is at least 50% charged
Open ADB cmd (MAF32.exe)
Run this command to make sure it recognizes your phone.
Code:
adb devices
After it recognizes it, run the command (It should reboot into bootloader)
Code:
adb reboot bootloader
Unzip the downloaded STOCK ROM into the same folder as where you installed minimal ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
Open the "flashfile.xml" file with any text editor
The file tells you how to flash the files into your phone
Mine said:
Code:
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 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
The sistem.img part was a big file divided into 9 files about 250MB each. If your system.img is bigger than 500MB you'll need to use mfastboot.
Do the commands one by one.
After you are done with everything, reboot and it should say in the Status: Official
EDIT 24/04/2016:
- Added faster alternative download to stock ROMS.

Tovagulet said:
Return to stock - Moto X 2014​
What you need:
Minimal ADB and Fastboot
Stock ROM (That's the only download page with like all the stock ROMs, downloads speed are super slow if you are not premium)
Moto fastboot (mfastboot.exe) (This one is only needed if the file system.img is too big to flash (More than 500MB))
Steps:
Connect your phone to your computer and make sure to have "USB Debugging" enabled (About phone > Tap several times "Build number" > Go back > Developer options > Enable USB debugging)
Make sure your phone is at least 50% charged
Open ADB cmd (MAF32.exe)
Run this command to make sure it recognizes your phone.
Code:
adb devices
After it recognizes it, run the command (It should reboot into bootloader)
Code:
adb reboot bootloader
Unzip the downloaded STOCK ROM into the same folder as where you installed minimal ADB (C:\Program Files (x86)\Minimal ADB and Fastboot)
Open the "flashfile.xml" file with any text editor
The file tells you how to flash the files into your phone
Mine said:
Code:
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 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
The sistem.img part was a big file divided into 9 files about 250MB each. If your system.img is bigger than 500MB you'll need to use mfastboot.
Do the commands one by one.
After you are done with everything, reboot and it should say in the Status: Official
Click to expand...
Click to collapse
the easiest way is using RSDlite and chose flashfile.xml to flash. Done !

md07 said:
the easiest way is using RSDlite and chose flashfile.xml to flash. Done !
Click to expand...
Click to collapse
Not everybody uses windows. I am a linux user, so no RSDLite is available. Also not available for mac. This guide is great for people who can't use RSDLite or need to do specific steps only instead of blindly trusting RSDLite.
Sent from my XT1095 using Tapatalk

Thanks, I'm also not fond of flashing ROM images via program scripts, I prefer the old step by step method. :thumbup:

Any word on XT1095 or XT1097_retca-retca? How freaken hard is it to capture an OTA or factory image these days?

I still get "Software status: Modified"

md07 said:
the easiest way is using RSDlite and chose flashfile.xml to flash. Done !
Click to expand...
Click to collapse
AGISCI said:
Not everybody uses windows. I am a linux user, so no RSDLite is available. Also not available for mac. This guide is great for people who can't use RSDLite or need to do specific steps only instead of blindly trusting RSDLite.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Also, RSDLite does not work in Windows 10.
Thanks for tutorial.

Is this for Stock 6.0 Firmware : VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip

thomstrack said:
Also, RSDLite does not work in Windows 10.
Click to expand...
Click to collapse
it works with Windows 10... try to upgrate RSD to the latest version

nikky2u20 said:
Is this for Stock 6.0 Firmware : VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
Click to expand...
Click to collapse
well, it's got all the right words and numbers (although the one I'm running from the TWRP method thread is MPE24.11-18, and this appears to be MPE24.49-18). I'm downloading it now - has anybody else tried it?

niciolaux said:
it works with Windows 10... try to upgrate RSD to the latest version
Click to expand...
Click to collapse
The latest version that I see is the 6.2.4, and does not work in Windows 10.
There is another version?

unfnknblvbl said:
I still get "Software status: Modified"
Click to expand...
Click to collapse
I think "Modified" means you unlocked the bootloader, right?
I used to successfully update my xt1095 to 5.1 by these steps:
unroot by using the uninstalling root function in the SEusers, and flash the stock recovery.img back.
download the OTA update, and let it flash my phone automatically.
got a stock 5.1. then you may do whatever you want.

unfnknblvbl said:
I still get "Software status: Modified"
Click to expand...
Click to collapse
+1
This method don't change to Status Official.
thomstrack said:
Also, RSDLite does not work in Windows 10.
Thanks for tutorial.
Click to expand...
Click to collapse
RSD Lite works perfectly in Windows 10.

I followed these steps, and reflashed to 5.1-21.3, then update to 21.6 (security patch).
Now I'm running 6.0! The OTA works!

We def need to get this stock image re-upped, because I could get gray hairs waiting for this to download... Anyone have any other links? Thanks

help!!! I downloaded the recovery image from the official motorola site, i have system image of 2 Gb and have no idea about how to flash the system image. I have a folder called windows(which was included in the recovery image zip that i downloaded) that folder contains a fastboot.exe file so is that the mfastoot file?If yes then how do i use it?
EDIT- Solved!

nikky2u20 said:
Is this for Stock 6.0 Firmware : VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
Click to expand...
Click to collapse
unfnknblvbl said:
well, it's got all the right words and numbers (although the one I'm running from the TWRP method thread is MPE24.11-18, and this appears to be MPE24.49-18). I'm downloading it now - has anybody else tried it?
Click to expand...
Click to collapse
Can confirm, this is the real deal. Works a treat, and none of those RPC errors that plagued me on the TWRP backup image.

I am on Brazilian frimware with 6.0 now on my device, but my actual model of the device is xt 1092 Indian version.
I want to go back to Indian frimware. Have anyone tried downgrading from 6.0 Brazilian frimware to 5.1 Indian frimware, is it possible? Is full image of 6.0 out for xt 1092, if so please share the link.
Sent from my XT1097 using Tapatalk

unfnknblvbl said:
Can confirm, this is the real deal. Works a treat, and none of those RPC errors that plagued me on the TWRP backup image.
Click to expand...
Click to collapse
Thnx for the info m8.
Could you upload it to something that is faster then filefactory perhaps? Cause this **** is SLOW
Thnx in advance
Cheers
Edit: it is also available here: https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
With thnx to @salaesp for finding the MU folder

Used this firmware on my MotoX
VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
And was able to get back to the stock state. The Bootloader is still unlocked but that I guess I can lock via OEM lock way?
Since this is the latest one couldn't verify if the OTA works or not.

Help! Moto x bricked

Hello friends... Yesterday I was trying to take short way to root by using king root. But messed up. Here is the situation.
I tried to root this phone through this bull**** Kingroot.. And it failed.. Later on when i restarted the phone it got bootlooped and is totally bricked! i get this error- Startup Failed: Your device didn't start up successfully. use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
AP Fastboot flashmode (secure)
Fastboot Reason: Last time flashing failed
hab check failed for boot
failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation. backup to fastboot
Boot Up failed
Can some please explain in details to recover the device.. Step by step procedure to bring phone back to life.. And link to files required.. Thanks a lot for your help guys. Also.. Phone bootloader is still locked and obviously not rooted.

mani16985 said:
Hello friends... Yesterday I was trying to take short way to root by using king root. But messed up. Here is the situation.
I tried to root this phone through this bull**** Kingroot.. And it failed.. Later on when i restarted the phone it got bootlooped and is totally bricked! i get this error- Startup Failed: Your device didn't start up successfully. use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
AP Fastboot flashmode (secure)
Fastboot Reason: Last time flashing failed
hab check failed for boot
failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation. backup to fastboot
Boot Up failed
Can some please explain in details to recover the device.. Step by step procedure to bring phone back to life.. And link to files required.. Thanks a lot for your help guys. Also.. Phone bootloader is still locked and obviously not rooted.
Click to expand...
Click to collapse
Download rsd lite and flash the stock rom through it.

Thanks buddy for replying.. Can you please guide where can I find rsdlite. What is it and which stock rom to flash.. 5.1 or 6 marshmalow. Any link will be appreciated. Thanks again bro.

Sorry to bump.. But I need help really bad.

mani16985 said:
Sorry to bump.. But I need help really bad.
Click to expand...
Click to collapse
http://rsdlite.com/
download rsd lite
download your phone's 6.0 rom and flash it

Thanks buddy, it worked

Phone wont show up under device!
I HAVE THE EXACT SAME PROBLEM, i tried using rsd lite but my phone wouldnt show up under devices? can anyone please help its been a whole week !

SuliE97 said:
I HAVE THE EXACT SAME PROBLEM, i tried using rsd lite but my phone wouldnt show up under devices? can anyone please help its been a whole week !
Click to expand...
Click to collapse
Use Windows 7. Rsdlite doesn't work on Windows 10 if I'm not mistaken, probably also on 8/Vista.
Sent from my XT1562 using XDA-Developers mobile app

wont work
I downloaded wine/wineloader on my mac because i have no windows and then i downloaded and used rsdlite for windows 7 but it still wouldnt read

Rsdlite was also unable to detect my Moto X Play. I tried Rsdlite on two laptops both running Window 7 as well as tried different data cables but to no avail.

Was the phone in fastboot mode when you connect it to rsdlite?
Sent from my XT1562 using XDA-Developers mobile app

Yes, mine was in fastboot. And I tried various advice from various forums but no success

its stuck on the bootloader screen, i tried it on windows 7 computers and windows 8, my phone wont be detected by any computer, its called "lux" and somethings wrong with the driver, i uninstalled it, installed it again (motorola device manager), in driver settings i uninstalled it, downloaded the latest update for the driver) and my phone would still not be recognized by rsdlite or the computer in general BUT when i tried using the verizon software repair software on my mac, it was read as razr 2 but it would get stuck at 6%

mani16985 said:
Hello friends... Yesterday I was trying to take short way to root by using king root. But messed up. Here is the situation.
I tried to root this phone through this bull**** Kingroot.. And it failed..
Click to expand...
Click to collapse
What ROM were you on when you tried Kingroot? It worked perfectly for me after I returned my Xt1564 to stock, then ran Kingroot, I trashed the root app that it installed and replaced with SuperSu Pro. Has been working like a charm for weeks.

SuliE97 said:
I HAVE THE EXACT SAME PROBLEM, i tried using rsd lite but my phone wouldnt show up under devices? can anyone please help its been a whole week !
Click to expand...
Click to collapse
It's okay. It still works actually. I had this condition with locked bootloader and boot loop

Hey man, its been months and my phone is still bricked, i tried doing everything. Can someone give me a step by step tutorial? Boot loader is still locked. I tried everything!
Thanks

SuliE97 said:
Hey man, its been months and my phone is still bricked, i tried doing everything. Can someone give me a step by step tutorial? Boot loader is still locked. I tried everything!
Thanks
Click to expand...
Click to collapse
Dual sim or single simple.?
Phone region?(Brazil,India,EU etc)
Does your phone still boot to bootloader?If it boots into bootloader,download minimal fastboot and adb file given in the link below
http://forum.xda-developers.com/showthread.php?t=2317790.
Download the latest appropriate firmware and extract it to the Minimal Fastboot and adb folder.
Firmwares: https://github.com/motoxplay/stock
Download the latest drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
If you are on Windows 10 or 8.1 disable driver signature enforcement
https://www.youtube.com/watch?v=71YAIw7_-kg
If you still get error while installing drivers download the following file for windows 10
https://www.microsoft.com/en-us/download/details.aspx?id=48231
Put the phone in bootloader mode by holding down the volume button down while connecting it to the computer.Open the minimal adb fastboot folder,hold shift key and right click the mouse.Select "Open Command window here" option.Once command window is open,type the following commands
fastboot devices
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 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 reboot
You can also follow this guide.
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687

Sirob said:
Yes, mine was in fastboot. And I tried various advice from various forums but no success
Click to expand...
Click to collapse
Don't worry too much. Rsdlite works perfectly. It might show unknown device but it works

Complicated problem, never came across in the whole lifetime of my android usage.

TLR: Phone boots up and says. Launcher has stopped working, contacts has stopped working and etc.
Ok so i bought Moto G4 XT1625, yesterday. Was very happy with the device. It came with Android 6.0.1, i updated it to nougat 7.0.
But in android 6.0 and 7.0 both i noticed the phone giving random apps freezes and randomly even restarting on 7.0. The problem was minimal so i rebooted the phone 2,3 times and made it working. Then i received another update "NPJS25.93-14-4" on that update the phone got successful but bootlooped when booting for the first time on that update. I thoughts its ok so rebooted to bootloader and booted the phone from bootloader. the phone booted. after that another update came "NPJS25.93-14- (5 or 8) i dont remember properly" in this update the update failed during the installation. Keep in mind that i did not touch anything before this update. The phone was totally stock with stock recovery and everything. On this update the phone failed the update and i got constant bootloop no matter if i factory reset or erase cache it kept bootlooping, now i unlocked the bootloader and installed twrp and flashed a custom stock rom it crash on the boot. Again the random app has stopped working error came continously making the phone unusable. Then i flashed the stock rom correct firmware and everything it bootlooped again, then i rebooted numerous times the phone booted fine. Installed apps. This time did not get any app has stopped working error. Then rebooted the phone to install the sim card phone bootlooped again. Im 99% sure this is a hardware issue. Can somebody enlighten me? Whats going on in here? Thanks. I never faced this kind of problem ever in my life, i have bought more than 100 devices.

@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.

strongst said:
@whizinc
The Story is really frustrating especially when you bought it new :laugh:
So let's try to get your device working!
since you unlocked the bootloader you should clean flash the stock rom with fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 and see what happens. Don't put sim cards in and disable wifi. Just flash, boot and play around to see if it works without reboot.
Click to expand...
Click to collapse
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!

whizinc said:
I used the OEMLock.bat script. So far the phone booted first time properly without any issue. Sim is working as well. Current its on setup wizard checking network. Lets hope its fixed permanently. I will play with the phone for 5,10 hours constantly and report back. Thanks alot man!
Click to expand...
Click to collapse
Good luck:good:

UPDATE
It did not get past the "Checking Network" thing and after pressing the power button screen went black but i could see nav bar and status bar only. The phone has faulty hardware. Im now sure. Going to get it back tomorrow from where i bought it. Lets hope i get a refund or replacement. I bought it from a local mobile mall.

strongst said:
Good luck:good:
Click to expand...
Click to collapse
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working

whizinc said:
this phone has faulty hardware. IT failed. Again random apps saying "keeps stop working" such as : snapchat has stopped working
Click to expand...
Click to collapse
Have you installed any third-party apps or restored them?

strongst said:
Have you installed any third-party apps or restored them?
Click to expand...
Click to collapse
nope, not a single app. Everything is clean and properly flashed.

whizinc said:
nope, not a single app. Everything is clean and properly flashed.
Click to expand...
Click to collapse
Snapchat is pre-installed?

strongst said:
Snapchat is pre-installed?
Click to expand...
Click to collapse
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.

whizinc said:
You did not get me brother. I was giving an example. Here is a real example:
"Contacts has stopped working"
".com android process keeps stopping"
these are the random errors.
Click to expand...
Click to collapse
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?

strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
posted in a new thread because the problem did not belong to the rom's thread, im sorry did i do something wrong? No. I did not flash the stock custom rom before all of this. I never wanted to flash a custom rom. The thing is the phone failed an OTA update which let me to come to this decision. The phone failed ".5" update and after that it bootlooped. So i thought flashing twrp and flash a custom rom with a clean install would fix it but even the custom rom the " xxx app stopped working error" came continously.
After that i followed echo92's guide and flashed the whole stock rom through fastboot. Still same issue. Random apps crashing.
I think this is hardware issue. Because every idea has been fail till now.
What do u say?
edit: note: when the phone failed ".npj25.93-14-5" update it was completely stock and i did not even touch anything, i dont know why it failed on the first place?

strongst said:
It's irritating that you described that problem here before https://forum.xda-developers.com/mo...d-stock-jx-s-rom-series-t3658055/post73877878 now posting in a new thread. Does it mean you flashed the modified stock rom first and get the error and after this you flashed fastboot stock rom like described here? I don't get you.
@echo92 did you follow?
Click to expand...
Click to collapse
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
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 erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.

I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.

echo92 said:
Yep, I've been tracking the topic over both topics, gonna reply here to keep the other ROM thread clean too As I understand it:
Bought the device, had random issues with apps crashing on MM and Nougat.
Flashed TWRP and accidentally took the OTA, soft bricking in the process.
Flashed J-X's NPJS25.93-14-8 modified stock ROM, still app errors.
Reverted back to stock, still app errors, to the point where the device isn't useable and is now bootlooping...
However, @whizinc it's odd that you're experiencing these errors across flashes of the stock ROM and even a modified stock ROM and the data's been wiped each time...
Can you just confirm that with the NPJS25.93-14-4 (March 2017 fastboot ROM) that the stock ROM was flashed with these instructions as well, given that something odd's happening with your device...
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 erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot reboot
The difference is that these include re-flashing your GPT/bootloader (just in case) and also include the equivalent of a factory reset (so effectively a clean install of the stock, unmodified, ROM). I recall you've mentioned doing this, just want to ensure we have a clean slate to work with.
If you can, can you post the output of your flash commands, just want to see if the flash worked, hold fire on updating to NPJ25.93-14.5 for now (or if you want to try your luck, you can get the fastboot file from here - you need to flash it with the above instructions, as it's an upgrade: https://androidfilehost.com/?fid=673368273298984458 )
Else, it may be a hardware failure - when you bought the device, was it new or sold as used? Do you have a warranty with the shop you bought the device from? If you can, can you boot into bootloader, attach your device to your computer, and in the adb terminal, type 'fastboot getvar all' without the quotes, please? This should output a list of the basic details of your device, please post that here - you may wish to edit out your IMEI if you wish.
Click to expand...
Click to collapse
No no, You got the story wrong. Let me make it correct.
1: Bought the phone from a local mobile mall i have 3 days warranty left. (Phone was on Android 6.0 update)
2: Did not touch the phone. Just installed my daily apps. i.e: whatsapp,facebook and stuff.
3hone started doing odd things like auto touch while charging and apps saying "force stopped" error
4:Then i thought that this is Android 6.0 bug on Moto g4, so i should update it via OTA.
5: Updated to 7.0 same issues.
6:I saw another update did it as well 14-4 update. This update caused bootloop but i managed to make it through by booting from bootloader.
7: Then saw another update 14-5 and that update failed. (WHILE THE WHOLE PHONE WAS ON STOCK STATE) Why did the update fail? I didnt even touch the recovery or anything at that time.
8: Then i flashed the custom rom and the rest of the story goes on as u mentioned in the post.
And yes i cleaned flash the rom with the OEMlock.bat script that the guy above gave to me. It included all things such as boot,modem and all stuff. So it was def a clean install.
"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 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 erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot"
This was the script i used to flash the fastboot rom which is 14-4.
Then again got force stop errors and the 14-5 update failed causing bootloop again.
I just have 2 hours to check the devices further or else im gonna return it today. Thanks

MisterSteve said:
I have difficulty understanding why someone would void the warranty (by unlocking the bootloader) of a phone that is seemingly defective out if the box. Not a very good idea.
Click to expand...
Click to collapse
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.

whizinc said:
The phone was not in the official warranty from the start lol. I bought it used from a local mobile mall, they give 3 days checking warranty tho. I will try to get another handset. If i cant get it working.
Click to expand...
Click to collapse
Oh, you didn't mention that you have bought a used device! Bring it back to the shop and buy another/new one. Who knows what's wrong with that device or which history it has...

Apologies for getting the story mixed up, the information you provided in your corrected post and subsequently makes the situation worse though. Sounds like you bought a device exhibiting ghost touching or the beginnings of ghost touch and possibly was hard bricked/had the incorrect firmware flashed previously. As strongst mentioned, return that device. It sounds like it'll be more trouble than it's worth... especially for a used device.

UPDATE
I returned the handset to the shop guy, he was skeptical at first but then he gave it to another guy who said that the phone would go in used market claim and then after that he'll either return me the money or give me a new G4 device. I'll have to wait till monday. It sucks. Anyways Thanks alot guys for the help i appreciate it alot.
Feel free to lock the thread @ moderators.

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