keep getting blank IMEI and unknow baseband, so i run ~ # parted /dev/block/mmcblk0 and noticed efs is not EXT4 file system as it should be. Could you please help how to fix mine partition. here how it looked now.
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 msftres
12 15.2GB 15.8GB 537MB ext4 HIDDEN
Wrong section and there is a topic related to your issue already here:
[Guide]How to revive your bricked Gnote
EFS IS EXT4 DON'T MESS WITH IT IF YOU DON'T HAVE A DUMP OF YOUR EFS PARTITION!
If you don't have a dump of your EFS i wouldn't mess with it!
With 7 posts and you are messing with parted?
Btw, use the topic that i quoted... you will find help there!
Reported!
Thread moved and closed
Do not post questions in Development, and since you've been given good advice, thread closed.
Related
Hello,
My question is related to this article "An easy guide to relocate faulty partition for super-brick Note".
Can someone briefly explain the purpose of Galaxy Note Partitions?
Partitions:
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS - contains a lot of information about your phone, f.e: wifi/bt mac address and your IMEI
2 25.2MB 26.5MB 1311kB SBL1 - secondary bootloader, find OS???
3 27.3MB 28.6MB 1311kB SBL2 - download mode + sbl1???
Two-stage bootloader, the Primitive Bootloader (PBL) and Secondary Bootloader (SBL)??? A piece of code that runs before the operating system is started when the phone is turned on. It tells the phone what to boot eg normal boot, recovery mode, download mode.
4 29.4MB 37.7MB 8389kB PARAM - contains paramaters to run the phone and required for boot
5 37.7MB 46.1MB 8389kB KERNEL - contain kernel for your ROM ???
6 46.1MB 54.5MB 8389kB RECOVERY - the recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it.
7 54.5MB 264MB 210MB ext4 CACHE - this is the partition where Android stores frequently accessed data and app components
8 264MB 281MB 16.8MB MODEM - part of ROM, Manages radio signals eg Wifi, bluetooth, mobile network
9 281MB 1174MB 893MB ext4 FACTORYFS - ???
10 1174MB 3322MB 2147MB ext4 DATAFS - partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go ... anymore???
11 3322MB 15.2GB 11.9GB fat32 UMS - USB Mass Storage (UMS) allows a portion of the phone to shared on the PC, when the phone is plugged into the PC via USB cable. Since UMS is a block-based protocol, it requires "ownership" of the filesystem being shared. In technical terms, this means that only the contents of an entire partition may be shared. ???
12 15.2GB 15.8GB 537MB ext4 HIDDEN - ???
Any links to explain mentioned above?
AndrewASB said:
Hello,
My question is related to this article "An easy guide to relocate faulty partition for super-brick Note".
Can someone briefly explain the purpose of Galaxy Note Partitions?
Partitions:
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS - contains a lot of information about your phone, f.e: wifi/bt mac address and your IMEI
2 25.2MB 26.5MB 1311kB SBL1 - secondary bootloader, find OS???
3 27.3MB 28.6MB 1311kB SBL2 - download mode + sbl1???
Two-stage bootloader, the Primitive Bootloader (PBL) and Secondary Bootloader (SBL)??? A piece of code that runs before the operating system is started when the phone is turned on. It tells the phone what to boot eg normal boot, recovery mode, download mode.
4 29.4MB 37.7MB 8389kB PARAM - contains paramaters to run the phone and required for boot
5 37.7MB 46.1MB 8389kB KERNEL - contain kernel for your ROM ???
6 46.1MB 54.5MB 8389kB RECOVERY - the recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it.
7 54.5MB 264MB 210MB ext4 CACHE - this is the partition where Android stores frequently accessed data and app components
8 264MB 281MB 16.8MB MODEM - part of ROM, Manages radio signals eg Wifi, bluetooth, mobile network
9 281MB 1174MB 893MB ext4 FACTORYFS - ???
10 1174MB 3322MB 2147MB ext4 DATAFS - partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go ... anymore???
11 3322MB 15.2GB 11.9GB fat32 UMS - USB Mass Storage (UMS) allows a portion of the phone to shared on the PC, when the phone is plugged into the PC via USB cable. Since UMS is a block-based protocol, it requires "ownership" of the filesystem being shared. In technical terms, this means that only the contents of an entire partition may be shared. ???
12 15.2GB 15.8GB 537MB ext4 HIDDEN - ???
Any links to explain mentioned above?
Click to expand...
Click to collapse
I added a thread in Android General.
I think this is also interesting for other phones, and we may get more info this way.
Perhaps you want head over to it?
Would be nice, if you tell there something about this:
can you explain where some of your comments above come from?
especially about SBL1/2 and PARAM, e.g. why do you think SBL2 is for download mode? why do you think PARAM is needed for boot?
did you do own experiments about this?
May I add some of your comments (perhaps modified) to the list?
hey m8´s,
for some reason i need a picture of the partitions from your s3lte. Would be very nice if someone can provide me one
go like this:
You need: ADB & Java SDK installed
1 Reboot to recovery
2 open cmd and start adb
- adb devices
- adb shell
- parted /dev/block/mmcblk0
- (parted) print
the last input should provide you something like:
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB ext4 BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB fat16 RADIO
11 164MB 432MB 268MB TOMBSTONES
12 432MB 1506MB 1074MB ext4 CACHE
13 1506MB 3116MB 1611MB ext4 SYSTEM
14 3116MB 3704MB 587MB ext4 HIDDEN
15 3704MB 3712MB 8389kB OTA
16 3712MB 15.8GB 12.0GB ext4 USERDATA
thank you for the help
best regards
F1tty
Hello Team,
I do have my friend's GT N 7000 16gb., while installting new ROM through ODIN by mistake he has selected PIT ....Anyhow it is booting up and fine.
But now at USB storage space showing as 11.07GB instead of 16gb.
I want to recover 16gb. Kindly advise below steps is correct to bring back to normal.
Burning custom rom gt n 7000 DDLSC through ODIN.
1. Download 16gb GT N 7000 pit file.
2. Download CUSTOM ROM ICS DDLSC
3. IN ODIN select pit and pda to start the process.
Is the above procedure is correct to get back 16gb., or any other precautions to be taken.
Kindly advise.
Thanks in advance.
Sathish .J
11.07 GB is the usual storage space that is the UMS partition.. Its normal. Rest of the storage is used for other partitions..
Here is a more clear view
Number Start End Size File system Name
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
So ivee tried lots of things to get my xt1063 running again, but it looks that dont mater what it always comes to the same point, so the las thing i want to try, as i took the phone to a shop and they couldnt fix it , i would like to wipe all of the internal memory.
Is this even posible? i know i will probably kill the phone and its ok, so i boot ir in TWRP , im using a computer with ubuntu, installed the latest adb and fastboot, got into adb shell and issue the parted print command i got this
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) print
print
Model: MMC SEM08G (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 131kB 67.2MB 67.1MB ext4 modem
2 67.2MB 67.8MB 524kB sbl1
3 67.8MB 67.8MB 32.8kB DDR
4 67.9MB 68.9MB 1036kB aboot
5 69.4MB 69.6MB 205kB rpm
6 69.9MB 70.4MB 410kB tz
7 70.5MB 70.5MB 32.8kB sdi
8 70.5MB 71.0MB 524kB utags
9 71.0MB 73.1MB 2097kB logs
10 73.1MB 75.5MB 2388kB padA
11 75.5MB 76.5MB 1036kB abootBackup
12 77.0MB 77.2MB 205kB rpmBackup
13 77.5MB 78.0MB 410kB tzBackup
14 78.1MB 78.1MB 32.8kB sdiBackup
15 78.1MB 78.6MB 524kB utagsBackup
16 78.6MB 79.7MB 1077kB padB
17 79.7MB 81.3MB 1573kB modemst1
18 81.3MB 82.8MB 1573kB modemst2
19 82.8MB 83.3MB 500kB hob
20 83.3MB 83.4MB 32.8kB dhob
21 83.5MB 85.1MB 1573kB ext2 fsg
22 85.1MB 85.1MB 1024B fsc
23 85.1MB 85.1MB 8192B ssd
24 85.1MB 86.1MB 1049kB sp
25 86.1MB 86.3MB 131kB cid
26 86.3MB 89.4MB 3146kB ext3 pds
27 89.4MB 93.6MB 4194kB logo
28 93.6MB 97.8MB 4194kB clogo
29 97.9MB 106MB 8389kB ext4 persist
30 106MB 107MB 524kB misc
31 107MB 117MB 10.4MB boot
32 117MB 128MB 10.5MB recovery
33 128MB 129MB 1049kB deviceinfo
34 129MB 146MB 16.8MB ext4 ftmlog
35 146MB 706MB 560MB ext4 cache
36 706MB 1863MB 1158MB ext4 system
37 1863MB 1872MB 8389kB kpan
38 1872MB 7784MB 5913MB userdata
So can anyone help to wipe, format or whatever needs to be done to wipe the internal memory. Also, do you guys see any weird partitions taht might not belong there? thanks for any help.
abispac said:
So ivee tried lots of things to get my xt1063 running again, but it looks that dont mater what it always comes to the same point, so the las thing i want to try, as i took the phone to a shop and they couldnt fix it , i would like to wipe all of the internal memory.
Is this even posible? i know i will probably kill the phone and its ok, so i boot ir in TWRP , im using a computer with ubuntu, installed the latest adb and fastboot, got into adb shell and issue the parted print command i got this
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) print
print
Model: MMC SEM08G (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 131kB 67.2MB 67.1MB ext4 modem
2 67.2MB 67.8MB 524kB sbl1
3 67.8MB 67.8MB 32.8kB DDR
4 67.9MB 68.9MB 1036kB aboot
5 69.4MB 69.6MB 205kB rpm
6 69.9MB 70.4MB 410kB tz
7 70.5MB 70.5MB 32.8kB sdi
8 70.5MB 71.0MB 524kB utags
9 71.0MB 73.1MB 2097kB logs
10 73.1MB 75.5MB 2388kB padA
11 75.5MB 76.5MB 1036kB abootBackup
12 77.0MB 77.2MB 205kB rpmBackup
13 77.5MB 78.0MB 410kB tzBackup
14 78.1MB 78.1MB 32.8kB sdiBackup
15 78.1MB 78.6MB 524kB utagsBackup
16 78.6MB 79.7MB 1077kB padB
17 79.7MB 81.3MB 1573kB modemst1
18 81.3MB 82.8MB 1573kB modemst2
19 82.8MB 83.3MB 500kB hob
20 83.3MB 83.4MB 32.8kB dhob
21 83.5MB 85.1MB 1573kB ext2 fsg
22 85.1MB 85.1MB 1024B fsc
23 85.1MB 85.1MB 8192B ssd
24 85.1MB 86.1MB 1049kB sp
25 86.1MB 86.3MB 131kB cid
26 86.3MB 89.4MB 3146kB ext3 pds
27 89.4MB 93.6MB 4194kB logo
28 93.6MB 97.8MB 4194kB clogo
29 97.9MB 106MB 8389kB ext4 persist
30 106MB 107MB 524kB misc
31 107MB 117MB 10.4MB boot
32 117MB 128MB 10.5MB recovery
33 128MB 129MB 1049kB deviceinfo
34 129MB 146MB 16.8MB ext4 ftmlog
35 146MB 706MB 560MB ext4 cache
36 706MB 1863MB 1158MB ext4 system
37 1863MB 1872MB 8389kB kpan
38 1872MB 7784MB 5913MB userdata
So can anyone help to wipe, format or whatever needs to be done to wipe the internal memory. Also, do you guys see any weird partitions taht might not belong there? thanks for any help.
Click to expand...
Click to collapse
my suggestion is to wipe 38 userdata and 35 cache if it doesn't reboot after that then try system (36) but only if you believe you will be able to reflash .... I still think its a corrupt userdata (38) (missing ext 3/4? ) if you can find the correct dd= (linux command ) to wipe / format / repartition this , think HTC and samsungs sometimes suffer this
http://forum.xda-developers.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447 reading / maybe adaptable to fix?
http://android.stackexchange.com/questions/88277/corrupted-data-partition again more info but need to check file system etc
Thanks for the help, so acording to those links i tried
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
and it returned
Code:
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
any idea why?
I think this would not wor either, i formated every single partition or file with this comand
mke2fs /dev/block/platform/msm_sdcc.1/by-name/*****
where ****** i aded the name of the all 38 partition parted tells me i have, everything seems ok i dont get erros, but at the end, same result, reboot the phone to the same state.
Please tell me a simple command ,if theres any, to format the whole internal card....please i dont care about the phone anymore, i just want to know if the internal memory can be erased
abispac said:
Thanks for the help, so acording to those links i tried
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
and it returned
Code:
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
any idea why?
I think this would not wor either, i formated every single partition or file with this comand
mke2fs /dev/block/platform/msm_sdcc.1/by-name/*****
where ****** i aded the name of the all 38 partition parted tells me i have, everything seems ok i dont get erros, but at the end, same result, reboot the phone to the same state.
Please tell me a simple command ,if theres any, to format the whole internal card....please i dont care about the phone anymore, i just want to know if the internal memory can be erased
Click to expand...
Click to collapse
i dont know linux that well, i said ideas - expected you to learn commands are not for your phone , you really need to ask in moto g 1st gen and or linux forum for help as now one here has had this problem , blindly formattting every partiton will kill phone and like I said i think your userdata (data) partition should be ext4 - guessing its just lost its partition table / lable
I believe if you fix 38 userdata partition and only this you will be able to boot or reflash phone
http://forum.xda-developers.com/showthread.php?t=2557781 more ideas but adapt do NOT blindly copy
---------- Post added at 11:30 PM ---------- Previous post was at 11:10 PM ----------
http://androidforums.com/threads/cant-wipe-corrupt-data-bootloop.645860/ READ THIS
---------- Post added 21st February 2015 at 12:07 AM ---------- Previous post was 20th February 2015 at 11:30 PM ----------
Apparently if you relock boot loader then unlock again it formats data and has been used to fix this as a work around.....
http://forum.xda-developers.com/showthread.php?t=2542219&page=136
see posts 1352 and 1353 same problem
reefuge said:
http://forum.xda-developers.com/showthread.php?t=2542219&page=136
see posts 1352 and 1353 same problem
Click to expand...
Click to collapse
thank you ,will take a loo before sending it to motorola tomorrow
delete please, my mistake
im done, sending this to motocare.... thanks again for the help
The following operations are dangerous, and improper operations require 9008 recovery. Please backup the data you need before the next step
I come from China, my English is not good, these words come from Google Translate
Download the file I provided without suffix 0，Remove the attachment suffix APK and change it to 0 without any text and suffix.O file, use the REC file manager to move to the SBIN folder, then use the REC file manager to find the SBIN folder, open it, find the 0 file, and change the 0 file permission to 775.
The red below is the text I entered. You can expand the 5G system partition by pressing the red input.
--------------------------------------
C:\AutumnBox\file\Resources\AdbExecutable>fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.032s]
Finished. Total time: 0.035s
C:\AutumnBox\file\Resources\AdbExecutable>fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
C:\AutumnBox\file\Resources\AdbExecutable>fastboot flash boot twrp-3.4.0-0-Z01RD.img
Sending 'boot_b' (35064 KB) OKAY [ 0.814s]
Writing 'boot_b' OKAY [ 0.135s]
Finished. Total time: 0.960s
C:\AutumnBox\file\Resources\AdbExecutable>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
127|ASUS_Z01R_1:/ # 0 /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
(parted) p
Warning: Not all of the space available to /dev/block/sda appears to be used,
you can fix the GPT to use all of the space (an extra 28 blocks) or continue
with the current setting?
Fix/Ignore? ignore
Model: SAMSUNG KLUDG4U1EA-B0C1 (scsi)
Disk /dev/block/sda: 124GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 24.6kB 32.8kB 8192B ssd
2 32.8kB 1081kB 1049kB misc
3 1081kB 1606kB 524kB keystore
4 1606kB 2130kB 524kB frp
5 2130kB 35.7MB 33.6MB ext4 asdf
6 35.7MB 46.2MB 10.5MB flashlog
7 46.2MB 62.9MB 16.8MB absolute
8 62.9MB 96.5MB 33.6MB ADF
9 96.5MB 130MB 33.6MB ext4 persist
10 130MB 466MB 336MB APD
11 466MB 533MB 67.1MB asusfw
12 533MB 1070MB 537MB ext2 xrom_a
13 1070MB 1606MB 537MB ext2 xrom_b
14 1606MB 4593MB 2986MB ext2 system_a
15 4593MB 7579MB 2986MB ext2 system_b
16 7579MB 124GB 117GB userdata
(parted) rm 14
(parted) rm 15
(parted) rm 16
Error: Partition(s) 16 on /dev/block/sda have been written, but we have been
unable to inform the kernel of the change, probably because it/they are in use.
As a result, the old partition(s) will remain in use. You should reboot now
before making further changes.
Ignore/Cancel? ingnore
0: invalid token: ingnore
Ignore/Cancel? ignore
(parted) ignore
align-check TYPE N check partition N for TYPE(min|opt)
alignment
help [COMMAND] print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE create a new disklabel (partition
table)
mkpart PART-TYPE [FS-TYPE] START END make a partition
name NUMBER NAME name partition NUMBER as NAME
print [devices|free|list,all|NUMBER] display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit exit program
rescue START END rescue a lost partition near START
and END
resizepart NUMBER END resize partition NUMBER
rm NUMBER delete partition NUMBER
select DEVICE choose the device to edit
disk_set FLAG STATE change the FLAG on selected device
disk_toggle [FLAG] toggle the state of FLAG on selected
device
set NUMBER FLAG STATE change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]] toggle the state of FLAG on partition
NUMBER
unit UNIT set the default unit to UNIT
version display the version number and
copyright information of GNU Parted
(parted)
(parted) p
Model: SAMSUNG KLUDG4U1EA-B0C1 (scsi)
Disk /dev/block/sda: 124GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 24.6kB 32.8kB 8192B ssd
2 32.8kB 1081kB 1049kB misc
3 1081kB 1606kB 524kB keystore
4 1606kB 2130kB 524kB frp
5 2130kB 35.7MB 33.6MB ext4 asdf
6 35.7MB 46.2MB 10.5MB flashlog
7 46.2MB 62.9MB 16.8MB absolute
8 62.9MB 96.5MB 33.6MB ADF
9 96.5MB 130MB 33.6MB ext4 persist
10 130MB 466MB 336MB APD
11 466MB 533MB 67.1MB asusfw
12 533MB 1070MB 537MB ext2 xrom_a
13 1070MB 1606MB 537MB ext2 xrom_b
(parted) mkpart
Partition name? []? system_a
File system type? [ext2]? ext2
Start? 1606
End? 7gb
Warning: The resulting partition is not properly aligned for best performance.
Ignore/Cancel? ignore
Error: Partition(s) 16 on /dev/block/sda have been written, but we have been
unable to inform the kernel of the change, probably because it/they are in use.
As a result, the old partition(s) will remain in use. You should reboot now
before making further changes.
Ignore/Cancel? ignore
(parted) p
Model: SAMSUNG KLUDG4U1EA-B0C1 (scsi)
Disk /dev/block/sda: 124GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 24.6kB 32.8kB 8192B ssd
2 32.8kB 1081kB 1049kB misc
3 1081kB 1606kB 524kB keystore
4 1606kB 2130kB 524kB frp
5 2130kB 35.7MB 33.6MB ext4 asdf
6 35.7MB 46.2MB 10.5MB flashlog
7 46.2MB 62.9MB 16.8MB absolute
8 62.9MB 96.5MB 33.6MB ADF
9 96.5MB 130MB 33.6MB ext4 persist
10 130MB 466MB 336MB APD
11 466MB 533MB 67.1MB asusfw
12 533MB 1070MB 537MB ext2 xrom_a
13 1070MB 1606MB 537MB ext2 xrom_b
14 1606MB 7000MB 5394MB ext4 system_a
(parted) mkpart
Partition name? []? system_b
File system type? [ext2]? ext2
Start? 7gb
End? 12gb
Error: Partition(s) 15, 16 on /dev/block/sda have been written, but we have been
unable to inform the kernel of the change, probably because it/they are in use.
As a result, the old partition(s) will remain in use. You should reboot now
before making further changes.
Ignore/Cancel? ignore
(parted) p
Model: SAMSUNG KLUDG4U1EA-B0C1 (scsi)
Disk /dev/block/sda: 124GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 24.6kB 32.8kB 8192B ssd
2 32.8kB 1081kB 1049kB misc
3 1081kB 1606kB 524kB keystore
4 1606kB 2130kB 524kB frp
5 2130kB 35.7MB 33.6MB ext4 asdf
6 35.7MB 46.2MB 10.5MB flashlog
7 46.2MB 62.9MB 16.8MB absolute
8 62.9MB 96.5MB 33.6MB ADF
9 96.5MB 130MB 33.6MB ext4 persist
10 130MB 466MB 336MB APD
11 466MB 533MB 67.1MB asusfw
12 533MB 1070MB 537MB ext2 xrom_a
13 1070MB 1606MB 537MB ext2 xrom_b
14 1606MB 7000MB 5394MB ext4 system_a
15 7000MB 12.0GB 5000MB ext4 system_b
(parted) mkpart
Partition name? []? userdata
File system type? [ext2]? ext2
Start? 12gb
End? 124gb
Error: Partition(s) 15, 16 on /dev/block/sda have been written, but we have been
unable to inform the kernel of the change, probably because it/they are in use.
As a result, the old partition(s) will remain in use. You should reboot now
before making further changes.
Ignore/Cancel? ignore
(parted) p
Model: SAMSUNG KLUDG4U1EA-B0C1 (scsi)
Disk /dev/block/sda: 124GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 24.6kB 32.8kB 8192B ssd
2 32.8kB 1081kB 1049kB misc
3 1081kB 1606kB 524kB keystore
4 1606kB 2130kB 524kB frp
5 2130kB 35.7MB 33.6MB ext4 asdf
6 35.7MB 46.2MB 10.5MB flashlog
7 46.2MB 62.9MB 16.8MB absolute
8 62.9MB 96.5MB 33.6MB ADF
9 96.5MB 130MB 33.6MB ext4 persist
10 130MB 466MB 336MB APD
11 466MB 533MB 67.1MB asusfw
12 533MB 1070MB 537MB ext2 xrom_a
13 1070MB 1606MB 537MB ext2 xrom_b
14 1606MB 7000MB 5394MB ext4 system_a
15 7000MB 12.0GB 5000MB ext4 system_b
16 12.0GB 124GB 117GB ext4 userdata
-------------------------------
The expansion is now complete，But you need to verify the system，Without verification, unlimited FB mode
fastboot flash vbmeta vbmeta.img
-------------------------------------------
The attachment is below
-----------------
View attachment 5100723
View attachment 5100729
View attachment 5100731
View attachment vbmeta.img
xbe28 said:
Download the file I provided without suffix 0
Click to expand...
Click to collapse
I can't find the file