What will happen if I attempt to flash my OEM locked/locked bootloader Amazon Variant Moto G5 Plus with a stock rom using RSD Lite? Will the flash fail or will I have a new permanent paperweight?
Not using adb fastboot but using RSD Lite.
Thank for your assistance.
It won't work... sorry. Plus there is no stock image I am aware of for the Amazon devices.
You can only flash a stock image to a locked device that is specifically intended for that device and the same or newer version. Down grading or switching to a different ROM is not possible.
Plus, RSD Lite hasn't been supported for years... It is essentially just "fastboot" with some extra scripting abilities, literally anything you can do with RSD Lite you can do with a current version of fastboot, it just uses Motorola's "custom" build of fastboot called mfastboot to do it's stuff.
G5+ Stock Firmware Images
I've personally flashed the latest version to my Amazon G5+.
It also let me downgrade the bootloader to the previous 137-35-5 version, but not below that unfortunately :crying:
I was trying to get root which was last available on the 137-35 bootloader. I may still try to blankflash & then flash 137-35.
I used RSD Lite to flash the entire firmware, it works. As acejavelin mentioned, it's just running fastboot commands. The nice part about it is that it reads the flashfile.xml & does all the steps in that file for you automatically, no scripting required.
acejavelin said:
It won't work... sorry. Plus there is no stock image I am aware of for the Amazon devices.
You can only flash a stock image to a locked device that is specifically intended for that device and the same or newer version. Down grading or switching to a different ROM is not possible.
Plus, RSD Lite hasn't been supported for years... It is essentially just "fastboot" with some extra scripting abilities, literally anything you can do with RSD Lite you can do with a current version of fastboot, it just uses Motorola's "custom" build of fastboot called mfastboot to do it's stuff.
Click to expand...
Click to collapse
Is it possible or not to flash a stock rom on a original locked device?
So is it possible to flash a stock rom on Amazon Prime Moto G5 Plus with original locked bootloader? My device is not eligible for the Motorola's unlocking bootloader program and I couldn't get it unlocked. I just got the oreo update a week ago and it just not charging properly. I would like to try a downgrade or even flash another oreo version to see if it corrects the bug.
Related
So recently I bricked my deviced and I had to flash the original image that the phone came with - I have moto G4 XT1625.
My phone is unlocked although I have unsuccessfully tried to relock it.
Problem: Once I flashed the original version of android which was Marshmallow 6.0 I am unable to update to 7.0 as I had before I bricked my device.
How can I update to Nougat 7.0 and relock it. I cannot find any image for Nougat 7.0 anywhere as that is not the original for the Moto G4. Any ideas?
Edit: I tried relocking it the 2 ways -
1. fastboot oem lock
2. fastboot oem lock begin and then reflashing all the firmware and then locking
Nougat stock image
https://androidfilehost.com/?fid=673368273298955218
Sure?
zonggestsu said:
Nougat stock image
https://androidfilehost.com/?fid=673368273298955218
Click to expand...
Click to collapse
Do you know if this would be an official ROM or is this a custom copy where I wont get updates?
*XAOS* said:
Do you know if this would be an official ROM or is this a custom copy where I wont get updates?
Click to expand...
Click to collapse
Its the the official image. You should be able to flash it then remove your bootloader if you feel like it. Word of warning, it looks like, at least from my experience, that the g4 bootloader doesn't properly check the images properly unless you invoke
Code:
fastboot oem lock
twice. Then you can start flashing over the images such as oem.img and system.img_sparsechunck.0
The bootloader.img and gpt.bin need to be flashed before this though.
Thank you!!
I have Lineage OS 14.1 on my phone and need to use Duo Mobile for 2 factor authentication. In spite of the fact that I have "unrooted" the system is still detecting that I a have tampered with my device. I will assume it's because the bootloader is unlocked.
I really, really don't want to wipe the phone and reconfigure all my apps (yes, it's easier than it used to be). Getting into fastboot and doing the fast relock commands is pretty clear to me, but how to get my device back to exactly where it is, but just with the bootloader locked?
Not possible.
Sent from my ZTE A2017U using Tapatalk
kendoori said:
I have Lineage OS 14.1 on my phone and need to use Duo Mobile for 2 factor authentication. In spite of the fact that I have "unrooted" the system is still detecting that I a have tampered with my device. I will assume it's because the bootloader is unlocked.
I really, really don't want to wipe the phone and reconfigure all my apps (yes, it's easier than it used to be). Getting into fastboot and doing the fast relock commands is pretty clear to me, but how to get my device back to exactly where it is, but just with the bootloader locked?
Click to expand...
Click to collapse
You can't relock unless you are fully stock (actually you can, but you'll have a brick for life)
Choose an username... said:
You can't relock unless you are fully stock (actually you can, but you'll have a brick for life)
Click to expand...
Click to collapse
I have the a2017 model. Can I flash G or U stock firmware keeping the Chinese firmware modem and relock the bootloader. Do you know whether this is possible or would work without bricking.
FuzzyDunlop9 said:
I have the a2017 model. Can I flash G or U stock firmware keeping the Chinese firmware modem and relock the bootloader. Do you know whether this is possible or would work without bricking.
Click to expand...
Click to collapse
To relock the bootloader you will need fastboot. None of the newer stock firmwares have fastboot asides from Chinese B19. You will need to EDL Flash B19 and use the Axon 7 Tool to relock the bootloader. After that, you can flash any Axon 7 firmware you'd like. Any A7 firmware works on any A7 model.
Make sure to replace the NONHLOS.bin in the files of the EDL package with the NONHLOS.bin from the Chinese firmware. This file is the modem, and so if you live in China, you will need to replace the US/EU modem file inside the package with the Chinese one.
It won't brick your phone, but it's not possible to relock the bootloader without wiping. I'd suggest a backup app such as Titanium Backup or something else (not too sure about non-root backup apps).
runninghamster said:
To relock the bootloader you will need fastboot. None of the newer stock firmwares have fastboot asides from Chinese B19. You will need to EDL Flash B19 and use the Axon 7 Tool to relock the bootloader. After that, you can flash any Axon 7 firmware you'd like. Any A7 firmware works on any A7 model.
Make sure to replace the NONHLOS.bin in the files of the EDL package with the NONHLOS.bin from the Chinese firmware. This file is the modem, and so if you live in China, you will need to replace the US/EU modem file inside the package with the Chinese one.
It won't brick your phone, but it's not possible to relock the bootloader without wiping. I'd suggest a backup app such as Titanium Backup or something else (not too sure about non-root backup apps).
Click to expand...
Click to collapse
Thanks for replying. So I flashed the A2017_B15_FULL_EDL Android: 6.0.1 onto my a2017 axon 7. I replaced the NONHLOS.bin (modem) in the edl file with the Chinese modem which I took from A2017_B15_FULL_EDL Android: 6.0.1. I'm able to get network signal and works as expected.
I can't seem to lock the bootloader. Fastboot works on this firmware but the fastboot oem lock command does nothing, I keep getting failed.
Are you suggesting I flash stock firmware, one that has fastboot commands working, designed for a2017, lock the bootloader and then using a tool like djkuz Axon 7 EDL Tool flash a2017g firmware.
The reason why I need a2017g firmware is I'm tryna sell my axon at CEX and they won't accept it cos it has Chinese software. If it has European firmware with locked bootloader it'll pass their software check.
FuzzyDunlop9 said:
Thanks for replying. So I flashed the A2017_B15_FULL_EDL Android: 6.0.1 onto my a2017 axon 7. I replaced the NONHLOS.bin (modem) in the edl file with the Chinese modem which I took from A2017_B15_FULL_EDL Android: 6.0.1. I'm able to get network signal and works as expected.
I can't seem to lock the bootloader. Fastboot works on this firmware but the fastboot oem lock command does nothing, I keep getting failed.
Are you suggesting I flash stock firmware, one that has fastboot commands working, designed for a2017, lock the bootloader and then using a tool like djkuz Axon 7 EDL Tool flash a2017g firmware.
The reason why I need a2017g firmware is I'm tryna sell my axon at CEX and they won't accept it cos it has Chinese software. If it has European firmware with locked bootloader it'll pass their software check.
Click to expand...
Click to collapse
Yeah, that's basically it.
runninghamster said:
Yeah, that's basically it.
Click to expand...
Click to collapse
Ooh so it's possible to edl flash even with a locked bootloader?
FuzzyDunlop9 said:
Ooh so it's possible to edl flash even with a locked bootloader?
Click to expand...
Click to collapse
Yep.
A month ago my Moto g5 plus died trying to fix a Moto Z Play from a friend. I had mistakenly connected my cell phone thinking it was my friend's and I ended up flashing mine by mistake. Since then my Potter died! I have tried everything to be able to relive it but I can not find the way. I have downloaded all the official Stock Roms and none has been able to raise my phone again.
The result after the flash was that the original bootlader that I had changed completely! Now I have the data of a Moto Z Play on my Moto G5 Plus.
AP Fastboot Flash Mode (Secure)
BL: C1.07 (sha-9d7f987, 2017-04-01 13:44:07).
Is there any way to relive it again? The Model is Moto G5 Plus Potter XT1680 32GB P3B. Every day I try to do something new but I can not find the way anymore ....
diegosilvax8 said:
A month ago my Moto g5 plus died trying to fix a Moto Z Play from a friend. I had mistakenly connected my cell phone thinking it was my friend's and I ended up flashing mine by mistake. Since then my Potter died! I have tried everything to be able to relive it but I can not find the way. I have downloaded all the official Stock Roms and none has been able to raise my phone again.
The result after the flash was that the original bootlader that I had changed completely! Now I have the data of a Moto Z Play on my Moto G5 Plus.
AP Fastboot Flash Mode (Secure)
BL: C1.07 (sha-9d7f987, 2017-04-01 13:44:07).
Is there any way to relive it again? The Model is Moto G5 Plus Potter XT1680 32GB P3B. Every day I try to do something new but I can not find the way anymore ....
Click to expand...
Click to collapse
I think you need to use the blankflash from albus. If you flashed Z Play's firmware then you changed the bootloader of your G5 Plus to Z Play's. Have you tried the albus blankflash? Please report after trying.
psychopac said:
I think you need to use the blankflash from albus. If you flashed Z Play's firmware then you changed the bootloader of your G5 Plus to Z Play's. Have you tried the albus blankflash? Please report after trying.
Click to expand...
Click to collapse
I can not download the albus blankflash from the page because it does not exist. I got a BlankFlash from Moto Z Play from another side but when I run the .bat it remains on waiting device.
In device manager I am listed as "Fastboot Potter S", after installing the driver, it is in ADB Interface. But from there I can not execute Blankflash.
Another solution?
This is the flash file that no longer appears on the page but I can not find it on the other hand the same link
cloud vache-android com/Moto/albus/blankflash/
Try downloading blankflash from here...
https://androidfilehost.com/?a=show&w=files&flid=213037
Is your ADB and Fastboot working correctly on PC?
Download the flash blank but it still does not work. The ADB and Fastboot works correctly but it does not let me run the blank flash. Any other idea?
If I try to load a rom from Fastboot, it works. But if I try to do blank flash with the qbot.exe command from the .bat it does not work.
It is always on <waiting device>
@acejavelin, can you assist please?
psychopac said:
@acejavelin, can you assist please?
Click to expand...
Click to collapse
Not really sure why I'm tagged here... This isn't my area of expertise at all.
Sorry, but I have no incite here.
@NZedPred, @echo92
Hmm, is your bootloader unlocked? In the G5 plus unbrick guide, those users who managed to recover their device after using the albus bootloader and the addison2potter GPT/bootloader were only able to use stock TWRP flashables (though you didn't hard brick, flashing the Z play bootloader is a similar result). I'm not sure if flashing a stock ROM via fastboot is an option, due to the different bootloader. There are reports that the stock ROM may be flashable if you omit the GPT and bootloader, however you'd need an unlocked bootloader and also you'd have to forget about using OTA updates at all. Else, you'd likely actually hard brick this time with an OTA update.
Thus, if you can, stock TWRP flashables or a custom ROM are likely your best options.
Just checking if you've tried these:
- Fastboot to boot a TWRP image (i.e. fastboot boot twrp.img, where twrp.img is a TWRP file)
- Fastboot to flash just a bootloader from the right device
This isn't really my area of expertise either. I usually fix things after having broken them myself, but I don't want to try this
I had hardbricked my devices while installing an OTA update and the device was Hardbricked .
I blank flashed the device and it booted and bootloader.
Now the problem starts here.
I flashed the OEM_Lock.bat as I wanted to relock the bootloader. I'm not sure what went wrong but the flash didn't complete and stuck in middle.
The problem remains here is it shows
Fastboot Reason: Failed to initialize partition table
I am unable to flash anything now. Recovery.img fails, bootloader.img fails, twrp flashing fails.
Nothing flashes as Bootloader is locked.
I went to Motorola Service Centre. They also couldn't do anything and simply said that their software doesnt read the phone.
Is there anyone whoe can really help me out with anything left to do?
Any method to force flash recovery, even twrp?
Phone is detected as Fastboot athene_16mp S in computer. It doesnt detect as "Qualcomm HS-USB QDLoader 9008".
What firmware are you attempting to flash?
Your device looks like it's still on the blank flash provided bootloader, which means you have to flash at least the GPT and bootloader. The lack of a serial number and the generic identifier implies you have not been able to flash an actual GPT and bootloader. Also, OEM_locked is normal until you get an actual bootloader flashed over the blank flash bootloader, which usually means trying to flash a GPT and bootloader at least as new as the latest version you had on your device (regardless of downgrades).
I'd suggest downloading the latest Nougat stock ROM we have from here. Do not use any of the scripts at this time.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Edit - also, this post probably is better suited to the Q and A section...
echo92 said:
What firmware are you attempting to flash?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Click to expand...
Click to collapse
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
mysteryno46 said:
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
Click to expand...
Click to collapse
Eh, you live and learn. Besides, you've now got your device running now!
Honestly, it's up to you. Having a locked or unlocked bootloader will not affect your ability to receive OTA updates - you should still receive updates so long as your firmware matches your software channel (and since your device was XT1643, the NPJS25.93-14-18 April 2018 security update should be the correct firmware). At this moment in time, you'll have to use the NPJS25.93-14-18 firmware to re-lock your bootloader - we don't have the stock Oreo firmware at this time. Thus, if you update to stock Oreo, you will not be able to re-lock your bootloader until you can get a leak of the Oreo firmware.
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Back to Locked Bootloader, complete stock.
echo92 said:
Eh, you live and learn. Besides, you've now got your device running now!
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Click to expand...
Click to collapse
I am back to Locked Bootloader as feel the same as you said that anyone buying might get scared by looking the warning sign. Thanks for helping out. :highfive:
Oreo Update via OTA has already started rolling out as per the news I've been reading. I just wanted to see the oreo 8.1 before I sell the phone.
Anyways I got a new device now, Realme C1, 3|32GB as my smartphone usage has declined a lot recently and might remain similar. This device will suffice my requirements.
Thanks for the help and support. :victory:
Since I bought the Moto G5 I always used platform tools (ADB + Fastboot) version r27.
Two weeks ago I updated to the latest version (r28) and had no problems using ADB, but when I first used Fastboot I was unfortunate to get the following error before every flash operation:
Code:
(bootloader)is-logical:not found
And the flash process apparently went on normally, but it did not, it just bricked my phone.
I googled for the error and found out several Motorola users were having the same issue with other devices too (Moto X2, Moto G5 Plus and I found one other Cedric user with the same problem).
After trying several firmwares with no success I realized the problem was with Fastboot, so I tried both Fastboot r26 and r27 and both flashed my phone normally, but again on r28 I had the issue above, so I warn you all to stay away from Fastboot r28.
Of course it only soft bricked my phone, but if I were relocking my bootloader or flashing a newer firmware using Fastboot r28, I'd hard brick my phone for sure, since that's what to be expected from a failed attempt to flash gpt.bin or bootloader.img
I've been using fastboot v28 with no issues. I used it flash my G5 from Nougat to Oreo a month or so ago, used it to unlock my bootloader, flash TWRP, and flash a custom bootlogo. I do get those "(bootloader)is-logical:not found" messages, but I think it has to do with fastboot looking for the partition structure used on native-Oreo devices for Treble, but I'm not sure. Hasn't been an issue for me though. (FWIW, I'm on Linux)
xtermmin said:
I've been using fastboot v28 with no issues. I used it flash my G5 from Nougat to Oreo a month or so ago, used it to unlock my bootloader, flash TWRP, and flash a custom bootlogo. I do get those "(bootloader)is-logical:not found" messages, but I think it has to do with fastboot looking for the partition structure used on native-Oreo devices for Treble, but I'm not sure. Hasn't been an issue for me though. (FWIW, I'm on Linux)
Click to expand...
Click to collapse
interesting. I haven't tried this on linux though.
xtermmin said:
I've been using fastboot v28 with no issues. I used it flash my G5 from Nougat to Oreo a month or so ago, used it to unlock my bootloader, flash TWRP, and flash a custom bootlogo. I do get those "(bootloader)is-logical:not found" messages, but I think it has to do with fastboot looking for the partition structure used on native-Oreo devices for Treble, but I'm not sure. Hasn't been an issue for me though. (FWIW, I'm on Linux)
Click to expand...
Click to collapse
Same for me here using Linux. Still able to flash without issues at all.