Flashing error - Nexus 6 Q&A, Help & Troubleshooting

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.

Related

[Q] [TOOL] Help BhunDven

Hey guys I'm mostly a lurker not too much of a poster I would respond to "BHUNDVEN"'s thread ([TOOL] Moto X FXZ Flashing Script (100% back to stock) [10/03/2013]) over on the OG Android development sections but alas my "Post count" is too low.
I keep getting this when trying to run the final command "moto-x-flash [insert .xml file]"
Any help? Thanks!
Last login: Thu Nov 7 00:31:17 on ttys001
jeffreys-mbp:~ jeffreymarshall$ cd desktop/moto-x-tools-0.2.0
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ sudo python setup.py install
running install
running build
running build_py
running build_scripts
running install_lib
running install_scripts
changing mode of /usr/local/bin/moto-x-flash to 755
running install_egg_info
Removing /Library/Python/2.7/site-packages/moto_x_tools-0.2.0-py2.7.egg-info
Writing /Library/Python/2.7/site-packages/moto_x_tools-0.2.0-py2.7.egg-info
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ moto-x-flash VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml
Traceback (most recent call last):
File "/usr/local/bin/moto-x-flash", line 24, in <module>
tree = ET.parse(firmware_xml)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 656, in parse
parser.feed(data)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
self._raiseerror(v)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 1, column 2
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$
I'm not to sure I have the python pkg installed correctly. Had to use the "sudo" command to get it to take.
AceBoonKoon said:
I'm not to sure I have the python pkg installed correctly. Had to use the "sudo" command to get it to take.
Click to expand...
Click to collapse
i cant help you with that toolkit as i don't use it. But if you are merely trying to flash your phone to stock then find the rsd back to 100% stock thread and do that. Just as simple as any other tool you can find.
But honestly, if you spent say 4 hours reading and installing things for adb/fastboot stuff, you won't ever need one of those tools and you won't ever again spend countless hours trying to figure out how to get some tool someone created to work correctly for your phone. The simple sometimes becomes the most time consuming.
Once you figure out a few commands and realize whats going on, you will understand how simple all of that stuff is, and then will be confused as to why anyone ever created a tool for that simple task. Not bashing on the people that created the toolkit, that helps hundreds of people out I'm sure that dont feel like reading a little bit.
memapp can
I would but this [TOOL] is for mac.
No windows machine ala no rsdlite. I did however see that I needed to rename the .xml file to a .zip file ... Then extract the contents and move them over to the moto-x-tools folder and tried flashing it that way but got a "Command not found" error.
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ moto-x-flash VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml
Running: fastboot oem fb_mode_set
/bin/sh: fastboot: command not found
Running: fastboot flash partition gpt.bin
/bin/sh: fastboot: command not found
Running: fastboot flash motoboot motoboot.img
/bin/sh: fastboot: command not found
Running: fastboot flash logo logo.bin
/bin/sh: fastboot: command not found
Running: fastboot flash boot boot.img
/bin/sh: fastboot: command not found
Running: fastboot flash recovery recovery.img
/bin/sh: fastboot: command not found
Running: fastboot flash system system.img
/bin/sh: fastboot: command not found
Running: fastboot flash modem NON-HLOS.bin
/bin/sh: fastboot: command not found
Running: fastboot erase modemst1
/bin/sh: fastboot: command not found
Running: fastboot erase modemst2
/bin/sh: fastboot: command not found
Running: fastboot flash fsg fsg.mbn
/bin/sh: fastboot: command not found
Running: fastboot erase cache
/bin/sh: fastboot: command not found
Running: fastboot erase userdata
/bin/sh: fastboot: command not found
Running: fastboot erase customize
/bin/sh: fastboot: command not found
Running: fastboot erase clogo
/bin/sh: fastboot: command not found
Running: fastboot oem config carrier vzw
/bin/sh: fastboot: command not found
Running: fastboot oem fb_mode_clear
/bin/sh: fastboot: command not found
Flashing was successful!
Running: fastboot reboot
/bin/sh: fastboot: command not found
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$
jayboyyyy said:
i cant help you with that toolkit as i don't use it. But if you are merely trying to flash your phone to stock then find the rsd back to 100% stock thread and do that. Just as simple as any other tool you can find.
But honestly, if you spent say 4 hours reading and installing things for adb/fastboot stuff, you won't ever need one of those tools and you won't ever again spend countless hours trying to figure out how to get some tool someone created to work correctly for your phone. The simple sometimes becomes the most time consuming.
Once you figure out a few commands and realize whats going on, you will understand how simple all of that stuff is, and then will be confused as to why anyone ever created a tool for that simple task. Not bashing on the people that created the toolkit, that helps hundreds of people out I'm sure that dont feel like reading a little bit.
Click to expand...
Click to collapse
In response to the fastboot commands suggestion - I have already tried using the adb/fastboot methods didn't work. Did a search for people with similar issues and found that it has something about it being on a mac or some other nonsense. That's the reason for the [TOOL] I think. It's a workaround.
AceBoonKoon said:
In response to the fastboot commands suggestion - I have already tried using the adb/fastboot methods didn't work. Did a search for people with similar issues and found that it has something about it being on a mac or some other nonsense. That's the reason for the [TOOL] I think. It's a workaround.
Click to expand...
Click to collapse
don't know where you fastboot is but i believe its trying to call it and its not in the directory that the cmd is pointed to.
Ok I've went down the list and manually flashed each command.
When I get to ./fastboot flash system system.img
I keep getting this error
"Mismatched PIV partition name for system
Invalid PIV image: system"
I can successfully flash all other commands except this one. I went into the .xml file and deleted the "getvar" portion already. Any help?
AceBoonKoon said:
Ok I've went down the list and manually flashed each command.
When I get to ./fastboot flash system system.img
I keep getting this error
"Mismatched PIV partition name for system
Invalid PIV image: system"
I can successfully flash all other commands except this one. I went into the .xml file and deleted the "getvar" portion already. Any help?
Click to expand...
Click to collapse
not sure about the error sorry. also you might want to click on the reply button so it appears as a notification for me or i might not ever look at the thread again if i forget, jsut fyi.
are you sure you are using the right fxz for your phone? also when you run manual commands in fastboot, the xml file doesn't matter. that file is just there for rsd and other programs to use (it is basically just a script of commands that gets called on by programs to run). i don't know if you are typing "./fastboot" instead of just "fastboot" in cmd prompt but you only need to type "fastboot flash system system.img"
jayboyyyy said:
not sure about the error sorry. also you might want to click on the reply button so it appears as a notification for me or i might not ever look at the thread again if i forget, jsut fyi.
are you sure you are using the right fxz for your phone? also when you run manual commands in fastboot, the xml file doesn't matter. that file is just there for rsd and other programs to use (it is basically just a script of commands that gets called on by programs to run). i don't know if you are typing "./fastboot" instead of just "fastboot" in cmd prompt but you only need to type "fastboot flash system system.img"
Click to expand...
Click to collapse
Thanks for the fyi didn't know. I've tried flashing both fxz's for my phone and nothing both keep saying the same error Mismatched PIV. Thanks for the schooling on the xml file didn't know that. Going to keep searching.
AceBoonKoon said:
Thanks for the fyi didn't know. I've tried flashing both fxz's for my phone and nothing both keep saying the same error Mismatched PIV. Thanks for the schooling on the xml file didn't know that. Going to keep searching.
Click to expand...
Click to collapse
both? you can't just flash both like that. are you sure you are doing all of this right? one for your phone is a different FW version than the other one. This could be why you are getting this mismatch. Also, you would need to unzip and move all of the files to the directory that your fastboot is in. Then if you were trying to flash a different fxz, you would need to remove the old files from that directory and replace them with the new fxz files.
Finally, the commands to run manually will be found at this link. http://forum.xda-developers.com/showthread.php?p=46712761&highlight=flash+stock#post46712761
jayboyyyy said:
both? you can't just flash both like that. are you sure you are doing all of this right? one for your phone is a different FW version than the other one. This could be why you are getting this mismatch. Also, you would need to unzip and move all of the files to the directory that your fastboot is in. Then if you were trying to flash a different fxz, you would need to remove the old files from that directory and replace them with the new fxz files.
Finally, the commands to run manually will be found at this link. http://forum.xda-developers.com/showthread.php?p=46712761&highlight=flash+stock#post46712761
Click to expand...
Click to collapse
Now it's saying that can't downgrade when trying to flash the bootloader and it still won't flash the system.img same error.
I think I messed up when I tried to flash the "newer" FXZ. To see if I could get it to go through.
AceBoonKoon said:
I think I messed up when I tried to flash the "newer" FXZ. To see if I could get it to go through.
Click to expand...
Click to collapse
ya you can't flash the old one anymore. it will fail. you should be able to flash the new system img though. just make sure you are using the right one for your device. couldn't find anything on the internet for that particular error. So not many people run into it. It has to be something you are doing. try redownloading the fxz (the correct new fxz for your phone) and then start over from the beginning of the code and flash all the new stuff.
jayboyyyy said:
ya you can't flash the old one anymore. it will fail. you should be able to flash the new system img though. just make sure you are using the right one for your device. couldn't find anything on the internet for that particular error. So not many people run into it. It has to be something you are doing. try redownloading the fxz (the correct new fxz for your phone) and then start over from the beginning of the code and flash all the new stuff.
Click to expand...
Click to collapse
The fastboot flashes through every command flawlessly all EXCEPT the system.img. Keeps saying the bootloader preauthorization failed. I've flashed it every which way, straight through, at random, only the recovery, bootloader, and system.img. Can't get it to play nice.
I did read somewhere that mac fastboot had an issue with how large the system file was for VZW's moto x and couldn't flash it. Someone said that rsd lite breaks it up into smaller pieces in order to get it to flash. I wonder if there is a manual way to do this?
AceBoonKoon said:
The fastboot flashes through every command flawlessly all EXCEPT the system.img. Keeps saying the bootloader preauthorization failed. I've flashed it every which way, straight through, at random, only the recovery, bootloader, and system.img. Can't get it to play nice.
I did read somewhere that mac fastboot had an issue with how large the system file was for VZW's moto x and couldn't flash it. Someone said that rsd lite breaks it up into smaller pieces in order to get it to flash. I wonder if there is a manual way to do this?
Click to expand...
Click to collapse
forgot you were using a mac. just throw that thing away and get a big boy computer. lol. jk. don't need to start hearing a bunch of people chime in but here is a link to a fastboot file that splits it up for you. don't know if it will help or not.
http://forum.xda-developers.com/showthread.php?t=2489249
jayboyyyy said:
forgot you were using a mac. just throw that thing away and get a big boy computer. lol. jk. don't need to start hearing a bunch of people chime in but here is a link to a fastboot file that splits it up for you. don't know if it will help or not.
http://forum.xda-developers.com/showthread.php?t=2489249
Click to expand...
Click to collapse
I went and downloaded the "motofastboot-olympus" file and extracted the Linux fastboot file and placed in my folder replacing the current fastboot and now when I try to run a fastboot command I get "./fastboot: cannot execute binary file" I've tried the "Darwin" fastboot as well same thing.
AceBoonKoon said:
I went and downloaded the "motofastboot-olympus" file and extracted the Linux fastboot file and placed in my folder replacing the current fastboot and now when I try to run a fastboot command I get "./fastboot: cannot execute binary file" I've tried the "Darwin" fastboot as well same thing.
Click to expand...
Click to collapse
i see that you actually searched for this answer because i went to that mac thread i remembered seeing to see if there was a solution there. so you can just factory reset the device right? you don't need the system.img there to factory reset i don't think. just try a factory reset.
just found this. try downloading the nexus for stuff. pull the fastboot-mac file or whatever it is out of it. run all your commands with the "./fastboot-mac" and see if it works now.
jayboyyyy said:
i see that you actually searched for this answer because i went to that mac thread i remembered seeing to see if there was a solution there. so you can just factory reset the device right? you don't need the system.img there to factory reset i don't think. just try a factory reset.
Click to expand...
Click to collapse
I've been searching all day for all of these answers. Just thought it would help to ask as well.
I found the solution to my problem. For any of those who are having trouble flashing back to stock ON A MAC It will not flash because the system.img file is TOO BIG you need the CORRECT version of Moto-Fastboot. Here's the link that you can download and place it in your "Fastboot" folder. http://forum.xda-developers.com/showthread.php?t=1138092
I suggest you hold on to that fastboot for future flashes/return to stock. Thank you for your help jayboyyyy!
AceBoonKoon said:
I've been searching all day for all of these answers. Just thought it would help to ask as well.
I found the solution to my problem. For any of those who are having trouble flashing back to stock ON A MAC It will not flash because the system.img file is TOO BIG you need the CORRECT version of Moto-Fastboot. Here's the link that you can download and place it in your "Fastboot" folder. http://forum.xda-developers.com/showthread.php?t=1138092
I suggest you hold on to that fastboot for future flashes/return to stock. Thank you for your help jayboyyyy!
Click to expand...
Click to collapse
nice find. im going to update that thread i made with this link instead of the link i had because it seems to have fastboot for everyone.

[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] Cannot Flash factory images EVEN when flashing each image seperately

Fastboot flash system ...
(bootloader) Data size exceeds download buffer
FAILED (Remote Failure)
What is going on?
Need the new fastboot
papi92 said:
Need the new fastboot
Click to expand...
Click to collapse
I have tried that with no success
Unlocked bootloader? Stock USB cable.
papi92 said:
Unlocked bootloader? Stock USB cable.
Click to expand...
Click to collapse
Yeah stock cable, bootloader is unlocked and everything besides the system image flashes without a hitch
Weird.
Maybe a corrupt download? Try downloading it again and/or check the MD5. (af4520213c1a3e2b3dd811aef030b87b)
same here
i'm stuck...
jamesadalpiaz said:
Maybe a corrupt download? Try downloading it again and/or check the MD5. (af4520213c1a3e2b3dd811aef030b87b)
Click to expand...
Click to collapse
Thanks man didn't even think to check, 'twas a bad download!
still doesnt work for me.
my download is okay.
when trying to flash system img -- still getting the same message as above.
when trying to use flash all bat file --getting these quoets:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain recovery.sig'
failed to allocate 1679592636 bytes
error: update package missing system.img
Click to expand...
Click to collapse
Please help me
itamarbh said:
still doesnt work for me.
my download is okay.
when trying to flash system img -- still getting the same message as above.
when trying to use flash all bat file --getting these quoets:
Please help me
Click to expand...
Click to collapse
what error do you get when you try to unzip and flash the individual img files?
jj14 said:
what error do you get when you try to unzip and flash the individual img files?
Click to expand...
Click to collapse
this...
(bootloader) Data size exceeds download buffer
FAILED (Remote Failure)
Thanks !
itamarbh said:
still doesnt work for me.
my download is okay.
when trying to flash system img -- still getting the same message as above.
when trying to use flash all bat file --getting these quoets:
Please help me
Click to expand...
Click to collapse
When you downloaded the .tgz file and extracted it, it contained a .tar file. When you extract the .tar file you get the shamu-lrx21o folder. Within that folder you have the flash-all.bat, but you also have the image-shamu-lrx21o.zip file. Extract the contents of that zip file and try again. The system.img file is in that zip file.
Astraeus85 said:
When you downloaded the .tgz file and extracted it, it contained a .tar file. When you extract the .tar file you get the shamu-lrx21o folder. Within that folder you have the flash-all.bat, but you also have the image-shamu-lrx21o.zip file. Extract the contents of that zip file and try again. The system.img file is in that zip file.
Click to expand...
Click to collapse
I know, tried that as well, didn't work...
i'm stuck.
itamarbh said:
still doesnt work for me.
my download is okay.
when trying to flash system img -- still getting the same message as above.
when trying to use flash all bat file --getting these quoets:
Please help me
Click to expand...
Click to collapse
Here's your help. I had the same exact problem. Follow the instructions to this link and you'll be back on track.
http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
glensta said:
Here's your help. I had the same exact problem. Follow the instructions to this link and you'll be back on track.
http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
Click to expand...
Click to collapse
Thanks for reponding,
But this didn't help, like I said before -- I'm getting an error while flashing the system img alone as well...
Thanks anyway...
Anyone else?
itamarbh said:
Thanks for reponding,
But this didn't help, like I said before -- I'm getting an error while flashing the system img alone as well...
Thanks anyway...
Anyone else?
Click to expand...
Click to collapse
Did u even try this method above I posted? How could it not help. It works perfectly. Seems u didn't try it is my guess. If your stuck don't try just flashing the system.img only, start over with a complete factory image reflash. It'll wipe ur data but so what, u'll be back in business
itamarbh said:
this...
(bootloader) Data size exceeds download buffer
FAILED (Remote Failure)
Thanks !
Click to expand...
Click to collapse
I ran into this yesterday, do this:
Download the Android SDK: https://developer.android.com/sdk
Grab fastboot from the platforms-tools folder.
Flash System again
This will fix it, you just need the newest Fastboot.
Sent from my Nexus 6 using XDA Free mobile app
I'm also stuck.
I keep getting the error 'cannot load system.img'. Everything else flashes fine. The bootloader and the radio. I received the OTA and that didn't install either. I was left with the android guy on his back and it said error. I'm not sure if it has to do with the encryption on the phone or not but it's frustrating. I did root with CFauto root method but my recovery is still stock. I'll try the new fastboot and see what happens.
This might not apply in this situation, but coming from several years of previous Motorola phones, sometimes I had to download and use mfastboot (Motorola's version of fastboot) for large images to flash. It's worth a shot and won't hurt to try it
Edit: here is the link. If you decide to try it, make sure to read the first section on renaming the file http://mark.cdmaforums.com/ADB.htm

I think there is an issue with the factory image for 5.1

I downloaded the factory image from two places and was able to flash the boot image and the radio manually but when I go to flash the image itself I receive this.
I am rooted using the Nexus root tool kit with twrp recoovery
fastboot -w update [image file].zip, I receive
C:\Android\platform-tools>fastboot -w update image-shamu-lmy47d.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
??
I have flsh each manually and using the flash all plus used the tool kt
Any ideas
I tried the flash-all.bat and got the same error. I extracted all the files from the zip and flashed the images separately and it worked fine.
worldsoutro said:
I downloaded the factory image from two places and was able to flash the boot image and the radio manually but when I go to flash the image itself I receive this.
I am rooted using the Nexus root tool kit with twrp recoovery
fastboot -w update [image file].zip, I receive
C:\Android\platform-tools>fastboot -w update image-shamu-lmy47d.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
??
I have flsh each manually and using the flash all plus used the tool kt
Any ideas
Click to expand...
Click to collapse
Last time I had that error, it turned out I had an outdated version of fastboot. I was using the packaged version, adnroid-tools-fastboot, on Ubuntu and all was well after installing the latest version through the Android SDK. Not sure if the same would apply here but that was my experience.
Marcellus1 said:
I tried the flash-all.bat and got the same error. I extracted all the files from the zip and flashed the images separately and it worked fine.
Click to expand...
Click to collapse
Same thing here, when I got the error I flashed system, boot and recovery from the zip manually (I've kept my cache and userdata intact to avoid the factory reset).
It went all good but at the first boot the phone executed the encryption of the memory because I've had un-encrypted it when I was on 5.0.1
Yeah I end up flashing each file one by one. I was also getting the errors. All seem fine now
---------- Post added at 01:21 AM ---------- Previous post was at 01:19 AM ----------
This update was a nightmare took me 6 hours to update. I'm not a noib either. Lol

Error when trying to flash Android M to stock Nexus 6

Hey guys. So I've been trying to manually update with no success so far. I was going to sideload, but I got the November security update ota and there is no ota file for LMY48X to Marshmallow (as far as I know). So I bit the bullet and unlocked the bootloader yesterday, and got the adb and fastboot set up and tried to run the ./flash-all.sh command. (I'm on a Mac) Everything was going fine until I came across an error. So I basically gave up and restored all my user data.
Today I figured I'd try again since I have already unlocked my bootloader and have nothing to lose. mra58k didn't work, so I figured I'd try the mra58n image and removed the -w command from the flash-all.sh and tried again. This is what I got:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(69137) malloc: *** mmap(size=2094391296) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 2092296104 bytes
error: update package missing system.img
Can anyone help me out? I have a feeling I won't be getting the ota through my phone anytime soon.
I may be wrong as this is a pure guess, but did you check the download to confirm it met the checksum? You might just try deleting your download and redownloading the latest version.
haibane said:
I may be wrong as this is a pure guess, but did you check the download to confirm it met the checksum? You might just try deleting your download and redownloading the latest version.
Click to expand...
Click to collapse
No it is Google. Same here. Flashall.bat stops after flashing m-bootloader and m-radio.
After that it is needed to extract all the images and fastboot flash every image.
Don't use the flash-all.sh file to flash, flash the files manually. Plenty of guides outline the commands to use. Plus, make sure that you're Android SDK Tools is updated to the latest version.
RMarkwald said:
Don't use the flash-all.sh file to flash, flash the files manually. Plenty of guides outline the commands to use. Plus, make sure that you're Android SDK Tools is updated to the latest version.
Click to expand...
Click to collapse
Thanks for the reply. So I went ahead and followed your advice and tried to do it manually. I checked everything was up to date. I flashed the bootloader, radio, recovery and boot images and rebooted the bootloader between every flash with no incident. Then I tried to flash the system.img and it first everything seemed to be ok but the terminal is stuck at "sending sparse 'system' " and hasn't done anything in 20 minutes. I'm afraid to do anything right now. Is it ok to close terminal, reopen it and try flashing the system.img again?
ICStevenC. said:
Thanks for the reply. So I went ahead and followed your advice and tried to do it manually. I checked everything was up to date. I flashed the bootloader, radio, recovery and boot images and rebooted the bootloader between every flash with no incident. Then I tried to flash the system.img and it first everything seemed to be ok but the terminal is stuck at "sending sparse 'system' " and hasn't done anything in 20 minutes. I'm afraid to do anything right now. Is it ok to close terminal, reopen it and try flashing the system.img again?
Click to expand...
Click to collapse
Hmmm...the system.img does take time but shouldn't take 20 minutes. Did you flash all the .img files separately, or did you use the command:
Code:
fastboot -w update image-shamu-mra58n.zip
?
I've never done any of this from a Mac, only Linux and Windows, but here's what I do when flashing manually. I extract the contents of the factory image zip, AND the image-shamu-mra58n.zip into my SDK directory (see image attached).
Once everything is extracted, after backing up things I wanna save on my device, I boot to the bootloader and go to town:
Code:
fastboot erase boot
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot erase system
Code:
fastboot erase userdata
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash radio radio-shamu-d4.01-9625-05.27+fsg-9625-02.104.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot reboot
RMarkwald said:
Hmmm...the system.img does take time but shouldn't take 20 minutes. Did you flash all the .img files separately, or did you use the command:
Code:
fastboot -w update image-shamu-mra58n.zip
?
Click to expand...
Click to collapse
No, I decompressed that zip and flashed them all separately using the
Code:
./fastboot flash
command and dragging the files directly to the terminal and then using
Code:
./fastboot reboot-bootloader
in between every flash.
ICStevenC. said:
No, I decompressed that zip and flashed them all separately using the
Code:
./fastboot flash
command and dragging the files directly to the terminal and then using
Code:
./fastboot reboot-bootloader
in between every flash.
Click to expand...
Click to collapse
Okay, seems like you're on the right path. See my post above. You'll erase everything first, then flash everything back one by one, kinda like what you are already doing. I've never had issues doing it this way ever, it may be overkill and it will wipe your phone completely, but if you've backed things up (pictures, docs, music, etc) beforehand, no biggie. The only times I reload the bootloader is after flashing the bootloader, and then the radio.
The system.img will take the longest, and userdata will take a little time too, but the others should be almost instant.
RMarkwald said:
Okay, seems like you're on the right path. See my post above. You'll erase everything first, then flash everything back one by one, kinda like what you are already doing. I've never had issues doing it this way ever, it may be overkill and it will wipe your phone completely, but if you've backed things up (pictures, docs, music, etc) beforehand, no biggie. The only times I reload the bootloader is after flashing the bootloader, and then the radio.
The system.img will take the longest, and userdata will take a little time too, but the others should be almost instant.
Click to expand...
Click to collapse
The terminal doesn't appear to be responding to any command now. I tried erasing boot and after pressing enter, nothing happened. Closing it and reopening it doesn't help. Should I try restarting my computer?
ICStevenC. said:
The terminal doesn't appear to be responding to any command now. I tried erasing boot and after pressing enter, nothing happened. Closing it and reopening it doesn't help. Should I try restarting my computer?
Click to expand...
Click to collapse
Yeah, give that a shot. As long as you have bootloader access you will be okay.
RMarkwald said:
Yeah, give that a shot. As long as you have bootloader access you will be okay.
Click to expand...
Click to collapse
I am now on 6.0 and everything appears to be functional. Thank you so much for all your help! I really appreciate it.
Awesome man! Glad I could help.

Categories

Resources