Develop Bugs

Missing storage after "manually" updating to android 5.1 - [SOLVED]

Hi, I recently installed official android 5.1 from factory source but now I have issues "missing" storage.
32GB Nexus 7 2013 (Wifi)
TOTAL: 26,9 GB
Used: 17,3GB
Free: 9,6GB
Theese numbers are not supposed to be what they are right out of the box with barely no apps installed and nothing else stored. I am supposed to have much more free space.
I followed this guide to install every .img file manually that was included in the official factory images.
Install instructions followed:
Flash bootloader and radio (radio does not appear on all devices, if it's not in your tgz, you don't need it)
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
NEXUS 9 ONLY - flash this as well
fastboot flash vendor vendor.img
If you want to wipe cache and user data (full wipe), flash these
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
The reason that I "manually" flashed every .img file is because I got errors when using the flash-all.bat file
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 842365088 bytes
error: update package missing system.img
Thanks in advance for help!
EDIT:
Confirmed: factory reset/data wipe in stock recovery solved the storage problem

Try formatting data with twrp. That fixed the no storage problem I had a while ago.

yosmokinman said:
Try formatting data with twrp. That fixed the no storage problem I had a while ago.
Click to expand...
Click to collapse
I haven't installed TWRP yet, do you know if it supports 5.1? Any chance that the stock recovery can do the same?

You could try a factory reset/data wipe in stock recovery. Latest twrp works fine.

yosmokinman said:
You could try a factory reset/data wipe in stock recovery. Latest twrp works fine.
Click to expand...
Click to collapse
Confirmed: factory reset/data wipe in stock recovery solved the storage problem
Thank you very much

my nexus 32gb is showing like 26.5gb after the update for 5.1 this is normal value? 6gb is consumed by the OS or something?
my device is fullwiped

[GUIDE] How to manually upgrade firmware

First of all, this guide expects you to have some basic knowledge how to use fastboot, have working ADB/fastboot connection on your computer and understand the fact that this may brick your phone if you mess up.
I am NOT responsible for anything! This will wipe everything on your phone, so get backups if needed.
This guide is written for X720 and supplied files are ONLY for X720. Same procedure will work on X727, but you will have to get right files yourself.
All files are from stock 23S, just extracted, converted and repacked for your convenience.
Read the whole guide before doing anything. If you're unsure about anything, don't do it.
Here we go:
1. Download .zip containing files from Mega: https://mega.nz/#!5boxDYrL!_O-oD05yhiU5FbCmYuf47VH4Qar5RhV5LKwyHa39bWM
2. Extract files to path where you are able to flash them using fastboot (ie. same folder with fastboot)
3. Boot your phone to bootloader (Vol- & Power)
4. Flash everything:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format data <-- THIS WILL WIPE YOUR PHONE INCLUDING INTERNAL STORAGE
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash ddr ddr.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash hyp hyp.mbn
fastboot flash pmic pmic.elf
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash xbl xbl.elf
fastboot flash keymaster keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash devinfo devinfo.bin​5. Reboot, and let it boot up (takes some time)
6. Flash TWRP, wipe everything and install ROM (you have done this before, won't write a guide)
Credit for this guide goes to @darkobas

get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi

I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.

Presterin said:
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Click to expand...
Click to collapse
thx
i will try again.

Does anyone know which ones are safe to flash over the existing rom? I do not wish to wipe or break current rom.

I flashed everything except system and boot on top of Omni rom. Everything works great.

Does anyone know where I can get all of the files for my x727, I considered using the files from these OTA zips but I think some of the files are missing like the modem firmware and system.img.

On x720 some of the files were divided into scatter files, had to do some research to get them sorted.

Which fastboot is compatible with system.img? Because of me too :"target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". minimal fast boot 1.42
Edit: ok..as long as the post I wrote started installation

Should/Can we install the latest fastboot? Mine is on shop altered 17s from over a year a go, which to be fair runs great; i just fancy a change.
Thanks

write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do

Any solution?
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
Stuck here as well

Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished

Great guide Thanks.
It saved me from a system wipe and a nightly not recognized by TWRP...:crying:

tsongming said:
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Click to expand...
Click to collapse
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.

jackpollard said:
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720

amdol said:
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Click to expand...
Click to collapse
Thank you! My flaw was looking on https://lineageos.org/ and not on here.

ajegile said:
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
get the same. iam not shure if i have the x722 or x720. they look same

Help restoring to stock image, after trying to install copperhead os

Hi all,
I'm sorry to ask this question, but I'm really struggling to get my Nexus 5X to boot into stock rom. The install seems to go ok, but there was error when flashing.. See below...
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
The phone now boots to the google boot logo, then loops back to either the "Unlocked Bootloader" or the Custom OS message. (depending on the locked state of the bootloader)
I cannot get into recovery, as the phone just loops back as described above when selecting it from the bootloader option.
Can anyone advise me on how to restore the phone back to stock os. I've tried flashing version 7.1.2 8.0.0 and 8.1.0, using either the flash-all.bat or manually typing the commands. I'm 110% sure this is not to do with over heating on CPU/RAM, I have another nexus 5x that has the bootloop of death and it's bootloop is very different from what I'm seeing on this Nexus 5x.
Thanks in advance

First, the .sig errors are normal so you can ignore those. I would make sure your booloader is unlocked then manually flash the bootloader.img. Then boot back into the bootloader. Then manually flash the remainder of the partitions. Use the 8.1.0 os.
Sent from my [device_name] using XDA-Developers Legacy app

Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.

pinkstink said:
Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.
Click to expand...
Click to collapse
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.

i.adrian said:
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.
Click to expand...
Click to collapse
Hiya,
I have also tried using the .bat script, it leads to the same place. A phone that does not boot.
thanks in advance.

Can you boot into twrp, fastboot boot twrp.img? If you can try formatting, not wiping, the data partition. It also gives you the option to repairing some other partitions, I don't remember which ones. You could try that.
Sent from my [device_name] using XDA-Developers Legacy app

Stuck in fastboot after failed upgrade from rooted 8.0 to 9.0

So today I tried to flash Pie over my rooted 8.0. I used partition DL mode and first selected everything but ABL_A/B, userdata, and all my A partitions, hoping to preserve that slot just in case. When I tried to boot into my B slot with 9.0, it just went into fastboot. Alright, whatever, I can keep 8.0, no biggie. I fastboot --set-active=a but this time it got stuck decrypting on the open lock icon with the rotating ring after entering my PIN. Okay, fine, I'll flash again. Enter Firmware Update mode, use partition DL mode, select everything except ABL_A/B, flash. Now I'm stuck in fastboot. Android won't boot, and attempting to enter Firmware Update mode and get a red triangle with the message "your device has failed a routine safety check and will not boot". I then used fastboot to flash my previous 8.0 backed up laf.img over my laf_b partition. Now, when I attempt to enter Firmware Update mode, I get the normal blue progress bar briefly, but then it just goes back to fastboot.
Which is where I am now. Any ideas? I'm thinking maybe if I "complete" the upgrade and flash a stock 9.0 ABL partition it might work, but I don't have one of those, LG Firmware Extract only produces an .elf file, kdztools gives an error when trying to extract the .dz:
F:\backup\LGV35\kdztools-master>undz.py -f tmp/V35020d_00_OPEN_US_0612.dz -l
[!] Warning: extraneous data found IN version
Traceback (most recent call last):
File "F:\backup\LGV35\kdztools-master\undz.py", line 1069, in <module>
dztools.main()
File "F:\backup\LGV35\kdztools-master\undz.py", line 1035, in main
self.dz_file = UNDZFile(cmd.dzfile)
File "F:\backup\LGV35\kdztools-master\undz.py", line 901, in __init__
self.loadChunks()
File "F:\backup\LGV35\kdztools-master\undz.py", line 622, in loadChunks
g = gpt.GPT(self.chunks[0].extract())
File "F:\backup\LGV35\kdztools-master\undz.py", line 221, in extract
buf = dctx.decompress(zdata, max_output_size=200000000)
zstd.ZstdError: error determining content size from frame header
I'd prefer not to have to hire an Octoplus owner to fix it since I still have an unlocked bootloader and still have fastboot, but I'm out of ideas. Oh, yeah, I also did "fastboot erase userdata", and attempted to do "fastboot format userdata", but the format failed. I also tried "fastboot -w" but got
F:\backup\LGV35>fastboot -w
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
Update: I flashed my backup 8.0 xbl partition. That, along with my 8.0 laf, has let me back into firmware update mode. I then flashed Pie again in partition DL mode, deselecting my abl_b, xbl_b, and laf_b. Seems it automatically switched my active slot back to A. At least I hope so, and my engineering abl_b with fastboot is still there.

Question about rooting with Magisk

I have successfully unlocked the Pixel 2 XL and installed the official release 8.0.0 / OPD1.170816.010 from Sep 2017. I downloaded Magisk and transfered the image to the phone and extracted the files on the phone.
According to the official guide, I have to patch the boot.img, but the image only contains a bootloader.img. When I use the "fastboot flash boot boot.img" command, it also tells me "No such partition".
How do I properly patch the official file and root the Pixel 2 XL without bricking it? Am I doing something wrong?

Venomiz said:
I have successfully unlocked the Pixel 2 XL and installed the official release 8.0.0 / OPD1.170816.010 from Sep 2017. I downloaded Magisk and transfered the image to the phone and extracted the files on the phone.
According to the official guide, I have to patch the boot.img, but the image only contains a bootloader.img. When I use the "fastboot flash boot boot.img" command, it also tells me "No such partition".
How do I properly patch the official file and root the Pixel 2 XL without bricking it? Am I doing something wrong?
Click to expand...
Click to collapse
Are you unzipping the second folder as well?
Factory Image .zip > unzip to factory image folder > unzip to 2nd factory image folder > boot.img
Curious as to why you're flashing 8x instead of android 10?
If you still hit a wall, check out the step by step instructions linked in my sig, near the bottom is an upgrade from os to os section ( 9x to android 10).

Az Biker said:
Are you unzipping the second folder as well?
Factory Image .zip > unzip to factory image folder > unzip to 2nd factory image folder > boot.img
Curious as to why you're flashing 8x instead of android 10?
If you still hit a wall, check out the step by step instructions linked in my sig, near the bottom is an upgrade from os to os section ( 9x to android 10).
Click to expand...
Click to collapse
Thanks for the reply. In the folder are the following files:
bootloader-taimen-tmz10n.img
flash-all.bat & .sh
flash-base.sh
radio-taimen-g8998-.....
And I overlooked the image-taimen-opd1.170816.010.zip
So, I patched with magisk the wrong file but it was successful (at least if I trust the onscreen text). I will now transfer the boot.img to the pixel, patch it, transfer it back, and flash. I will reply after doing so
PS: Android 8 is easier to use if you do something you should not in Pokemon Go... :silly:
And the

Why patch the boot image manually, flashing magisk via TWRP as it works fine. Ive never used the patch boot image method ever on any of the devices ive owned.
1) Flash ROM
2) Boot TWRP
3) Flash TWRP (optional)
4) Flash Magisk
5) Reboot

Hi folks, this is the current status.
I patched the boot.img and tried the following:
fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boota' (25632 KB)...
OKAY [ 0.542s]
writing 'boota'...
FAILED (remote: No such partition.)
finished. total time: 0.548s
What did I miss here?

Venomiz said:
Hi folks, this is the current status.
I patched the boot.img and tried the following:
fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boota' (25632 KB)...
OKAY [ 0.542s]
writing 'boota'...
FAILED (remote: No such partition.)
finished. total time: 0.548s
What did I miss here?
Click to expand...
Click to collapse
Let's start over from scratch because you're not following the instruction being posted, so maybe you are trying to accomplish something else.
What state is your device currently in and what are you trying to accomplish? I was under the impression you simply want to flash the last 8x factory image to your device, is that correct?

Az Biker said:
Let's start over from scratch because you're not following the instruction being posted, so maybe you are trying to accomplish something else.
What state is your device currently in and what are you trying to accomplish? I was under the impression you simply want to flash the last 8x factory image to your device, is that correct?
Click to expand...
Click to collapse
Uhm not really. As I said in the title, I want to root the Pixel 2 XL with Android 8 and Magisk.
So what I did so far is:
- Unlocked the bootloader and applied the Android 8 image
- Downloaded and installed magisk
- Unzipped the original rom wice to get the boot.img, transfer it to the phone, patched it with magisk and transfered it back to the PC.
When now trying to flash it with fastboot, the output above showed up.

Venomiz said:
Uhm not really. As I said in the title, I want to root the Pixel 2 XL with Android 8 and Magisk.
So what I did so far is:
- Unlocked the bootloader and applied the Android 8 image
- Downloaded and installed magisk
- Unzipped the original rom wice to get the boot.img, transfer it to the phone, patched it with magisk and transfered it back to the PC.
When now trying to flash it with fastboot, the output above showed up.
Click to expand...
Click to collapse
In fastboot do the following:
flash your factory 8 image (leave the -w intact to wipe your device, remove the -w to keep your data)
after your device boots up, get back to bootloader and fastboot the TWRP img from platform folder
once booted into TWRP, flash TWRP.ZIP to install cust recovery
in twrp flash cust kernel (optional)
reboot and allow the OS to fully settle in ( 1-2 minutes after bootup)
boot into TWRP and install magisk
reboot
These same instructions are found in much more detail in the link in my sig. I use this method every month for the latest update, and it's never failed. No patching images, no booting to diff slots, just follow the simple steps.

Az Biker said:
In fastboot do the following:
flash your factory 8 image (leave the -w intact to wipe your device, remove the -w to keep your data)
after your device boots up, get back to bootloader and fastboot the TWRP img from platform folder
once booted into TWRP, flash TWRP.ZIP to install cust recovery
in twrp flash cust kernel (optional)
reboot and allow the OS to fully settle in ( 1-2 minutes after bootup)
boot into TWRP and install magisk
reboot
These same instructions are found in much more detail in the link in my sig. I use this method every month for the latest update, and it's never failed. No patching images, no booting to diff slots, just follow the simple steps.
Click to expand...
Click to collapse
It worked perfectly, thank you!