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.
Related
As far as I know, there is:
/boot
/bootloader
/userdata
/system
/cache
/recovery
/radio
Is there a way for me to create a new partition on the NAND to which I can write to and from?
Sinfamy said:
As far as I know, there is:
/boot
/bootloader
/userdata
/system
/cache
/recovery
/radio
Is there a way for me to create a new partition on the NAND to which I can write to and from?
Click to expand...
Click to collapse
There are actually more partitions that you thought.
Code:
# 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) p
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 15.8GB 14.1GB ext4 userdata
24 15.8GB 15.8GB 524kB DDR
25 15.8GB 15.8GB 507kB grow
Hey,
My phone display 16Gb instead of 32Gb !
I had restored my phone multiple times lately because of some things I shouldn't do..
I've a LG G2 D802, get back to stock rom (KOR) rooted but no recovery as I have "adbd cannot run as root in production builds" issue.
So if anyone know how to go back to normal or just install a recovery in order to go under a non stock rom, i'd be glad to follow his advice.
By the way when I go to hardware information on Android I see 32Gb but anywhere else even on PC i see 16Gb (10 actually).
You may want to have a look here http://forum.xda-developers.com/showthread.php?t=2432476 sounds like you have to install a kdz from a country that uses 32gb G2. I had a similar issue when restoring a stock rom on my G pro once, some kdz files are for 16gb variants.
PallyBud said:
You may want to have a look here http://forum.xda-developers.com/showthread.php?t=2432476 sounds like you have to install a kdz from a country that uses 32gb G2. I had a similar issue when restoring a stock rom on my G pro once, some kdz files are for 16gb variants.
Click to expand...
Click to collapse
Ok, thank you! I'll give it a shot tomorow, internet is too slow here ...
Will say if it worked tomorow! Thanks again!
shark_max said:
Ok, thank you! I'll give it a shot tomorow, internet is too slow here ...
Will say if it worked tomorow! Thanks again!
Click to expand...
Click to collapse
I do not think it will help you might have a partition problem like many of us have had. Try this http://forum.xda-developers.com/showpost.php?p=50790181&postcount=49
K,
Kickoff said:
I do not think it will help you might have a partition problem like many of us have had. Try this http://forum.xda-developers.com/showpost.php?p=50790181&postcount=49
K,
Click to expand...
Click to collapse
Hey!
I was actually trying it on my own as I find it on another forum but the output is different than yours :
Code:
[email protected]:/system/bin # ./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) p
p
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 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 15.7GB 11.6GB ext4 userdata
36 15.7GB 15.8GB 37.7MB grow
Edit : ok, I will try to be a better student and try to actually read your post.. I will send the result later..
Edit2 : Thanks a lot, it worked perfectly!
Hello everyone,
Instead of hijacking the topic of gkalen i'am going to expose my problem here, is my phone dead ?!
5 days after installing the miui v7 global rom my phone rebooted and got stuck at Mi logo.
Since then i dont have acces to xiaomi recover only to fastboot mode.
I cant use miflash because i kept getting the following error: [00000AFC]86d6ac8f 0.27 FAILED (remote: failed to write partition)
Mi PC suite isnt working either.
Today i managed to access TWRP recovery and as well adb shell, but installaing via recovery is not working as well and I get the following message:
E:Unable to mount '/data'
Same error using adb shell.
So I think the problem is linked to the partitions, let me show you thoses logs:
/dev/block/mmcblk0p24 /cache ext4 rw
/dev/block/mmcblk0p23 /system ext4 rw
/dev/block/mmcblk0p30 /data ext4 rw
/dev/block/mmcblk0p1 /firmware vfat rw
/dev/block/mmcblk0p25 /persist ext4 rw
/dev/block/mmcblk1p1 /external_sd vfat rw
/usb-otg vfat rw
Parted /dev/block/mmcblk0p24
print
Error: /dev/block/mmcblk0p24: unrecognised disk label
Parted /dev/block/mmcblk0p23 => Fine
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p23: 1074MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 1074MB 1074MB ext4
Parted /dev/block/mmcblk0p30
print
]Error: /dev/block/mmcblk0p30: unrecognised disk label
I'am getting desesperate, anyone knows how to fix partitions issue ?
Actually i could need some help, if someone would be kind enough to run the following command with adb shell:
parted /dev/block/mmcblk0
print
And give me the output, here is mine and I guess i'am missing a few bits...:
Model: MMC HAG2e (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 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 524kB tz
9 139MB 139MB 524kB tzbak
10 139MB 140MB 524kB hyp
11 140MB 141MB 524kB hypbak
12 141MB 142MB 1049kB pad
13 142MB 143MB 1573kB modemst1
14 143MB 145MB 1573kB modemst2
15 145MB 146MB 1049kB misc
16 146MB 146MB 1024B fsc
17 146MB 146MB 8192B ssd
18 146MB 156MB 10.5MB splash
19 201MB 201MB 32.8kB DDR
20 201MB 203MB 1573kB fsg
21 203MB 203MB 16.4kB sec
22 203MB 237MB 33.6MB boot
23 237MB 1310MB 1074MB ext4 system
24 1310MB 1646MB 336MB cache
25 1646MB 1679MB 33.6MB ext4 persist
26 1679MB 1713MB 33.6MB recovery
27 1745MB 1745MB 524kB keystore
28 1745MB 1745MB 32.8kB config
29 1745MB 1812MB 67.1MB oem
30 1879MB 15.8GB 13.9GB userdata
Hi,
were you abel to solve your problem or have you received any reply to it? I also think that my internal SD card is corrupted and to install a new ROM I have to set it up again. I always get the following error messagre if I want to flash it with Mi-flash
"remote: failed to write partition" .
If I check it with fastboot in detail, I miss the partition with the name "partition". This is the first one which is flashed, but I do not have.
My phone is 2014813.
I hope somebody may help me.
Hello,
did any of you ever get this fixed ? Would be nice to hear the solution because I am faced with the same problem unfortunatly....
tia !
Did anyone here fixed this issue? Or is it hardbricked forever?
I never was able to repair it unfortunatly.
Hi,
So since my the Gionee Elife E7 has 32GB of space but only 4 GB is for apps it's quite annoying to delete something all the time.
Has anyone had any luck partitioning ? Took a look at the partition table
Code:
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 32.8kB dbi
4 201MB 201MB 32.8kB DDR
5 268MB 279MB 10.5MB aboot
6 279MB 279MB 512kB rpm
7 336MB 357MB 21.0MB boot
8 403MB 403MB 512kB tz
9 403MB 404MB 1049kB pad
10 404MB 406MB 1573kB modemst1
11 406MB 407MB 1573kB modemst2
12 470MB 1812MB 1342MB ext4 system
13 1812MB 6107MB 4295MB ext4 userdata
14 6107MB 6140MB 33.6MB ext4 persist
15 6140MB 6543MB 403MB ext4 cache
16 6543MB 6564MB 21.0MB recovery
17 6564MB 6566MB 1573kB fsg
18 6577MB 6577MB 1024B fsc
19 6577MB 6577MB 8192B ssd
20 6577MB 30.9GB 24.4GB fat32 udisk
21 30.9GB 30.9GB 10.5MB splash
22 30.9GB 31.3GB 322MB grow
The partition 13 "userdata" seems to be the partition for apps and the partition 20 "udisk" is the storage for files only.
Do I need to delete all the partitions from 13 to 20 in order to extend userdata from 4295MB to 8192MB and then proceed to add 14-20 again?
Also if I performed a full backup in twrp and moved it to my PC, is it still risky to do this? Since the recovery partition is between the 13 and 20 as well
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