i was trying to flash lineageOS 13.0 on driod razr xt912 using safestrap 3.75 right after that flash open gapp but couldn't due to low storage error of system partition so i decided to increase system memory . After googling found two way of doing , 1st parted , 2nd fdisk. After getting in error in parted so i switch to fdisk . Below are the steps i did please correct me
1) connected phone in safetrap 3.75 recovery to pc. CONNECTION WAS SUCCESSFUL . took backup of /system and /data from safetrap 3.75.
adb root
adb shell
# cat /etc/fstab
/dev/block/mmcblk1p25 /sdcard vfat rw
/sdcard-ext vfat rw
/dev/block/mmcblk1p24-orig /data ext3 rw
/dev/block/mmcblk1p21-orig /cache ext3 rw
/dev/block/mmcblk1p20-orig /system ext3 rw
/dev/block/mmcblk1p23 /osh ext3 rw
/dev/block/mmcblk1p20-orig /systemorig ext3 rw
/dev/block/mmcblk1p25 /ss vfat rw
# cat /proc/partitions
179 0 15564800 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 1 mmcblk1p4
179 5 512 mmcblk1p5
179 6 128 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8 utags
179 9 1024 mmcblk1p9
179 10 2048 mmcblk1p10
179 11 512 mmcblk1p11
179 12 512 mmcblk1p12
179 13 4096 mmcblk1p13
179 14 8192 mmcblk1p14 boot
179 15 9216 mmcblk1p15 recovery
179 16 217088 mmcblk1p16 cdrom
179 17 512 mmcblk1p17 misc
179 18 512 mmcblk1p18 cid
179 19 4096 mmcblk1p19 kpanic
179 20 655360 mmcblk1p20 system
179 21 1048576 mmcblk1p21 cache
179 22 622592 mmcblk1p22 preinstall
179 23 1364992 mmcblk1p23 webtop
179 24 3203072 mmcblk1p24 userdata
179 25 8401792 mmcblk1p25 emstorage
179 26 128 mmcblk1p26
179 64 2048 mmcblk1boot1
179 32 2048 mmcblk1boot0
# /sbin/fdisk /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 15.9 GB, 15938355200 bytes
16 heads, 16 sectors/track, 121600 cylinders, total 31129600 sectors
Units = sectors of 1 * 512 = 512 bytes
u (unit to sector )
p
Device Boot Start End Blocks Id System
block/mmcblk1p1 * 256 511 128 83 Linux
block/mmcblk1p2 1024 2047 512 83 Linux
block/mmcblk1p3 2048 3071 512 83 Linux
block/mmcblk1p4 3072 31105023 15550976 5 Extended
block/mmcblk1p5 4096 5119 512 83 Linux
block/mmcblk1p6 5120 5375 128 83 Linux
block/mmcblk1p7 6144 14335 4096 83 Linux
block/mmcblk1p8 14336 15359 512 83 Linux
block/mmcblk1p9 16384 18431 1024 83 Linux
block/mmcblk1p10 18432 22527 2048 83 Linux
block/mmcblk1p11 22528 23551 512 83 Linux
block/mmcblk1p12 23552 24575 512 83 Linux
block/mmcblk1p13 24576 32767 4096 83 Linux
block/mmcblk1p14 32768 49151 8192 83 Linux
block/mmcblk1p15 49152 67583 9216 83 Linux
block/mmcblk1p16 67584 501759 217088 83 Linux
block/mmcblk1p17 501760 502783 512 83 Linux
block/mmcblk1p18 502784 503807 512 83 Linux
block/mmcblk1p19 503808 511999 4096 83 Linux
block/mmcblk1p20 512000 1822719 655360 83 Linux
block/mmcblk1p21 1822720 3919871 1048576 83 Linux
block/mmcblk1p22 3919872 5165055 622592 83 Linux
block/mmcblk1p23 5165056 7895039 1364992 83 Linux
block/mmcblk1p24 7895040 14301183 3203072 83 Linux
block/mmcblk1p25 14301184 31104767 8401792 83 Linux
block/mmcblk1p26 31104768 31105023 128 83 Linux
2) i decide to make changes in (20-25)'s partition ( system to +3072M, cache to +1024M, preinstall to +1S, webtop to +1S, userdata to +3072M, emstorage to +8102M). But in order to make changes in (20-25)'s i had to delete 26's partitions but after creating new table starting and ending sector of 26's partitions remains the same . Also after i knew that safetrap 3.75 does not use preinstall, webtop for stock slot so i change them to +1S SECTORE.
d 26
d 25
d 24
d 23
d 22
d 21
d 20
3) after creating the new partitions. Table as follows
P
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 * 256 511 128 83 Linux
/dev/block/mmcblk1p2 1024 2047 512 83 Linux
/dev/block/mmcblk1p3 2048 3071 512 83 Linux
/dev/block/mmcblk1p4 3072 31105023 15550976 5 Extended
/dev/block/mmcblk1p5 4096 5119 512 83 Linux
/dev/block/mmcblk1p6 5120 5375 128 83 Linux
/dev/block/mmcblk1p7 6144 14335 4096 83 Linux
/dev/block/mmcblk1p8 14336 15359 512 83 Linux
/dev/block/mmcblk1p9 16384 18431 1024 83 Linux
/dev/block/mmcblk1p10 18432 22527 2048 83 Linux
/dev/block/mmcblk1p11 22528 23551 512 83 Linux
/dev/block/mmcblk1p12 23552 24575 512 83 Linux
/dev/block/mmcblk1p13 24576 32767 4096 83 Linux
/dev/block/mmcblk1p14 32768 49151 8192 83 Linux
/dev/block/mmcblk1p15 49152 67583 9216 83 Linux
/dev/block/mmcblk1p16 67584 501759 217088 83 Linux
/dev/block/mmcblk1p17 501760 502783 512 83 Linux
/dev/block/mmcblk1p18 502784 503807 512 83 Linux
/dev/block/mmcblk1p19 503808 511999 4096 83 Linux
/dev/block/mmcblk1p20 512016 6512016 3000000+ 83 Linux
/dev/block/mmcblk1p21 6512033 8512033 1000000+ 83 Linux
/dev/block/mmcblk1p22 8512050 8512052 1+ 83 Linux
/dev/block/mmcblk1p23 8512069 8512071 1+ 83 Linux
/dev/block/mmcblk1p24 8512088 14512088 3000000+ 83 Linux
/dev/block/mmcblk1p25 14512105 31104751 8296323+ 83 Linux
/dev/block/mmcblk1p26 31104768 31105023 128 83 Linux
w (writing)
recreating table successful
q (quit)
# mke2fs -t ext3 /dev/block/mmcblk1p20
# mke2fs -t ext3 /dev/block/mmcblk1p21
# mke2fs -t ext3 /dev/block/mmcblk1p22
# mke2fs -t ext3 /dev/block/mmcblk1p23
# mke2fs -t ext3 /dev/block/mmcblk1p24
# mkdosfs /dev/block/mmcblk1p25
#mount /dev/block/mmcblk1p20 /system/
#mount /dev/block/mmcblk1p21 /cache/
#mount /dev/block/mmcblk1p24 /data/
#mount /dev/block/mmcblk1p25 /sdcard/
# mount /dev/block/mmcblk1p25 /ss/
# mount /dev/block/mmcblk1p25 /and-sec/
4) after that wiped cache, data , andriod secure, data, webtop, system.
5) restored backup of /system and /data /
6) reboot the system
7) after Motorola logo "M" got error
ap fastboot flash mode [boot failure]
0A.77
eMMC Info: Size 16g
to return to normal mode - first press power key to power down
device is LOCKED, Status Code:0
battery ok
ok to program
Connect USB
Data cable
Invalid CG OTV [CG: system]: Invalid SP Data
Invalid CG HAB [CG: system, status: 0X004E]
Invalid CG OTV [CG: system]
8) i had to use RSD LITE to flash VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml to boot normally.
9) after booting i check for changes i made , f**k system returns back to default partition table.
QUESTIONS
1) where do i go wrong
2) does i have to also make change in "ebr" or "mbr" after changing partitions size
4) does it relate to preinstall and webtop which i left to +1S SECTOR
5)does lineageOS 13.0 need /osh (webtop partitions) because i was flashing saw it searching for /osh for mount
6)does to safe to left the preinstall and webtop to +1S SECTOR
Related
Hello:
Here'smy understanding of the internal partitioning scheme (mmcblk0px):
p12 - system
p13 - osh
p14 - cdrom (windows motorola drivers)
p15 - cache
p16 - data
p17 - prebuilt
p18 - emmc/sdcard
Since CM7 doesnt have osh, I thought I'd add destructively add the space on 13 to my data partition. Booted into recovery, loaded up fdisk, and in order to not muck around with the partition scheme, I thought I'd create a 1k partition for 13, and add the space to 16. So i deleted p13-16 and recreated them in fdisk.
Here's my problem: fdisk said it altered the partition table successfully. So I rebooted back to recovery. However, the partition table changes are not showing. It shows the same old table.
So: - can you repartition the internal storage/flash? Is fdisk the tool to use?
Thanks in advance.
i have this question too
i think i messed up my partition table
when I type fdisk -H 1 /dev/block/mmcblk0 it shows:
/dev # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 513 576 512 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 577 832 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
---------- Post added at 02:11 AM ---------- Previous post was at 01:55 AM ----------
can anyone paste the partition table with the command above?
fdisk -l /dev/block/mmcblk0
not sure if this will help, i've just installed gentop2
atrix adas # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders, total 31083520 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1024 8191 3584 83 Linux
/dev/block/mmcblk0p2 8192 9215 512 83 Linux
/dev/block/mmcblk0p3 9216 13311 2048 83 Linux
/dev/block/mmcblk0p4 13312 31005695 15496192 5 Extended
/dev/block/mmcblk0p5 14336 16383 1024 83 Linux
/dev/block/mmcblk0p6 16384 17407 512 83 Linux
/dev/block/mmcblk0p7 17408 18431 512 83 Linux
/dev/block/mmcblk0p8 18432 20479 1024 83 Linux
/dev/block/mmcblk0p9 20480 24575 2048 83 Linux
/dev/block/mmcblk0p10 24576 40959 8192 83 Linux
/dev/block/mmcblk0p11 40960 57343 8192 83 Linux
/dev/block/mmcblk0p12 57344 712703 327680 83 Linux
/dev/block/mmcblk0p13 712704 2285567 786432 83 Linux
/dev/block/mmcblk0p14 2285568 2326527 20480 83 Linux
/dev/block/mmcblk0p15 2326528 3637247 655360 83 Linux
/dev/block/mmcblk0p16 3637248 7831551 2097152 83 Linux
/dev/block/mmcblk0p17 7831552 8538111 353280 83 Linux
/dev/block/mmcblk0p18 8538112 31005695 11233792 83 Linux
Hallo everyone here ,
Today I decided to install the CM9 on my unlocked Atrix (UK Orage).
I made a big mistake: I used a software called: "MiniTool Partition Wizard Professional Edition 6.0" to format the internal storage disk on my device and created following partitions in this order:
- Primary EXT4 2 GB
- swap 512 MB
- Primary FAT32 rest of the space.
After applying the changes I lost any access to the internal disk at all.
I booted into "Recovery" and connected the device using ADB and ran the following commands:
- adb shell
- fdisk -H 1 /dev/block/mmcblk0
And that was the result:
Code:
fdisk -H 1 /dev/block/mmcblk0
The number of cylinders for this disk is set to 1942720.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help):
I ran then the following command and got that result:
Command: fdisk -l /dev/block/mmcblk0
Results:
Code:
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
[B]Partition 1 does not end on cylinder boundary[/B]
/dev/block/mmcblk0p2 513 576 512 83 Linux
[B]Partition 2 does not end on cylinder boundary[/B]
/dev/block/mmcblk0p3 577 832 2048 83 Linux
[B]Partition 3 does not end on cylinder boundary[/B]
/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
[B]Partition 4 does not end on cylinder boundary[/B]
/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
/dev/block #
Now I can't access that storage anymore. Can anyone help me in this matter ?
Thanks for your support.
Top
Any info, help, hint, would be great !
Hi Arwany,
I am in CWM 5.0.2.0 right now. Here is what I get on my healthy Atrix (no modifications made to internal memory --- at least none that I know of ):
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
[B]Partition 1 does not end on cylinder boundary
[/B]/dev/block/mmcblk0p2 513 576 512 83 Linux
[B]Partition 2 does not end on cylinder boundary
[/B]/dev/block/mmcblk0p3 577 832 2048 83 Linux
[B]Partition 3 does not end on cylinder boundary
[/B]/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
[B]Partition 4 does not end on cylinder boundary
[/B]/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
Are you SURE you were modifying internal storage instead of external? I ask this because a partitioning tool MAY not recognize internal storage, in which case it MAY assign an index of "0" (e.g. dev/mmcblk0) to EXTERNAL storage. This is what happened when I pulled my SD card from Atrix, inserted to computer and ran GParted on it. If GParted HAD recognized internal storage, I presume that it would look like...
/dev/mmcblk0 (internal)
/dev/mmcblk1 (external)
And here is what I get for my healthy external storage (the Linux partitions are custom-created for dual boot --- normally you just have FAT32).
Code:
~ # fdisk -l /dev/block/mmcblk1
Disk /dev/block/mmcblk1: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 1301 10445123 c Win95 FAT32 (LBA)
/dev/block/mmcblk1p2 1302 1349 385560 83 Linux
/dev/block/mmcblk1p3 1350 1435 690795 83 Linux
/dev/block/mmcblk1p4 1436 1690 2048287+ 83 Linux
I hope this helps in some way.
Thank you very much for your help, the problem is: I have done modification to the internal storage, as I deattached the SD-Card first, then connected the Atrix (at that time with CM7 from Atrix-Dev-Team) as USB Storage, so the software detected it, I made only SWAP&FAT32 partitions, then applied the changes, after that I didn't see my internal storage, and the Atrix can't access it anymore, tried to format it from my CWM, or CM7 or some other tools.. no success
I even tried to partition it using the same shell, but access was always denied.
Anyway, thanks for the info, and If you have some other helpful comments, please provide me. I appreciate your time with me.
Thanks
Arwany
Finally my issue is solved.
What have I done: I flashed the small SBF file which is available for unlocking the phone, this file has fixed the issue, don't ask me how.
The file is here: Orange/Bell/Telestra/Latin America/International users ONLY
I am happy with my 10 GB back ^_^
Hi,
After reflashing the PDS to get my partitions back to normal, I can now flash roms again. Unfortunately my internal memory card is at the moment borked and after an entire evening spent trying to fix it, it seems an impossible task. I can see my external SD fine, but trying to mount the emmc in recovery comes up with Error mounting /emmc.
Anyone have any good advice they can give me to solve this? I was going to try and reflash the original SBF (yeah, I know how dodgy that can be but I am desperate) from this superthread: http://forum.xda-developers.com/showthread.php?t=1125944 but the feds have put a stop to that...file sharing sites just don't let you get as many downloads these days!
So...any help, please?
there are other links for stock sbf. only flash 4.5.91, not 4.5.140. keep searching around.
Sent from my MB860 using XDA
el_venga said:
there are other links for stock sbf. only flash 4.5.91, not 4.5.140. keep searching around.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
That's the AT&T one isn't it though? My phone is a UK Orange handset (well it was, I've long since sim unlocked it )
Would this brick my Atrix? I know there is a risk already on handsets that are actually AT&T so don't want to raise the risk even more.
Surely there must be an easier way to get my internal memory card back to working order than SBFing?
Bump... Anyone know of a better way of rescuing my emmc partition?
You'll need adb type this and the post what the output is
adb shell
# cat /proc/partitions
# fdisk /dev/block/mmcblk0
p
q
rickwyatt said:
You'll need adb type this and the post what the output is
adb shell
# cat /proc/partitions
# fdisk /dev/block/mmcblk0
p
q
Click to expand...
Click to collapse
Hi there,
Thanks so much for getting back to me on this, sorry about the delay, only just got back in, despite the beers I have managed to navigate the cmd line
Ok, so my output is this:
1|[email protected]:/ $ su
su
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2048 loop0
253 0 98304 zram0
179 0 15541760 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 327680 mmcblk0p12
179 13 786432 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 655360 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 353280 mmcblk0p17
179 18 11233792 mmcblk0p18
179 32 7772160 mmcblk1
179 33 7771136 mmcblk1p1
[email protected]:/ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 1942720.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): ←[6np
p
Disk /dev/block/mmcblk0: 15.9 GB, 15914762240 bytes
1 heads, 16 sectors/track, 1942720 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 512 3584 83 Linux
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 513 576 512 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 577 832 2048 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 833 1937856 15496192 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 897 1024 1024 83 Linux
/dev/block/mmcblk0p6 1025 1088 512 83 Linux
/dev/block/mmcblk0p7 1089 1152 512 83 Linux
/dev/block/mmcblk0p8 1153 1280 1024 83 Linux
/dev/block/mmcblk0p9 1281 1536 2048 83 Linux
/dev/block/mmcblk0p10 1537 2560 8192 83 Linux
/dev/block/mmcblk0p11 2561 3584 8192 83 Linux
/dev/block/mmcblk0p12 3585 44544 327680 83 Linux
/dev/block/mmcblk0p13 44545 142848 786432 83 Linux
/dev/block/mmcblk0p14 142849 145408 20480 83 Linux
/dev/block/mmcblk0p15 145409 227328 655360 83 Linux
/dev/block/mmcblk0p16 227329 489472 2097152 83 Linux
/dev/block/mmcblk0p17 489473 533632 353280 83 Linux
/dev/block/mmcblk0p18 533633 1937856 11233792 83 Linux
Command (m for help): ←[6nq
q
[email protected]:/ #
Bump...
I can help but you must be careful I take no responsibility if I brick your phone now that bits over you will need to be connected to a computer then type this
rickwyatt said:
I can help but you must be careful I take no responsibility if I brick your phone now that bits over you will need to be connected to a computer then type this
Click to expand...
Click to collapse
Hey, thanks...this is for my internal SD though, so should I simply drop the -ext from the # umount sdcard line?
Just enter mke2fs /dev/block/mmcblk0p18 it should wipe your internal sdcard
Ok...it simply says mke2fs: can't open '/dev/block/': ls a directory
what am i doing wrong?
rickwyatt said:
Just enter mke2fs /dev/block/mmcblk0p18 it should wipe your internal sdcard
Click to expand...
Click to collapse
sorry, scratch that, it says:
mke2fs: lseek: value too large for defined data type
Any ideas?
Would mke3fs work to upgrade to ext3?
Type this in adb busybox mkfs.vfat /dev/block/mmcblk0p18
it just goes through a whole list of adb commands but doesn't seem to do anything, am I doing it incorrectly?
I have the same issue with my atrix. Unable to mount or use /emmc . Posting my recovery log for your reference. Any help or advice would be appreciated. Already tried reflashing the TWIZ recovery and the ROM but no luck.
Starting recovery on Wed Aug 1 05:48:04 2012
Loading volume table...
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p11 (null)
2 /cache ext4 /dev/block/mmcblk0p15 NULL
3 /data ext4 /dev/block/mmcblk0p16 NULL
4 /sdc vfat /dev/block/mmcblk1p1 (null)
5 /emmc vfat /dev/block/mmcblk0p18 (null)
6 /system ext4 /dev/block/mmcblk0p12 NULL
7 /recovery emmc /dev/block/mmcblk0p10 (null)
8 /osh ext3 /dev/block/mmcblk0p13 (null)
9 /preinstall ext3 /dev/block/mmcblk0p17 (null)
I:Internal path defined: '/emmc'
I:External path defined: '/sdc'
Pixel format: 540x960 @ 16bpp
Pixel format: BGR_565
framebuffer: fd 4 (540 x 960)
I:=> Installing busybox into /sbin
ln: /sbin/mke2fs: File exists
ln: /sbin/sh: File exists
ln: /sbin/tune2fs: File exists
I:=> Linking mtab
I:=> Getting locations
Wevice does not support /proc/emmc
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
I:'data' was 'ext4' now set to 'ext3'
I:'cache' was 'ext4' now set to 'ext3'
I:=> Created /sdc folder.
I:=> Created /osh folder.
* Verifying partition sizes...
E:Unable to mount '/emmc' (tw_mount)
E:Unable to mount '/emmc' (tw_mount)
du: /emmc/.android_secure: No such file or directory
E:Unable to mount '/osh' (tw_mount)
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p12 | ext4 | 327680 | 267096 | 1 | f |
| data | /dev/block/mmcblk0p16 | ext3 | 2097152 | 1204136 | 1 | f |
| boot | /dev/block/mmcblk0p11 | emmc | 8192 | 8192 | 0 | i |
| recovery | /dev/block/mmcblk0p10 | emmc | 8192 | 8192 | 0 | i |
| cache | /dev/block/mmcblk0p15 | ext3 | 655360 | 80816 | 1 | f |
| sdc | /dev/block/mmcblk1p1 | vfat | 15628288 | 11597696 | 1 | n |
| emmc | /dev/block/mmcblk0p18 | vfat | 11233792 | 0 | 1 | n |
| andsec | /emmc | vfat | 0 | 0 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | | 0 | 0 | 1 | f |
| osh | /dev/block/mmcblk0p13 | ext3 | 786432 | 0 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
Sent from my MB860 using Tapatalk 2
same problem with atrix 2
Hi guys, with my atrix 2 (me865) i have same problem, when i run cat /proc/partitions
output is:
179 0 7757824 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 512 mmcblk1p4
179 5 512 mmcblk1p5
179 6 512 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8
179 9 512 mmcblk1p9
179 10 1024 mmcblk1p10
179 11 2048 mmcblk1p11
179 12 512 mmcblk1p12
179 13 512 mmcblk1p13
179 14 4096 mmcblk1p14
179 15 8192 mmcblk1p15 boot
179 16 9216 mmcblk1p16 recovery
179 17 12288 mmcblk1p17 cdrom
179 18 512 mmcblk1p18 misc
179 19 512 mmcblk1p19 cid
179 20 4096 mmcblk1p20 kpanic
179 21 491520 mmcblk1p21 system
179 22 716800 mmcblk1p22 cache
179 23 282624 mmcblk1p23 preinstall
179 24 1368064 mmcblk1p24 webtop
179 25 4845440 mmcblk1p25 userdata
179 26 128 mmcblk1p26
179 64 1024 mmcblk1boot1
179 32 1024 mmcblk1boot0
179 96 31074304 mmcblk0
179 97 31070208 mmcblk0p1
how i can identify what block i need wipe with fdisk command?
at atrix 2 bootloader is locked, is the problem? Can i try this method?
qwerfv said:
Hi guys, with my atrix 2 (me865) i have same problem, when i run cat /proc/partitions
output is:
179 0 7757824 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 512 mmcblk1p4
179 5 512 mmcblk1p5
179 6 512 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8
179 9 512 mmcblk1p9
179 10 1024 mmcblk1p10
179 11 2048 mmcblk1p11
179 12 512 mmcblk1p12
179 13 512 mmcblk1p13
179 14 4096 mmcblk1p14
179 15 8192 mmcblk1p15 boot
179 16 9216 mmcblk1p16 recovery
179 17 12288 mmcblk1p17 cdrom
179 18 512 mmcblk1p18 misc
179 19 512 mmcblk1p19 cid
179 20 4096 mmcblk1p20 kpanic
179 21 491520 mmcblk1p21 system
179 22 716800 mmcblk1p22 cache
179 23 282624 mmcblk1p23 preinstall
179 24 1368064 mmcblk1p24 webtop
179 25 4845440 mmcblk1p25 userdata
179 26 128 mmcblk1p26
179 64 1024 mmcblk1boot1
179 32 1024 mmcblk1boot0
179 96 31074304 mmcblk0
179 97 31070208 mmcblk0p1
how i can identify what block i need wipe with fdisk command?
at atrix 2 bootloader is locked, is the problem? Can i try this method?
Click to expand...
Click to collapse
You're posting in the wrong section. Please go to Atrix 2 forum.
Thank you.
a dev from Google Play contacted me asking for the "partion layout" for my Galaxy player 5. He replied to my usage data my device sent to him via my email. Can anyone help me help this guy? Much Appreciated
What my device apparently sent to him
This email doesn't contain any personal information.
It only contains technical information needed to improve the quality of the backup on your device.
Your help is very appreciated!
-- TECHNICAL INFORMATION --
Device detected as:
Commercial name: YP-G70
Technical name: YP-G70
Searched patch filename: partlayout4nandroid.YP-G70
Information from Android system
Device brand: samsung
Device technical name: YP-G70
Device commercial name: YP-G70
Device board name: YP-G70
Device hardware name: smdkc110
Firmware version: UEKI8
Android SDK: 10
Partition Table:
major minor #blocks name
7 0 9387 loop0
7 1 3150 loop1
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 6 256 mmcblk0p6
179 7 1280 mmcblk0p7
259 0 1280 mmcblk0p8
259 1 5120 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 7680 mmcblk0p11
259 4 7680 mmcblk0p12
259 5 296960 mmcblk0p13
259 6 137216 mmcblk0p14
259 7 65536 mmcblk0p15
259 8 1970176 mmcblk0p16
259 9 5252096 mmcblk0p17
179 8 31166976 mmcblk1
179 9 31162880 mmcblk1p1
254 0 9387 dm-0
254 1 3150 dm-1
THE MESSAGE HE SENT AS A REPLY
to me
Information about your device is rare on the internet. Would you be able to direct me to a place where I can obtain information about partition layout for that device?
Thanks,
(His name)
Sent from my Xperia Pro
any devs see this let me know if you have any info =)
Sent from my YP-G70 using Tapatalk 2
You could always do a mount command in an adb shell, and send the output but I think he wants all the partitions right?
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
You could always do a mount command in an adb shell, and send the output but I think he wants all the partitions right?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
no idea lol
LordZilo said:
no idea lol
Click to expand...
Click to collapse
As root (adb or emulator)
Code:
fdisk -l /dev/block/mmcblk0
mount
That's about all the information there is.
Meticulus said:
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 969728 7757792 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p5 9 40 256 83 Linux
/dev/block/mmcblk0p6 45 76 256 83 Linux
/dev/block/mmcblk0p7 81 240 1280 83 Linux
/dev/block/mmcblk0p8 245 404 1280 83 Linux
/dev/block/mmcblk0p9 409 1048 5120 83 Linux
/dev/block/mmcblk0p10 1053 2332 10240 83 Linux
/dev/block/mmcblk0p11 2337 3296 7680 83 Linux
/dev/block/mmcblk0p12 3301 4260 7680 83 Linux
/dev/block/mmcblk0p13 4265 41384 296960 83 Linux
/dev/block/mmcblk0p14 41389 58540 137216 83 Linux
/dev/block/mmcblk0p15 58545 66736 65536 83 Linux
/dev/block/mmcblk0p16 66741 313012 1970176 83 Linux
/dev/block/mmcblk0p17 313017 969528 5252096 83 Linux
Click to expand...
Click to collapse
This is the one (from another thread) that I used to repartition mine
thanks
I'm using a Xiaomi Redmi Note 9S with MIUI 11.0.10 which is Android 10. There seems to be some bug with root that can soft-brick your phone. When you boot into TWRP, it can no longer mount the System partition - pressing it, will do nothing.
So I connect via adb to the phone. It's root adb and I am root according to "whoami".
cat /proc/partitions output:
Code:
~ # cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
8 0 120479744 sda
8 1 8 sda1
8 2 32768 sda2
8 3 1024 sda3
8 4 512 sda4
8 5 512 sda5
8 6 131072 sda6
8 7 1048576 sda7
8 8 131072 sda8
8 9 131072 sda9
8 10 64 sda10
8 11 64 sda11
8 12 16384 sda12
8 13 393216 sda13
8 14 393216 sda14
8 15 16384 sda15
259 0 8192 sda16
259 1 8388608 sda17
259 2 109786956 sda18
8 16 8192 sdb
8 17 7168 sdb1
8 18 128 sdb2
8 64 4194304 sde
8 65 512 sde1
8 66 4096 sde2
8 67 512 sde3
8 68 262144 sde4
8 69 1024 sde5
8 70 4096 sde6
8 71 32768 sde7
8 72 8192 sde8
8 73 32768 sde9
8 74 512 sde10
8 75 512 sde11
8 76 512 sde12
8 77 128 sde13
8 78 64 sde14
8 79 2048 sde15
259 3 2048 sde16
259 4 512 sde17
259 5 4096 sde18
259 6 512 sde19
259 7 262144 sde20
259 8 1024 sde21
259 9 4096 sde22
259 10 32768 sde23
259 11 8192 sde24
259 12 32768 sde25
259 13 512 sde26
259 14 512 sde27
259 15 512 sde28
259 16 128 sde29
259 17 64 sde30
259 18 2048 sde31
259 19 2048 sde32
259 20 4 sde33
259 21 1024 sde34
259 22 256 sde35
259 23 8192 sde36
259 24 33424 sde37
259 25 4 sde38
259 26 1024 sde39
259 27 8192 sde40
259 28 2048 sde41
259 29 65536 sde42
259 30 128 sde43
259 31 32 sde44
259 32 32 sde45
259 33 512 sde46
259 34 28 sde47
259 35 512 sde48
259 36 1024 sde49
259 37 64 sde50
259 38 131072 sde51
259 39 24576 sde52
259 40 64 sde53
259 41 24576 sde54
259 42 131072 sde55
8 32 8192 sdc
8 33 7168 sdc1
8 34 128 sdc2
8 80 131072 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 10240 sdf4
8 85 128 sdf5
8 48 131072 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 1024 sdd3
253 0 934804 dm-0
253 1 1403780 dm-1
253 2 2356452 dm-2
df -h output after flashing new .EU ROM - this is how it should look like:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 2.7G 752.0K 2.7G 0% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
tmpfs 2.7G 0 2.7G 0% /apex
tmpfs 2.7G 6.4M 2.7G 0% /tmp
/dev/block/sda18 104.7G 14.5G 90.2G 14% /data
/dev/block/sda18 104.7G 14.5G 90.2G 14% /sdcard
/dev/block/dm-1 1.3G 1.2G 33.4M 97% /vendor
/dev/block/sda13 356.0M 428.0K 328.7M 0% /cache
/dev/block/dm-2 2.2G 2.1G 109.5M 95% /system_root
/dev/block/dm-2 2.2G 2.1G 109.5M 95% /system
df -h output - what it actually looks like after soft-brick:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 2.7G 752.0K 2.7G 0% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
tmpfs 2.7G 0 2.7G 0% /apex
tmpfs 2.7G 2.6M 2.7G 0% /tmp
/dev/block/sda13 356.0M 1.1M 328.0M 0% /cache
/dev/block/sda18 104.7G 15.3G 89.4G 15% /data
/dev/block/sda18 104.7G 15.3G 89.4G 15% /sdcard
Trying to mount the "dm" devices, you can mount dm-0 and dm-1, but dm-2 (which should be system) fails:
Code:
~ # mount -r /dev/block/dm-2 /fufu/ -v -t ext4
mount: mounting /dev/block/dm-2 on /fufu/ failed: Read-only file system
DM-verity is disabled:
Code:
adb enable-verity
verity not enabled - ENG build
e2fsck fails because it claims to have no write access:
Code:
~ # e2fsck /dev/block/dm-2
e2fsck 1.44.4 (18-Aug-2018)
e2fsck: Operation not permitted while trying to open /dev/block/dm-2
You must have r/w access to the filesystem or be root
~ # whoami
root
File system is still intact. You can "dd" the dm-2 partition to some other place and access it via Linux or an ext4 viewer on Windows (https://www.diskinternals.com/linux-reader/ for example). You can also do it via adb: "adb pull /dev/block/dm-2"
When mounting (see above) and then looking in the log (dmesg):
Code:
<6>[ 1057.614782] EXT4-fs (dm-2): INFO: recovery required on readonly filesystem
<3>[ 1057.614797] EXT4-fs (dm-2): write access unavailable, cannot proceed
tune2fs for dm-1 and dm-2:
Code:
~ # tune2fs -l /dev/block/dm-1
tune2fs 1.44.4 (18-Aug-2018)
Filesystem volume name: vendor
Last mounted on: <not available>
Filesystem UUID: 6d16bab1-58d9-3c5d-8f14-f608f924affd
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 87824
Block count: 350944
Reserved block count: 0
Free blocks: 12643
Free inodes: 84860
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 87
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 7984
Inode blocks per group: 499
Last mount time: n/a
Last write time: Thu Jan 1 08:00:00 1970
Mount count: 0
Maximum mount count: -1
Last checked: Thu Jan 1 08:00:00 1970
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
~ # tune2fs -l /dev/block/dm-2
tune2fs 1.44.4 (18-Aug-2018)
Filesystem volume name: /
Last mounted on: /
Filesystem UUID: bbcb9ad2-245d-035f-a549-7d500312efe1
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype needs_recovery extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 147456
Block count: 589113
Reserved block count: 0
Free blocks: 32124
Free inodes: 142168
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 143
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Last mount time: Sun Aug 2 03:07:27 2020
Last write time: Thu Jan 1 08:00:00 1970
Mount count: 4
Maximum mount count: -1
Last checked: Thu Jan 1 08:00:00 1970
Check interval: 0 (<none>)
Lifetime writes: 692 kB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
-> dm-2 has a flag called "needs_recovery" set.
- I can run e2fsck on the dd exported image of dm-2 which recovers it fine, but I cannot dd it back to dm-2 - again no write access:
Code:
~ # dd if=/sdcard/systemfile.img of=/dev/block/dm-2
dd: writing '/dev/block/dm-2': Operation not permitted
1+0 records in
0+0 records out
0 bytes (0B) copied, 0.000131 seconds, 0B/s
Ideas how I can write anything to /dev/block/dm-2 (I also cannot change anything via tune2fs to the other dm devices).
Thank you
@herlgl You should take a look at this or this. Good luck!
have you solved? how?