Related
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.
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
My device: MotoX (ghost)
Hey guys,
Today i pushed "parted" to my /sbin, chmodded 0755 and removed/recreated my userdata partition removing 5mb of total.. (to try to solve a known encryption bug of CM). Then, i reboot.
Now MY PHONE LOOKS HARD BRICKED!
How it is possible? i just deleted/recreated the userdata partition,
yes parted create on format ext2, but the next step is to convert to ext4 > f2fs..
but my phone does not start!
Black screen
No fastboot
lsusb does not list the usb connection..
Pressing the ON = doesn't boot
Pressing vol down + power = doesn't boot
Inserting charger = doesn't boot
No Lights on.
Battery is ok (i think), i started working w/ 100%.
full log of my actions here:
Code:
$ adb push sdparted/parted /sbin
3067 KB/s (346680 bytes in 0.110s)
~/droid $ adb shell
~ # ls
boot init.qcom.sh sepolicy
cache init.rc sideload
charger init.recovery.qcom.rc supersu
data license sys
default.prop proc system
dev property_contexts tmp
etc recovery twres
file_contexts res ueventd.qcom.rc
fstab.qcom root ueventd.rc
init sbin usb-otg
init.mmi.boot.sh sdcard
init.mmi.touch.sh seapp_contexts
~ # chmod 0755 /sbin/parted
~ # 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 SEM16G (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 131kB 105MB 105MB ext4 modem
2 105MB 107MB 1536kB sbl1
3 107MB 108MB 1536kB sbl2
4 108MB 109MB 526kB sbl3
5 110MB 111MB 524kB aboot
6 112MB 112MB 145kB rpm
7 112MB 112MB 215kB tz
8 113MB 113MB 524kB utags
9 113MB 114MB 1049kB logs
10 114MB 117MB 3150kB padA
11 117MB 119MB 1536kB sbl2Backup
12 119MB 121MB 2097kB sbl3Backup
13 121MB 123MB 1536kB abootBackup
14 123MB 123MB 512kB rpmBackup
15 123MB 124MB 512kB tzBackup
16 124MB 124MB 524kB utagsBackup
17 124MB 126MB 1671kB padB
18 126MB 129MB 3146kB modemst1
19 129MB 132MB 3146kB modemst2
20 132MB 134MB 2097kB mbl
21 134MB 135MB 655kB hob
22 135MB 135MB 8192B dhob
23 135MB 143MB 8389kB ext4 persist
24 143MB 143MB 8192B ssd
25 143MB 147MB 3146kB ext2 fsg
26 147MB 148MB 1049kB sp
27 148MB 148MB 524kB misc
28 148MB 151MB 3146kB ext3 pds
29 151MB 151MB 131kB cid
30 151MB 156MB 4194kB logo
31 156MB 160MB 4194kB clogo
32 160MB 161MB 1049kB devtree
33 161MB 171MB 10.5MB boot
34 171MB 182MB 10.5MB recovery
35 182MB 190MB 8389kB kpan
36 190MB 1257MB 1067MB cache
37 1257MB 1258MB 1049kB padC
38 1258MB 2869MB 1611MB ext4 system
39 2869MB 2982MB 113MB customize
40 2982MB 15.8GB 12.8GB userdata
(parted) rm 40
rm 40
(parted) mkpartfs primary ext2 2982MB 15695MB
mkpartfs primary ext2 2982MB 15695MB
(parted) name 40 userdata
name 40 userdata
(parted) quit
quit
Information: You may need to update /etc/fstab.
.. and rebooted using twrp reboot/system button.
Wtf is happened?
any ideas how to solve this?
thanks.
Umm, gpt.bin corrupted.. Head towards the unbrick thread..
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
Hi, when trying to install twrp, i get this message:
Code:
Sending 'recovery' (131072 KB) OKAY [ 3.060s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
with windows 11, i can see that i still have 53Go available but that does not help.
TRying to dig in this issue, here is what i got :
Code:
\platform-tools>adb shell df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 3.3G 3.2G 167M 96% /
tmpfs 2.6G 0.9M 2.6G 1% /dev
tmpfs 2.6G 0 2.6G 0% /mnt
tmpfs 2.6G 0 2.6G 0% /apex
/dev/block/dm-1 1.4G 1.3G 55M 97% /vendor
none 2.6G 0 2.6G 0% /sys/fs/cgroup
/dev/block/sda29 232M 4.3M 220M 2% /cache
/dev/block/sda14 4.9M 160K 4.8M 4% /dev/logfs
/dev/block/sda30 976M 728M 222M 77% /cust
/dev/block/sda31 109G 51G 58G 47% /data
/data/media 109G 51G 58G 47% /storage/emulated
Well, if i get it right, that could mean, i only have 167 Mo left on the system partition, which is ... not much..
digging further i got
Code:
adb shell df /
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 3555292 3368200 170708 96% /apex/com.android.resolv
which confirms what may be an issue..
But i definitely don't know what to do
I've tried to temporarily boot on twrp using
Code:
fastboot boot twrp.img
but a black screen occurs, and that was it...
So definitely don't know what to do.
Any help would be appreciate!
The question is, how big is your recovery partition, presuming that you have one?
The image you have is 128 MB. Undoubtedly it's 30 MB of recovery, 98 MB or zeroes and a stupid AVB0 footer.
Use some tool to chop it down to 64 MB or so and try flashing it.
Or if you do Windows, try my imgutil /p /v recovery.img (on a copy of the file).
It's in the sig.
Seems like ur /system is just full. PixelOS or some other heavy Rom installed?
Other than that, when u have the balls u could repartitionate ur Phone as i had todo so on the P20 Pro, as /system was too small with <2.8gb~ for some roms. But wont recommend when u have no idea what todo.
aLcaTr4z said:
Seems like ur /system is just full. PixelOS or some other heavy Rom installed?
Other than that, when u have the balls u could repartitionate ur Phone as i had todo so on the P20 Pro, as /system was too small with <2.8gb~ for some roms. But wont recommend when u have no idea what todo.
Click to expand...
Click to collapse
I agree with the "system full" theory. I do not see anything mounted on "/" (only on subfolders of "/") on my phone. https://source.android.com/docs/core/ota/modular-system/dns-resolver
Im not 100% sure, but i think thats correct. Will do a search across the system, to check if i can find my old partion table.
Spoiler: P20 Pro stock partitions
Code:
Number Start End Size File system Name Flags
1 524kB 1049kB 524kB vrl msftdata
2 1049kB 1573kB 524kB vrl_backup msftdata
3 1573kB 10.5MB 8913kB ext4 modem_secure msftdata
4 10.5MB 15.7MB 5243kB nvme msftdata
5 15.7MB 16.8MB 1049kB certification msftdata
6 16.8MB 83.9MB 67.1MB oeminfo msftdata
7 83.9MB 117MB 33.6MB ext4 secure_storage msftdata
8 117MB 151MB 33.6MB ext4 modem_om msftdata
9 151MB 168MB 16.8MB modemnvm_factory msftdata
10 168MB 185MB 16.8MB modemnvm_backup msftdata
11 185MB 206MB 21.0MB ext4 modemnvm_img msftdata
12 206MB 222MB 16.8MB modemnvm_system msftdata
13 222MB 226MB 4194kB hisee_encos msftdata
14 226MB 228MB 1049kB veritykey msftdata
15 228MB 229MB 1049kB ddr_para msftdata
16 229MB 257MB 28.3MB reserved2 msftdata
17 257MB 341MB 83.9MB ext4 splash2 msftdata
18 341MB 343MB 2097kB bootfail_info msftdata
19 343MB 345MB 2097kB misc msftdata
20 345MB 362MB 16.8MB dfx msftdata
21 362MB 379MB 16.8MB rrecord msftdata
22 379MB 379MB 262kB fw_lpm3_a msftdata
23 379MB 383MB 3932kB reserved3_a msftdata
24 383MB 384MB 1049kB hdcp_a msftdata
25 384MB 388MB 4194kB hisee_img_a msftdata
26 388MB 392MB 4194kB hhee_a msftdata
27 392MB 401MB 8389kB ext4 hisee_fs_a msftdata
28 401MB 413MB 12.6MB fastboot_a msftdata
29 413MB 417MB 4194kB vector_a msftdata
30 417MB 419MB 2097kB isp_boot_a msftdata
31 419MB 434MB 14.7MB isp_firmware_a msftdata
32 434MB 447MB 12.6MB fw_hifi_a msftdata
33 447MB 455MB 8389kB teeos_a msftdata
34 455MB 472MB 16.8MB sensorhub_a msftdata
35 472MB 497MB 25.2MB erecovery_kernel_a msftdata
36 497MB 531MB 33.6MB erecovery_ramdisk_a msftdata
37 531MB 547MB 16.8MB erecovery_vendor_a msftdata
38 547MB 573MB 25.2MB kernel_a msftdata
39 573MB 585MB 12.6MB eng_system_a msftdata
40 585MB 619MB 33.6MB recovery_ramdisk_a msftdata
41 619MB 635MB 16.8MB recovery_vendor_a msftdata
42 635MB 657MB 22.0MB dts_a msftdata
43 657MB 665MB 7340kB dto_a msftdata
44 665MB 667MB 2097kB trustfirmware_a msftdata
45 667MB 726MB 58.7MB ext4 modem_fw_a msftdata
46 726MB 738MB 12.6MB eng_vendor_a msftdata
47 738MB 740MB 2097kB recovery_vbmeta_a msftdata
48 740MB 742MB 2097kB erecovery_vbmeta_a msftdata
49 742MB 747MB 4194kB vbmeta_a msftdata
50 747MB 763MB 16.8MB modemnvm_update_a msftdata
51 763MB 805MB 41.9MB modemnvm_cust_a msftdata
52 805MB 839MB 33.6MB reserved7 msftdata
53 839MB 872MB 33.6MB ext4 version_a msftdata
54 872MB 1871MB 998MB vendor_a msftdata
55 1871MB 1879MB 8389kB ext4 preload_a msftdata
56 1879MB 2080MB 201MB cust_a msftdata
57 2080MB 2231MB 151MB odm_a msftdata
58 2231MB 2366MB 134MB ext4 cache msftdata
59 2366MB 3683MB 1317MB preas msftdata
60 3683MB 3716MB 33.6MB preavs msftdata
61 3716MB 5453MB 1736MB product_a msftdata
62 5453MB 8061MB 2609MB ext2 system_a msftdata
63 8061MB 8271MB 210MB ext4 patch_a msftdata
64 8271MB 128GB 120GB userdata msftdata
i Think Xi might using /system_x just as around ~3gb too.
Edit²:
Code:
./parted /dev/block/sdd
is a entrypoint to dig deeper.
Well, I don't get it.
There's a bunch of people who have reported problems and gotten "volume full"'.
Most of the times they say that they were flashing the wrong thing.
The weird part is that fastboot doesn't normally have anything to do with "volumes".
It works on partitions.
So, clearly I'm missing something.
In any case imgutil /v /l whatever.img will tell you what the file you're trying to flash is.
(Don't quote the whole ramdisk! Just say if there is one.)
fastboot getvar all will also tell us what it has for a recovery partition.
Renate said:
Well, I don't get it.
There's a bunch of people who have reported problems and gotten "volume full"'.
Most of the times they say that they were flashing the wrong thing.
The weird part is that fastboot doesn't normally have anything to do with "volumes".
It works on partitions.
So, clearly I'm missing something.
Click to expand...
Click to collapse
Yes, Renate, that's what I don't understand either. I don't know much about all this, but most of what I read about this error was about a wrong img. Though the first thing I did was to download from this website the latest twrp available but again it failed.
I'll try all what you ppl adviced me to do, and will come back here to talk about the results.
Many thanks
ok, let's try to dig in:
imgutil /v /l gives me this ;
Header1: 1,648 (00000670) Kernel: 17,767,553 (010f1c81) 00001000 Payload: 17,369,640 (01090a28) DTB: 397,913 (00061259) Ramdisk: 27,351,923 (01a15b73) 010f3000 Recovery: 261,873 (0003fef1) 02b09000 Signature: 2,432 (00000980) 02b49000 Padding: 88,825,856 (054b6000) 02b4a000
fastboot getvar all returns many things but there's no recovery partition yet.
here is what I get about this twrp file (using cygwin)
file twrp.img twrp.img: Android bootimg, kernel (0x8000), ramdisk (0x1000000), page size: 4096, cmdline (androidboot.hardware=qcom androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filt)
You make that hard to read:
Code:
Header1: 1,648 (00000670)
Kernel: 17,767,553 (010f1c81) 00001000
Payload: 17,369,640 (01090a28)
DTB: 397,913 (00061259)
Ramdisk: 27,351,923 (01a15b73) 010f3000
Recovery: 261,873 (0003fef1) 02b09000
Signature: 2,432 (00000980) 02b49000
Padding: 88,825,856 (054b6000) 02b4a000
Are you rooted and/or can you do any of the following commands over adb shell:
Code:
ls -l /dev/block/by-name
(We only care about recovery partition(s).)
Code:
dd if=/dev/block/by-name/recovery of=/dev/null
What does it say for numbers?
Ok, for what I understand (not much) here are the answers:
ls -l /dev/block/by-name
Code:
otal 0
lrwxrwxrwx 1 root root 16 1972-07-14 02:48 abl -> /dev/block/sde35
....
lrwxrwxrwx 1 root root 15 1972-07-14 02:48 bk51 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1972-07-14 02:48 bk52 -> /dev/block/sdf3
....
lrwxrwxrwx 1 root root 16 1972-07-14 02:48 rawdump -> /dev/block/sda27
lrwxrwxrwx 1 root root 16 1972-07-14 02:48 recovery -> /dev/block/sda28
lrwxrwxrwx 1 root root 14 1972-07-14 02:48 sda -> /dev/block/sda
lrwxrwxrwx 1 root root 14 1972-07-14 02:48 sdb -> /dev/block/sdb
lrwxrwxrwx 1 root root 14 1972-07-14 02:48 sdc -> /dev/block/sdc
lrwxrwxrwx 1 root root 14 1972-07-14 02:48 sdd -> /dev/block/sdd
lrwxrwxrwx 1 root root 14 1972-07-14 02:48 sde -> /dev/block/sde
lrwxrwxrwx 1 root root 14 1972-07-14 02:48 sdf -> /dev/block/sdf
lrwxrwxrwx 1 root root 15 1972-07-14 02:48 secdata -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1972-07-14 02:48 splash -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 1972-07-14 02:48 spunvm -> /dev/block/sde41
lrwxrwxrwx 1 root root 15 1972-07-14 02:48 ssd -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1972-07-14 02:48 storsec -> /dev/block/sde11
lrwxrwxrwx 1 root root 15 1972-07-14 02:48 switch -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1972-07-14 02:48 system -> /dev/block/sde54
...
I then tried to launch dd if=/dev/block/by-name/recovery of=/dev/null
But I got only errors:
from cygwin terminal, in platform tools folder I launched everything I could but for no avail...
Code:
$ adb shell dd if=/dev/block/by-name/recovery of=/dev/null
dd: /dev/block/by-name/recovery: Permission denied
**I tried to replace "recovery" with sda28
Code:
/platform-tools
$ adb shell dd if=/dev/block/by-name/sda28 of=/dev/null
dd: /dev/block/by-name/sda28: No such file or directory
dunno what to do...
Cyjam said:
Code:
lrwxrwxrwx 1 root root 16 1972-07-14 02:48 recovery -> /dev/block/sda28
Click to expand...
Click to collapse
Ok, so you have a nice recovery partition. We still don't know how big it is.
You can chop down (a copy of) your image to something smaller and try that.
Eventually we'll find something that fits. Whether it works is a different question.
The current source code for fastboot doesn't have any error that has "volume" in it. That's one reason that I'm confused.
I wasn't really expecting dd to work, that's usually only for root.
So do that imgutil /p copy-of and try to flash it.
Some questions...
Really sweet or sweetin?
TWRP (recovery partition) doesn't equal with system, system full was shown in flashing recovery?
Which recovery was tried to flash?
Tried completely clean flash?
Tried to flash stock with miflash?
Hi laptapper, thanks for trying to help. Unfo, I'm a real noob and unsure about any of your questions:
Really sweet or sweetin? what's the difference?
TWRP (recovery partition) doesn't equal with system, system full was shown in flashing recovery?
Which recovery was tried to flash? the last one available, TWRP-3.6.2_12.1-sweet-20220705
Tried completely clean flash? don't know what "clean flash" is, but I guess i didn't try it, meaning, I did not swipe my phone. I'd be happy to flash it without totally reseting it.
Tried to flash stock with miflash? never heard about this.
Cyjam said:
Hi laptapper, thanks for trying to help. Unfo, I'm a real noob and unsure about any of your questions:
Really sweet or sweetin? what's the difference?
TWRP (recovery partition) doesn't equal with system, system full was shown in flashing recovery?
Which recovery was tried to flash? the last one available, TWRP-3.6.2_12.1-sweet-20220705
Tried completely clean flash? don't know what "clean flash" is, but I guess i didn't try it, meaning, I did not swipe my phone. I'd be happy to flash it without totally reseting it.
Tried to flash stock with miflash? never heard about this.
Click to expand...
Click to collapse
Sweet or sweetin means I wanna know if it's a Redmi note 10 pro and which variant.
First get orange fox 12.1.3 and try to flash
Complete clean flash means format data with yes (almost necessary)
I suggest to read more in this forum....to get more knowledge
I was trying to use a 120mb twrp then I downloaded a smaller one of 60mb from the official website and it worked