Database Develop

Help with moto x

I tried to manually flash back to stock 4.4.2 (so I can upgrade to 4.4.3) on my moto x but whenever I type the command "mfastboot flash system system.img" I get "invalid sparse image chunk count. The rest of the commands worked. Now my phone is stuck in the unlocked bootloader screen and I don't know what else to do. Help please?

Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app

serophia said:
Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Where would I get the latest version?

http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip

KidJoe said:
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
Click to expand...
Click to collapse
Thanks for the link. I used it and I still got the same error.

Make sure you are using the system.img from the correct firmware. Below is a link to the Moto model firmwares. Download the right one, unzip the files until you get to the .img files and use that system.img.
Motorola Firmwares

I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated

n0obpr0 said:
I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated
Click to expand...
Click to collapse
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.

samwathegreat said:
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.
Click to expand...
Click to collapse
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s

n0obpr0 said:
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s
Click to expand...
Click to collapse
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0

samwathegreat said:
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)

n0obpr0 said:
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)
Click to expand...
Click to collapse
That's what were here for to help others xD
Sent from my XT1053 using XDA Free mobile app

[Q] Need Nexus 6 boot.img

I messed up the boot.img file on my new Nexus 6. Will someone that has the phone pull the boot.img from their phone for me? Google doesn't yet have the Factory image up yet, so I am hoping that someone can pull it for me, so I can get up and running quicker than waiting for the Factory image to be uploaded.
I would be eternally grateful. Thank you so much.

joelbon said:
I messed up the boot.img file on my new Nexus 6. Will someone that has the phone pull the boot.img from their phone for me? Google doesn't yet have the Factory image up yet, so I am hoping that someone can pull it for me, so I can get up and running quicker than waiting for the Factory image to be uploaded.
I would be eternally grateful. Thank you so much.
Click to expand...
Click to collapse
what do you need me to do to pull it? I'm assuming an adb command?

joelbon said:
I messed up the boot.img file on my new Nexus 6. Will someone that has the phone pull the boot.img from their phone for me? Google doesn't yet have the Factory image up yet, so I am hoping that someone can pull it for me, so I can get up and running quicker than waiting for the Factory image to be uploaded.
I would be eternally grateful. Thank you so much.
Click to expand...
Click to collapse
I also need this lol.

I'd be happy to help, but I can't figure out how to pull it off my of my device. I found an article describing it, but it doesn't work.

loggainsd said:
what do you need me to do to pull it? I'm assuming an adb command?
Click to expand...
Click to collapse
It should be "adb pull (folder location)boot.img
I don't know the location of the boot.img, though. Can anyone please provide the proper command and the location? Thank you very much.

mtpease said:
I'd be happy to help, but I can't figure out how to pull it off my of my device. I found an article describing it, but it doesn't work.
Click to expand...
Click to collapse
i'm looking into it as well. Thank you for responding in the first place.
---------- Post added at 03:02 PM ---------- Previous post was at 02:55 PM ----------
joelbon said:
It should be "adb pull (folder location)boot.img
I don't know the location of the boot.img, though. Can anyone please provide the proper command and the location? Thank you very much.
Click to expand...
Click to collapse
I'm not finding anything myself sadly. The only thing ive found with adb is "adb backup" but that may copy personal data that we dont need.

joelbon said:
I messed up the boot.img file on my new Nexus 6. Will someone that has the phone pull the boot.img from their phone for me? Google doesn't yet have the Factory image up yet, so I am hoping that someone can pull it for me, so I can get up and running quicker than waiting for the Factory image to be uploaded.
I would be eternally grateful. Thank you so much.
Click to expand...
Click to collapse
I am curious what you did to mess it up? Without factory images available, it's not wise to mess around too much. Just curious.

livinginkaos said:
I am curious what you did to mess it up? Without factory images available, it's not wise to mess around too much. Just curious.
Click to expand...
Click to collapse
i goofed and tried to flash a recovery that i thought was for the 6 and it hasnr started since lol.

You will need to pull it from the partition it's on. Maybe you can check /fstab.shamu or something to see where it is?
Something like this is what you'd wanna do;
dd if=/dev/block/mmcblk0p13 of=/sdcard/boot.img
Replacing if=/dev/block/mmcblk0p13 with if=<boot.img partition>

almost certain you need root to pull the boot.img i could b wrong though.

djkinetic said:
almost certain you need root to pull the boot.img i could b wrong though.
Click to expand...
Click to collapse
Looks like you're about right.
You can follow the path to /dev/block/platform/<msmsomethingmaybe>/by-name and it'll show you the symlinks for boot, recovery, etc. (You could use something like root explorer, or just a shell and do ls -l in the by-name directory). For example on the nexus 5 I'd see that recovery is mmcblk0p20 and boot is mmcblk0p19. Wherever boot is, that's the one you want to pull.
But it looks like you can't read any of that stuff unless you have root privileges (could do it from a recovery, if there is one), which begs the question - where da factory image at google?

bbedward said:
Looks like you're about right.
You can follow the path to /dev/block/platform/<msmsomethingmaybe>/by-name and it'll show you the symlinks for boot, recovery, etc. (You could use something like root explorer, or just a shell and do ls -l in the by-name directory). For example on the nexus 5 I'd see that recovery is mmcblk0p20 and boot is mmcblk0p19. Wherever boot is, that's the one you want to pull.
But it looks like you can't read any of that stuff unless you have root privileges (could do it from a recovery, if there is one), which begs the question - where da factory image at google?
Click to expand...
Click to collapse
rough, o well hopefully they release those images soon. Having my new brick is nice and all but having a phone would be even better lol

Could someone pull the system as well? System dump...

david279 said:
Could someone pull the system as well? System dump...
Click to expand...
Click to collapse
it looks like google has released the factory image

Factory Image is now live - https://developers.google.com/android/nexus/images

livinginkaos said:
Factory Image is now live - https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
having trouble getting it to flash though. I'm using minimal adb and fastboot.

ravath said:
having trouble getting it to flash though. I'm using minimal adb and fastboot.
Click to expand...
Click to collapse
Me as well. Take a look at my thread. The flash went well until the end when I got this message:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(1322,0xa0b121d4) malloc: *** mach_vm_map(size=1681272832) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679592636 bytes
error: update package missing system.img
The package looks complete. Not sure what is missing.

Nucleonic said:
Me as well. Take a look at my thread. The flash went well until the end when I got this message:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(1322,0xa0b121d4) malloc: *** mach_vm_map(size=1681272832) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679592636 bytes
error: update package missing system.img
The package looks complete. Not sure what is missing.
Click to expand...
Click to collapse
i got the same error!

I just tried performing this process manually. The flashing process seems to fail when this command gets executed: fastboot update image-shamu-lrx210.zip

You guys need to flash the imgs individually via command line

[Q] Lolipop update bootloop assistance M7

My HTC One M7 (UK O2) was prompting me to update to the latest operating system.
Eventually I succumbed and installed the update. The phone is stock although I had unlocked the bootloader in preparation for experimenting with new operating systems (I'm a noob but curious about experimenting).
After installing, the phone rebooted and wound up on a screen with a red exclamation mark in a picture of a phone.
Sometimes it boots into the white Android startup screen, then shuts down and goes throught the whole startup cycle in a loop
I can get it into bootloader mode but none of the options presented there such as factory reset seem to do anything.
I don't think it's a hardwear problem as it seems to be a direct result of trying to install the update.
I would send it in for a warranty repair but I think that as I have unlocked then relocked the bootloader and it shows a 'relocked' flag then that voids the warranty, is that right?
Any help to sort this mess out would be appreciated.
Thanks
jimbobly

During unlocking bootloader some files deleted and during update ota checks file integrity so file found missing and update stops
So basically you have to restore that files
Or RUU update can be found here
But it will delete your all data photo songs contact apps so backup them
http://forum.xda-developers.com/showthread.php?t=3053944

Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks

jimbobly said:
Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks
Click to expand...
Click to collapse
this file: https://www.androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.

RUU
Seanie280672 said:
this file androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.
Click to expand...
Click to collapse
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks

jimbobly said:
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks
Click to expand...
Click to collapse
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca

alray said:
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca
Click to expand...
Click to collapse
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?

jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
First is the Md5 good?

RUU
jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
Also, when I try to unpack the zip file I get the message that the compressed file is empty!

jimbobly said:
Also, when I try to unpack the zip file I get the message that the compressed file is empty!
Click to expand...
Click to collapse
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.

alray said:
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.
Click to expand...
Click to collapse
Unfortunately, this is a bit advanced for me. How can I do this?

jimbobly said:
Unfortunately, this is a bit advanced for me. How can I do this?
Click to expand...
Click to collapse
http://www.winmd5.com/

alray said:
http://www.winmd5.com/
Click to expand...
Click to collapse
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?

jimbobly said:
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?
Click to expand...
Click to collapse
you need learn flashing RUU zip
reboot your phone to fastboot mode (same as you posted pic )
setup adb folder find miniSDK HERE and Here
Download htc fastboot HERE copy it adb folder rename it fastboot.exe (rename old fastboot to other name)
open adb folder put your RUU zip there rename it RUU.zip
connect your phone with PC
your phone should be locked/relocked
at adb folder open CMD (shift + right click)
type command below
Code:
fastboot devices
(will show attached phone to PC match serial no)
Code:
fastboot oem rebootRUU
(reboot phone to flashing ruu mode)
Code:
fastboot flash zip RUU.zip
(wait it will take time 8-10 minutes it will show successfully at last if not repeat same command immediately)
Code:
fastboot reboot-bootloader
( it is last and important step of flashing)
now see new version showing at phone details
reboot to system

RUU
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.

jimbobly said:
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.
Click to expand...
Click to collapse
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot

RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.

yatindroid said:
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot
Click to expand...
Click to collapse
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.

jimbobly said:
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
Click to expand...
Click to collapse
check md5
fastboot flash zip ( pressing tab will show files in fastboot folder press tab until you got ruu.zip )

Already checked the md5 and it's ok.
What is the best thing to do? Just try a new RUU?

Ruu urgent help needed

I NEED HELP!!!
When I try to flash an RUU that I have I get this error:
Invalid sparse file format at header magi
If I don't flash it my phone will not work, I tried to open up the android info.txt inside of the RUU but WinRAR told me that the zip was corrupted. I need to know what is going on and if anyone would be kind enough to find me a 7.18.161.21 RUU alternative to the one in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

Varss said:
I NEED HELP!!!
When I try to flash an RUU that I have I get this error:
Invalid sparse file format at header magi
If I don't flash it my phone will not work, I tried to open up the android info.txt inside of the RUU but WinRAR told me that the zip was corrupted. I need to know what is going on and if anyone would be kind enough to find me a 7.18.161.21 RUU alternative to the one in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
I got mine from here http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2 worked for me.

Varss said:
I NEED HELP!!!
When I try to flash an RUU that I have I get this error:
Invalid sparse file format at header magi
If I don't flash it my phone will not work, I tried to open up the android info.txt inside of the RUU but WinRAR told me that the zip was corrupted. I need to know what is going on and if anyone would be kind enough to find me a 7.18.161.21 RUU alternative to the one in this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
The ruu is not corrupted, its encrypted
You need to use htc's version of fastboot not the normal fastboot from the android sdk
Both these info are written in the OP of the ruu collection thread you have linked btw
As many in this thread, ask about zip corruption, zip are not corrupted they are encrypted and can't open normally , they need decryption check md5 and dont try to unzip them.
Click to expand...
Click to collapse
5. Also use the htc_fastboot.exe not the normal fastboot.exe
Click to expand...
Click to collapse

Flashing error

I just downloaded the official factory image from Google Developers. The file I am using is shamu-lmy48m-factory-336efdae. I am following the instructions on the site. Running flash-all.bat, the Bootloader and Radio flash OK. When it comes to flashing the System, I get the following:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778897872 bytes
error: update package missing system.img
Press any key to exit...
Any help is appreciated.

mojoehand said:
I just downloaded the official factory image from Google Developers. The file I am using is shamu-lmy48m-factory-336efdae. I am following the instructions on the site. Running flash-all.bat, the Bootloader and Radio flash OK. When it comes to flashing the System, I get the following:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778897872 bytes
error: update package missing system.img
Press any key to exit...
Any help is appreciated.
Click to expand...
Click to collapse
sure, flash-all doesnt work. you need to flash each part separately.

Going by what is in the batch file, I assume that the OS images are done individually the same way:
fastboot flash system system.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
There are five image files. Should they be done in any particular order?
Thanks.

mojoehand said:
Going by what is in the batch file, I assume that the OS images are done individually the same way:
fastboot flash system system.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
There are five image files. Should they be done in any particular order?
Thanks.
Click to expand...
Click to collapse
na, any order.

I had a similar issue, and updating my Android SDK Tools fixed it.

simms22 said:
na, any order.
Click to expand...
Click to collapse
I got everything flashed. Thanks for the help. Now to see if the LTE works any better.

mojoehand said:
I got everything flashed. Thanks for the help. Now to see if the LTE works any better.
Click to expand...
Click to collapse
you can always try out all the different n6 radios. some work better for others than newer radios.