Database Info

Urgent Linux Help Req'd. Bad ext2 partition...

My phone accidentally became unplugged from xp pc when it was mounted- the phone also dropped on the floor so i am not sure which caused the problem.
Problem is now that i cannot read the ext2 partition on my sd- hence it keeps hanging on boot screen..... when i open it in windows using extfs (or whatever the program is- i am typing this from dual booted linux) it wont even recognise it.
So i booted into ubuntu, which i have not used a hell of a lot, and it recognises the fat32 partition on the sd card but the ext2 it calls it 557.1MB Media. when i click on this a couple of errors come up- "cannot mount volume" and "unable to mount 557.1MB media"
please see attached screenshot.
Is there a way i can fix this ext2 partition?
If it is totally stuffed how do i format it again when gparted and partitin manager dont recognise this partition?
thanks

MontAlbert said:
My phone accidentally became unplugged from xp pc when it was mounted- the phone also dropped on the floor so i am not sure which caused the problem.
Problem is now that i cannot read the ext2 partition on my sd- hence it keeps hanging on boot screen..... when i open it in windows using extfs (or whatever the program is- i am typing this from dual booted linux) it wont even recognise it.
So i booted into ubuntu, which i have not used a hell of a lot, and it recognises the fat32 partition on the sd card but the ext2 it calls it 557.1MB Media. when i click on this a couple of errors come up- "cannot mount volume" and "unable to mount 557.1MB media"
please see attached screenshot.
Is there a way i can fix this ext2 partition?
If it is totally stuffed how do i format it again when gparted and partitin manager dont recognise this partition?
thanks
Click to expand...
Click to collapse
you can try to use fsck -t ext2 on linux to try to fix it, but if it got broken because you dropped I really doubt you'll be able to recovery everything. So you mind as well reformat it using fdisk and mkfs. even that may not help if there is physical damage on the sdcard itself.

knaries2000 said:
you can try to use fsck -t ext2 on linux to try to fix it, but if it got broken because you dropped I really doubt you'll be able to recovery everything. So you mind as well reformat it using fdisk and mkfs. even that may not help if there is physical damage on the sdcard itself.
Click to expand...
Click to collapse
how do i reformat it using fdisk and mkfs?
I can see the partition in file browser but when i go to open it it gives me the unable to mount error....i just want to reformat it and start all over again...... any ideas how to do that?

ok. surely there must be someone here who can help me?
I can't even determine which /dev/sda it is.....
I can see it but not load it in linux..... i just want to format the bugger and start over again!

when i do dmesg tail it gives me:
[ 242.702892] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 242.702918] EXT2-fs: group descriptors corrupted!
[ 1410.052668] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1410.052691] EXT2-fs: group descriptors corrupted!
[ 1530.800896] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1530.800923] EXT2-fs: group descriptors corrupted!
[ 1796.715217] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1796.715243] EXT2-fs: group descriptors corrupted!
[ 2628.601044] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 2628.601071] EXT2-fs: group descriptors corrupted!
[ 2660.632918] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 2660.632941] EXT2-fs: group descriptors corrupted!
now i am stumped- just want to somehow delete the bloody partition and format the whole disk over again....

it should be something like /dev/mmcblk0
just run "fdisk -l /dev/mmcblk0" if that doesn't exist try blk1... anyways if that is the card you should see 2 partition like you mention before..
then do "fdisk /dev/mmcblk0" delete the broken partition (should be 2nd one) and then recreate it. Do man on fdisk if you don't know how should be very simple.
once you have created the partition do "mkfs -t ext2 /dev/<partition that you created>"

MontAlbert said:
when i do dmesg tail it gives me:
[ 242.702892] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 242.702918] EXT2-fs: group descriptors corrupted!
[ 1410.052668] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1410.052691] EXT2-fs: group descriptors corrupted!
[ 1530.800896] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1530.800923] EXT2-fs: group descriptors corrupted!
[ 1796.715217] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 1796.715243] EXT2-fs: group descriptors corrupted!
[ 2628.601044] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 2628.601071] EXT2-fs: group descriptors corrupted!
[ 2660.632918] EXT2-fs error (device mmcblk0p2): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)!
[ 2660.632941] EXT2-fs: group descriptors corrupted!
now i am stumped- just want to somehow delete the bloody partition and format the whole disk over again....
Click to expand...
Click to collapse
that means the block bit map of your ext2 partition is corrupted. wouldn't bother with trying to fix that. just recreate it. if you use ubuntu there should be a gui tool that lets you do this easier, but I've never used it... I only used fdisk

MontAlbert said:
ok. surely there must be someone here who can help me?
I can't even determine which /dev/sda it is.....
I can see it but not load it in linux..... i just want to format the bugger and start over again!
Click to expand...
Click to collapse
Patience. It hasn't even been an hour since you last asked. ^_^
Anyhoo, if you want an "easy" way to repartition it, just install Gparted and use that. ^_^
While you're using it, the difference between your hard drive and the sd card is that the SD card is the one with barely any space.

how would i do it with fdisk?
just did a fdisk -l and got:
[email protected]:/dev$ sudo fdisk -l
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8ae08ae0
Device Boot Start End Blocks Id System
/dev/sda1 * 1 23438 188265703+ 7 HPFS/NTFS
/dev/sda2 23439 23504 530145 82 Linux swap / Solaris
/dev/sda3 27638 30401 22201830 f W95 Ext'd (LBA)
/dev/sda4 23505 27637 33198322+ 83 Linux
/dev/sda5 27638 30401 22201798+ b W95 FAT32
Partition table entries are not in disk order
Disk /dev/sdb: 8017 MB, 8017412096 bytes
255 heads, 63 sectors/track, 974 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 907 7281381+ b W95 FAT32
/dev/sdb2 908 975 544026 83 Linux
Partition 2 has different physical/logical endings:
phys=(973, 254, 63) logical=(974, 185, 42)
[email protected]:/dev$

thanks for your help- for some reason when i had card in card reader of PC gparted couldnt see it but when i put it into phone and mounted phone it found it ok. Reformatting now.
damn...... time to buy a back up card i reckon!!!

your memory card is not there in your fsck it should be something like "/dev/mmcblk0" try "fdisk -l /dev/mmcblk0"

knaries2000 said:
your memory card is not there in your fsck it should be something like "/dev/mmcblk0" try "fdisk -l /dev/mmcblk0"
Click to expand...
Click to collapse
thanks mate- just reformatted it- lucky i did a nandroid yesterday and backep up apps the day before.....
i spent about 8hrs trying to fix this- the first 4-5 before i realised it was a stuffed sd card (realised when in bed at 2am)......i was even ringing local pc stores to see if they had cl6 8GB cards....

Mounting in Gentoo Linux with A2SD partitions

I am running cyanogen's rom with a fat32 partition and ext3 partition. When i run fdisk on the device /dev/sdb, i get this as a result and it looks ok:
Code:
# fdisk /dev/sdb
Command (m for help): p
Disk /dev/sdb: 8067 MB, 8067743744 bytes
249 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15438 * 512 = 7904256 bytes
Disk identifier: 0x000eadb7
Device Boot Start End Blocks Id System
/dev/sdb1 1 941 7263548 c W95 FAT32 (LBA)
/dev/sdb2 942 1005 487398 83 Linux
Partition 2 does not end on cylinder boundary.
however, I cant mount my partitions reliably. Sometimes when I plug it in, I get the fat32 partition as /dev/android, and sometimes I get the ext3 partition. but under both circumstances, i NEVER see /dev/sdb1 or /dev/sdb2.
Code:
# ls /dev | grep sd
lrwxrwxrwx 1 root root 4 2009-07-20 15:55 root -> sda3
brw-rw---- 1 root disk 8, 0 2009-07-20 15:55 sda
brw-rw---- 1 root disk 8, 1 2009-07-20 15:55 sda1
brw-rw---- 1 root disk 8, 2 2009-07-20 15:55 sda2
brw-rw---- 1 root disk 8, 3 2009-07-20 15:55 sda3
brw-rw---- 1 root disk 8, 16 2009-07-21 20:43 sdb
however, my dmesg reports this:
Code:
78640.618666] sd 30:0:0:0: [sdb] 15757312 512-byte hardware sectors: (8.06 GB/7.51 GiB)
[78640.620661] sd 30:0:0:0: [sdb] Write Protect is off
[78640.620664] sd 30:0:0:0: [sdb] Mode Sense: 03 00 00 00
[78640.620667] sd 30:0:0:0: [sdb] Assuming drive cache: write through
[78640.624658] sd 30:0:0:0: [sdb] 15757312 512-byte hardware sectors: (8.06 GB/7.51 GiB)
[78640.626659] sd 30:0:0:0: [sdb] Write Protect is off
[78640.626662] sd 30:0:0:0: [sdb] Mode Sense: 03 00 00 00
[78640.626665] sd 30:0:0:0: [sdb] Assuming drive cache: write through
[78640.626669] sdb: sdb1 sdb2
[78640.633034] usb 1-2:1.0: uevent
[78640.633122] usb 1-2: uevent
[78640.899187] usb 1-2:1.0: uevent
[78640.899276] usb 1-2: uevent
[78641.054596] VFS: Can't find ext3 filesystem on dev sdb1.
it takes a bunch of tries of unplugging the usb and plugging it back in until it finally somehow mounts my fat32 partition under /media/disk. Is this some configuration issue? Before I partitioned my sdcard, it was fine mounting just a fat32 partition as the entire card, no problems.

check you hald
/etc/init.d/hald restart
do you have support for udev in you kernel ?
Check this steps and tell us it worked

yes HAL is running and has been running the entire time:
Code:
# rc-update show
alsasound | boot
bootmisc | boot
checkfs | boot
checkroot | boot
clock | boot
consolefont | boot
cupsd | default
dbus | default
hald | default
hostname | boot
keymaps | boot
lm_sensors | default
local | default nonetwork
localmount | boot
modules | boot
net.eth0 | default
net.lo | boot
numlock | default
rdate | default
rmnologin | boot
sshd | default
syslog-ng | default
urandom | boot
xdm | default
Code:
$ ps aux | grep hal
103 3544 0.0 0.0 26956 4032 ? Ss Jul24 0:01 /usr/sbin/hald --use-syslog --verbose=no
root 3545 0.0 0.0 15624 1176 ? S Jul24 0:00 hald-runner
root 3548 0.0 0.0 17748 1124 ? S Jul24 0:00 hald-addon-input: Listening on /dev/input/event1 /dev/input/event0 /dev/input/event3
103 3553 0.0 0.0 16608 968 ? S Jul24 0:00 hald-addon-acpi: listening on acpi kernel interface /proc/acpi/event
root 3558 0.0 0.0 17748 1128 ? S Jul24 0:08 hald-addon-storage: polling /dev/sr0 (every 2 sec)
john5788 4596 0.0 0.0 130688 3120 ? Sl Jul24 0:00 /usr/libexec/gvfs-hal-volume-monitor
root 11452 0.0 0.0 17748 1124 ? S Jul24 0:01 hald-addon-storage: polling /dev/sdb (every 2 sec)
john5788 13851 0.0 0.0 84792 864 pts/1 R+ 10:10 0:00 grep --colour=auto hal
restarting does not help anything.

udevd --version ??
since version 140 those stupids rules messed up with removable devices.

Since I'm lazy I built my kernel with genkernel and it took care of everything about udev.

Code:
# udevd --version
141
so its a rule in udev that is screwin this up?
i'm not using genkernel, I rolled my own kernel out, have been doing it this way for years.
Code:
# uname -a
Linux john5788 2.6.29-gentoo-r5 #1 SMP Fri May 29 16:56:58 PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux

John5788 said:
Code:
# udevd --version
141
so its a rule in udev that is screwin this up?
i'm not using genkernel, I rolled my own kernel out, have been doing it this way for years.
Code:
# uname -a
Linux john5788 2.6.29-gentoo-r5 #1 SMP Fri May 29 16:56:58 PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux
Click to expand...
Click to collapse
Yeah i think ...
what's the output of dmesg |grep EXT3-fs ?

the output has a bunch of instances last night when i was plugging and unplugging the device. like i said, sometimes it recognized my fat32 partition, sometimes ext3.
Code:
# dmesg | grep EXT3-fs
[ 9016.479321] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9016.481783] EXT3-fs: mounted filesystem with ordered data mode.
[ 9111.770944] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
[ 9134.532699] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9134.534632] EXT3-fs: recovery complete.
[ 9134.536841] EXT3-fs: mounted filesystem with ordered data mode.
[ 9166.843481] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9166.849252] EXT3-fs: mounted filesystem with ordered data mode.
[ 9184.778649] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
[ 9243.636550] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9243.638973] EXT3-fs: recovery complete.
[ 9243.638976] EXT3-fs: mounted filesystem with ordered data mode.
[ 9305.343298] EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended
[ 9305.345249] EXT3-fs: mounted filesystem with ordered data mode.
[ 9328.776678] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal
[15048.450805] EXT3-fs: recovery complete.
[15048.452800] EXT3-fs: mounted filesystem with ordered data mode.
[15055.778655] EXT3-fs error (device sdb2): ext3_put_super: Couldn't clean up the journal

ok it seems one of partitions is broken i've looked around the web
try to :
e2fsck -p your /home partitions and
fsck.vfat -p /dev/sdb1 and e2fsck -p /dev/sdb2

I don't use any kind of automation, not even hal, but I have the same issue, without corruption though.
However, I have found that using cfdisk on /dev/sdb makes /dev/sdb{1,2} appear magically, and I can mount them correctly.
That's not really elegant, but it works for me.
I use adb push most of the time anyways, that way I don't have to unmount the SD from the phone and everything is smooth.

Zappletoo said:
I don't use any kind of automation, not even hal, but I have the same issue, without corruption though.
However, I have found that using cfdisk on /dev/sdb makes /dev/sdb{1,2} appear magically, and I can mount them correctly.
That's not really elegant, but it works for me.
I use adb push most of the time anyways, that way I don't have to unmount the SD from the phone and everything is smooth.
Click to expand...
Click to collapse
tht's strange cfdisk should not help mounting the devices but if it work it's worthing give it a try.
it has to be something with hal and rules :
emerge -pv hal dbus
etc-update
should get rid of that problem
PS : Zappletoo what linux distribution are you using ??

Gentoo.
But I don't use HAL, I don't see any good reason to. I'll try to activate it to see if it makes a difference, but I doubt it.
I'm not sure why cfdisk helps, maybe it simply updates the partition table somewhere.
Update : starting hald makes it work. Using partprobe works as well.. So I guess I was right about the partition table part.

what do you mean use cfdisk on it?
did you just select mount from the phone, then run cfdisk /dev/sdb, then immediately quit?

no no run cfdisk on your computer
Edit: yes I misread. That's what he did.
If things goes well your 2 partitions should appear

John5788 said:
what do you mean use cfdisk on it?
did you just select mount from the phone, then run cfdisk /dev/sdb, then immediately quit?
Click to expand...
Click to collapse
Yes, on the computer.
Apparently it does the same as partprobe, which is available in the sys-apps/parted package.
Hald does everything automatically though, but it's bloated.

Never had a problem with gentoo. No Hal...udev 1.41...custom kernel. Somewhere else on this forum however someone pointed out the phone doesn't show up properly in linux without first probing it. i.e. 'fdisk -l /dev/sda'. This has worked for me whenever I choose to mount it (which is almost never cuz i love adb).

[Resolved] Huawei P8 Lite - Flashing shrinked the /data partition

Some info:
Code:
Phone: Huawei P8 Lite (ALE-L21) - 1 SIM
So, i've been rooting my device and got it working after probably 12 hours of downloading Firmwares that were corrupted and had slow download speed and flashing up to 12 updates.
I got it working, still not rooted but i can live with that. TWRP is enough.
The problem is, I've downloaded some apps, and some updates were applied from Google Play.
What I've encountered is that the memory is just 2G big!
That's so strange, because I've already had a bigger storage size before flashing.
I'll show you what's the problem:
As i've found out, mmcblk0 is the internal NAND memory.
So, we fetch the partition table which is stored in mmcblk0
Code:
/data # fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 30785536 sectors, 2744M
Logical sector size: 512
Disk identifier (GUID): f9f21fff-a8d4-5f0e-9746-594869aec34e
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30785535
Number Start (sector) End (sector) Size Code Name
...
40 8118272 30785535 [U][COLOR="Red"]10.8G[/COLOR][/U] 0700 userdata
Ok, so now we have this information,
Partition is 10.8G big
The partition name in the /dev/block is mmcblk0p40 (as mmcblk0 is the main internal disk and "/data" partition is the 40th partition)
Ok, It's least 10G big, so, what's the problem?
We see the partition is 10.8G big. BUT...
If we use "df" we can see the real deal
Code:
/data # df -h
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p10
11.7M 7.3M 4.1M 64% /mnvm1:0
tmpfs 917.2M 16.0K 917.2M 0% /dev
tmpfs 917.2M 16.0K 917.2M 0% /tmp
/dev/block/mmcblk0p40
[U][COLOR="Red"]2.4G[/COLOR][/U] 2.4G 50.6M 98% /data
My mom's phone, that is the same phone as mine.
i(dot)imgur(dot)com(slash)dZcD1ME(dot)png
Mine instead
i(dot)imgur(dot)com(slash)Z9aybBu(dot)png
Anyone knows what's going on?
Do i need to wipe partition?
Do i need to resize fs?
Thanks beforehand

Solution:
If you have TWRP:
Wipe -> Advanced Wipe -> Select "Data" and press "Repair or Change File System" -> Resize -> Swipe to Resize
If you dont have TWRP:
Use resize2fs command

SD Card access

I've made this mistake before, and it drives me nuts. I changed phones and put my old phones sd card in my new phone (Nokia 8.3). I was just going to see if it could read it. It couldn't and asked me if I wanted to format. I selected no, and removed the card. I put the card in my linux computer and I can't mount it. I did get a replacement for my old phone through warranty (teracube) and tried putting it in that, and it wouldn't read it either. I've had this problem before. I think even having the sdcard in a phone does something to it even if you don't format it. I think I formatted the card initially as ext2 but I could be mistaken.
Any help would be appreciated. I really want to recover the data.
mount:
Code:
[3630 21-01-23 7:06][email protected]/home/larry%sudo mount /dev/sda2 /mnt/tmp
NTFS signature is missing.
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
[3630 21-01-23 7:06][email protected]/home/larry%sudo mount -tvfat /dev/sda2 /mnt/tmp
mount: /mnt/tmp: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.
fdisk:
Code:
[3630 21-01-23 7:06][email protected]/home/larry%sudo fdisk /dev/sda
Command (m for help): p
Disk /dev/sda: 119.1 GiB, 127865454592 bytes, 249737216 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
Disklabel type: gpt
Disk identifier: C8FBA780-1A1F-4B71-8D9D-D623A671C61D
Device Start End Sectors Size Type
/dev/sda1 2048 34815 32768 16M unknown
/dev/sda2 34816 249737182 249702367 119.1G unknown

An SD-card ( from Android's point of view it's a portable USB-device ) usually is FAT32 formatted, AFAIK, but I may err as always ...

Question How to gain read/write access after Magisk Root?

Hi,
I just got this phone and it seems promising, really dig the screen size, although i need some getting used to the UI.
After following some of the tutorials on magisk rooting I've seem to have rooted the phone since i can see the root files, but most of the /system/ files are read only which limits a lot what i wanted to do with it.
I've followed the popular Universal RW tutorial for android 10+ by lebigmac, but it doesn't seem to be working for this phone. Only once have i successfully gotten the image, but then it would not flash. I've been up all night and have come up short.
Has anyone else gained RW on the whole filesystem? If so, how?
Bonus: Has anyone gotten MicroG to work successfully? How do you signature spoof?
Thanks.

Atlas667 said:
Hi,
I just got this phone and it seems promising, really dig the screen size, although i need some getting used to the UI.
After following some of the tutorials on magisk rooting I've seem to have rooted the phone since i can see the root files, but most of the /system/ files are read only which limits a lot what i wanted to do with it.
I've followed the popular Universal RW tutorial for android 10+ by lebigmac, but it doesn't seem to be working for this phone. Only once have i successfully gotten the image, but then it would not flash. I've been up all night and have come up short.
Has anyone else gained RW on the whole filesystem? If so, how?
Bonus: Has anyone gotten MicroG to work successfully? How do you signature spoof?
Thanks.
Click to expand...
Click to collapse
Much needed topic I tried alot and no luck!

Atlas667 said:
Hi,
I just got this phone and it seems promising, really dig the screen size, although i need some getting used to the UI.
After following some of the tutorials on magisk rooting I've seem to have rooted the phone since i can see the root files, but most of the /system/ files are read only which limits a lot what i wanted to do with it.
I've followed the popular Universal RW tutorial for android 10+ by lebigmac, but it doesn't seem to be working for this phone. Only once have i successfully gotten the image, but then it would not flash. I've been up all night and have come up short.
Has anyone else gained RW on the whole filesystem? If so, how?
Bonus: Has anyone gotten MicroG to work successfully? How do you signature spoof?
Thanks.
Click to expand...
Click to collapse
Hey did you ever find a way to gain access to read/write?

cwgzz said:
Hey did you ever find a way to gain access to read/write?
Click to expand...
Click to collapse
Not yet. I tried the superrepack scripts, but they did not work either. It never gave me a boot loop, but it also never gave me R/W on root. If you read the superrepack thread there seems to be talk of Motorola implementing Forward Error Correction, but i dont know if that would apply in this case. The error i had when running Superrepack was "Unable to open /dev/block/sde24".
Maybe try superrepack yourself and we can determine if it was user error or the phone/script.

Atlas667 said:
I've followed the popular Universal RW tutorial for android 10+ by lebigmac, but it doesn't seem to be working for this phone. Only once have i successfully gotten the image, but then it would not flash. I've been up all night and have come up short.
Click to expand...
Click to collapse
Hi @Atlas667 thanks for your interest in my SystemRW / SuperRW feat. MakeRW project.
What do you mean it didn't work on your device? If you don't send me your log files or give me any feedback how do you expect me to make it work for your Motorola device? I only have Xiaomi device...
Also keep in mind brand new version of my script will be released very soon. If you want to give me additional feedback to make it work for your device then now is the time to do it

lebigmac said:
Hi @Atlas667 thanks for your interest in my SystemRW / SuperRW feat. MakeRW project.
What do you mean it didn't work on your device? If you don't send me your log files or give me any feedback how do you expect me to make it work for your Motorola device? I only have Xiaomi device...
Also keep in mind brand new version of my script will be released very soon. If you want to give me additional feedback to make it work for your device then now is the time to do it
Click to expand...
Click to collapse
Hey, thanks for your work.
I have a fresh root on my devie and ill go through the process at the same time as i write this.
I have downloaded extracted and copied systemrw_1.32 into /data/local/tmp.
Therefore i now have /data/local/tmp/systemrw_1.32 and i make systemrw.sh executable
I run the command for detecting my super partition:
Bash:
denver:/data/local/tmp # ls -l /dev/block/by-name/super
lrwxrwxrwx 1 root root 16 1970-05-08 11:21 /dev/block/by-name/super -> /dev/block/sde24
Then i run the shared blocks detect commands i get this.
Bash:
denver:/data/local/tmp # for a in /dev/block/dm-*; do tune2fs -l $a | grep -e "feat" -e "vol"; done
Filesystem volume name: /
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem volume name: system_ext
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem volume name: vendor
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem volume name: product
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem volume name: /
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
Filesystem volume name: system_ext
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
Filesystem volume name: vendor
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
Filesystem volume name: product
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
tune2fs: Bad magic number in super-block while trying to open /dev/block/dm-8
Filesystem volume name: <none>
Filesystem features: ext_attr dir_index filetype extent sparse_super large_file huge_file uninit_bg dir_nlink extra_isize shared_blocks
I go into the /data/local/tmp/systemrw_1.32
And i run ./systemrw.sh which produces:
Bash:
denver:/data/local/tmp/systemrw_1.32 # ./systemrw.sh
--------------------------------------------------
| SystemRW v1.32 automated script by lebigmac |
| @xda ©2021 Big thank you to @Kolibass @Brepro1 |
|@munjeni @AndyYan @gabrielfrias @YOisuPU @bynarie |
| without your help this would not be possible! |
--------------------------------------------------
systemrw: Initiating procedure...
systemrw: Device is in Android mode. Ignoring
systemrw: Current device: motorola
systemrw: Current Android version: 11
systemrw: Current SELinux status: Permissive
systemrw: Current slot is: 1
systemrw: Your super partition is located at: /dev/block/sde24
systemrw: / is read-only
systemrw: /product is read-only
systemrw: /vendor is read-only
systemrw: Adjusting permissions...
systemrw: Attempting to disable dm-verity and verification...
verification is already disabled on slot with suffix _b.
verity is already disabled on slot with suffix _b.
systemrw: Dumping super partition to: /data/local/tmp/systemrw_1.32/img/super_original.bin
systemrw: Please wait patiently...
27262976+0 records in
27262976+0 records out
13958643712 bytes (13 G) copied, 83.699237 s, 159 M/s
systemrw: Successfully dumped super partition to: /data/local/tmp/systemrw_1.32/img/super_original.bin
systemrw: Unpacking embedded partitions from /data/local/tmp/systemrw_1.32/img/super_original.bin
systemrw: Nested partitions were successfully extracted from super
systemrw: Current size of system_a.img in bytes: 896122880
systemrw: Current size of system_a.img in MB: 854
systemrw: Current size of system_a.img in 512-byte sectors: 1750240
systemrw: NO 'shared_blocks feature' detected @ system_a.img
systemrw: Shrinking size of system_a.img back to minimum size...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/system_a.img to 202516 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/system_a.img is now 202516 (4k) blocks long.
=================================================
systemrw: Current size of system_ext_a.img in bytes: 666558464
systemrw: Current size of system_ext_a.img in MB: 635
systemrw: Current size of system_ext_a.img in 512-byte sectors: 1301872
systemrw: NO 'shared_blocks feature' detected @ system_ext_a.img
systemrw: Shrinking size of system_ext_a.img back to minimum size...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/system_ext_a.img to 145668 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/system_ext_a.img is now 145668 (4k) blocks long.
=================================================
systemrw: Current size of vendor_a.img in bytes: 896487424
systemrw: Current size of vendor_a.img in MB: 854
systemrw: Current size of vendor_a.img in 512-byte sectors: 1750952
systemrw: NO 'shared_blocks feature' detected @ vendor_a.img
systemrw: Shrinking size of vendor_a.img back to minimum size...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/vendor_a.img to 207489 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/vendor_a.img is now 207489 (4k) blocks long.
=================================================
systemrw: Current size of product_a.img in bytes: 3711655936
systemrw: Current size of product_a.img in MB: 3539
systemrw: Current size of product_a.img in 512-byte sectors: 7249328
systemrw: NO 'shared_blocks feature' detected @ product_a.img
systemrw: Shrinking size of product_a.img back to minimum size...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/product_a.img to 901908 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/product_a.img is now 901908 (4k) blocks long.
=================================================
systemrw: Current size of system_b.img in bytes: 896122880
systemrw: Current size of system_b.img in MB: 854
systemrw: Current size of system_b.img in 512-byte sectors: 1750240
systemrw: 'shared_blocks feature' detected @ system_b.img
systemrw: Increasing filesystem size of system_b.img...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/system_b.img to 273475 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/system_b.img is now 273475 (4k) blocks long.
systemrw: Removing 'shared_blocks feature' of system_b.img...
e2fsck 1.45.4 (23-Sep-2019)
systemrw: Read-only lock of system_b.img successfully removed
systemrw: Shrinking size of system_b.img back to minimum size...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/system_b.img to 230418 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/system_b.img is now 230418 (4k) blocks long.
=================================================
systemrw: Current size of system_ext_b.img in bytes: 666583040
systemrw: Current size of system_ext_b.img in MB: 635
systemrw: Current size of system_ext_b.img in 512-byte sectors: 1301920
systemrw: 'shared_blocks feature' detected @ system_ext_b.img
systemrw: Increasing filesystem size of system_ext_b.img...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/system_ext_b.img to 203425 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/system_ext_b.img is now 203425 (4k) blocks long.
systemrw: Removing 'shared_blocks feature' of system_ext_b.img...
e2fsck 1.45.4 (23-Sep-2019)
systemrw: Read-only lock of system_ext_b.img successfully removed
systemrw: Shrinking size of system_ext_b.img back to minimum size...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/system_ext_b.img to 164146 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/system_ext_b.img is now 164146 (4k) blocks long.
=================================================
systemrw: Current size of vendor_b.img in bytes: 896487424
systemrw: Current size of vendor_b.img in MB: 854
systemrw: Current size of vendor_b.img in 512-byte sectors: 1750952
systemrw: 'shared_blocks feature' detected @ vendor_b.img
systemrw: Increasing filesystem size of vendor_b.img...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/vendor_b.img to 273586 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/vendor_b.img is now 273586 (4k) blocks long.
systemrw: Removing 'shared_blocks feature' of vendor_b.img...
e2fsck 1.45.4 (23-Sep-2019)
systemrw: Read-only lock of vendor_b.img successfully removed
systemrw: Shrinking size of vendor_b.img back to minimum size...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/vendor_b.img to 220492 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/vendor_b.img is now 220492 (4k) blocks long.
=================================================
systemrw: Current size of product_b.img in bytes: 3711660032
systemrw: Current size of product_b.img in MB: 3539
systemrw: Current size of product_b.img in 512-byte sectors: 7249336
systemrw: 'shared_blocks feature' detected @ product_b.img
systemrw: Increasing filesystem size of product_b.img...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/product_b.img to 1132708 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/product_b.img is now 1132708 (4k) blocks long.
systemrw: Removing 'shared_blocks feature' of product_b.img...
e2fsck 1.45.4 (23-Sep-2019)
systemrw: Read-only lock of product_b.img successfully removed
systemrw: Shrinking size of product_b.img back to minimum size...
resize2fs 1.45.4 (23-Sep-2019)
Resizing the filesystem on /data/local/tmp/systemrw_1.32/img/product_b.img to 924153 (4k) blocks.
The filesystem on /data/local/tmp/systemrw_1.32/img/product_b.img is now 924153 (4k) blocks long.
=================================================
systemrw: Joining all extracted images back into one single super image...
systemrw: Please wait and ignore the invalid sparse warnings...
Invalid sparse file format at header magic
Invalid sparse file format at header magic
Invalid sparse file format at header magic
Invalid sparse file format at header magic
Invalid sparse file format at header magic
Invalid sparse file format at header magic
Invalid sparse file format at header magic
Invalid sparse file format at header magic
systemrw: Successfully created patched super image @
systemrw: /data/local/tmp/systemrw_1.32/img/super_fixed.bin
systemrw: Congratulations! Your image(s) should now have R/W capability
systemrw: Please reboot into bootloader and flash the file(s) manually
denver:/data/local/tmp/systemrw_1.32 #
After that, i copy super_fixed.bin to my computer, boot my phone into recovery and use fastboot flash super to flash:
Bash:
Sending sparse 'super' 1/16 (769727 KB) OKAY [ 25.722s]
Writing 'super' OKAY [ 0.103s]
Sending sparse 'super' 2/16 (762769 KB) OKAY [ 26.191s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 3/16 (754767 KB) OKAY [ 27.851s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 4/16 (723716 KB) OKAY [ 23.787s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 5/16 (769724 KB) OKAY [ 27.542s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 6/16 (769726 KB) OKAY [ 25.579s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 7/16 (769725 KB) OKAY [ 24.952s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 8/16 (759887 KB) OKAY [ 24.984s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 9/16 (706722 KB) OKAY [ 22.790s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 10/16 (739235 KB) OKAY [ 24.188s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 11/16 (750459 KB) OKAY [ 24.374s]
Writing 'super' OKAY [ 0.016s]
Sending sparse 'super' 12/16 (768332 KB) OKAY [ 25.115s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 13/16 (769724 KB) OKAY [ 25.250s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 14/16 (769724 KB) OKAY [ 24.980s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 15/16 (676812 KB) OKAY [ 22.618s]
Writing 'super' OKAY [ 0.000s]
Sending sparse 'super' 16/16 (668353 KB) OKAY [ 22.105s]
Writing 'super' OKAY [ 0.000s]
Finished. Total time: 487.440s
Now i am in a recovery boot loop.
Ive tried flashing vbmeta and super from my original rom files, but it wont boot normally.
The only way to get it to boot is to reflash the whole stock rom. And im back to square one.

Flash back to stock with smart assistant.
Use @Electimon custom twrp recovery which is labeled as osaka variant on his site
1pwn.ixmoe
(fastboot boot twrp.img)
and @ArtiicPanda has custom skym3 kernel you should flash the zip in twrp through the install button.
Reboot to bootloader and fastboot to twrp again.
Now install the systemrw.zip
Wait for finish and Do not reboot due to error code.
Boot of into Linux distro, plug in your device and run the sysrw_1.32.sh shell script. Wait for it to finish (will take a long time).
When complete fastboot boot back into twrp and wipe dalvik cache/cache then reboot system.
Cake!!!