Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it
Very good news! Hopefully something comes of this. I want to look at the code for TWRP 2.0 and see if that can be ported over to the fire, its touch control.
Sent from my Kindle Fire
you got partition table for fire yet ? i am looking for boot partition
cat /proc/mounts....
Code:
# cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/platform/mmci-omap-hs.1/by-name/splash /dropbox ext4 rw,nosuid,nodev,noatime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/vold/179:12 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:12 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#
cat /proc/partitions
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
#
cat /proc/filesystems
Code:
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev devtmpfs
nodev binfmt_misc
nodev debugfs
nodev sockfs
nodev usbfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
msdos
nodev nfs
nodev nfs4
#
ls /dev/block/platform/mmci-omap-hs.1/by-name
Code:
# ls /dev/block/platform/mmci-omap-hs.1/by-name
media
cache
userdata
system
splash
boot
backup
recovery
dfs
dkernel
bootloader
xloader
#
Probably doesn't help. But I guess it was worth a shot. I'm not sure what the partitions are mapped to. :/
using root explorer i can tell that
/dev/block/platform/mmci-omap-hs.1/by-name/boot
is symlinked to
/dev/block/platform/mmci-omap-hs.1/mmcblk0p7
so if you wanted to mount boot
you could type
mount -o rw,remount /boot
i believe..
well i did a dd if= from the phone to the sdcard, but now we can just grab the boot.img from the update on amazon's site
Can you post pictures? This is the main reason I am not trading my fire for a nook.
http://i.imgur.com/9zWTk.jpg just gettings rid of those error messages now. had the wrong filesystem for /cache
I love you.screw the nook.
Wow JackpotCalvin! How were you able to flash the clockwork recovery? Also are you still able to load your KF as normal?
really nice work
another way to mount things as is done in the init.rc:
mount [email protected]/system system
so for rw..."mount -o rw,remount -t ext4 [email protected] /system"
anyway mounts are as follows:
backup -> mmcblk0p6
boot -> mmcblk0p7
bootloader ->mmcblk0p2
cache -> mmcblk0p11
dfs -> mmcblk0p4
dkernel -> mmcblk0p3
media -> mmcblk0p12
recovery -> mmcblk0p5
splash -> mmcblk0p8
system -> mmcblk0p9
userdata -> mmcblk0p10
xloader -> mmcblk0p1
well we're at a bit of a road block as of right now as we have no way to navigate through the menu, we can just press OK and reboot the kindle. also, pressing reboot now does not start the device normally, it just reboots into clockwork. i'm looking for the flag that the OS puts in /cache or /data to trigger a recovery reboot because pressing reboot now does not remove that flag so it will continue to reboot into clockwork unless you do a little hackery to put the stock recovery back on it and then reboot it into the stock recovery and make it fail the signature verification this fluke update.zip i made. we need to find a way to make a fail safe to reboot into recovery as well in case when we start roming, something goes wrong
Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
JackpotClavin said:
when we start roming,
Click to expand...
Click to collapse
Emphasis mine. I can't wait. Great work so far, this seems to be going a lot faster than I imagined at first. I wish I had the programming chops to become a dev, instead i just look on from the sidelines, and maybe monetarily support projects when and where I can.
Awesome work guys. I've got the Nook Tablet but thought I'd pop over to see how it's going. Again, awesome work.
Sent from my Nook Tablet using Tapatalk
littleemp said:
Do you think something like this might work?
https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en
Click to expand...
Click to collapse
The official clockword mod does not support the fire yet... if that's what you're asking. That is what OP is trying to do.
JackpotClavin said:
Here's the deal, I flashed a clockwork port for the kindle fire that I made. It was 100% useless as of now because of the one hardware button that we have to work with. I sent Koush a message on twitter asking if there is a possibility to have a long press and quick/short press differentiate between scrolling down and actually selecting the item on the menu but he hasn't gotten back to me yet but I'm sure he's working on it
Click to expand...
Click to collapse
How did you boot into recovery?
well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do
JackpotClavin said:
well i've just made a clockwork backup of my current system. i believe ive found a way that we can manage to "navigate" through the menu, even though it's a real pain in the ass to do
Click to expand...
Click to collapse
Sounds like we may have to be connected to our PC to run the commands...??
Related
Cwm v5.0.2.7 For LG Nitro HD (P930) /Optimus LTE
Current Status: Operational
Installation/Update Instructions:
Before installing make sure that your phone is rooted
Code:
Backup your existing recovery:
1) [COLOR="Magenta"]cat /dev/block/mmcblk0p13 > /sdcard/recovery-backup.img[/COLOR]
Flash the new recovery by:
1) Download the bc64-recovery.rar and extract it
2) Copy the extracted bc64-recovery.img to your /sdcard
3) via terminal emulator or adb shell execute:
[COLOR="Magenta"]
su
cd /sdcard
cat bc64-recovery.img > /dev/block/mmcblk0p13[/COLOR]
All Done!
Now to Boot into recovery , press the vol down+pwr button , when it asks you to factory reset , tap twice the pwr button to confirm (dont worry it wont format your device)
Screenshots:
Video:
Code:
http://www.youtube.com/watch?v=okr8PWeQ30E
ChangeLog:
Code:
v0.2 B20120124
Changes:
* Added postrecoveryboot.sh to clear out boot command
* Added Partition/fs Utils (useful for rom dev in formatting/checking ext4 fs)
-e2fsck_static
-mke2fs_static
-resize2fs_static
-tune2fs_static
v0.1 B20120120 (Initial Release)
Known Issues:
Code:
wrong timestamps
Tested On:
Code:
Atnt LG Nitro HD (P930)
LG Optimus LTE (SU640)
Thanks To:
Code:
schwin97
[email protected]
Malnilion
repherb
aquariuz23
gte460z
and everyone else who contributed to this thread :P
Download:
Code:
http://www.mediafire.com/?mnf53sxmp5aifd9
Source Code (Sorry , too lazy for github fttb):
Code:
http://www.mediafire.com/?f27d8j8d7mc8qi8
For Rom Developers:
It seems that default cwm format is messing up (due to ext4 file system) , Please use (edify) the following script to format the data and cache partition (or System)
Code:
#Format Data
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30
#Format Cache
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p28
# After Format Verify the FIle System
/sbin/e2fsck_static -y /dev/block/mmcblk0p30
/sbin/e2fsck_static -y /dev/block/mmcblk0p28
Edify (To Format System):
Code:
run_program("/sbin/mke2fs_static", "-t" , "ext4" "/dev/block/mmcblk0p27");
AND
run_program("/sbin/e2fsck_static", "-y", "/dev/block/mmcblk0p27");
/proc/mtd doesn't exist...
Don't know if this any help:
http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32
Images Added based on the info provided :
Code:
http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32
Is this suppose to be Clockwork Mod for the Nitro? Wat's with the 5? Version 5?
Can you teach me how to make the recovery.img.
My device is LG Optimus LTE SU640 which has the most same hardware with P930.
Yes this is version 5
@belth219 ill port it for you once i get confirmation for this image
Ok,thanks.
@belth219 could you do a "cat /proc/partitions" on your cell and post its results?
Also providing the results for the above command for nitro HD would also be very usefull.
This is the result of my lu6200
Another version of p930
# su
su
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3526656 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1048576 mmcblk0p26
179 27 327680 mmcblk0p27
179 28 1548288 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 1024 mmcblk0p30
179 31 229376 mmcblk0p31
259 0 4096 mmcblk0p32
179 32 7774208 mmcblk1
179 33 7773184 mmcblk1p1
#
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p26 /system ext4 rw,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p29 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p31 /lgumsg ext4 rw,nosuid,nodev,relatime,barrier=1,data=order
ed 0 0
/dev/block/mmcblk0p23 /mm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0
0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,
dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,e
rrors=remount-ro 0 0
My phone is LU6200,too. Could you tell me if I can install this mod on my phone? The only difference of 2 device is the CPU
I dont think it would work on your device as im sure it has diffrent kernel , upload your boot.img , i will port it once i get nitro hd confirmation
SU640
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 3526656 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 860160 mmcblk0p27
179 28 327680 mmcblk0p28
179 29 3072 mmcblk0p29
179 30 1957638 mmcblk0p30
179 31 16384 mmcblk0p31
259 0 2048 mmcblk0p32
179 32 15622144 mmcblk1
179 33 15618048 mmcblk1p1
254 0 2110 dm-0
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p27 /system ext4 ro,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p22 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o
rdered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p30 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p31 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p23 /mm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0
0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,
dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,e
rrors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.cyandroid.pianofull-1 vfat ro,dirsync,nosuid,nodev
,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shor
tname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
OK...
I just ran 'cat /dev/zero > /dev/block/mmcblk0p27', remounted my system partition as read/write and copied the recovery.img into the directory. Just rebooted in hopes it will flash the recovery image to the recovery partition p27 above. Will now attempt rebooting into recovery to see if anything happened...
---------- Post added at 09:05 AM ---------- Previous post was at 09:01 AM ----------
Upon using anreboot to boot into recovery I get...
Code:
Enter the fastboot...
Enter the fastboot...
Long time no see!
And the LG logo beneath it... It also attempted to install a new driver 'android', but couldn't find it on my computer. Very excited that we are moving closer to getting a 'real' recovery mode on the phone...
Now to see if I can reboot normally?
---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------
And it still boots normally and is fully functional when it does boot!!! Good progress so far. Now, does anyone know how to determine the driver it is looking for? I think if I find the right driver I can get into fastboot mode and do anything else that is necessary?
schwin97 said:
OK...
I just ran 'cat /dev/zero > /dev/block/mmcblk0p27', remounted my system partition as read/write and copied the recovery.img into the directory. Just rebooted in hopes it will flash the recovery image to the recovery partition p27 above. Will now attempt rebooting into recovery to see if anything happened...
---------- Post added at 09:05 AM ---------- Previous post was at 09:01 AM ----------
Upon using anreboot to boot into recovery I get...
Code:
Enter the fastboot...
Enter the fastboot...
Long time no see!
And the LG logo beneath it... It also attempted to install a new driver 'android', but couldn't find it on my computer. Very excited that we are moving closer to getting a 'real' recovery mode on the phone...
Now to see if I can reboot normally?
Click to expand...
Click to collapse
Why did you ran cat /dev/zero > /dev/block/mmcblk0p27?
as of this http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32 post your recovery partition should be /dev/block/mmcblk0p27
so To be me steps would have been:
1) Backing up recovery partition using dd
2) Remounting System partiton as read write
3) copying recovery.img to /system and flashing the recovery.img
4) booting into recovery
For fastboot you should have andriod sdk installed , get it at :
Code:
http://developer.android.com/sdk/download.html
I agree, but when I miss the part about putting the recovery image in the system directory for it to automatically reflash, I started running the steps to flash the recovery image as people flash the boot image...
An extra step that luckily didn't have any bad consequences...
---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------
bytecode64 said:
For fastboot you should have andriod sdk installed , get it at :
Code:
http://developer.android.com/sdk/download.html
Click to expand...
Click to collapse
I have the sdk installed - but my laptop is asking for a driver - is the driver within the sdk download? If I don't give it the driver then it says the device didn't get installed correctly and fastboot doesn't see it.
what about USB drivers and Modem?
Did you installed http://s3.amazonaws.com/lgforum.com/resources/assets/680/original/LGP930.zip?1322664514
?
I have uploaded my boot.img & recovery.img to dropbox.
But I can not post any links now.It needs 8 posts.
Sure did. I have the drivers that are needed when the phone boots up normally? Just when it boots up in this new recovery mode that it is asking for a new driver? It shouldn't be asking for anything new, but it is... Another question - after it loads up the new recovery image from the /system directory should it remove the recovery image? If so, then if the recovery image is still in the system directory we may have a problem?
---------- Post added at 09:44 AM ---------- Previous post was at 09:39 AM ----------
As I had thought - recovery.img is still in the system directory... Does this indicate a problem?
schwin97 said:
I have the sdk installed - but my laptop is asking for a driver - is the driver within the sdk download? If I don't give it the driver then it says the device didn't get installed correctly and fastboot doesn't see it.
Click to expand...
Click to collapse
You should install the LGMobile update which can be downloaded from LG official website.
That is a useful tool.
I got my nexus 7 2013 a few weeks ago. It worked great for some time until I decided to flash a kernel that claimed to add support for CIFS windows shares mount. After installing this kernel, when the OS booted, I did not have landscape mode working anymore - only portrait. I decided to do adb full restore to a full backup i made before this step, which seemed to have passed without any errors, but something happened to the recognition of the internal SD memory - applications are not able to use it - I am getting "no external storage" messages when I launch the gallery application and an error when trying to run the google play store - "unfortunetley, google play store has stopped". The device is still starting with only portrait mode.
i then tried to format the device and used TWRP to format everything including the internal memory. After that I reflashed the original rom of google for this device (taken from here https://developers.google.com/android/nexus/images#razorjss15r). The problem is still the same. In TWRP recovery console - I am able to access and push files to and from /sdcard folder with no problems, and see its content with adb shell.
When android loads - cd /sdcard + ls shows that it is empty (even though it does contain files copied to it in recovery console mode) the reason for this is that with ls I can see that "/sdcard" points to "/storage/emulated/legacy" which points to "/mnt/shell/emulated/0" which DOES NOT exist. "/mnt/shell/emulated/" folder exists, but it is empty.
I am unable to use the device - just start the OS (and get the error messages when trying to launch applications). When the OS loads I immediately get the "unfortunetley, google play store has stopped" error without doing anything.
running google earth application when logcat active gives the following output:
--------
E/cutils (10727): Failed to chmod(/mnt/shell/emulated/0, 0): Read-only file system
E/dalvikvm(10727): cannot mountExternalStorage(): Read-only file system
I/ActivityManager( 492): Start proc com.google.earth for activity com.google.earth/.EarthActivity: pid=10727 uid=10024 gids={50024, 3003, 1015, 1028}
D/dalvikvm(10727): No JNI_OnLoad found in /system/lib/libearthmobile.so 0x41dc5158, skipping init
--------
i've attached logcat and dmesg outputs i got.
Any idea how do I solve this? Why are the folder links broken when I am using an original google rom?
I've attached a bug report created using nexus root toolkit 1.78. searching for "failed" word in the log shows the problem happens over and over again as i try to use different applications:
"Failed to mkdir(/mnt/shell/emulated/0): Read-only file system".
i cannot use any application that needs the internal SD storage even though it is mounted to /data and the system reports 25GB available storage as can be seen by searching this log for "FREE SPACE" (df output)
working in "adb shell" as root (after "su"), i cannot write to any of the device's folders - only after executing "mount -o rw,remount /" it becomes possible (and only for the same session of the shell).
It would be very helpful if someone with a working nexus 7 2nd can post he/she's own device's bug report file so I'll be able to compare it to mine and see if i can find any differences. It can be done using the nexus toolkit:
"Launch" -> "Launch Generator" -> "OK" -> "Dump bug report to file" (filter output and alternate buffer log are unchecked).
Is there no one here that has experience with under the hood stuff of android and its filesystem?
Any help/directions will be appreciated.
I have the same problem did you find a solution?
Waledzaki said:
I have the same problem did you find a solution?
Click to expand...
Click to collapse
not yet - we need someone to post his debug info or at least "mount" command output for a working android 4.3+ device. maybe by comparison we'll be able to find what is wrong.
I must say i find the android community is quite disappointing - no one seems to give any directions even though full logs and detailed problem description supplied here.
I'm coming from maemo community (n900 device) which has many way better OS professionals.
liran corleone said:
It would be very helpful if someone with a working nexus 7 2nd can post he/she's own device's bug report file so I'll be able to compare it to mine and see if i can find any differences. It can be done using the nexus toolkit:
"Launch" -> "Launch Generator" -> "OK" -> "Dump bug report to file" (filter output and alternate buffer log are unchecked).
Click to expand...
Click to collapse
I have a new nexus7 (2013) with android 4.4.2 , not unlocked, not rooted. Can i help you with this bug report?
Have you a link to the nexus toolkit?
alligator_asl said:
I have a new nexus7 (2013) with android 4.4.2 , not unlocked, not rooted. Can i help you with this bug report?
Have you a link to the nexus toolkit?
Click to expand...
Click to collapse
you can download it from here: http://www.wugfresh.com/
after starting and choosing your device, press "Launch" button -> "Launch Generator" -> "Dump bug report to file" -> this will create the needed log file.
It would be great if you can post it (the log file) here.
Thanks.
Hello,
I generated this report and looked at him, unfortunately he contains too many personal details such as MAC addresses, SSID's, e-mail addresses, used apps, calendars and many others. I think, I can only post parts here. Can you tell me which parts you need?
alligator_asl said:
Hello,
I generated this report and looked at him, unfortunately he contains too many personal details such as MAC addresses, SSID's, e-mail addresses, used apps, calendars and many others. I think, I can only post parts here. Can you tell me which parts you need?
Click to expand...
Click to collapse
These sections are important (search for these strings in the log file):
KERNEL LOG
SYSTEM LOG
EVENT LOG
LAST KMSG
FILESYSTEMS & FREE SPACE
if there is a problem to publish it here, maybe you can send me on private?
it would be great if you can post these section from a log file which was created in the following way (in order to produce a clean log):
reboot the device, run an application that uses the internal storage (google earth for example) and recreate the log.
Thanks.
liran corleone said:
reboot the device, run an application that uses the internal storage (google earth for example) and recreate the log.
Click to expand...
Click to collapse
I did so, and here are the logs:
alligator_asl said:
I did so, and here are the logs:
Click to expand...
Click to collapse
i already found very interesting differences, although i'm not sure yet how this should be fixed:
in KERNEL LOG (dmesg):
Working device:
<6>[ 6.572631] EXT4-fs (mmcblk0p30): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
<7>[ 6.572784] SELinux: initialized (dev mmcblk0p30, type ext4), uses xattr
<6>[ 6.578033] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nodelalloc
<7>[ 6.578155] SELinux: initialized (dev mmcblk0p4, type ext4), uses xattr
Non working device:
<6>[ 6.130340] EXT4-fs (mmcblk0p30): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
<7>[ 6.130462] SELinux: initialized (dev mmcblk0p30, type ext4), uses xattr
<3>[ 6.131042] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 6.198333] fs_mgr: Cannot mount filesystem on /dev/block/platform/msm_sdcc.1/by-name/persist at /persist
<3>[ 6.198425] init: fs_mgr_mount_all returned an error
"df" on working device:
Filesystem Size Used Free Blksize
/dev 902.9M 128.0K 902.8M 4096
/sys/fs/cgroup 902.9M 12.0K 902.9M 4096
/mnt/asec 902.9M 0.0K 902.9M 4096
/mnt/obb 902.9M 0.0K 902.9M 4096
/system 827.8M 700.9M 126.9M 4096
/cache 551.7M 9.9M 541.8M 4096
/data 26.4G 2.9G 23.6G 4096
/persist 14.5M 4.2M 10.2M 4096
/mnt/shell/emulated 26.4G 2.9G 23.6G 4096
"df" on non working device missing 2 mount points, and found a new one:
Filesystem Size Used Free Blksize
/dev 902.9M 128.0K 902.8M 4096
/sys/fs/cgroup 902.9M 12.0K 902.9M 4096
/mnt/asec 902.9M 0.0K 902.9M 4096
/mnt/obb 902.9M 0.0K 902.9M 4096
/system 827.8M 690.2M 137.5M 4096
/cache 551.7M 13.2M 538.6M 4096
/data 26.4G 337.4M 26.1G 4096
/mnt/secure 902.9M 0.0K 902.9M 4096
May be, this helps a little bit:
Code:
e:\Prog\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ mount
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
debugfs /sys/kernel/debug debugfs 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/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ $
alligator_asl said:
May be, this helps a little bit:
Code:
e:\Prog\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ mount
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
debugfs /sys/kernel/debug debugfs 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/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ $
Click to expand...
Click to collapse
i suggest you keep the full log and full file structure (list of all files in all folders) - just in case you will get to this situation also.
liran corleone said:
i already found very interesting differences, although i'm not sure yet how this should be fixed:
in KERNEL LOG (dmesg):
Working device:
<6>[ 6.572631] EXT4-fs (mmcblk0p30): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
<7>[ 6.572784] SELinux: initialized (dev mmcblk0p30, type ext4), uses xattr
<6>[ 6.578033] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nodelalloc
<7>[ 6.578155] SELinux: initialized (dev mmcblk0p4, type ext4), uses xattr
Non working device:
<6>[ 6.130340] EXT4-fs (mmcblk0p30): mounted filesystem with ordered data mode. Opts: barrier=1,data=ordered,nomblk_io_submit,errors=panic
<7>[ 6.130462] SELinux: initialized (dev mmcblk0p30, type ext4), uses xattr
<3>[ 6.131042] EXT4-fs (mmcblk0p4): VFS: Can't find ext4 filesystem
<3>[ 6.198333] fs_mgr: Cannot mount filesystem on /dev/block/platform/msm_sdcc.1/by-name/persist at /persist
<3>[ 6.198425] init: fs_mgr_mount_all returned an error
"df" on working device:
Filesystem Size Used Free Blksize
/dev 902.9M 128.0K 902.8M 4096
/sys/fs/cgroup 902.9M 12.0K 902.9M 4096
/mnt/asec 902.9M 0.0K 902.9M 4096
/mnt/obb 902.9M 0.0K 902.9M 4096
/system 827.8M 700.9M 126.9M 4096
/cache 551.7M 9.9M 541.8M 4096
/data 26.4G 2.9G 23.6G 4096
/persist 14.5M 4.2M 10.2M 4096
/mnt/shell/emulated 26.4G 2.9G 23.6G 4096
"df" on non working device missing 2 mount points, and found a new one:
Filesystem Size Used Free Blksize
/dev 902.9M 128.0K 902.8M 4096
/sys/fs/cgroup 902.9M 12.0K 902.9M 4096
/mnt/asec 902.9M 0.0K 902.9M 4096
/mnt/obb 902.9M 0.0K 902.9M 4096
/system 827.8M 690.2M 137.5M 4096
/cache 551.7M 13.2M 538.6M 4096
/data 26.4G 337.4M 26.1G 4096
/mnt/secure 902.9M 0.0K 902.9M 4096
Click to expand...
Click to collapse
did u find any solution or there is non?!
Waledzaki said:
did u find any solution or there is non?!
Click to expand...
Click to collapse
didn't find one yet - i am currently using it without the SD storage - installing the apks manually (the ones that does not require it).
Still nothing ?
liran corleone said:
didn't find one yet - i am currently using it without the SD storage - installing the apks manually (the ones that does not require it).
Click to expand...
Click to collapse
Still no solutions ? thanks in advance
have to bring this from the dead, i made a new post about this exact same issue with no response, you are obviously far more knowledgeable on this subject so i hope a dev sees this or someone who knows a fix can chime in.
have you found a fix yet though?
Got this one fixed.
Steps:
Root your device
Boot into android and enable USB debugging
Connect device to PC
Start up "adb shell", then type in "su"
A supersu prompt would pop up on the device, agree to give adb shell root permissions.
In adb shell execute "make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist"
In adb shell type "exit" twice to quit.
Execute "adb reboot".
Fixed.
Since Lollipop, I can no longer access hboot via /dev/block/mmcblk0p11, and when I do # mount | grep blk, it shows:
/dev/block/mmcblk0p45 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/mmcblk0p46 /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p39 /devlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p27 /fataldevlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p37 /carrier ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=ordered 0 0
/dev/block/mmcblk0p22 /custdata ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
During 4.4.x, I was able to access hboot via mmcblk0p22 but it was gone since 5.0.x. I wanna take away those annoying red text, can anyone point me to the right direction?
You can get it from here:
http://forum.xda-developers.com/showthread.php?t=2710503
I don't know what happened, my battery died, I plugged it in, turned the phone back on, and boom, my phone is throwing errors out left and right, and ES File Explorer is saying '/sdcard/' is not found. I've tried going to storage/emulated/0 & legacy, but I get the same not found message.
Storage in System Settings shows that the storage is still being used, and the file browser in TWRP shows all the files are still there. It just seems like the mount points or bindings got all screwy.
My phone is on the BOF5 firmware, it's stock rooted. I've had no problems restarting my phone, usually have to atleast twice a week. Nothing funky installed, atleast nothing that would mess with the SD card. No SW was uninstalled, just frozen, and it wasn't much [Voicemail, Internet (Browser), Hangouts]
I'm really just hoping that someone, somewhere knows a way to help me fix this so I don't have to restore!
krakerx said:
I don't know what happened, my battery died, I plugged it in, turned the phone back on, and boom, my phone is throwing errors out left and right, and ES File Explorer is saying '/sdcard/' is not found. I've tried going to storage/emulated/0 & legacy, but I get the same not found message.
Storage in System Settings shows that the storage is still being used, and the file browser in TWRP shows all the files are still there. It just seems like the mount points or bindings got all screwy.
My phone is on the BOF5 firmware, it's stock rooted. I've had no problems restarting my phone, usually have to atleast twice a week. Nothing funky installed, atleast nothing that would mess with the SD card. No SW was uninstalled, just frozen, and it wasn't much [Voicemail, Internet (Browser), Hangouts]
I'm really just hoping that someone, somewhere knows a way to help me fix this so I don't have to restore!
Click to expand...
Click to collapse
Youre taking all the fun out of it. Backing up and restoring from scratch is half the fun with android phones. If youre gonna root to have fun, be prepared to do the dirty work as well. JMHO
xxSTARBUCKSxx said:
Youre taking all the fun out of it. Backing up and restoring from scratch is half the fun with android phones. If youre gonna root to have fun, be prepared to do the dirty work as well. JMHO
Click to expand...
Click to collapse
Well, I'm looking to do the dirty work, otherwise I would have just restored the phone from my backup weeks ago. But I don't want to do that, because, honestly, there has got to be a way to see this data. With that said, here is the output from running 'mount' in TWRP and Terminal Emulator:
C:\MiniADB\adb shell
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1418352k,nr_inodes=154938,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,size=1418352k,nr_inodes=154938)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p27 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p27 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p25 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
===========================================================================================================
[email protected]:/ $ su
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1414720k,nr_inodes=153121,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=700 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1414720k,nr_inodes=153121,mode=755,gid=1000 0 0
/dev/block/bootdevice/by-name/modem /firmware-modem vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/apnhlos /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,norecovery 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/bootdevice/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/carrier /carrier ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persdata /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1414720k,nr_inodes=153121,mode=050,gid=1028 0 0
tmpfs /storage/emulated/legacy tmpfs rw,seclabel,nosuid,nodev,relatime,size=1414720k,nr_inodes=153121,mode=050,gid=1028 0 0
[email protected]:/ #
Hopefully someone with BOF5 rooted stock can take a look at their mount points and see if they lineup with what I'm getting
krakerx said:
Well, I'm looking to do the dirty work, otherwise I would have just restored the phone from my backup weeks ago. But I don't want to do that, because, honestly, there has got to be a way to see this data. With that said, here is the output from running 'mount' in TWRP and Terminal Emulator:
Click to expand...
Click to collapse
Thanks for posting this.
Hopefully someone who is still on OF5 can match and compare/contrast whats there or not there. Maybe unrooting and OG5 is the way to go or simply trying it in your laptop(if it has a SD cardslot reader and see if it functions properly there) Might be time to get a new card
SD card is fine, internal memory is fine... Found the issue was a corrupted sdcard pointer, once fixed, phone runs like it should
In the past I've done this from the recovery shell. But TWRP 3.0.0.1 does not offer this option under advanced wipe ... From the adb shell while booted into Pure Nexus i see a make_f2fs binary ... but have never attempted to format partitions from the booted system ...
Code:
1|roo[email protected]:/ # make_f2fs
F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18)
Error: Device not specified
Usage: mkfs.f2fs [options] device [sectors]
[options]:
-a heap-based allocation [default:1]
-d debug level [default:0]
-e [extension list] e.g. "mp3,gif,mov"
-l label
-o overprovision ratio [default:5]
-s # of segments per section [default:1]
-z # of sections per zone [default:1]
-t 0: nodiscard, 1: discard [default:1]
sectors: number of sectors. [default: determined by device size]
Code:
1|[email protected]:/ # mount
rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=919280k,nr_inodes=229820,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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
/sys/kernel/debug /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=919280k,nr_inodes=229820,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=919280k,nr_inodes=229820,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/vendor /vendor ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,errors=panic,data=ordered 0 0
/dev/block/platform/soc.0/f9824900.sdhci/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=919280k,nr_inodes=229820,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
http://4pda.ru/forum/dl/post/7694971/recovery.img
luis666 said:
http://4pda.ru/forum/dl/post/7694971/recovery.img
Click to expand...
Click to collapse
Hey, thanks - but I'm getting a 404 at that link. Is that a version of TWRP or another recovery that will let me use F2FS?
+1
Use jolla kernel's recovery, flash it. It has the option to change the file system to f2fs.
RonnellTapawan said:
Use jolla kernel's recovery, flash it. It has the option to change the file system to f2fs.
Click to expand...
Click to collapse
After that, can i flash FLASH-kernel(with f2fs support) and still have f2fs?
axiel7 said:
After that, can i flash FLASH-kernel(with f2fs support) and still have f2fs?
Click to expand...
Click to collapse
after you change the file system to f2fs, it will be retained unless you change it again to ext4 or format it again (not sure about this one). in short, yes, you can flash 'flash' kernel and use any rom you want. also, i advice not to use other twrp anymore because jolla's twrp is much better.