Database Users

[GUIDE] Increase internal storage for Grand i9082

Hi guys
today i am gonna guide you to increase internal storage of galaxy grand.
so first you need following things.
1. patience
2. computer with adb enabled.
3. galaxy grand i9082 with CWM or Philz or TWRP installed.
This procedure will wipe out your whole internal partition. means your all data on internal storage will be gone.
So make back up first.
This is dangerous procedure. needs advance knowledge.
1. So, first boot into recovery.
i think you guys know how to do that.
2. Connect PC and mobile
3. open terminal/CMD on PC/linux computer.
4. type following
PHP:
adb shell
5. Type
PHP:
cd /dev/block
parted mmcblk0
print
6. This looks like following
PHP:
print
Model: MMC M8G1WA (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 14.7MB 15.7MB 1049kB cal
2 15.7MB 16.0MB 262kB sysparm_dep
3 16.0MB 16.3MB 262kB parm-spml_dep
4 16.3MB 16.5MB 262kB RF_CAL_FILE
5 16.5MB 24.9MB 8389kB KERNEL
6 24.9MB 33.3MB 8389kB RECOVERY
7 33.3MB 53.0MB 19.7MB modem
8 53.0MB 86.2MB 33.3MB reserved
9 86.2MB 88.3MB 2097kB SBL1
10 88.3MB 90.4MB 2097kB SBL2
11 90.4MB 98.8MB 8389kB PARAM
12 98.8MB 99.4MB 524kB DTSBK
13 99.4MB 99.9MB 524kB DTS
14 99.9MB 108MB 8389kB VC-FirmwareBK
15 108MB 117MB 8389kB VC-Firmware
16 117MB 117MB 262kB FOTA_SIG
17 117MB 138MB 21.0MB ext4 efs
18 138MB 1212MB 1074MB ext4 CSC
19 1212MB 2822MB 1611MB ext4 system
20 2822MB 3409MB 587MB ext4 HIDDEN
21 3409MB 7813MB 4404MB ext4 data
7. last 4 partitions i.e number 18,19,20, 21 will be erased and repartitioned again.
this is dangerous step. dont do it. if you dont understand what you doing.
8. type following
PHP:
rm 21
rm 20
rm 19
rm 18
9. Now we will create new partitions as we wanted. copy following cammands one by one followed by ENTER.
PHP:
mkpartfs primary ext2 138 538
mkpartfs primary ext2 538 1638
mkpartfs primary ext2 1638 1838
mkpartfs primary ext2 1838 7813
quit
10. after last "QUIT" command it wil say.
PHP:
quit
Information: You may need to update /etc/fstab.
Ignore the warning Reboot into recovery again on pc type
11.
PHP:
adb shell
mke2fs /dev/block/mmcblk0p18
tune2fs -j /dev/block/mmcblk0p18
mke2fs /dev/block/mmcblk0p19
tune2fs -j /dev/block/mmcblk0p19
mke2fs /dev/block/mmcblk0p20
tune2fs -j /dev/block/mmcblk0p20
mke2fs /dev/block/mmcblk0p21
tune2fs -j /dev/block/mmcblk0p21
This will create ext3 partition from ext2
Now convert them to ext4
12.
PHP:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p18
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p19
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p20
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p21
Now lets check everything is ok
13.
PHP:
cd /dev/block
parted mmcblk0
print
This should look like following
14.
PHP:
Number Start End Size File system Name Flags
1 14.7MB 15.7MB 1049kB cal
2 15.7MB 16.0MB 262kB sysparm_dep
3 16.0MB 16.3MB 262kB parm-spml_dep
4 16.3MB 16.5MB 262kB RF_CAL_FILE
5 16.5MB 24.9MB 8389kB KERNEL
6 24.9MB 33.3MB 8389kB RECOVERY
7 33.3MB 53.0MB 19.7MB modem
8 53.0MB 86.2MB 33.3MB reserved
9 86.2MB 88.3MB 2097kB SBL1
10 88.3MB 90.4MB 2097kB SBL2
11 90.4MB 98.8MB 8389kB PARAM
12 98.8MB 99.4MB 524kB DTSBK
13 99.4MB 99.9MB 524kB DTS
14 99.9MB 108MB 8389kB VC-FirmwareBK
15 108MB 117MB 8389kB VC-Firmware
16 117MB 117MB 262kB FOTA_SIG
17 117MB 138MB 21.0MB ext4 efs
18 138MB 538MB 400MB ext4
19 538MB 1638MB 1100MB ext4
20 1638MB 1838MB 200MB ext4
21 1838MB 7813MB 5975MB ext4
So you can see your last partition is now 5.9 GB...
Now flash any rom you wanted,......
ENJOY...
CHECK THIS POST IF SOMETHING GETS MESSED UP ..THIS PROCESS WILL FIX ALL PARTITIONS AND MAKE THEM AS THEY WERE EARLIER
Disclaimer :- I will not be responsible for BRICKED devices.. USE THIS PROCEDRE ON YOUR OWN RISK>>>...................
[/U][/I][/B]​
XDA:DevDB Information
[GUIDE] Increase internal storage for Grand i9082, Tool/Utility for the Samsung Galaxy Grand Duos i9082
Contributors
k2wl, rutvikrvr
Version Information
Status: Stable
Created 2014-09-07
Last Updated 2014-09-16

Reserved

Reserved

reserved.

reserved.for more

How to restore a bricked device or how to restore the device if something goes wrong?
FILES REQUIRED : baffin.pit https://s.basketbuild.com/filedl/devs?dev=rutvikrvr&dl=rutvikrvr/i9082/restore/baffin.pit
ANy stock ROM (link for mk3) : https://docs.google.com/file/d/0B80jsFgYZGOhRHJoY200Zktyekk/edit
ODIN: http://forum.xda-developers.com/attachment.php?attachmentid=1751204&d=1361535462
STEP 1 : In the PIT option add .. the baffin.pit AND IN THE PDA OPTION PUT THE FIRMWARE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
STEP 2 : HIT START AND ONCE ITS COMPLETE YOUR PHONE SHOULD WORK FINE ...THEN YOU CAN ROOT YOUR DEVICE AND TRY THIS PROCEDURE AGAIN :laugh: :laugh:

Internal storage increased on Grand Duos
@k2wl You are an angel for us :laugh: You rockKkK man. Thank you very much for this amazing guide. With this awesome guide you made many Grand duos users on XDA forum indebted to you. :good::good::good:
PS : Hey members, See the screenshot of what is going to happen to your internal storage of GalaxyGrand Duos after following this guide successfully .

@k2wl Please clear this doubt of mine?. Will this storage space remains same even after restoring nandroid backup whether stock or custom!

Trilochanaaya said:
@k2wl Please clear this doubt of mine?. Will this storage space remains same even after restoring nandroid backup whether stock or custom!
Click to expand...
Click to collapse
I think .. Only if u flash stock via Odin .... Not recovery ... Only then the partition table gets restored

rutvikrvr said:
I think .. Only if u flash stock via Odin .... Not recovery ... Only then the partition table gets restored
Click to expand...
Click to collapse
it remain same after flashing via recovery. nandroid i dont know. never used one...LOL....

Can you plz make a flashable zip as I'm not an expert in this and I didn't understand those codes

Is it safe???
Is It safe i mean if something goes wrong during the process then what will happen to the device?? i have done many tweaks with my phone but 1st time i m a bit scared

k2wl said:
it remain same after flashing via recovery. nandroid i dont know. never used one...LOL....
Click to expand...
Click to collapse
@k2wl Sorry didn't get you! I am thinking that when we backup ROM using TWRP/CWM it's called nandroid backup. I prefer having STOCK ROM backup just to be safe in case something goes wrong while flashing. My question is about this backup, Will these internal storage changes remain?

This method was beta tested by me and @k2wl :good:
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
Trilochanaaya said:
@k2wl Sorry didn't get you! I am thinking that when we backup ROM using TWRP/CWM it's called nandroid backup. I prefer having STOCK ROM backup just to be safe in case something goes wrong while flashing. My question is about this backup, Will these internal storage changes remain?
Click to expand...
Click to collapse
The /system partition's size gets reduced to 1GB using repartitioning AFAIK, so the stock ROM won't probably will not fit on it.

Basic questions(Noobie questions)
#1 - Would work on SGG GT-i9080L ? (Same grand.. just, not duos (?) )
#2 - Are newbies able to do this tutorial withouth knowledge? Just following the steps.
#3 - Would this problem affect on doing this? (SDCard is emulated inside the internal storage so not taking the extsdcard as sdcard.) Link: http://forum.xda-developers.com/galaxy-grand-duos/help/help-single-partition-external-sd-t2866826

GabrielCool1 said:
Basic questions(Noobie questions)
#1 - Would work on SGG GT-i9080L ? (Same grand.. just, not duos (?) )
#2 - Are newbies able to do this tutorial withouth knowledge? Just following the steps.
#3 - Would this problem affect on doing this? (SDCard is emulated inside the internal storage so not taking the extsdcard as sdcard.) Link: http://forum.xda-developers.com/galaxy-grand-duos/help/help-single-partition-external-sd-t2866826
Click to expand...
Click to collapse
#1 Yes.
#2 The thing that matters the most in such cases is to follow the instructions carefully
#3 Your problem is an isolated one for the grand community and I'm not sure it will solve it or not.
Bonus tip: If you can post the result of 'print' (read in OP that command) we may be able to help you.

This guy must be a god's man??

VanshKhanna said:
Can you plz make a flashable zip as I'm not an expert in this and I didn't understand those codes
Click to expand...
Click to collapse
flashable zips often can currupt partitions..i have bad experience in this.
so i suggest. if yo do it carefully..one by one...it will not affect your device...and its one time procedure...
FuTech.360 said:
Is It safe i mean if something goes wrong during the process then what will happen to the device?? i have done many tweaks with my phone but 1st time i m a bit scared
Click to expand...
Click to collapse
only if you currupt boot loader partition...that would be end of it...but if you follow steps one by one...it will work..
GabrielCool1 said:
Basic questions(Noobie questions)
#1 - Would work on SGG GT-i9080L ? (Same grand.. just, not duos (?) )
#2 - Are newbies able to do this tutorial withouth knowledge? Just following the steps.
#3 - Would this problem affect on doing this? (SDCard is emulated inside the internal storage so not taking the extsdcard as sdcard.) Link: http://forum.xda-developers.com/galaxy-grand-duos/help/help-single-partition-external-sd-t2866826
Click to expand...
Click to collapse
as Akiratomorya said.. give log of "print command"
i will help you out.
ishmeet1995 said:
This guy must be a god's man??
Click to expand...
Click to collapse
thanks...

Man thanks

Reza Khan said:
Man u r just awesome keep good works
Click to expand...
Click to collapse
pl dont quote the op ..pl edit ur post

***Meizu MX4 - Partitions Table*** Need help for resize chache and system

MX4-Ubuntu Touch in Cyano
An little video tutorial : https://youtu.be/rzjF2Kiw4Ew
~ # print #show partition table
print #show partition table
/sbin/sh: print: not found
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print #shows partition table
print #shows partition table
print #shows partition table
Model: MMC BWBC3R (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 3670kB 3146kB proinfo
2 3670kB 8913kB 5243kB nvram
3 8913kB 19.4MB 10.5MB ext4 protect1
4 19.4MB 29.9MB 10.5MB ext4 protect2
5 29.9MB 30.1MB 262kB seccfg
6 30.1MB 30.5MB 393kB lk
7 30.5MB 47.3MB 16.8MB boot
8 47.3MB 64.1MB 16.8MB recovery
9 64.1MB 70.4MB 6291kB secro
10 70.4MB 70.9MB 524kB para
11 70.9MB 79.3MB 8389kB logo
12 79.3MB 89.8MB 10.5MB ext4 custom
13 89.8MB 101MB 10.9MB expdb
14 101MB 2265MB 2164MB ext4 system
15 2265MB 3003MB 738MB ext4 cache
16 3003MB 31.3GB 28.2GB ext4 userdata
17 31.3GB 31.3GB 16.8MB flashinfo
Click to expand...
Click to collapse
I can try to resize my userdata for incrise system and cache from recovery--->adb shell--->parted blalbalba
But i need an table of a normal version.

@Danj1
on recovery (philz)
-adb devices
-adb shell
-parted /dev/block/mmcblk0
-unit MB
-print
please share your table

resized my "userdata" losting 2 gb for incrise cache and system but...parted don't accept ext4 only ext2
View attachment 3554921
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Changed "system" and "cache"
View attachment 3554951
from my 32 gb this is the command after deleted 3 partition:
system: + 1 gb (+ o -)
mkpartfs system ext2 101MB 3265MB
cache: + 1 gb (+ o -)
mkpartfs cache ext2 3265MB 5003MB
userdata:- 2 gb
mkpartfs userdata ext2 5003MB 31251MB
--------------------------------------
WAIT DON'T CONSIDER IT GOOD-MY PHONE CAN'T BE FLASHED FROM RECOVERY (wiping and formatting all from recovery and try to reflash cyano )

BOOOM BABY! Wipe and Format : system, data, sd card and cache. Reflash cyano!
View attachment 3554970

@Danj1 you can do it.

Hi,
here is my current partition table:
Model: MMC 032GE4 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 3670kB 3146kB proinfo
2 3670kB 8913kB 5243kB nvram
3 8913kB 19.4MB 10.5MB ext4 protect1
4 19.4MB 29.9MB 10.5MB ext4 protect2
5 29.9MB 30.1MB 262kB seccfg
6 30.1MB 30.5MB 393kB lk
7 30.5MB 47.3MB 16.8MB boot
8 47.3MB 64.1MB 16.8MB recovery
9 64.1MB 70.4MB 6291kB secro
10 70.4MB 70.9MB 524kB para
11 70.9MB 79.3MB 8389kB logo
12 79.3MB 616MB 537MB ext4 custom
13 616MB 629MB 13.0MB expdb
14 629MB 2005MB 1376MB ext4 system
15 2005MB 2122MB 117MB ext4 cache
16 2122MB 31.3GB 29.1GB ext4 userdata
17 31.3GB 31.3GB 16.8MB flashinfo
Click to expand...
Click to collapse

Danj1 said:
Hi,
here is my current partition table:
Click to expand...
Click to collapse
mmm nice

Resized partitions to:
14 629MB 3005MB 2376MB ext4 system
15 3005MB 4005MB 1000MB ext4 cache
16 4005MB 31251MB 27246MB ext4 userdata
Click to expand...
Click to collapse
Currently doing ubuntu device flash. Will report later.
Thank you so much Naphtha. You rock!

Danj1 said:
Resized partitions to:
Currently doing ubuntu device flash. Will report later.
Thank you so much Naphtha. You rock!
Click to expand...
Click to collapse
Goodluck! :')

"$ wget http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
# boot device into fastboot mode
$ fastboot flash recovery recovery.img
# boot device into recovery
$ ubuntu-device-flash touch --device arale --channel
ubuntu-touch/stable/meizu.en"

Hi,
I tried to flash the device with ubuntu-device-flash but recovery afterwards fails. Here is the output:
ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --wipe
2015/11/25 22:09:04 Device is |arale|
2015/11/25 22:09:04 Flashing version 7 from ubuntu-touch/stable/meizu.en channel and server https://system-image.ubuntu.com to device arale
2015/11/25 22:09:04 Start pushing /home/user/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz to device
2015/11/25 22:09:06 Start pushing /home/user/.cache/ubuntuimages/pool/custom-xxxxx.tar.xz to device
2015/11/25 22:09:06 Start pushing /home/user/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2015/11/25 22:09:06 Done pushing /home/user/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz to device
2015/11/25 22:09:06 Start pushing /home/user/.cache/ubuntuimages/pool/device-xxxxx.tar.xz to device
2015/11/25 22:09:06 Done pushing /home/user/.cache/ubuntuimages/gpg/image-master.tar.xz to device
16.00 KB / 282.42 MB [_____________________________________________________________________________________] 0.01 % 79.91 KB/s 1h0m18s2015/11/25 22:09:06 Start pushing /home/user/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
48.00 KB / 282.42 MB [_____________________________________________________________________________________] 0.02 % 119.88 KB/s 40m11s2015/11/25 22:09:06 Done pushing /home/user/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
784.00 KB / 282.42 MB [____________________________________________________________________________________] 0.27 % 105.84 KB/s 45m24s2015/11/25 22:09:13 Done pushing /home/user/.cache/ubuntuimages/pool/custom-xxxxx.tar.xz to device
944.00 KB / 282.42 MB [_____________________________________________________________________________________] 0.33 % 94.31 KB/s 50m56s
1.19 MB / 282.42 MB [________________________________________________________________________________________________________________________________________________________________________________________________________________________________] 0.42 % 82.09 KB/s 58m28s2015/11/25 22:09:21 Done pushing /home/user/.cache/ubuntuimages/pool/device-xxxxx.tar.xz to device
282.42 MB / 282.42 MB [=================================================================================================================================================================================================================================] 100.00 % 173.64 KB/s
2015/11/25 22:36:51 Start pushing /home/user/.cache/ubuntuimages/pool/ubuntu-xxxxx.tar.xz to device
2015/11/25 22:37:29 Done pushing /home/user/.cache/ubuntuimages/pool/ubuntu-xxxxx.tar.xz to device
2015/11/25 22:37:29 Created ubuntu_command: /home/user/.cache/ubuntuimages/ubuntu_commands182902206
2015/11/25 22:37:29 Rebooting into recovery to flash
Failed to enter Recovery
Click to expand...
Click to collapse
After executing ubuntu-device-flash the device switched to blank screen and does not come up anymore. It is not booting up. If I plug it in
to power it won't show any loading screen. I tried all different key combinations (long press power/ power + vol up / power + vol down) but it doesn't wake up.
I even opened the device and disconnected the battery for some time but this didn't help either.
I will continue to get device back. So for now I can NOT recommend this way of flashing.

Back to ubuntu touch from SP Flash Tool. We can't see the name but is the same:View attachment 3555432

Naphtha said:
Back to ubuntu touch from SP Flash Tool. We can't see the name but is the same:View attachment 3555432
Click to expand...
Click to collapse
Will try this later. Must download files first.

Hi,
so here are my results. I think I bricked my phone somehow. Black screen is always present.
If I try to flash with the MTK-Flash-Tool I get the following error:
I then tried to get into fastboot mode and reflash a recovery but even this fails. If I hold power+vol down and connect to my Linux machine I see
the device popping up but I am not possible to make adb or fastboot on device. Here is the lsusb output:
[email protected]:~lsusb
...
Bus 003 Device 037: ID 0e8d:0003 MediaTek Inc. MT6227 phone
...
Click to expand...
Click to collapse
Any ideas how to recover?

First of that: $ ubuntu-device-flash touch --device arale --channel
ubuntu-touch/stable/meizu.en --wipe
have you flashed the ubuntu recovery?

Yes I installed recovery from http://people.canonical.com/~alextu/tangxi/recovery/ before using ubuntu-device-flash.

Lost memory

Hi my phones memory is 9 GB instead of 16 Gb could this be error or how to fix it please help?
Sent from my GT-I9505 using XDA-Developers mobile app

HIS YB said:
Hi my phones memory is 9 GB instead of 16 Gb could this be error or how to fix it please help?
Sent from my GT-I9505 using XDA-Developers mobile app
Click to expand...
Click to collapse
It is no error, it is normal.
Internal storage for user is only 9 GB.
There is no way to change this, except if you use Marshmallow and use the adopted storage option to make the microSD card part of the internal memory.

GDReaper said:
It is no error, it is normal.
Internal storage for user is only 9 GB.
There is no way to change this, except if you use Marshmallow and use the adopted storage option to make the microSD card part of the internal memory.
Click to expand...
Click to collapse
Thanks for the insight but check this for me. Doesn't it mean the firmware was rather installed on the 9gb?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9505 using XDA-Developers mobile app

HIS YB said:
Thanks for the insight but check this for me. Doesn't it mean the firmware was rather installed on the 9gb?
Sent from my GT-I9505 using XDA-Developers mobile app
Click to expand...
Click to collapse
No. 9GB are for user files.
2GB are for cache and 2GB are for system. That's about 13GB in total. I don't know what the missing 3GB are for.

Check this post. It gives a breakdown of every mount point on the S4, including partition size. The OP isn't missing any storage, though he thinks he is.

GDReaper said:
No. 9GB are for user files.
2GB are for cache and 2GB are for system. That's about 13GB in total. I don't know what the missing 3GB are for.
Click to expand...
Click to collapse
Good thus that me am right?
Sent from my GT-I9505 using XDA-Developers mobile app

No, you're not.
/system is 2894MB (2.894GB).
/cache is 2171MB (2.171GB).
/userdata is 9961MB (9.961GB)
That is 15GB of space right there. The remaining GB of space is taken up by a hidden partition of 524MB, with the remaining 476MB or so given over to the rest of the partitions in the chart below, taken from the thread I linked to earlier.
Code:
Number Start End Size File system Name Flags
1 4194kB 17.3MB 13.1MB apnhlos
2 17.3MB 71.3MB 54.0MB mdm
3 71.3MB 71.4MB 131kB sbl1
4 71.4MB 71.7MB 262kB sbl2
5 71.7MB 72.2MB 524kB sbl3
6 72.2MB 74.3MB 2097kB aboot
7 74.3MB 74.8MB 524kB rpm
8 74.8MB 75.4MB 524kB tz
9 75.4MB 92.7MB 17.3MB pad
10 92.7MB 107MB 14.3MB ext4 efs
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 114MB 799kB m9kefs1
14 114MB 115MB 799kB m9kefs2
15 115MB 116MB 799kB m9kefs3
16 116MB 3010MB 2894MB ext4 system
17 3010MB 3018MB 8389kB persist
18 3018MB 5189MB 2171MB ext4 cache
19 5189MB 5195MB 6291kB param
20 5195MB 5205MB 10.5MB boot
21 5205MB 5216MB 10.5MB recovery
22 5216MB 5226MB 10.5MB fota
23 5226MB 5233MB 6291kB backup
24 5233MB 5236MB 3146kB fsg
25 5236MB 5236MB 8192B ssd
26 5236MB 5245MB 9437kB ext4 persdata
27 5245MB 5770MB 524MB ext4 hidden
28 5770MB 5791MB 21.0MB carrier
29 5791MB 15.8GB 9961MB ext4 userdata
You're not missing any space, and never were. On a 16GB device, you lose 6GB right off the top for the system storage. It's going to be roughly the same on any device out there. For example, my Nexus 6 is a 64GB model. I only have 54.64GB available to store files on, as I lost 10.5GB off the top for the system partitions.

Strephon Alkhalikoi said:
No, you're not.
/system is 2894MB (2.894GB).
/cache is 2171MB (2.171GB).
/userdata is 9961MB (9.961GB)
That is 15GB of space right there. The remaining GB of space is taken up by a hidden partition of 524MB, with the remaining 476MB or so given over to the rest of the partitions in the chart below, taken from the thread I linked to earlier.
Code:
Number Start End Size File system Name Flags
1 4194kB 17.3MB 13.1MB apnhlos
2 17.3MB 71.3MB 54.0MB mdm
3 71.3MB 71.4MB 131kB sbl1
4 71.4MB 71.7MB 262kB sbl2
5 71.7MB 72.2MB 524kB sbl3
6 72.2MB 74.3MB 2097kB aboot
7 74.3MB 74.8MB 524kB rpm
8 74.8MB 75.4MB 524kB tz
9 75.4MB 92.7MB 17.3MB pad
10 92.7MB 107MB 14.3MB ext4 efs
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 114MB 799kB m9kefs1
14 114MB 115MB 799kB m9kefs2
15 115MB 116MB 799kB m9kefs3
16 116MB 3010MB 2894MB ext4 system
17 3010MB 3018MB 8389kB persist
18 3018MB 5189MB 2171MB ext4 cache
19 5189MB 5195MB 6291kB param
20 5195MB 5205MB 10.5MB boot
21 5205MB 5216MB 10.5MB recovery
22 5216MB 5226MB 10.5MB fota
23 5226MB 5233MB 6291kB backup
24 5233MB 5236MB 3146kB fsg
25 5236MB 5236MB 8192B ssd
26 5236MB 5245MB 9437kB ext4 persdata
27 5245MB 5770MB 524MB ext4 hidden
28 5770MB 5791MB 21.0MB carrier
29 5791MB 15.8GB 9961MB ext4 userdata
You're not missing any space, and never were. On a 16GB device, you lose 6GB right off the top for the system storage. It's going to be roughly the same on any device out there. For example, my Nexus 6 is a 64GB model. I only have 54.64GB available to store files on, as I lost 10.5GB off the top for the system partitions.
Click to expand...
Click to collapse
Haha okay. But you see, i tried flashing a custom rom and in recovery after i did a full system wipe i still had 9gb meaning the the new custom rom was installed on the the 9gb. Per all that you sent i understand that after installing either new firmware or custom rom i shoulf be left with with 9gb+/- right?
Sent from my GT-I9505 using XDA-Developers mobile app

Strephon Alkhalikoi said:
No, you're not.
/system is 2894MB (2.894GB).
/cache is 2171MB (2.171GB).
/userdata is 9961MB (9.961GB)
That is 15GB of space right there. The remaining GB of space is taken up by a hidden partition of 524MB, with the remaining 476MB or so given over to the rest of the partitions in the chart below, taken from the thread I linked to earlier.
Code:
Number Start End Size File system Name Flags
1 4194kB 17.3MB 13.1MB apnhlos
2 17.3MB 71.3MB 54.0MB mdm
3 71.3MB 71.4MB 131kB sbl1
4 71.4MB 71.7MB 262kB sbl2
5 71.7MB 72.2MB 524kB sbl3
6 72.2MB 74.3MB 2097kB aboot
7 74.3MB 74.8MB 524kB rpm
8 74.8MB 75.4MB 524kB tz
9 75.4MB 92.7MB 17.3MB pad
10 92.7MB 107MB 14.3MB ext4 efs
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 114MB 799kB m9kefs1
14 114MB 115MB 799kB m9kefs2
15 115MB 116MB 799kB m9kefs3
16 116MB 3010MB 2894MB ext4 system
17 3010MB 3018MB 8389kB persist
18 3018MB 5189MB 2171MB ext4 cache
19 5189MB 5195MB 6291kB param
20 5195MB 5205MB 10.5MB boot
21 5205MB 5216MB 10.5MB recovery
22 5216MB 5226MB 10.5MB fota
23 5226MB 5233MB 6291kB backup
24 5233MB 5236MB 3146kB fsg
25 5236MB 5236MB 8192B ssd
26 5236MB 5245MB 9437kB ext4 persdata
27 5245MB 5770MB 524MB ext4 hidden
28 5770MB 5791MB 21.0MB carrier
29 5791MB 15.8GB 9961MB ext4 userdata
You're not missing any space, and never were. On a 16GB device, you lose 6GB right off the top for the system storage. It's going to be roughly the same on any device out there. For example, my Nexus 6 is a 64GB model. I only have 54.64GB available to store files on, as I lost 10.5GB off the top for the system partitions.
Click to expand...
Click to collapse
Haha okay. But you see, i tried flashing a custom rom and in recovery after i did a full system wipe i still had 9gb meaning the the new custom rom was installed on the the 9gb. Per all that you sent i understand that after installing either new firmware or custom rom i shoulf be left with with 9gb+/- right?
HIS YB said:
Haha okay. But you see, i tried flashing a custom rom and in recovery after i did a full system wipe i still had 9gb meaning the the new custom rom was installed on the the 9gb. Per all that you sent i understand that after installing either new firmware or custom rom i shoulf be left with with 9gb+/- right?
Sent from my GT-I9505 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my GT-I9505 using XDA-Developers mobile app

Let's parse your post here.
"...i tried flashing a custom rom and in recovery after i did a full system wipe i still had 9gb...." Your /userdata partition will always be 9.9GB. A small portion of that will be taken by some of the apps Samsung includes on the device in the /system partition. So let's say you're at about 9.7GB, which is about average.
"...meaning the new custom rom was installed on the 9GB." Virtually impossible. In order for a ROM to correctly install it must be installed into the /system partition, or else it will not run.[1] That is one of the first things you learn in developing a ROM, and can be easily verified just by opening up the zip file and looking at the installer script located somewhere in the META-INF directory.
"Per all that you sent i understand that after installing either new firmware or custom rom i shoulf be left with with 9gb+/- right?" Yep. It seems to me that the confusion stems from a misconception. A custom ROM when installed does not delete any files in the internal storage except for those attached to a /system app.
For example, last weekend I installed Pure Nexus onto my Nexus 6. This was a clean install. Yet after I was done, not only were all my music and video files present, but also my books and my app backups. The Nexus 6 does not have a MicroSD slot, so everything is on internal storage. If Pure Nexus, or any ROM for that matter deleted those files, end users would be up in arms over that and the developers would be drawn and quartered.
The point here is that anything you added onto the /userdata partition prior to changing ROMs will still be present after the new ROM has booted up. Therefore, your stuff should still be there. If it's not there, then something else is taking up the space. That something else however is not a ROM.[2]
[1][2]The only exception to the above is if the device has been modified to support multiple ROMs using Safestrap recovery if owning an AT&T or Verizon S4, or MultiROM for anything else. The second and subsequent ROMs could then be installed on the internal storage.

Partitiontable Z3+/Z4 (For who it might interest)

Here, maybe you might need the partition table of our lovely device(s) somehow and are too lazy or have no possibility to get it
1 0.13MB 2.23MB 2.10MB TA
2 4.19MB 21.0MB 16.8MB ext4 LTALabel
3 21.0MB 105MB 83.9MB fat16 modem
4 105MB 105MB 0.13MB pmic
5 105MB 105MB 0.13MB alt_pmic
6 105MB 105MB 0.00MB limits
7 105MB 106MB 1.05MB DDR
8 106MB 106MB 0.26MB apdp
9 106MB 107MB 0.26MB msadp
10 107MB 107MB 0.00MB dpo
11 107MB 107MB 0.52MB hyp
12 107MB 108MB 0.52MB alt_hyp
13 109MB 111MB 1.57MB fsg
14 111MB 111MB 0.01MB ssd
15 111MB 112MB 1.05MB sbl1
16 112MB 113MB 1.05MB alt_sbl1
17 113MB 115MB 1.57MB modemst1
18 117MB 119MB 1.57MB modemst2
19 119MB 119MB 0.26MB s1sbl
20 119MB 120MB 0.26MB alt_s1sbl
21 120MB 120MB 0.13MB sdi
22 120MB 120MB 0.13MB alt_sdi
23 120MB 121MB 1.05MB tz
24 121MB 122MB 1.05MB alt_tz
25 122MB 122MB 0.52MB rpm
26 122MB 123MB 0.52MB alt_rpm
27 123MB 124MB 1.05MB aboot
28 124MB 125MB 1.05MB alt_aboot
29 125MB 192MB 67.1MB boot
30 192MB 226MB 33.6MB rdimage
31 226MB 259MB 33.6MB ext4 persist
32 259MB 326MB 67.1MB FOTAKernel
33 326MB 327MB 1.05MB misc
34 327MB 328MB 0.52MB keystore
35 328MB 328MB 0.00MB devinfo
36 328MB 328MB 0.52MB config
37 331MB 436MB 105MB rddata
38 436MB 447MB 10.5MB ext4 apps_log
39 449MB 466MB 16.8MB ext4 diag
40 466MB 780MB 315MB ext4 oem
41 780MB 990MB 210MB ext4 cache
42 990MB 25753MB 24763MB ext4 userdata
43 25753MB 31266MB 5513MB ext4 system
Click to expand...
Click to collapse

KuroTheBang said:
Here, maybe you might need the partition table of our lovely device(s) somehow and are too lazy or have no possibility to get it
Click to expand...
Click to collapse
Thanks. Do you know if any of these partitions contain the boot splash image?

I don't know tbh, I can look these days if you want

Install original firmware

Hi. I had lineage os installed on my phone. Now i want to restore it to original. I can flash original firmware from there https://developers.google.com/android/images#occam without any error. The problem is during boot. It boot endless. I wait couple hours without any effect. I installed twrp and check partitions but it looks ok
Bash:
~ # ./parted /dev/block/mmcblk0 p
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.2MB 524kB sbl1
3 68.2MB 68.7MB 524kB sbl2
4 68.7MB 70.8MB 2097kB sbl3
5 70.8MB 71.3MB 524kB tz
6 71.3MB 94.4MB 23.1MB boot
7 94.4MB 117MB 23.1MB recovery
8 117MB 118MB 799kB m9kefs1
9 118MB 119MB 799kB m9kefs2
10 119MB 120MB 799kB m9kefs3
11 120MB 121MB 524kB rpm
12 121MB 121MB 524kB aboot
13 121MB 122MB 524kB sbl2b
14 122MB 124MB 2097kB sbl3b
15 124MB 124MB 524kB abootb
16 124MB 125MB 524kB rpmb
17 125MB 125MB 524kB tzb
18 125MB 126MB 524kB metadata
19 126MB 143MB 16.8MB misc
20 143MB 159MB 16.8MB ext4 persist
21 159MB 1040MB 881MB ext4 system
22 1040MB 1627MB 587MB ext4 cache
23 1627MB 7817MB 6190MB ext4 userdata
24 7817MB 7818MB 524kB DDR
25 7818MB 7818MB 507kB grow
Do you have any idea what is wrong?

skoczo said:
Hi. I had lineage os installed on my phone. Now i want to restore it to original. I can flash original firmware from there https://developers.google.com/android/images#occam without any error. The problem is during boot. It boot endless. I wait couple hours without any effect. I installed twrp and check partitions but it looks ok
Bash:
~ # ./parted /dev/block/mmcblk0 p
Model: MMC 016G92 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.2MB 524kB sbl1
3 68.2MB 68.7MB 524kB sbl2
4 68.7MB 70.8MB 2097kB sbl3
5 70.8MB 71.3MB 524kB tz
6 71.3MB 94.4MB 23.1MB boot
7 94.4MB 117MB 23.1MB recovery
8 117MB 118MB 799kB m9kefs1
9 118MB 119MB 799kB m9kefs2
10 119MB 120MB 799kB m9kefs3
11 120MB 121MB 524kB rpm
12 121MB 121MB 524kB aboot
13 121MB 122MB 524kB sbl2b
14 122MB 124MB 2097kB sbl3b
15 124MB 124MB 524kB abootb
16 124MB 125MB 524kB rpmb
17 125MB 125MB 524kB tzb
18 125MB 126MB 524kB metadata
19 126MB 143MB 16.8MB misc
20 143MB 159MB 16.8MB ext4 persist
21 159MB 1040MB 881MB ext4 system
22 1040MB 1627MB 587MB ext4 cache
23 1627MB 7817MB 6190MB ext4 userdata
24 7817MB 7818MB 524kB DDR
25 7818MB 7818MB 507kB grow
Do you have any idea what is wrong?
Click to expand...
Click to collapse
If your stock firmware installed correctly you shouldn't have root any longer. How did you install TWRP? How did you install your firmware? flash-all.bat?

Tulsadiver said:
If your stock firmware installed correctly you shouldn't have root any longer. How did you install TWRP? How did you install your firmware? flash-all.bat?
Click to expand...
Click to collapse
So when i figure out that stock rom don't want to boot i installed twrp from command line by
Code:
sudo fastboot flash recovery twrp-3.5.0_9-0-mako.img
to check partitions.
I installed stock rom by executing
Code:
sudo ./flash-all.sh

I see that i have 16G version but from partitions it looks like 8G version. Can it be a problem? How to restore partitions to original?

Your firmware should take care of everything. Did you edit the flash-all.sh? Take off the -w?
I've never used sudo before when flashing mine.

Tulsadiver said:
Your firmware should take care of everything. Did you edit the flash-all.sh? Take off the -w?
I've never used sudo before when flashing mine.
Click to expand...
Click to collapse
No i didn't edit files from google. Sudo is needed for fastboot execution on my system(manjaro). Then this command is run with higher privileges.

skoczo said:
No i didn't edit files from google. Sudo is needed for fastboot execution on my system(manjaro). Then this command is run with higher privileges.
Click to expand...
Click to collapse
Have you tried a factory reset from within TWRP?
It's been a while since I've had a working TWRP.

Tulsadiver said:
Have you tried a factory reset from within TWRP?
It's been a while since I've had a working TWRP.
Click to expand...
Click to collapse
Tulsadiver said:
Have you tried a factory reset from within TWRP?
It's been a while since I've had a working TWRP.
Click to expand...
Click to collapse
I have some progress. I run stock firmware but with some additional steps. This is what i did:
- install stock rom
- install clockwork or twrp
- boot to clockwork
- start `adb shell`
- execute `mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p23` in shell
But if i flash it again i need to do this procedure again. I don't understand why. I can't also do factory reset in twrp because it shows that can't mount some partitions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can do factory reset after calling `mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p23` in adb shell

I started stock android and did some configuration. It looks that system is working. Now as a test i flash stock firmware again and i have boot loop again. Probably i need do the procedure one again. Do you have any idea why? And how to fix this? i see that cache also can't be mounted after flash stock rom so i did `mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p22` and now it can be mounted. But why i need to do this? Why stock rom is not working? And this happen each time when i flash stock rom.
There is also such thing that if i don't execute `mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p2` after flashing lineage os is showing screen that device is encrypted. Then i need to login do adb shell and execute mke2fs. This is wired that i need to do this every time when i flash device.

skoczo said:
I see that i have 16G version but from partitions it looks like 8G version. Can it be a problem? How to restore partitions to original?
Click to expand...
Click to collapse
You can find the Solution here:
[TUTORIAL]How to unbrick your N4
How to unbrick your N4 I'm not responsible for anything that happens with your device! I accidently flashed a S4 ROM. After I noticed that, I tried to flash a factory image, but it booted for a very long time and WiFi, signal and other radio...
forum.xda-developers.com

Akhilesh S V said:
You can find the Solution here:
[TUTORIAL]How to unbrick your N4
How to unbrick your N4 I'm not responsible for anything that happens with your device! I accidently flashed a S4 ROM. After I noticed that, I tried to flash a factory image, but it booted for a very long time and WiFi, signal and other radio...
forum.xda-developers.com
Click to expand...
Click to collapse
I solve my problem by following this instruction https://forums.androidcentral.com/n...3923-guide-nexus-4-factory-image-restore.html
I think that key was those commands:
- fastboot erase boot
- fastboot erase cache
- fastboot erase recovery
- fastboot erase system
- fastboot erase userdata
- fastboot oem lock
- fastboot oem unlock