I did not found vold.fstab file so I looked from the internet and i found that android can have vold.fstab file named fstab.*model* in "/" directory, and I found it but now i want to swap my sdcard and internal memory, but fstab.*model* looks like this: # Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/devices/msm_sdcc.2/mmc_host /storage/external_SD vfat nosuid,nodev wait,voldmanaged=external_SD:auto
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1,discard wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard,data=ordered wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-name/encrypt
#/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc wait,check
#/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered wait,check
#/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 nosuid,nodev,barrier=1,data=ordered wait,check
#/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 nosuid,nodev,barrier=1,data=ordered wait,check
#/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
#/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
#/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
What i have to change?
Send from lg D620r (rooted).
Send me your boot.img and your build.prop
Sorry, but where is boot.img
Sent from my LG G2 Mini using XDA Labs
And how i send them to you? Via email or? When I am trying to link with xda it says this:
Sent from my LG G2 Mini using XDA Labs
eeeelinen said:
And how i send them to you? Via email or? When I am trying to link with xda it says this:
Click to expand...
Click to collapse
Use google to figure out how to grab the boot.img , zip it and upload it here.
As for build.prop , first copy it to the internal SD and then upload it here.
Can't upload?
Sent from my LG G2 Mini using XDA Labs
eeeelinen said:
Can't upload?
Click to expand...
Click to collapse
Put them in a zip file
Already did. But i don't have boot.img. yet.
Sent from my LG G2 Mini using XDA Labs
.zip
Sent from my LG G2 Mini using XDA Labs
eeeelinen said:
.zip
Click to expand...
Click to collapse
Upload it on some other service (Google Drive, Dropbox, Mega, etc.) and give me the link.
Ok. Build.prop: Files in https://db.tt/aRorEzNT2F are shared. Tap link to go to web page.
Sent from my LG G2 Mini using XDA Labs
But i dont have boot.img yet i'm trying to get it as fast as i can.
Sent from my LG G2 Mini using XDA Labs
K, I didn't find any ways to get boot.img that are working. I keep searching but if none of them work What I will do?
Sent from my LG G2 Mini using XDA Labs
eeeelinen said:
K, I didn't find any ways to get boot.img that are working. I keep searching but if none of them work What I will do?
Click to expand...
Click to collapse
Download a terminal emulator app from Play Store and enter these commands:
Code:
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/emulated/0
Grand SU permissions when prompted.
Thank you!:laugh: now both files are in same link!
Sent from my LG G2 Mini using XDA Labs
https://db.tt/aRorEzNT2F
Sent from my LG G2 Mini using XDA Labs
Related
Anyone interested on this part
EXT4 has journaling FS so it will be more fast I/0
Code:
ui_print("EXT4 script by LtHuNTer_StepheN");
ui_print("");
show_progress(1, 50);
ui_print("-> Formatting System To EXT4 ");
format("ext4", "MTD", "system");
ui_print("-> Formatting Cache To EXT4");
format("ext4", "MTD", "cache");
ui_print("-> Formatting Data To EXT4");
format("ext4", "MTD", "userdata");
ui_print("Finished");
for edititing necesary file
ask ur rom builder ok
LtHuNTer_StepheN said:
Anyone interested on this part
EXT4 has journaling FS so it will be more fast I/0
Click to expand...
Click to collapse
What???
WTF?!
Sent from my E15i using xda premium
LtHuNTer_StepheN said:
Anyone interested on this part
EXT4 has journaling FS so it will be more fast I/0
Click to expand...
Click to collapse
im to interest
n1kolaa said:
im to interest
Click to expand...
Click to collapse
I'm interested too, but what's this?
Sent from my E15i using xda premium
we can try to format system,data,cache with EXT4 filesystem
and use it
we need to edit init.rc (and some file) to mount system,data,cache as ext4
LtHuNTer_StepheN said:
Anyone interested on this part
EXT4 has journaling FS so it will be more fast I/0
Click to expand...
Click to collapse
http://www.thegeekstuff.com/2011/05/ext2-ext3-ext4/
Journaling is SLOWING DOWN writes and it destroy SD card faster!
rav3n_pl said:
http://www.thegeekstuff.com/2011/05/ext2-ext3-ext4/
Journaling is SLOWING DOWN writes and it destroy SD card faster!
Click to expand...
Click to collapse
no ur wrong
ur totaly wrong
here some code for you
Code:
tune2fs -o journal_data_writeback /block/path/to/system
tune2fs -O ^has_journal /block/path/to/system
tune2fs -o journal_data_writeback /block/path/to/cache
tune2fs -O ^has_journal /block/path/to/cache
tune2fs -o journal_data_writeback /block/path/to/data
tune2fs -O ^has_journal /block/path/to/data
this code remove some journalism
this will make I/0 faster
and sdcard ???
?????????????
O.k., so what and how can I do to have faster i/o?
Sent from my E15i using xda premium
LtHuNTer_StepheN said:
we can try to format system,data,cache with EXT4 filesystem
and use it
we need to edit init.rc (and some file) to mount system,data,cache as ext4
Click to expand...
Click to collapse
Okay, maybe you write down exact solution?
And what about CWM?
Update Script finished
still editing init.rc to mount system with ext4 file system
LtHuNTer_StepheN said:
Update Script finished
still editing init.rc to mount system with ext4 file system
Click to expand...
Click to collapse
But for safe I'll try that with a 2GB card, I don't want to destroy my 8GB ;D
Sent from my E15i using xda premium
Our X8 don't have emmc,but mtd(nand).Your script will not work.
I'm currently testing to see if this is something we can use.
alfsamsung said:
Our X8 don't have emmc,but mtd(nand).Your script will not work.
I'm currently testing to see if this is something we can use.
Click to expand...
Click to collapse
i think ext4 is the fastest i/0
update script changed
we need rom/kernel builder (i found kernel builder you)
just rom builder to edit necessary file
I have experience in this stuff, my former phone was a galaxy spica.
ext2 will be the fastest, ext4 is slower, ext3 is in middle.
For that phone the fs conversion did miracle in speed (stock fs is rfs).
I don't really know that this fs conversion will do something with this phone, but if it will do some plus I will try... but will wait for news on this
hey...I tried to implement that script in my rom and edited the init.rc to mount system and cache from the boot.img but my rom doesn't boot...
i changed the init.rc from this
Code:
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
mount yaffs2 [email protected] /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
to this
Code:
mount ext4 [email protected] /system
mount ext4 [email protected] /system ro remount
mount ext4 [email protected] /data nosuid nodev
mount ext4 [email protected] /cache nosuid nodev
droidx8 said:
But for safe I'll try that with a 2GB card, I don't want to destroy my 8GB ;D
Sent from my E15i using xda premium
Click to expand...
Click to collapse
facepalm This mod is for internal storage, not external like sd.
i have 1 gb partition in ext 3 on my sdcard, i can update to ext 4 without format the sd card? there is a way?
type in terminal
su
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0pX
/* Where X is, is the partition number to find this out use root explorer and navigate to /dev/block and look for the partiton number bear in mind that mmcblk0 is you fat32 partition with all you pictures video etc so dont convert it or windows wont read it. another way to find it in terminal type "mount" without quotes and look for your current ext3 partition number */
then type
e2fsck -pf /dev/block/mmcblk0pX
this will check the partition for any errors that may have happened during conversion.
eoghan2t7 said:
type in terminal
su
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0pX
/* Where X is, is the partition number to find this out use root explorer and navigate to /dev/block and look for the partiton number bear in mind that mmcblk0 is you fat32 partition with all you pictures video etc so dont convert it or windows wont read it. another way to find it in terminal type "mount" without quotes and look for your current ext3 partition number */
then type
e2fsck -pf /dev/block/mmcblk0pX
this will check the partition for any errors that may have happened during conversion.
Click to expand...
Click to collapse
this what do? it format something?
djsolidsnake86 said:
this what do? it format something?
Click to expand...
Click to collapse
no this will not format anything it should just upgrade ext3 to ext4 i dont it that way a few months back and nothing got formatted but backup to be safe
i see, and for create a swap partition for ram? do you think it's useful?
if you kernel supports zram then swap is not needed as zram gets used as swap but if not i recommend swap if your on android 4.X as its will get better performance that a gingerbread rom. I you go down the road to making a swap partition it will format your sd card in order to make the partition correctly.
On my kernels i have enabled zram, zcache, frontswap and clean cache so maybe you could ask your Favorite rom dev to include these kernel features in there next update.
the terminal say me tune2fs 1.41.12 17 may 2010
what means?
djsolidsnake86 said:
the terminal say me tune2fs 1.41.12 17 may 2010
what means?
Click to expand...
Click to collapse
That's just telling you the version that's within busy box do the rest of the commands and it will upgrade.
Sent from my Wildfire S A510e using Tapatalk 2
but nothing happen after this
djsolidsnake86 said:
but nothing happen after this
Click to expand...
Click to collapse
What command are you typing including partition number?
Sent from my Wildfire S A510e using Tapatalk 2
su
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
this with the number partition
and say me that message
the partition is still in ext3
Questions should be posted in Q&A forums, not Development forums.
http://forum.xda-developers.com/announcement.php?a=81
See rule #15
Thread moved.
djsolidsnake86 said:
su
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
this with the number partition
and say me that message
the partition is still in ext3
Click to expand...
Click to collapse
That's odd it worked for me ill do more digging to find a fix.
Sent from my Wildfire S A510e using Tapatalk 2
thank you man however there is a strange thing: in 4ext recovery (sd version i use) it see the partition as ext4, in partition magic for windows in ext3
djsolidsnake86 said:
thank you man however there is a strange thing: in 4ext recovery (sd version i use) it see the partition as ext4, in partition magic for windows in ext3
Click to expand...
Click to collapse
are you using any apps2sd or data2sd scripts?
First off, mods, if this is in the wrong place sorry, secondly, thanks for the help in advance.
I have dsixda's kitchen set up via cygwin, but do not have the proper files in the edify_defs folder so that the kitchen knows the proper mount points. What I am talking about is in the following bit quoted from the original kitchen thread.
WARNING: If your device is not listed in post #1 of this thread, and it does NOT use a 'YAFFS'-based filesystem (e.g. usually only low-end devices use YAFFS), do not attempt to flash a ROM that you built with this kitchen. Instead, you must do the following if your device is NOT listed:
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
NOTE: This method does not guarantee your device will work with your custom ROM, however. Some devices may require more steps than just the edify_defs file, but the procedure is outside the scope of this FAQ. Ask around in the XDA sub-forum for your device if you need further help.
Click to expand...
Click to collapse
The devices I would like to add are both the first gen Nexus 7 (nakasi/grouper) and second gen Nexus 7 (flo). When I follow the instructions from that quoted section I am unable to make sense of the listed mount points and how to create the proper files. Any help is appreciated, thanks!
Have u rooted???
Sent from my Micromax A30 using xda app-developers app
danger_beast said:
Have u rooted???
Sent from my Micromax A30 using xda app-developers app
Click to expand...
Click to collapse
Yes, going to sell the first gen N7, so just would like to add support for the 2nd gen (flo/razor).
dark2099 said:
Yes, going to sell the first gen N7, so just would like to add support for the 2nd gen (flo/razor).
Click to expand...
Click to collapse
would like to add support for LG-E510, I've tried many times, help
---------- Post added at 07:59 PM ---------- Previous post was at 07:38 PM ----------
here is my fstab file:
# Mount point fstype device [device2]
/ boot mtd boot
/ cache yaffs2 cache
/ data yaffs2 userdata
/ misc mtd misc
/ recovery mtd recovery
/ sdcard vfat / dev/block/mmcblk0p1 / dev/block/mmcblk0
/ system yaffs2 system
help me
danger_beast said:
Have u rooted???
Sent from my Micromax A30 using xda app-developers app
Click to expand...
Click to collapse
No one can help:good:
giltros1 said:
No one can help:good:
Click to expand...
Click to collapse
Mobile name?? version >> android
danger_beast said:
Mobile name?? version >> android
Click to expand...
Click to collapse
Mobile name: LG-E510, LG optimus Hub
Version android 2.3.6
Thanks
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
giltros1 said:
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Click to expand...
Click to collapse
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
So if u got the ro.product.device ID (can be found in build.prop its easy then follow the steps above.....)
This is my recovery.fstab
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
This is my recovery.fstab
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
giltros1 said:
This is my recovery.fstab
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Click to expand...
Click to collapse
Could u upload and pm me the files??
Could someone please help me with this recovery.fstab file for the hisense sero 7 lt tablet? It looks like the partitioning is messed up but im not completely sure. Im trying to make a partition file for android kitchen and thats why i need help with this recovery.fstab.
i cant attach the recovery.fstab so i'll copy and paste whats in it
recovery.fstab
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/boot mtd boot
/cache ext4 /dev/block/mtd/by-name/cache
/data ext4 /dev/block/mtd/by-name/userdata
/kernel mtd kernel
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mtd/by-name/user lun=/sys/class/android_usb/android0/f_mass_storage/lun/file
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 lun=/sys/class/android_usb/android0/f_mass_storage/lun1/file
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/mtd/by-name/system
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thank you for helping me!!
Well, I'm also in the progress of trying to figure this out, but try this:
get an ADB shell, or use a terminal app from the Play Store,
and execute:
Code:
cat /proc/mtd
That should give a list of partitions and their dev codes.
Tip: when posting files or code, try to make use of the code tags,
text inside them will be displayed with a monospaced font, so things will be more readable.
See more info here.
Thanks for the tip and I figured it out by using
cat /proc/partitions and cat /proc/mtd
Click to expand...
Click to collapse
those commands gave me the names of the partitions and what block number they are. Credit goes to Abdul_pt for giving me the partitions command credit goes to you hamc0re for helping me with the mtd command
Sent from my Amazon Otter2 using Tapatalk
So I did some exploring in the posted custom recovery by AnZhi. There was some discussion over which partitions could be accessed. There is an fstab file in there that can be modified which should allow access to other partitions...
Recovery.fstab
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
Looking further it seems this works by overwriting the files in /system/recovery. The process can't be that simple... can it?
Also there is a keys file with a bunch of cryptic hex codes....not quite sure what they're used for.... useful?
I'm a very experienced programmer, but new when it comes to android bootloader/recovery exploit development.
Any ideas guys? What can we learn by perusing this apk?
PS
Newbies.... To see the contents of an apk file just rename *.apk to *.zip and unzip it
I'm also new to bootloaders, we can probably pull a fstab from a rooted g3 and edit the existing one from there
I'm Also curious to see what's in the apk, I'll extract it to see if I can gather some more info
Sent from my VS985 4G using XDA Premium 4 mobile app