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
Related
Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC
Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).
Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here
Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.
the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.
It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system
If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader
bump? Did anyone end up getting a system image? Thanks.
Nader
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.
ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.
bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.
Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with
I am also not able to flash this system.img file. I get the same error.
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.
I was rooted and removed some of the bloatware, before applying this update I reinstalled the bloatware and unrooted, when I try to update(5.6.980) it goes through but hangs on updating bp then it says
assert failed: motorola.motoflash("/tmp/bp.img")
E:Error in /tmp/sideload/package.zip
(status 7)
installation aborted
...idk what to do I tried wiping, rooting then unrooting and I keep getting the sam message and I guess thats needed for radio because now my phone can't find it, is there a package file or something i need????????????
anybody....
LRiley said:
anybody....
Click to expand...
Click to collapse
Have you tried flashing bp.img in fastboot?
rynosaur said:
Have you tried flashing bp.img in fastboot?
Click to expand...
Click to collapse
how do I do that?
LRiley said:
how do I do that?
Click to expand...
Click to collapse
I think this will be the file you need.
Then, get fastboot and put that file in the same directory.
Put the phone in AP Flash mode.
Connect with Moto cable to a good USB port.
type in:
Code:
fastboot devices
and verify that your device is shown without restrictions (you'll see a 16-char HEX code/serial id#)
if windows:
Code:
.\fastboot flash bpsw bpsw.img
if linux/unix/Mac:
Code:
./fastboot flash bpsw bpsw.img
reboot into recovery then try the update again.
did it and it says sending, OKAY, writing, (bootloader) command restricted, FAILED...is that right?
LRiley said:
did it and it says sending, OKAY, writing, (bootloader) command restricted, FAILED...is that right?
Click to expand...
Click to collapse
Well, yes, probably. For some reason, only certain partitions are available to flash from AP Fastboot.
rynosaur said:
Well, yes, probably. For some reason, only certain partitions are available to flash from AP Fastboot.
Click to expand...
Click to collapse
no, that means nothing happened. It sent it to the device, but didnt write it. So right where you started.
I got the same error again, I'm gonna root and try again
edru said:
no, that means nothing happened. It sent it to the device, but didnt write it. So right where you started.
Click to expand...
Click to collapse
Well, yeah, that's what I meant. It's normal for that partition to fail out. I'm guessing certain blocks can only be written in raw form from BP/SBF.
now I'm stuck in fastboot wut do I do now
LRiley said:
now I'm stuck in fastboot wut do I do now
Click to expand...
Click to collapse
Stuck? Reflash a non-protected partition, like cdrom. Then.
Code:
fastboot reboot
did it with mdm, but I'm back to square one
In the future, you'll probably get more help by titling your thread something more useful. I have skipped over it a few times already.
What's the output of
Code:
df /system
Edit: scratch that. bp.img is extracted to /tmp, which I'm guessing is a RAM disk. Have you tried running the update again? I'm not sure I understand why it would fail. Regardless, it is flashed using a Motorola utility so I imagine flashing by fastboot won't work.
I flashed it a lot of times but the update always gets stuck at bp
any ideas?
Can you post /cache/recovery/last_log
limaxray said:
Can you post /cache/recovery/last_log
Click to expand...
Click to collapse
where do I get that
LRiley said:
where do I get that
Click to expand...
Click to collapse
I assume you have adb installed? In a terminal, run:
Code:
adb shell
su
cp /cache/recovery/last_log /sdcard/
exit
exit
adb pull /sdcard/last_log <some local directory>
Replacing <some local directory> with wherever is convenient.
Hi all. Quick notice:
Usual disclaimers apply.
This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.
Okay cool... but what is an insecure boot.img?
An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin
adb shell
su
mount -o remount,rw /system
exit
See more here: External Link
_____________________________________________________________________________________________________________
To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).
A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/
To boot this boot.img:
must be in the platform-tools folder in the android-sdk
must be in fastboot mode (power+vol-)
First use: fastboot boot "boot.img" (no ")
Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**
**Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.
Thank you for helping!
-fkrone
-Ranguvar
-USSENTERNCC1701E
This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)
DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.
Click to expand...
Click to collapse
Please Lock!
Placeholder reserve
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
I wouldn't be lazy and do it myself but PC is off
Sent from a phone
Click to expand...
Click to collapse
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Ranguvar said:
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Click to expand...
Click to collapse
Pull it apart in hex editor
Sent from my HTC Explorer A310e using xda app-developers app
Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
Sent from a phone
Click to expand...
Click to collapse
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
USSENTERNCC1701E said:
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
Click to expand...
Click to collapse
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
I could probably do it without this, but it probably wouldn't mount data/media (what emulates the SD) so it would be relatively useless as that's where zips are
Also this might prove useful: http://forum.xda-developers.com/showthread.php?t=1494036 (requires Cygwin or Linux environment)
Harry GT-S5830 said:
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
Click to expand...
Click to collapse
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
USSENTERNCC1701E said:
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
Click to expand...
Click to collapse
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Harry GT-S5830 said:
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Click to expand...
Click to collapse
Lol, I'm having a hell of a time getting Slax as a cooperative VM, might have to go all out with ubuntu
Got it!
Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored Would be nice if you can mention me in the people helped to create this recovery
http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror
Dammit, beat me to it!
Serves me right for making dinner first
http://ompldr.org/vZ2ExYQ/recovery.fstab
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
pikachukaki said:
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
Click to expand...
Click to collapse
That's not quite how it works. These .img files we are talking about are pictures of the stock version of those paritions. Try reading this article for an explanation of Android partitioning.
There is also a great graphic here. The site is in Spanish, I haven't used Google to translate it, but the picture there is in English. Take your time with it, there's a lot of info there.
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Stryder5 said:
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Click to expand...
Click to collapse
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
USSENTERNCC1701E said:
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
Click to expand...
Click to collapse
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Stryder5 said:
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Click to expand...
Click to collapse
Woops, wrong thread.
Yes, if you push the su binary from a superuser flashable zip to /system/bin/ and chmod 0655, plus the superuser apk, you will have permanent root after.
Also, there is a recovery.img now, so you can test that out, if it works, flash it from fastboot, then flash a superuser zip from that recovery.
Thank you for getting it (recovery.fstab), looks like someone beat me to it though!
Sorry for late response I have to sleep as I'm in last school year
Ill cook up a recovery just to make your efforts worthwhile
It's in OP, its probably 99.9% the same as the other guys so i'm not going to make duplicate thread, use who evers recovery you wish.
____________________________________________________________________________________________________________________________________
Reason I say fastboot boot first is because it allows you to boot the image without permanently (well, unless you flash another over) flashing a partition without knowing it works.
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Stryder5 said:
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Click to expand...
Click to collapse
Not at my comp now or I'd upload it, bit of you rip open the fa Tory image from the Google servers you should find it
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
On a side note, what possessed you to do that?
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 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.