moto g4 play stuck in bootloop after official motorola update. - Moto G4 Play Questions & Answers

Hi, i updated my moto g4 play (xt1602) to the android update in india. Unfortunately it is in bootloop and wont start to lock screen. Oem is locked and usb debugging is disabled. developed options also not enabled. i used LMSA (Lenovo moto smart assistant) to recover it by flashing original firmware but it is still in bootloop. i have searched on google and forums and found that due to these i.e.(Oem is locked and usb debugging is disabled) i cannot flash any recovery and cannot install any rom through fastboot. Also "adb devices" command does not recognise but "fastboot devices" command shows serial number of my device. i also got oem unlock code from moto website but it said remote failed for "oem unlock" command in fastboot.
(Also i was wondering is there any way that i can edit oem.img and bootloader.img file in official firmware that LMSA downloads and flashes in the device and can that unlock the oem and bootloader )
Is there any way to recover the device or is it bootloop bricked to eternity.
Note: i had my screen replaced and after that i did the update. can it be the issue. (i' ve kept the old broken screen module, can it help recover the device if it is connected.)
Thanks in advance

Can you paste the code of the error?

IkerST said:
Can you paste the code of the error?
Click to expand...
Click to collapse
fastboot oem unlock
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.031s
Now since its bootloop i cant do anything

Try this, and then flash firmware
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase system
If it doesn't work contact me on telegram (so it's easier to communicate) @IkerST

IkerST said:
Try this, and then flash firmware
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase system
If it doesn't work contact me on telegram (so it's easier to communicate) @IkerST
Click to expand...
Click to collapse
fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.283s]
finished. total time: 0.286s
fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.148s]
finished. total time: 0.153s
fastboot erase system
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.133s
so system erase failed.
further flashing firmware with LMSA. phone still in bootloop.

I'm having same issue with my Moto G4 Play. Have you found any solution?

sreekanthpp said:
I'm having same issue with my Moto G4 Play. Have you found any solution?
Click to expand...
Click to collapse
Unfortunately its a paperweight to me now. After having tried all i could, I gave to 4 mobile repair shops and after about half a day trying, they have all given up.
If anybody does find a solution kindly let us know.

Related

Help, my Moto X Style XT1752 Brick :(

Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
https://www.youtube.com/watch?v=njXQYn53SPc
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.
AlexAndroid said:
Hello people, I come with a Moto X XT1572 brickeado, out of nowhere is stuck in the Motorola logo and it does not pass from there, restarting over and over again.
I tried several methods to try to install a stock Firm, 6.0 or 6.1, but without success.
Because I can only connect it in fastboot mode and RSD Lite does not recognize it, I followed the tutorial:
Whatever Firm it is, I throw the following error:
Fastboot flash boot boot.img
(Bootloader) has-slot: boot: not found
Target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB) ...
OKAY
Writing 'boot' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2
I understand and I have read, the problem is initially in the boot, I have tried flashing only the boot, but it does not respond, throwing the same error.
It is worth clarifying that the bootloader is blocked, and if I try to unlock it it throws me:
(Bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Finished. Total time: 0.00s
I can not check that option, since it does not fix je.
Also it is worth clarifying that it does not allow me to enter the recovery, when it enters that option it is automatically restarted returning to the motorola logo again and again.
Do you have any idea what else to try? Thank you in advance.
Click to expand...
Click to collapse
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.
acejavelin said:
Have you tried a factory reset in the stock recovery? From the bootloader select Recovery and let it start, when you get "Dead Andy" with an exclamation mark after the timeout, hold power and tap Vol Up and release both keys. Select Factory reset/Wipe data and let finish and then reboot... First boot can take 20 minutes plus after a reset.
Click to expand...
Click to collapse
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.
AlexAndroid said:
Selecting Recovery restarts the device, returning to the Motorola logo and restarting again and again, without ever entering the recovery mode.
Click to expand...
Click to collapse
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?
acejavelin said:
In the bootloader, can you post the output of 'fastboot getvar all' (just mask out your IMEI number)?
Click to expand...
Click to collapse
You mean this? (attached image)
Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you
AlexAndroid said:
Sorry, I understand what you mean, when I go back to my house, I give you that information. Thank you
Click to expand...
Click to collapse
Do you know how to use fastboot and adb? This is from a computer...
acejavelin said:
Do you know how to use fastboot and adb? This is from a computer...
Click to expand...
Click to collapse
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Micron S8 SDRAM DIE=6Gb M5=x3 M6=x0 M7=x0 M8
(bootloader) ram[1]: =x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ---
(bootloader) cid: 0x0007
(bootloader) channelid: 0x51
(bootloader) uid: 368A71011E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: -----
(bootloader) meid:
(bootloader) date: 12-13-2016
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Feb 5 7:26: 3 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_APAC_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ga389d53 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:27:17 CST 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=7ea7c4c-dirty
(bootloader) hyp.git: git=7ea7c4c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retapac
AlexAndroid said:
Yes, here is the information.
My English is not very good, for that reason sometimes I do not understand je.
(bootloader) date: 12-13-2016
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia/clark:6.0/M
(bootloader) ro.build.fingerprint[1]: PHS24.49-20-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_reta
(bootloader) ro.build.version.full[1]: sia.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
Click to expand...
Click to collapse
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8 (Verify # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot
acejavelin said:
This is the key info... You currently have MPHS24.49-20-16 that was released in January/February, problem is we don't have that firmware and don't know when/if we will get it. That said you should be able to use XT1572_CLARK_RETASIA_DS_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and flash it manually with fastboot. Make sure to open the cmd window as Administrator.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin <- If this step fails, try once more, then continue
fastboot flash bootloader bootloader.img <- If this step fails, try once more, then continue
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8 (Verify # of sparsechunks, match the number with what is in ROM image)
fastboot flash modem NON-HLOS.bin <- If this step fails, try once more, then continue
fastboot erase modemst1 <- If this step fails, try once more, then continue
fastboot erase modemst2 <- If this step fails, try once more, then continue
fastboot flash fsg fsg.mbn <- If this step fails, try once more, then continue
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?
AlexAndroid said:
Thank you very much, I will try with this firmware. Can you do it even though my bootloader is locked?
Click to expand...
Click to collapse
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.
acejavelin said:
Stock firmware images are digitally signed, so yes, you can flash them with a locked bootloader., but downgrading is tricky even with an unlocked bootloader. The key here us to just get it bootable.
Click to expand...
Click to collapse
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s
AlexAndroid said:
Unfortunately it did not work, boot.img, recovery.img and the following throw
sending 'boot' (40960 KB)... OKAY [ 3.857s]
writing 'boot'... INFOPreflash validation failed
FAILED (remote failure)
finished. total time: 4.550s
Click to expand...
Click to collapse
Then your choices are Moto repair or wait for the 20-16 firmware to be released.
acejavelin said:
Then your choices are Moto repair or wait for the 20-16 firmware to be released.
Click to expand...
Click to collapse
Do Motorola's official technical services have the necessary firmware?
AlexAndroid said:
Do Motorola's official technical services have the necessary firmware?
Click to expand...
Click to collapse
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
If you are in warranty and u haven't unlocked your boot loader yet you can give silly reason's like i revived updates last night but battery was low and while updating it turned off and now my phone isn't booting up
acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Hello, finally I take the equipment to an official technical service of Motorola, where they told me that they could not repair it since the cell phone did not take Software. Is this possible or would it be that the technical service did not have the necessary software version?
acejavelin said:
Do they? I'm sure they do... and if you send it in for repair I am sure they can fix it, but they won't give it to you if that is what you are asking. :/
Click to expand...
Click to collapse
Good afternoon, I return the subject after a long time since yesterday I thought to try again, and I found that the cell now turns on, but when trying to complete the initial configuration, after choosing the language gives me to select the wifi networks, where it does not detect any, and I do not enable the jump or forward button, and I'm stuck there again, it's very strange, as soon as I enter that screen, it gives me the option to add a new network, and I can see that says Mac Address with pure zeros, as if it did not have MAC.
If I try to enter the recovery, now I see "No Command" (previously not directly entered), and there is no way to skip this "No Command", I have tried all the methods that appear online.
EDIT: I was able to get into recovery, but I do not know if it can help me now.
Any ideas? he seems to be brigado, but not as much as before
Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.
Edvin73 said:
Flash the right modem for your region in fastboot. You should repeat the fastboot command "fastboot flash modem NON-HLOS.bin" at least two times because the first time it won't "stick". After you'll have to execute "fastboot erase modemst1" and "fastboot erase modemst2" commands and your wi-fi and data signal should return.
Click to expand...
Click to collapse
I still have a problem, when the device is turned on, it always turns on Bootloader mode, and I have to select "Start" to turn it on. This is why when you want to upgrade to Android 7 via OTA, when the device is restarted during installation, it enters Bootloader mode, select "Start", restarts the update, restarts in Bootloader, and remains in an infinite cycle.
Is there a solution to this? I have already activated USB debugging in order to unlock the Bootloader.
Thank you!!

bootloader is bricked

Hello,
I have bricked my bootloader in the past to refresh my bootloader. I have unbricked my phone to bootloader 1.03 with blank flash. Now when i try to flash, erase do ANYTHING it won't allow me because my OEM_LOCKED state. If i try to unlock my bootloader it says:
Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.032s]
finished. total time: 0.036s
but there is no android installed.
When i try to flash a stock rom it says:
Code:
C:\Users\nick\Desktop\total firmware>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.068s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.088s
C:\Users\nick\Desktop\total firmware>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.540s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.576s
C:\Users\nick\Desktop\total firmware>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.548s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.568s
C:\Users\nick\Desktop\total firmware>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.532s]
writing 'dsp'...
(bootloader) Invalid partition name dsp
FAILED (remote failure)
finished. total time: 0.560s
C:\Users\nick\Desktop\total firmware>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (124713 KB)...
OKAY [ 3.993s]
writing 'oem'...
(bootloader) Invalid partition name oem
FAILED (remote failure)
finished. total time: 4.017s
C:\Users\nick\Desktop\total firmware>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (261790 KB)...
Everything is 'invalid partition name'.
when i try to brick my bootloader again to install try again it says
Code:
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.020s]
writing 'sbl1'...
(bootloader) Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.036s
rebooting...
And when i try to flash another bootloader it says:
Code:
PS C:\Users\nick\Desktop\total firmware> fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.250s
PS C:\Users\nick\Desktop\total firmware>
please help
I guess there is a partion problem
Look into this thread
https://forum.xda-developers.com/showthread.php?t=3496912
Sent from my Moto G4 Plus using Tapatalk
Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.
codGmer said:
Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.
Click to expand...
Click to collapse
Did you run all stock steps in order? In particular this one first:
Code:
fastboot flash partition gpt.bin
That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.
If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.
givitago said:
Did you run all stock steps in order? In particular this one first:
Code:
fastboot flash partition gpt.bin
That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.
If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.
Click to expand...
Click to collapse
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
codGmer said:
Did you run all stock steps in order? In particular this one first:
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
Click to expand...
Click to collapse
I too have this question bro .... Plus help me if you find a solution ... I m a newbie... Nd face the same problem as yours
Sounds like fastboot expects a working partition table to start with then.
I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.
Good luck.
givitago said:
Sounds like fastboot expects a working partition table to start with then.
I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.
Good luck.
Click to expand...
Click to collapse
Im affraid i already tried booting twrp but without success.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: 74f9d6fa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: A420B70000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.147s
hey bro , did you get any solution of this problem?
i am getting
fastboot reason : failed to initialize partition table
any solution?
king_priithvi said:
hey bro , did you get any solution of this problem?
Click to expand...
Click to collapse
Provide more information of your problem/situation,
what happened ?
Have you flashed any firmware ?
Took any OTA ?
What was firmware version you were using ?
Tried latest December's firmware ? This> https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I think you're flashing older bootloader & GPT then it is already installed on your device;
take a look here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
from that thread download the latest ROM and firstly flash GPT and boot-loader by following command:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
but however after flashing the latest firmware the current blankflash that we have won't work, because GPT and boot-loader version is higher.
now after you flashed the GPT and bootloader then flash the whole firmware by following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash 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
Now once you flashed it then you're good to go:good:
i cant flash anything , my android is not installed
it kept saying
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No BootImage Found. skip to fastboot
boot up failed
king_prithvi said:
i cant flash anything , my android is not installed
it kept saying
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No BootImage Found. skip to fastboot
boot up failed
Click to expand...
Click to collapse
Are you able to flash the latest stock ROM via fastboot? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I am getting an error when I try to flash twrp. I want to make sure I am doing it right
in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img
then I got this error
target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s
has anyone else run into this problem. Am I doing something wrong?
kiyip said:
I am getting an error when I try to flash twrp. I want to make sure I am doing it right
in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img
then I got this error
target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s
has anyone else run into this problem. Am I doing something wrong?
Click to expand...
Click to collapse
What device do you have? I'm guessing it's a Moto X4 from the TWRP name?
Are you on Nougat or Oreo? From looking at this thread, you've got 2 different build: https://forum.xda-developers.com/moto-x4/development/dev-testing-t3707432
If you are running a X4, you may have better luck over there rather than here on the Moto G4 forums, as there's more users familiar with the A/B partitioning on the Moto X4.
Ohh my bad, I had like 6 xda tabs open, I actually meant to post it there. My bad man, thank you!
got the same problem any luck yet?
Any luck yet? I got a suggestion that the problem could only get fixed flashing the memory of the phone directly with this kind of device... (search for the octopus box, I cant post links yet im new here) but im lost and they say that thing is expensive... I really want my phone to be saved on my computer. My case is exactly the same as you.... oem locked and failed partition everything and remote failure.
SOLVED!! Failed to initialize partition table
..
First of all convert phone to hard brick to Softbrick...
After that if you want to bootup phone than..IT shows bootloader log::
Failed to initialize partition Table
SOLUTION:-
1) Download Minimal ADB Drivers , gpt.bin, Motorola Device driver
For link mail me on [email protected]
2.) Now Install adb and motorola drivers .
3.) Copy gpt.bin file in ADB folder in installed drive.
4.) Open Minimal ADB and Fastboot.exe
Now Run the following command
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot
The cell phone should restart after this if you do not type the last code and enter if still yes it is not just hang up and call to enter the fastboot.
Now YOUR PROBLEM SOLVED
codGmer said:
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
Click to expand...
Click to collapse
Even I got the same error. Its because adb couldn't find the gpt.bin file in the adb folder from where you had executed the command window.
Copy the gpt.biin file in that folder and try again, that should work.

HARD BRICKED MOTO G4 plus

my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
tried this too but device get recognise
Cooltango26 said:
my phone is hard bricked and the oem is locked and no custom recovery
tried to unlock oem but it gives this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.014s]
finished. total time: 0.015s
phone wont open how do i allow oem unlock
i even tried flashing stock rom as it does not required bootloader unlocks but stock rom wont install it gives error
C:\Users\MOHIT\Downloads\Compressed\ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.242s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.715s
plz help me out guys .....:crying::crying::crying::crying:
Click to expand...
Click to collapse
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.
ADITYA_KUMAR said:
How did your phone got bricked?
According to you,you are trying to unlock bootloader but it doesn't succed. Why are you flashing stock rom in your phone?
plzz elaborate.
Click to expand...
Click to collapse
after the official update from ....update in my device .......my device was struck in boot loop ...so i tries flashing the stock rom to repair that ....during flashing it giving the above mention error ........
Only other things I can think of is perhaps holding down your power button (for up to 2-3 minutes) to force a hard shutdown, and then try booting. Alternatively, hold down both the power and volume down key, see if you can boot into the bootloader (which it looks like you can, if you're trying to fastboot the stock ROM). If so, then try to boot into the stock recovery and try a cache wipe or a factory reset (the factory reset will obviously wipe your data).
If your device is under warranty (and you did not unlock your bootloader at any point), the service centre might be the best bet for you, as we can't do anything with a locked bootloader and you're unable to boot to get to OEM unlocking...
The new [Updated] blankflash file for Moto g4 plus [June security patch ]
Hello friends
here is the new [Updated] blankflash file for June security patch
i hope it will help you. here is complete guide https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
about how to install it.
if it's works for you please let me know:highfive:

Moto G4 Plus going into boot loader when turned off

I flashed latest moto g4 plus ROM which has April security patch, when I turn off or reboot the device it is going to bootloader mode. I also tried flashing the ROM again but it says bootloader slot is not found
Please help
Try this commands in fastboot mode
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
it shows the following
sid3589 said:
Try this commands in fastboot mode
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
C:\mfast>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.172s]
finished. total time: 0.172s
C:\mfast>fastboot oem fb_mode_clear
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.172s]
finished. total time: 0.172s

MOTO G5 PLUS, stuck in fastboot flash mode

Failed to pass validation, backup to fastboot
Boot up failed.
The flashboot flash mode screen says:
Product/Variant : potter 000000000000000 32GB P3B
....
oem_locked
All variables: https://file.io/rF0SqpBhP398
On running the cammands:
C:\ProgramData\RSA\Download\newfolder>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.123s
Every command is failing by saying remote failure.
I saw some flashboot commands and tried to run it. But I think it required oem unlocked. How to do that, can anyone please help me?
The Rescue and Smart Assistant software isn't working because the IMEI is showing all 0 (zero) here. And it says something is wrong and should go to customer support. Please help me guys. Let me know what should I do now? It is out of warranty as well.
For the image files I am using the same I downloaded via the rescue and smart assistant software.
#motog5 #motog5plus #oem_locked.
ssoni0097 said:
Failed to pass validation, backup to fastboot
Boot up failed.
The flashboot flash mode screen says:
Product/Variant : potter 000000000000000 32GB P3B
....
oem_locked
All variables: https://file.io/rF0SqpBhP398
On running the cammands:
FAILED (remote failure)
finished. total time: 0.123s
Every command is failing by saying remote failure.
I saw some flashboot commands and tried to run it. But I think it required oem unlocked. How to do that, can anyone please help me?
Click to expand...
Click to collapse
Within phone's Android -> Settings -> Developer options you have to enable "OEM Unlock" and reboot phone afterwards. Then you have to unlock phone's bootloader
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock
fastboot reboot
jwoegerbauer said:
Within phone's Android -> Settings -> Developer options you have to enable "OEM Unlock" and reboot phone afterwards. Then you have to unlock phone's bootloader
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock
fastboot reboot
Click to expand...
Click to collapse
But the phone is not turning on na .. It is stuck on the fastboot flash mode screen. How do I unlock the oem then
Try
Code:
fastboot reboot
to exit Fastboot mode
jwoegerbauer said:
Try
Code:
fastboot reboot
to exit Fastboot mode
Click to expand...
Click to collapse
The fastboot opens again. As I said, it is stuck there.
On selecting start on fastboot, it says
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed.
Try to re-flash phone's Stock ROM.
jwoegerbauer said:
Try to re-flash phone's Stock ROM.
Click to expand...
Click to collapse
How to do that? Can you please help .. please
I tried following some steps, downloading the files from a website. But it results into fail.
Fix a dead Moto G5 plus and fix bootloop problem Animetrick
Recently my moto g5S plus got stuck on moto screen and I was flash with this method and this got worked on my phone. Now my phone was completely working and
animetrick.com
for example:
C:\Program Files (x86)\Minimal ADB and Fastboot1>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.023s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.157s
@sd_shadow can you help please?
What you basically are doing wrong is NOT to use Motorola's proprietary mfastboot but Google's fastboot.
Must admit I didn't know of this, too.
jwoegerbauer said:
What you basically are doing wrong is NOT to use Motorola's proprietary mfastboot but Google's fastboot.
Must admit I didn't know of this, too.
Click to expand...
Click to collapse
Tried with mfastboot as well. It shows the same thing ..
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 1.554s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.562s
jwoegerbauer said:
Within phone's Android -> Settings -> Developer options you have to enable "OEM Unlock" and reboot phone afterwards. Then you have to unlock phone's bootloader
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot flashing unlock
fastboot reboot
Click to expand...
Click to collapse
Motorola devices require an unlock code
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
ssoni0097 said:
Tried with mfastboot as well. It shows the same thing ..
C:\mfastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 1.554s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.562s
Click to expand...
Click to collapse
What does getvar all say?
Remove the imei line before posting
Code:
fastboot getvar all
You need the firmware that matches
Device Model #, Codename, and Software Channel.
If you have a windows PC try LMSA's fash rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
jwoegerbauer said:
What you basically are doing wrong is NOT to use Motorola's proprietary mfastboot but Google's fastboot.
Must admit I didn't know of this, too.
Click to expand...
Click to collapse
I generally do not use mfastboot, it has not been updated in years.
but if fastboot.exe fails, it doesn't hurt to try mfastboot.
sd_shadow said:
What does getvar all say?
Remove the imei line before posting
Code:
fastboot getvar all
You need the firmware that matches
Device Model #, Codename, and Software Channel.
If you have a windows PC try LMSA's fash rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
https://file.io/EEveR0bZCRDV
Tried the rescue and smart assistant tool as well. But it catches the imei as 0, and stops there.
Removed imei line below:
Code:
C:\ProgramData\RSA\Download\newfolder>mfastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 3fb4905f
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 7D81062600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.081s
sd_shadow said:
What does getvar all say?
Remove the imei line before posting
Code:
fastboot getvar all
You need the firmware that matches
Device Model #, Codename, and Software Channel.
If you have a windows PC try LMSA's fash rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Tried every version of POTTER_RETAIL_8.1.0.XX (8 zip files) and run mfastboot oem get_unlock_data. But all resulted into the failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
Please help.
ssoni0097 said:
Tried every version of POTTER_RETAIL_8.1.0.XX (8 zip files) and run mfastboot oem get_unlock_data. But all resulted into the failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
Please help.
Click to expand...
Click to collapse
What does getvar all say?
sd_shadow said:
What does getvar all say?
Click to expand...
Click to collapse
MOTO G5 PLUS, stuck in fastboot flash mode
Failed to pass validation, backup to fastboot Boot up failed. The flashboot flash mode screen says: Product/Variant : potter 000000000000000 32GB P3B .... oem_locked All variables: https://file.io/rF0SqpBhP398 On running the cammands...
forum.xda-developers.com
Posted it above
ssoni0097 said:
Posted it above
Click to expand...
Click to collapse
Have you ever fetched the unlock code from Motorola? No way without it If you're not able to boot into your device try to flash the latest firmware and carry on from there.
Here's how to flash the latest firmware:
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com
Wolfcity said:
Have you ever fetched the unlock code from Motorola? No way without it If you're not able to boot into your device try to flash the latest firmware and carry on from there.
Here's how to flash the latest firmware:
Click to expand...
Click to collapse
please share the link
I tried it by following instructions from Motorola site. The first command to get code is
mfastboot oem get_unlock_data. But it results into failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
ssoni0097 said:
please share the link
I tried it by following instructions from Motorola site. The first command to get code is
mfastboot oem get_unlock_data. But it results into failure.
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.017s]
finished. total time: 0.019s
Click to expand...
Click to collapse
Did you check if your devices bootloader is unlockable at all?
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
I would recommend to not use mfastboot as it is outdated. Better try this one:
[TOOL][WINDOWS] ADB & Fastboot++ | February 2023
NFO: • Versions: Installer, Portable & ADBKit • Android Debug Bridge & Fastboot updated to latest v1.0.41 (Version 34.0.0-9570255, February 2023) Features: • Installation Folder chooseable (Installer) • Desktop & Start Menu Shortcuts (Installer)...
forum.xda-developers.com
As written above, best may be to flash the latest signed firmware and start from scratch.
Follow this tutorial (the upper part):
[GUIDE] Moto G5 Plus: Flashing Stock Firmware & Rooting [2021]
Flashing signed stock firmware: You need: Latest signed stock firmware: Europe (RETEU): https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/potter/official/RETEU/ India (RETIN)...
forum.xda-developers.com

Categories

Resources