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
Related
Can anyone please share me the latest nougat boot logo, the one in blue colour, so as to remove the bootloader unlocked warning message...
Take a look in this tread.
https://forum.xda-developers.com/moto-g4-plus/themes/customized-logo-t3451349
Thanks dear, got the nougat logo...
does anyone actually have a working method to remove the boot loader warning as none of the steps listed in the link actually do anything. the image was flash without error but the warning remains
brostar2017 said:
does anyone actually have a working method to remove the boot loader warning as none of the steps listed in the link actually do anything. the image was flash without error but the warning remains
Click to expand...
Click to collapse
How do you mean by 'the warning remains' though, can you still see the 'device has been unlocked' message even after flashing the logo.bin via fastboot (using the adb terminal)? Can you show us which logo.bin you're trying to flash and what steps you're using to flash the file?
If you've got TWRP, you may wish to try some of the TWRP flashable logo.bin
https://forum.xda-developers.com/moto-g4-plus/themes/guide-t3588090
https://forum.xda-developers.com/moto-g4-plus/themes/bootlogo-dev-edition-black-n-removed-t3609835
https://forum.xda-developers.com/moto-g4-plus/themes/splash-screen-stark-sigil-game-thrones-t3562019
The only other way I know of removing the bootloader warning is to re-lock your bootloader. The custom logo.bin, though they don't shorten the 5-10 delay on booting, at least hide the bootloader warning (and the N/A bit too).
The v1 Android logo wouldn't even flash, the V2 logo says it's 100% completed but the full warning remains and no logo of powered by Android. I am using the minimum abd package which is working fine as I did everything else without issues via fast boot command, I'm using the commands listed on xda for it I've tried both fastboot flash logo logo.bin and mfastboot flash logo logo.bin Sudo fastboot flash logo logo.bin and flash logo logo.bin all came back as 100% complete without any errors being displayed then I did fastboot reboot.
---------- Post added at 01:29 PM ---------- Previous post was at 01:29 PM ----------
---------- Post added at 01:30 PM ---------- Previous post was at 01:30 PM ----------
Could it be because moto just pushed a new software update to this model ending with .67 the latest nogurt build, sorry for any typos.
Could it be because moto just pushed a new software update to this model ending with .67 the latest nogurt build, sorry for any typos.
brostar2017 said:
Could it be because moto just pushed a new software update to this model ending with .67 the latest nogurt build, sorry for any typos.
Click to expand...
Click to collapse
If you're running an update ending in .67, are you using a G5 Plus with NPN25.137.67? If so, you may wish to look here for logo.bin images https://forum.xda-developers.com/g5-plus/how-to/logo-fix-g5-logo-bin-t3610456
No using a moto G4 plus XT1642 Australia variety.
brostar2017 said:
No using a moto G4 plus XT1642 Australia variety.
Click to expand...
Click to collapse
I'm confused now as you've mentioned you've had an update pushed to your device with .67? For Moto G4 Plus, I recall the latest update is NPJS25.93-14.4 (March 2017), unless you're on a soak test.
So, just to clarify, you've:
1) Downloaded the zip of the logo.bin
2)Extracted the logo.bin from the zip file
3)Copied the logo.bin to your adb directory (ensuring that there aren't any other logo.bin files in the directory or the original/your new logo.bin has been renamed, if for example you had your stock ROM there), or made a note of the path directory to your desired logo.bin
4)Rebooted your device to the bootloader and plugged your device into your computer
5)In adb, typed 'fastboot flash logo logo.bin' (ensuring that the 'logo.bin' is pointing to the correct logo.bin)
6)Rebooted
Yes I have e followed all those steps and nothing changed. Don't even know what a soak test is or how to get it.
brostar2017 said:
Yes I have e followed all those steps and nothing changed. Don't even know what a soak test is or how to get it.
Click to expand...
Click to collapse
I was getting confused as you quoted an update version that doesn't appear to exist currently on Moto G4 athene devices (to the best of my knowledge). Out of interest, can you post a screenshot of your device info under Settings>About Phone? I'd just like to verify what build you have. You'll either get a soak test from the Motorola Feedback Network if you signed up to be a tester, usually. It'll appear as a software update (and accompanied with a questionnaire, if I recall).
It's odd these steps aren't working, I've got a XT1642 (on the retgb retail software channel) and have been able to flash these logo.bin images. Perhaps someone else can chime in with solutions.
That information hmwas removed when lineage is was installed onto the handset I own the XT1643 which is an Australian model. Definitely not a moto tester that would break my contract with Jide technologies. Both my moto G4 plus device got the update so did most the people I know here with that model. Updated about a week ago. Ending in .67 my moto G5 plus which I just got has no software updates and is ending in .14
brostar2017 said:
That information hmwas removed when lineage is was installed onto the handset I own the XT1643 which is an Australian model. Definitely not a moto tester that would break my contract with Jide technologies. Both my moto G4 plus device got the update so did most the people I know here with that model. Updated about a week ago. Ending in .67 my moto G5 plus which I just got has no software updates and is ending in .14
Click to expand...
Click to collapse
I think you've got your devices mixed up - as far as I know:
Moto G4 Plus - updated to NPJ25.93-14.4 (March 1 2017 security update) - which would be your XT1642. XT1643 is the Indian model. Thus far, does not have an update ending in .67.
Moto G5 Plus - updated to NPN25.137-67 (March 1 2017 security update) (you've even posted getting this update on your device in the G5 Plus OTA thread! https://forum.xda-developers.com/showpost.php?p=72784029&postcount=194) As far as I know, Moto G5 Plus devices have only received .15, .33, .35 and .67 updates.
LineageOS will still show if you're running a Moto G4 Plus or Moto G5 Plus under the Device info. Also, the build will tell you whether it's for Moto G4 ( it'll list athene as the codename) or Moto G5 Plus (listing potter as the codename).
chottu109 said:
Thanks dear, got the nougat logo...
Click to expand...
Click to collapse
Brother could u please give me the stock nougat logo.bin
So, here is my problem that somehow my bootloader or any one of the partition is corrupted which somehow messup with the moto g4 plus HW partition file and corrupt it. I try to push a edited file but it tucks the recovery. The only hope light is from the Blankflash as it actually flashes everything from scratch.
The main thing is that my device is working just it shows y Moto g4 plus a Moto g4 with no sim working and no fingerprint working. I can't connect my device as a “Qualcomm HS-USB QDLoader 9008” as my device bootup in fastboot mode always. So, any workaround to Blankflash a working device anyone please.
its easy, first download very old fastboot stock rom, for instance Android marshmallow, which is very old;
flash it using fastboot and take OTA, it will miss-match the GPT and boot-loader Because GPT partition is not downgradable and it will brick your phone,
then you can flash the working blankflash
I would do the same. Can you explain me exactly how i brick my Phone to use the blankflash?
thx
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.
Hey guys please help me,
Last time i installed stock on my moto g5 plus after that I can't able to unlock bootloader and not able to install recovery on my device.
And when i tried to do that it shows
Plot suffix not found
Solve my problem i want a custom rom on my device.
Manisshyaddvv said:
Hey guys please help me,
Last time i installed stock on my moto g5 plus after that I can't able to unlock bootloader and not able to install recovery on my device.
And when i tried to do that it shows
Plot suffix not found
Solve my problem i want a custom rom on my device.
Click to expand...
Click to collapse
Slot Suffix not found is normal, that's because TWRP is checking for another slot like in Pixel or other A/B devices.
About your other problem you have to provide more information, which stock ROM version did you flash and from which version did you come?
Maybe you downgraded your bootloader?
Have you been on any 64bit custom ROM? If yes which one?
Sent from my Moto G5 Plus using XDA Labs
Manisshyaddvv said:
Hey guys please help me,
Last time i installed stock on my moto g5 plus after that I can't able to unlock bootloader and not able to install recovery on my device.
And when i tried to do that it shows
Plot suffix not found
Solve my problem i want a custom rom on my device.
Click to expand...
Click to collapse
In addition to wolfcity's useful post, have you unlocked this device's bootloader in the past? If so, then what happens if you try to unlock with your unlock key as given to you by Motorola?
If your key no longer works, and OEM unlocking (under Settings>Developer Options) is turned on, then you may have to request help from the official Motorola forums: https://forums.lenovo.com/t5/MOTOROLA-Android-Developer/Bootloader-Unlock-Problems/td-p/3222809
If you have not unlocked this device bootloader, then have you obtained the OEM unlock code and submitted that code to Motorola as per this tool? https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Please help me
Wolfcity said:
Slot Suffix not found is normal, that's because TWRP is checking for another slot like in Pixel or other A/B devices.
About your other problem you have to provide more information, which stock ROM version did you flash and from which version did you come?
Maybe you downgraded your bootloader?
Have you been on any 64bit custom ROM? If yes which one?
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Help me,
POTTER_NPN25.137-35 this was the stock rom version i used.
And today camera is stopped working,
What should i do now
I've to flash stock again help me
Manisshyaddvv said:
Help me,
POTTER_NPN25.137-35 this was the stock rom version i used.
And today camera is stopped working,
What should i do now
I've to flash stock again help me
Click to expand...
Click to collapse
Looks like you flashed a ROM meant for US devices onto your Indian device... Also, NPN25.137-35 is a really old firmware (March 2017) and Moto devices sometimes do not work well if you've flashed an older firmware to your device.
I'd recommend flashing the NPNS25.137-92-10 (April 2018 security patch) or NPNS25.137-92-14 (June 2018 security patch) firmware onto your device. I'd also recommend flashing with wiping your userdata, as I don't know what's causing this; with a data wipe, you will want to back up your data if possible. Copy your essential files to a computer/cloud storage and hopefully have your contacts backed up. You could use MyPhoneExplorer to back up your contacts, text messages and call log.
Manisshyaddvv said:
Help me,
POTTER_NPN25.137-35 this was the stock rom version i used.
And today camera is stopped working,
What should i do now
I've to flash stock again help me
Click to expand...
Click to collapse
Not much to add to echo92's post, a full wipe and flashing one of the mentioned firmwares is exactly what you should do.
For the case that you have downgraded your bootloader in the past I would recommend to not take future OTA as this could hardbrick your device.
Sent from my Moto G5 Plus using XDA Labs
How could i unlock bootloader
Tell me the full process of unlocking bootloader and flashing stock,
And please give me the link for firmware,
And what if again it shows slot suffix not found???
How to unlock bootloader in moto g5 plus
How could i unlock bootloader when lenovo is not sending me the key and also "Slot suffix is not found" is a big problem for me,
And also send me the link of firmware which i should use,
Please help me.
I'm waiting for your response
My device is totally in bad condition camera is not working and file explorer is not opening either,
So please help me
Which firmware and full process how to?
Manisshyaddvv said:
How could i unlock bootloader when lenovo is not sending me the key and also "Slot suffix is not found" is a big problem for me,
And also send me the link of firmware which i should use,
Please help me.
I'm waiting for your response
My device is totally in bad condition camera is not working and file explorer is not opening either,
So please help me
Which firmware and full process how to?
Click to expand...
Click to collapse
Here you'll find the firmware
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use NPNS25.137-92-10 (April 2018 security patch) or NPNS25.137-92-14 (June 2018 security patch.
As I told you before the "slot suffix not found" message is normal and no problem.
It just tells you that your device has only one update slot and not two like Pixel or some Xiaomi devices.
And about the unlock key: Have you tried to get one like echo92 posted? Have you tried to use the
fastboot oem unlock command?
Here you find a complete guide for rooting your device, the first part is only about flashing stock firmware. Just follow the first part of this guide but use the above firmware.
https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659/post74673573
Sent from my Moto G5 Plus using XDA Labs
As Wolfcity has mentioned above, the slot suffix is normal for our devices as we don't have A/B partitioning. To illustrate, if I boot my G4 Plus to fastboot and then issue the command 'fastboot reboot' from ADB, using minimal ADB 1.4.3 and the Motorola USB drivers, on Windows 10 64 bit, this is the output:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: 0.176s
Also, as I asked you in your PM, have you actually posted to that Motorola thread? Once AlphaDog or one of the moderators sees your post in that thread, they should start the process for getting you an unlock key, or at least advise you on what to do next. I do not know if posting outside of that Motorola thread will get you results.
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.