Database Develop

Will I be forever stuck at 4.2.2 if I cant flash recovery?

I have tried everything I have read on here and I cant seem to flash recovery. I used pwnmymoto to gain root when I first received my moto x. When the camera update came I thought I unrooted and flashed back to stock becasue I was able to get the OTA. Yesterday I could not install the OTA 4.4 because it gave me a error sign. I tried to flash recovery using fastboot but everytime now matter what I do this shows up:
colins-air:Android Tools colinj22$ ./fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.798s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.848s
colins-air:Android Tools colinj22$
Can someone please help me. I am fairly new to fastboot and I am on a Mac and I have read everything in these threads and nothing seems to help. Can I erase everything and somehow start from scratch?
Thank you all!

colinj22 said:
I have tried everything I have read on here and I cant seem to flash recovery. I used pwnmymoto to gain root when I first received my moto x. When the camera update came I thought I unrooted and flashed back to stock becasue I was able to get the OTA. Yesterday I could not install the OTA 4.4 because it gave me a error sign. I tried to flash recovery using fastboot but everytime now matter what I do this shows up:
colins-air:Android Tools colinj22$ ./fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.798s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.848s
colins-air:Android Tools colinj22$
Can someone please help me. I am fairly new to fastboot and I am on a Mac and I have read everything in these threads and nothing seems to help. Can I erase everything and somehow start from scratch?
Thank you all!
Click to expand...
Click to collapse
try using a different fastboot besides the one you are using. also make sure you are trying to flash the right FW version. you can't downgrade FW so it needs to be the FW version that is currently on the device.
try the second link in the OP of this thread for a different fastboot
http://forum.xda-developers.com/showthread.php?t=2489249

Flashing recovery requires a unlocked boot loader, you're obviously on Verizon and unless you have a DE moto you can't flash recovery due to your boot loader being locked
Sent on my Moto X

Incorrect^
Sent from my XT1060 using Tapatalk

[Q] soft bricked verizon non-dev moto x

I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.

slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2635366

slappydj1 said:
I accidentally flashed the 4.4.2 bootloader and now I cant boot my phone, access recovery or anything. Im stuck in fastboot mode. It says Partition (boot) Security Version Downgraded. I need help because Ive spent hours trying to fix this.
Click to expand...
Click to collapse
Are you still able to enter the Bootloader menu?

jpd_ said:
Are you still able to enter the Bootloader menu?
Click to expand...
Click to collapse
yes, I just cant boot into recovery or android.

slappydj1 said:
yes, I just cant boot into recovery or android.
Click to expand...
Click to collapse
Go ahead and flash the stock recovery img then follow the instructions from here:
http://forum.xda-developers.com/showthread.php?t=2639102
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Very helpful link here as well on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=2603358
If you made a back up through TWRP, you can try restoring your phone from there too.

jpd_ said:
Also, they may be posting the OTA specifically made for verizon soon:
http://support.verizonwireless.com/dam/support/pdf/system_update/moto-x.pdf
Click to expand...
Click to collapse
The Verizon OTA is out. That is what got him in the situation he is in.

I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?

slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
They generally seem to show up 1 week to 1 month from when the OTA is released.

slappydj1 said:
I tried flashing the recovery image from 4.4 and i got this:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.963s
I think the only hope for me is a factory image of 4.4.2. Based on the past, when do you think it will get released?
Click to expand...
Click to collapse
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.

Cozume said:
That is because you need to use mfastboot, not fastboot.
mfastboot.exe
fastboot can't handle file sizes that large; mfastboot can.
Click to expand...
Click to collapse
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)

slappydj1 said:
Just tried it, got this message:
sending 'recovery' (10240 KB)... OKAY [ 0.876s]
writing 'recovery'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?

Cozume said:
If you are on the 4.4.2 bootloader, I don't think you can use the 4.4 recovery.
http://forum.xda-developers.com/showthread.php?t=2635366
Also what are you doing to try to boot into recovery?
Click to expand...
Click to collapse
I tried to boot into recovery using the fastboot menu on the phone.

slappydj1 said:
I tried to boot into recovery using the fastboot menu on the phone.
Click to expand...
Click to collapse
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?

Cozume said:
So you hold the Volume Down + Power to get into fastboot menu and then you hit Volume Down to highlight Recovery and then you hit Volume Up to select Recovery. Then you get the Android on its back with the red triangle. Then you Hold the Volume Up + Volume Down for about 5 seconds and press the Power button once. This is what you did? What does it do?
Click to expand...
Click to collapse
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed

slappydj1 said:
I can get to the fastboot menu fine, it just doesnt enter recovery. I dont get the android with the red triangle, it just shows the moto boot logo and goes back into fastboot mode with this message :
Partition (recovery) Security Version Downgraded
Boot up failed
Click to expand...
Click to collapse
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.

Cozume said:
Ok, got it. I think the problem is that you can't have a 4.4.2 bootloader with a 4.4 recovery. So what it is telling you is that your recovery is downgraded because it is the version below your bootloader. I think you need the 4.4.2 recovery with the 4.4.2 bootloader. And there is no way to downgrade the 4.4.2 bootloader.
I read through the threads and I don't see where you can have the newer bootloader with the older recovery. You can have the older system with the newer bootloader.
I will post that question by itself and see if anyone can tell me if I am right or wrong on that.
Click to expand...
Click to collapse
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)

slappydj1 said:
I just tried flashing the system with mfastboot and got this message:
sending 'system' (262144 KB)... OKAY [ 17.113s]
writing 'system'... INFOPreflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?

Cozume said:
Ok, sorry I am getting confused. It is the 4.4.2 system that will work with the 4.4 bootloader.
So I think the bottom line from all I have read is that you need the 4.4.2 stock recovery.img file.
How did you get to this point again? You took the OTA but for some reason it only upgraded the bootloader?
Click to expand...
Click to collapse
So Ill have to wait until the factory image is released?

slappydj1 said:
So Ill have to wait until the factory image is released?
Click to expand...
Click to collapse
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.

Cozume said:
I don't see any other option if the 4.4.2 bootloader won't work with the 4.4 recovery. I believe that is what those error messages are saying.
So what exactly did you do that resulted in this situation? Explaining that might be helpful to others who may be able to help you.
Click to expand...
Click to collapse
I was going to do a factory reset using fastboot, and I flashed the gpt.bin. after that I could not flash anything. Later I learned that wasnt the factory image but the OTA update, so I realized I messed up then.

[Q] No Red Text Firmware 7.17.1540.7 Solved

Has anyone done a no red text version of the firmware for 7.17.1540.7? This is from the current dev edition release of lollipop. At this point I can't seem to find it if someone has done one already.

I have done one, but not tested it yet. If you want to test it, go ahead but I'm not responsible if this brick your phone.
If you want to test it, report if its working fine, then I'll upload it to my thread and give you credit for testing it. You can compare the origianl hboot with this one with an hex editing tool to double check if you want.
Edit:
7.17.1540.7 no red text hboot available here: http://forum.xda-developers.com/htc-one/general/stock-rom-reset-developer-edition-t2915170

Thanks! I tested and it works. I did verify it against my copy of the clean hboot here and it checked out and based on instruction I saw elsewhere looked fine so I took a try. Here is the zip pack I used. It only updates the hboot (I've seen others doing a full pack) so it is best run on top after already having firmware 7.17.1540.7.
Please note it may appear to get stuck at about 75%. As long as it says OKAY at the end and does not indicate it failed then it should be ok to reboot. It got stuck for me on my screen so I had to fastboot reboot-bootloader after. From my understanding that last 25% is actually the reboot stage which doesn't happen automatically so here you do get a chance to check the result before rebooting manually.
For those that do download from this post...
If it says FAILED at the end DO NOT reboot the device. Instead try to flash again or flash a stock hboot. If you reboot at this point there is a very high chance it will not boot and become a lightweight doorstop. Let's not have that happen ok?
Trial run (serial is censored):
Code:
C:\Users\User\Desktop>fastboot flash zip 7.17.1540.7_no_red.zip
target reported max download size of 1514139648 bytes
sending 'zip' (603 KB)...
OKAY [ 0.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.211s]
finished. total time: 2.461s
C:\Users\User\Desktop>fastboot devices
HT42CW000000 fastboot
C:\Users\User\Desktop>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.038s

signes or unsigned firmware?
Hi,
I'm sorry for the noob question but what's the difference of a signed and unsigned firmware?

shinji257 said:
Thanks! I tested and it works. I did verify it against my copy of the clean hboot here and it checked out and based on instruction I saw elsewhere looked fine so I took a try. Here is the zip pack I used. It only updates the hboot (I've seen others doing a full pack) so it is best run on top after already having firmware 7.17.1540.7.
Please note it may appear to get stuck at about 75%. As long as it says OKAY at the end and does not indicate it failed then it should be ok to reboot. It got stuck for me on my screen so I had to fastboot reboot-bootloader after. From my understanding that last 25% is actually the reboot stage which doesn't happen automatically so here you do get a chance to check the result before rebooting manually.
For those that do download from this post...
If it says FAILED at the end DO NOT reboot the device. Instead try to flash again or flash a stock hboot. If you reboot at this point there is a very high chance it will not boot and become a lightweight doorstop. Let's not have that happen ok?
Trial run (serial is censored):
Click to expand...
Click to collapse
Thanks for reporting, will remove the file from this thread and post it I'm my collection thread and also in a firmware.zip

RucaNebas said:
Hi,
I'm sorry for the noob question but what's the difference of a signed and unsigned firmware?
Click to expand...
Click to collapse
Signed firmware is official HTC firmware signed with their private (encrypted) key. S-ON phones can only flash signed firmware. Firmware to flash must be the same version or newer (higher) than whats already running on the phone and bootloader must be locked/relocked.
S-OFF phone can flash unsigned firmware package, like this one, with a modded bootloader (hboot), no matters what the version is can be done with an locked/unlocked/relocked bootloader.

Unable to Install TWRP from Fastboot Mode

Hello Guys im attempting to install TWRP 3.0.2 on my Moto X 2nd Gen 2014 with Android 6.0 Official but im getting an error in my command prompt. I have already attempt to request and an unlock code for unlocking the bootloader but motorolas site state my phone is not authorize for unlocking it. Does my phone need to have boot loader unlocked to be able to follow this step? Im pretty much attempting to install this recover to be able to root following this method: http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
C:\Users\****\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery C:\Users\****\AppData\Local\Android\sdk\platform-tools\twrp-3.0.2-1-victara.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (9160 KB)...
OKAY [ 0.329s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.356s
Click to expand...
Click to collapse

Yes, the bootloader needs to be unlocked to install a custom recovery (which is stated prior to the first step in the thread you mentioned). At one time there was an"unofficial" bootloader unlock that you might look into.

Pretty sure I just bricked my wife's G5S Plus

First let me start by saying, I KNOW...
This all started when her signal started to jump around. She was unable to access 4g or anything. I had Pixel Perfect (or something like that) on it. I was going back to stock so it just 'worked.' Stupidly I grabbed the G5's firmware, no G5S. Strangely I was able to flash everything (ugh!). This has result in a lot of pain for me. I am now unable to flash the proper firmware, no matter how hard I try.
I can reflash bootloader, boot, recovery. But i am unable to flash system, oem or GPT (which I think is required here).
Flashing GPT gives me:
HTML:
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.034s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.122s
Flashing oem gives me a failed validation, but a "image is too large" on the screen. Booting into recovery works but I'm unable to do anything as there is no file system. The SD Card also isn't working.
If anyone has some ideas, I'd appreciate it. I'm thinking I could possibly put a external SD card in but since I'm unable to write gpt, I think I'm screwed.
Please...anyone got an idea?

natalic said:
First let me start by saying, I KNOW...
This all started when her signal started to jump around. She was unable to access 4g or anything. I had Pixel Perfect (or something like that) on it. I was going back to stock so it just 'worked.' Stupidly I grabbed the G5's firmware, no G5S. Strangely I was able to flash everything (ugh!). This has result in a lot of pain for me. I am now unable to flash the proper firmware, no matter how hard I try.
I can reflash bootloader, boot, recovery. But i am unable to flash system, oem or GPT (which I think is required here).
Flashing GPT gives me:
target max-sparse-size: 256MBsending 'partition' (45 KB)...OKAY [ 0.034s]writing 'partition'...(bootloader) Validating 'gpt.default.xml'(bootloader) Security version downgrade(bootloader) Image primary_gpt failed validation(bootloader) Preflash validation failed(bootloader) Cancelling 'gpt.default.xml'FAILED (remote failure)finished. total time: 0.122s
Flashing oem gives me a failed validation, but a "image is too large" on the screen. Booting into recovery works but I'm unable to do anything as there is no file system. The SD Card also isn't working.
If anyone has some ideas, I'd appreciate it. I'm thinking I could possibly put a external SD card in but since I'm unable to write gpt, I think I'm screwed.
Please...anyone got an idea?
Click to expand...
Click to collapse
Flash newest software version
61-5

Adi5 said:
Flash newest software version
61-5
Click to expand...
Click to collapse
Got a link? I'm using:
NPSS26.116-45-5_cid50
I'm panicing here

https://androidfilehost.com/?fid=673956719939831738

Adi5 said:
https://androidfilehost.com/?fid=673956719939831738
Click to expand...
Click to collapse
This will be new enough to supercede the one from the G5's firmware since that is 137 vs 116?

natalic said:
This will be new enough to supercede the one from the G5's firmware since that is 137 vs 116?
Click to expand...
Click to collapse
Flash this one from afh should be flashed without error

Adi5 said:
Flash this one from afh should be flashed without error
Click to expand...
Click to collapse
I REALLY hope so

adi5 said:
flash this one from afh should be flashed without error
Click to expand...
Click to collapse
you saved me man...i am so thankful! It worked!!!

Hey, I have exactly the same problem but no luck with flashing 61-5. I can access fastboot from a PC but unfortunately nothing showing on the screen.