Related
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....
About:
fastboot stores each file it receives in RAM before flashing it to your Android device.
For this reason, large partitions (such as the /system partition) must be splitted using the "compressed ext4 file system sparse image format",
this format is defined by the AOSP (Android Open Source Project) and was designed for the single purpose of flashing a large partition.
If you tried to flash system.img from backup and received the "Invalid sparse file format at header magi" error, you have come to the right place.
The Solution:
SparseConverter is a tool that can create / decompress compressed ext4 file system sparse image format (e.g. system.img_sparsechunk1).
Note for Motorola phone owners:
The factory images from Motorola contains a 128KB motorola header and a 4KB motorola footer, if you decompress those images you may want to remove the header and footer.
I had no problem using the standard Android fastboot with my unlocked Moto G and flashing images without the Motorola header / footer.
(If you keep the header / footer, then you must use Motorola's fastboot)
Usage Examples:
SparseConverter.exe /compress D:\system.img E:\ 256MB
( will compress D:\system.img to 256MB sparse files starting from E:\system.img_sparsechunk1 )
SparseConverter.exe /decompress E:\system.img_sparsechunk1 D:\system.img
( will decompress E:\system.img_sparsechunk1, E:\system.img_sparsechunk2 and etc. to D:\system.img )
The software may contain bugs and/or limitations that may result in damage to your phone, I take no responsibility for any damage that may occur.
For additional information about the "compressed ext4 file system sparse image format" see libsparse/sparse_format.h
p.s. Source code in C# is provided, Windows XP \ 2003 users must install the .Net Framework 2.0 before running this tool.
How can i flash system.img when is too large. i have compressed it using this tool, now how to flash?
Everything is explained in the original post, You need to use fastboot.exe which is part of the ADT bundle (Android Development Tools).
tal.aloni said:
Everything is explained in the original post, You need to use fastboot.exe which is part of the ADT bundle (Android Development Tools).
Click to expand...
Click to collapse
fastboot flash system system.img_sparsechunk1 ?
Not working for me. :/
It will be downloaded to device, but not flashed.
yes,
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
make sure the system partition size match the image that you're trying to flash, to flash a bigger image you'll have to reflash the partition table and all the partitions (boot, recovery etc.)
p.s. not sure what "not working" means, what error do you get exactly?
tal.aloni said:
yes,
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
make sure the system partition size match the image that you're trying to flash, to flash a bigger image you'll have to reflash the partition table and all the partitions (boot, recovery etc.)
p.s. not sure what "not working" means, what error do you get exactly?
Click to expand...
Click to collapse
Here is my error code, after attemp to flash system system.img_sparechunk1:
FAILED (remote: flash_cmds error!)
partition size match, it is system dump from another same device.
Sorry, I'm not familiar with this error.
tal.aloni said:
Sorry, I'm not familiar with this error.
Click to expand...
Click to collapse
I have Rooted my ASUS Tablet, and deleted something in system, now i am soft-bricked.
Now i cannot do somethnig, only use fastboot, butt i cannot flash system.
So i must waiting to developers, to port CWM/TWRP for my device.
Hi, I'm trying to convert a userdata.img file (60GB!) so I can flash it with fastboot onto my phone, when I run the tool I get this
Code:
C:\Users\Matt\Documents\SparseConverter_1.0.0>sparseconverter /compress C:\Users
\Matt\Documents\userdata.img "C:\Users\Matt\Documents\userdata sparse" 256MB
Image size is not a multiple of 4096 bytes
Does this mean that it won't convert my image? Thanks
EDIT: Also I know this image is valid as under linux
Code:
[email protected]:~$ sudo mount -t ext4 -o loop /home/matt/userdata.img /home/matt/ext4
[sudo] password for matt:
[email protected]:~$ sudo su
[email protected]:/home/matt# cd ext4
[email protected]:/home/matt/ext4# ls
anr bugreports dontpanic media resource-cache user
app cam_socket1 dpm mediadrm security
app-asec cam_socket2 drm misc shared
app-lib connectivity fdAlbum nfc system
app-private dalvik-cache local opponvitems time
backup data lost+found property tombstones
Hi Matt,
ext4 allocates storage space in units of "blocks". A block is a group of sectors between 1KiB and 64KiB, and the number of sectors must be an integral power of 2. Block size is specified at mkfs time and typically is 4KiB.
Click to expand...
Click to collapse
The sector size for most flash devices is 4096 bytes.
The "compressed ext4 file system sparse image format" assumes that the image is going to be flashed to a flash device, and thus expects its size to be a multiple of 4096 bytes.
I'm not sure how you created this user data partition image, the size of a proper image (for flashing purposes) should be a multiple of 4096 bytes.
Edit: BlockSize can be set to 512 instead of 4096 in SparseConverter source code (SparseCompressionHelper.cs).
tal.aloni said:
Hi Matt,
The sector size for most flash devices is 4096 bytes.
The "compressed ext4 file system sparse image format" assumes that the image is going to be flashed to a flash device, and thus expects its size to be a multiple of 4096 bytes.
I'm not sure how you created this user data partition image, the size of a proper image (for flashing purposes) should be a multiple of 4096 bytes.
Click to expand...
Click to collapse
I ran into this issue as well. I am trying to compress the userdata image from my phone that was previously bricked and I'd like to find a way to hold onto this data.
Thank you!
hazard666 said:
I ran into this issue as well. I am trying to compress the userdata image from my phone that was previously bricked and I'd like to find a way to hold onto this data.
Thank you!
Click to expand...
Click to collapse
How did you create this image? are you sure it's a raw image?
if it's indeed a raw image, you could append a the necessary amount of zero bytes to the image (e.g. using HxD) and then you could compress it.
I'm not sure what you mean by "hold onto this data", this tool is to prepare an image for flashing, if you're trying to access the files there are other methods (e.g. linux).
Awesome, I use this tool to compress system file of Motorola X2014 of 2.7GB that I was not able to flash it... works great, thank you so much
Great progress! In my case
I generate my system.img.raw by
adb root
adb wait-for-device
adb shell "dd if=/dev/block/platform/f9824900.sdhci/by-name/system of=/sdcard/system.img.raw"
adb pull -p /sdcard/system.img.raw
1st Trail below will NOT works, but at the end you will see my solution:
Windows cmd log:
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>sparseconverter /compress system.img.raw .\ 536870912
...
pause
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>fastboot flash system system.img.raw_
sparsechunk1
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.591s]
sending 'system' (524284 KB)...
OKAY [ 1.350s]
writing 'system'...
OKAY [ 13.953s]
finished. total time: 15.897s
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>fastboot flash system system.img.raw_
sparsechunk2
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.532s]
sending 'system' (524287 KB)...
OKAY [ 1.351s]
writing 'system'...
OKAY [ 8.678s]
finished. total time: 10.565s
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>fastboot flash system system.img.raw_
sparsechunk3
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.524s]
sending 'system' (411515 KB)...
OKAY [ 1.075s]
writing 'system'...
OKAY [123.069s]
finished. total time: 124.671s
Please note even we pass the fastboot flashing, but it does NOT works after flash is finished, the phone can reboot to Linux logo, but block there, can not start Android Animation and go to desktop.
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
SO, SOLUTION is:
as an conclusion, it seems fastboot can not manage the multi input images well, BUT it can handle a single compressed image files, so set the max image side to the partition size to 2684354560 can make fastboot works well.
I need to find my original dd output file system.img.raw in 2.5GB, then:
Windows cmd logs:
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>sparseconverter /compress system.img.raw .\ 2684354560
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>fastboot flash system system.img.raw_sp
arsechunk1
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.767s]
sending sparse 'system' (521371 KB)...
OKAY [ 4.530s]
writing 'system'...
OKAY [ 9.577s]
sending sparse 'system' (511116 KB)...
OKAY [ 6.465s]
writing 'system'...
OKAY [ 10.833s]
sending sparse 'system' (445892 KB)...
OKAY [ 6.274s]
writing 'system'...
OKAY [139.377s]
finished. total time: 177.831s
that will bring my system.img.raw back to my phone WELL
you can see my rooted su is there, ^_^:
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>adb shell
[email protected]:/ $ su
su
[email protected]:/ #
Matt, hazard666,
I was wrong, there is no restriction on BlockSize , you're welcome to download SparseConverter source code and set BlockSize to 512 (in SparseCompressionHelper.cs),
please let me know if this helps.
tal.aloni said:
Note for Motorola phone owners:
The factory images from Motorola contains a 128KB motorola header and a 4KB motorola footer, if you decompress those images you may want to remove the header and footer.
I had no problem using the standard Android fastboot with my unlocked Moto G and flashing images without the Motorola header / footer.
(If you keep the header / footer, then you must use Motorola's fastboot)
Click to expand...
Click to collapse
Hi, I used your tool to decompress sparsechunks into a single system image for the Moto X 2014 XT1097, AT&T. This is needed as a preliminary step in order to get root.
The next step is to convert the image into an ext4 format. However, the instructions we have to do that require using linux command simg2img and it doesn't like the header. The errors are:
"Invalid sparse file format at header magi
Failed to read sparse file"
"Bad magic"
or
"Error reading sparse file header"
How do we get rid of this header? Thanks!
JulesJam said:
How do we get rid of this header? Thanks!
Click to expand...
Click to collapse
I usually do it manually with HxD (hex editor).
JulesJam said:
The next step is to convert the image into an ext4 format. However, the instructions we have to do that require using linux command simg2img and it doesn't like the header.
Click to expand...
Click to collapse
I think you're confused, once the image is decompressed, it's no longer a sparse file, you shouldn't use simg2img (to convert it to raw image, because it's already been done).
instead, you can just mount the image, for ext4 it would be:
Code:
sudo mount -t ext4 -o loop,offset=131072 system.img mnt/
and when you're done customizing:
Code:
sudo ./make_ext4fs -l 840M -a system mysystem.img mnt/
sudo umount mnt
(note that I've used offset=131072 instead of removing the header)
tal.aloni said:
I think you're confused, once the image is decompressed, it's no longer a sparse file, so you shouldn't use simg2img.
Click to expand...
Click to collapse
Yeah, I am definitely confused, lol!
tal.aloni said:
instead, use something along the line of (note that I've used offset=131072 instead of removing the header):
Code:
sudo mount -t ext4 -o loop,offset=131072 system.img mnt/
sudo ./make_ext4fs -l 840M -a system mysystem.img mnt/
sudo umount mnt
Click to expand...
Click to collapse
Ok great, I will have someone who knows linux try that. What we want is a single file system image in ext4 format so hopefully that will work!
Thanks!
tal.aloni said:
I usually do it manually with HxD (hex editor).
I think you're confused, once the image is decompressed, it's no longer a sparse file, you shouldn't use simg2img (to convert it to raw image, because it's already been done).
instead, you can just mount the image, for ext4 it would be:
Code:
sudo mount -t ext4 -o loop,offset=131072 system.img mnt/
and when you're done customizing:
Code:
sudo ./make_ext4fs -l 840M -a system mysystem.img mnt/
sudo umount mnt
(note that I've used offset=131072 instead of removing the header)
Click to expand...
Click to collapse
JulesJam said:
Yeah, I am definitely confused, lol!
Ok great, I will have someone who knows linux try that. What we want is a single file system image in ext4 format so hopefully that will work!
Thanks!
Click to expand...
Click to collapse
And I'm someone who's running a Linux distro!
After the second command I'm getting a memory allocation error though
"error: do_inode_allocate_extents: Failed to allocate 6524 blocks"
tal.aloni said:
I think you're confused, once the image is decompressed, it's no longer a sparse file, you shouldn't use simg2img (to convert it to raw image, because it's already been done).
Click to expand...
Click to collapse
Also, just to be complete, the way I am going to modify/root the ext4 image is by using TWRP on a bootloader unlocked device according to these instructions:
http://forum.xda-developers.com/showpost.php?p=60389310&postcount=177
It worked for the XT1096 so it should work for the XT1097. Once we get the rooted ext4 image, we have a tool to flash it to the XT1097 that bypasses the signature check. Our bootloaders are locked so we have to do it this way.
Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
any other thoughts on why this issue would occur?
Got another crash last night, again copying a lot of new music onto the phone from computer. Crash call stack is different this time though.
Code:
[ 7523.190689] Buffer I/O error on device mmcblk0p15, logical block 6850041
[ 7523.197373] Buffer I/O error on device mmcblk0p15, logical block 6850042
[ 7523.204241] Buffer I/O error on device mmcblk0p15, logical block 6850043
[ 7523.210711] Buffer I/O error on device mmcblk0p15, logical block 6850044
[ 7523.217395] Buffer I/O error on device mmcblk0p15, logical block 6850045
[ 7523.224140] Buffer I/O error on device mmcblk0p15, logical block 6850046
[ 7523.230732] Buffer I/O error on device mmcblk0p15, logical block 6850047
[ 7523.237721] Aborting journal on device mmcblk0p15-8.
[ 7523.288385] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[ 7523.633754] cypress_touchkey 16-0020: not real interrupt (1).
[ 7524.010986] EXT4-fs error (device mmcblk0p15): ext4_journal_start_sb:328: Detected aborted journal
[ 7524.018982] EXT4-fs (mmcblk0p15): Remounting filesystem read-only
[ 7524.061985] Kernel panic - not syncing: EXT4-fs panic from previous error
[ 7524.062016]
[ 7524.069340] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c07b5180>] (panic+0x88/0x1f8)
[ 7524.077459] [<c07b5180>] (panic+0x88/0x1f8) from [<c01a0714>] (__ext4_abort+0xc0/0xe0)
[ 7524.085394] [<c01a0714>] (__ext4_abort+0xc0/0xe0) from [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8)
[ 7524.094794] [<c01a0b34>] (ext4_journal_start_sb+0x154/0x1b8) from [<c018b140>] (ext4_dirty_inode+0x14/0x40)
[ 7524.104530] [<c018b140>] (ext4_dirty_inode+0x14/0x40) from [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4)
[ 7524.113839] [<c014e37c>] (__mark_inode_dirty+0x2c/0x1c4) from [<c0141c9c>] (file_update_time+0x100/0x120)
[ 7524.123392] [<c0141c9c>] (file_update_time+0x100/0x120) from [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428)
[ 7524.133586] [<c00f15a4>] (__generic_file_aio_write+0x2cc/0x428) from [<c00f1760>] (generic_file_aio_write+0x60/0xc8)
[ 7524.144085] [<c00f1760>] (generic_file_aio_write+0x60/0xc8) from [<c01819e4>] (ext4_file_write+0x258/0x2bc)
[ 7524.153821] [<c01819e4>] (ext4_file_write+0x258/0x2bc) from [<c012b108>] (do_sync_write+0x9c/0xd8)
[ 7524.162763] [<c012b108>] (do_sync_write+0x9c/0xd8) from [<c012b1ec>] (vfs_write+0xa8/0x130)
[ 7524.171095] [<c012b1ec>] (vfs_write+0xa8/0x130) from [<c012b414>] (sys_pwrite64+0x50/0x80)
[ 7524.179275] [<c012b414>] (sys_pwrite64+0x50/0x80) from [<c000de80>] (ret_fast_syscall+0x0/0x30)
[ 7524.188004] CPU1: stopping
[ 7524.190659] [<c00138c8>] (unwind_backtrace+0x0/0xe0) from [<c001294c>] (handle_IPI+0x100/0x1cc)
[ 7524.199357] [<c001294c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[ 7524.207964] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000dc3c>] (__irq_usr+0x3c/0x60)
[ 7524.216296] Exception stack(0xc6637fb0 to 0xc6637ff8)
[ 7524.221271] 7fa0: b65f8b76 b6ed66d7 b65f8b77 00000037
[ 7524.229481] 7fc0: 00000000 b6ed66da b65faba4 b65f8b54 b65f8b74 b796f610 b6ed5398 00000000
[ 7524.237630] 7fe0: 50704001 b65f8b3c b6ecb283 b6ebf55c 60030030 ffffffff
[ 7524.344360] Rebooting in 5 seconds..
[ 7529.347686] Going down for restart now
[ 7529.350708] msm_restart : clear reset flag
Wrong forum or the content too technical for people?
BSOD2600 said:
Phone: Galaxy S3 VZW 32GB
Recovery: TWRP 2.7.1.0
Mod: CM11 m8
Kernel, governer, etc all CM11 stock.
Problem:
Twice today the phone rebooted itself while performing large file copy operations. last_kmsg from both reboots basically look the same:
Code:
[40996.107363] Buffer I/O error on device mmcblk0p15, logical block 6751031
[40996.114291] Buffer I/O error on device mmcblk0p15, logical block 6751032
[40996.120761] Buffer I/O error on device mmcblk0p15, logical block 6751033
[40996.127476] Buffer I/O error on device mmcblk0p15, logical block 6751034
[40996.134160] Buffer I/O error on device mmcblk0p15, logical block 6751035
[40996.140813] Buffer I/O error on device mmcblk0p15, logical block 6751036
[40996.147528] Buffer I/O error on device mmcblk0p15, logical block 6751037
[40996.154181] Buffer I/O error on device mmcblk0p15, logical block 6751038
[40996.160926] Buffer I/O error on device mmcblk0p15, logical block 6751039
[41056.701656] ACDB=> get_hw_delay: Path = 0 samplerate = 48000 usec = 0 status 0
[41056.708065] afe_callback: cmd = 0x100dc returned error = 0x3
[41056.713681] afe_send_hw_delay: config cmd failed
[41065.991721] kgsl kgsl-3d0: |kgsl_late_resume_driver| late resume start
[41066.310781] cypress_touchkey 16-0020: not real interrupt (1).
[41117.725034] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 113, 644 clusters in bitmap, 530 in gd
[41117.744476] Aborting journal on device mmcblk0p15-8.
[41117.764161] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[41117.764161]
[41117.773257] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0778f40>] (panic+0x88/0x1f8)
[41117.781344] [<c0778f40>] (panic+0x88/0x1f8) from [<c01a7134>] (ext4_handle_error+0x8c/0x98)
[41117.789738] [<c01a7134>] (ext4_handle_error+0x8c/0x98) from [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4)
[41117.799626] [<c01a7ca0>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[41117.810125] [<c01b6618>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0)
[41117.820288] [<c01b8620>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4)
[41117.830085] [<c01b8db8>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c)
[41117.840005] [<c01ba0fc>] (ext4_mb_find_by_goal+0x3c/0x23c) from [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388)
[41117.850351] [<c01ba9e0>] (ext4_mb_regular_allocator+0x4c/0x388) from [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0)
[41117.860728] [<c01bc120>] (ext4_mb_new_blocks+0x1fc/0x5c0) from [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac)
[41117.870739] [<c01b31d8>] (ext4_ext_map_blocks+0xfcc/0x15ac) from [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4)
[41117.880353] [<c018cf7c>] (ext4_map_blocks+0xf8/0x2e4) from [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c)
[41117.890241] [<c0190d4c>] (mpage_da_map_and_submit+0x114/0x57c) from [<c0191908>] (ext4_da_writepages+0x340/0x5b8)
[41117.900496] [<c0191908>] (ext4_da_writepages+0x340/0x5b8) from [<c00ff3e0>] (do_writepages+0x24/0x38)
[41117.909713] [<c00ff3e0>] (do_writepages+0x24/0x38) from [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c)
[41117.919419] [<c00f6d14>] (__filemap_fdatawrite_range+0x60/0x6c) from [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68)
[41117.930436] [<c00f6de8>] (filemap_write_and_wait_range+0x34/0x68) from [<c0188ab0>] (ext4_sync_file+0xb4/0x414)
[41117.940447] [<c0188ab0>] (ext4_sync_file+0xb4/0x414) from [<c0158338>] (vfs_fsync_range+0x34/0x44)
[41117.949451] [<c0158338>] (vfs_fsync_range+0x34/0x44) from [<c0158368>] (vfs_fsync+0x20/0x28)
[41117.957874] [<c0158368>] (vfs_fsync+0x20/0x28) from [<c01586a0>] (sys_fdatasync+0x18/0x34)
[41117.966115] [<c01586a0>] (sys_fdatasync+0x18/0x34) from [<c000e000>] (ret_fast_syscall+0x0/0x30)
[41117.974874] CPU1: stopping
[41117.977529] [<c0013ee8>] (unwind_backtrace+0x0/0xe0) from [<c0012f6c>] (handle_IPI+0x100/0x1cc)
[41117.986258] [<c0012f6c>] (handle_IPI+0x100/0x1cc) from [<c0008670>] (gic_handle_irq+0xa8/0xb4)
[41117.994804] [<c0008670>] (gic_handle_irq+0xa8/0xb4) from [<c000ddbc>] (__irq_usr+0x3c/0x60)
[41118.003166] Exception stack(0xcb443fb0 to 0xcb443ff8)
[41118.008141] 3fa0: 75254dc0 752a4547 000001a4 00000564
[41118.016321] 3fc0: 00002000 00000010 00000612 75252000 bea932dc 75254f00 bea932ed 7522b6e8
[41118.024531] 3fe0: 40224e24 bea93268 40211be7 4021ab9c 80010030 ffffffff
[41118.131322] Rebooting in 5 seconds..
[41123.135045] Going down for restart now
[41123.138005] msm_restart : clear reset flag
Connected via ADB and ran e2fsck, but all appears ok.
Code:
e2fsck -pcfv /dev/block/mmcblk0p15
sh: badblocks: not found
/dev/block/mmcblk0p15: Updating bad block inode.
19845 inodes used (1.13%)
1139 non-contiguous files (5.7%)
19 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 19521/116/1
6040224 blocks used (86.35%)
0 bad blocks
1 large file
17771 regular files
1861 directories
0 character device files
0 block device files
5 fifos
0 links
191 symbolic links (185 fast symbolic links)
8 sockets
--------
19836 files
~ # ?[6ne2fsck -pcfv /dev/block/mmcblk0p17
e2fsck -pcfv /dev/block/mmcblk0p17
sh: badblocks: not found
/dev/block/mmcblk0p17: Updating bad block inode.
161 inodes used (0.30%)
19 non-contiguous files (11.8%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 153
34685 blocks used (16.13%)
0 bad blocks
0 large files
147 regular files
5 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
152 files
1) Did the file system already correct the previous errors, which is why none are detected now?
2) Any other commands/tests that can be run to determine really what is/was wrong?
Click to expand...
Click to collapse
Did you ever figure this out?
Was it transferring from SD to External SD? Or just to Internal?
Sent from my SCH-I535 using XDA Free mobile app
Nope, never figured this out and yes it's occurred more than once.
Seem to recall was transferring large file content from PC to Internal. Don't think it's happened with CM11m10 -- yet... but on the other hand I dont do large file transfers daily.
Still an issue with CM11m11 (or more likely the hardware). system reboot when deleting a ~300 MB file from within MX Player.
Code:
[52140.774902] Buffer I/O error on device mmcblk0p15, logical block 4134812
[52140.781556] end_request: I/O error, dev mmcblk0, sector 43663360
[52140.787874] Buffer I/O error on device mmcblk0p15, logical block 5046272
[52140.794405] end_request: I/O error, dev mmcblk0, sector 44711936
[52140.800387] Buffer I/O error on device mmcblk0p15, logical block 5177344
[52140.807254] Buffer I/O error on device mmcblk0p15, logical block 5242880
[52140.813846] Buffer I/O error on device mmcblk0p15, logical block 5275648
[57664.812106] EXT4-fs error (device mmcblk0p15): ext4_mb_generate_buddy:741: group 158, 2379 clusters in bitmap, 1936 in gd
[57664.822300] Aborting journal on device mmcblk0p15-8.
[57664.833928] Kernel panic - not syncing: EXT4-fs (device mmcblk0p15): panic forced after error
[57664.833928]
[57664.842962] [<c0013928>] (unwind_backtrace+0x0/0xe0) from [<c07abc78>] (panic+0x88/0x1f8)
[57664.851172] [<c07abc78>] (panic+0x88/0x1f8) from [<c01a257c>] (ext4_handle_error+0x8c/0x98)
[57664.859504] [<c01a257c>] (ext4_handle_error+0x8c/0x98) from [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4)
[57664.869393] [<c01a30e8>] (__ext4_grp_locked_error+0xe8/0x1c4) from [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8)
[57664.879892] [<c01b1a60>] (ext4_mb_generate_buddy+0x25c/0x2e8) from [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0)
[57664.890055] [<c01b3a68>] (ext4_mb_init_cache+0x358/0x5f0) from [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4)
[57664.899852] [<c01b4200>] (ext4_mb_load_buddy+0x278/0x2b4) from [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0)
[57664.909436] [<c01b7ea4>] (ext4_free_blocks+0x578/0x9f0) from [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94)
[57664.919385] [<c01ac74c>] (ext4_ext_remove_space+0x6ec/0xe94) from [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0)
[57664.929365] [<c01aed00>] (ext4_ext_truncate+0x100/0x1d0) from [<c0188a24>] (ext4_truncate+0xb4/0x174)
[57664.938582] [<c0188a24>] (ext4_truncate+0xb4/0x174) from [<c018d2c0>] (ext4_evict_inode+0x328/0x490)
[57664.947678] [<c018d2c0>] (ext4_evict_inode+0x328/0x490) from [<c0142c84>] (evict+0x94/0x158)
[57664.956101] [<c0142c84>] (evict+0x94/0x158) from [<c0139f50>] (do_unlinkat+0xe8/0x130)
[57664.963975] [<c0139f50>] (do_unlinkat+0xe8/0x130) from [<c000dec0>] (ret_fast_syscall+0x0/0x30)
[57665.072964] Rebooting in 5 seconds..
[57670.076779] Going down for restart now
[57670.079800] msm_restart : clear reset flag
Official TWRP for Huawei P8 Lite 2017
Working
Code:
[CENTER]* Touchscreen
* Adb
* Backup
* Wipe
* File manager
* MTP
[/CENTER]
Not Working
Code:
[CENTER]You tell me
[/CENTER]
Installation
Code:
[CENTER]* put you phone in fastboot mode and type
"fastboot flash recovery_ramdisk <grab_here_the_img>"
* reboot
[/CENTER]
Download
TWRP official page
Android 11 Unofficial TWRP
DarkJoker360 Sourceforge
Please support my work, it's very important! Thanks
DONATIONS
Regards !
Reserved
Using it on Honor 6X, working fine.
One issue, it doesn't recognise the device while flashing stock rom using hurupdater.
Adoptable storage is not working, show sdcard but empty. (I wouldn't recommend putting something to SD card because it will on 99% overwrite existing stuff).
I am doing with my p8 lite and the result is all the time same error: partition lenght
i have tried fastboot flash recovery file.img and fastboot flash recovery_ramdisk file.img this last says ok, but then when i reboot appear all the same
Is there any solution ????
Thanks.
New TWRP Update !
* Fixed Adb
* Re-enabled OTG Usb wipes
Also I submitted for Official mantainership.
NOTE: P10 Lite won't receive supports since I broke it, just use P8 Lite 2017 stuff.
Hello from now the recovery is official !
Grab latest builds from official website and enjoy
DarkJoker360 said:
Hello from now the recovery is official !
Grab latest builds from official website and enjoy
Click to expand...
Click to collapse
Nice job dude! Keep rocking
(Anyway this twrp won't recongnize my adoptable storage so....)
DunoCZ said:
Nice job dude! Keep rocking
(Anyway this twrp won't recongnize my adoptable storage so....)
Click to expand...
Click to collapse
DMESG output
Code:
[ 395.228881s][pid:249,cpu0,mmcqd/1]mmcqd/1 rw time:7228125 ms,write time:0 ms,read time:7228125 ms
[ 395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 workload < 1%, duty 7228125, period 335947444373, req_cnt=4
[ 395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 Read Throughput=21650 kB/s, size: 151552 bytes, time:7 ms
[ 395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.244384s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[ 395.324401s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[ 395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.704528s][pid:325,cpu5,recovery]hisi_vibrator_enable,value=80
[ 395.784545s][2020:08:10 14:22:16][pid:0,cpu5,in irq]hisi_vibrator_timer_func called
[ 395.925598s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.925628s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.926483s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[ 396.006622s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[ 396.088073s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 396.088104s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 396.088928s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
Mount output when it's working
Code:
/dev/block/dm-0 on /external_sd type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
/dev/block/dm-0 on /sdcard type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
DunoCZ said:
DMESG output
Code:
[ 395.228881s][pid:249,cpu0,mmcqd/1]mmcqd/1 rw time:7228125 ms,write time:0 ms,read time:7228125 ms
[ 395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 workload < 1%, duty 7228125, period 335947444373, req_cnt=4
[ 395.228912s][pid:249,cpu0,mmcqd/1]mmcqd/1 Read Throughput=21650 kB/s, size: 151552 bytes, time:7 ms
[ 395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.243530s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.244201s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.244384s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[ 395.324401s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[ 395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.703674s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.704345s][pid:325,cpu5,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.704528s][pid:325,cpu5,recovery]hisi_vibrator_enable,value=80
[ 395.784545s][2020:08:10 14:22:16][pid:0,cpu5,in irq]hisi_vibrator_timer_func called
[ 395.925598s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.925628s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 395.926300s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 395.926483s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
[ 396.006622s][pid:325,cpu7,in irq]hisi_vibrator_timer_func called
[ 396.088073s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 396.088104s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): bogus number of reserved sectors
[ 396.088745s][pid:325,cpu7,recovery]FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[ 396.088928s][pid:325,cpu7,recovery]hisi_vibrator_enable,value=80
Mount output when it's working
Code:
/dev/block/dm-0 on /external_sd type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
/dev/block/dm-0 on /sdcard type f2fs (rw,seclabel,noatime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,verify_encrypt,active_logs=6)
Click to expand...
Click to collapse
ofc, wrong file system, should be VFAT not F2FS
haky 86 said:
ofc, wrong file system, should be VFAT not F2FS
Click to expand...
Click to collapse
F2FS it's because Adoptable storage, for example discontinued SHRP can mount it and read it without any problem.
Anyone can help me unlock the bootloader first, i dont have the unlock code from huawei because they closed it.
DunoCZ said:
F2FS it's because Adoptable storage, for example discontinued SHRP can mount it and read it without any problem.
Click to expand...
Click to collapse
well I see this : FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
it's mean wrong file system lol
haky 86 said:
well I see this : FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
it's mean wrong file system lol
Click to expand...
Click to collapse
You never used adopted storage right?
Here is output of fdisk.
Code:
:/ $ su
:/ # fdisk -l /dev/block/mmcblk1
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk1: 60456960 sectors, 848M
Logical sector size: 512
Disk identifier (GUID): d8cd974c-9971-4801-aa06-39559b5fa3c1Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 60456926
Number Start (sector) End (sector) Size Name
1 2048 34815 16.0M android_meta
2 34816 60456926 28.8G android_expand
:/ #
And even shrp have in fstab vfat for /external_sd, so it's not sdcard related problem, it's TWRP's partition support problem. And also SHRP mounts /dev/block/dm-0 not /dev/block/mmcblk1p1.
DunoCZ said:
You never used adopted storage right?
Here is output of fdisk.
Code:
:/ $ su
:/ # fdisk -l /dev/block/mmcblk1
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk1: 60456960 sectors, 848M
Logical sector size: 512
Disk identifier (GUID): d8cd974c-9971-4801-aa06-39559b5fa3c1Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 60456926
Number Start (sector) End (sector) Size Name
1 2048 34815 16.0M android_meta
2 34816 60456926 28.8G android_expand
:/ #
And even shrp have in fstab vfat for /external_sd, so it's not sdcard related problem, it's TWRP's partition support problem...
Click to expand...
Click to collapse
exactly it has been disabled even on official berkeley twrp.
haky 86 said:
exactly it has been disabled even on official berkeley twrp.
Click to expand...
Click to collapse
Still doesn't mean it's useless on 16GB device....
DunoCZ said:
Still doesn't mean it's useless on 16GB device....
Click to expand...
Click to collapse
I never use twrp for such of things only for testing roms/gapps, knowing that it's broken at least. but meh it's good to see something official for such platform
haky 86 said:
I never use twrp for such of things only for testing roms/gapps, knowing that it's broken at least. but meh it's good to see something official for such platform
Click to expand...
Click to collapse
Yep that's true, hope someone will brought adoptable back to 3.4.0-0.
papoy1019 said:
Anyone can help me unlock the bootloader first, i dont have the unlock code from huawei because they closed it.
Click to expand...
Click to collapse
Use DC unlocker, you can buy credits via Google Pay... First Downgrade to Android 7 ... Then unlock bootloader
I got a FAILED remote: partition lenght get error, when flashing
Do you know why?
As the thread starter state's...
Android 10 'System-As-Root' was never supposed to be released. Google it.
It never was. Nothing wrong with my fone. boot-debug.img IS the system-as-root, it just isnt a root app.
User-debug will be tied to your account, so dont expect to see them ever again...
So many naysayers saying my fone company got it wrong, that my fone is fecked up...
Na.. System-As-Root = root, as good as it's ever gonna be in the open, provided by boot-debug.
You have root but cant flash a dynamic /system. Magisk KILL's Developer/Feature Flags. With stock boot, feature flags is seen, but shows 'experimental' nothing else. With boot-debug, all feature flags are shown. First thing you'll do is flash magisk. Why does magisk remove this access? In particular for YOU is 'settings-dynamic-system' (used to overlay your gsi - needed to flash gsi). Without these feature flags to set, how will your magisk'd fone boot gsi on system-as-root a-only? It cant. Uninstall magisk... but magisk leaves traces on the fone that prevent earlier versions of magisk being installed, so how can we test earlier versions? That we know worked before?
Magisk'd boot removes the feature flags section from developer menu in Android 10_Q. Why?
This is needed to mount any gsi on an 'a-only' 'system-as-root', by mounting to 'upper' partition, which wipes when re-flashing stock boot.img. Do the work in the upper (like we do in twrp) reflash to the lower after 'sync' will retain your work before reflashing stock boot.img, so no root app needed, but we need one to cut down on how tedious it all is now.. at least they keep you at home... safe lol...
Magisk is only using overlay because it works in pie... in fact, all using magisk are using PIE exploits that dont work in android 10 system as root!! (just a noticed warning )
SystemRW works in PIE, even works in my system-as-root but useless, cause the point, being able to write system while in fone gui, is negated by the fact that system is ro, in about 20 different locations, in about a billion different mount points and well... right down to file sizes for each file in each partition contained within the super.img, but what I dont get is why it works in twrp, yet not in the gui.. (i'm in the directory so cant mount it when using fone, duh...)
As for the other tool to create rw in the super partition, I'll say this:
Pie is dying. Re-write your apps to work with the android 10 super, which is NOT the same as PIE super.img... (this is not a super.img ring any bell's?)
Both rw tool authors stuck on them damn pie's.. I'd swap parted to get the auto resize of space on the fly, I'd give my 10 cents worth, but you know better... if they kill all fones previous to android 10... google win.
They gave us root.
Overlay your own tools!
In a system-as-root booted fone. Feck safety net, I use my nokia 8310 to this day..
And for the naysayers...
D:\0\AdbStation>adb reboot download
D:\0\AdbStation>fastboot flashing unlock_critical
(bootloader) Start unlock flow
OKAY [ 4.196s]
Finished. Total time: 4.196s
D:\0\AdbStation>fastboot --disable-verity --disable-verification flash boot boot
-debug.img
Sending 'boot' (32768 KB) OKAY [ 0.764s]
Writing 'boot' OKAY [ 0.515s]
Finished. Total time: 1.420s
D:\0\AdbStation>fastboot -w
Erasing 'userdata' OKAY [ 0.452s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 6311931 4k blocks and 1581056 inodes
Filesystem UUID: aa3b871c-2496-11ec-9dd6-d71d0c30be37
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (180 KB) OKAY [ 0.016s]
Writing 'userdata' OKAY [ 0.047s]
Erasing 'cache' OKAY [ 0.016s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 110592 4k blocks and 110592 inodes
Filesystem UUID: aa63fe86-2496-11ec-99f6-f719dec4c630
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (68 KB) OKAY [ 0.016s]
Writing 'cache' OKAY [ 0.031s]
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw data not supported.
Finished. Total time: 0.889s
D:\0\AdbStation>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
D:\0\AdbStation>adb disable-verity
Error getting verity state. Try adb root first?
D:\0\AdbStation>adb root
restarting adbd as root
D:\0\AdbStation>adb shell
Armor_X5_Q:/ # whoami
root
Armor_X5_Q:/ # mount -o rw,remount /
'/dev/block/dm-3' is read-only
Armor_X5_Q:/ # mount -o rw,remount /sys
Armor_X5_Q:/ # cd sys
Armor_X5_Q:/sys # ls
block bus dev firmware kernel mtk_rgu
bootinfo class devices fs module power
Armor_X5_Q:/sys # bootinfo
/system/bin/sh: bootinfo: inaccessible or not found
127|Armor_X5_Q:/sys # bootinfo --help
/system/bin/sh: bootinfo: inaccessible or not found
127|Armor_X5_Q:/sys # devices
/system/bin/sh: devices: inaccessible or not found
127|Armor_X5_Q:/sys # cd dev
Armor_X5_Q:/sys/dev # ls
block char
Armor_X5_Q:/sys/dev # cd /
Armor_X5_Q:/ # cd /
Armor_X5_Q:/ # ls
acct d init.environ.rc metadata sbin
apex data init.rc mnt sdcard
bin debug_ramdisk init.usb.configfs.rc odm storage
bugreports default.prop init.usb.rc oem sys
cache dev init.zygote32.rc proc system
charger etc init.zygote64_32.rc product ueventd.rc
config init lost+found product_services vendor
Armor_X5_Q:/ # cd system
Armor_X5_Q:/system # cd bin
Armor_X5_Q:/system/bin # ls
AudioSetParam hwclock printenv
abb hwservicemanager printf
acpi i2cdetect procrank
adbd i2cdump profman
aee i2cget ps
aee_aed i2cset pwd
aee_aed64 iconv racoon
aee_archive id readlink
aee_core_forwarder idmap realpath
aee_dumpstate idmap2 reboot
am idmap2d recovery-persist
apexd ifconfig renice
app_process ime requestsync
app_process32 incident resize.f2fs
app_process64 incident_helper resize2fs
applypatch incidentd restorecon
appops init rm
appwidget inotifyd rmdir
art_apex_boot_integrity input rmmod
ashmemd insmod rss_hwm_reset
atrace install rtt
audioserver install-recovery.sh run-as
auditctl installd runcon
awk ionice schedtest
badblocks iorapd screencap
base64 iorenice screenrecord
basename ip sdcard
batterywarning ip-wrapper-1.0 secdiscard
bc ip6tables secilc
bcc ip6tables-restore sed
blank_screen ip6tables-save sendevent
blkid ip6tables-wrapper-1.0 sensorservice
blockdev iptables seq
bmgr iptables-restore service
boot_logo_updater iptables-save servicemanager
bootstat iptables-wrapper-1.0 setenforce
bootstrap keystore setprop
bpfloader keystore_cli_v2 setsid
bu kill settings
bugreport killall sgdisk
bugreportz kpoc_charger sh
bunzip2 lbs_dbg sha1sum
bzcat lcdc_screen_cap sha224sum
bzip2 ld.mc sha256sum
cal librank sha384sum
cameraserver linker sha512sum
cat linker64 showmap
charger linker_asan simpleperf
chcon linker_asan64 simpleperf_app_runner
chgrp lmkd sleep
chmod ln sload_f2fs
chown load_policy sm
chroot locksettings sort
chrt log split
cksum logcat ss
clatd logd sspm_log_writer
clear loghidlsysservice st_factorytests
cmd logname start
cmp logwrapper stat
comm losetup statsd
connsyslogger lpdump stop
content lpdumpd storaged
cp ls strings
cpio lshal stty
crash_dump32 lsmod surfaceflinger
crash_dump64 lsof svc
cut lspci swapoff
dalvikvm lsusb swapon
dalvikvm32 make_f2fs sync
dalvikvm64 md5sum sysctl
date mdlogger tac
dd mdnsd tail
debuggerd media tar
defrag.f2fs mediadrmserver taskset
device_config mediaextractor tc
devmem mediametrics tc-wrapper-1.0
dex2oat mediaserver tcpdump
dexdiag met-cmd tee
dexdump met_log_d telecom
dexlist microcom terservice
dexoptanalyzer migrate_legacy_obb_data.sh thermald
df mini-keyctl time
diff mkdir timeout
dirname mke2fs tombstoned
dmctl mkfifo toolbox
dmesg mkfs.ext2 top
dnsmasq mkfs.ext3 touch
dos2unix mkfs.ext4 toybox
dpm mknod tr
drmserver mkswap traced
du mktemp traced_probes
dumpstate mobile_log_d trigger_perfetto
dumpsys modemdbfilter_client true
e2fsck modinfo truncate
e2fsdroid modprobe tty
echo monkey tune2fs
egrep more tzdatacheck
emdlogger1 mount ueventd
emdlogger2 mountpoint uiautomator
emdlogger3 move_widevine_data.sh ulimit
emdlogger5 mtkbootanimation umount
env mtpd uname
expand mv uncrypt
expr nc uniq
fallocate ndc unix2dos
false ndc-wrapper-1.0 unlink
fgrep netcat unshare
file netd unzip
find netdiag uptime
flags_health_check netstat usbd
flock netutils-wrapper-1.0 usleep
fmt newfs_msdos uudecode
free nfcstackp uuencode
fsck.f2fs nice uuidgen
fsck_msdos nl vdc
fsverity_init nohup viewcompiler
fsync notify_traceur.override.sh vintf
gatekeeperd notify_traceur.sh vmstat
getconf nproc vold
getenforce nsenter vold_prepare_subdirs
getevent oatdump vr
getprop od vtservice
gpuservice oem-iptables-init.sh wait_for_keymaster
grep paste watch
groups patch watchdogd
gsi_tool perfetto wc
gsid pgrep which
gunzip pidof whoami
gzip ping wificond
head ping6 wm
heapprofd pkill xargs
hid pm xxd
hostname pmap yes
hw pppd zcat
Armor_X5_Q:/system/bin # getenforce
Enforcing
Armor_X5_Q:/system/bin # setenforce 0
Armor_X5_Q:/system/bin # get enforce
/system/bin/sh: get: inaccessible or not found
127|Armor_X5_Q:/system/bin # getenforce
Permissive
Armor_X5_Q:/system/bin # root mofo's, System-As-Root! boot-debug rocks!
> ^C
130|Armor_X5_Q:/system/bin # Who needs su
/system/bin/sh: Who: inaccessible or not found
127|Armor_X5_Q:/system/bin # whoami
root
Armor_X5_Q:/system/bin #