Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you
adavies said:
Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you
Click to expand...
Click to collapse
First of all, "adb devices" doesn't work on the bootloader. The adb app only works in recovery or while booted into the system. Secondly, is your bootloader unlocked? How you proceed depends on that. If you still want to install Nougat there are a couple of options. Let me know your current bootloader status. Above all, don't panic and do something rash.
Here is a link to your phone's stock firmware" https://www.filefactory.com/file/5c...24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip
Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.
Also thank you for the link to the firmware, I just checked and this is the same file that I already downloaded so I do at least have peace of mind that I selected the right one.
Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.
_wyrm said:
Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.
Click to expand...
Click to collapse
Hi, thanks for your reply, sadly I have tried all the options from the bootloader with no success, they do the following:
START - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
RESTART BOOTLOADER - Just takes me back to the same bootloader screen immediately
RECOVERY MODE - Takes me back to android man fallen over with 'No command' underneath
POWER OFF - turns it off (obviously lol)
FACTORY MODE - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BARCODES - displays white screen with four barcodes relating to IMEI, SKU, DATE and SERIAL NUMBER
BP TOOLS - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
QCOM - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BOOTLOADER LOGS - Doesn't do anything when I click the power button on this option but shows some yellow text on the screen that says 'Fastboot reason: Volume down key pressed'
That is all the options I have then, none seem to resolve the problem.
Thank you
Also, I'm not sure if this is relevant but when I ran the flashstock.bat file to try and install the files from XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml, I noticed as the text scrolled up the CMD window that there was several mentions of:
slot count not found
slot suffixes not found
has-slot system not found
invalid signed image
These lines appear several times, I'm not sure if this is part of the problem or not. If the CMD window didn't automatically close I would have copied and pasted exactly what it says.
Thanks again
Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.
adavies said:
Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.
Click to expand...
Click to collapse
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
_wyrm said:
Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.
Click to expand...
Click to collapse
Hi, thank you for your reply, I just downloaded and tried the RSD Lite software. It detected my phone on Port number 1 as 'Fastboot athene_13mp S' and I selected the 'flashfile.xml' and pressed start. Unfortunately it stopped with the status 'Failed flashing process. 3/27 flash partition "gpt.bin" -> Phone returned FAIL.' Does anyone know how to get round this?
Thank you
pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
]
Click to expand...
Click to collapse
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.
adavies said:
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.
Click to expand...
Click to collapse
Did you manually flash the fastboot images in the sequence provided?
If that doesn't work, I would send it back to Motorola. If it isn't in warranty, well, rip.
pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
I do still get the serial number when running 'fastboot devices', do you think unlocking the bootloader might be the answer? I went through te steps yesterday to get the code, was a little put off by voiding the warranty though. With regards to running the commands one at a time, I think I am now getting a bit confused on the correct procedure of where to run the commands from. I have tried running it from the folder for 'Minimal ADB and fastboot' (this folder contains all the files from the stock firmware folder as well which I copied and pasted in there) and also directly from the stock firmware folder itself. I will paste the results of each below (sorry to confuse the issue, my head is fried now, lol).
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.049s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I stopped after the second line as the text above suggests to me that part has failed so no point continuing. When running directly from the firmware folder I get the following :
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot devices
ZY223H6QF4 fastboot
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.062s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>
Again this seems to fail also but with some slightly different messages. Interesting that it failed on the gpt.bin part as this was also mentioned when it failed on RSD Lite.
If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.
_wyrm said:
If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.
Click to expand...
Click to collapse
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.
adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
AFAIK, this one isnt safe to skip.. Im out of ideas, sorry. Try another usb cable just in case.. but if it keeps failing at the same point you will probably need to send it to motorola service.
pastorbob62 said:
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.
Click to expand...
Click to collapse
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.
negusp said:
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.
Click to expand...
Click to collapse
You may be right. He has not successfully unlocked the phone so therefore his warranty should still be good.
---------- Post added at 04:18 PM ---------- Previous post was at 03:51 PM ----------
adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
I don't understand why you can't flash the stock ROM. Your baseband version is still on stock. That said if you want to continue trying give this a shot: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943 This will bring you up to Nougat the latest release. It does not require an unlocked bootloader and has been used on your model.
Or here: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
Otherwise I would go ahead and do a warranty return. Your warranty should still be okay since you did not go through with unlocking the bootloader.
Click to expand...
Click to collapse
Related
So I successfully installed TWRP recovery.
I then tried to flash SuperSU, but that gave me a boot loop, so I wanted to try and flash the stock rom again.
I wiped my phone with TWRP.
I wasn't totally sure what the correct version of the ROM was to download. I can't check because the phone is already wiped. It's a UK Moto X Play "lux XT1562 16GB P2C" single sim slot. I had installed an OTA update yesterday. I downloaded XT1562_LUX_RETEU_6.0.1_MPD24.107-52.xml.zip, would that be the correct version? Is there any way to know for sure?
So when I tried to flash the stock rom I ran into problems.
I ran "fastboot flash partition gpt.bin" and I got "(bootloader) Preflash validation failed".
I saw someone say that this could be because you need to flash the correct version of the bootloader first, so I did "fastboot flash bootloader bootloader.img" which was successful, but even after restarting "fastboot flash partition gpt.bin" still failed.
I'm really confused as to what I'm doing wrong. Am I having problems because I'm trying to flash the wrong version of the bootloader, or a version older then that which I had on my phone before wiping? Is this the kind of error you'd get if you were trying to downgrade, or should that work fine?
Help greatly appreciated!
Edit: Should I possibly try flashing 5.1.1 X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip or is flashing an older version a bad idea?
Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen
tavares_one said:
Have you used this method? You have to export the zip file, its not a flashable zip and then you fastboot all the files via adb.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
---------- Post added at 03:40 AM ---------- Previous post was at 03:39 AM ----------
Also I think that its not considered bricked when you still open fastboot. Brick means there's no way to flash anything at all wich is really hard to happen
Click to expand...
Click to collapse
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
It fails when I try and flash gpt.bin
Code:
❯ fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.143s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.740s
and on the bootloader logs is says
Code:
cmd: getvar:partition-type:partition
cmd: getvar:max-download-size
cmd: download 00008000
cmd: flash:partition
version downgraded for primary_gpt
johtso said:
Sorry, should have said "soft-bricked".
Looking at the guide you linked, it doesn't seem to suggest anything different from what I'm already doing. I'm following the how-to-unroot-the-motorola-moto-x-play guide on theunlockr.
Click to expand...
Click to collapse
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Dio-Genes said:
You should try the Motorola device manager, it helped me once, when I deleted ALL and couldn't acces the phone anymore. Worked very easy, at least you get full access again va ADB.
Click to expand...
Click to collapse
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.
johtso said:
I already have access to the phone, I have bootloader and recovery, just no firmware, but can't get flashing of the stock firmware to work.
Click to expand...
Click to collapse
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
fablebreton said:
I have read somewhere gpt.bin was not to flash under certain circumstances, don't remember exactly, but you can try without to see.
And i my case ( in france) my rom was a retasia (bought on amazon)
The normal process is below, but look your unziped files, you can have sparsechunk.7 sparsechunk.8 too
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
...
Click to expand...
Click to collapse
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s
johtso said:
Flashing boot.img doesn't work either
Code:
❯ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (32768 KB)...
OKAY [ 1.032s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.770s
Click to expand...
Click to collapse
Your bootloader is unlocked ?
fablebreton said:
Your bootloader is unlocked ?
Click to expand...
Click to collapse
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.
johtso said:
Yes, I've unlocked my bootloader, and successfully flashed TWRP. Bootloader says "Device is UNLOCKED. Status Code: 3"
Click to expand...
Click to collapse
if impossible with stock and if Twrp ok why not flash a custom rom
minimale_ldz said:
try this command in fastboot:
Code:
fastboot getvar all
and see if it tells you anything about your current firmware and flash exactly the same one. Look for
Code:
(bootloader) ro.build.fingerprint:
line.
Click to expand...
Click to collapse
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU
johtso said:
Thanks for the pointer, didn't know about this command!
Bare in mind that I've already fully wiped the phone in TWRP, and I also successfully flashed the bootloader (and just the bootloader) from the 6.0.1 rom I mentioned above. Would this not affect the output?
This is what I get:
Code:
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-5/5:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.5.lux_reteu.r
(bootloader) ro.build.version.full[1]: eteu.en.EU
Click to expand...
Click to collapse
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says
minimale_ldz said:
Looks like you've got this one:
http://www.filefactory.com/file/qqz...S24.107-52-5_cid7_subsidy-DEFAULT_CFC.xml.zip
try it and see what it says
Click to expand...
Click to collapse
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Edit: It worked! You're an absolute life saver! So confusing that those two ROM are named so similarly..
johtso said:
Ah interesting! That seems to be a slightly different variant? MPDS2 instead of MPD2.. any idea what that means?
Nearly downloaded, will give it a go and see what happens!
Click to expand...
Click to collapse
No idea what it means, but both your getvar info and linked firmware are MPDS. Anyway - good luck.
Hi, Here is my issue: I have the xt1625 and i downloaded an OTA nougat software from india NPJ25.9 (7.0). It worked great, then i unlock my bootloader to install cm14. The problem began when i wanted to revert back to the official Nougat, i was able to come back but the .bat file that came with the Stock Rom didnt have the option to relock the bootloader so i tried downgrade to mm to lock it with the fastboot oem lock begin and fastboot oem lock, However it didnt work.
The mfastboot said bootloader pre verification failed and never locked, so i went back to nougat which i am running atm. the problem is i still am with unlocked bootloader and i see a change in the warning screen instead of n/a it says bad key.
another problem i see is during flashing some of them return (bootloader) image signed with key bad key
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.560s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.276s]
finished. total time: 0.842s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.556s]
writing 'recovery'...
(bootloader) Image signed with key bad key
And the lock never happens. it says at the end: flash a valid android image and rerun the comand.
Does anyone have a solution for this? can the bootloader be locked with nougar rom, if so, should i edit the .bat file? and how? i tried edditing the .bat file but dont know how. does the ''bad key'' message means something wrong?
Samerhk said:
Hi, Here is my issue: I have the xt1625 and i downloaded an OTA nougat software from india NPJ25.9 (7.0). It worked great, then i unlock my bootloader to install cm14. The problem began when i wanted to revert back to the official Nougat, i was able to come back but the .bat file that came with the Stock Rom didnt have the option to relock the bootloader so i tried downgrade to mm to lock it with the fastboot oem lock begin and fastboot oem lock, However it didnt work.
The mfastboot said bootloader pre verification failed and never locked, so i went back to nougat which i am running atm. the problem is i still am with unlocked bootloader and i see a change in the warning screen instead of n/a it says bad key.
Does anyone have a solution for this? can the bootloader be locked with nougar rom, if so, should i edit the .bat file? and how? i tried edditing the .bat file but dont know how. does the ''bad key'' message means something wrong?
Click to expand...
Click to collapse
I have successfully flashed latest nougat and locked my bootloader through oem lock command.
Iqbal Ansari said:
I have successfully flashed latest nougat and locked my bootloader through oem lock command.
Click to expand...
Click to collapse
my problem is the guy who posted the nougat rom did it with a .bat file but didnt include the lock comands, and i dont know how to add them. do you have the .bat file or bloc comands you can share?
Samerhk said:
my problem is the guy who posted the nougat rom did it with a .bat file but didnt include the lock comands, and i dont know how to add them. do you have the .bat file or bloc comands you can share?
Click to expand...
Click to collapse
The command to flash a factory image is everywhere. Just search.
These are the commands i used,
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
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot reboot
Iqbal Ansari said:
The command to flash a factory image is everywhere. Just search.
Click to expand...
Click to collapse
i have searched and tried every command. I noted after command fastboot oem unlock begin it gives and error saying still need signed boot.img and there is the problema with the bad key thing. i really am out of ideas here.
Samerhk said:
i have searched and tried every command. I noted after command fastboot oem unlock begin it gives and error saying still need signed boot.img and there is the problema with the bad key thing. i really am out of ideas here.
Click to expand...
Click to collapse
I used the firmware which is available on russian lenovo forum.
The error has something to do with your firmware.
Iqbal Ansari said:
I used the firmware which is available on russian lenovo forum.
The error has something to do with your firmware.
Click to expand...
Click to collapse
thanks. i will try a different nougat rom
Samerhk said:
thanks. i will try a different nougat rom
Click to expand...
Click to collapse
Can you tell if you managed to solve? i have the same problems when i tried to lock bootloader and haven't find any solution..
mksail said:
Can you tell if you managed to solve? i have the same problems when i tried to lock bootloader and haven't find any solution..
Click to expand...
Click to collapse
I did not. The nougat firmware I installed had a bad signature key and I could not relock because of it and downgrading did not help because boot loader cannot be downgraded. I have to wait for a newer nougat firmware with not bad key Signed to lock. I have npj25.99-11 so I have to wait for newer version.
Enviado desde mi Moto G (4) mediante Tapatalk
Samerhk said:
I did not. The nougat firmware I installed had a bad signature key and I could not relock because of it and downgrading did not help because boot loader cannot be downgraded. I have to wait for a newer nougat firmware with not bad key Signed to lock. I have npj25.99-11 so I have to wait for newer version.
Enviado desde mi Moto G (4) mediante Tapatalk
Click to expand...
Click to collapse
Hopefully not too long a wait - is 99-11 the latest build from Moto? Haven't seen any firmware updates captured yet.
Same here...
I flashed a Nugat rom last night and ran into the same issues. I'll be eager to flash again once a new rom is available.
Samerhk said:
...i still am with unlocked bootloader and i see a change in the warning screen instead of n/a it says bad key.
another problem i see is during flashing some of them return (bootloader) image signed with key bad key
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.560s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.276s]
finished. total time: 0.842s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.556s]
writing 'recovery'...
(bootloader) Image signed with key bad key
Click to expand...
Click to collapse
Same, but when I run the commands to lock the bootloader, the phone stays at "bad key" forever ( no warning message only a black screen with "bad key" on it) and i have to flash the rom without the lock commands for the phone to boot. And I'm also getting those errors.
Mine is XT1641
Old thread, but same problem here. I can't get the phone to boot no matter what now. I tried out this link: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Everything is normal up to running the `fastboot flash boot boot.img` and then it complains `(bootloader) Image signed with key bad key`. The phone refuses to boot no matter what now. Any advice on how to fix it?
Old thread: Unrooting gives me bootloop?
Hi there everyone,
After upgrading to Oreo, I unlocked my bootloader, flashed TWRP and Magisk. After that I did a backup of my System and Boot partitions on my currently active slot B. For some reason Slot A doesn't really boot up, so I don't really know what's up with that.
The problem is, before rooting everything was perfect and after the root I feel the instability. I've been using rooted devices for years now and I've never really had problems with the stock ROM being rooted.
So how do I unroot? Well, it's as simple as clicking Complete Unroot in Magisk. Yeah, that bootloops. Trying to flash MagiskUninstaller zip? That bootloops too. The only thing that saved me from those bootloops was that backup I did with TWRP. Yeah, that was after Magisk already had take a crap on my boot image.
Any suggestions that don't involve me losing my 30 Gigs of precious data? I would like to try with Mi Flash Tool but I'm scared from bootlooping for long periods of time (I don't have all day, after all).
New question: How to lock bootloader without wiping?
Hi there again!
I tried flashing the original system.img and boot.img from a fastboot Oreo ROM I found online. I just wanted to lock my bootloader, since currently I don't really need Root access anymore and I don't want this poor security a phone with an unlocked bootloader brings. The problem is, when I type fastboot oem lock it doesn't want to boot anymore, even without Magisk.
Does anybody know a fastboot ROM out there that can be locked? At the official MIUI.com website the fastboot ROM hasn't been updated for a very long time and I don't want to wipe my data. Does anybody have a perfectly working Oreo image that can be locked?
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
_mysiak_ said:
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
Click to expand...
Click to collapse
Thank you very much for the help! I'm gonna try this now. I'm pretty new to this A/B partitioning scheme, I knew that there isn't a recovery partition but I didn't know that TWRP is stored in Boot.img
Thanks again! Have a wonderful day/night!
_mysiak_ said:
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
Click to expand...
Click to collapse
Hey there again!
I tried to boot from the stock boot.img but it bootloops again! The backup from before is, again, what saved me.
Am I stuck now? Is there something wrong with my system.img? Or my /data partition? I'm scared of even reflashing clean.
nicolasmart said:
Hey there again!
I tried to boot from the stock boot.img but it bootloops again! The backup from before is, again, what saved me.
Am I stuck now? Is there something wrong with my system.img? Or my /data partition? I'm scared of even reflashing clean.
Click to expand...
Click to collapse
Which stock boot.img exactly did you use?
_mysiak_ said:
Which stock boot.img exactly did you use?
Click to expand...
Click to collapse
The one from the Oreo fastboot ROM. Got it from here.
nicolasmart said:
The one from the Oreo fastboot ROM. Got it from here.
Click to expand...
Click to collapse
When you ran TWRP for the first time, it asked you if you want to allow system modification (mount as R/W) - did you allow it? If yes, it has tampered your system partition and you won't be able to boot with stock boot.img due to dm-verity. Either install Magisk again or reflash stock Oreo system.img (from the link you provided).
_mysiak_ said:
When you ran TWRP for the first time, it asked you if you want to allow system modification (mount as R/W) - did you allow it? If yes, it has tampered your system partition and you won't be able to boot with stock boot.img due to dm-verity. Either install Magisk again or reflash stock Oreo system.img (from the link you provided).
Click to expand...
Click to collapse
OK, I can reinstall the system.img and boot.img via Fastboot. It won't delete any data, right?
Edit: Thanks for all your support again! You're the saviour of my Mi!
nicolasmart said:
OK, I can reinstall the system.img and boot.img via Fastboot. It won't delete any data, right?
Edit: Thanks for all your support again! You're the saviour of my Mi!
Click to expand...
Click to collapse
Your data is safe as long as you don't run incorrect command (DON'T flash userdata.img and DON'T run fastboot command with "-w" switch)
fastboot flash boot boot.img
fastboot flash system_a (and/or system_b) system.img
and you are good to go. Don't panic when system flashing will appear as stuck, it takes some time while it splits 3gb file into 6 smaller ones and starts the actual flashing.
_mysiak_ said:
Your data is safe as long as you don't run incorrect command (DON'T flash userdata.img and DON'T run fastboot command with "-w" switch)
fastboot flash boot boot.img
fastboot flash system_a (and/or system_b) system.img
and you are good to go. Don't panic when system flashing will appear as stuck, it takes some time while it splits 3gb file into 6 smaller ones and starts the actual flashing.
Click to expand...
Click to collapse
Thank you! But why should I run fastboot flash boot boot.img?? Isn't it fastboot flash boot_b boot.img? I'm on slot B currently.
nicolasmart said:
Thank you! But why should I run fastboot flash boot boot.img?? Isn't it fastboot flash boot_b boot.img? I'm on slot B currently.
Click to expand...
Click to collapse
You are right, for restore you should "fastboot flash boot_b boot.img". I was probably thinking about rooting procedure where you should use "fastboot boot boot.img"
_mysiak_ said:
You are right, for restore you should "fastboot flash boot_b boot.img". I was probably thinking about rooting procedure where you should use "fastboot boot boot.img"
Click to expand...
Click to collapse
Well, I did all that and I now have a perfectly working system with stock recovery and I think it doesn't boot loop anymore with a stock boot image. Thank you!
However, I tried to lock my bootloader via fastboot oem lock, the first time I was using some shady boot image which should be "stock" but it really wasn't, and it said "The system has been destroyed." I really laughed at this label and went into fastboot to unlock my bootloader again. I switched the boot image to a legit one which has Magisk installed, tried to lock again but this time it flashed the Mi logo for a split second and then a dark screen appeared (can somebody please explain this weird behaviour?). I really scared because the PC wasn't detecting the phone but I held the Volume Down + Power buttons for 10 seconds hoping I will see the Mi Bunny on the Fastboot. Yeah, it worked. I unlocked the bootloader again (lol) and my phone was working again!
Don't worry! My phone's still OK and 100% functioning.
The only reason I tried to lock my bootloader with Magisk installed is because somebody said it worked for them. However, now I realize how risky would that be. Whenever an OTA appears you should hope you don't get locked out of your phone.
So, people with a rooted Mi A1 - don't lock your bootloader unless you fully unroot and revert to stock!!!
How can I lock my bootloader again without wiping? (See the updated first post for more information)
nicolasmart said:
How can I lock my bootloader again without wiping? (See the updated first post for more information)
Click to expand...
Click to collapse
Just wait for an official Xiaomi fastboot Oreo ROM and either use MiFlash or included script "flash_all_except_storage.bat". It will lock bootloader at the end of flashing procedure. Though you probably won't gain much added security as you can unlock the bootloader without data wipe at any time (some reports say that you even don't need "allow oem unlock" in developer settings, but I haven't tried that).
nicolasmart said:
How can I lock my bootloader again without wiping? (See the updated first post for more information)
Click to expand...
Click to collapse
For more detailed instructions have a look over here: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
flash_all_except_storage = Keep your data, bootloader gets re-locked is the variant you are looking for.
Please keep in mind, that downgrading is not recommended. So this solution is absolutely fine when you are at 7.12.19 or below.
If you are not, you have to wait for the next fastboot update package to become available (like me)
It’s better to do a clean flash using the ROM and MiFlash provided on Xiaomi Website to ensure that the system is unmodified and you won’t get errors or bricks during a future OTA.
I don't want to clean flash. It will take forever for Xiaomi to release the new fastboot ROM
nicolasmart said:
I don't want to clean flash. It will take forever for Xiaomi to release the new fastboot ROM
Click to expand...
Click to collapse
Fastboot ROM should be out in a couple of days, usually it's released one week after first OTA update (the one from 19th December was online on 26th or 27th if I remember correctly).
Edit: Clean flash is not necessary, only full flash of all stock images, except user data.
_mysiak_ said:
Though you probably won't gain much added security as you can unlock the bootloader without data wipe at any time
Click to expand...
Click to collapse
As an old Nexus user (Nexus 7, Nexus 7 2013, Nexus 5X) I was shocked when I have found this.
_mysiak_ said:
(some reports say that you even don't need "allow oem unlock" in developer settings, but I haven't tried that).
Click to expand...
Click to collapse
Even this is true for Mi A1 in Nougat and Oreo too. So two critical security omissions by XIAOMI. One must ask himself if it is bug or strange feature
Code:
Developer options / OEM unlocking
Alow the bootloader to be unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.073s
C:\>fastboot oem unlock
...
OKAY [ 0.153s]
finished. total time: 0.158s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.073s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
Developer options / OEM unlocking
Bootloader is already unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot oem lock
...
OKAY [ 0.088s]
finished. total time: 0.091s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\>
_jis_ said:
As an old Nexus user (Nexus 7, Nexus 7 2013, Nexus 5X) I was shocked when I have found this.
Even this is true for Mi A1 in Nougat and Oreo too. So two critical security omissions by XIAOMI. One must ask himself if it is bug or strange feature
Code:
Developer options / OEM unlocking
Alow the bootloader to be unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.073s
C:\>fastboot oem unlock
...
OKAY [ 0.153s]
finished. total time: 0.158s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.073s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
Developer options / OEM unlocking
Bootloader is already unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot oem lock
...
OKAY [ 0.088s]
finished. total time: 0.091s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\>
Click to expand...
Click to collapse
Thanks for the confirmation. I consider it as a serious security flaw and was really surprised as well. I would like to know Xiaomi's reason to do it this way.. Users should be aware that they have to keep data encrypted with good PIN/pattern and request it on each boot to keep information secure.
Hi guys, I'm new here and I just wanted to know if someone else have had this issue too and knew how to solve it.
Yesterday I was playing pool on my phone when suddenly it turned off. I though the battery was very low but I had barely charged it. When I was trying to turn it on it didn't respond, I connected the charger and noticed that the only thing that was working was the LED and the screen never turned on again, I realized that it was a hardbrick.
I guess the cause was that a few days ago I changed the kernel, I installed Elemental X kernel, but I didn't like how it was working on my device so I restored the backup with the RR ROM I always use and everything was normal until yesterday.
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
I use a zip file as help through adb commands on my laptop and the Fastboot Flash Mode (Secure) on my device.
I don't know what else to do and the problem is unknown for now.
Would it be the bootloader?
Is there a problem if the OEM is locked?
Is the non-existent IMEI interfering?
Am I doing things right?
What else should I do?
PS: It's obvious that I'm desperate and I know that is possible to save it.
Thanks for reading I hope someone answer.
Caney said:
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
Click to expand...
Click to collapse
That's not good, flashing wrong firmware can be dangerous to losing fingerprint and losing IMEI.
Get latest December's patch ROM from link thred and try to flash it. : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work
The device is in Fastboot Flash Mode (Secure), is it necessary to do that?
Caney said:
The device is in Fastboot Flash Mode (Secure), is it necessary to do that?
Click to expand...
Click to collapse
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it
stehaworth said:
@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work
Click to expand...
Click to collapse
stehaworth said:
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it
Click to expand...
Click to collapse
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.
Caney said:
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.
Click to expand...
Click to collapse
Tbh.... I'm not too sure... But I would start at looking into flashing full Moto stock image via fastboot (see other thread for details)
Hey, I think I have lock my bootloader accidentally :'c When I try to put the commands to flash firmware it throws me this:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
error: cannot load 'gpt.bin'
How do I unlock it?
You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all
C:\Users\hp>fastboot getvar all
(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: 5
(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: b61bc8aa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 57A9A70100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.291s
@Caney from this data, i can see bootloader version is old, so you can try blank-flash with September's gpt and bootloader.
Follow (link below) thread for it, and where it says about download gpt and Bootloader files, go for September's one (2nd link there)...
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
When you get bootloader (after blank-flash), flash December's update.
____Mdd said:
You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all
Click to expand...
Click to collapse
Why isn't that good?
Caney said:
Why isn't that good?
Click to expand...
Click to collapse
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...
____Mdd said:
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...
Click to expand...
Click to collapse
Oooh man, can you please attach the link of that gpt here? I don't find it.
Caney said:
Oooh man, can you please attach the link of that gpt here? I don't find it.
Click to expand...
Click to collapse
GPT and bootloader of the September 2017 stock ROM update (NPJS25.93-14-10) - bootloader version B1:06. https://drive.google.com/open?id=0B-GUyOfb8Ogzc25FdW1WUDBMS1U
GPT and bootloader of the December 2017 stock ROM update (NPJS25.93-14-13) - bootloader version B1:07.
https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80
However, I would caution against just using these files, and suggest that you update fully by flashing the entire stock September or December 2017 ROM. Your bootloader is from the November/December 2016 firmware (B1:03) so just updating your bootloader isn't a good idea, especially when it comes to OTA updates.
Alternatively, if you want to reflash the stock ROM that has the same bootloader version as your reported bootloader, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?
Caney said:
I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?
Click to expand...
Click to collapse
Are you following a guide to help you flash?
Generally for any flashing via fastboot (e.g. for stock ROMs or for TWRP)
1)Install the ADB and Motorola drivers as directed by the guide.
1a)Extract the stock ROM zip file (should be about 2 GB in size extracted), copy all the files to your ADB folder (so they're on the same level as your adb.exe and fastboot.exe).
2)Reboot your device to the bootloader (fastboot mode) and connect to your computer via USB. Preferably this should be the same cable as came with your device or another high quality data + power USB cable.
3)Open the ADB terminal on your computer and verify that your device is communicating by typing 'fastboot devices' in the ADB terminal, without quotes. This should return your device's serial number.
4)If so, then proceed with flashing as per the guide's fastboot commands. They are the same as the stock ROMs for Moto G4/Plus devices have followed the same layout (7 sparsechunks for system, for example). If you do not wish to re-lock your bootloader, then do not use the two OEM lock begin or the OEM lock commands. If you wish to try to keep your data, then you can omit fastboot erase userdata. However, with your device in the state it is, it may be worth thinking about a fresh start and erasing your userdata.
For omitting bootloader re-locking and trying to preserve your data (though be aware you may have to wipe anyway, the following fastboot commands should suffice.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
You can either edit a flashing script to mirror these commands and use the script or enter the commands, individually and in order, by copypasting each line into the ADB terminal, then executing. Ideally, you want to see [OKAY] before you proceed. You may see errors about 'Image signed with bad key' if you're actually still unlocked, that's normal.
However, if you see any other errors, such as pre-flash validation or security downgrade, then you will need to use a newer stock ROM. Depending on which blankflash you used, the September 2017 or December 2017 stock ROMs would be suitable candidates.
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
Click to expand...
Click to collapse
After flashing bootloader file from September ROM, your bootloader will be automatiically updated to B1.06 and same apply for December ROM.
But you have used the blank flash file so it is recommended to downloading the June 2017 fastboot ROM and flashing that in fastboot.
Caney said:
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
As of Windows PowerShell of WIndows 10 still it doesn't fully supported for all Commands and Features so Its better to use CMD or ADB.
Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
Then you may wish to try manually flashing each command individually, and in order, ensuring you see [OKAY] before continuing. The script may proceed too quickly to see if it's all worked, so manually flashing is another option. You could always add 'pause' before 'reboot' in the script (without quotes) to let you review the flash before rebooting.
As for Powershell instead of cmd, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/help/installing-twrp-using-powershell-t3727761/
As for updating bootloaders, I would recommend it - your bootloader is a crucially important piece of firmware and should stay at the same patch level as your system/device firmware. This should reduce the number of complications you may face and also ensure that OTA updates go more smoothly.
Be aware that the B1:06 bootloader in the June 2017 and September 2017 security patches (NPJS25.93-14-8 and NPJS25.93-14-10) close a bootloader vulnerability, which makes downgrading to an older stock ROM even more risky as it appears Motorola does not like you downgrading. Strictly speaking, it's not the act of downgrading, but the act of taking an OTA update whilst downgraded - the mismatch between your newer bootloader patch level and the older stock ROM can hard brick your device should you attempt to install an OTA update.
Furthermore, with the December 2017 stock ROM patch, bootloaders are updated to B1:07, meaning our current latest blankflash is not likely to work (blankflashes older than your current bootloader, corrupted or not, do not appear to be permitted to flash to your bootloader). So be careful when updating and flashing anything to your device if you choose to update to the December 2017 patch.
Hello all, I need your help. I tried everything and i can't unbrick my phone. After an OTA, then reebot the system stucks in the bootloader with the "Failed to validate boot image".
I can't unlock the OEM to flash a stock rom:
Code:
fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.010s]
finished. total time: 0.010s
Please, help me (sorry for my bad english)
Edd95 said:
Hello all, I need your help. I tried everything and i can't unbrick my phone. After an OTA, then reebot the system stucks in the bootloader with the "Failed to validate boot image".
I can't unlock the OEM to flash a stock rom:
Please, help me (sorry for my bad english)
Click to expand...
Click to collapse
Just flash stock firmware from bootloader.
Here is the firmware download link:-https://firmware.center/.zdrive/z_gdrive_viewer.php?ID=0Bw_NsGJYGFyVa1RkUC1tM3RrWVk
Link for minimal ADB:-https://androidfilehost.com/?fid=745425885120698566
---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------
Step 1:*Install*Minimal adb and fastboot and extract the downloaded*rom*to the same folder where you have installed Minimal And fastboot package.
Step 2: After extracting open command prompt in that folder (where you have extracted the*rom/ the adb and fastboot folder)
Step 3: Now*boot*your*phone*into your bootloader by pressing volume down+*power*button*at the same time.
Step 4: Type the following in your command prompt: fastboot*devices
If it detects your*device*move to the next step, if it does not then you will have to*install*drivers*for your*device.
Step 5: Now Copy the following*code*and paste it to your command prompt:
mfastboot oem fb_mode_set
mfastboot*flash*logo logo.bin
mfastboot*flash*boot*boot.img
mfastboot*flash*recovery recovery.img
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
Step 6: This will completely wipe your*data*and*install*stock 7.0*on your potter*device.*
Step7:-reboot your device.
(Note:-use this codes only, to flash firmware as your device is having a latest bootloader there is a chance of hard brick, don't use other codes.)
Done.
riyan65 said:
Just flash stock firmware from bootloader.
Click to expand...
Click to collapse
Hi riyan, I tried to flash the stock firm: POTTER_RETAIL_7.0_NPNS25.137-92-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml but im getting errors like:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
FAILED (remote failure)
finished. total time: 0.180s
And nothing happens, but it appears with the fastboot devices comm.
Edd95 said:
Hi riyan, I tried to flash the stock firm: POTTER_RETAIL_7.0_NPNS25.137-92-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml but im getting errors like:
And nothing happens, but it appears with the fastboot devices comm.
Click to expand...
Click to collapse
It seems your trying to flash a old version of the stock rom try with different one with a latest stock rom and then flash bootloader with same version you have in your phone then try to flash full stock
riyan65 said:
Try to just flash bootloader with same version you have in your phone then try to flash full stock
Click to expand...
Click to collapse
How can I get the version that my phone already have? I don’t remember what it was before the OTA (and then the brick)
Ty
Edd95 said:
How can I get the version that my phone already have? I don’t remember what it was before the OTA (and then the brick)
Ty
Click to expand...
Click to collapse
When you don't know on what firmware you were nobody else can. Where do you come from?
If it's India or Brazil the 92-14 build should be safe as it is the latest available so you can't downgrade.
If you're from Europe/US etc the 93-10 build is the latest available. You find both here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Sent from my Moto G5 Plus using XDA Labs
I get that error with minimal adb, use this system wide version, never failed me:
https://forum.xda-developers.com/showthread.php?t=2588979
Also, make sure you installed moto drivers:
https://drive.google.com/file/d/0B3byUPGqbBw_ZjdiWF8wNmkwc28/view
Wolfcity said:
When you don't know on what firmware you were nobody else can. Where do you come from?
If it's India or Brazil the 92-14 build should be safe as it is the latest available so you can't downgrade.
If you're from Europe/US etc the 93-10 build is the latest available. You find both here:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Hi again, I from Chile (LATAM) so Brazil build would work?
TY, and sorry for being a noob about this
Cupcake 1.5 said:
I get that error with minimal adb, use this system wide version, never failed me:
https://forum.xda-developers.com/showthread.php?t=2588979
Also, make sure you installed moto drivers:
https://drive.google.com/file/d/0B3byUPGqbBw_ZjdiWF8wNmkwc28/view
Click to expand...
Click to collapse
Hi Cupcake! I'll give it a try, ty for the advice, I'll post later what I get
I'm getting errors like this:
Code:
C:\adb>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.026s
but the phone it's connected and appears:
Code:
C:\adb>fastboot devices
35af6194 fastboot
Suggestions?
Edd95 said:
I'm getting errors like this:
but the phone it's connected and appears:
Suggestions?
Click to expand...
Click to collapse
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
FAILED (remote failure)
finished. total time: 0.180s
The first set of outputs (slot-count:not found and slot-suffixes:not found) is no failure.
It's just that Minimal ADB and Fastboot is checking if you've got a device with two slots like the Pixel devices with their A/B architecture. I get them too every time I use it. The failure message is supposed to be after that and is most probably the same like
Code:
C:\adb>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.026s
which is related to the bootloader as you wrote in your first post.
Have you flashed a firmware in the past that was older than the one you were running?
Than your bootloader has been downgraded and when you wanted to apply the OTA the bootloader was not the one the OTA expected.
Have you flashed some stock firmware in the past before applying the OTA?
If yes you have a real problem. In that case I would try to flash a TWRP flashable build:
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Sent from my Moto G5 Plus using XDA Labs