Related
I tried to update to 4.4 while keeping root, but messed up somewhere along the way. Now I can't flash system.img - fastboot says the buffer isn't big enough? - and so my phone won't boot past the opening Motorola logo.
Any suggestions? I'm on OSX, which is why I haven't been able to try RSD Lite.
EDIT: The speficic error info after running 'fastboot flash system.img system.img' is
sending 'system.img' (971855 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.337s
EDIT 2: SOLVED! Turns out that the older fastboot files have issues with large file sizes. I used the new fastboot file from here (zip file) and instructions #2 from here, specifically the following fastboot instructions:
astboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Hi guys, I think I really messed up my new Moto X: and when I say new I mean I bought it yesterday even if used and bricked today.
I had a 4.4 Sprint firmware and I followed the guide to unlock the device (which it seemed to work), since I need it in Europe with a Vodafone sim. After that I decided to get a UK firmware, so I flashed the phone with RSD Lite, but the flash failed and now in boot mode I have the following message: Partition (boot) Security Version Downgraded - Fasboot reason: boot failure. If you have the solution can you explain it step by step, I'm not actually good with this kind of things. Do you think I have to toss the device in the trash bin? Thank you
Jack881 said:
Hi guys, I think I really messed up my new Moto X: and when I say new I mean I bought it yesterday even if used and bricked today.
I had a 4.4 Sprint firmware and I followed the guide to unlock the device (which it seemed to work), since I need it in Europe with a Vodafone sim. After that I decided to get a UK firmware, so I flashed the phone with RSD Lite, but the flash failed and now in boot mode I have the following message: Partition (boot) Security Version Downgraded - Fasboot reason: boot failure. If you have the solution can you explain it step by step, I'm not actually good with this kind of things. Do you think I have to toss the device in the trash bin? Thank you
Click to expand...
Click to collapse
I just want to add that I've altready tried to flash back to the original version, but how you can imagine...nothing to do...
Jack881 said:
I just want to add that I've altready tried to flash back to the original version, but how you can imagine...nothing to do...
Click to expand...
Click to collapse
You shouldn't have attempted to downgrade and/or flash another carriers rom. It's documented many places not to do this. Now you are in a pickle.
This will probably fix you up:
Download the FULL SBF of the ROM you want to flash. It must be the SAME VERSION, or HIGHER than the newest version you have flashed.
Boot into bootloader.
Type:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Now you SHOULD be able to flash the ENTIRE SBF with RSD Lite or Manual method.
Explaination: By doing this, we are JUST flashing the bootloader and partition table (gpt.bin), THEN we reboot back to the bootloader in order to allow the bootloader to LOAD the new partition table before we flash the rest of the partitions.
It fixes people up most of the time, but not all. Good luck, hope it does the trick for you. Next time, heed the warning -- specifically not to downgrade. :good:
samwathegreat said:
You shouldn't have attempted to downgrade and/or flash another carriers rom. It's documented many places not to do this. Now you are in a pickle.
This will probably fix you up:
Download the FULL SBF of the ROM you want to flash. It must be the SAME VERSION, or HIGHER than the newest version you have flashed.
Boot into bootloader.
Type:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Now you SHOULD be able to flash the ENTIRE SBF with RSD Lite or Manual method.
Explaination: By doing this, we are JUST flashing the bootloader and partition table (gpt.bin), THEN we reboot back to the bootloader in order to allow the bootloader to LOAD the new partition table before we flash the rest of the partitions.
It fixes people up most of the time, but not all. Good luck, hope it does the trick for you. Next time, heed the warning -- specifically not to downgrade. :good:
Click to expand...
Click to collapse
You are very kind, but I don't know if I can do it. I downloaded the firmware. But wheere I have to type the command? Sorry I'm really ignorant...
Jack881 said:
You are very kind, but I don't know if I can do it. I downloaded the firmware. But wheere I have to type the command? Sorry I'm really ignorant...
Click to expand...
Click to collapse
Get the latest android SDK from here: http://developer.android.com/sdk/index.html
Install it. It should have a folder called "Platform-tools" inside. Put gpt.bin and motoboot.img from the firmware inside this folder. Then open a command prompt, go to that folder, then run the commands as I outlined in the previous post.
After you "fastboot reboot-bootloader", try to flash the entire firmware zip file using RSD Lite.
I tried, but when I type the device still write Fastboot reason:flash failure. Any idea? Maybe I did something wrong. Thank you.
samwathegreat said:
You shouldn't have attempted to downgrade and/or flash another carriers rom. It's documented many places not to do this. Now you are in a pickle.
This will probably fix you up:
Download the FULL SBF of the ROM you want to flash. It must be the SAME VERSION, or HIGHER than the newest version you have flashed.
Boot into bootloader.
Type:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Now you SHOULD be able to flash the ENTIRE SBF with RSD Lite or Manual method.
Explaination: By doing this, we are JUST flashing the bootloader and partition table (gpt.bin), THEN we reboot back to the bootloader in order to allow the bootloader to LOAD the new partition table before we flash the rest of the partitions.
It fixes people up most of the time, but not all. Good luck, hope it does the trick for you. Next time, heed the warning -- specifically not to downgrade. :good:
Click to expand...
Click to collapse
This is what it writes when I type the commands:
target reported max download size of 805306368 bytes
sending 'bootloader' (1604 KB)...
OKAY [ 0.346s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.454s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.261s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.146s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.010s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
Can you help me? thank you.
Jack881 said:
This is what it writes when I type the commands:
target reported max download size of 805306368 bytes
sending 'bootloader' (1604 KB)...
OKAY [ 0.346s]
writing 'bootloader'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.454s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.261s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.146s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.010s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
Can you help me? thank you.
Click to expand...
Click to collapse
You noted that you flashed multiple ROMS. What is the LATEST VERSION of all the roms you tried to flash. You can never go lower, so please advise. Did you flash --any-- 4.4.2 or 4.4.4 ROM? If so, you MUST flash a new rom of the same or higher version.
samwathegreat said:
You noted that you flashed multiple ROMS. What is the LATEST VERSION of all the roms you tried to flash. You can never go lower, so please advise. Did you flash --any-- 4.4.2 or 4.4.4 ROM? If so, you MUST flash a new rom of the same or higher version.
Click to expand...
Click to collapse
I flashed a UK retail 4.4.2 and after a France retail 4.4.2...what should I flash now? I was trying your system on the Sprint 4.4 which was the original firmware of the telephone...
Jack881 said:
I flashed a UK retail 4.4.2 and after a France retail 4.4.2...what should I flash now? I was trying your system on the Sprint 4.4 which was the original firmware of the telephone...
Click to expand...
Click to collapse
That will absolutely not work. You are attempting to downgrade!!! (4.4.2 > 4.4) I already mentioned that you must use the same version or higher than the highest version you flashed previously. You MUST flash the Sprint 4.4.2 ROM, and not 4.4
If you try again, with the 4.4.2 Sprint SBF, you should be able to successfully recover.
Jack881 said:
I flashed a UK retail 4.4.2 and after a France retail 4.4.2...what should I flash now? I was trying your system on the Sprint 4.4 which was the original firmware of the telephone...
Click to expand...
Click to collapse
I also tried the 4.4.2 Sprint now, but same results. Do I have to get the file from the same firmware I flash, right? and when I flash do I have to flash without the getvar string?
Jack881 said:
I also tried the 4.4.2 Sprint now, but same results. Do I have to get the file from the same firmware I flash, right? and when I flash do I have to flash without the getvar string?
Click to expand...
Click to collapse
Please just use the manual method.
Do this:
First extract all the files in the SBF zip file (the 4.4.2 Sprint one!!!!!) to the same folder that includes fastboot & mfastboot (you do have the "mfastboot" binary, right?)
Now do this exactly: (ignore the fact that some of these commands are being run twice - this is intentional. Also notice that we are using "mfastboot" to flash system.img. If you don't have it, get it here [and put it in the same folder as fastboot]: https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit )
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot 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
If everything is successful to this point, now do:
fastboot reboot
If something fails, move on with the other commands. If you get stuck, let me know. Pictures of the errors will be helpful if you have any.
Taking timgree
samwathegreat said:
Please just use the manual method.
Do this:
First extract all the files in the SBF zip file (the 4.4.2 Sprint one!!!!!) to the same folder that includes fastboot & mfastboot (you do have the "mfastboot" binary, right?)
Now do this exactly: (ignore the fact that some of these commands are being run twice - this is intentional. Also notice that we are using "mfastboot" to flash system.img. If you don't have it, get it here [and put it in the same folder as fastboot]: https://docs.google.com/file/d/0B9qC3vvamytkSVp0NXhlSEhZVFU/edit )
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot 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
If everything is successful to this point, now do:
fastboot reboot
If something fails, move on with the other commands. If you get stuck, let me know. Pictures of the errors will be helpful if you have any.
Click to expand...
Click to collapse
First of all I want to thank you, because I've never med anyone so kind online. Unfortunately I didn't succeed. I explain you exactly what I did:
1) I got from here http://sbf.droid-developers.org/phone.php?device=0 the Sprint 4.4.2 firmware (I had 4.4 originally, so this should be fine according to what you said)
2) I unzipped every file inside sdk/platform-tools
3) I downloaded your mfastboot (since I didn't have it) and stick it inside the same folder sdk/platform tools
4) So now I have this folder with inside all the files I thought you were asking to have there
5) at this point I opened from there the command prompt and started to type the commands you suggested
6) I had this:
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot partition gpt.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.027s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
I got stuck at the second command. Any idea? thank you.
Jack881 said:
First of all I want to thank you, because I've never med anyone so kind online. Unfortunately I didn't succeed. I explain you exactly what I did:
1) I got from here http://sbf.droid-developers.org/phone.php?device=0 the Sprint 4.4.2 firmware (I had 4.4 originally, so this should be fine according to what you said)
2) I unzipped every file inside sdk/platform-tools
3) I downloaded your mfastboot (since I didn't have it) and stick it inside the same folder sdk/platform tools
4) So now I have this folder with inside all the files I thought you were asking to have there
5) at this point I opened from there the command prompt and started to type the commands you suggested
6) I had this:
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot partition gpt.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.344s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.027s
C:\Users\Giacomo\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
I got stuck at the second command. Any idea? thank you.
Click to expand...
Click to collapse
You also didn't correctly issue the first command. You left out "flash"
You typed "fastboot partition gpt.bin"
Instead of "fastboot flash partition gpt.bin"
Please start over. If it fails at motoboot.img -- don't worry. Just continue with the rest of the commands. If we can get everything else to flash, you may well recover. Sometimes it DOES fail at flashing motoboot, but just continue with the commands.
Be sure to type them EXACTLY as I've listed -- you can't leave off "flash" anymore
Please try and update as to status. If you can get to the very end, with nothing but motoboot.img failing, we should be able to recover you.
samwathegreat said:
You also didn't correctly issue the first command. You left out "flash"
You typed "fastboot partition gpt.bin"
Instead of "fastboot flash partition gpt.bin"
Please start over. If it fails at motoboot.img -- don't worry. Just continue with the rest of the commands. If we can get everything else to flash, you may well recover. Sometimes it DOES fail at flashing motoboot, but just continue with the commands.
Be sure to type them EXACTLY as I've listed -- you can't leave off "flash" anymore
Please try and update as to status. If you can get to the very end, with nothing but motoboot.img failing, we should be able to recover you.
Click to expand...
Click to collapse
Something moving...I repeated every single command, now I have on the phone Fastboot reason: Sticky bit factory_fastboot
What should I do now?
Thank you
Jack881 said:
Something moving...I repeated every single command, now I have on the phone Fastboot reason: Sticky bit factory_fastboot
What should I do now?
Thank you
Click to expand...
Click to collapse
Do this:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then start over with all the commands I previously listed
I recommend using copy / paste for all the commands just so none get messed up
samwathegreat said:
Do this:
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then start over with all the commands I previously listed
I recommend using copy / paste for all the commands just so none get messed up
Click to expand...
Click to collapse
I did it: fastboot oem fb_mode_clear and fastboot reboot-bootloader and repeated all the commands, but now I have Partition (boot) Security version Downgraded. Fastboot reason: boot failure. Thank you
Jack881 said:
I did it: fastboot oem fb_mode_clear and fastboot reboot-bootloader and repeated all the commands, but now I have Partition (boot) Security version Downgraded. Fastboot reason: boot failure. Thank you
Click to expand...
Click to collapse
OK!
It looks like when you were on one of the other roms, you accepted an OTA to 4.4.3 or 4.4.4.....did this happen?
anyways, do this:
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot 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 fb_mode_clear
fastboot reboot
Does it boot?? Hopefully at this point, you boot into android. Fingers crossed.... :fingers-crossed:
samwathegreat said:
OK!
It looks like when you were on one of the other roms, you accepted an OTA to 4.4.3 or 4.4.4.....did this happen?
anyways, do this:
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot 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 fb_mode_clear
fastboot reboot
Does it boot?? Hopefully at this point, you boot into android. Fingers crossed.... :fingers-crossed:
Click to expand...
Click to collapse
No, gosh! maybe I have to repeat everything? now I have Partition (boot) Security version Downgraded Fastboot reason: Boot failure
Jack881 said:
No, gosh! maybe I have to repeat everything? now I have Partition (boot) Security version Downgraded Fastboot reason: Boot failure
Click to expand...
Click to collapse
I will have to continue helping you later tonight. Have to leave for a bit. I'm still hoping we will be able to recover you but it will take some more work, and we have to run the commands perfect. I'll post back here when I return.
Ok, so I'll be the first to admit, I'm a bit new to all this.... I figured I was following directions, but something went amiss...
I was working through the process to put CM11 on my Razr i (which had the soak of 4.4.2 from Motorola on it...).
I unlocked the bootloader, rooted it, (but of course never made a back-up). I was able to put in TWRP into the recovery partition and attempt to flash the OS zip image - which failed.
In that thread, there were many options to try, which I did, and eventually my phone will either get stuck at the "Warning - Bootloader Unlocked" screen, or if I reboot with Power/VolDown I can get into Fastboot. But every option in Fastboot menu just reboots the phone.
I can get to the phone with Fastboot from the PC through USB - and it *looks* like I can re-flash different recovery images, but nothing seems to change. The Lebobo flasher will not flash to the device at all - keeps saying "waiting for device" with any option. I have the Motorola USB drivers loaded.
Not sure what else to try.....
Check your drivers again and even reinstall them. U will need the Motorola ones and maybe even the Google ones.
The lebobo flasher uses the 'fastboot' executable to interact with the phone in fastboot. Get a copy off the fastboot exe from the Index thread in the general section. If u have the fastboot.exe or 'fastboot' binary if u are on linux then reboot your phone in bootloader mode. Open a commandprompt in the directory where u have the fastboot executable (shift+right mouse button). Now do the command "fastboot devices" if your device shows up in it the drivers are correctly installed. If it doesn't it not. If it does, install a recovery by using the command "fastboot flash recovery recovery.img" assuming u renamed the recovery image to recovery.img.
i have the same probleme , my motorola razr i is stuck on warning ......... help me pleas:crying:
Verified Moto driver installed (reinstalled).
fastboot.exe is latest from Android SDK - api 21 version
fastboot devices shows "TA237059P0 fastboot"
fastboot flash recovery recovery.img looks like it works. on the PC says "OKAY" and finished. On the phone says Downloading.... then Flashing recovery ... but just sits there. Tried with 2 different Recovery images.
Forgot to mention - in command window on PC, when I use above commend - first thing that comes back "(bootloader) Variable not supported!"
If I use fastboot menu on the phone to then go to Recovery, the phone reboots and sits at the Warning screen again.
Lelobo still says "waiting for device" even though command line fastboot seems to connect to the device.
Wipe cache through fastboot and try again. It van help
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
ccallana said:
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
Click to expand...
Click to collapse
Success!! used "fastboot erase cache" instead.... then flashed in the suggested Newbie recovery on page 1 of the CM11 thread. adb wouldn't sideload the modded image, so I stuck it on an sd card and loaded it from there... and voila, it is booting!
I have an XT1095. I flashed the 23.1.28 leaked OTA a couple of months ago to get to 5.1, and now I'm attempting to get to the final 5.1 OTA. My phone was unrooted, and had the stock recovery.
I downloaded the nycgraffix 5.0 image. I followed this guide, but I forgot to unlock the bootloader. I got partway though flashing the files before I realized my mistake. Here's how it went, to the best of my memory:
Unzip the stock 5.0 image SUCCEEDED
Boot into fastboot SUCCEEDED
fastboot flash logo logo.bin SUCCEEDED
fastboot flash boot boot.img SUCCEEDED
fastboot flash recovery recovery.img SUCCEEDED
fastboot flash system system.img_sparsechunk.0 FAILED
Here's what happened on the failure:
Code:
C:\android\x\gnyc>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.081s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.190s
At this point, I realized I forgot to unlock, so I issued the "fastboot oem unlock" command with the key I got from Motorola. Unfortunately, this now fails:
Code:
C:\android\x\gnyc>fastboot oem unlock JQ3QVNTEBxxxxxxxxxx
...
(bootloader) Check 'Enable OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
The phone now only boots into fastboot, saying "Fastboot Reason: Last time flashing failed".
I'd be grateful for any help bailing out of this.
I decided to try the stock image that Motorola posted (note: this image won't allow you to get the 5.1 OTA!). Using the fastboot from Android's SDK, I did this:
Code:
1. Make sure you have a Moto Pure Edition or a Developer Edition device.
2. Make sure you download the corresponding recovery image from the above portal.
3. To flash, put the phone in fastboot mode: Power OFF...then Power ON+Volume Down .Alternatively, you can reboot into fastboot mode if you have adb... adb reboot bootloader
4. Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
All these succeeded except the boot.img. So I tried unlocking again:
Code:
C:\android\x\official\TMO_LXE22.46-11_22.21.11.victara_tmo.tmo.en.US\TMO_LXE22.4
6-11_22.21.11.victara_tmo.tmo.en.US>fastboot oem unlock JQ3QVxxxxxxxxxxxx
...
(bootloader) Unlock code = JQ3QVxxxxxxxxxxxx
(bootloader) Unlock completed! Wait to reboot
Since that succeeded, I tried again:
Code:
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
These all succeeded and I'm booting to 5.0 again. Now I'll re-attempt the nycgraffix image so I can finally get the real 5.1 OTA.
I got the 5.1 OTA update as soon as I booted into the GraffixNYC image. I donated $20, since Motorola's own image is screwed up.
My next phone will be a Nexus. This phone has been a complete mess.
I've had my Moto G6 rooted for some time now. An ota update for PPS29.118-15-11-16 was continually nagging so I uninstalled Magisk and installed it.
Upon reboot when checking for updates I now get the following:
As your device system integrity is compromised, it is no longer eligible for software updates. Please contact customer service to re-program the device with official software.
I tried restoring to factory using Lenovo Moto smart assistant and that worked as it should. I still get the same "System integrity is compromised" error. I was under the impression that this would be reset upon doing this factory reset.
How would I get this message to be removed as I don't ever remember seeing it when this phone was rooted all this time.
Thanks
If I downgrade back to my last version PPSS29.118-15-11-9 the "System integrity is compromised" is NOT present.
Installing magisk seems to allow the ota updater to NOT report the "System integrity is compromised". As for stock, no dice.
minipretzel said:
Installing magisk seems to allow the ota updater to NOT report the "System integrity is compromised". As for stock, no dice.
Click to expand...
Click to collapse
without Magisk = system recognizes your unlocked bootloader
with Magisk = unlocked bootloader is hidden and OTAs and OEM-Unlock toggle are enabled, even SafetyNet check will pass.
I know this thread is old but I have the exact same problem.
I also restored stock roms from PPS29.118-15-11-16 using Smart assistant. I was already at this version, but I did the update anyway, as I have read that the smart assistant rescue would completely restore the phone to stock condition. But this didn't clear my "System Integrity..." message.
Just fyi, I actually ran the smart assistant commands manually... The SA failed to update my phone so I reconstructed the commands from the xml file and executed them one by one to find and fix this problem.
I re-ran the standard rescue after this and it was fine.
I noticed that my oem lock/unlock switch is enabled in my system->developer settings ( this was greyed out before).
Thing is, I do have magisk installed , as I wanted to root the phone. But this doesn't clear the message as it did for the OP.
I saw another article (thread) that recommended issuing "fastboot oem lock" twice, followed by some (re)flashing of the oem, system, and boot img files, and one final lock command. See "Using Lenovo Moto Smart Assistant to restore stock rom (and lock bootloader after)" by alexmaisa.
But the article by alexmaisa is from 2019 and is for a G5S....
Any ideas would be greatly appreciated.
pdpantages said:
I noticed that my oem lock/unlock switch is enabled in my system->developer settings ( this was greyed out before).
Click to expand...
Click to collapse
With magisk installed it's quiet normal.
pdpantages said:
I saw another article (thread) that recommended issuing "fastboot oem lock" twice, followed by some (re)flashing of the oem, system, and boot img files, and one final lock command. See "Using Lenovo Moto Smart Assistant to restore stock rom (and lock bootloader after)" by alexmaisa.
Click to expand...
Click to collapse
That's the correct way to relock your bootloader. Just follow the output lines in your cmd after executing fastboot oem lock.
WoKoschekk said:
That's the correct way to relock your bootloader. Just follow the output lines in your cmd after executing fastboot oem lock.
Click to expand...
Click to collapse
Thank you for the input. My bootloader was locked so the lock commands just reported this. When I ran the subsequent commands I got an error about unable to flash (bc the bootloader was locked)..... I thought maybe the original post had a typo so I switched to two "unlock" commands as the first commands. This unlocked me, and all the subsequent commands completed OK, including the final lock. But after setup I still have the System Integrity msg when I check for s/w updates under System menu.
The original post was from 2020 so possibly my version of Magisk (24.3) is the cause.?
I have most of what I want; latest stock ROMs and phone is rooted... just want to clear the problem with s/w updates.
I found another command set that that flashed the boot, system and oem twice.. I have cut these commands below. Unfortunately I don't recall where I got the bat file. It was called FLASH_OEM_LOCK.bat. Again these commands issue a lock command followed by some flash cmds which I thought would not work with the bootloader locked? Does a lock command not take effect until after reboot or something? Anyway, here they are:
fastboot oem lock
fastboot oem lock
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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash boot boot.img
fastboot oem lock
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
@pdpantages That's the way to relock the bootloader and get the status "oem_locked":
1. Flash the current complete firmware
2. !!! THIS STEP IS HIGHLY RECOMMENDED !!!
If your bootloader will be relocked successfully after these steps, you won't have any options to fix errors! So, this is your last chance...
Important functions to check: are you able to boot into system, mobile (data) connections, Wifi
boot into system and check everything's working fine.
3. Are you really sure everything`s fine?
4. *** The following shows fastboot commands + output for a better understanding of what we are doing here. I took them from the last relock of my Moto G6 ***
Reboot into bootloader and run these commands:
Code:
########################################################################
# new lines beginning with "#" are comments and should not be executed!!
########################################################################
$ fastboot oem lock
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.001s]
finished. total time: 0.001s
$ fastboot oem lock
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.002s]
finished. total time: 0.002s
# no need to flash the whole firmware (= valid Android images) again since we already did it in step 1.. Skip it and run lock command again.
$ fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.001s]
finished. total time: 0.001s
# ATTENTION: Cannot be skipped as we did before! Bootloader needs signed boot.img a second time!
$ fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.919s]
writing 'boot'...
OKAY [ 0.518s]
finished. total time: 1.438s
$ fastboot oem lock
...
(bootloader) Still require signed system.img and/or oem.img
OKAY [ 0.001s]
finished. total time: 0.001s
# ATTENTION: Cannot be skipped as we did before! Bootloader needs signed system/oem.img AND vendor.img (it's also signed since it contains sensitive firmware data, too) a second time!
$ fastboot flash system system.img_sparsechunk*
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 9.463s]
writing 'system'...
OKAY [ 5.836s]
finished. total time: 15.300s
(...flashing all other sparse images of system...)
$ fastboot flash vendor vendor.img_sparsechunk*
target reported max download size of 534773760 bytes
sending 'vendor' (254668 KB)...
OKAY [ 8.950s]
writing 'vendor'...
OKAY [ 5.484s]
finished. total time: 14.434s
( ...flashing all other sparse images of vendor...)
$ fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (153181 KB)...
OKAY [ 5.566s]
writing 'oem'...
OKAY [ 4.727s]
finished. total time: 10.294s
# now bootloader is satisfied and can be locked (yeah!!)
$ fastboot oem lock
...
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.163s]
finished. total time: 0.163s
Thank you kindly for the into. The notes in particular clarified things for me quite a bit, and I understand that issuing the unlock commands as I did was incorrect. I will try it shortly and report the success or failure of my attempt.
My bl is currently locked- my intent is to unlock it (2 commands) , let the phone reset and boot, verify with "fastboot flashing get_unlock_ability" that it is in fact unlocked, and start your procedure from there...
Thank you again for the help. I expect your post will be helpful to others too.
pdpantages said:
I will try it shortly and report the success or failure of my attempt.
Click to expand...
Click to collapse
So I did as promised. The basic answer is that it worked as described. A few notes follow; things I wonder about and error msgs I saw.
Procedure: Not exactly as outlined above; my boot loader was locked so I issued some unlock commands:
rigel:/home/pdp/adb>fastboot oem unlock
(bootloader) invalid boot state
OKAY [ 0.006s]
Finished. Total time: 0.006s
rigel:/home/pdp/adb>fastboot oem unlock
(bootloader) invalid boot state
OKAY [ 0.001s]
Finished. Total time: 0.001s
rigel:/home/pdp/adb>fastboot flashing unlock
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.001s]
Finished. Total time: 0.001s
So, I got errors trying oem unlock but "flashing unlock" worked and the phone booted when I entered the second one. Not sure if this is an issue or not.
Errors: I got a "not found" error with each img I flashed. I was a bit nervous about this as it looked like partition names were "not found". But despite this, the commands appeared to work so I carried on.
rigel:/home/pdp/adb> fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (22528 KB) OKAY [ 0.901s]
Writing 'boot' OKAY [ 0.381s]
Finished. Total time: 1.675s
In the end, everything worked as expected- the "System Integrity..." message was gone from the Software update setting, and the also the boot-time warming about unlocked bootloader was gone (I have seen many posts claiming it is not possible to clear this message).
Magisk: After all that, I still wanted to root my phone... I thought i would be able to install Magisk using twrp.
I tried booting into twrp recovery using adb (not flashing recovery.img ) but this didn't work. So in the end I unlocked my bootloader again. (required the unlock key) to install Magisk.
WoKoschekk said:
with Magisk = unlocked bootloader is hidden and OTAs and OEM-Unlock toggle are enabled, even SafetyNet check will pass.
Click to expand...
Click to collapse
I was hoping the above would apply to me but it didn't; I now see the "System Integrity message" again in my software update settings. It is manageable- if I really want a software update I now know how to revert the phone to stock. Now that I am rooted I can make backups with Titanium Backup which was my primary motive for rooting in the first place .
Thank you again for the help, WoKoschekk , it is much appreciated.
pdpantages said:
Not sure if this is an issue or not.
Click to expand...
Click to collapse
It seems to be an issue because oem unlock does work for me. But as long as your bootloader is unlocked it does not matter.
pdpantages said:
and the also the boot-time warming about unlocked bootloader was gone (I have seen many posts claiming it is not possible to clear this message)
Click to expand...
Click to collapse
It happens on Moto G6+ devices but not on our device.
pdpantages said:
Errors: I got a "not found" error with each img I flashed. I was a bit nervous about this as it looked like partition names were "not found".
Click to expand...
Click to collapse
This is related to the new fastboot versions that are used to flash devices with a partition /super. It contains /system, /vendor and some others and they are called "logical partitions". Moto G6 does not use a /super partition and you can ignore that check by fastboot.
WoKoschekk said:
This is related to the new fastboot versions that are used to flash devices with a partition /super. It contains /system, /vendor and some others and they are called "logical partitions". Moto G6 does not use a /super partition and you can ignore that check by fastboot.
Click to expand...
Click to collapse
OK thank you again. I see now that I get this error when I flash from Linux, but not Windows 10....
In case it might help someone here are my linux versions:
rigel:/home/pdp/adb>fastboot --version
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
rigel:/home/pdp/adb>adb --version
Android Debug Bridge version 1.0.41
Version 31.0.2-android-tools
Installed as /usr/bin/adb[/FONT]
pdpantages said:
OK thank you again. I see now that I get this error when I flash from Linux, but not Windows 10....
In case it might help someone here are my linux versions:
rigel:/home/pdp/adb>fastboot --version
fastboot version 31.0.2-android-tools
Installed as /usr/bin/fastboot
rigel:/home/pdp/adb>adb --version
Android Debug Bridge version 1.0.41
Version 31.0.2-android-tools
Installed as /usr/bin/adb[/FONT]
Click to expand...
Click to collapse
What version is installed on your Windows system? If you don't get any "error" like that you are not using the latest version of fastboot. SDK Platform Tools
WoKoschekk said:
What version is installed on your Windows system? If you don't get any "error" like that you are not using the latest version of fastboot. SDK Platform Tools
Click to expand...
Click to collapse
Adb version 1.0.39
fastboot version 0.0.1-4500957
I don't like to use windows but I ran Motorola Rescue & Smart Assistant tool there... If I have to use windows again I will update it.