Can any one provide me with guidance as to how can i get ext2 / ext3 and loop mount support in my Xperia X10i
i have upgraded to baseband 54 and currently using a custom rom 2.2.1
I am kind of confused about this and have been searching the whole forum for past many days please help me.
is it possible to get these modules in kernel without bootloader crack if yes do anyone have them.
my ultilmate aim is to get a linux installed in a loop mount device where i can have my custom softwares...
Mod : if this is not the correct place, please shift it to correct place
Requires kernel support. Now possible right now.
Sent from my X10
I see people using debian / ubuntu on xperia x10...
so please help me if possible.
loop mount / ext2 / ext3 /ext4 what ever my task is i want ubuntu / debian on my andriod machine.
anantshri said:
I see people using debian / ubuntu on xperia x10...
so please help me if possible.
loop mount / ext2 / ext3 /ext4 what ever my task is i want ubuntu / debian on my andriod machine.
Click to expand...
Click to collapse
Yes its possible... that's how the freex10-alpha release had dual boot...
On phone right now... will post exact commands later...
sent from FreeX10_beta4+CM6 settings
anantshri said:
I see people using debian / ubuntu on xperia x10...
so please help me if possible.
loop mount / ext2 / ext3 /ext4 what ever my task is i want ubuntu / debian on my andriod machine.
Click to expand...
Click to collapse
the following is from the boot hijack file 'chargemon' in FreeX10-alpha (which was dual boot and was running off sdcard)...
Code:
# Mount system and data ext2 images
losetup /dev/block/loop1 /sd/FreeX10/system.img
sleep 5
losetup /dev/block/loop2 /sd/FreeX10/data.img
sleep 5
e2fsck -y /dev/block/loop1
e2fsck -y /dev/block/loop2
mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /system
sleep 5
mount -t ext2 -o rw,noatime,nodiratime,nosuid,nodev /dev/block/loop2 /data
sleep 5
thanks to zdzihu & jerpelea for their work on FreeX10...
always do a full backup by xrecovery/nandroid before proceeding and keep flashtool ready with the firmware files or ur choice before trying out wht u planned...
incase u need some help refer to http://forum.xda-developers.com/showthread.php?t=955703
anantshri said:
Can any one provide me with guidance as to how can i get ext2 / ext3 and loop mount support in my Xperia X10i
i have upgraded to baseband 54 and currently using a custom rom 2.2.1
I am kind of confused about this and have been searching the whole forum for past many days please help me.
is it possible to get these modules in kernel without bootloader crack if yes do anyone have them.
my ultilmate aim is to get a linux installed in a loop mount device where i can have my custom softwares...
Mod : if this is not the correct place, please shift it to correct place
Click to expand...
Click to collapse
something i found which might be useful... http://www.talkandroid.com/31994-installing-ubuntu-on-your-motorola-xoom-tablet/
Thanks a lot for the help DoomLord,,,, i am able to loopmount now..
the problem that i had was the ubuntu bootscript tried mounting on loop2 and i am using App2SD so loop2 was already booked.
finally customized script to use loop99 and now it works fine....
Related
{ LONG POST WARNING }
{ NOT FULLY WORKING YET}
{ NEEDS A LOT OF FURTHER DEVELOPMENT }
Hey everyone I had thought of making this Dual Booting system work along side recovery… because initially (with FreeX10-alpha) it was not possible to have both recovery & dual boot...
Thank you zdzihu & jerpelea for your great work on FreeX10-alpha, which booted off SDCARD… I got inspiration to try and make this work for FreeX10-beta4 based on the amazing work that u guys did! Thank you jerpelea for all your feedback on my repeated messages when I was testing this a few months back (hope I didn’t bother u too much with questions )...
zdzihu & jerpelea u are truly LEGENDS!!!
[This is just my personal opinion] Really hoping that some devs can take interest in this to provide compatible files (ramdisks, system files) for this to work… may be as an add-on to their main roms… please don’t keep bothering devs to create ramdisks for booting off SDCARD… they are already very busy trying to make our X10 better with faster and stable ROMS/MODS/etc… this is just an additional feature…
The basic idea was to use the chargemon booting scripts provided in FreeX10-alpha and to try and make FreeX10-beta4 to boot off SDCARD…
Initially I used the img files which came with FreeX10-alpha and wiped the image to then put FreeX10-beta4 on it… while doing so I realized that all of the symbolic links were not getting copied correctly (obviously)… so I started from scratch with blank ext2fs images…
Later I thought of using clean/base nandroid/recovery backups as they are already working/preconfigured system of FreeX10-beta4…
Following is a small How-To on converting NANDROID/RECOVERY images (with yaffs fs) to ext2 fs images keeping the symlinks intact!!
I have used Ubuntu for these steps.
I have attached blank_files.7z which contains precompiled ext2fs images:
system.img [size: 256 MB]
data.img [size: 512 MB]
cache.img [size: 128 MB]
To resize or create newer ext2fs images:
[APP] Windows: Create Your Own Data.img Maker Application, +/- From Existing data.img
U can use the commands provided there even in linux to create/resize these images...
We will keep the NANDROID images at:
Code:
/home/user/nandroid_imgs/test1/
and EXT2 FS images at:
Code:
/home/user/ext2fs_imgs/test1/
while temporary mounts points will be made at:
Code:
/home/user/mntpts/
We will be using unyaffs from here:
[How-To] Extracting/Accessing Recovery/Nandroid backup (.img) files
Extracting files from the nandroid/recovery backups:
Code:
cd /home/user/nandroid_imgs/test1
mv system.img /home/user/nandroid_imgs/test1/system/
cd /home/user/nandroid_imgs/test1/system/
sudo unyaffs system.img
mv system.img ../.
mv data.img /home/user/nandroid_imgs/test1/data/.
cd /home/user/nandroid_imgs/test1/data/
sudo unyaffs data.img
mv data.img ../.
mv cache.img /home/user/nandroid_imgs/test1/cache/
cd /home/user/nandroid_imgs/test1/cache/
sudo unyaffs cache.img
mv cache.img ../.
Loop mounting ext2 fs files:
Code:
sudo mount -t ext2 -o loop,rw,noatime,nodiratime /home/user/ext2fs_imgs/test1/system.img /home/user/mntpts/system/
sudo mount -t ext2 -o loop,rw,noatime,nodiratime,nosuid,nodev /home/user/ext2fs_imgs/test1/data.img /home/user/mntpts/data/
sudo mount -t ext2 -o loop,rw,noatime,nodiratime,nosuid,nodev /home/user/ext2fs_imgs/test1/cache.img /home/user/mntpts/cache/
Recursively copy all files (preserving symlinks) from extracted yaffs images to mount points
Code:
sudo cp -r -p /home/user/nandroid_imgs/test1/system/* /home/user/mntpts/system/.
sudo cp -r -p /home/user/nandroid_imgs/test1/data/* /home/user/mntpts/data/.
sudo cp -r -p /home/user/nandroid_imgs/test1/cache/* /home/user/mntpts/cache/.
Unmount the mounts:
Code:
sudo umount /home/user/mntpts/system/
sudo umount /home/user/mntpts/data/
sudo umount /home/user/mntpts/cache/
Ok now that the ext2fs iamges are populated with working files copy them onto SDCARD…
I have placed it at:
Code:
/sdcard/FreeX10
lets move on to the chargemon script...
This is, as of now, based off xRecovery chargemon (modified from FreeX10-alpha)
Code:
#!/system/bin/busybox sh
# modified chargemon for recovery + dual boot from NAND/SDCARD
/system/bin/charger
cat /dev/input/event2 > /dev/keycheck&
sleep 3
kill -9 $!
# intact recovery
if [ -s /dev/keycheck ]
then
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount MTDs
umount -l /data
umount -l /cache
# Extract recovery
cd /
rm -r /sbin
rm -f etc
tar -xf /system/bin/xrecovery.tar
# Umount system
umount -l /system
chroot / /init
fi
echo "check if reboot into SDCARD OS was called"
if [ -e /data/local/tmp/rebootsdcardos ]
then
echo "Booting from SDCARD!"
# FreeX10-alpha code follows with slight modifications!!!
# remount rootfs rw
mount -o remount,rw rootfs /
busybox chmod 0777 /dev -R
busybox chown 0.2000 /dev/oncrpc -R
rm -r /sdcard
cd /
mkdir sd
chmod 777 sd
rm init*
rm logo.rle
rm default.prop
tar -xf /system/bin/sdcardos_ramdisk.tar
# Umount system,data,cache
umount -l /system
umount -l /data
umount -l /cache
# Check and mount SD Card
dosfsck -y /dev/block/mmcblk0p1
sleep 5
mount -t vfat -o rw,noatime,nodiratime /dev/block/mmcblk0p1 /sd
sleep 5
# Mount system and data ext2 images
losetup /dev/block/loop1 /sd/FreeX10/system.img
sleep 5
losetup /dev/block/loop2 /sd/FreeX10/data.img
sleep 5
losetup /dev/block/loop3 /sd/FreeX10/cache.img
sleep 5
e2fsck -y /dev/block/loop1
e2fsck -y /dev/block/loop2
e2fsck -y /dev/block/loop3
mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /system
sleep 5
mount -t ext2 -o rw,noatime,nodiratime,nosuid,nodev /dev/block/loop2 /data
sleep 5
mount -t ext2 -o rw,noatime,nodiratime,nosuid,nodev /dev/block/loop3 /cache
sleep 5
# zdzihu: hack-fix
if [ -e /data/data/com.android.providers.telephony/databases/telephony.db ]; then
/system/bin/chroot / /init
exit
fi
# Chroot :)
chroot / /init
# jump out of chargemon to skip NAND booting
exit
fi
echo "Booting from NAND!"
# remount rw
mount -o remount,rw rootfs /
cd /
rm -r /sdcard
rm init*
rm logo.rle
rm default.prop
tar -xf /system/bin/ramdisk.tar
# zdzihu: hack-fix
if [ -e /data/data/com.android.providers.telephony/databases/telephony.db ]; then
/system/bin/chroot / /init
exit
fi
chroot / /init
Recovery is intact so u can get into recovery the normal way… (press/tap back key after seeing SE text logo)
OS on NAND (normal system on MTD) will boot by default…
To reboot into OS on SDCARD issue the following commands in terminal emulator/adb shell:
Code:
touch /data/local/tmp/rebootsdcardos
reboot
NOW the OS should start booting off the SDCARD…
It completes commands in chargemon and then BootAnimation can be seen…
BUT HERE IS THE PROBLEM!
Check LOGCAT here: http://www.mediafire.com/?phxm3uqzp0dzzhb
here is wht J had to say:
jerpelea said:
as you can see in logcat
1.your prelink is not ok
2.you don't have something ok in initrd
3.you dont have all permisions ok on data
Click to expand...
Click to collapse
From my limited understanding we yet have to make a proper ramdisk (sdcardos_ramdisk.tar)… I feel the init.rc file has to be changed especially the following line (based off FreeX10-beta4 ramdisk):
Code:
mount yaffs2 [email protected] /system rw remount
mount yaffs2 [email protected] /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
As for Multi-Booting:
We can keep adding different sections to chargmeon:
Code:
/data/local/tmp/rebootsdcardos1
/data/local/tmp/rebootsdcardos2
etc…
OR
possible solution for having both recovery and dual boot
and similarly keep adding ramdisks in NAND /system:
Code:
sdcardos1_ramdisk.tar
sdcardos2_ramdisk.tar
etc
So we can have as many OS/ROMs on SDCARD as u have free space… though we need to make specific ramdisks for each…
Hope this was slightly useful… and waiting for feedback from advance users on how we can get this working....
Lol, you're working very hard Doom! Keep going!
Doom! You are making enormous progress and helping a lot with Other Devs.
A Combination of a good rom and one of these additional Dual Boot would make x10 better than any Android mobile SE could deliver.
Thank you and I really pray to give SE a run for their money!
for someone thats always saying hes not a developer you sure as hell seem to know what your doing!
Keep up the great work, i hope to see this working flawlessly that would be awesome to be able to dual boot.
Whats the next steps in the project?
BULL3TPR00F said:
for someone thats always saying hes not a developer you sure as hell seem to know what your doing!
Keep up the great work, i hope to see this working flawlessly that would be awesome to be able to dual boot.
Whats the next steps in the project?
Click to expand...
Click to collapse
well i am not exactly a ROM developer and dont know much about how to compile libs/sources/etc...
next step is that we need to make compatible system files & ramdisk (init.rc) for dual booting
DooMLoRD said:
well i am not exactly a ROM developer and dont know much about how to compile libs/sources/etc...
next step is that we need to make compatible system files & ramdisk (init.rc) for dual booting
Click to expand...
Click to collapse
You may not be a rom developer but your an amazing commited x10 modder
Sent from my X10i TripNMiUI using XDA App
DooMLoRD said:
well i am not exactly a ROM developer and dont know much about how to compile libs/sources/etc...
next step is that we need to make compatible system files & ramdisk (init.rc) for dual booting
Click to expand...
Click to collapse
I am also excited buddy..... Once i get through my experiments i will surely like to focus on this as this will allow us to have more then one version of ROM on one machine.
Based on your first post
all i can get is we are getting the boot animation but not going after that.
i would suggest following things based on my experiments with ubuntu work.
use loops above 10 coz i suspect some loops are already in use during my ubuntu boot i am watching that loop7 is already created so i would suggest avoiding it.
also as we have been adding debug "we have reached here" style code can we do the same here that might help us.
also can we find any debug-able place i mean place where we can track the progress to get the position inside the rom so that we can understand except logcat where we are.
any progress or hurdles buddy.....
i am eager to test this .....
anantshri said:
any progress or hurdles buddy.....
i am eager to test this .....
Click to expand...
Click to collapse
sorry man havent had time to do any further testing for this... have been very busy with some personal work and kernel manager scripts...
DooMLoRD said:
sorry man havent had time to do any further testing for this... have been very busy with some personal work and kernel manager scripts...
Click to expand...
Click to collapse
Keep up the good Work Doom. ! and thx for your work
Sorry if its no help but there's a thread in the x10 mini pro section
http://forum.xda-developers.com/showthread.php?t=1084555
Sent from my SEX10 using XDA App
These are great news, keep on developing!
sent from my x10i with wolfbreaks CM 6.1.3 v006 undervolted, bb67
rtblittlebrown said:
Sorry if its no help but there's a thread in the x10 mini pro section
http://forum.xda-developers.com/showthread.php?t=1084555
Sent from my SEX10 using XDA App
Click to expand...
Click to collapse
they have posted exactly the same thing!
read my 1st post in this thread and then read the first few posts there
Ohk so since we now have one more option in Xrecovery i am back to my old suggestion.
however this time i will post my thought out in open so that if someone has required skills and time then they can work on .
I have an idea of using xrecovery as a boot menu.
process would be
1) Xrecovery to start everytime. (this needs some consideration.)
2) To have a timeout value if any key pressed before that then remain in menu otherwise boot to the os.
3) inside menu we should have options of all O.S. / ROM (os coz my intention are to run linux off dualboot) available with selection options.
4) ON selection it will just be the same procedure as already using in xrecovery 1.0 to handover the command to a script. and let it load.
5) boot menu if possible could be controlled by an outside file which we can edit just like grub.conf in linux.
Note : This will requires good understanding of booting process of X10i and c skills as xrecovery is written in complete c.
anantshri said:
Ohk so since we now have one more option in Xrecovery i am back to my old suggestion.
however this time i will post my thought out in open so that if someone has required skills and time then they can work on .
I have an idea of using xrecovery as a boot menu.
process would be
1) Xrecovery to start everytime. (this needs some consideration.)
2) To have a timeout value if any key pressed before that then remain in menu otherwise boot to the os.
3) inside menu we should have options of all O.S. / ROM (os coz my intention are to run linux off dualboot) available with selection options.
4) ON selection it will just be the same procedure as already using in xrecovery 1.0 to handover the command to a script. and let it load.
5) boot menu if possible could be controlled by an outside file which we can edit just like grub.conf in linux.
Note : This will requires good understanding of booting process of X10i and c skills as xrecovery is written in complete c.
Click to expand...
Click to collapse
point no.1 is easy... not an issue..
abt point 2 i think that too would be possible... a while loop with sleep function & wait for input/keppress
pt3 the newer xrecovery v1.0.0 already has something similar may be we can look into it to add "Boot NAND system" as first option
point no. 5 if possible WILL BE BRILLIANT!!!
@anantshri
dude may be these guys can help us:
http://forum.xda-developers.com/showpost.php?p=14354231&postcount=49
DooMLoRD said:
they have posted exactly the same thing!
read my 1st post in this thread and then read the first few posts there
Click to expand...
Click to collapse
Oops sorry..
Sent from my SEX10 using XDA App
rtblittlebrown said:
Oops sorry..
Sent from my SEX10 using XDA App
Click to expand...
Click to collapse
no dude thanks for the info... i have already contacted those guys for help... lets see may be they can help us out to get this working!!!
dual boot hint by Z
http://forum.xda-developers.com/showthread.php?t=1107111
something related
=================== GOOD NEWS ================
Thanks to GORO and Z we have a solution
tkymgr said:
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
Click to expand...
Click to collapse
Step by step guide
http://forum.xda-developers.com/showpost.php?p=16853029&postcount=39
thanks to waigsr
for those looking to see the technical aspects of it.
SE sample zip contains a vold replacement from cm7 which actually do the magic of making sure that first partition gets mounted.
Note : as Link2SD messes with install-recovery.sh its adviced that after flashing this zip port any specific tweak you have in install-recovery.sh over to install-recovery2.sh in the same folder.
and then run link2SD
Hope this helps.
-============== Keeping old study for later reference and memories only ==============
I have been messing around with Link2SD and its config here is a short writeup for those who want to help.
The basic problem
Link2SD looks for a partition no of /sdcard +1 partition
Android has a habbit of mounting the last partition as /sdcard
so link2sd is going to fail in all senses.
however if anything is mounting at /data/sdext2 Link2sd condsider it as a second partition
so we still have hope of using it however there are several limitations of it.
multiple ways in which link2sd could be used.
1) create 2 partitions on sdcard
a) ext2 partition as mmcblk0p1
b) vfat partition as mmcblk0p2
entry in install-recovery.sh
mount -t ext2 /dev/block/mmcblk0p1 /data/sdext2
Cons : xrecovery can't mount sdcard as its mmcblk0p1 that xrecovery mounts
2) create 2 vfat partitions
a) mmcblk0p1 mounting itself at /data/sdext2
b) mmcblk0p2 mounting itself as /sdcard
cons recovery related files will go in /data/sdext2
3) three partition layout
a) mmcblk0p1 -> reserverd for recovery related stuff
b) mmcblk0p2 -> link2sd
c) mmcblk0p3 -> SDCARD
or find an alternative to use mmcblk0p1 as /sdcard
or use a loop file as /data/sdext2
Do suggest what you all think and how should we proceed.
-=======reserved==========
and u sure this doesnt break recovery?
ok now that i read the post carefully i understand that it WILL BREAK recovery
DooMLoRD said:
and u sure this doesnt break recovery?
ok now that i read the post carefully i understand that it WILL BREAK recovery
Click to expand...
Click to collapse
cons highlighted to avoid confusion.
any idea how we can get this piece to work.
BTW why do we need it when we have app2sd ?
How's it better ?
anantshri said:
cons highlighted to avoid confusion.
any idea how we can get this piece to work.
Click to expand...
Click to collapse
keep only one FAT32 partition...
modify the recovery ramdisk to mount that partition to /sdcard
DooMLoRD said:
keep only one FAT32 partition...
modify the recovery ramdisk to mount that partition to /sdcard
Click to expand...
Click to collapse
that could be done
however there is one more issue which i found just now
SDCARD can't be mounted to PC till both partitions are umounted and that won't be done automatically so we need alternative for sdcard umounting also
something like a gscript code for umounting /data/sdext2 before attempting sdcard mount to pc
the new vold introduced in froyo causes this issue
Adolf1994 said:
the new vold introduced in froyo causes this issue
Click to expand...
Click to collapse
the default vold.fstab listing is
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
some stuff online suggests that i can specify a partition number manually.
however
Code:
dev_mount sdcard /mnt/sdcard [B]1[/B] /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
when i am trying this it barks out and not even mounts sdcard.
With the sdcard parted in 3 partitions, I tried to make the third partition recognized by my pc, and I tried an application named multimount sd or something like that and it worked for me. You can found it in the market. With it, the pc can recognize the third partition not the first. Maybe that will help in your project.
Sent from my X10i
i meant the vold binary/system, not the fstab config
Adolf1994 said:
i meant the vold binary/system, not the fstab config
Click to expand...
Click to collapse
can you point me to the correct code for this.
fat32 is first partition
ext2 is second partition
vold.fstab
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
this will mount fat32 partition
dev_mount ext2 /mnt/sdcard 1 or 2 /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
should mount ext2 for link2sd
the vold from 2.1 works well as you can see and if you'd have googled it, then you'd know there is a revised version of vold in 2.2+
How about instead bind mounting a folder on /system as /data/sdext2 did this for ages on 2.1 to get more space for apps without probs. Obviously /system has to be mounted rw which isn't a prob for me and at least on stock there's loads of free space there which is a shame to waste.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o bind /system/app2 /data/sdext2
Think the folders need to be created first.
patch for using link2sd
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
aZuZu said:
fat32 is first partition
ext2 is second partition
vold.fstab
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
this will mount fat32 partition
dev_mount ext2 /mnt/sdcard 1 or 2 /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
should mount ext2 for link2sd
Click to expand...
Click to collapse
I also assumed something like this however android seems to be needing a last partition as vfat and that vfat is mounted as sdcard or nothing is mounted.
shaunbu said:
How about instead bind mounting a folder on /system as /data/sdext2 did this for ages on 2.1 to get more space for apps without probs. Obviously /system has to be mounted rw which isn't a prob for me and at least on stock there's loads of free space there which is a shame to waste.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o bind /system/app2 /data/sdext2
Think the folders need to be created first.
Click to expand...
Click to collapse
for you i recommand checking http://forum.xda-developers.com/showthread.php?t=1206149 and also system being rw all the time is not at all a good idea.
tkymgr said:
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
Click to expand...
Click to collapse
Thanks buddy will check it as soon as possible ...rightnow my sdcard is not mounting nomatter what setting i do thinking of flashing CM7 and will see how it goes from there.
Note : just checked the zip i think SE stock needed a relacement at vold. will just flash the vold and see if it works.
tkymgr said:
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
Click to expand...
Click to collapse
Thanks buddy. I can confirm the SE 2.3.3 sample zip worked. I flashed the zip, turned off my x10, partitioned the sd on my pc using fat32 & ext32, powered on and DID NOT get previous error of sd not recognized on startup. It mounted fat32 partition and link2sd recognized ext2 partition right away. Selected ext type, rebooted again and I've moved apps that I wanted to the sd card. Rebooted a couple more times and apps are still linked and running fine. Time will tell if any apps will have issues or any tweaks on this rom will be affected. Using WBs v3.9 custom GB and I'll report again later.
Again thank you to everyone's efforts and for not giving up on this old feature.
Edit: Forgot to mention I can still enter xrecovery manually and using the xperia reboot app.
tkymgr said:
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
Click to expand...
Click to collapse
confirmed working
Post updated with details......
Please, note, that everything you had previously added to install-recovery.sh, is now renamed into install-recovery.sh.ori. So, if you want it back, working, you need to rename/copy to install-recovery2.sh
Hello,
I promise I tried to find an answer before posting, but without success.
I can't mount a Ext3 USB device. Nothing happen. I tried with :
- VFAT => OK
- NTFS => OK
- Ext3 => NOK
- Ext4 => NOK
I don't believe that a Linux based Kernel was unable to manage Ext3 FS.
I also tried apps like "Drive Mount" and Mount Manager". Nothing.
I think it's a stupid thing I don't understand but ...
Others tests :
When I plug the USB device, in the kernel log (dmesg) I have :
usb-storage [...]
sda : sda1
[..]
VFS : Can't find a valid FAT filesystem on dev sda1
[...] Not an NTFS volume
It seems to be impossible but when I try :
dmesg | grep ext3
or
lsmod | grep ext3
I obtain nothing. Does the ext3 support is present in this kernel (2.6.39.4) ?
[UPDATE]
It seems that the kernel is ok, I have CONFIG_EXT<2,3,4>_FS to y in the /proc/config.gz
So, ... I really don't know I can't plug a Ext3 device
Note :
- Android 3.2.1 update to 4.0.3 : Same problem
- The system is rooted.
Thanks a lot !
A little Up
Hi SLEA_Bourges,
I got MK802 with android 4.0, I had the same problem like you, I tried searching and I bumped into your post, and later I found the solution, so here is what I did:
ssh into your android, I'm using SSHDroid
track your connected device by dmesg, mine was sda1.
then do:
mkdir /mnt/test/
mount -o loop /dev/block/sda1 /mnt/test/
ls /mnt/test/
Arena.mkv lost+found
you need to chmod /mnt/test/ so it can be readable from your browsers.
regards
Bash
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?
Hello All,
I hope I am in the good plce to post.
Well I start to play with my android tablet (oem tablet base on imx53 from Freescale).
I made a very simple things, add the capability to mount my second SD partition (ext2 in my case).
Before this problem I was in Android 2.3.4, and I made this (I am rooted):
Code:
# mkdir /mnt/sdcard2
# mount -o rw -t ext2 /dev/block/mmcblk1p2 /mnt/sdcard2
it was perfect!
This morning I upgrade to android 4.0.4 (rooted also)
And surprise, my simple command to mount the partion was not working!
Why?
Because I haven't dev/block/mmcblk1p2, but /dev/block/09:45 mmcblk1p2 !
in fact all files have a time stamp like that.
The time stamp change each time I boot my tablet..
So what's that kinde of **** ??
Hope somebody can explain, because I search on google and found nothing about that!
Thanks
Emmanuel