Database Develop

Problem with flashing

Okay, i've wanted to flash TWRP, to flash CM11, so i have root, unlocked bootloader, drivers, etc. Required for flashing but there are two problems.
---DONT MIND THIS, MY FAULT (Solved)---
With TWRP flashing:
* Whenever i try to flash it (i have the file in the adt bundle folder with the cmd window open from the directory) and write:
fastboot flash recovery [filename].img (yes, i've checked many times for typos)
I get this:
(Bootloader) variable not supported
---This is the actual problem---
With Stock flashing:
Then i tried to re-flash stock firmware in case that there were any corrupted file interrupting the process.
Flashed, but in the process, after, or while flashing system.img (All with RSD Lite), in the phone, appeared a red text line that said "sp space is not enough" and the phone took like half a minute to reboot again and everything seemed to be normal. But if i try to do any of those processes again, even if i re flash stock fw, it keeps the same.
Need responses please D:

ANMTMS said:
Okay, i've wanted to flash TWRP, to flash CM11, so i have root, unlocked bootloader, drivers, etc. Required for flashing but there are two problems.
---DONT MIND THIS, MY FAULT (Solved)---
With TWRP flashing:
* Whenever i try to flash it (i have the file in the adt bundle folder with the cmd window open from the directory) and write:
fastboot flash recovery [filename].img (yes, i've checked many times for typos)
I get this:
(Bootloader) variable not supported
---This is the actual problem---
With Stock flashing:
Then i tried to re-flash stock firmware in case that there were any corrupted file interrupting the process.
Flashed, but in the process, after, or while flashing system.img (All with RSD Lite), in the phone, appeared a red text line that said "sp space is not enough" and the phone took like half a minute to reboot again and everything seemed to be normal. But if i try to do any of those processes again, even if i re flash stock fw, it keeps the same.
Need responses please D:
Click to expand...
Click to collapse
If I understand your post correctly..
Sir..use mfastboot with this command >>
mfastboot flash recovery recovery.img
Rename your recovery file to this >> recovery.img
Then flash..make sure that the recovery.img file is in the same directory as adb.exe
Make sure that you do have a mfastboot.exe in the same directory as the adb.exe..you may have to also copy some .dll files from another directory to the same directory as the mfastboot.exe (and) adb.exe
Also..you mentioned that you flashed a new OS..maybe the FXZ is modified to NOT erase data/cache.?
Make SURE that you have the proper TWRP version for your device..(probably) "ghost" code name type TWRP is what you'll need..many ones mess up by not using the proper TWRP version for the device..
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html

ANMTMS said:
Okay, i've wanted to flash TWRP, to flash CM11, so i have root, unlocked bootloader, drivers, etc. Required for flashing but there are two problems.
---DONT MIND THIS, MY FAULT (Solved)---
With TWRP flashing:
* Whenever i try to flash it (i have the file in the adt bundle folder with the cmd window open from the directory) and write:
fastboot flash recovery [filename].img (yes, i've checked many times for typos)
I get this:
(Bootloader) variable not supported
---This is the actual problem---
With Stock flashing:
Then i tried to re-flash stock firmware in case that there were any corrupted file interrupting the process.
Flashed, but in the process, after, or while flashing system.img (All with RSD Lite), in the phone, appeared a red text line that said "sp space is not enough" and the phone took like half a minute to reboot again and everything seemed to be normal. But if i try to do any of those processes again, even if i re flash stock fw, it keeps the same.
Need responses please D:
Click to expand...
Click to collapse
Find the Return to Stock thread.
Use the manual method instead of RSD Lite, and use 'mfastboot' for ALL commands.
The problem is that the native fastboot cannot flash system.img because it is too large. The modified motorola 'mfastboot' is able to flash it.
Please try and post results.

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

Cannot load system.img : not enough space

So i was flashing manually ATT 5.1 Zip firmware(Source) with cmd, but i'm stuck on flashing system.img :crying:
E:\Bootloader Tool Kits>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1482130164 bytes
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
And after trying several times and it gives same result, i decided to skip that one. And then i tried to flash TWRP, it successful. I tried to restore my CM12 backup, it's going though but i can't reboot to system. When i reboot to system it keep going back to fastboot :crying:
How i can flash system.img or at least restore my CM12 backup?
EDIT:Now i can reboot to system with CM12 installed (backup) but it could not recognize my sim card
EDIT2:Now it can recognize my sim card. so for now, i ended up just updating my bootloader version hahaha

Solution to "cannot load 'system.img': Not enough space"
LuthfiKun said:
...
Click to expand...
Click to collapse
SOLUTION
I had the same issue using the official 5.1 from Motorola and KidJoe's guide. I saw in the options section that -P "enable parallel loading for multi-flash if there is no [sic] enough memory on host to load whole image."
Thus, using mfastboot flash system system.img -P loaded it in 256MB chunks which worked. It did sit on the moto logo for just long enough to strike fear, but is running beautifully now.
This was on a system with 13.9GB free of 16GB RAM....

I faced this issue just the last day, when I was trying to flash through mfastboot. I tried to flash with rsdlite and it worked fine. I guess the -P switch must be automatic in rsdlite!

-P worked thank you very much

Flashing 5.1 to XT1053 not working

I have requested the stock 5.1 file from motorola and it comes with everything to flash it on the phone via fastboot which also comes in the file. I know what im doing but for some reason everytime i get to flashing the system file it says this?
$ fastboot flash system system.img
sending 'system' (1404896 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Does anybody have a clue i cant get a system img on my phone and I kinda need my phone

Shafty6 said:
I have requested the stock 5.1 file from motorola and it comes with everything to flash it on the phone via fastboot which also comes in the file. I know what im doing but for some reason everytime i get to flashing the system file it says this?
$ fastboot flash system system.img
sending 'system' (1404896 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Does anybody have a clue i cant get a system img on my phone and I kinda need my phone
Click to expand...
Click to collapse
have you tried mfastboot, its modified version of fastboot for larger files
Download mfastboot-v2.zip

hugh a said:
have you tried mfastboot, its modified version of fastboot for larger files
Download mfastboot-v2.zip
Click to expand...
Click to collapse
When I requested the system image for 5.1 it came with fastboot in it everything is from motorola. Why would they not include a fastboot that can load a file that large?
Also i got the mfastboot v2 and it would not work as a fastboot, then i renamed it as fastboot and still will not load the system.img

Shafty6 said:
When I requested the system image for 5.1 it came with fastboot in it everything is from motorola. Why would they not include a fastboot that can load a file that large?
Also i got the mfastboot v2 and it would not work as a fastboot, then i renamed it as fastboot and still will not load the system.img
Click to expand...
Click to collapse
Make sure that the fastboot which is running is the one included with the moto download, and not the one from the Android SDK...
In other words, for Windows PC's, if the Android SDK Platform Tools folder is in the path, often its fastboot will be used instead of the one included in the moto download.
Try renaming the one which came in the moto download as mfastboot.exe, and running it that way, by typing mfastboot.....

KidJoe said:
Make sure that the fastboot which is running is the one included with the moto download, and not the one from the Android SDK...
In other words, for Windows PC's, if the Android SDK Platform Tools folder is in the path, often its fastboot will be used instead of the one included in the moto download.
Try renaming the one which came in the moto download as mfastboot.exe, and running it that way, by typing mfastboot.....
Click to expand...
Click to collapse
Im using mac because its much easier than windows, and ive used the fastboot that comes with everything to fast and everything works perfect till I try system.img

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.