Showed 13.1gb free at first, but became 5gb+ free after I flashed the user data.IMG from Google dev website.
Beamed from my Maguro
UPDATE.
I fixed it, can't use the way i flashed my gnex, have to do this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jro03d.zip
Mach3.2 said:
UPDATE.
I fixed it, can't use the way i flashed my gnex, have to do this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jro03d.zip
Click to expand...
Click to collapse
Thanks for the instructions. Solved my problem
nigameash said:
Thanks for the instructions. Solved my problem
Click to expand...
Click to collapse
You actually searched, thumbs up for you:good:
Beamed from my Grouper.
Mach3.2 said:
UPDATE.
I fixed it, can't use the way i flashed my gnex, have to do this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jro03d.zip
Click to expand...
Click to collapse
glad to hear you resolved it. There is a more complete instruction set for Windows users sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=1907796
Mach3.2 said:
UPDATE.
I fixed it, can't use the way i flashed my gnex, have to do this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jro03d.zip
Click to expand...
Click to collapse
You seriously rock. This helped me fix my 16GB Nexus 4 storage issue after flashing the full Android 4.2.2 image from Google's site. The available space was limited to about 5GB after. I assumed the image didn't partition it correctly. During the process I noticed my radio baseband wasn't at the correct version for 4.2.2 either so I updated that at the same time. (The radio wasn't updated properly in the first 4.2.2 update I ran.)
Works for Nexus 4
Mach3.2 said:
UPDATE.
I fixed it, can't use the way i flashed my gnex, have to do this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jro03d.zip
Click to expand...
Click to collapse
Thanks for sharing this fix! I was having the same available storage problem with my nexus 4 after installing android 4.3 from the Google Dev website following the instructions found here.
Any idea why applying the update from the zipped file results in the device recognizing the actual amount of available storage space, whereas following the directions from that thread doesn't? The only difference that I can see is that applying the update from the zipped file results in 'userdata' being formatted, which doesn't occur following the other thread's directions. Perhaps there's a way to manually format it?
Thanks a million for sharing this though!
Fastboot format userdata would format the userdata partition.
Beamed from my Maguro
Guys, i need some help. i was messing with my nexus 7. then i tried to start fresh again by re-installing the stock 4.4.4. It's been a while since i flash Stock roms. So i find this tutorial, Erase boot, erase userdata etc. then when i tried to flash the bootloader, it always fail (unknown error). So im stuck with a OS-less Nexus 7 and no recovery. I can go to Fastboot. My device is recognizable through Fastboot devices. My old Rom was 4.4.4 stock. Please help me guys
Hello @vyrus027,
flash the files inside the factory image manually with these commands, it'll do the trick:
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
Keelah se'lai,
GethPrime
I'm trying to flash stock android from pure nexus, im in bootloader and have opened command prompt from the folder my images are in, I'm trying to use these commands i found on xda forum's guide to flash to stock
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
but im getting the error - 'fastboot' is not recognized as an internal or external command, operable program or batch file.
please help, how do i get through this :/
kalendaan said:
I'm trying to flash stock android from pure nexus, im in bootloader and have opened command prompt from the folder my images are in, I'm trying to use these commands i found on xda forum's guide to flash to stock
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
but im getting the error - 'fastboot' is not recognized as an internal or external command, operable program or batch file.
please help, how do i get through this :/
Click to expand...
Click to collapse
1) Is this on Windows, Linux, or Mac?
2) Were you able to unlock the bootloader on this same computer with no issues?
3) Are you getting this error after each fastboot command or just for "fastboot flash vendor"? If this is an error for any command, you should first update your platform-tools and fastboot.
kalendaan said:
I'm trying to flash stock android from pure nexus, im in bootloader and have opened command prompt from the folder my images are in, I'm trying to use these commands i found on xda forum's guide to flash to stock
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
but im getting the error - 'fastboot' is not recognized as an internal or external command, operable program or batch file.
please help, how do i get through this :/
Click to expand...
Click to collapse
Do you have the correct drivers and sdk files installed on your pc listed here? http://developer.android.com/sdk/index.html#download
kalendaan said:
I'm trying to flash stock android from pure nexus, im in bootloader and have opened command prompt from the folder my images are in, I'm trying to use these commands i found on xda forum's guide to flash to stock
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
but im getting the error - 'fastboot' is not recognized as an internal or external command, operable program or batch file.
please help, how do i get through this :/
Click to expand...
Click to collapse
You need to setup Android SDK tools on your PC. The generic process is by downloading, installing, and setting up the Android SDK. Once that is done, you should be good to go.
This is the commands run by yotaphone flasher:
fastboot flash aboot firmware/emmc_appsboot.mbn
fastboot flash boot firmware/boot.img
fastboot flash system firmware/system.img
fastboot flash recovery firmware/recovery.img
fastboot flash cache firmware/cache.img
fastboot flash modem firmware/radio/NON-HLOS.bin
fastboot flash sbl1 firmware/radio/sbl1.mbn
fastboot flash rpm firmware/radio/rpm.mbn
fastboot flash tz firmware/radio/tz.mbn
fastboot flash userdata firmware/userdata.img
fastboot reboot
robinmalmberg said:
This is the commands run by yotaphone flasher:
fastboot flash aboot firmware/emmc_appsboot.mbn
fastboot flash boot firmware/boot.img
fastboot flash system firmware/system.img
fastboot flash recovery firmware/recovery.img
fastboot flash cache firmware/cache.img
fastboot flash modem firmware/radio/NON-HLOS.bin
fastboot flash sbl1 firmware/radio/sbl1.mbn
fastboot flash rpm firmware/radio/rpm.mbn
fastboot flash tz firmware/radio/tz.mbn
fastboot flash userdata firmware/userdata.img
fastboot reboot
Click to expand...
Click to collapse
It is a mistery for me. I make all this commands and the flash it is ok for all but my yd201 it is in bootloop always. I have tried alk kind if Roms kit kat, lollipoop. Version RU, EU, Chine, Hong Kong.
It worked! I used these commands to flash my yd206 to yd201 coming from 4.4.3 kitkat to 5.0.0-RU1.1.124 (the archive I downloaded from the Internet contained all required files) and after running them using the fastboot, as I said already, it worked! The first boot took very long, like like 8-10 minutes, I am not sure how long it took, but it was a while, but it worked in the end.
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
try http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
then flash android 6.0 maybe trupure 2.9 and then get the modem from trupure and flash it
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.
acejavelin said:
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.
Click to expand...
Click to collapse
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.
goldentequila said:
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.
Click to expand...
Click to collapse
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.
Sagar_1401 said:
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed
Click to expand...
Click to collapse
The instruction in that post said to not worry about the sparse error message, so I went with it. This is what the post said.
"You may notice a "sparse header error" when flashing at the beginning. Don't worry about it, all is well. The current AutoFlashFirmware.bat file doesn't work with this Firmware file. Flash the files manually!"
Also, i posted above too, but I just accidentally wiped internal via TWRP too. Do you know what I need to do now in order to get my phone back? I've found solutions for other phones regarding this situation, but I haven't come across one for Moto X Pure. This is what happens when you work on your phone all day long and some more into late night lol...
acejavelin said:
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.
Click to expand...
Click to collapse
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.
goldentequila said:
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.
Click to expand...
Click to collapse
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
acejavelin said:
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?
goldentequila said:
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?
Click to expand...
Click to collapse
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Oh ok. Thanks again. I'll report back if I succeed (or not) later today. I appreciate your help.
acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:
goldentequila said:
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:
Click to expand...
Click to collapse
Glad I could help. You're welcome.
Lol it was sparsechunk i just got confused with it and said spunk??