Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.
This firmware can be flashed on Both locked and Unlocked Bootloaders
Moto G4 Plus [XT1640/XT1641/XT1642/XT1643/XT1644] ATHENE NPJ25.93-14 FASTBOOT + Relock Bootloader
Requirements:
1. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
2. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/showthread.php?t=2317790
3. Moto Drivers
For Windows: http://www.devfiles.co/download/5eExXq3a/MotorolaDeviceManager_2.5.4.exe
For Mac:http://www.devfiles.co/download/i51GYJjz/MDM_Installer_2.2.9.dmg
4. Download Fastboot ROM Zip : https://drive.google.com/file/d/0Bx6eXSiwEdFFWXZyYjB5S0xlZWs/view :good:
Firmware via FASTBOOT:
1. Download the rar file and unzip it.
2.Extract all the files to your fasboot folder.
3.Restart the Moto G4 in fastboot mode.
4. Make sure that usb debugging is on.
5.Connect the Phone in fastboot mode to the computer
Run the "OEM Flash.bat" script that is inside the folder that is created when you unzip the file.(If you want to lock your bootloader Use "OEM lock.bat")
You Can also do it Manually In adb fastboot folder shift+right click and then in the pop up click open command window here
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 (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
NOTE:
1. If you dont want to lock your bootloader just skip the "fastboot oem lock" and "fastboot oem lock begin" Commands
2. Since this file was compressed using 7zip you need 7zip to extract it using Winrar or Winzip will give you an error you can download 7zip from http://www.7-zip.org/download.html
3.Using the "OEM Flash.bat" or "OEM lock.bat" will wipe your data and all the Customizations like Root and Xposed and get it to Factory Condition if You are Reverting back to Stock from a Custom Rom Or Upgrading Stock it is Strongly Advised to Wipe your Data to avoid bugs and crashes(system/app)
In any case if you don't want to wipe data just remove this command "fastboot erase userdata" from the bat file or skip it if your flashing manually
HIT THANKS IF I HELPED YOU !
FOR FURTHER ASSISTANCE JOIN THE TELEGRAM GROUP FOR OUR G4 FAMILY https://telegram.me/g4plus
Works on XT1622 ?
kosmasgr said:
Works on XT1622 ?
Click to expand...
Click to collapse
May work not confirmed
kosmasgr said:
Works on XT1622 ?
Click to expand...
Click to collapse
Yes it does. Just used it to re lock my uk 1622. All seems to be working perfectly. Shows the correct model in about settings
oldsoulsong said:
Yes it does. Just used it to re lock my uk 1622. All seems to be working perfectly. Shows the correct model in about settings
Click to expand...
Click to collapse
Can confirm.
Just re-locked the bootloader on my European XT1622 with this.
Don't forget to enable OEM Unlocking and USB Debugging in Developer Options!
How about xt1641
Sent from my Moto G (4) using XDA-Developers Legacy app
Can i use this for rooted ressurection remix
Sent from my Moto G4 Plus using Tapatalk
tonypooyappallil said:
Can i use this for rooted ressurection remix
Click to expand...
Click to collapse
Yes
daeshawn said:
How about xt1641
Click to expand...
Click to collapse
Yes it works on xt1641
Greekgodmerwyn said:
Yes
Click to expand...
Click to collapse
So if i use this, i will relock my bootloader, then iam eligible for warranty?
Sent from my Moto G4 Plus using Tapatalk
tonypooyappallil said:
So if i use this, i will relock my bootloader, then iam eligible for warranty?
Click to expand...
Click to collapse
No you have received an unlock key from Motorola to unlock your bootloader hence when they enter your serial no they will find out in their data base that your device was unlocked
Greekgodmerwyn said:
No you have received an unlock key from Motorola to unlock your bootloader hence when they enter you serial no they will find out in their data base that your device was unlocked :good:
Click to expand...
Click to collapse
Okay. But the device will get locked bootloader right?
Sent from my Moto G4 Plus using Tapatalk
tonypooyappallil said:
Okay. But the device will get locked bootloader right?
Click to expand...
Click to collapse
Yes use the oemlock.bat or if you are doing it manually then use the OEM lock commands this will only work if you are upgrading
Greekgodmerwyn said:
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own.
Moto G4 Plus [XT1640/XT1641/XT1642/XT1643] ATHENE NPJ25.93-14 FASTBOOT + Relock Bootloader
Requirements:
1. Download the Minimal ADB and Fastboot = https://drive.google.com/file/d/0B1M...ew?usp=sharing
2. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/showthread.php?t=2317790
3. Moto Drivers
For Windows: http://www.devfiles.co/download/5eExXq3a/MotorolaDeviceManager_2.5.4.exe
For Mac:http://www.devfiles.co/download/i51GYJjz/MDM_Installer_2.2.9.dmg
4. Download Fastboot ROM Zip : https://drive.google.com/file/d/0Bx6eXSiwEdFFWXZyYjB5S0xlZWs/view :good:
Firmware via FASTBOOT:
1. Download the rar file and unzip it.
2.Extract all the files to your fasboot folder.
3.Restart the Moto G4 in fastboot mode.
4. Make sure that usb debugging is on.
5.Connect the Phone in fastboot mode to the computer
Run the "OEM Flash.bat" script that is inside the folder that is created when you unzip the file.(If you want to lock your bootloader Use "OEM lock.bat")
You Can also do it Manually In adb fastboot folder shift+right click and then in the pop up click open command window here
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
NOTE:
If you dont want to lock your bootloader just skip the "fastboot oem lock" and "fastboot oem lock begin" Commands
HIT THANKS IF I HELPED YOU !
FOR FURTHER ASSISTANCE JOIN THE TELEGRAM GROUP FOR OUR G4 FAMILY https://telegram.me/g4plus
Click to expand...
Click to collapse
The image is corrupted plz upload new image in google drive
a-2-k said:
The image is corrupted plz upload new image in google drive
Click to expand...
Click to collapse
Use 7Zip to Extract it is a 7zip file if you try to extract it with winrar or WinZip you will definitely get an error and please don't quote the whole thread while replying
Greekgodmerwyn said:
Use 7Zip to Extract it is a 7zip file if you try to extract it with winrar or WinZip you will definitely get an error and please don't quote the whole thread while replying
Click to expand...
Click to collapse
sorry I don't see....7zip
xploder270 said:
Can confirm.
Just re-locked the bootloader on my European XT1622 with this.
Don't forget to enable OEM Unlocking and USB Debugging in Developer Options!
Click to expand...
Click to collapse
What about your baseband version now ? Is it still EMEA ? (I am extra cautious not to lose European LTE bands).
a-2-k said:
sorry I don't see....7zip
Click to expand...
Click to collapse
download from here:
http://www.7-zip.org/download.html
rjtgupta84 said:
download from here:
http://www.7-zip.org/download.html
Click to expand...
Click to collapse
I think he meant to say that he didn't know that it was 7zip
Greekgodmerwyn said:
I think he meant to say that he didn't know that it was 7zip
Click to expand...
Click to collapse
Yes you got it
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, then hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Final reboot:
Code:
fastboot reboot
7. If everything worked your phone should now boot into OxygenOS.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To check current slot:
Code:
fastboot getvar current-slot
To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. This will wipe your device! Reboot to the bootloader and run:
Code:
fastboot -w
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Edit: script attached. I've (unfortunately) had the opportunity to test it and fix all the bugs. So it works. You will need to have fastboot.exe accessible in your system PATH to run it.
Slikkster2k said:
If you want, you can do the flashing easily with powershell, rather than running each command one after the other. Here is what I did:
1. Have fastboot.exe in your path, or in the same folder as all your extracted images. Open powershell and navigate to the folder with your boot images. Connect your phone to USB.
2. Reboot to the bootloader and run:
Code:
fastboot -w
This will wipe your device!
3. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'boot|cpucp|dtbo|modem|oplusstanvbk|oplus_sec|qweslicstore|shrm|splash|vbmeta|vbmeta_vendor|vbmeta_system|vendor_boot|vm-bootsys'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
4. Run:
Code:
fastboot reboot fastboot
5. Run:
Code:
gci -filter *.img | where {$_.Name.split('.')[0] -match 'abl|aop|bluetooth|devcfg|dsp|featenabler|hyp|imagefv|keymaster|multiimgoem|qupfw|tz|uefisecapp|xbl|xbl_config|product|system|system_ext|vendor|odm'} | foreach-object { fastboot.exe flash $($_.Name.split('.')[0]) $_.Name }
6. Run:
Code:
fastboot reboot bootloader
7. Proceed to boot normally.
The commands in steps 3 and 5 get a list of all files in the current directory with the .img extension, filter them to the correct ones to flash, and then flash them one after another.
If someone wants, I can probably throw together a script to run the whole process start to finish.
Click to expand...
Click to collapse
That would be helpful indeed. Would this script run on mac as well?
Not unless there's a version of PowerShell for macs (there is for Linux, but I don't know if it's compatible).
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
AxelM said:
@Slikkster2k: I tried your tutorial. At first it did not work...serveral errors occure during copying one file. On the second run I had to change the slot, than it runs through.
But now I am in a boot loop, during starting the oxygen.
While wiping I got this message:
Code:
fastboot: error: Cannot generate image for userdata
Which version of the OS did you use?
I tried to install the actual european rom (11.2.3.3) on my indian device from china but this obviously did not work. Do you have any suggestions for me?
Click to expand...
Click to collapse
I used 11.2.2.2.LE25AA as I said in the original post (this is the global variant, which matches my device). I am not sure if this works for cross-flashing, or if it's possible to cross-flash an Indian phone to EU. Have you tried restoring the Indian ROM? Does that work?
You're getting an actual boot loop? The error I was getting (and the reason I had to restore) was the phone booting to the bootloader or fastbootd (depending on the slot I tried) instead of Oxygen, because it couldn't mount the user partition due to encryption. In fastbootd an error was reported (I forget the exact one) which made me suspect it was a partition mounting issue. At no point was my phone actually boot looping, even during partial/failed flashes.
I've never encountered the error with fastboot -w, but I only did that on my phone once. From some searching online, it can be caused by an old version of the platform tools, so did you download the latest version?
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
AxelM said:
@Slikkster2k: First of all, thank you for providing help
In deed, what worked was the indian first version. This i could flash and from there on everything works. Up to OS and than installing the latest european os. Now everything ist fine...
The error while whiping did not occure while using the indian version...so no clue why...
But now it works for me, thank you!
Click to expand...
Click to collapse
Glad to hear you got it working!
PowerShell script added to second post. Totally untested, but I tried to make it as idiot proof as possible.
Slikkster2k said:
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using payload dumper. If you haven't done any of these things yet, there are plenty of other guides out there on how to do them.
Steps:
1. Reboot your device to the bootloader (power off, hold volume up + power) and connect it to USB.
2. The following command will wipe your device. I found this to be necessary to recover my OnePlus 9:
Code:
fastboot -w
3. Now flash the following files:
Code:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
4. Now reboot into userspace fastboot, aka fastbootd. If you don't do this, the remaining files cannot be flashed:
Code:
fastboot reboot fastboot
5. Flash the remaining files:
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
6. Reboot back into the bootloader:
Code:
fastboot reboot bootloader
7. You should now be able to continue booting normally by pressing the power button.
Note:
The files will be flashed to your currently active boot slot. If any of them fail to flash, switch to the other slot and start over from the beginning. I wasn't able to flash odm, product, system, system_ext and vendor to slot a, and had to use slot b instead. To switch slots:
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
Use this guide at your own risk. I take no responsibility if you brick your device, set it on fire, or otherwise mess it up as a result of any of the above steps. That being said, it worked for me using 11.2.2.2.LE25AA available from the official OnePlus support website.
Click to expand...
Click to collapse
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
toyanucci said:
That would be helpful indeed. Would this script run on mac as well?
Click to expand...
Click to collapse
Windows offered now to add to MAC - https://support.apple.com/en-us/HT201468
toyanucci said:
My phone has been weird for a week or so occasionally freezing up and saying system ui has crashed or something so I followed these instructions last night to completely wipe and reset everything (after backing up). It worked perfectly!
My only suggestion would be for step 7 to be:
fastboot reboot
Since we're already using fastboot it's just quicker and less fiddly than using the power button
Click to expand...
Click to collapse
Thanks, updated OP.
ok i kind of bricked my phone using this and i need a little help PLEASE?
Ok i tried the fist 2 steps 1. fastboot -w than the first list of commands using cmd with admin rights it worked...i think but it did load everything without issues...now i go to do the "fastboot reboot fastboot"
and now my phone is stuck on a black screen with nothing and i just hear the chime windows makes when you disconnect and reconnect a device..... and in the Device manager this comes up for 10 seconds than goes away for 5 than comes back NON STOP
i cant adb i cant do anything please help !
I'm not sure if this will help you, but I had a lot of issues initially running this. First off you need to use the Oneplus drivers, I don't think the qualcom driver will work the same way. I could be wrong, but that's what I did. Secondly, you need to force install the driver because Windows doesn't like it.
Here are the steps I took.
1. Uninstall any old drivers.
2. Install the newest Oneplus Drivers from here https://oneplususbdrivers.com/
3. Extract the zip file and run the installer like normal
4. Once the installer finishes, you'll need to reboot your machine and bring up the Startup settings (hold down shift and reboot (keep holding down shift until you get a screen with options)) Then click advanced and startup settings and hit restart after that. Once the machines starts up, on the first boot you will have a bunch of options. Choose option 7 "disabling driver signature enforcement" mode.
5. Once Windows launches and you login, go back into the device manager and follow these steps:
right click the device --> update driver
Browse my computer for drivers
Let me pick from a list of available drivers on my computer
Show all Devices --> Next
Have Disk (Button)
Navigate to where you installed Oneplus drivers (Default: C:\Program Files (x86)\OnePlus USB Drivers)
Select "OnePlus_android_winusb.inf"
Select "Oneplus Android Bootloader Interface" and then just hit next/OK until it installs.
You might need to reboot after doing the above, but this worked for me.
----------------------------------------
The above should get your drivers working properly in all modes (adb, fastbootd, bootloader, normal)
One other issue that I ran into when I was using the powershell script was that I was seeing intermittent errors. After trial and error I realized that Windows was picking up a different version of fastboot. I was initially using the minimal adb/fastboot files, but if you compare those to the ones listed in the first post in the "SDK Platform Tools", they are very different from each other, so you need to make sure you use the SDK Platform Tools version. The minimal ADB/Fastboot version will NOT work.
After I got those 2 things ironed out, the powershell script ran without a hiccup and my phone is stock and booting without an issue.
I know I'm late to respond to this thread, but I hope someone finds this information helpful!
Mine keeps trying this and it isn't running and or rebooting into Fastbootd when the script is ran. Should I just try and invoke this manually? I've tried that as well an I'm seeming to get errors left and right with no resolve.
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Good work
toyanucci said:
I'd say try it manually and see where the errors happen. Does it boot into fastbootd at all?
Click to expand...
Click to collapse
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
ilikepie___ said:
Actually, I ended up making my phone hard bricked to the point where it doesn’t even turn on at this point. I’m just going to send it in for repair, which is nothing short of being due to my stupidity.
Click to expand...
Click to collapse
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
toyanucci said:
It's probably stuck in edl mode. Nothing on the screen, no vibration or anything but it shows up in device manager when connected to a computer?
Try the man tool mentioned Here that worked for me.
Click to expand...
Click to collapse
I’ll give it a shot, yeah it doesn’t do anything. Can’t see a display or anything on the screen.
Flashing signed stock firmware:
Latest signed stock firmwares:
Europe (RETEU):
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
India (RETIN):
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
US (RETUS):
https://mirrors.lolinet.com/firmware/moto/guamp/official/RETUS/
All other locations:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Also:
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=sharing
ADB & Fastboot setup:
minimal_adb_fastboot_v1.4.3_setup.exe
drive.google.com
1) Download the A10/A11 firmware for guamp for your region
2) Install ADB & Fastboot (best place is the root directory of C: or wherever your OS resides).
3) Extract the firmware to that ADB & Fastboot folder.
4) Download and install Motorola device drivers. The program is called "Motorola Device Manager".
5) Reboot your phone to the bootloader. To do this, turn it off, then hold down the power and volume down buttons until you see a bugdroid undergoing open-heart surgery.
6) Connect the phone to your PC with your USB cable. Type
Code:
fastboot devices
to check if your device is connected. A serial number should be shown.
7) then run the following command to flash the firmware
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot flash super super.img_sparsechunk.16
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
8) once the flashing is done the device will reboot
note:
1)first boot will take time, so be patient &
2)i am not resposible, if something gone wrong/damaged to your device. you are doing this at your own will.
Use This Script To Update Your Firmware From Fastboot. ot won't format data.
Put this in extracted folder and run
This CAN be done. Please note of course that I am NOT responsible for bricked devices.
I tried it on an XT2113-2 after finding this Moto G Power thread (kudos to the ever-informative @sd_shadow for giving my nerves a boost with his post):
How to downgrade Android 11 to 10
I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to...
forum.xda-developers.com
I successfully downgraded from Android 11 to 40-95-6. I did not have the last Android 10 version 40-95-9, so I had to fall back one more version. But it worked 100% fine, no snags at all.
Instructions for downgrading:
1. *** Bootloader MUST be UNLOCKED ***. Downgrading will NOT work on a locked bootloader, it will fail rollback protection. If you try and it fails, your current firmware is ilkely trashed and you'll have to reflash it.
2. Make sure you have a copy (uncompressed) of the firmware version you want to download to.
3. Copy all unzipped firmware files to your ADB folder, and open a command window.
4. Reboot to bootloader ("adb reboot bootloader" from system, or from power off, press Power + Volume-Down until bootloader screen shows).
5. "fastboot devices" in command window to check connection between phone and PC (I used Windows 7).
6. Manually run all fastboot commands listed below, or use a batch file, or maybe try RSDLite (run flashfile.xml in the firmware folder). RSDLite is old, but the last version of it (6.2.4) worked fine on a Moto G Stylus 2021 that I unlocked and rooted a year ago. It's a fairly simple tool that has aged well thus far.
7. Check that each flash command finished with an OKAY (actually 2 OKAYs). It ANY fail, you should start all over, or suspect that your firmware download is corrupt, or USB cable is bad . . .
8. If ALL files flashed OKAY, "fastboot reboot" or use the Volume and Power keys.
Commands (your firmware may be slightly different, possibly one extra sparsechunk file):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth btfm.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase ddr
fastboot erase userdata ... optional but advised (included in flashfile.xml but not in servicefile.xml)
fastboot oem fb_mode_clear
fastboot reboot
I posted this in the wrong section. I hope a diligant moderator will find and correct my mistake soon.
Moondroid said:
I posted this in the wrong section. I hope a diligant moderator will find and correct my mistake soon.
Click to expand...
Click to collapse
That’s what the report button is for
I've posted in the wrong section
sd_shadow said:
That’s what the report button is for
I've posted in the wrong section
Click to expand...
Click to collapse
I thought about trying that but was afraid it might set off a 3-alarm fire or something. Lol.
Badger50 got it fixed for me.