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
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
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.
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 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.
Hello I have a machine Redmi2 that does not boot, only boots with fastboot when I pressed the power off button ans Vol - button
I can execute fastboot commands.
For example:
fastboot devices
Click to expand...
Click to collapse
967354587d12 fastboot
Click to expand...
Click to collapse
fastboot oem device-info
Click to expand...
Click to collapse
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
finished. total time: 0.004s
Click to expand...
Click to collapse
I could dowloaded various rom (official from xiaomi and not official like aosp-caf_wt88047_64-21-05-2017-eng.pirej.zip or xiaomi-miui-hellas-5.1_wt88047_V8_XTRVbeta2_7.2.24.zip) but I can install a new system in this machine.
First I try to unlock the bootloader with official method from Xiaomi but the result is error.
Now I try to boot with twrp and this is works.
To boot with twrp I cam execute this with fastboot
fastboot flash recovery twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'recovery' (11426 KB)...
OKAY [ 0.360s]
writing 'recovery'...
OKAY [ 0.184s]
finished. total time: 0.544s
Click to expand...
Click to collapse
fastboot flash boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
target reported max download size of 268435456 bytes
sending 'boot' (11426 KB)...
OKAY [ 0.361s]
writing 'boot'...
OKAY [ 0.132s]
finished. total time: 0.493s
Click to expand...
Click to collapse
And with this comand boots the machine with twrp
fastboot boot twrp_arm64_3.1.1.img
Click to expand...
Click to collapse
When machine boots I have access to external card from my PC and I can put the rom to try to install.
When try to clean the partitions I can not do it:
This is the errors
Error al desmontar '/system' (invalid argument)
Error al desmontar '/data' (invalid argument)
Error al desmontar '/cache' (invalid argument)
Incapaz de montar almacenamiento
Click to expand...
Click to collapse
When I try to install RR-N-v5.8.3-20170516-wt88047-OFFICIAL.zip for example I can not install this rom.
Do you know if it is possible install a rom with bootloader locked?
Doy you know if it is possible unlocked the bootloader if xiaomi unlocker does not works?
Any ideas to install a rom in this machine?
Best regards.
i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?
AKHILR4J said:
i heard that redmi2 has unlocked bootloader and you are using twrp arm64 ? try official twrp and install rom ?
Click to expand...
Click to collapse
Thanks for your help,
I have downloaded the lastest twrp img from redmi 2, and I have the same problems.
Machine boots with twrp but I can not write in the internal partitions and I can not install a rom.
I think that I need unlock the bootloader to can to modify the android partitions but I do not know to do it.
try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS
Liquid2 said:
try this one
when in twrp, open mount, give check to system, but uncheck "mount system partition read-only"
then try flash the custom rom
when tried "fastboot oem device-info" to my redmi 2 it also show "(bootloader) Device unlocked: false"
yet i can install just now, LineageOS
Click to expand...
Click to collapse
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.
Hello again, I have tried to mount /system with a terminal in TWRP with this command
Code:
# Montamos la carpeta /system como lectura(r) y escritura(w)
mount -o remount,rw /system
but the problem is my /proc/mounts file
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=967420k,nr_inodes=153983,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=967420k,nr_inodes=153983 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p25 /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk1p1 /external_sd vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /firmware vfat rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
Do you know how can I can change this file to include the /system partition to mount read/write and I can install a rom os.
Regards,
jriosa said:
Hello, thanks for your help, but when I open Mount, only I can check Firmware, Persist, Micro SDCard and I can check Mount system partition read only.
I can not check System, Data, Cache and when I select Storage (Internal Storage (0MB).
I can use TWRP becuase I execute fastboot boot twrp-3.1.1-0-wt88047.img, ¿it is possible open twrp with any parameters?
Regards, Julio.
Click to expand...
Click to collapse
have u tried another twrp?? make sure it for your device
Liquid2 said:
have u tried another twrp?? make sure it for your device
Click to expand...
Click to collapse
Thanks for your help, I have tried different versions from twrp with the same result.
Regards, Julio.
sori, cant help much, maybe
i myself in very newbie
how about if you flash fresh with flashboot rom using miflash, see if it can boot into official miui first
then you can try install twrp again and flash custom rom
have you tried twrp
Hello Now I access to android with adb.
When I boot the android with TWRP, I can access with my PC using adb.
I execute this.
adb root
Click to expand...
Click to collapse
adb shell
Click to expand...
Click to collapse
This is the partitions on my machine
~ # cat /proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1 mmcblk0p16
179 17 8 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 32 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 16 mmcblk0p21
179 22 32768 mmcblk0p22
179 23 1048576 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 512 mmcblk0p27
179 28 32 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 13557743 mmcblk0p30
179 32 4096 mmcblk0rpmb
179 64 30375936 mmcblk1
179 65 30371840 mmcblk1p1
Click to expand...
Click to collapse
~ # cd /dev
/dev # find -inme mmcblk0
find: unrecognized: -inme
Segmentation fault
/dev # find -iname mmcblk0
./block/mmcblk0
./block/platform/soc.0/7824900.sdhci/mmcblk0
Click to expand...
Click to collapse
I have added parted to managed partitions in my machine
To see parttions in my disk
~ # /sbin/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
Click to expand...
Click to collapse
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 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
Click to expand...
Click to collapse
To see my partitions
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 32.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 13.4G 15.6G 46% /external_sd
Click to expand...
Click to collapse
I think that I can not install a new rom (offcial or unofficial) because the system I can not access to partitions /system for example and I think that system partitions is mmcblk0p23.
Do you know how I can modify my partitions to see in df -h and launch a new rom with twrp?
Thanks a lot,
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
Click to expand...
Click to collapse
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
jriosa said:
Hello again, I download parted soft to try to create the partitions
I execute parted and I try to delete the partitions.
For example:
I execute
parted /dev/block/mmcblk0
I think that this is my internal sd
I execute rm 30 to try to delete the last partition (userdata)
but when I see the partitions with command p, rm does not delete the partition and I can nor create it again.
Do you know how can I delete the partitions?
Best regards.
Click to expand...
Click to collapse
Have you unmounted the data partition in twrp before executing the rm command?
SidOfficial said:
Have you unmounted the data partition in twrp before executing the rm command?
Click to expand...
Click to collapse
This is my commands and my point mounts are
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
Click to expand...
Click to collapse
I see a new error
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
Click to expand...
Click to collapse
maybe the first partition I think is OK
~ # parted /dev/block/mmcblk0p1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p1: 67.1MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 67.1MB 67.1MB fat16
Click to expand...
Click to collapse
adb shell
~ # cp /external_sd/parted /sbin/parted
~ # chmod +x /sbin/parted
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 944.7M 156.0K 944.6M 0% /dev
tmpfs 944.7M 28.0K 944.7M 0% /tmp
/dev/block/mmcblk1p1 29.0G 14.9G 14.0G 52% /external_sd
~ # 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) unit MiB
unit MiB
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) rm 30
rm 30
(parted) p
p
Model: MMC HAG2e (sd/mmc)
Disk /dev/block/mmcblk0: 15032MiB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 64.0MiB 128MiB 64.0MiB fat16 modem
2 128MiB 128MiB 0.50MiB sbl1
3 129MiB 129MiB 0.50MiB sbl1bak
4 129MiB 130MiB 1.00MiB aboot
5 130MiB 131MiB 1.00MiB abootbak
6 131MiB 131MiB 0.50MiB rpm
7 132MiB 132MiB 0.50MiB rpmbak
8 132MiB 132MiB 0.50MiB tz
9 133MiB 133MiB 0.50MiB tzbak
10 133MiB 133MiB 0.50MiB hyp
11 134MiB 134MiB 0.50MiB hypbak
12 134MiB 135MiB 1.00MiB pad
13 135MiB 136MiB 1.50MiB modemst1
14 137MiB 138MiB 1.50MiB modemst2
15 138MiB 139MiB 1.00MiB misc
16 139MiB 139MiB 0.00MiB fsc
17 139MiB 139MiB 0.01MiB ssd
18 139MiB 149MiB 10.0MiB splash
19 192MiB 192MiB 0.03MiB DDR
20 192MiB 194MiB 1.50MiB fsg
21 194MiB 194MiB 0.02MiB sec
22 194MiB 226MiB 32.0MiB boot
23 226MiB 1250MiB 1024MiB system
24 1250MiB 1570MiB 320MiB cache
25 1570MiB 1602MiB 32.0MiB ext4 persist
26 1602MiB 1634MiB 32.0MiB recovery
27 1664MiB 1664MiB 0.50MiB keystore
28 1665MiB 1665MiB 0.03MiB config
29 1665MiB 1729MiB 64.0MiB oem
30 1792MiB 15032MiB 13240MiB userdata
(parted) q
q
Information: You may need to update /etc/fstab.
~ # parted /dev/block/mmcblk0p30
Error: Could not stat device /dev/block/mmcblk0p30 - No such file or directory.
Retry/Cancel? C
C
~ # 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 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 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
(parted)
Click to expand...
Click to collapse
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?
jriosa said:
This is my commands and my point mounts are
I see a new error
maybe the first partition I think is OK
Do you know Iif it is possible to clean all disk and I can recreate /system, /cache, /persist, /firmware and /data partitions?
Click to expand...
Click to collapse
Yes, you can recreate all the partitions and can even resize the system and data partitions. Head over to this link https://forum.xda-developers.com/redmi-2/how-to/wt88047-redmi-2-resize-partition-t3612933