[GUIDE][Perry(Qualcomm)][Windows, macOS & Linux] Flash Stock Firmware and Recovery
*This has only been personally done and tested using a Sprint Qualcomm variant of the Moto E4. I will be working on expanding this guide to cover all specific models of the Perry to avoid potential confusion as there are minor differences, so if anyone wants to pass along their firmware's flashfile.xml into my inbox it would be greatly appreciated.*
Links:
ADB and Fastboot mini .zip for macOS/Windows (Linux users make sure to have android-sdk installed, no need for this download)
All Stock Firmwares (sperry is Sprint firmware, perry is the rest of the Qualcomm models (Thanks to proudlytm) https://mirrors.lolinet.com/firmware/moto//
What you need:
A Windows/macOS/Linux computer
A USB cable
ADB and Fastboot files
Stock Firmware
Your phone
*Disclaimer* Your warranty is now void if you modify your phone. I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Let's get started! First, backup to your computer/Dropbox/etc. all the files you wish to save. This will wipe all data off your phone including root (Not data saved on any cloud services, such as Google, OneDrive, Dropbox, etc.)
Second, boot your phone into the bootloader. This can be done in certain ROM power menus, or with the ADB command "adb reboot bootloader" in Command Prompt/Terminal, or also by turning off your phone and then holding the power and volume down buttons at the same time. After booting into the bootloader, plug your phone into your computer.
The firmware file will look similar to This when extracted
Make sure to look in the firmware folder to see if you need to change a few lines during flashing. If you are unsure, check the flashfile.xml
Next open up Command Prompt if on Windows, Terminal if on macOS/Linux.
Navigate in CMD Prompt/Terminal to the directory you downloaded and extracted the stock firmware. Copy the Fastboot and ADB files into the same directory as the stock firmware files.
For Windows and Linux users, enter the following commands in Command Prompt/Terminal (use sudo before each command in Linux, or use sudo -s beforehand):
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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 oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
For macOS, enter the following in Terminal:
./fastboot oem fb_mode_set
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./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 oem oem.img_sparsechunk.0
./fastboot flash oem oem.img_sparsechunk.1
./fastboot erase cache
./fastboot erase userdata
./fastboot erase DDR
./fastboot oem fb_mode_clear
./fastboot reboot
Click to expand...
Click to collapse
Hope it helps!
*Reserved*
This is good for the XT1766, but the other variants firmwares have differences. Some have an extra system sparsechunk and an oem.img rather than 2 oem sparsechunks.
</poorly_coded> said:
This is good for the XT1766, but the other variants firmwares have differences. Some have an extra system sparsechunk and an oem.img rather than 2 oem sparsechunks.
Click to expand...
Click to collapse
Thanks for letting me know, I'll add a note
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
codyalan said:
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Because your bootloader is unlocked.
codyalan said:
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
I have restored stock on my E4's (I have two, one with a cracked screen) a whole bunch of times, from soft-bricked stock and also from custom ROM's. The key for me was to NOT flash gpt.bin. Leave that step out.
First thing I'd try is re-flashing just the stock boot.img, then see if you can get boot normally... if not...
Try re-flashing stock bootloader and stock recovery, reboot to stock recovery and factory reset. Reboot to bootloader and start stock flashing again (thanks @acejavelin), but don't flash the gpt.bin.
If that fails, one thing that worked for me when I was bootlooped was to completely install a custom ROM and Recovery (I used LineageOS and TWRP), get it up and running, then go ahead and restore the whole business back to stock.
The bad key thing.... it will say that for a few seconds (up to 30 seconds, maybe?) on boot when you restore stock but should get past it. I think it keeps echoing that every time you restart until you've replaced your recovery with a custom one, then the message turns into 'N/A'.
HTH
Ok so I wanted to update this thread. I have the XT1768 and the instructions are a bit different. For the XT1768 there is a Sparsechunk.5 and also for the XT1768 there is only a oem.img. By changing those steps I was able to get unstuck and back in business.
Vicpdx18 said:
Ok so I wanted to update this thread. I have the XT1768 and the instructions are a bit different. For the XT1768 there is a Sparsechunk.5 and also for the XT1768 there is only a oem.img. By changing those steps I was able to get unstuck and back in business.
Click to expand...
Click to collapse
Do you happen to have a copy of the flashfile.xml for your model number you could send to me? I've been wanting to further expand this guide to encompass each individual QComm model
fireball0093 said:
Do you happen to have a copy of the flashfile.xml for your model number you could send to me? I've been wanting to further expand this guide to encompass each individual QComm model
Click to expand...
Click to collapse
For the Xt1768??
codyalan said:
For the Xt1768??
Click to expand...
Click to collapse
Yes, if you have one for it that'd be awesome
fireball0093 said:
Yes, if you have one for it that'd be awesome
Click to expand...
Click to collapse
No Problem,
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
McTRASH692 said:
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ap...perr-s-kitchen-v3-0-0-0-t3601702/post72168885
How to start building
madbat99 said:
https://forum.xda-developers.com/ap...perr-s-kitchen-v3-0-0-0-t3601702/post72168885
How to start building
Click to expand...
Click to collapse
Thanks heaps, it'd be nice to create stock rom before root just incase the phone bricks.
McTRASH692 said:
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
Click to expand...
Click to collapse
I built the XT1765 Flashable rom in Assaayd's Kitchen. Followed the instructions to a T, and had no problems. Try him out too.
Articul8Madness said:
I built the XT1765 Flashable rom in Assaayd's Kitchen. Followed the instructions to a T, and had no problems. Try him out too.
Click to expand...
Click to collapse
Cheers mate,
I have since found a stock rom for my phone and fixed it completely,
Thank you for helping though,
Hi guys,
Could someone please post the contents of their stock build.prop file? I have corrupted mine and can't find one anywhere,
Device is moto e4 xt1769
Related
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.
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
I had the complete restore section reversed when you saw it on my thread, someone pointed it out and it's been fixed now.
Edit: I see someone's done it here too.
You also don't need to restore fully, just do the restore for ota and it should be enough if you've not flashed over the other stuff.
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
Hey Guys,
I recently had hardbricked my potter device.. Was unable to flash any rom, not even stock rom and I didnt find any thread in this forum which could have helped me.
I unbricked my device, flashed the stock rom and locked the bootloader,
The following steps will also get you unbrick your device... So, I would like to share the steps with all of you.
Note that this isnt only for unbricking, this can be done by any user who wants to flash stock rom and lock their bootloader.
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip file.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
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 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
fastboot reboot
Step 8: This will completely wipe your data and install stock 7.0 OS on your potter device. Note that this does not lock your bootloader.
Step 9: Boot your device to check if it boots and if it works.... now if you want to lock your bootloader move to the next step.
Step 10: Reboot again into your bootloader.
Step 11: Again follow the step 4, step 5 and step 6.
Step 12: Now paste the following commands in the command prompt:
fastboot oem lock
fastboot oem lock
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
Step 13: Reboot your device...
In this way you will be able to move to stock rom and lock your bootloader..
Please do comment if this works for you too and if you find any issues...
Thank you!!
All the Best!!:fingers-crossed::fingers-crossed::good::good:
rishivg said:
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
Click to expand...
Click to collapse
The quoted lines are redundant (surely they gave you an error since they don't exist in the G5+ firmware)
Otherwise, pretty standard Moto stuff... interesting that in 5th gen stuff you can lock after only flashing system sparsechunks, almost all previous devices required a complete flash with wipe to relock. https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ is another good source for stock factory ROM's (it is the official repo of FirmwareTeam), and Minimal ADB and Fastboot has a lots of "hacks" out there, so it is best to only reference the original source: https://forum.xda-developers.com/showthread.php?t=2317790
I am extremely familiar with previous Moto device, but am curious on this device what is the bootloader status number after relocking with this method and do you still get the unlocked warning screen after relocking like on previous Moto devices?
Hi,
Great if this guide works (not tested by me). However, it sounds viable. :good:
In any case, I suggest to put the original device and retail versions witht the link of the firmware. For example:
- XT1680 & retus: "POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
This is necessary. For example my is XT1685 and RETEU, then this file is not for me!
Not working. Its says cant be downgrade.
No does not work with the XT 1685 and reteu
surjeet.vishwas said:
Not working. Its says cant be downgrade.
Click to expand...
Click to collapse
what is your model number?
rishivg said:
what is your model number?
Click to expand...
Click to collapse
Xt1686 but i download another stock rom
surjeet.vishwas said:
Xt1686 but i download another stock rom
Click to expand...
Click to collapse
okay that is why it gave you error, try with the file that is mentioned in the post
This only works if you are on a previous or the exact same build. If you have already installed the August ota atm you can't relock the bootloader.
Gingernut78 said:
This only works if you are on a previous or the exact same build. If you have already installed the August ota atm you can't relock the bootloader.
Click to expand...
Click to collapse
yes exactly! you ll need to flash the whole previous build again...
rishivg said:
yes exactly! you ll need to flash the whole previous build again...
Click to expand...
Click to collapse
You can flash a previous build but it won't lock the bootloader that is the problem.
Gingernut78 said:
You can flash a previous build but it won't lock the bootloader that is the problem.
Click to expand...
Click to collapse
it will
rishivg said:
it will
Click to expand...
Click to collapse
The firmware will only re-lock your bootloader in that case if it's of the same or newer patch level as your bootloader. Older firmwares, as Gingernut78 pointed out, will get you back to stock, but if you're on the August 2017 patch level (and your bootloader is at the August 2017 patch level as well), you need a August 2017 or later stock ROM to re-lock your bootloader.
rishivg said:
Hey Guys,
I recently had hardbricked my potter device.. Was unable to flash any rom, not even stock rom and I didnt find any thread in this forum which could have helped me.
I unbricked my device, flashed the stock rom and locked the bootloader,
The following steps will also get you unbrick your device... So, I would like to share the steps with all of you.
Note that this isnt only for unbricking, this can be done by any user who wants to flash stock rom and lock their bootloader.
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip file.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
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 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
fastboot reboot
Step 8: This will completely wipe your data and install stock 7.0 OS on your potter device. Note that this does not lock your bootloader.
Step 9: Boot your device to check if it boots and if it works.... now if you want to lock your bootloader move to the next step.
Step 10: Reboot again into your bootloader.
Step 11: Again follow the step 4, step 5 and step 6.
Step 12: Now paste the following commands in the command prompt:
fastboot oem lock
fastboot oem lock
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
Step 13: Reboot your device...
In this way you will be able to move to stock rom and lock your bootloader..
Please do comment if this works for you too and if you find any issues...
Thank you!!
All the Best!!:fingers-crossed::fingers-crossed::good::good:
Click to expand...
Click to collapse
thank you so much you safe my life:good
rishivg said:
yes exactly! you ll need to flash the whole previous build again...
Click to expand...
Click to collapse
Please let me know how. I'm on August security patch. Xt1686 67 5 build indian version. I can flash only 67 5 build stock rom. When i try flashing older stock roms, it says bootloader version downgrade. Please please tell me how i can fully go back to stock.
ksvirdi105 said:
Please let me know how. I'm on August security patch. Xt1686 67 5 build indian version. I can flash only 67 5 build stock rom. When i try flashing older stock roms, it says bootloader version downgrade. Please please tell me how i can fully go back to stock.
Click to expand...
Click to collapse
dont flash the bootloader! ignore that command and report!:fingers-crossed:
rishivg said:
dont flash the bootloader! ignore that command and report!:fingers-crossed:
Click to expand...
Click to collapse
Are you sure it will work perfectly. No bricking and stuff?? which commands should i skip.
And once i flash it will i be able to get ota to august patch and relock?
ksvirdi105 said:
Are you sure it will work perfectly. No bricking and stuff??
Click to expand...
Click to collapse
it wont brick your device.. try it out:good:
rishivg said:
it wont brick your device.. try it out:good:
Click to expand...
Click to collapse
Once i flash it will i be able to get ota updates.
ksvirdi105 said:
Once i flash it will i be able to get ota updates.
Click to expand...
Click to collapse
lock your bootloader, you ll get updates but not security updates.. I dont know why? Need some help from developers
Can anybody provide with the flashing instruction for moto g5
yolomonkey said:
Can anybody provide with the flashing instruction for moto g5
Click to expand...
Click to collapse
Assuming you have fastboot installed on your pc
Download firmware and unzip to where you have fastboot
Open command prompt at fastboot location with firmware
type the following although I have marked lines that you should not use unless you have to as flashing wrong firmware can damage your device
Code:
fastboot oem fb_mode_set Only required if you wish to relock bootloader - if not skip it
fastboot flash partition gpt.bin Do not use unless you want to repartition your device - incorrect file will damage your phone
fastboot flash bootloader bootloader.img Do not use unless you want to replace the bootloader - flashing wrong file will hard brick
fastboot flash logo logo.bin No need to flash if you are going to flash a custom rom after and have already flashed a modded version
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 Will erase everything on internal storage but you need to do it
fastboot erase customize Not sure about this - might be for other device
fastboot erase clogo Not sure about this - might be for other device
fastboot oem fb_mode_clear Only required to relock bootloader if you used the very first command
fastboot reboot
NOt working
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp
yolomonkey said:
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp
Click to expand...
Click to collapse
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)
TheFixItMan said:
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)
Click to expand...
Click to collapse
could you please link it. I am so grateful for you replying this fast
yolomonkey said:
could you please link it. I am so grateful for you replying this fast
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
FAQs are on 2nd post
WARNING: if the gpt.bin flash did not work, please stop and do not continue with the rest of the commands. It has been brought to my attention that software upgrades to the phone has changed the gpt and may not allow you to go back to the original stock firmware.
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Outstanding. Thank you for the post. I'm sure this will get used quite a bit. I did do a backup but it's always nice to have contingencies at the ready.
Sent from my Nexus 10 using XDA Premium HD app
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
glockman4519 said:
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
Click to expand...
Click to collapse
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
aj2333 said:
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thank you very much. You sir are an awesome person.
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
glockman4519 said:
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
Click to expand...
Click to collapse
Did you remember to do an fastboot OEM fb_mode_clear?
no I didn't do that. I will go back over your instructions and re-do it. Thank you again for your assistance. I usually don't bug people for help and try to fix things on my own so I really appreciate you help.
Sent from my G3223 using XDA Premium HD app
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
glockman4519 said:
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
Click to expand...
Click to collapse
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
doodalydoo said:
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Click to expand...
Click to collapse
You Sir are the man. I can't thank you enough for your help.
Update: Awesome.... It worked like a charm. I have everything copied now in case I hit the wall again. Thank you once again.
So I have used this and it worked great. However does anyone know when the firmware in that download will be updated to the latest version?
XT1775 rom's is possible install on XT1776 ?
almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Cool miner malware that pops up on firmware.center.
mattleft said:
Cool miner malware that pops up on firmware.center.
Click to expand...
Click to collapse
I haven't had that problem. Have you scanned your PC for virus/malware?
I would like to relock my bootloader but on this firmware it says the boot is not signed. Can I relock it after I do the ota as they should be signed then right?
bcrichster said:
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Click to expand...
Click to collapse
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
mindstream98 said:
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
Click to expand...
Click to collapse
I read in another thread that it was possible by using a Custom ROM but haven't tried it myself..
Although the Custom ROMs should work on several Carriers, this is a "Completely Back to Stock" thread..
Running an Xp3r!meπt with my XT1776
zerogun said:
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem 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 oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Click to expand...
Click to collapse
I used this to go back to stock, now my phone wont even turn on, at all.
Hello guys I've been trying out some different ROMs. Also tried the Oreo soak test but I'm now back on pixel experience but my finger print reader 4G and loud speaker is no longer working. It didn't work on aosp extended also.
How can I fix this please? I need 4G mainly...
Please help!
Thanks in advance.
junglebungle said:
Hello guys I've been trying out some different ROMs. Also tried the Oreo soak test but I'm now back on pixel experience but my finger print reader 4G and loud speaker is no longer working. It didn't work on aosp extended also.
How can I fix this please? I need 4G mainly...
Please help!
Thanks in advance.
Click to expand...
Click to collapse
Try flashing stock rom if you get 4g,speaker... Then try to come back to rom
riyan65 said:
Try flashing stock rom if you get 4g,speaker... Then try to come back to rom
Click to expand...
Click to collapse
Thanks for the reply. What is the stock ROM where can I find it? Is it safe to flash the older ROM?
junglebungle said:
Thanks for the reply. What is the stock ROM where can I find it? Is it safe to flash the older ROM?
Click to expand...
Click to collapse
The rom which came with your device is called stock rom. You can find it here
https://www.google.co.in/amp/s/foru...l-stock-moto-g5-cedric-firmware-t3733897/amp/
You can flash the old rom but you should not flash gpt and bootloader. If you flash bootloader and gpt your device will get hard bricked. So I suggest you to don't flash gpt and bootloader if you're having old stock rom. If you having latest stock rom then you can flash bootloader and gpt.
riyan65 said:
The rom which came with your device is called stock rom. You can find it here
https://www.google.co.in/amp/s/foru...l-stock-moto-g5-cedric-firmware-t3733897/amp/
You can flash the old rom but you should not flash gpt and bootloader. If you flash bootloader and gpt your device will get hard bricked. So I suggest you to don't flash gpt and bootloader if you're having old stock rom. If you having latest stock rom then you can flash bootloader and gpt.
Click to expand...
Click to collapse
Thanks I will try it, I am going to try it, I am from the UK so this link you give me is universal ROM and will work?
junglebungle said:
Thanks I will try it, I am going to try it, I am from the UK so this link you give me is universal ROM and will work?
Click to expand...
Click to collapse
It doesn't matter which country you live. All are same just different in receiving update time.
riyan65 said:
It doesn't matter which country you live. All are same just different in receiving update time.
Click to expand...
Click to collapse
Ok great, so because I am on the latest Pixel Experience ROM I just do the following commands to flash the november 2017 stock rom:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin - NO
fastboot flash bootloader bootloader.img - NO
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
fastboot reboot
Right?
junglebungle said:
Ok great, so because I am on the latest Pixel Experience ROM I just do the following commands to flash:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin - NO
fastboot flash bootloader bootloader.img - NO
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
fastboot reboot
Right?
Click to expand...
Click to collapse
Yes, right
riyan65 said:
Yes, right
Click to expand...
Click to collapse
Thanks for the help! I'll report back to see if 4G is working, does this fix the finger print reader too?
junglebungle said:
Thanks for the help! I'll report back to see if 4G is working, does this fix the finger print reader too?
Click to expand...
Click to collapse
When you flash stock rom there is possibility of losing imei. So take a backup of efs, if it efs didn't work then there a forum about how to recover imei with 4g. Wait for few minutes I send the link of the thread
---------- Post added at 02:30 PM ---------- Previous post was at 02:27 PM ----------
riyan65 said:
When you flash stock rom there is possibility of losing imei. So take a backup of efs, if it efs didn't work then there a forum about how to recover imei with 4g. Wait for few minutes I send the link of the thread
Click to expand...
Click to collapse
Here is the link
https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860
---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------
junglebungle said:
Thanks for the help! I'll report back to see if 4G is working, does this fix the finger print reader too?
Click to expand...
Click to collapse
Here is the link
https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860
---------- Post added at 02:40 PM ---------- Previous post was at 02:31 PM ----------
junglebungle said:
Thanks for the help! I'll report back to see if 4G is working, does this fix the finger print reader too?
Click to expand...
Click to collapse
Hey, I have forgotten to say that you can get 4g in Pixel rom also. But I don't know if it going to fix loudspeaker and finger scanner. The thread I have send you the link it is present there.
riyan65 said:
When you flash stock rom there is possibility of losing imei. So take a backup of efs, if it efs didn't work then there a forum about how to recover imei with 4g. Wait for few minutes I send the link of the thread
---------- Post added at 02:30 PM ---------- Previous post was at 02:27 PM ----------
Here is the link
https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860
---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------
Here is the link
https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860
---------- Post added at 02:40 PM ---------- Previous post was at 02:31 PM ----------
Hey, I have forgotten to say that you can get 4g in Pixel rom also. But I don't know if it going to fix loudspeaker and finger scanner. The thread I have send you the link it is present there.
Click to expand...
Click to collapse
Ok I flashed the original stock ROM and I ended up getting 0 IMEI and no network. I followed your guide :
It seem like many of are not getting imei after doing this also.let me explain you in a clear way
Step1:-run on a custom rom such as lineage,aosp...
(Note:-if you have 4g/LTE in custom rom then skip step2)
Step2:-turn off your phone and get into bootloader and run the following commands
Fastboot erase modemst1
Fastboot erase modemst2
Step3:-make a back up of efs in Twrp 64x bits(save the efs in external memory so it will not get erased) and erase data,cache only
Step4:-now flash 32xbits Twrp then
Step5:-flash stock rom using following commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.o
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 flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
fastboot oem fb_mode_clear
Step6:-now reboot your phone
Step7:-you will get the Imei and 4g/LTE
Step8:-don't use OTA, use adb you can download updates from here
https://drive.google.com/drive/mobil...Py?usp=sharing
Step9:-reboot to stock recovery and select apply update from adb
Step10:-run the following command to apply update
Adb sideload filename.zip
Step11:-In may security patch you may lose imei
Step12:-now install Twrp 64x bits and restore efs from it which you have make it before
Step13:-reboot your device.done
Now you will get the Imei,4g/LTE and latest update.
Let me know if it works for you.
--------------
This didn't work though, I have been messing around and finally got IMEI and 3G back again by reinstalling pixel experience ROM. But 4G doesn't even come up anymore when I select it in the Android network option, It just stays 3G when i select 4G, before it would say 4G with a X through it at the top of the home screen.
I have some questions, why do you need to flash 32bit TWRP because after you use the commands to flash stock it wipes thw TWRP anyway? also where can I get the 32bit as I can only find 64bit version.
Is that the reason why I got 0 IMEI because I didn't use 32 bit TWRP?
Finger print and loud speaker is now working but I REALLY need 4G back, please tell me how I can accomplish this?
I backed up my EFS AFTER I used the following commands:
fastboot erase modemst1
fastboot erase modemst2
But all that did was remove my IMEI.
I am lost how to get 4G back
Restoring EFS does nothing....
Thanks
junglebungle said:
Ok I flashed the original stock ROM and I ended up getting 0 IMEI and no network. I followed your guide :
It seem like many of are not getting imei after doing this also.let me explain you in a clear way
Step1:-run on a custom rom such as lineage,aosp...
(Note:-if you have 4g/LTE in custom rom then skip step2)
Step2:-turn off your phone and get into bootloader and run the following commands
Fastboot erase modemst1
Fastboot erase modemst2
Step3:-make a back up of efs in Twrp 64x bits(save the efs in external memory so it will not get erased) and erase data,cache only
Step4:-now flash 32xbits Twrp then
Step5:-flash stock rom using following commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.o
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 flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
fastboot oem fb_mode_clear
Step6:-now reboot your phone
Step7:-you will get the Imei and 4g/LTE
Step8:-don't use OTA, use adb you can download updates from here
https://drive.google.com/drive/mobil...Py?usp=sharing
Step9:-reboot to stock recovery and select apply update from adb
Step10:-run the following command to apply update
Adb sideload filename.zip
Step11:-In may security patch you may lose imei
Step12:-now install Twrp 64x bits and restore efs from it which you have make it before
Step13:-reboot your device.done
Now you will get the Imei,4g/LTE and latest update.
Let me know if it works for you.
--------------
This didn't work though, I have been messing around and finally got IMEI and 3G back again by reinstalling pixel experience ROM. But 4G doesn't even come up anymore when I select it in the Android network option, It just stays 3G when i select 4G, before it would say 4G with a X through it at the top of the home screen.
I have some questions, why do you need to flash 32bit TWRP because after you use the commands to flash stock it wipes thw TWRP anyway? also where can I get the 32bit as I can only find 64bit version.
Is that the reason why I got 0 IMEI because I didn't use 32 bit TWRP?
Finger print and loud speaker is now working but I REALLY need 4G back, please tell me how I can accomplish this?
I backed up my EFS AFTER I used the following commands:
fastboot erase modemst1
fastboot erase modemst2
But all that did was remove my IMEI.
I am lost how to get 4G back
Restoring EFS does nothing....
Thanks
Click to expand...
Click to collapse
Now your in which rom stock or custom??? If you're on custom rom just use this command's
fastboot erase modemst1
fastboot erase modemst2
If you are in stock you need to go back to custom check if 4g is there if not use the above command and then come to stock without using this codes
fastboot erase modemst1
fastboot erase modemst2
And gpt, bootloader.
riyan65 said:
Now your in which rom stock or custom??? If you're on custom rom just use this command's
fastboot erase modemst1
fastboot erase modemst2
If you are in stock you need to go back to custom check if 4g is there if not use the above command and then come to stock without using this codes
fastboot erase modemst1
fastboot erase modemst2
And gpt, bootloader.
Click to expand...
Click to collapse
I am on pixel again, if I go back to stock it gives me 0 IMEI, and I don't want to risk it as I don't have the internet at home right now I am tethered via my phone. I did these commands
fastboot erase modemst1
fastboot erase modemst2
Before and it wiped my IMEI.
What do you mean "and gpt, bootloader" they need flashing too? for which ROM? I am so confused.
Why is 32bits TWRP needed?
I tried stock rom and the oreo rom and both gave me 0 IMEI but I am not sure what I did to get it working on pixel, I flashed pixel in TWRP and booted the phone and the IMEI and 3G was working again, but no 4G.
riyan65 said:
Now your in which rom stock or custom??? If you're on custom rom just use this command's
fastboot erase modemst1
fastboot erase modemst2
If you are in stock you need to go back to custom check if 4g is there if not use the above command and then come to stock without using this codes
fastboot erase modemst1
fastboot erase modemst2
And gpt, bootloader.
Click to expand...
Click to collapse
Any update? this is really stressing me out
even two guys in this thread: https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860/
Said that getting 4g back wasn't possible? and the post before my one that guy had issues too. I hear there is no fix to get 4G back....
junglebungle said:
I am on pixel again, if I go back to stock it gives me 0 IMEI, and I don't want to risk it as I don't have the internet at home right now I am tethered via my phone. I did these commands
fastboot erase modemst1
fastboot erase modemst2
Before and it wiped my IMEI.
What do you mean "and gpt, bootloader" they need flashing too? for which ROM? I am so confused.
Why is 32bits TWRP needed?
I tried stock rom and the oreo rom and both gave me 0 IMEI but I am not sure what I did to get it working on pixel, I flashed pixel in TWRP and booted the phone and the IMEI and 3G was working again, but no 4G.
Click to expand...
Click to collapse
If you on custom rom just use this command's in Pixel or other roms it don't wipe imei.
fastboot erase modemst1
fastboot erase modemst2
riyan65 said:
If you on custom rom just use this command's in Pixel or other roms it don't wipe imei.
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I am on Pixel rom with 3G only, no 4G, I just used those commands and rebooted the phone, it wiped my IMEI and gave me no signal..... so that doesn't work....
I then had to install stock rom again (without the above codes and gpt/bootloader it didn't give me imei stilI) So I wipe data, reinstall pixel custom rom and still no imei or 3g, I then installed Oreo soak test with all the commands (including fastboot erase modemst1/2 and gpt/bootloader) then flash pixel again to get my 3g back... I think I am doomed and 4g doesn't work anymore, many people are saying the same thing. Even on this guys video: https://www.youtube.com/watch?v=XmKg84IXEbo
I also can't restore my EFS file as when I try to it says some error about a partition?
Apprently the only way to fix it is install official android 8.0 that guy said? is this true?
riyan65 said:
If you on custom rom just use this command's in Pixel or other roms it don't wipe imei.
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
Hey man sorry to bug you but did you have any thing else I can try? it's driving me mad
junglebungle said:
Hey man sorry to bug you but did you have any thing else I can try? it's driving me mad
Click to expand...
Click to collapse
Hey did you try any rom of 32bit with 32 bit twrp.
riyan65 said:
Hey did you try any rom of 32bit with 32 bit twrp.
Click to expand...
Click to collapse
Not sure, I did use 32bit twrp for something I can't remember what though, it wasn't stock rom as I used the commands to flash stock rom.
Also tried this: https://forum.xda-developers.com/g5/how-to/how-to-recovery-4g-moto-g5-t3787208
But that didn't work either, using the erase modem commands just wipes my IMEI. I tried this on Pixel rom though not the DotOS, surely that doesn't make any difference?
junglebungle said:
Not sure, I did use 32bit twrp for something I can't remember what though, it wasn't stock rom as I used the commands to flash stock rom.
Also tried this: https://forum.xda-developers.com/g5/how-to/how-to-recovery-4g-moto-g5-t3787208
But that didn't work either, using the erase modem commands just wipes my IMEI. I tried this on Pixel rom though not the DotOS, surely that doesn't make any difference?
Click to expand...
Click to collapse
Try this commands on AOSP/lineage rom.