Related
Hello. At first I want to ask if any of you working on Gingerbread experienced "Force Close" loop on restart for many applications (for repair required format /data backup or restore via CWM)?
I spent a lot of time to get to the source of the problem, because even though the system version of JB's okay, it's GB is more stable and does not eat much RAM, moreover is much better for multitasking in the current situation.
Get to the point. The problem appears to be that from time to time, as in any filesystem, in the user partition (/ data) errors may occur that normally are repaired at boot time by e2fsck program. Moreover, in the case of my own and yet another piece of Samsung I8160 e2fsck is unable to complete repairs due to an error related to the library supports file systems.
When I connect ADB in recovery mode, umount /data and issue the command "e2fsck -y -f /dev/block/mmcblk0p5" the mass of errors are discovered, and repairing starts, but of course does not end well:
Code:
"FILESYSTEM WAS MODIFIED,
invalid argument passed to ext2 library while rewriting block and inode bitmaps "
...which tells that filesystem was modified, but the wrong argument was passed to the filesystem library and the correct structure not been written completely, resulting in an even greater massacre on the partition. It is not difficult to guess that the system will not boot normally (/data mounted in read only mode), and applications will start the "Force close" loop .
The story is not only on my phone, but also in other arts. After formatting it for a few weeks until you see the error and restart. After restoring a backup via CWM has usually only until the next reboot.
Has anyone experienced this? Is anyone able to solve this problem?
I tried stock ROM and kernel, reflashing, substitution of e2fsck binaries and libext2fs libraries. Chip does not have bad blocks, checked by dd command and calculated CRCs.
Please don't reply "do full wipe," not considering myself an Android noob, I want to solve the problem.
Have you ever tried to do filesystem check on Gingerbread and did it work for you? "e2fsck -y -f /dev/block/mmcblk0p5" ?
Can you restart the phone without problem?
Can you try if it works now?
Part of the log with dmesg at boot:
Code:
<4> [10.306152] EXT4-fs warning (device mmcblk0p5): ext4_clear_journal_err: Filesystem error recorded from previous mount: IO failure
<4> [10.306213] EXT4-fs warning (device mmcblk0p5): ext4_clear_journal_err: Marking fs in need of filesystem check.
<4> [10.331756] EXT4-fs (mmcblk0p5): warning: mounting fs with errors, running e2fsck is recommended
You can try
1.Boot in recovery mode(NEED CWM-Based Recovery).
2.Select "mounts and storage".
3.Select"mount /data".
4.Reboot.
But It's not really solve the problem because you need do these step when you boot your phone everytime, but this is the only solution(as I know) until who have better solution......
Sorry for my poor English......OTL
This is not possible...
Sent from my GT-I8160 using xda app-developers app
Maybe reflash your fw with odin you can download your fw at sammobile
I tried this, flashing JB and GB back. It seems that CWM 5 formatting procedure is buggy. When I format thru my own binary mke2fs this error is gone. So...
Sent from my GT-I8160 using xda app-developers app
So last night i finally decided to install JetiX20. Installation ran smoothly until reboot.
hmm ... stuck on Samsung galaxy note 2 logo for over 45 mins.
Reboot into clockworkMod recovery v6.0.4.3
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log
So.. i tried to wipe data/factory reset and cache partition....
Code:
--wiping data--
formatting /data...
error mounting /data!
skipping format...
formatting /cache...
E: format_volume:make_extf4fs failed on /dev/block/mmcblk0p12
formatting /sd-ext...
formatting /sdcard/.android_secure...
E: unknown volume "/sdcard/.android_secure"
data wipe complete
So, now i move to adb:
[email protected]:~$ adb devices
List of devices attached
42f7410e7bc79f3f recovery
Code:
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 67.1 GB, 67108864000 bytes
4 heads, 16 sectors/track, 2048000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 2048000 65535992 83 Linux
~ #
Code:
# mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
Some how i manage to corrupt my mobile's partition?
I tried Odin, Heimdall, fastboot and adb as per recommended on the forum.
Is there anything else i could try?
Thanks for any advices.
You should re-flash the stock ROM of Samsung Galaxy Note 2 through ODIN.
I did, still getting the very same error.
May need to fix partitions by flashing a PIT file...
Zen Arcade has a pit thread in the development section...
Read EVERYTHING before flashing a PIT....g
gregsarg said:
May need to fix partitions by flashing a PIT file...
Zen Arcade has a pit thread in the development section...
Read EVERYTHING before flashing a PIT....g
Click to expand...
Click to collapse
I sure will read up on it. thanks
http://forum.xda-developers.com/showthread.php?t=2609871
There they are...
Again....I cannot stress enough the importance of reading every word Zen posted on the subject...
And remember....the PIT may not be your issue....so evaluate carefully...
I bid you good luck....g
Hello again
So sadly I'm still having the same issue, looks like everything install/runs ok but at reboot the phone still at bootloop when I try to pull the logs from the device all I get is can't mount mmcblk0p12.
Are you getting a "cannot mount sd card " in that error message ??
That error would indicate a failed partition on the emmc..
This is not looking good.....g
No just can't mount/open /cache/recovery.
But on wipe data/factory reset one of the lines say "E: unknown volume "/sdcard/.android_secure".
I can't find anything else that will give me that error.
Okay ...please post the link to the stock rom you are trying to flash....and also tell us what bootloader version you have..g
gregsarg said:
Okay ...please post the link to the stock rom you are trying to flash....and also tell us what bootloader version you have..g
Click to expand...
Click to collapse
Hi greg, this is the link http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189 and i am pretty sure NE5.
at first i though it was the actual external sd card, but then after some more careful reading, mmcblk0p12 is a partition of my internal storage correct?
Yep....emmc
And if those permanent partitions are whacked ....then it's bye bye phone....
No PIT will fix the emmc...it would be a chip replacement or new phone..
The emmc is essentially the boot sector of the device...g
gregsarg said:
Yep....emmc
And if those permanent partitions are whacked ....then it's bye bye phone....
No PIT will fix the emmc...it would be a chip replacement or new phone..
The emmc is essentially the boot sector of the device...g
Click to expand...
Click to collapse
Well thats a shame is there another way to verify the status of the emmc or this is pretty much it?is just strange how i try to install the JediX20 rom before and installed ok still boot, i would figure it will give errors installing and hang.
Oh well... ill try a few more times before i decide to move onto hardware
thanks greg.
Hello again everyone
So doing some more reading last night about my issue and found this:
****@****:~$ adb shell cat /sys/block/mmcblk0/device/manfid
0x000000
Will this confirm the issue to be with the chip?
thanks. \m/
One last attempt here...
Format your external SD CARD to FAT32 on a PC....then reload it into the device and reflash your rom....g
Omg Greg I was just about to do that lmao. Thanks working on it
While this is formatting I have a question. I just noticed that I can only see mmcblk0 when the external card is in. Why would that be?
Thanks.
I hope this doesn't come up twice. External SD formatted to fat32... Try installing ucune5.. Odin said it pass but still stuck on logo after reboot
Chamo709 said:
While this is formatting I have a question. I just noticed that I can only see mmcblk0 when the external card is in. Why would that be?
Thanks.
Click to expand...
Click to collapse
Because your device is trying to mount the storage block....and the mmcblk0 is the address...
I'm hoping it's an external error and not internal...because the emmc will give similar errors....g
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Chamo709 said:
I hope this doesn't come up twice. External SD formatted to fat32... Try installing ucune5.. Odin said it pass but still stuck on logo after reboot
Click to expand...
Click to collapse
Wipe data....factory reset in recovery...g
Ok... So no bueno still getting the same exact error ... What a shame really. I guess next step is getting a new board?
The problem started when I flashed the philz touch recovery, and used the "Clear for new rom" in the wipe menu. I then proceeded to try to install two different roms unsuccessfully, as well as trying two different recoveries, and they always return the same error:
Code:
Mount:failed to mount /dev/block/mmcblk0p6
This is a strange error, since using the df command returns the following results:
Code:
tmpfs 683452 160 683292 0% /dev
tmpfs 683452 652 682800 0% /tmp
/dev/block/mmcblk0p42
273948 4408 269540 2% /cache
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /data
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /sdcard
/dev/block/mmcblk1p1 15540224 4846896 10693328 31% /external_sd
If I am understanding this correctly, the ROM should be installed on mmcblk0p44 since it is the internal drive and always has been, not mmcblk0p6, and I don't see why it needs access to mmcblk0p6.
I tried a method of repairing the filesystem using a mkfs.ext4 file, found in a blog.
I then used the following commands after putting the mkfs file in /tmp:
Code:
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
After this, I managed to get a ROM to report installing successfully, but when I booted the phone, it got stuck in a boot loop which was better than the immediate booting to recovery, and am now getting the same error again, and I can't boot the phone at all, it just goes into recovery.
I have tried to restore from previous backups, with no luck.
Can anyone help?
jacobjake683 said:
The problem started when I flashed the philz touch recovery, and used the "Clear for new rom" in the wipe menu. I then proceeded to try to install two different roms unsuccessfully, as well as trying two different recoveries, and they always return the same error:
Code:
Mount:failed to mount /dev/block/mmcblk0p6
This is a strange error, since using the df command returns the following results:
Code:
tmpfs 683452 160 683292 0% /dev
tmpfs 683452 652 682800 0% /tmp
/dev/block/mmcblk0p42
273948 4408 269540 2% /cache
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /data
/dev/block/mmcblk0p44
4506568 707644 3798924 16% /sdcard
/dev/block/mmcblk1p1 15540224 4846896 10693328 31% /external_sd
If I am understanding this correctly, the ROM should be installed on mmcblk0p44 since it is the internal drive and always has been, not mmcblk0p6, and I don't see why it needs access to mmcblk0p6.
I tried a method of repairing the filesystem using a mkfs.ext4 file, found in a blog.
I then used the following commands after putting the mkfs file in /tmp:
Code:
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
After this, I managed to get a ROM to report installing successfully, but when I booted the phone, it got stuck in a boot loop which was better than the immediate booting to recovery, and am now getting the same error again, and I can't boot the phone at all, it just goes into recovery.
I have tried to restore from previous backups, with no luck.
Can anyone help?
Click to expand...
Click to collapse
Could you please provide me with the mkfs.ext4 binary? The link in that blog has expired.
I'm also having problems with my partitions and can't flash anything. I can't relock the bootloader either.
If you have stock recovery installed on your phone, you should relock the bootloader. Then run the ruu. That should fix the problem.
Thanks in advance.
uhm said:
Could you please provide me with the mkfs.ext4 binary? The link in that blog has expired.
I'm also having problems with my partitions and can't flash anything. I can't relock the bootloader either.
If you have stock recovery installed on your phone, you should relock the bootloader. Then run the ruu. That should fix the problem.
Thanks in advance.
Click to expand...
Click to collapse
Sorry, but I do not have the file anymore due to the fact that I have gone through various hard drive formats and I don't seem to have it on the HTC anymore.
No problem. Thanks for your reply.
HI
I have a HTC one M9 hima. Lastly, it has suddenly rebooted. I have not use it.
But it have not stuck in boot. It has boot to the withe Logo screen then go off and boot again, again and again.
If i push power + vol down, the Black screen with e HTC logo comes and the loop go faster.
The only way to come to the bootloader ist to push power + vol down + vol up.
From there i come to the recovery or download Mode. I have twrp installed.
In twrp i discovered that some Partitions can not mount:
mount: mounting /dev/block/mmcblk0p65 on /cache failed: Invalid argument
mount: mounting /dev/block/mmcblk0p67 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p36 on /devlog failed: Invalid argument
mount: mounting /dev/block/mmcblk0p50 on /carrier failed: Invalid argument
mount: mounting /dev/block/mmcblk0p69 on /cota failed: Invalid argument
mount: mounting /dev/block/mmcblk0p68 on /preload failed: Invalid argument
mount: mounting /usb_otg on vfat failed: No such file or directory
mount: mounting /sd-ext on ext4 failed: No such file or directory
I tried:
- wipe Data --> mount error
- formate Data --> mount error
- flash new rom --> mount error
- install new Firmware --> requiret new start then loop
- mount manuel over adb --> invalied argument
- e2fsck /dev/block/mmcblk0p* --> bad magic number in super-block
- flash rom with fastboot --> invalid zip file
- new recovery --> after flash and boot to recover: exist old recovery <-- with dd, twrp and with fastboot
- twrp repair or change File System --> mount error
- twrp resize File System --> end with ERROR: 8
- twrp Change File System --> ERROR: 8
pls help me!!
sorry for my bad English
anyone here who knows the solution for above errors please? coz it did happen to me also. Thanks XDA for your help.
my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".
Radianer said:
my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".
Click to expand...
Click to collapse
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"
kmx0101 said:
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"
Click to expand...
Click to collapse
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.
shivasrage said:
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.
Click to expand...
Click to collapse
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?
kmx0101 said:
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?
Click to expand...
Click to collapse
https://forum.xda-developers.com/one-m9/help/download-modepossible-fix-t3555678
Dear to all, I have a samsung galaxy s9 g9600/ds (snapdragon) with last official firmware android 10 and rooted with magisk and with custom kernel of klabit87. Even if the device is rooted, system partition it's read-only (seems that is related to Android 10) but if I try to install and execute systemrw ( https://www.systemrw.com/ ), I 've message "Fatal error! No super partition detected". But if I run "cat /vendor/etc/*fstab*" I'll get the following outputs
Code:
:/ # cat /vendor/etc/*fstab*
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/system /system ext4 ro,errors=panic wait
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,encryptable=footer,quota,reservedsize=128M
#/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1,discard wait
/dev/block/bootdevice/by-name/persist /mnt/vendor/persistext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/bootdevice/by-name/apnhlos /vendor/firmware_mnt vfat ro,context=u:object_r:firmware_file:s0,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337 wait
/dev/block/bootdevice/by-name/modem /vendor/firmware-modem vfat ro,context=u:object_r:firmware_file:s0,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337 wait
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/efs /mnt/vendor/efs extnoatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/bootdevice/by-name/dqmdbg /mnt/vendor/dqmdbg ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/bootdevice/by-name/carrier /carrier extnoatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic defaults,nofail,check
#
# Need to have this entry in here even though the mount point itself is no longer needed.
# The update_engine code looks for this entry in order to determine the boot device address
# and fails if it does not find it.
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
# /dev/block/bootdevice/by-name/nad_refer /nad_refer ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,formattable,factoryuse
# VOLD :: fstab.qcom
/dev/block/bootdevice/by-name/hidden /preload extnoatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic voldmanaged=preload:auto,check
/devices/platform/soc/8804000.sdhci/mmc_host/mmc* auto vfat defaults voldmanaged=sdcard:auto
/devices/platform/soc/a600000.ssusb/a600000.dwc3/xhci-hcd.0.auto/usb* auto auto defaults voldmanaged=usb:auto
# TODO: Needs to be checked by memory part
# /dev/block/zram0 none swap defaults zramsize=1073741824
:/ #
so system partition is read-only and I can't use app debloat or Link2SD app. Somebody have found a solution to this problem ?
p.s.: the same utility throw error message about dm-verity and dm-verification: "ERROR: Data from 'vbmeta' does not look like a vbmeta header" ... so I can know if verity and verification are disabled ?
In the install of the firmware and root I have made the followings steps:
in download mode: Odin install Android 10 stock firmware G9600ZHS9FVA4 from here https://samfw.com/firmware/SM-G9600/TGY
check and disable oembootloader
Reboot
in downlaod mode Odin install TWRP
Reboot into TWRP (recovery mode)
Install multidisabler-samsung-2.2_klabit
Install forceencrypt_remover_Q
Format data partition
reboot to recovery
Install g9600_klabit_q_v6.3
Install Magisk-v26.1
reboot to system
there is something that I have wrong?