Related
I'm running 2.03 and my browser started crashing so I did a reboot. Now I keep looping between the ViewSonic screen and gtablet screen. I've tried several restores through ClockWorkMod and it still doesn't work. I thought I could try to do the upgrade.zip off of a sd card but how do I get the system to recongize it and not the internal memory?
Stupid question : Have you done a user data wipe/system data wipe from CW?
If cw is not seeing the internal sd and the updates located on the internal sd are not working with full users data wipe, then a nvflash push from pc will have to be done to vanilla tnt, then do an update to get clockwork back, then tnt lite 2.0 with clockwork?
You might need to do a re-partition of your SD card (or rather, of the internal SD card memory) from clockwork mod. That has gotten other people out of a boot loop. This most likely has something to do with partitions getting corrupted, which seems to occasionally happen when you are flashing ROMs. You might want to search the forum for SD card partition and boot loop, I know several people have had the same issue.
There is also the APX mode as a backup mechanism if that fails. Search forum for that one too - it's basically a backup to the normal CW or other recovery that lets you flash a fresh ROM even if all else has failed. But I don't think you need to go there if your recovery is still working fine.
arrow21 said:
Stupid question : Have you done a user data wipe/system data wipe from CW?
Click to expand...
Click to collapse
Yes, tried nearly everything I can in Clock and nothing changes the loop. I thought in the worst case you could always find a way to get the system back to it's original state but no luck so far.
another option is this
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
I have never done the partiton of my sdcard... so I guess that might work also.
arrow21 said:
another option is this
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
I have never done the partition of my sdcard... so I guess that might work also.
Click to expand...
Click to collapse
HELP!!! I think my data partition just go hosed, all I tried to do was restore a backup since I was getting a lot of FC, all trying to access my data folder according to logcat....what do I do, will redoing the partition of my sdcard fix the errors below. How do I repartition and what settings do I use? I was trying to do the restore since I too got stuck in reboot loop. I have the logcat ouput if any dev is interested in seeing it.
Trying to restore backup in clockworkmod I get this:
ClockworkMod Recovery v2.5.1.1-bekit-0.8
Checking MD5 sums...
Erasing boot before restore
Restoring system...
Restoring data...
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Error mounting /data/!
Skipping format...
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Can't mount /data/!
rcgabriel said:
You might need to do a re-partition of your SD card (or rather, of the internal SD card memory) from clockwork mod. That has gotten other people out of a boot loop. This most likely has something to do with partitions getting corrupted, which seems to occasionally happen when you are flashing ROMs. You might want to search the forum for SD card partition and boot loop, I know several people have had the same issue.
There is also the APX mode as a backup mechanism if that fails. Search forum for that one too - it's basically a backup to the normal CW or other recovery that lets you flash a fresh ROM even if all else has failed. But I don't think you need to go there if your recovery is still working fine.
Click to expand...
Click to collapse
rc, thanks for the help. Honestly partitioning is something I've never fully understood so I wasn't even sure how to do that. I went into CW and then advanced settings and chose to partition the sd card. The only problem is I didn't know what settings to use so I just used the first ones to pop up. After doing that I did a reboot and things worked fine.
I was going to go back and try a CW restore and see if I could get everything back but now it can't find the restore file. I assume that happened when I tried to reformat the card.
scmobileman said:
I was going to go back and try a CW restore and see if I could get everything back but now it can't find the restore file. I assume that happened when I tried to reformat the card.
Click to expand...
Click to collapse
The restore files were are stored on the internal sdcard, so when you formatted, you wiped them out...is my guess. You could have used adb to save them off before hand and then put them back after format.
For the benefit of others, here is how I fixed this:
-Boot into clockworkmod
-Used adb to copy off all sdcard files (including backup files to use in restore)
-Use CW to partition the sdcard (2048mb ext, 256mb swap)
-Tried to copy backup files back...see issues below
-Restore backup files
-Back to working tab
Two issues I had, one is that for the life of me, I could not get the backup files back onto the sdcard. adb must not like windows because it had issues copying the files back unless you copy them to the root of the device. Even then I tried to shell into the device and move the files to the sdcard, but then CW would not see the files, when I reboot the device and try again, the files were gone. I tried to just copy the update.zip file, again CW didn't see the file, and reboot caused it to disappear as well. I managed to mount the tab in USB mode and copy the files to the sdcard using windows. Afterwards CW didn't see the files either.
I figured the system image was good, rebooted to start from scratch, and the setup program ran. I tried to tap the screen bu nothing would happen. Issue two from the log, is that it the setup wizard ignores touch evens if there is no phone interface...reboot again, back into CW, and this time it saw my backup files, restore, then good to go.
My next step would have been to delete the setupwizard apk, wipe data, boot into android, copy backup files, reboot, restore, but not needed finally.
Have other people run into the above issue where you copy files to the sdcard uin adb while within CW, and the files don't stick. How do you get around this?
raydog.. thank you thank you thank you
thanks
raydog, your post helped greatly. thank you.
Life in LA said:
raydog, your post helped greatly. thank you.
Click to expand...
Click to collapse
Thanks, sad to say I am back in a reboot loop, so I have to do this all over again...uggg
I have shut my tablet off by holding down the power button and bypassing the shutdown screen, wonder if this corrupted the data partition.
I had the reboot problem when trying to load 2.0.0
My fix: Loaded original vanilla via sdcard (took two load tries) then retried 2.0.0 via sdcard and it worked.
please help to make my data read write
raydog153 said:
Have other people run into the above issue where you copy files to the sdcard uin adb while within CW, and the files don't stick. How do you get around this?
Click to expand...
Click to collapse
1|[email protected]:/sbin # su
[email protected]:/sbin # is
sh: is: not found
127|[email protected]:/sbin # cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/sbin # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/sbin # fs
sh: fs: not found
127|[email protected]:/sbin # df
Filesystem Size Used Free Blksize
/dev 407.7M 32.0K 407.6M 4096
/sys/fs/cgroup 407.7M 12.0K 407.7M 4096
/mnt/asec 407.7M 0.0K 407.7M 4096
/mnt/obb 407.7M 0.0K 407.7M 4096
/system 1.3G 443.6M 934.3M 4096
/efs 19.7M 8.1M 11.5M 4096
/data 11.9G 5.5G 6.3G 4096
/cache 689.0M 129.8M 559.1M 4096
/mnt/shell/emulated 11.9G 5.5G 6.3G 4096
[email protected]:/sbin # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 12640239 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
[email protected]:/sbin # format 259
sh: format: not found
127|[email protected]:/sbin # del
sh: del: not found
127|[email protected]:/sbin # mount /efs rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,remount /efs
[email protected]:/sbin # mount -o rw,remount /dev
[email protected]:/sbin # mount -o rw,remount /sys/fs/cgroup
[email protected]:/sbin # mount -o rw,remount /mnt/asec
[email protected]:/sbin # mount -o rw,remount /mnt/obb
[email protected]:/sbin # mount -o rw,remount /system
[email protected]:/sbin # mount -o rw,remount /syste
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,remount /efs
[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /cache
[email protected]:/sbin # mount -o rw,remount /mnt/shell/emulated
[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw, del /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,del /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # help
sh: help: not found
127|[email protected]:/sbin # Read-only file system
sh: Read-only: not found
127|[email protected]:/sbin # rw
sh: rw: not found
127|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin #
this is my partition table and errors for p3100.
please help me how to make it read write.
please mailm e the steps.
[email protected]
thanks in advance
Hi everybody,
I'm in deep troubles with my nexus (maguro).
Yesterday, it started to reboot after showing for about 5-10 seconds the lock screen.
the phone is rooted, Iand the last rom (cyanogenmod) was running stable in the last 6 months.
twrp 2.8.0.1 was installed, so I Rebooted to fastboot to flash the 2.8.6.0.
And then the weird part begins:
it's like every partition is read only, but from the mount command it doesn't look like it.
flashing the new recovery is a success, but after reboot the 2.8.0.1 is still there.
factory reset successful, and everything is like before.
wiping sdcard, nothing happens.
if I try to create a backup in twrp, it fails after 20 seconds or so. (I've copied everything to the pc using the pull command in adb).
Try to fix or to change the partitions filesystem in twrp doesn't change anything.
I tried also to change the file system in parted, through the adb shell,this happens:
Code:
~ # ←[6nparted /dev/block/mmcblk0p12 mkfs ext2
parted /dev/block/mmcblk0p12 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
parted: invalid token: ext2
Yes/No? yes
yes
yes
Partition number? 1
1
1
File system type? [ext2]?
Error: File system was not cleanly unmounted! You should run e2fsck. Modifying
an unclean file system could cause severe corruption.
Ignore/Cancel? i
i
i
Error: File system has an incompatible feature enabled. Compatible features are
has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or
debugfs to remove features.
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
...
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
...
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
and of course nothing changes.
so, I have access to adb in recovery and to fastboot, there is a way to wipe completely the filesystem and start from scratch, or load a different kernel, that would help?
If I send with adb push a new rom to the sdcard, twrp fails and at the next reboot the files disappear.
this is my mount result:
Code:
~ # ←[6nmount
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 /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p11 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barri
er=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,seclabel,relatime,user_xattr,barrie
r=1,data=writeback)
/dev/block/mmcblk0p12 on /sdcard type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=writeback)
/dev/block/mmcblk0p10 on /system type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=ordered)
and remounting in rw the partitions has no effect.
Even the parted, e2fsck, etc files disappear from /sbin after each reboot.
thank you
edit:
Having a second nexus, I could take a look at the partitions, and the difference seems to be the data=writeback options.
I'm looking for a procedure to make them "ordered" as the other phone.
edit2:
Code:
/tmp # ←[6ntune2fs -l /dev/block/mmcblk0p12 | grep features
tune2fs -l /dev/block/mmcblk0p12 | grep features
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Filesystem features: has_journal ext_attr resize_inode filetype needs_recov
ery extent sparse_super large_file
/tmp # ←[6ne2fsck -f /dev/block/mmcblk0p12
e2fsck -f /dev/block/mmcblk0p12
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p12: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
y
yes
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p12
/dev/block/mmcblk0p12: ********** WARNING: Filesystem still has errors *********
*
/tmp #
/tmp # ←[6ntune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs 1.42.9 (28-Dec-2013)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
Stuck here at the moment, cannot set superblock flags..
edit3:
Tested every possible superblock position, no luck.
I'm starting to think that the internal memory could be dead.
I forgot to say that I've tried also the fastboot -w command, it works a lot (about 270 seconds) but no effect.
ghirux said:
Hi everybody,
I'm in deep troubles with my nexus (maguro).
Yesterday, it started to reboot after showing for about 5-10 seconds the lock screen.
the phone is rooted, Iand the last rom (cyanogenmod) was running stable in the last 6 months.
twrp 2.8.0.1 was installed, so I Rebooted to fastboot to flash the 2.8.6.0.
And then the weird part begins:
it's like every partition is read only, but from the mount command it doesn't look like it.
flashing the new recovery is a success, but after reboot the 2.8.0.1 is still there.
factory reset successful, and everything is like before.
wiping sdcard, nothing happens.
if I try to create a backup in twrp, it fails after 20 seconds or so. (I've copied everything to the pc using the pull command in adb).
Try to fix or to change the partitions filesystem in twrp doesn't change anything.
I tried also to change the file system in parted, through the adb shell,this happens:
Code:
~ # ←[6nparted /dev/block/mmcblk0p12 mkfs ext2
parted /dev/block/mmcblk0p12 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
parted: invalid token: ext2
Yes/No? yes
yes
yes
Partition number? 1
1
1
File system type? [ext2]?
Error: File system was not cleanly unmounted! You should run e2fsck. Modifying
an unclean file system could cause severe corruption.
Ignore/Cancel? i
i
i
Error: File system has an incompatible feature enabled. Compatible features are
has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or
debugfs to remove features.
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
...
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
...
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
and of course nothing changes.
so, I have access to adb in recovery and to fastboot, there is a way to wipe completely the filesystem and start from scratch, or load a different kernel, that would help?
If I send with adb push a new rom to the sdcard, twrp fails and at the next reboot the files disappear.
this is my mount result:
Code:
~ # ←[6nmount
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 /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p11 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barri
er=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,seclabel,relatime,user_xattr,barrie
r=1,data=writeback)
/dev/block/mmcblk0p12 on /sdcard type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=writeback)
/dev/block/mmcblk0p10 on /system type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=ordered)
and remounting in rw the partitions has no effect.
Even the parted, e2fsck, etc files disappear from /sbin after each reboot.
thank you
edit:
Having a second nexus, I could take a look at the partitions, and the difference seems to be the data=writeback options.
I'm looking for a procedure to make them "ordered" as the other phone.
edit2:
Code:
/tmp # ←[6ntune2fs -l /dev/block/mmcblk0p12 | grep features
tune2fs -l /dev/block/mmcblk0p12 | grep features
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Filesystem features: has_journal ext_attr resize_inode filetype needs_recov
ery extent sparse_super large_file
/tmp # ←[6ne2fsck -f /dev/block/mmcblk0p12
e2fsck -f /dev/block/mmcblk0p12
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p12: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
y
yes
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p12
/dev/block/mmcblk0p12: ********** WARNING: Filesystem still has errors *********
*
/tmp #
/tmp # ←[6ntune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs 1.42.9 (28-Dec-2013)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
Stuck here at the moment, cannot set superblock flags..
edit3:
Tested every possible superblock position, no luck.
I'm starting to think that the internal memory could be dead.
I forgot to say that I've tried also the fastboot -w command, it works a lot (about 270 seconds) but no effect.
Click to expand...
Click to collapse
have you tried repairing system via twrp?
toolhas4degrees said:
have you tried repairing system via twrp?
Click to expand...
Click to collapse
yes, I forgot to say it but yes. On /data and /sdcard the procedure fails, i think for the same reason that makes e2fsck fail too.
I'm almost sure that the memory is gone, I need to find a tool to test its functionality.
Whatever I write on there it gets deleted at the next reboot, I don't think it's normal.
thank you.
Hello,
I am flashing roms since nearly two years and I got my first big problem 2 days ago.
My GT-i9100 (DBT Germany) was running stable under cm-12.1-20150611-UNOFFICIAL-i9100.zip brought by Lysergic Acid.
When I tried to log on WLAN on Tuesday morning, my rom crashed with a few percent of energy remaining. I charged my battery and started the phone again. I had a message "No Service" and a barred circle. Pin Code was being asked, as well as my lock screen Pin Code.
I thought it was a mobile network operator issue, and that it would be temporary. Didn't care about it, I was able to log in my WLAN network. Then I saw an update (06/17) on xda, that I downloaded and flashed following the installation instructions. I noticed still the "No service" message and the circle barred. I looked at my telephone settings an saw Unknown Baseband, No Signal, Unknown Imei. When I called *#6#, there was a popup with only the Text IMEI no number.
Finally I did sthg really stupid (I didn't google Unknown Baseband Unknown Imei at this time), because I thought wrongly that the issue is a rom, modem or csc issue. Then I decided to flash back to a stable jelly bean version.
Thus, I had to flash the partition with Stock i9100 pit, because I was using a preload modified area partition before.
Then I made my great mistake, that's what I think now, I think I corrupted my /efs folder. I installed a stock firmware from sammobile on my SII (still no service, unknown baseband), then rooted the phone again, and installed
ASNET MIUI v5 (4.8.10) everything is working except this my mobile network unknown baseband, unknown Imei, etc
I tried to look on my external harddrive, if I had any backups from my phone, did not have any /efs backup. :crying:
With root explorer I am able to to see the /efs folder no file is missing I think, but it is certainly corrupt. I am joining a .tar file of this folder here. https mega.nz/#!4IZijDTK!2eZ1lhC01bTEcbzwP7OVe8tePiIm5GNQ_dwpZRZHF0k
~ $ mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=writeback)
/dev/block/mmcblk0p12 on /preload type ext4 (ro,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard)
~ $ su
[email protected]:/ # #
[email protected]:/ #
[email protected]:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 422816 76 422740 0% /dev
tmpfs 422816 0 422816 0% /mnt/asec
tmpfs 422816 0 422816 0% /mnt/obb
/dev/block/mmcblk0p9 516040 453384 62656 88% /system
/dev/block/mmcblk0p7 100784 4160 96624 4% /cache
/dev/block/mmcblk0p1 20144 10492 9652 52% /efs
/dev/block/mmcblk0p12
516040 77688 438352 15% /preload
/dev/block/mmcblk0p10
2064208 306208 1758000 15% /data
df: /mnt/.lfs: Function not implemented
/dev/block/vold/259:3
12063840 445792 11618048 4% /storage/sdcard0
1|[email protected]:/ # mount /efs
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /data
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /preload
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /cache
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /system
mount: can't read '/etc/fstab': No such file or directory
I still have the IMEi on the back of my phone.
Is there a way to fix this or is it impossible?
I was able to install lollipop on my phone. But I couldn't get root. I lost some information. So I went back to my backup 4.3 within TWRP and that's when it all went to ****. HWuserdata can't be mounted and sometimes internal_sd can't be mounted either.
What I can do:
-Install new roms
-Install backups [restore them]
-Access to adb
-Can push out img through through adb/fastboot
What I can't do:
-with all of the above, the internal sd doesn't mount in ANY of the roms [both 4.3 and 5.1]
-Can't remove /hwuserdata in TWRP
-Can't remove /internal_sd in TWRP [Error message: E: Unable to mount '/internal_sd']
More Error Messages:
E: Block device not present, cannot wipe internal storage.
E: Unknown MTP message type: 1
E: Unable to wipe 'internal_sd'
Updating partition details...
E: Update to mount 'internal_sd'
Available Partitions as in the Wape menu within TWRP 2.8.7.1
-Dalvik Cache
-Cache
-data
-Internal Storage 11975MB
-System
-Custom Storage
-Internal Storage 0MB [There is actually two of these partition.]
-External Storage
-USB OTG
My best guess is delete the internal sd some how. And/or remove /hwuserdata as well. Or completely return it to stock. Then install 4.3, install TWRP 2.8.7.1, install 5.1, and finally install root. I can't find the img file to push out through adb in "Fastboot&Rescue Mode".
Can someone point me to stock img? This didn't fix my issue within TWRP. I tried installing "MT2L03_B148_Stock_ROM.zip" within TWRP.
All advice would greatly be appreciated.
Thanks!
UPDATE 7/2:
sdcard0 / internal_sd is still broken after applying the downgrade and the b309 rom. Does anyone have the stock rom in an img file format?
Download the public preview of B309 from the blog.
Install it as instructed in the blog post. (You will lose your data, so backup.)
To root and get TWRP, do the below.
Credit to Foltz61.
1. Boot to bootloader.
2. Fastboot boot TWRP-L.img
3. Install supersu-2.49.zip (even though I didn't lose root)
4. Reboot back to system.
5. Reboot back to bootloader.
6. fastboot flash recovery TWRP-L.img.
7. fastboot reboot.
8. Boot to recovery and had TWRP
Thanks for the reply. But I am still stuck with a broken sdcard0 / internal_sd partition. Does anyone have a stock rom in an img file format? Applying the B309.zip and downgrading to 4.3 provided by Huawei still hasn't fixed my problem.
Oh my God...... Which version of TWRP did you use when you restored using your 4.3 backup???
Please, tell me you did not use TWRP 2.8.7.1-L or 2.8.7.0-L for that matter???
in current state, maybe you can try use parted to print your current partition table, and paste here
adb within twrp, it has parted builtin, under OS, you need install the binary.
parted /dev/blk/mmcblk0
unit b
print
I'm posting here for public view.
DO NOT USE TWRP-L IF YOU ARE ON JELLYBEAN 4.3. IT IS MEANT ONLY FOR LOLLIPOP.
SHM said:
I'm posting here for public view.
DO NOT USE TWRP-L IF YOU ARE ON JELLYBEAN 4.3. IT IS MEANT ONLY FOR LOLLIPOP.
Click to expand...
Click to collapse
I installed 4.3 with the huawei files and went over to 5.1. I am not sure if I am in the clear yet. I have a "emulated 0" partition for my sdcard0/internal_sd. When I open ES file browser, it says "no sdcard can be found". But I can write to this "emulated 0" partition. I am guessing this is still broken? I am on TWRP 2.8.7.0 with 5.1.
lowao said:
I installed 4.3 with the huawei files and went over to 5.1. I am not sure if I am in the clear yet. I have a "emulated 0" partition for my sdcard0/internal_sd. When I open ES file browser, it says "no sdcard can be found". But I can write to this "emulated 0" partition. I am guessing this is still broken? I am on TWRP 2.8.7.0 with 5.1.
Click to expand...
Click to collapse
Open terminal, type and enter, su, then type and enter, mount. Share with me what mount says.
That's the same as mine
lowao said:
I installed 4.3 with the huawei files and went over to 5.1. I am not sure if I am in the clear yet. I have a "emulated 0" partition for my sdcard0/internal_sd. When I open ES file browser, it says "no sdcard can be found". But I can write to this "emulated 0" partition. I am guessing this is still broken? I am on TWRP 2.8.7.0 with 5.1.
Click to expand...
Click to collapse
The emulated 0 partition is the same as I have. That should be your internal memory.
robertbarber said:
The emulated 0 partition is the same as I have. That should be your internal memory.
Click to expand...
Click to collapse
Still, to be sure he didn't screw something up since he did use TWRP-L while on 4.3 JellyBean, I still want to see what, mount, displays for him on his terminal.
Emulated partition
I'm using X-plore file manager and I'm not seeing internal_sd but rather getting the internal SD drive showing up under Root/Storage/Emulated/0
I've tried reverting back to 4.3 and associated TWRP, but X-plore still doesn't show internal_sd properly. I'm pretty sure it used to show it properly...or am I imagining it
CromDubh said:
I'm using X-plore file manager and I'm not seeing internal_sd but rather getting the internal SD drive showing up under Root/Storage/Emulated/0
I've tried reverting back to 4.3 and associated TWRP, but X-plore still doesn't show internal_sd properly. I'm pretty sure it used to show it properly...or am I imagining it
Click to expand...
Click to collapse
On 4.3 yes, on 5.1 yes, but on 5.1 it's main location is /data/media/0
You can check by opening terminal and typing then entering, mount.
so as long as it accessible by going to /data/media/0 then its all okay, even though it doesn't show up as an actual drive under X-Plore?
Thanks for your time and help.
Terminal Emulator output
SHM said:
Open terminal, type and enter, su, then type and enter, mount. Share with me what mount says.
Click to expand...
Click to collapse
Mine is also screwed up after the upgrade and I cannot get back to stock, nor can I get TWRP back. Yes, I've reflashed supersu etc. Here's my dump.
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
[email protected]:/ #
tomlogan1 said:
Mine is also screwed up after the upgrade and I cannot get back to stock, nor can I get TWRP back. Yes, I've reflashed supersu etc. Here's my dump.
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:65 /mnt/media_rw/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
[email protected]:/ #
Click to expand...
Click to collapse
Define screwed up? Everything looks normal for your mount points.
Screwed up
SHM said:
Define screwed up? Everything looks normal for your mount points.
Click to expand...
Click to collapse
Updated to 5.1 (was a beta tester). After the upgrade, root, but no TWRP. Tried numerous times to reflash TWRP-L but still the stock EMUI 3 persists. Have verified I can fastboot TWRP to restore previous backups and create new backups but cannot make TWRP permanent.
Have tried the reinstall of SuperSI 2.4x and all the steps multiple times with no success. Tried the Huawei downgrade to B148 and that fails as well.
Regarding trying to install TWRP, that is because of the 5.1 Rom. It checks to see if the recovery is stock. If it isn't then it will overwrite the custom recovery. TWRP has to be booted and system has to be mounted as read/write, not read only, in order for it to patch the Rom so TWRP will stick.
I can't help regarding the beta test Rom though. I was not a tester. So I cannot say specifically what changes there were between the beta Rom and official released Rom. Maybe @xordos, @kimtyson, @Iguanadon, @ScoobSTi or someone else can assist regarding your current dilemma.
tomlogan1 said:
Updated to 5.1 (was a beta tester). After the upgrade, root, but no TWRP. Tried numerous times to reflash TWRP-L but still the stock EMUI 3 persists. Have verified I can fastboot TWRP to restore previous backups and create new backups but cannot make TWRP permanent.
Have tried the reinstall of SuperSI 2.4x and all the steps multiple times with no success. Tried the Huawei downgrade to B148 and that fails as well.
Click to expand...
Click to collapse
Try removing anything related to twrp on internal and/or external sd. Backup if needed. Then fastboot boot twrp. You should get the prompt about read/write.
Edit: remember to use 2.8.0 L
Sent from my MT2L03 using XDA Free mobile app
I am also new to the 5.1 fused internal storage. following is what I noticed.
/sdcard is soft link to /storage/emulated/legacy, which in turn is link to /storage/emulated/0, which again is link to /mnt/shell/emulated/0, which is the internal storage fused to /data: /data/media/0.
But some how ES file explorer can not handle it. In ESFileExplorer in my B309, it show /sdcard as a *file* with a tiny link icon, instead of others normal one (like /vendor) which showed as a *folder* with a tiny link. And every time, when I open ESFileExplorer, it also report error, "/sdcard can not find" something like that. I have to go to its settings page, Directory Settings, and set "Home Directory" to "/storage/emulated/0", then the error is gone. For me, I changed it to /storage/sdcard1, which is my external sdcard.
Another side notes, if sometime your app (that requires root) complains can not write to storage, goto SuperSU settings, and disable "Mount namespace separation", this may help resolve lots of problem.
These is more info from the command line, I can not tell the different between /sdcard and /vendor, but ESFileExplorer can not open /sdcard
(when run these "ls" as non-root user, the result is same)
Code:
[email protected]:/ # ls -l sdcard
ls -l sdcard
lrwxrwxrwx root root 1970-01-01 00:20 sdcard -> /storage/emulated/legacy
[email protected]:/ # ls -l vendor
ls -l vendor
lrwxrwxrwx root root 1970-01-01 00:20 vendor -> /system/vendor
[email protected]:/ # ls -l sdcard/
ls -l sdcard/
drwxrwx--- root sdcard_r 2008-12-31 18:48 Alarms
drwxrwx--x root sdcard_r 2015-07-03 03:36 Android
...
[email protected]:/ # ls -l vendor/
ls -l vendor/
drwxr-xr-x root shell 2015-06-24 13:09 etc
drwxr-xr-x root shell 2015-06-24 13:09 firmware
...
PS, Just realized in the phone setting-storage, I can set default storage to "External", then after that /sdcard become normal as it is not link to fused FS anymore:
Code:
[email protected]:/ # ls -l /sdcard
ls -l /sdcard
lrwxrwxrwx root root 1970-01-01 04:15 sdcard -> /storage/sdcard1
[email protected]:/ # ls -l /storage
ls -l /storage
dr-xr-xr-x root root 1970-01-01 04:15 emulated
lrwxrwxrwx root root 1970-01-01 04:15 sdcard0 -> /storage/emulated/0
drwxrwxr-x root sdcard_rw 2015-07-03 12:50 sdcard1
drwx------ root root 1970-01-01 04:15 uicc0
drwx------ root root 1970-01-01 04:15 usbotg
Why did I not have any problems booting into fastboot, flashing TWRP-L through fastboot, booting directly into TWRP, enabling the read/write dialog option, then flashing SuperSu? TWRP survives, root worked, etc
Couldn't have been a more standard way of going about it.
Also, I had a problem with my external SD card being read only after lollipop update, but I think I fixed it by going to settings and changing default storage to external sd card and rebooting. Now both internal and external can be written to.
Hi,
Completely new to smartphones in general, I just bought a second-hand Samsung Galaxy S2 from a specialized website. I tried to install LineageOS on it but with no success so far (the LineageOS wiki for this device seems to forget some important things when starting from a stock ROM).
Current situation and things that might help:
I don't have a microSD card.
I have a backup of the original .pit file.
Even if I really do not want to use the stock ROM, I can not find a way to reinstall a working one: installation with Odin works but there is a "boot loop" on the Samsung logo.
Installing Replicant works, but it is unfortunately too extremist for me.
As I don't have a microSD card, I try installing with "adb sideload image_file.zip" (like I do with Replicant), but TWRP displays errors about partitions :
Code:
...
E:Unable to locate storage partition for storing settings file.
Updating partition details...
...done
Unable to find partition for path '/system'
Unable to find partition for path '/data'
MTP enabled
Starting ADB sideload feature...
Installing zip file '/sideload/package.zip'
Target: samsung/GT-I9100:4.1.2/JZ054K/I9100XWMS2:user/release-keys
detected filesystem ext4 for /dev/blockmmcblk0p9
detected filesystem ext4 for /dev/blockmmcblk0p10
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
Updater process ended with ERROR: 7
I tried doing a "factory reset" from TWRP but result is the same.
Here are some information that might be useful, gathered from an ADB shell:
/etc/recovery.fstab
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# 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
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0* auto auto defaults wait,voldmanaged=sdcard0:11,nonremovable,noemulatedsd
/devices/platform/s3c-sdhci.2/mmc_host/mmc1* auto auto defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
/devices/platform/s3c_otghcd/usb* auto auto defaults voldmanaged=usbdisk0:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
/etc/mtab
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
/tmp/recovery.fstab
Code:
...
=> Linking mtab
=> Processing recovery.fstab
I:Processing '/dev/block/mmcblk0p9'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p9 /system ext4 ro,noatime
wait
'I:Processing '/dev/block/mmcblk0p7'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
'I:Processing '/dev/block/mmcblk0p1'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
'I:Processing '/dev/block/mmcblk0p10'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
'I:Processing '/dev/block/mmcblk0p12'
E:Invalid block device 'ext4' in fstab line '/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
'I:Processing '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0*'
E:Invalid block device 'auto' in fstab line '/devices/platform/dw_mmc/mmc_host/mmc0/mmc0* auto auto defaults wait,voldmanaged=sdcard0:11,nonremovable,noemulatedsd
'I:Processing '/devices/platform/s3c-sdhci.2/mmc_host/mmc1*'
E:Invalid block device 'auto' in fstab line '/devices/platform/s3c-sdhci.2/mmc_host/mmc1* auto auto defaults wait,voldmanaged=sdcard1:auto,noemulatedsd
'I:Processing '/devices/platform/s3c_otghcd/usb*'
E:Invalid block device 'auto' in fstab line '/devices/platform/s3c_otghcd/usb* auto auto defaults voldmanaged=usbdisk0:auto
'I:Processing '/dev/block/mmcblk0p5'
E:Invalid block device 'emmc' in fstab line '/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
'I:Processing '/dev/block/mmcblk0p6'
E:Invalid block device 'emmc' in fstab line '/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
'E:Unable to locate storage partition for storing settings file.
Updating partition details...
...done
I:Unable to find storage partition '/'.
I:Unmounting main partitions...
Unable to find partition for path '/system'
Unable to find partition for path '/data'
...
I spent many hours hours on this issue and read many many things. I really hope someone will be able to help, or at least sympathise Feel free to ask if I can provide some information. Thanks!
Your life would be easier if you paid ten dollars for an SD card lol. My advice is to flash the stock ROM back. Root it. Install dual boot patcher apk and install lineage as data1. This way you avoid your headache and if anything goes wrong you can just boot back to the stock ROM and try again. Also are you sure you have the right ROM? S2 stuff is hard to find. I've been working on an s3 with no luck. Years ago I downgraded the bootloader and bricked it.
Interesting to know that dual boot with microSD card would be easier than only LineageOS (I am coming from the Linux word where it is generally simpler to remove Windows)… I will try to see that.
I got the stock ROM from samsung-updates.com/device/?id=GT-I9100. I am really disappointed to know that vendors like Samsung does not provide these officially.
Finally done it, thanks to people on Reddit! :victory:
Go to 3W dot reddit dot com/r/LineageOS/comments/603qeq/cannot_boot_into_twrp_on_samsung_galaxy_s2/ where the solution is written many times by different persons. Just note that you have to use TWRP 3.1.0, version 3.1.1 fails (see first post).
Now the goal is to update the LineageOS official wiki…