Bricked Moto X - Partition (boot) Security Version Downgraded

Status
Not open for further replies.

Jack881

Senior Member
Aug 2, 2014
58
1
0
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

Senior Member
Aug 2, 2014
58
1
0
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
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...
 

samwathegreat

Senior Member
Apr 17, 2010
2,097
1,843
0
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...
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:
 
  • Like
Reactions: Nandim and Jack881

Jack881

Senior Member
Aug 2, 2014
58
1
0
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:
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...
 

samwathegreat

Senior Member
Apr 17, 2010
2,097
1,843
0
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...
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.
 
  • Like
Reactions: Jack881

Jack881

Senior Member
Aug 2, 2014
58
1
0
I tried, but when I type the device still write Fastboot reason:flash failure. Any idea? Maybe I did something wrong. Thank you.
 

Jack881

Senior Member
Aug 2, 2014
58
1
0
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:
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.
 

samwathegreat

Senior Member
Apr 17, 2010
2,097
1,843
0
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.
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.
 
  • Like
Reactions: Jack881

Jack881

Senior Member
Aug 2, 2014
58
1
0
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.
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...
 

samwathegreat

Senior Member
Apr 17, 2010
2,097
1,843
0
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...
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.
 
  • Like
Reactions: Jack881

Jack881

Senior Member
Aug 2, 2014
58
1
0
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...
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?
 

samwathegreat

Senior Member
Apr 17, 2010
2,097
1,843
0
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?
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.
 
Last edited:
  • Like
Reactions: Jack881

Jack881

Senior Member
Aug 2, 2014
58
1
0
Taking timgree

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.
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.
 

samwathegreat

Senior Member
Apr 17, 2010
2,097
1,843
0
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.
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.
 
  • Like
Reactions: Jack881

Jack881

Senior Member
Aug 2, 2014
58
1
0
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.
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
 

samwathegreat

Senior Member
Apr 17, 2010
2,097
1,843
0
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
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
 
  • Like
Reactions: Jack881

Jack881

Senior Member
Aug 2, 2014
58
1
0
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
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
 

samwathegreat

Senior Member
Apr 17, 2010
2,097
1,843
0
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
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:
 

Jack881

Senior Member
Aug 2, 2014
58
1
0
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:
No, gosh! maybe I have to repeat everything? now I have Partition (boot) Security version Downgraded Fastboot reason: Boot failure
 

samwathegreat

Senior Member
Apr 17, 2010
2,097
1,843
0
No, gosh! maybe I have to repeat everything? now I have Partition (boot) Security version Downgraded Fastboot reason: Boot failure
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.
 
Status
Not open for further replies.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone