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.
Related
Hello guys, I wanted to share something I've discovered so that others will not repeat my same mistake. And yes I'm a noob
A little backstory
I have an Asian XT1033 Moto G, bootloader unlocked, rooted and using Faux's kernel. So, after reading some feedback about 5.1.1 for XT1033, I've been tempted to flash 5.1.1 over my 4.4.4.
The problem
I've downloaded the stock 5.0.2 Asia XT1033 firmware in img format, and proceeded to flash them via fastboot using Minimal ADB and Fastboot. (I tried to fastboot flash 5.0.2 stock firmware directly from 4.4.4 stock). Everything was fine, after flashing each part, Okay messages were shown. After rebooting, my Moto G booted and showed the usual "Warning Bootloader Unlocked" screen. EXCEPT, the "Warning Bootloader Unlocked" screen stayed for more than 10minutes......., I've spent the whole midnight trying to reflash back using 4.4.4 stock Asia firmwares (same stucked at warning screen), baffled, googling for similar problems encountered in hopes of a solution, but found nothing. The next day something came to my mind and I googled "the difference between fastboot and mfastboot" which led me to Mark_Venture's website, and after some reading, I first facepalmed myself hard and then screamed Eureka with my mind
What's causing this
To rephrase Mark_Venture, "fastboot is compatible with almost all Android devices, but is limited on how big the size of files it can actually flash, while Motorola have their own version called mfastboot which surpassed the file size limits of the usual fastboot", so basically when I tried to flash via fastboot, the command I've typed was "fastboot.exe flash partition gpt.bin" which is wrong and should be "mfastboot.exe flash partition gpt.bin", so basically I've used the usual fastboot.exe instead of Motorola's own mfastboot.exe. This probably explains why all the other files from the stock firmware are successfully flashed, EXCEPT the system.img_sparsechunk.0123 files due to their average sizes easily exceeding 256MB (my own take here, correct me if I'm wrong). This probably explains why rebooting after flashing via fastboot doesn't work because the system imgs are not flashed, and hence the phone get stucked at "Warning Bootloader Unlocked" screen because there is no ROM to boot to.
Alternatively, actually much more easier
You can also flash using fastboot a custom recovery, then boot into the custom recovery and either adb push or using USB OTG to install ROM zips. Personally I've used USB OTG with PhilZ Touch Recovery to install custom ROM and my phone finally boots.
TL;DR
Use mfastboot.exe instead of fastboot.exe when flashing via fastboot
Big credits to Mark_Venture and his website
Source: http://mark.cdmaforums.com/MotoX-mFastboot.htm
Great find. TIL for me too
Hi all,
I have a Moto G5 Plus that I brought on Amazon Prime day (11/07/17). and after trying to install TWRP I have ran into problems.
Heres what happened and where I'm left.
1) I unlocked the Bootlloader via moto website. No problems I now receive the BS message about the phone being unlocked.
2) Tried flashing twrp_3.1.1-0_potter.zip using "fastboot flash recovery twrp_3.1.1-0_potter.img"
Whenever I performed this command and rebooted in recovery I was never taken into the TWRP screen, but taken a screen showing a droid on it back with a message saying no command. I found how to bring up the command menu, but trying to flash the custom roms from the stock recovery always failed.
3) I used this article https://forum.xda-developers.com/g5-...-plus-t3605667 and found using this did allow me to boot into the TWRP screen. The only difference i noticed was that when i used the article mentioned above to get into TWRP the phone displayed the Moto boot ami before going into TWRP. It never did this when i used the Flash command manually.
4) Once in TWRP i flashed supersu and the RR .img, wiped cache etc..
On exiting TWRP I was asked whether I wanted TWRP installed as a system app, i selected yes to this question and now.....
5) BRICKED!!!
My moto will only boot into fastboot now and I get this message:-
Start up failed:
the bs about software repair assistant etc.
ap fastboot Flash Mode (secure)
Error: failed to load kernel!
Fastboot Reason: Fall-through from charge boot mode
usb....
6) I tried using this article https://forum.xda-developers.com/g5-plus/how-to/npn25-137-33-stock-firmware-t3577081
But I'm unsure of this version to use?
My question is can anyone help me to at least get my phone working again. Thanks will be paid.
JammieB said:
I have a Moto G5 Plus that I brought on Amazon Prime day (11/07/17). and after trying to install TWRP I have ran into problems.
Click to expand...
Click to collapse
Which Amazon Moto G5 Plus did you buy on Prime Day? The cheaper subsidized Amazon Prime version with ads or the more expensive non subsidized version without ads?
Apparently you cannot unlock the bootloader on the subsidized ad based Amazon Prime version. This is well discussed. One such discussion from the Lenovo/Moto support forum:
https://forums.lenovo.com/t5/Moto-G5-Moto-G5-Plus/Is-there-anyway-to-unlock-my-Moto-G5-Plus-from-Amazon/td-p/3638019
If one does a forum search on this site they'll find past discussions indicating the bootloader on Amazon Prime subsided Moto G5 Plus phones cannot be unlocked.
Try the Toolkit.
Once in it flash the TWRP and boot_image and try rebooting. If that doesn't work flash the Stock ROM and then flash the TWRP and boot_image. Once you get those flashed you should be able to flash the latest TWRP using fastboot.
Please let me know if that fixed it.
Thanks,
CP
cyber_prometheus said:
Try the Toolkit.
Once in it flash the TWRP and boot_image and try rebooting. If that doesn't work flash the Stock ROM and then flash the TWRP and boot_image. Once you get those flashed you should be able to flash the latest TWRP using fastboot.
Please let me know if that fixed it.
Thanks,
CP
Click to expand...
Click to collapse
Thanks for the suggestion, however I have tried this toolkit already and when connecting the USB cable, the toolkit only ever says connecting to device, but never manages to actually connect. As such, no command from the toolkit can be run, as when tried I get a "no device" message.
Also when I try to use the toolkit to install Windows 64bit driver, the install stops telling me I have a newer driver installed already.
Do you think I should uninstalled the newer device driver or should the toolkit still connect using the newer driver?
bennor3814 said:
Which Amazon Moto G5 Plus did you buy on Prime Day? The cheaper subsidized Amazon Prime version with ads or the more expensive non subsidized version without ads?
Apparently you cannot unlock the bootloader on the subsidized ad based Amazon Prime version. This is well discussed. One such discussion from the Lenovo/Moto support forum:
https://forums.lenovo.com/t5/Moto-G5-Moto-G5-Plus/Is-there-anyway-to-unlock-my-Moto-G5-Plus-from-Amazon/td-p/3638019
If one does a forum search on this site they'll find past discussions indicating the bootloader on Amazon Prime subsided Moto G5 Plus phones cannot be unlocked.
Click to expand...
Click to collapse
Im 100% confident that my moto has had its bootloader unlocked and that I was not sold a Moto G5 Plus with amazon ads.....
Thanks for your suggestion though.
FIXED back to stock rom. Here's what I did:-
1) Downloaded the stock rom from https://forum.xda-developers.com/g5/how-to/npp25-137-33-stock-firmware-moto-g5-t3577084
Used the mega link it took 5mins (1.4 mbps) to download.
2) Then run these commands:- (thanks to https://forum.xda-developers.com/member.php?u=5033408)
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize (gave error about bootloader)
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot oem lock
fastboot reboot
It still see the annoying unlocked bootloader screen, but my moto boots into the stock rom.
I'm not giving up on getting a custom rom onto this device, but thanks to anyone who's helped me to get back to square one.
JammieB said:
Thanks for the suggestion, however I have tried this toolkit already and when connecting the USB cable, the toolkit only ever says connecting to device, but never manages to actually connect. As such, no command from the toolkit can be run, as when tried I get a "no device" message.
Also when I try to use the toolkit to install Windows 64bit driver, the install stops telling me I have a newer driver installed already.
Do you think I should uninstalled the newer device driver or should the toolkit still connect using the newer driver?
Click to expand...
Click to collapse
I didn't install the drivers with the toolkit. Was your phone connected to it in fastboot mode? That's what I had to do to get it to detect mine.
If you can't get the toolkit to work you can still use fastboot to flash the included version of TWRP and the modified boot_image. They're located in TOOLKIT_DIR\resources\app.asar.unpacked\files.
CP
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.
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
Hi I flashed the ATHENE_RETAIL_8.1.0_OPJ28.111-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in my Moto G4 Amazon variant phone.
Now the phone is stocked at logo.
Has anyone root this model with bootloader locked ?
meolivares06 said:
Hi I flashed the ATHENE_RETAIL_8.1.0_OPJ28.111-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in my Moto G4 Amazon variant phone.
Now the phone is stocked at logo.
Has anyone root this model with bootloader locked ?
Click to expand...
Click to collapse
You cannot root with a locked bootloader.
i have the same issue, wondering if any solution out yet ?
henser said:
i have the same issue, wondering if any solution out yet ?
Click to expand...
Click to collapse
Could try LMSA Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
sd_shadow said:
Could try LMSA Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
i've just tried, tried rescue but i got an error when trying to install flashboot flash error. Says Flash failed, try again. stuck at 68 Percent
Currently looking in to flashing this.
Did you all try to flash the rom as a single file in twrp or similar or did you try to flash individual files to individual partitions?
With fastboot like:
DO NOT USE FOR THIS PHONE, SHOWN AS EXAMPLE!
sudo fastboot flash bluetooth BTFM.bin
sudo fastboot flash dsp dspso.bin
sudo fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
I used this kind of code for flashing new software to my G7
(Sudo is for using these commands in linux)
Restore
Just follow those steps, doesn't matter if you have the bootloader locked.
Important:
Next time, unlock the bootloader and install a custom recovery, twrp is the most common. After that flash the 8.1, it will reboot several times like if it has a problem but thats just the android config. Don't panic if you see it reach the homescreen and reboot, 3 or 4 times. It will do that untill you see the finishing progress bar prompt when it boots to homescreen
will give a try with this to see if it works.
edit tried, with 7.0 and the second command says preflash validation failed, with 8.1.0 the phone says okay all the commands but when i reboot the phone gets stuck on the blue m logo