Database Develop

Flashing System : "data length is too large" problem

I have been trying to flash an old GB image from an RUU provided in the Shipped ROMS thread.
I flashed my boot and recovery OK, but flashed system failed somehow. Now, am stuck on HTC logo. When I flash my system image, it gives an error:
sending 'system' (917504 KB)... FAILED (remote: data length is too large)
Please help.

roc_vader said:
I have been trying to flash an old GB image from an RUU provided in the Shipped ROMS thread.
I flashed my boot and recovery OK, but flashed system failed somehow. Now, am stuck on HTC logo. When I flash my system image, it gives an error:
sending 'system' (917504 KB)... FAILED (remote: data length is too large)
Please help.
Click to expand...
Click to collapse
Which recovery and boot did you flash? Also this post should have been created in the general section.
Sent from my HTC PH39100 using XDA

megatronisabeast said:
Which recovery and boot did you flash? Also this post should have been created in the general section.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
Sorry for wrong section. Maybe a moderator can move this to General section plz
Also, I flashed the RUU_Holiday_Cingular_US_1.63.502.4 from this http://forum.xda-developers.com/showthread.php?t=1338919 thread

roc_vader said:
Sorry for wrong section. Maybe a moderator can move this to General section plz
Also, I flashed the RUU_Holiday_Cingular_US_1.63.502.4 from this http://forum.xda-developers.com/showthread.php?t=1338919 thread
Click to expand...
Click to collapse
What rom were you coming from? Were you already on gingerbread or on ics?

megatronisabeast said:
What rom were you coming from? Were you already on gingerbread or on ics?
Click to expand...
Click to collapse
No, I had not upgraded to ICS. I was using stock GB with a modified kernel

First thing you shouldve done was relock the bootloader to flash back to stock....hopefully you didnt bork your phone.....IF you can get into hboot relock the bootloader and re run the ruu
WC

http://forum.xda-developers.com/showthread.php?t=1416836
Go to the second post and follow all of the steps. It should get you back to where you need to be.

Guys, I did see that post earlier, but the problem is I cant boot my phone. Am stuck on HTC logo while booting(I mentioned it in my first post). Now, how do I run the RUU? I can get into HBOOT.
Also, fastboot update rom.zip gave following error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.83.0014
Baseband Version.....: N/A
Serial Number........:
--------------------------------------------
sending 'boot' (3580 KB)... OKAY [ 0.796s]
writing 'boot'... OKAY [ 1.202s]
sending 'recovery' (6438 KB)... OKAY [ 1.312s]
writing 'recovery'... OKAY [ 2.280s]
sending 'system' (917504 KB)... FAILED (remote: data length is too large)
finished. total time: 5.622s

Does the bootloader say locked or unlocked? IF locked connect phone to computer with fastboot enabled and run the ruu. If it says unlocked you have to run fastboot oem lock and see if it will lock....IF it does lock and says relocked then follow " IF locked connect phone to computer with fastboot enabled and run the ruu"
WC
roc_vader said:
Guys, I did see that post earlier, but the problem is I cant boot my phone. Am stuck on HTC logo while booting(I mentioned it in my first post). Now, how do I run the RUU? I can get into HBOOT.
Also, fastboot update rom.zip gave following error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.83.0014
Baseband Version.....: N/A
Serial Number........:
--------------------------------------------
sending 'boot' (3580 KB)... OKAY [ 0.796s]
writing 'boot'... OKAY [ 1.202s]
sending 'recovery' (6438 KB)... OKAY [ 1.312s]
writing 'recovery'... OKAY [ 2.280s]
sending 'system' (917504 KB)... FAILED (remote: data length is too large)
finished. total time: 5.622s
Click to expand...
Click to collapse

Wild Child said:
Does the bootloader say locked or unlocked? IF locked connect phone to computer with fastboot enabled and run the ruu. If it says unlocked you have to run fastboot oem lock and see if it will lock....IF it does lock and says relocked then follow " IF locked connect phone to computer with fastboot enabled and run the ruu"
WC
Click to expand...
Click to collapse
It was relocked. And the thread you mentioned did not seem to work. But following thing worked:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Anyways, Am on ICS now!!!! Thnx a lot for ur help!!

Glad you are on ics. Thanks for sharing your steps!
Sent from my HTC PH39100 using XDA

The error reason?
Hi,
My BL is unlocked with htcdev.
I have the same when trying to flash with fastboot.
Can someone tell me whats the reason of the error?

Thanks
roc_vader said:
It was relocked. And the thread you mentioned did not seem to work. But following thing worked:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Anyways, Am on ICS now!!!! Thnx a lot for ur help!!
Click to expand...
Click to collapse
Yes Bro you are right it worked for me too happy right now wnjoy buddy live more have a good day .

If some one is still on this problem, I had the issue Where upon boot the device said "Decrption Unsucessful" so i thought i should give it a factory reset which the device also prompts to but can't since the Partitions are Corrupted or just a Partition in my case, So flashed TWRP 3.0.2.-0 [Older i know], tried to Wipe Data and Cache but couldn't, so thought i should give it a Full Flash, upon doing so i stumbled on many problems, like the one OP has here, others like 'Device Haulted" [The one you get when you try to update via a SDCard], so been wasting my brain cells since yesterday, So a thought struck to my mind "Did i try to Wipe the System and Data via TWRP?" [Actually you just need to wipe the Data Partition] , So tried again and it couldn't said [Couldn't mount data/] so Google and Struck on a Video by usmanalitoo [ youtube.com/watch?v=Rs4zcryNt5Y ] in which he said to Format the Data partition to ext2 then back to ext4 which did wonders, See the video yourself. if you can't flash or other stuff. Before you do other wierd **** to you innocent device.

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.

File system slow in recovery. Can't flash ROMS.

Hello!
Having a pretty big problem, as I am trying to help my girlfriend get her phone all recovered and usable again for her. On our HTC Ones, we both use Android Revolution HD and were updating to the latest (4.4 version). With my phone, the installation of TWRP 2.6.3.3, then the rom went completely fine.
On her phone, it is going terribly. I made one mistake and forgot to copy the ROM over to the device before I wiped her system, so I don't have the new file to flash. I attempted to flash the old ROM, which was sitting on her device, but it is extremely slow to the point of we waited about an hour or two and it never installed. I have attempted to sideload, but the file is copying much slower than expected. Heck, everything involving the filesystem is running slow, even data wipes! I tried a full system erase, so now I am at a position where we have no flashable ROMS on the device.
I have tried both adb push and adb sideload to send the file, and both never successfully complete, even after waiting hours.
Where do I go from here? Any idea why flashing roms and file system is running so slow?

Change USB port/cable/computer and try push/sideload again
sent from my mobile device

SaHiLzZ said:
Change USB port/cable/computer and try push/sideload again
sent from my mobile device
Click to expand...
Click to collapse
I tried this already. I know this is not the cause as installing a zip of a new rom literally takes about 2 hours to write to the system.
Even a fastboot flash recovery takes about 30 seconds on her device, tested with multiple cables on two macbook pros. My HTC One flashed normally in less than a second...

When I flashed recovery:
MacBookownloads limitin$ fastboot flash recovery recovery.img
sending 'recovery' (9184 KB)...
OKAY [ 1.333s]
writing 'recovery'...
OKAY [ 0.696s]
finished. total time: 2.029s
When I flashed her phone with the same recovery file (TWRP 2.6.3.3):
MacBookownloads limitin$ fastboot flash recovery recovery.img
sending 'recovery' (9948 KB)...
OKAY [ 1.450s]
writing 'recovery'...
OKAY [ 35.708s]
finished. total time: 37.158s
Same phone. Some hboot version. Only thing I had to do to hers first (I had done mine previously) was use revone to s-off her device, which was successful after a few attempts.

Restore Stock Recovery - Amazon Fire 7 5th Gen (Ford)

IF YOU PLAN ON INSTALLING ANY CUSTOM ROM CHECK THAT YOUR RECOVERY IS ACCESSABLE!!!
If you have lost access to your stock recovery on your Amazon Fire 7 5th Gen (Ford) for whatever reason I would highly recommend restoring your recovery before doing any further customization to your device. Without recovery you have absolutely nothing to fall back on if your device becomes inoperable. If you have tried flashing any type of custom recovery directly to your device its more then likely you have lost access to your stock recovery. Hopefully youv made it to this thread before it was too late and luckily its a pretty simple process to restore your access.
Before we begin you must have a working OS for this process to work. If your device will not successfully boot then you can not complete the steps necessary to restore access to your recovery.
First lets
• Download Fire 7 Stock Recovery Image https://app.box.com/s/tjju5dptvsmsfjienf37siip8j6ch7wo
• Download and install the Flashfire App http://download.chainfire.eu/950/FlashFire/FlashFire-v0.30-20160331135212.apk
Next we'll
• Open the Flashfire App and allow it root access
• Press the red "+" button and select "Flash Firmware Package"
• Browse to the folder containing the Fire 7 Stock Recovery Image you previously downloaded and select it then press the "√" in the upper right corner
• Change Reboot option from "Normal" to "Recovery"
• Press the "FLASH" then "OK"
• Flashfire will reboot into recovery when its complete (Usually only takes a couple mins but its possible it may run for more)
It is also possible to restore access to recovery using Flashify
• Download and install Flashify
http://www.apkmirror.com/apk/christian-gollner/flashify/
• Press "Select Recovery Image" then choose file
• Browse to the Fire 7 Stock Recovery Image you downloaded earlier, select it and choose "Yup"
• Once complete reboot to recovery to confirm
That's it now you're back in action!!!

Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs

sd_shadow said:
Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Thought about that this morning as well. If no one else confirms before I get off work here shortly I will try then. (Especially like to see someone with a hard brick attempt it) In theory it seems it should work since the image seems to carry the signature from Amazon. Well at least that's what I picked up from researching for a fix to restore access to recovery on two of my fires.

Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
Click to expand...
Click to collapse
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse

knicknut said:
Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs

sd_shadow said:
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse

knicknut said:
used ?
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse
yes, my bad
Sent from my XT1080 using XDA Labs

Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?

vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
Unfortunately I don't believe so. We need a key to unlock the actual ability to flash via Fastboot. As far as I know at least

vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
I suspect that capability is coming (foundation is in v0.32) but probably not for this device due to fastboot restrictions I posed by Amazon.

Sorry cross posted removed

Robin Son said:
stuck with 5.1 will not boot to stock recovery
was going to try using fastboot with 5.3.1 stock img.file but can't find one
TGT123 super tool will reboot my A-fire but will not install stock recovery
O yeah and i lost root and no playstore
Anyone had this problem and fixed???
Click to expand...
Click to collapse
Please don't cross post. Answered here: http://forum.xda-developers.com/ama...stom-rom-fireos-5-3-1-0-t3418541/post70006008