Related
Hey guys,
I'm new to learning about the technical details of the Android system, and specifically my MOTO RAZR M. Yesterday my phone lost power, then was sent into a boot loop. The only functional feature from the boot menu is the AP Fastboot function. All the other options just take me back into the boot loop. Ive tried RSD, and Droid utility, with no success. All of them return an error and "FAIL." My guess would be that i'm tying the wrong version? If anyone can give me a point in the right direction, or any assistance at all, that would be great. Thanks!
IDK if this information helps, but here it is
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version-bootloader: 109B(*)
(bootloader) product: smq
(bootloader) secure: yes
(bootloader) mid: 0058
(bootloader) version: 0.5
(bootloader) qe: qe 0/1
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 8GB
(bootloader) reason: Boot menu selected
(bootloader) revision-hardware: 0x82A0
(bootloader) cpu: MSM8960 CS
(bootloader) uid: BBACD70802000100000000000000
(bootloader) cid: 0x02
all:
finished. total time: 0.659s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>
Bump, because i could really use some guidence, even the right reading material
The reason it's failing would help a lot more. What's it saying in RSD?
BTW, I'm in No-Dak too. Cool to see someone else on such a busy website.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
The reason it's failing would help a lot more. What's it saying in RSD?
BTW, I'm in No-Dak too. Cool to see someone else on such a busy website.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
When trying to use RSD lite to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml, i ge tthe following on the phone:
update gpt_main version failed
preflash validation failed for GPT
RSD lite stops at 1/19 with a similar message.
Okay, you're getting that message because you're flashing an older FW. Flash FE the same or newer as what was on your phone.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
Okay, you're getting that message because you're flashing an older FW. Flash FE the same or newer as what was on your phone.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So a 4.4.2 will work, regardless? Also, do you know where I can find that file? Ive had trouble looking for it.
Here's a link to all the FW. 4.4.2 should work to clear the fail: http://www.drdevs.com/devs/FXZ-files/XT907 (Droid RAZR M)/
RikRong said:
Here's a link to all the FW. 4.4.2 should work to clear the fail: http://www.drdevs.com/devs/FXZ-files/XT907 (Droid RAZR M)/
Click to expand...
Click to collapse
I tried it with VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml, and still failed on the 1/17 on GPT.bin, oddly enough? What could be causing this?
bump again, really need to get my phone working?
I thought flashing the latest version would always work regardless?
northdakota2170 said:
bump again, really need to get my phone working?
I thought flashing the latest version would always work regardless?
Click to expand...
Click to collapse
Sorry, I'm not good on the technical stuff, but it looks like you're getting some good help on DR.
Sent from my HTC6525LVW using Tapatalk
Hey guys, I used house of moto with the 4.4.2 file, and was successfully able to restore my phone. Thanks for the help!
I had a similar issue with my XT905 (Australian RAZR M)
Lost power due to a dead battery, and after it charged and started up, it entered a continuous boot loop. I could access recovery and the bootloader, so I attempted to reinstall multiple firmwares using fast boot, RSD Lite, or through a recovery (CWM and TWRP) but had no luck booting any. This was a week or so ago.
Just found this thread today and as I've never used the HouseOfMoto utitlity I thought I'd give it a shot. I installed the stock Telstra jellybean firmware using it and it successfully booted an OS for the first time. I can only assume the HouseOfMoto utility installs ROMs in a different fashion from RSD Lite. Had to be a jellybean ROM as the kitkat bootloader isn't out for the XT905 yet.
If anyone else has a similar issue please give this method a shot.
justin89h said:
I had a similar issue with my XT905 (Australian RAZR M)
Lost power due to a dead battery, and after it charged and started up, it entered a continuous boot loop. I could access recovery and the bootloader, so I attempted to reinstall multiple firmwares using fast boot, RSD Lite, or through a recovery (CWM and TWRP) but had no luck booting any. This was a week or so ago.
Just found this thread today and as I've never used the HouseOfMoto utitlity I thought I'd give it a shot. I installed the stock Telstra jellybean firmware using it and it successfully booted an OS for the first time. I can only assume the HouseOfMoto utility installs ROMs in a different fashion from RSD Lite. Had to be a jellybean ROM as the kitkat bootloader isn't out for the XT905 yet.
If anyone else has a similar issue please give this method a shot.
Click to expand...
Click to collapse
On my second reboot it entered a boot loop again so scratch that advice. Probably a hardware issue like I originally thought
After searching around for a bit trying different (known) exploits, I've come to the conclusion that my phone's bootloader cannot be unlocked. If you know otherwise, please link me to the thread. My original goal was to install CyanogenMod, but that requires an unlocked bootloader- again, apparently not possible. Plan B is now to use Safestrap and install a custom ROM that way.
I've successfully rooted it, but that's it. Currently running:
Android Version: 4.1.2,
System Version: 98.30.1
Build Number: 9.8.1Q-94-1
Build Date: Thu Sep 26 12:24:41 CDT 2013
I'm looking for a like-CyanogenMod ROM that will work with Safestrap/locked bootloader.
Any help?
What is your kernel? That android version should be early enough to unlock your boot loader.
Sent from my HTC Vivid 4G using XDA Free mobile app
projectisaac said:
What is your kernel? That android version should be early enough to unlock your boot loader.
Sent from my HTC Vivid 4G using XDA Free mobile app
Click to expand...
Click to collapse
Kernel Version: 3.0.31-gef7deb8 [email protected] #1
SMP PREEMPT Thu Sep 26 12:38:22 CDT 2013
I've tried Motopocalypse several times- here's the output. I put the error in bold.
[email protected]:motopocalypse% ./run.sh
[*] Press enter to unlock your bootloader...
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing unlock tool...
4021 KB/s (38280 bytes in 0.009s)
[*] Unlocking phone...
[+] TrustZone target address resolved to 2a020a02
[-] TrustZone write failed: -11.
[*] Cleaning up...
[*] Unlocking complete. Rebooting into bootloader mode.
[*] Press enter once the phone has rebooted into bootloader mode.
[*] Displaying bootloader variables:
(bootloader) version-bootloader: 109B(*)
(bootloader) product: smq
(bootloader) secure: yes
(bootloader) mid: 0058
(bootloader) version: 0.5
(bootloader) serialno: ##########
(bootloader) qe: qe 1/1
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 8GB
(bootloader) reason: Flash Failure
(bootloader) revision-hardware: 0x82A0
(bootloader) cpu: MSM8960 CS
(bootloader) uid: C4693B0A02000300000000000000
(bootloader) cid: 0x02
all:
finished. total time: 0.019s
[*] Press enter to reboot and exit.
resuming boot...
OKAY [ 0.005s]
finished. total time: 0.005s
[email protected]:motopocalypse%
Also, I came across this link with someone in what appears the exact same boat- http://forum.xda-developers.com/showthread.php?t=2670263
ProoN said:
After searching around for a bit trying different (known) exploits, I've come to the conclusion that my phone's bootloader cannot be unlocked. If you know otherwise, please link me to the thread. My original goal was to install CyanogenMod, but that requires an unlocked bootloader- again, apparently not possible. Plan B is now to use Safestrap and install a custom ROM that way.
I've successfully rooted it, but that's it. Currently running:
Android Version: 4.1.2,
System Version: 98.30.1
Build Number: 9.8.1Q-94-1
Build Date: Thu Sep 26 12:24:41 CDT 2013
I'm looking for a like-CyanogenMod ROM that will work with Safestrap/locked bootloader.
Any help?
Click to expand...
Click to collapse
Upgrade to 4.4.2 KDA20.62-10.1 with RSD Lite, then root and unlock your bootloader.
Go here > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
Upgrade to 4.4.2 KDA20.62-10.1 with RSD Lite, then root and unlock your bootloader.
Go here > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
This phone is currently in an AP Fastboot loop-thing. I'm able to do the up/down/power combo then boot up normally, but otherwise any time it restarts, it always goes into Fastboot. It says: Fastboot Reason: "Flash Failure"
Also, booting into "Recovery" just brings up the Droid icon with a red exclamation. Should I figure these out before upgrading the firmware and continuing to unlock the bootloader? Or will it even matter?
ProoN said:
This phone is currently in an AP Fastboot loop-thing. I'm able to do the up/down/power combo then boot up normally, but otherwise any time it restarts, it always goes into Fastboot. It says: Fastboot Reason: "Flash Failure"
Also, booting into "Recovery" just brings up the Droid icon with a red exclamation. Should I figure these out before upgrading the firmware and continuing to unlock the bootloader? Or will it even matter?
Click to expand...
Click to collapse
It would be good to know either way, but it shouldn't stop you from continuing to upgrade and unlocking the bootloader.
----------------------------------------------------------------------------------------------------------------------
1. For the fastboot loop go [HERE] and follow #8.
2. The "dead droid" screen is recovery. > https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88933/p/30,6720,8577
Code:
From the Android system recovery screen, press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key.
1. For the fastboot loop go [HERE] and follow #8.
I've tried this several times and it still boots into AP Fastboot Flash Mode, both on OSX and a Windows system. Would flashing the stock ROM remedy?
ProoN said:
. Would flashing the stock ROM remedy?
Click to expand...
Click to collapse
Not sure. What happen to cause the fastboot boot loop?
ATTACK said:
Not sure. What happen to cause the fastboot boot loop?
Click to expand...
Click to collapse
I'm not sure, honestly. It seems like it happened after I installed Safestrap. But I managed to fix it by flashing a stock image back onto it.
So now, I'm using RSD Lite 6.1.5 on Windows, trying to upgrade the firmware to 4.4.2. I had a flash failure alert after decompressing, "getvar" something or other. Edited the xml and removed that line, now it seems to be stuck at '2/20 flash partition "gpt.bin"'
Just an update so this can be "Solved" even though it went way off topic. I successfully flashed it to 4.4.2.
That gpt.bin error seemed to be RSD specific. I ended up manually flashing each file one by one. Had a hiccup at the "NON-HLOS.bin" file (modem), something about the size. Came across a thread suggesting to use a different version of fastboot, so I did (the fastboot.osx version). Restarted the entire process, grimaced when I got to the modem bit, but it ended up working. It went through the sending/writing process of system.img for about 10 minutes, repeating the same message for some reason (100ish times). But I just let it go through. At this moment-
Android Version: 4.4.2
Kernel Version: [email protected] #1
Fri May 2 00:30:06 PDT 2014
Build Number: KDA20.62-10.1
I'd just like to apologize for being a n00b in this area. Like most, the biggest worry was bricking the phone so I was kind of hesitant to do anything on my own, even though I read through several tutorials repeatedly.
Much appreciation though, will be looking into unlocking it now that I've gotten this far.
Unlocking it is the easy part... Root with towel root then find motoapokalypse.apk and run it... Then install flashify and flash the latest twrp.
Sent from my Amazon Tate using XDA Free mobile app
ProoN said:
Just an update so this can be "Solved" even though it went way off topic. I successfully flashed it to 4.4.2.
That gpt.bin error seemed to be RSD specific. I ended up manually flashing each file one by one. Had a hiccup at the "NON-HLOS.bin" file (modem), something about the size. Came across a thread suggesting to use a different version of fastboot, so I did (the fastboot.osx version). Restarted the entire process, grimaced when I got to the modem bit, but it ended up working. It went through the sending/writing process of system.img for about 10 minutes, repeating the same message for some reason (100ish times). But I just let it go through. At this moment-
Android Version: 4.4.2
Kernel Version: [email protected] #1
Fri May 2 00:30:06 PDT 2014
Build Number: KDA20.62-10.1
I'd just like to apologize for being a n00b in this area. Like most, the biggest worry was bricking the phone so I was kind of hesitant to do anything on my own, even though I read through several tutorials repeatedly.
Much appreciation though, will be looking into unlocking it now that I've gotten this far.
Click to expand...
Click to collapse
AWESOME!:good: Glad you got it all worked out. Now just root, bl unlock and your good to go.
Hi guys, first time posting.
I have now a moto g4 plus that was OTA updated from Android 6.x to Android 7.0 and that caused it to bootloop and die later. Before that I had no knowledge of ROMs, bootloaders, fastboot, flashing, sideloads, ADB, RSD or anything like that. But this last week I acquired a superficial knowledge thanks to google, foruns of all kinds and you guys from XDA.
My phone started doing nothing at all and I progressed, solving the not charging battery problem (disconnecting and reconnecting it), the not lighting up led (with the original turbo charger and a three minute hold of the vol - and power up buttons) and finally accessing the fastboot mode and later the recovery mode which allowed me to dive into all kinds of tutorials about the reasons that I could not use ADB (usb debugging disabled) or flash custom ROMs (unlocked bootloader and unchecked "allow oem unlock"). All the research ended up to the conclusion that the only thing I could do was to flash the stock rom of Android 7.0 through RSD or fastboot/mfastboot. Did that, wiped cache and users data/factory reset and... nothing. The phone installed the stock ROM but it still doesn't pass the Motorola logo screen.
After that I came to three possible solutions:
1) Try to install the brasilian ROM version I have in my sister's Moto G4 plus (NPJS 25.93-14.4), but I can't find it anywhere (thought about backing it up from her phone, but root would be needed and her phone is still in warranty).
2) To wait till Android 7.1.1 or 7.1.2 stock ROM be released for Moto g4 plus flash it and hope it do the trick.
3) Send to Motorola assistance so they change it's motherboard (last resource considering the phone is not in warranty anymore).
Well, as I said my knowledge is new and superficial so I need your help and opinion about my conclusions and other possible solutions.
I thank you all for all I've learned so far and for any tips you can spare on me. Thanks again and keep doing what you do here.
Kyrohn said:
Hi guys, first time posting.
I have now a moto g4 plus that was OTA updated from Android 6.x to Android 7.0 and that caused it to bootloop and die later. Before that I had no knowledge of ROMs, bootloaders, fastboot, flashing, sideloads, ADB, RSD or anything like that. But this last week I acquired a superficial knowledge thanks to google, foruns of all kinds and you guys from XDA.
My phone started doing nothing at all and I progressed, solving the not charging battery problem (disconnecting and reconnecting it), the not lighting up led (with the original turbo charger and a three minute hold of the vol - and power up buttons) and finally accessing the fastboot mode and later the recovery mode which allowed me to dive into all kinds of tutorials about the reasons that I could not use ADB (usb debugging disabled) or flash custom ROMs (unlocked bootloader and unchecked "allow oem unlock"). All the research ended up to the conclusion that the only thing I could do was to flash the stock rom of Android 7.0 through RSD or fastboot/mfastboot. Did that, wiped cache and users data/factory reset and... nothing. The phone installed the stock ROM but it still doesn't pass the Motorola logo screen.
After that I came to three possible solutions:
1) Try to install the brasilian ROM version I have in my sister's Moto G4 plus (NPJS 25.93-14.4), but I can't find it anywhere (thought about backing it up from her phone, but root would be needed and her phone is still in warranty).
2) To wait till Android 7.1.1 or 7.1.2 stock ROM be released for Moto g4 plus flash it and hope it do the trick.
3) Send to Motorola assistance so they change it's motherboard (last resource considering the phone is not in warranty anymore).
Well, as I said my knowledge is new and superficial so I need your help and opinion about my conclusions and other possible solutions.
I thank you all for all I've learned so far and for any tips you can spare on me. Thanks again and keep doing what you do here.
Click to expand...
Click to collapse
Hello Kyrohn, before I go into any specific idea on what you should do have you ever tried considering flashing Lineage OS onto your device?
if your phone has charge i would suggest you to do the following
1. make sure it's switched off, drain the charge and then recharge if you can't be sure if it's switched off or not.
2. install your drivers properly.
3. then connect your device(in switched off condition) via usb cable while simultaneously holding power button and volume down button only.
4. the phone should enter into a black area and from there reboot to bootloader.
5. follow this link properly
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
this should do it. cuz it should always boot to recovery/bootloader from moto screen
HIT LIKE IF IT HELPED
justinwgeiger said:
Hello Kyrohn, before I go into any specific idea on what you should do have you ever tried considering flashing Lineage OS onto your device?
Click to expand...
Click to collapse
Hi Justin, thanks for reply. Lineage OS is a custom ROM, right? So the stock bootloader won't allow me to flash this ROM considering my bootloader is locked and the OEM unlock option is unchecked (and inaccessible).
Have you tried flashing stock marshmallow?
Kyrohn said:
Hi Justin, thanks for reply. Lineage OS is a custom ROM, right? So the stock bootloader won't allow me to flash this ROM considering my bootloader is locked and the OEM unlock option is unchecked (and inaccessible).
Click to expand...
Click to collapse
Okay I understand, I will guide you through the process of unlocking your bootloader then.
Requirements:
A computer and a usb cord,
Moto G4/G4 Plus,
ADB/Fastboot Drivers: https://www.androidfilehost.com/?fid=745425885120698566,
Moto G4/G4 Plus Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481,
Once you have installed the Minimal ADB and Fastboot tool, launch the tool from the desktop icon named Minimal ADB and Fastboot. You should be brought to a command window.
Now power down your phone and hold the volume down and power button at the same time. you should see a screen pop up. then press the volume down button until you see bootloader and leave it there.
Now at the command window, type:
Code:
fastboot oem get_unlock_data
It should return with something like this:
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
After that, go to paste it all into notepad (A Windows application) and delete the bootloader text and all other spaces so it looks like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Go to Motorola’s bootloader unlock site and login with Google. Paste the entire code from notepad into the input box there. Then click can my device be unlocked and agree to the terms.
You will then be sent an email to unlock your bootloader.
Put the key that they send you into notepad and put it in the command line like shown below:
Code:
fastboot oem unlock "YOURKEY" (Replace YOURKEY with the key you received)
It will unlock your device. Congratulation you have successfully unlocked your device.
Credits:
devs-lab
If you have any questions or concerns just ask me and I will try my best to help you out. From this point forward you should be able to find your way throughout the forums to install a custom recovery. If not just ask me and I will guide you through that too. Glad to help, .
MisterSteve said:
Have you tried flashing stock marshmallow?
Click to expand...
Click to collapse
Hi Steve, yes I tried, but I can't downgrade the system, the stock bootloader doesn't allow me
justinwgeiger said:
Okay I understand, I will guide you through the process of unlocking your bootloader then.
Requirements:
A computer and a usb cord,
Moto G4/G4 Plus,
ADB/Fastboot Drivers: https://www.androidfilehost.com/?fid=745425885120698566,
Moto G4/G4 Plus Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481,
Once you have installed the Minimal ADB and Fastboot tool, launch the tool from the desktop icon named Minimal ADB and Fastboot. You should be brought to a command window.
Now power down your phone and hold the volume down and power button at the same time. you should see a screen pop up. then press the volume down button until you see bootloader and leave it there.
Now at the command window, type:
Code:
fastboot oem get_unlock_data
It should return with something like this:
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
After that, go to paste it all into notepad (A Windows application) and delete the bootloader text and all other spaces so it looks like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Go to Motorola’s bootloader unlock site and login with Google. Paste the entire code from notepad into the input box there. Then click can my device be unlocked and agree to the terms.
You will then be sent an email to unlock your bootloader.
Put the key that they send you into notepad and put it in the command line like shown below:
Code:
fastboot oem unlock "YOURKEY" (Replace YOURKEY with the key you received)
It will unlock your device. Congratulation you have successfully unlocked your device.
Credits:
devs-lab
If you have any questions or concerns just ask me and I will try my best to help you out. From this point forward you should be able to find your way throughout the forums to install a custom recovery. If not just ask me and I will guide you through that too. Glad to help, .
Click to expand...
Click to collapse
Thanks for the reply and patience again Justin. But as I said before the option "Allow OEM Unlock" in Android Settings > Developer Options is unchecked. So when I try unlock the bootloader with the commands you passed I get the following error: Check 'Allow OEM Unlock' in Android Settings > Developer Options. But I can't do that considering the phone doens't boot Android.
Ayan Uchiha Choudhury said:
if your phone has charge i would suggest you to do the following
1. make sure it's switched off, drain the charge and then recharge if you can't be sure if it's switched off or not.
2. install your drivers properly.
3. then connect your device(in switched off condition) via usb cable while simultaneously holding power button and volume down button only.
4. the phone should enter into a black area and from there reboot to bootloader.
5. follow this link properly
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
this should do it. cuz it should always boot to recovery/bootloader from moto screen
HIT LIKE IF IT HELPED
Click to expand...
Click to collapse
Hi Ayan, thanks for reply. Tried all of that before, but tried again now just in case I had made something wrong the first time. It does everything as it's supposed to do, but after reboot it still doesn't pass the logo screen
Kyrohn said:
Hi Steve, yes I tried, but I can't downgrade the system, the stock bootloader doesn't allow me
Click to expand...
Click to collapse
You should no use the bootloader and gpt commands as the bootloader is not downgraded once it has been updated.leave those two and try to fastboot stock marshmallow.
[email protected] said:
You should no use the bootloader and gpt commands as the bootloader is not downgraded once it has been updated.leave those two and try to fastboot stock marshmallow.
Click to expand...
Click to collapse
Hi Chaitu. I tried that now but I'm getting an "invalid PIV signed" error. Could you check the commands I'm using?
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Maybe I'm using one I shouldn't. The first error appears on this command line "mfastboot flash oem oem.img" and the error is "Invalid PIV signed oem image". I also tried the next line "mfastboot flash system system.img_sparsechunk.0" and the error is "Invalid PIV signed system image". Isn't that an error when we use an incorrect ROM for a region? I'm trying the asian ROM cause I couldn't found a brasilian one.
Just tried to flash a supposed brasilian retailed marshmallow ROM, but got the same PIV error. Any ideas about the reason why?
Kyrohn said:
Just tried to flash a supposed brasilian retailed marshmallow ROM, but got the same PIV error. Any ideas about the reason why?
Click to expand...
Click to collapse
Could redownload your ROM to double-check it's not corrupted. Also, is your device carrier unlocked or provided by a carrier? I've had a quick look on that error and in a few cases may be due to a carrier restriction.
However, in order to downgrade, you need an unlocked bootloader which isn't achievable as you've mentioned. And the fast boot won't work either...
When did you buy your device? I recall reading on the Motorola website the warranty is 12 months in Brasil, unless you've been told different? (Edit:https://help.motorola.com/hc/apps/settings/legal/global/pt-br/index.html?t=T1700272834 unless this is out of date)
echo92 said:
Could redownload your ROM to double-check it's not corrupted. Also, is your device carrier unlocked or provided by a carrier? I've had a quick look on that error and in a few cases may be due to a carrier restriction.
However, in order to downgrade, you need an unlocked bootloader which isn't achievable as you've mentioned. And the fast boot won't work either...
When did you buy your device? I recall reading on the Motorola website the warranty is 12 months in Brasil, unless you've been told different? (Edit:https://help.motorola.com/hc/apps/settings/legal/global/pt-br/index.html?t=T1700272834 unless this is out of date)
Click to expand...
Click to collapse
Hi Echo, thanks for reply. I'm almost sure the phone isn't locked by carrier, but can't assure that. Your're right about the warranty but I didn't buy the phone new, it's a used phone and due to Motorola legal contract the warranty is intransferable. And even if wasn't I asked for the bootloader unlock code in one of the tutorials, so I lost the warranty cause of that too.
About this "PIV", what does it mean? How can I find out the required PIV for my phone, do you have any ideia about that?
Thanks again.
Kyrohn said:
Hi Echo, thanks for reply. I'm almost sure the phone isn't locked by carrier, but can't assure that. Your're right about the warranty but I didn't buy the phone new, it's a used phone and due to Motorola legal contract the warranty is intransferable. And even if wasn't I asked for the bootloader unlock code in one of the tutorials, so I lost the warranty cause of that too.
About this "PIV", what does it mean? How can I find out the required PIV for my phone, do you have any ideia about that?
Thanks again.
Click to expand...
Click to collapse
Ah okay, so we've got no warranty/Motorola will charge for repairs, gotcha (and is probably looking like a motherboard repair )
As for PIV - I've read that is read by the bootloader to verify if your image is signed properly (i.e. by Motorola) and thus if it's not the right signature will fail to flash. Short of obtaining the correct, signed, image for your device (what is your device btw?), I'm not sure if you'll be able to bypass that. You may wish to have a look here, see if there are any images for your device (though I cannot say if they'll flash properly). https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
The strange thing is that flashing the stock Nougat ROM as you mentioned (and Ayan suggested) should have worked (since the NPJ25.93-14 build seems to be a global, universal build), the only thing I can think of was that something happened with the Marshmallow build on there (either a bad flash or an incorrect ROM, for example), but without asking the former owner, we just don't know.
For information, are you able to reboot into the bootloader, attach your device to your computer and in minimal ADB, execute 'fastboot getvar all' and post the info here, please? You may wish to remove your IMEI and serial number from the output.
echo92 said:
Ah okay, so we've got no warranty/Motorola will charge for repairs, gotcha (and is probably looking like a motherboard repair )
As for PIV - I've read that is read by the bootloader to verify if your image is signed properly (i.e. by Motorola) and thus if it's not the right signature will fail to flash. Short of obtaining the correct, signed, image for your device (what is your device btw?), I'm not sure if you'll be able to bypass that. You may wish to have a look here, see if there are any images for your device (though I cannot say if they'll flash properly). https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
The strange thing is that flashing the stock Nougat ROM as you mentioned (and Ayan suggested) should have worked (since the NPJ25.93-14 build seems to be a global, universal build), the only thing I can think of was that something happened with the Marshmallow build on there (either a bad flash or an incorrect ROM, for example), but without asking the former owner, we just don't know.
For information, are you able to reboot into the bootloader, attach your device to your computer and in minimal ADB, execute 'fastboot getvar all' and post the info here, please? You may wish to remove your IMEI and serial number from the output.
Click to expand...
Click to collapse
I didn't know this firmware center, surely will be usefull in the future. Got the latest version updated there for my XT 1640 (answering your question). Flashed it and still the same, flashs ok but don't leave bootloop (I was afraid to find out it's a motherboard problem )
Here is the result of that command line:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(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: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB 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:
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: EC9AEB0100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-22-2016
(bootloader) sku: XT1640
(bootloader) battid: SNN5966B
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 21 23:34:21 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: 25.93-14/16:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.16.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_BRAZIL_DS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g478d03a (hudsoncm
(bootloader) kernel.version[1]: @ilclbld26) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Jan 6 05:12:56 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.03-0-ge433b40
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=119e5b2-dirty
(bootloader) hyp.git: git=119e5b2-dirty
(bootloader) keymaster.git: git=119e5b2-dirty
(bootloader) cmnlib.git: git=119e5b2-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (75)
(bootloader) ro.carrier: retbr
Thanks for the patience
justinwgeiger said:
Okay I understand, I will guide you through the process of unlocking your bootloader then.
Requirements:
A computer and a usb cord,
Moto G4/G4 Plus,
ADB/Fastboot Drivers: https://www.androidfilehost.com/?fid=745425885120698566,
Moto G4/G4 Plus Drivers: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481,
Once you have installed the Minimal ADB and Fastboot tool, launch the tool from the desktop icon named Minimal ADB and Fastboot. You should be brought to a command window.
Now power down your phone and hold the volume down and power button at the same time. you should see a screen pop up. then press the volume down button until you see bootloader and leave it there.
Now at the command window, type:
Code:
fastboot oem get_unlock_data
It should return with something like this:
Code:
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
After that, go to paste it all into notepad (A Windows application) and delete the bootloader text and all other spaces so it looks like this:
Code:
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
Go to Motorola’s bootloader unlock site and login with Google. Paste the entire code from notepad into the input box there. Then click can my device be unlocked and agree to the terms.
You will then be sent an email to unlock your bootloader.
Put the key that they send you into notepad and put it in the command line like shown below:
Code:
fastboot oem unlock "YOURKEY" (Replace YOURKEY with the key you received)
It will unlock your device. Congratulation you have successfully unlocked your device.
Credits:
devs-lab
If you have any questions or concerns just ask me and I will try my best to help you out. From this point forward you should be able to find your way throughout the forums to install a custom recovery. If not just ask me and I will guide you through that too. Glad to help, .
Click to expand...
Click to collapse
I already had unlocked my bootloader and then installed twrp later, without resatring the device. Now I re locked the bootloader and I am stuck with the MOTO "M" logo, please help
Hi guys finally i managed to unbrick the hard bricked phone ...
now my question is how should i choose the stock firmware for my device which is Indian variant - XT1686 32 GB
Bcoz as there are lots of different variants .... i have tried brazil
XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2017-02-05
this doesnt give IMEI numbers it will make them 0 so can u guys please tell me how should i choose the variants
and also please if some one have the recent boot loader.img, recovery.img and gpt.bin please provide me im stuck in boot loop ... just the sake until we get oreo update - XT1686 is my phone
i am not able to use my phone right now request you guys....
It's normal not to have your IMEI on stock if you've flashed Oreo ROMs before.
You can follow instructions in this thread if you want to get IMEI back.
Happy flashing!
Jrhotrod said:
It's normal not to have your IMEI on stock if you've flashed Oreo ROMs before.
You can follow instructions in this thread if you want to get IMEI back.
Happy flashing!
Click to expand...
Click to collapse
now actually my phone is stuck with Moto Z2 play boot loader so that i need everything to be Moto z2 play's firmware .... to wake up the dead phone it took me around 4 hours .... So my boot loader is not letting me install any other firmwares on my phone
please help me :crying:
This is what i got when i tried to flash Moto g5 plus Boot loader by downloading all the firmwares from official website:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.118s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.405s
praveen Glaxi said:
now actually my phone is stuck with Moto Z2 play boot loader so that i need everything to be Moto z2 play's firmware .... to wake up the dead phone it took me around 4 hours .... So my boot loader is not letting me install any other firmwares on my phone
please help me :crying:
This is what i got when i tried to flash Moto g5 plus Boot loader by downloading all the firmwares from official website:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.118s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.405s
Click to expand...
Click to collapse
What on Earth did you do to get the Z2 bootloader and how did you get it to even flash in the first place?
Jrhotrod said:
What on Earth did you do to get the Z2 bootloader and how did you get it to even flash in the first place?
Click to expand...
Click to collapse
Okay dude .... Let me explain very quickly ....
First off I bought this device like 8 months ago .... 1 week b4 I flashed customs ROM that is lineago os 15.1 which was recent for my device .... Everything was fine until yrstdy.... Yrstdy morning what I did was I planned to flash normal stock ROM to my phone .... Using some brasil version by watching YouTube ... Everything went well I was like thank god and then I inserted the sim but there was not network due to imei issue ....
This is where problem started...
Thinking after I do the OTA update security patch might go back and I might get the signal but then I did ota update and phone restarted ... It showed installing updates in half wat it suddenly switched I realised that I hard bricked my phone ...
Then searched the whole xda forums and found this guide https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457/page6
By Rakesh1b.....
I did the same I used potter blank flash and my phone woke up after trying it several hours....
Then when I tried to flash bootloader of moto g5 plus it showed error like I previously displayed ..... Well there was one more post for all of these 3 files, bootloader.IMG gpt.bin and recovery.IMG well I did flash all of them they seem to be worked ...
Then I tried to flash moto g5 plus twrp recovery which gave me error of failure...
Then I tried moto z2 play twrp ... God damn it got flashed and went into twrp recovery then as I studied as per @Rakesh1b ......
And now I'm stuck here ..... Not able to go front...
I get error like /cache not found when I try to flash custom os ...
What all I need now is moto g5 plus boot loader.IMG recovery.IMG gpt.bin
Of January security patch ... Mine last update was November security patch
I request some one to give those files or give a proper solution for this plzzzzzz
praveen Glaxi said:
I did the same I used potter blank flash and my phone woke up after trying it several hours....
Then when I tried to flash bootloader of moto g5 plus it showed error like I previously displayed ..... Well there was one more post for all of these 3 files, bootloader.IMG gpt.bin and recovery.IMG well I did flash all of them they seem to be worked ...
Then I tried to flash moto g5 plus twrp recovery which gave me error of failure...
Then I tried moto z2 play twrp ... God damn it got flashed and went into twrp recovery then as I studied as per @Rakesh1b ......
And now I'm stuck here ..... Not able to go front...
I get error like /cache not found when I try to flash custom os ...
What all I need now is moto g5 plus boot loader.IMG recovery.IMG gpt.bin
Of January security patch ... Mine last update was November security patch
I request some one to give those files or give a proper solution for this plzzzzzz
Click to expand...
Click to collapse
Thank you for the explanation, your situation seems to (mostly) make sense to me now.
You probably realize this in retrospect, but you should not have accepted an OTA on stock with no IMEI. But enough with that, what exactly do you mean by "my phone woke up"? I'd love to offer you a solution, but to find one, I'll need to know if "waking up" involved booting into Android, booting into the bootloader, or whatever.
u should unlock bootloader first.. the version of bootloader is lower than on ur phone, you should not OTA update, OTA did upgraded ur bootloader ver to latest..
---------- Post added at 06:32 AM ---------- Previous post was at 06:28 AM ----------
Try this firmware for ur model latest from february 2018
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
or
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
---------- Post added at 06:54 AM ---------- Previous post was at 06:32 AM ----------
[/COLOR]if u followed this solution and unbricked ur devices,try this Rom
its debloated and deodexed stock rom
: https://doc-00-6o-docs.googleuserco...2322377&hash=4s4e5hh6kltpi7nthp0actt4434mbjof
Orginal post :
https://forum.xda-developers.com/g5-plus/development/stock-debloated-deodexed-t3619972
THE FIRST THING U SHOULD TO UNLOCK BOOTLOADER before to try and CWM OR TWRP, custom rom..
Hey guys thanks for everyone's assistance here
i have successfully flashed Pixel experience ROM to my phone by using this procedure
1st. Blank flash your phone as per the above procedure..... (disable signature enforcement if u are using windows 10)
press and hold power button you could hear that mobile disconnects and connects once you hear that then press voldown and power with one hand and run blankflash.bat and then release those buttons before u hear them again
2nd. Flash all 3 provided files in MotoG5Plus_addison2Potter in the attachement and it will take you to the boot loader
Using these Commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Fastboot flash recovery recovery.img
fastboot reboot-bootloader
(Flash the files from provided Zip attachment)
3rd. download Moto z2 play or plus twrp recovery as i didnt have time to compress everything i cud nt provide that, then flash the custom recovery, then try to enter into recovery mod and it should enter..... if u have done 1st and 2nd step properly then u will enter into TWRP recvery mod
and here is the link for debolated ROM download version 2 which has november patch on it....
https://forum.xda-developers.com/g5-...dexed-t3619972
then once ur in twrp mount it to ur pc and copy the debolate ROM to ur phone and then flash it though TWRP ....
once it is done reboot ur phone into os and it should successfully boot into ROM...
once done u can flash any custom ROM into ur phone using TWRP
But 1 major issue is that i lost 4g or VoLTE:
Can u guys please help me with that.....
Hi
I'm having a little problem, I initially unlocked my bootloader and installed magisk on my G6 Plus when I bought it. I wanted to upgrade to 9.0 and so tried to flash the new firmware through fastboot. I ended up soft bricking the device and after hours of searching the internet for solutions and trying a lot of different fastboot commands, it suddenly started working again.
It's great that it's working again, however, I'm stuck on OPW27.113-45 and now I can't install magisk or take OTA.
I try going to bootloader and boot into twrp, I get the following command:
C:\mfastboot>fastboot boot twrp-3.2.3-0-evert.img
downloading 'boot.img'...
It basically hangs while sending or downloading anything within fastboot.
I've experimented with multiple versions of mfastboot, platform-tools etc. I have also downloaded multiple firmware versions without success.
I wonder if anyone has come across this problem in the past and has a solution.
I can boot into recovery and could potentially update via adb, however, to do so I need a special update file with signature verification that I can't find.
Ultimately, I want to boot into TWRP, flash Lineage Gapps and Magisk. But with the bootloader "broken" I get stuffed at the first step.
Just some extra information.
I have tried 4 different cables from both usb 2.0 slots and my 3.0 slot. I went and bought a USB c to c cable which also didn't work.
The phone is recognized when I type FASTBOOT DEVICES
Any help greatly appreciated
some more commands and the outcome
C:\mfastboot>mfastboot getvar current-slot
current-slot: _a
finished. total time: 0.001s
C:\mfastboot>mfastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-bf761ac-180403
(bootloader) product: evert
(bootloader) board: evert
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ufs: N/A
(bootloader) ram: 4GB SKHYNIX LP4x DIE=16Gb M5=06 M6=04 M7=00 M8=11
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: XXXXXXXXXXXX
It hangs here
my bootloader is unlocked, usb debugging is on.
Fixed
Cracked out my old laptop today to give it a go and see if the issue was my computer.
Turns out it was. I've now been able to update and all is good.
gilljohniez said:
Cracked out my old laptop today to give it a go and see if the issue was my computer.
Turns out it was. I've now been able to update and all is good.
Click to expand...
Click to collapse
I've had this same problem and solution, did you get to what is the problem of the PC? Maybe specs or something?
gilljohniez said:
Hi
I'm having a little problem, I initially unlocked my bootloader and installed magisk on my G6 Plus when I bought it. I wanted to upgrade to 9.0 and so tried to flash the new firmware through fastboot. I ended up soft bricking the device and after hours of searching the internet for solutions and trying a lot of different fastboot commands, it suddenly started working again.
It's great that it's working again, however, I'm stuck on OPW27.113-45 and now I can't install magisk or take OTA.
I try going to bootloader and boot into twrp, I get the following command:
C:\mfastboot>fastboot boot twrp-3.2.3-0-evert.img
downloading 'boot.img'...
It basically hangs while sending or downloading anything within fastboot.
I've experimented with multiple versions of mfastboot, platform-tools etc. I have also downloaded multiple firmware versions without success.
I wonder if anyone has come across this problem in the past and has a solution.
I can boot into recovery and could potentially update via adb, however, to do so I need a special update file with signature verification that I can't find.
Ultimately, I want to boot into TWRP, flash Lineage Gapps and Magisk. But with the bootloader "broken" I get stuffed at the first step.
Just some extra information.
I have tried 4 different cables from both usb 2.0 slots and my 3.0 slot. I went and bought a USB c to c cable which also didn't work.
The phone is recognized when I type FASTBOOT DEVICES
Any help greatly appreciated
Click to expand...
Click to collapse
I'm having the same issue, i don't get the fix, just change computer and it should work?
I solved the described issue without changing computer in the following way:
1. Disconnect phone from computer
2. In cmd type fastboot boot twrp.img (or whatever the filename is)
3. Press enter
4. Connect the phone back to the computer
It should then send the img and boot into twrp successfully. Hope this helped someone.