[DEV] Multiboot Menu - Sony Ericsson XPERIA X10 Mini

Hey devs, owain got a nice Dualboot Script, I modded it, added some lines and fixed some wrong ones, here it is:
IF YOU WANT TO MAKE ANY CHANGE, PLEASE CLICK ON MAKE A NEW VERSION OF THIS PASTE!
Recovery sucessfully modded, chargemon still bad...
And there's where we need help, thanks to everyone of you devs , tip, take a look @ xrecovery sources here, Thanks to zdzihu, im looking into that..
THIS IS A DEV THREAD PLEASE DON'T SPAM HERE

This will be good.. we can make it like reboot to xrec! and maybe we can try porting windows ME 6.0 or something! or maybe two ROM.. and final Question... Does this script really work.. means i really don't find problem in it.. but still asking!

newtron_b1 said:
This will be good.. we can make it like reboot to xrec! and maybe we can try porting windows ME 6.0 or something! or maybe two ROM.. and final Question... Does this script really work.. means i really don't find problem in it.. but still asking!
Click to expand...
Click to collapse
Im sorry, this is a dev related post, as you can see on [DEV] tag, but anyway, Script should work not tested yet, and windows mobile port it's almost impossible, this is made to dual boot 2 android roms

Hell yeah! can't wait for Multiboot.
so Froyo, and Gingerbread at the same time will be possible some times?

Quote myself:
THIS IS A DEV THREAD PLEASE DON'T SPAM HERE
Click to expand...
Click to collapse
And please don't reply saying im sorry... cuz that's spam no offends to nobody ofc
so Froyo, and Gingerbread at the same time will be possible some times? -> Yes, but dont ask more, this is a dev thread, if we got it we're gonna change [DEV] to script o whatever
btw: good night need 2 sleep some
DEV INFO: Discovered a way to make it but without interface, tomorrow will post more info

D4rKn3sSyS said:
Im sorry, this is a dev related post, as you can see on [DEV] tag, but anyway, Script should work not tested yet, and windows mobile port it's almost impossible, this is made to dual boot 2 android roms
Click to expand...
Click to collapse
uhm hell yeah it is tested
!for DEV's only (and people that know what they are doing)!
to make the images that are placed on the sdcard
make 3 ext2fs images
system.img size: 256 MB
data.img size: 512 MB
cache.img size: 256 MB
you van make them bigger or smaller but i recommand this sizes
make an NANDROID backup from the rom that you want on the sdcard
FACTORY RESET FIRST! THEN BACKUP!!!!!!!
user in the next lines is ofc your username
put the NANDROID images at /home/user/nandroid/dualboot/
and put the ext2fs images at /home/user/ext2fs/dualboot/
and make this dir /home/user/mountpoints/
now run all these lines!
you will need unyaffs on our pc!
Code:
sudo su
mv system.img /home/user/nandroid/dualboot/system/
cd /home/user/nandroid/dualboot/system/
unyaffs system.img
mv system.img ../.
mv data.img /home/user/nandroid/dualboot/data/
cd /home/user/nandroid/dualboot/data/
unyaffs data.img
mv data.img ../.
mv cache.img /home/user/nandroid/dualboot/cache/
cd /home/user/nandroid/dualboot/cache/
unyaffs cache.img
mv cache.img ../.
mount -t ext2 -o loop,rw,noatime,nodiratime /home/user/ext2fs/dualboot/system.img /home/user/mntpts/system/
mount -t ext2 -o loop,rw,noatime,nodiratime,nosuid,nodev /home/user/ext2fs/dualboot/data.img /home/user/mntpts/data/
mount -t ext2 -o loop,rw,noatime,nodiratime,nosuid,nodev /home/user/ext2fs/dualboot/cache.img /home/user/mntpts/cache/
cp -r -p /home/user/nandroid/dualboot/system/* /home/user/mntpts/system/
cp -r -p /home/user/nandroid/dualboot/data/* /home/user/mntpts/data/
cp -r -p /home/user/nandroid/dualboot/cache/* /home/user/mntpts/cache/
umount /home/user/mntpts/system/
umount /home/user/mntpts/data/
umount /home/user/mntpts/cache/
now all your information is in the ext2fs (damn i hate to type ext2fs -.-'')
extract the ramdisk from the rom that u want for dual boot rename it to "sdcardos1-ramdisk.tar"
and push it into the /system/bin from the rom you want to have on NAND! (so not the rom you just bakupped that would be silly nand and second the same ROM xD)
and chmod it to 0777
now when you want to try it
just do this in adb shell or mobiel terminal
Code:
touch /data/local/tmp/sdcardOS1
reboot

owain94 said:
uhm hell yeah it is tested
!for DEV's only (and people that know what they are doing)!
to make the images that are placed on the sdcard
make 3 ext2fs images
system.img size: 256 MB
data.img size: 512 MB
cache.img size: 256 MB
you van make them bigger or smaller but i recommand this sizes
make an NANDROID backup from the rom that you want on the sdcard
FACTORY RESET FIRST! THEN BACKUP!!!!!!!
user in the next lines is ofc your username
put the NANDROID images at /home/user/nandroid/dualboot/
and put the ext2fs images at /home/user/ext2fs/dualboot/
and make this dir /home/user/mountpoints/
now run all these lines!
you will need unyaffs on our pc!
Code:
sudo su
mv system.img /home/user/nandroid/dualboot/system/
cd /home/user/nandroid/dualboot/system/
unyaffs system.img
mv system.img ../.
mv data.img /home/user/nandroid/dualboot/data/
cd /home/user/nandroid/dualboot/data/
unyaffs data.img
mv data.img ../.
mv cache.img /home/user/nandroid/dualboot/cache/
cd /home/user/nandroid/dualboot/cache/
unyaffs cache.img
mv cache.img ../.
mount -t ext2 -o loop,rw,noatime,nodiratime /home/user/ext2fs/dualboot/system.img /home/user/mntpts/system/
mount -t ext2 -o loop,rw,noatime,nodiratime,nosuid,nodev /home/user/ext2fs/dualboot/data.img /home/user/mntpts/data/
mount -t ext2 -o loop,rw,noatime,nodiratime,nosuid,nodev /home/user/ext2fs/dualboot/cache.img /home/user/mntpts/cache/
cp -r -p /home/user/nandroid/dualboot/system/* /home/user/mntpts/system/
cp -r -p /home/user/nandroid/dualboot/data/* /home/user/mntpts/data/
cp -r -p /home/user/nandroid/dualboot/cache/* /home/user/mntpts/cache/
umount /home/user/mntpts/system/
umount /home/user/mntpts/data/
umount /home/user/mntpts/cache/
Click to expand...
Click to collapse
Owain discovered a easy coded way.. if a=1 open os1, if a=2, open os2, if a=3 mount xrecovery, if a=4 **** mount sdcard, being "a" any **** we could make ... next step user interface
good night owain, see ya 2moro, my eyes hurt need 2 sleep

D4rKn3sSyS said:
Owain discovered a easy coded way.. if a=1 open os1, if a=2, open os2, if a=3 mount xrecovery, if a=4 **** mount sdcard, being "a" any **** we could make ... next step user interface
good night owain, see ya 2moro, my eyes hurt need 2 sleep
Click to expand...
Click to collapse
edited post btw just that you know
and yeah why make it hard when we can keep it simple right
with the sizes i recommand the os wil be 1GB in size...
you can also try
system 128 MB
data 256 MB
cache 128 MB
then the size will be 512MB
but yeah sorry this is not only a ROM
the data and cache img's are empty when u download them but still this size
just don't complain about it or find a way yourself
@d4 good night bro
EDIT: michael (A.K.A MikevHL) got an boot menu for the milestone 2 he can probz help us

owain94 said:
edited post btw just that you know
and yeah why make it hard when we can keep it simple right
with the sizes i recommand the os wil be 1GB in size...
you can also try
system 128 MB
data 256 MB
cache 128 MB
then the size will be 512MB
but yeah sorry this is not only a ROM
the data and cache img's are empty when u download them but still this size
just don't complain about it or find a way yourself
@d4 good night bro
EDIT: michael (A.K.A MikevHL) got an boot menu for the milestone 2 he can probz help us
Click to expand...
Click to collapse
Nice, let's ask MikevHL.. and btw, the linux thing post, it's for linux... dont try it on another os ¬_¬" its obvious no ?.
This is because some people dont read and just do things... no offends to nobody

Lyk we can have 3 partitions on memory card, alter xRecovery to install update.zip which can be any rom running over the default rom, while the default rom is still in background, something lyk they did on cellfone running symbian n windows 7, while symbian being running in background...
p.s. I'm not talking about WP7 but Windows 7,
i dont want to question legendry zdzihu, but can u provide me the source code of xRecovery...

galvic said:
Lyk we can have 3 partitions on memory card, alter xRecovery to install update.zip which can be any rom running over the default rom, while the default rom is still in background, something lyk they did on cellfone running symbian n windows 7, while symbian being running in background...
p.s. I'm not talking about WP7 but Windows 7,
i dont want to question legendry zdzihu, but can u provide me the source code of xRecovery...
Click to expand...
Click to collapse
we just use 1 partition
and 1 os at the time
we got not enough RAM for running 2 roms
take a look at XDANDROID on windows 6.1-6.5 phones
not the NAND version of XDANDROID btw
it is damn slow coz windows mobile 6 is running in the background and android on the foreground

Hey owain i was thinking.. and what if we do a apk?, slade and me are good @ java, and im sure you too
Edit:
Got another fast idea
Can chargemon load another files?, if yes, we can do this
chargemon:
if a=1, load script os1
if a=2, load script os2
if a=3, load script xrecovery unified
if a=4, mount SD
and then we can do a java interface (Apk ?)

That's a nice approach, but I'm afraid loop devices will make the device considerably slower. Got two questions:
- How long does it take to boot?
- What's the performance overhead (e.g. some benchmark results)?
Other than that, I see no reason why this wouldn't work.

D4rKn3sSyS said:
Hey owain i was thinking.. and what if we do a apk?, slade and me are good @ java, and im sure you too
Edit:
Got another fast idea
Can chargemon load another files?, if yes, we can do this
chargemon:
if a=1, load script os1
if a=2, load script os2
if a=3, load script xrecovery unified
if a=4, mount SD
and then we can do a java interface (Apk ?)
Click to expand...
Click to collapse
why not just add it in reboot menu
and we can add as many entries as we want
nobodyAtall said:
That's a nice approach, but I'm afraid loop devices will make the device considerably slower. Got two questions:
- How long does it take to boot?
- What's the performance overhead (e.g. some benchmark results)?
Other than that, I see no reason why this wouldn't work.
Click to expand...
Click to collapse
when i got my mimmi back i will try to improve the script
boot time i can't tell you sorry
i used another script with sleep 5 everytime and a complete ext2fs check
to be sure my images were not broken or something
when my mimmi is back from repair i will try new script and report back to you
about the performance
well not that bad! it was a bit slower then stock i must say did not benchmark it but it felt like it was nto that much slower
again when i got my device back will report also a benchmark score back to you

owain94 said:
we just use 1 partition
and 1 os at the time
we got not enough RAM for running 2 roms
take a look at XDANDROID on windows 6.1-6.5 phones
not the NAND version of XDANDROID btw
it is damn slow coz windows mobile 6 is running in the background and android on the foreground
Click to expand...
Click to collapse
Yeah you're absolutely right it'll make the device slow, but if we are able to freeze the ROM running in background while the one running in foreground gets full access to RAM... Do you think it'll work it out? Or just burn this background- foreground thing?

Well i did some research and found out that device is called Fujitsu LOOX-F07C, has 1.2 ghz intel atom, nd 1 gb ram,
i got an idea how about creating a virtual machine? Thats able to load other OS? Virtual machine can be .apk,
well it'll need RAM lots of it, theres no way it'll work on stock, but legendary owain your ROM might be able to do it, i hope mighty d4rk can add his skills nd knowledge, shoult i try develop such vritual machine?

galvic said:
Well i did some research and found out that device is called Fujitsu LOOX-F07C, has 1.2 ghz intel atom, nd 1 gb ram,
i got an idea how about creating a virtual machine? Thats able to load other OS? Virtual machine can be .apk,
well it'll need RAM lots of it, theres no way it'll work on stock, but legendary owain your ROM might be able to do it, i hope mighty d4rk can add his skills nd knowledge, shoult i try develop such vritual machine?
Click to expand...
Click to collapse
Hard, loop device it's easier
Recently got this from zdzihu:
Hi D4rKn3sSyS,
ClockWorkMod recovery (which xRec bases on) is quite big project and I'm not 100% familiar with all the code Maybe looking into stock Android recovery could shed some light on "how it's made"? As far as I remember it was much much simplier to catch on.
Cheers,
z
Click to expand...
Click to collapse

I know a little that you can do(not in this code, but a algorithm), but my english is SO horrible, anyone dev here speaks portuguese? T.T

Carcass.br said:
I know a little that you can do(not in this code, but a algorithm), but my english is SO horrible, anyone dev here speaks portuguese? T.T
Click to expand...
Click to collapse
Give us a idea, im not native english speaker, i speak spanish, but im sure somebody will got you idea

So, I'll start at the point that i understand here...
You guys are trying to load 2 roms for after this the user can choose what rom he wants?
First i guess that you will really need a extra partition, not in the way that you REALLY NEED, but for a bit that i understand of android system a extra partition will be more easy to work...
So, you can have a system based on XOR not a case option, for a case option (you'll need to have all "OS's" read to be choose). If someone have patience to explain me how the chargemon works I can help you, a while ago I was trying to learn these things, but no one supports me(and all content that I found was in english or in other languages :s), i'm graduate in computer science and don't know so much about kernel of android, if some one explain me, i can help you more with codes, because my english is REALLY horrible, i really don't understand too much of english, is really hard to me try to explain something in a language that i don't understand...

Related

[Q] Questions on the custom boot and system.ext2 images

I read in the bootloader development thread that it'd reached a level where it could almost boot into a custom system image stored on the SD card. Some questions about that:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Thanks
ddewbofh said:
1. The creation of that image, is it similar to how it's done for use with the XDAndroid project? (The porting of Android to HTC WinMo devices)
Click to expand...
Click to collapse
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
ddewbofh said:
2. Is there a way to avoid having to reflash the device after every attempt? It looks like the boot-scripts take control pretty early in the process so having a choice if you want to proceed would be awesome, especially since I can't figure out how to get hold of a bootlog.
Click to expand...
Click to collapse
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
zdzihu said:
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
ddewbofh said:
I've tried hammering all the keys without any success, since it works for you maybe I'm doing it at the wrong time. Where in the boot process do you do it?
Click to expand...
Click to collapse
Bash them for a while as soon as you see SE logo appearing
ddewbofh said:
And thanks for the tip about the image, didn't want to risk messing something up since I had to reflash after every try.
Click to expand...
Click to collapse
Make sure you either name your image rootfs.img (not .ext2) or edit the init in the ramdisk accordingly.
Cheers
Thanks, that should make things much, much easier.
zdzihu said:
I have no clue how they do it for XDAndroid, but here's how I created mine:
dd if=/dev/zero of=rootfs.ext2 bs=1M count=512 (for 512Mb fixed size)
mkfs.ext2 rootfs.ext2 (press y to accept)
mount somewhere
copy your stuff into
umount
You don't need to re/flash at all. Pressing any key during the bootup will cancel the script and get you back into old good SE's 1.6
Click to expand...
Click to collapse
is there different form flash?
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
ddewbofh said:
I've figured out why my phone refuses to go back to normal after testing the chroot. It needs grep and the standard sh doesn't provide it nor is there a grep symlink/binary in /system/bin so I'll add those manually.
Anyways, if anyone has a script or something to do all this it would be very helpful. I'm not looking forward to going over tons of symlinks manually.
Click to expand...
Click to collapse
How about busybox --install -s /your_destination_dir ?
zdzihu said:
How about busybox --install -s /your_destination_dir ?
Click to expand...
Click to collapse
Awesome, thanks. My knowledge about busybox is limited at best so when I saw install listed as a busybox function I assumed it was the "normal" install command.
In the quest for finding a way to use custom kernels I'm playing around with the splboot module but I need to find a way to get hold of dmesg or kmsg from failed attempts. Is there a reliable way to get any of these logs?
I've tried adding a line in the mount_iso script which cats kmsg to a file right before executing the splboot but I'm seeing nothing that would indicate that I'm running anything but the stock kernel.
Any ideas?

[REF] How to boot your SD build from magldr [quick guide]

This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Tip from aled99 to edit without linux.
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
Some files that are already edited:
CoreDroid HD 0.4 edited by ricola7
Desire_hd2 system.ext2 file
HD2ONE 0.3.5 system.ext2
JDMS 1.62
MDJ HD v4.6
MDJ rEVOlution 2.3 rootfs.img
NexusHD2-FRG83D v1.8 from nzxtneo
Superram 1.5 from letama
Builds that already work with magldr:
DL DesireZ v2.2 from dandiest
HD2 Gingerbread/CyanogenMod7 from copenhagen
Is this a method to boot a NAND Rom from SD Card without flashing?
blax123 said:
Is this a method to boot a NAND Rom from SD Card without flashing?
Click to expand...
Click to collapse
No it boots the sd builds from this subforum. Not the nand builds.
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
izzy spun said:
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
Click to expand...
Click to collapse
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
buzz killington said:
This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Click to expand...
Click to collapse
thanks.. so i must use linux? any tools available in win?
buzz killington said:
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Click to expand...
Click to collapse
can you elaborate on this please.
can you give a step by step.
i am real interested in trying this.
thanks in advance.
Anthonayy said:
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
Click to expand...
Click to collapse
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
vista1984 said:
thanks.. so i must use linux? any tools available in win?
Click to expand...
Click to collapse
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
WOOZ!E said:
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Dude, it has nothing to do with WP7, You boot Android from MAGLDR not WP7. So you would either use a different SD card to boot into Android BEFORE booting windows or you would partition your SD card in a way that it allows you to use it for WP7 and Android at same time.
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
asdfg2010 said:
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
Click to expand...
Click to collapse
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
buzz killington said:
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
Click to expand...
Click to collapse
I try but not successful
windows ext2 editing
buzz killington said:
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Click to expand...
Click to collapse
I think you can edit an ext2 image with windows using the method in post #4 from this thread: http://forum.xda-developers.com/showthread.php?t=808169
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
I've tried editing the file and it seemed to save the changes, but I haven't tried booting android yet.
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
can anyone uploade the files? i dont have linux..
Cool, thanks! I seems to be working for me with MDJ FroYo HD v4.6. Has anyone had any success getting two Android ROMs running from their microSD card? I was doing this when booting from WM6.5 by putting them in different directories and modifying rel_path in the startup.txt for one of them, but obviously this method won't work until MAGLDR supports startup.txt...
clio94 said:
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
I didn't do the superram built myself, but letama posted a full version later in that magldr thread. Try to see if you can find it. If not I'm sure I still have it somewhere I can post it for you.
You can change Android folder on SD using MAGLDR
Enter Magldr
Select 9. Services
then 1. BootSettings
then 3. AD SD Dir

[TUT] Android 2.2 on SD card (OUTDATED)

I made it for all of you who prefer to have their Android to be installed on SD card.
What do we need:
SD card with ext2 as a second partition (I believe that most of you know how to use gparted or any other linux partition manager)
filesystem: http://www.2shared.com/file/8p5Ci18r/SDAndroid.html
fota (the same as in Shodow's tut, so if you have this, there is no need to reflash it)
Step 1
Unzip downloaded filesystem.
Step 2a
Copy the "galaxyboot" folder into internal memory of your phone (or, as Shadow named it "Bada root").
Step2b
Copy the content of "filesystem" folder into ext2 partition on your card.
Step3
Open the terminal in this directory and type:
sudo chmod -R 0777 ./*
sudo sync
Step4
Unplug your sd card and boot by pressing start call button + on/off button.
Of course, all those steps must be done under Linux.
For those who do not have custom fota flashed:
Step5
Under Windows open Multiloader, select LSI, serach for fota and download it to your phone.
This is mixed version of first version of Android port and the filesystem posted by mylove90. It provides all functions which the newest version of Android from Shadow's tutorial has.
Great thanks to Bedson from bada-os.info for keeping all the old files.
Would this port still have "easy crash" after several reboot?
*yet again mumbles something about the annoyances of more than one tutorial*
part of the reason we moved to the scripted moviNAND version is because people time and again have difficulty running commands on a Linux commandline, if someone wants to create more tutorials it would be preferred that their filesystems have chmodding and partitioning scripted requiring no user intervention through a Linux distro, if possible.
EDIT: also be prepared to answer questions and to make it known that your tutorial isn't dev-created and thus for people following it to not PM devs asking why it won't work
@nbates66
As you said, the version for movinand is a way more simple to apply. On the other hand using this version is meant to be only for those with fast small files write on their SD card (fast, i mean aroud 1 - 2MB for 4KB Q1, where most of cards are about 0,01 - 0,04MB).
And there is one more thing... Bada 2.0 which made this section a bit less popular within couple of last weeks (and I think this won't change till Oleg give us new version).
@NitramNach
The entire process hasn't been changed when compared to the old version from Shadow's TUT, so it might be as unstable as you said. I think it's rather the matter of SD card, cause I haven't crashed my phone yet.
I'm using Class 4 Sandisk SDSDQM-032G-B35, but it's like rebranded Class 2 (9MB sequential read, about 5,5MB sequential write, 1MB random 4KB Q1 read, and 2MB random 4KB Q1 write).
i'm sorry, so may i ask, it means it's stable now?
does installing android on sd card will affect the already presend bada in the phone by any way ?
am asking this becoz am very very newbie,,, never tried flashing and dont want to have the risk of flashing ,,, so , if this way dont affect the already presend bada 1.2 in the phone , i may try to install android on sd card coz really want to c android on my s8500 ...
my firmware is jpkc1 ....
@chriszue
It depend on that what do you mean by stable.
It's the same version as published by devs in Shadow's tut, but this one is prepaired to be installed on SD card.
Though the speed and stability depends on your card I can say that I've used it for 4 days without any problem.
Now I'm using Bada 2.0, so I had to resign of Android.
@sarmoodi
Nor this or the version presented on Shadow's tut have any influence to Bada.
But if, you're not familiar with linux I suggest using the movinand version.
@Qron
thanx alot for the super fast reply..
Was the microphone working in this version?
Dude I want u r help...
i compare galaxy 3 and wave 723 and they are almost got same things..>
so i m thinking about about port galaxy 3 android froyo on wave 723 is that possible to do?
if wave 2 can run android they y not wave 723?
I'm not capable to help you. I simply made a conversion of newest filesystem so it could be installed on SD card. Nothing less, nothing more. I don't have proper knowledge to make any port.
what do you meaning by "It provides all functions"?
can you make calls on this methods?
Are You kidding me??
You rip this out of context. The whole sentense was "It provides all functions which the newest version of Android from Shadow's tutorial has."
So NO!, you can not make calls using this method.
Terminal commands
I cannot access the ext2 partition through the terminal and execute sudo chmod -R 0777 ./* and
sudo sync, that is I cannot find the folder in the FileSystem where Ubuntu places the mounted partitions. Could you tell me how to do this?
I have Ubuntu 11 installed through wubi if that makes any difference.
10x in advance
Root
It would be really helpful if someone could give the syntax for rooting froyo for this SD card version.
rohitman said:
It would be really helpful if someone could give the syntax for rooting froyo for this SD card version.
Click to expand...
Click to collapse
chmod -v -R 4755 ./system/xbin/*
badelemental said:
chmod -v -R 4755 ./system/xbin/*
Click to expand...
Click to collapse
Thanks for the reply.
I've come up with another problem though, On starting Market a white screen opens & the market closes, no message though.
Should I reinstall Android to fix the problem ?
rohitman said:
Thanks for the reply.
I've come up with another problem though, On starting Market a white screen opens & the market closes, no message though.
Should I reinstall Android to fix the problem ?
Click to expand...
Click to collapse
Yes, give it a try, as far as I'm aware it should work. Maybe the installation went a little wrong, probably nothing to do with you ^^.
Hope I've helped.
i followed all the steps several times and my phone keeps hanging at galaxy s screen.
any idea of what im doing wrong?already tried ext2 and ext3.
I am unable to use the touchscreen functionality properly in android on bada. I have loaded on SD card dual boot with Bada 2.0.
I am finding difficulty in scrolling or long-press (to create shortcut in home screen) or play "angry bird" , I cannot pull and hold the catapult.
Is there any workaround ? Have others faced this problem ?

[I9505] Ubuntu Touch Development

Ok guys, starting this theard also to find other devs that also are working on porting ubuntu touch to the same device and buildup a team, anyone interested?
So my 1st try was when CM wasn't final release and got stuck at boot, i could connect with adb, but i only got displayed ubuntu and kernel version, and only a few commands worked, this is my 2nd try, so let's hope it will work better this time, also i will put my work on github.
24.NOV.2013:
-Having issues with libstagefright: http://pastebin.com/C8cuCAYA
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
JustSueMe said:
Not much at rom porting but I'm a strictly linux only user and will help anyway I can. Send me a pm or post where your git is.
Sent from my GT-I9505 using xda app-developers
Click to expand...
Click to collapse
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
Nice I have a dev build env for ubuntu touch but unsure how to pull repo for unknown device. But if u get a build that boots I'm more than eager to work on it
Sent from my GT-I9505 using xda app-developers app
I've tried a few times to get it going for the M919 but each time I can't get past the Samsung Splash screen. I wasn't even able to connect via adb. Granted, I don't exactly know what I'm doing, but I do have a build environment set up and do have a little experience building and debugging builds. I should have time to tinker with it again in a few weeks.
ubuntu build
nyl said:
Nice to have people interested in this project, I will get GIT up when I will have it running 1st 13.10 since its stable.
Click to expand...
Click to collapse
i have a build enviroment made up and pulled repos ect.. i just need to work a few things out before im ready to test it and post on here, if you can point in right direction (if yours boots)
need to do the audio part but can boot without sound in the alpha
neeed to add in apparmor later, can be done later ubuntu should boot without it
brightness, i dont think it matters so much as booting up is priority but i dont seem to have file it wants me to change "device/[manufacturer]/[codename]/init.[codename].rc"
problem with the way fstab has to be setup
within my android source my fstab is "void.fstab" which has lines that look like :
dev_mount sdcard /storage/sdcard1 auto /devices/platform/msm_sdcc.4/mmc_host/mmc2/ /devices/platform/msm_sdcc.2/mmc_host/mmc2/
ubuntu port guide for fstab asks to find a filename like "fstab.jfltexx" and have lines that look like:
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1
help with fstab will be much appreciated.
then ill make my build ready for testing/debugging + suppose ill upload files output files for others that are interested to use
Try this
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
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1,errors=panic wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,journal_async_commit wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,journal_async_commit,noauto_da_alloc,errors=panic wait,check,encryptable=footer,length=-16384
# recovery
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults recoveryonly
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults recoveryonly
# vold managed volumes
/devices/platform/msm_sdcc.2/mmc_host/mmc2 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=sda:auto
Yes I used part of that, problem now is compile errors, I have fixed a lot of them which involved discarding some features for the time being.
Boot is the main priority though
Im stuck on a compile errors for shared library, ill attempt this one after I've slept.
Hope fully this is the last error, then ill have a .zip to upload .
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
coolnessQ said:
Thats some great news ^^
What is the rom size?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
JustSueMe said:
Erm i haven't got a system to flash yet, possibly I could try just getting a boot.img and flashing a ubuntu filesystem but the system modified will be needed to boot fully, in theory I'd only get a shell. I did have a boot.img [seemed to have misplaced it :s , comes out at 7.3mb]
When I've got more time I will go bk to source code and try work out how to solve the errors so I can have boot.img and system.img.
If anyone else is working on this, share problems and solutions With me ti help further the progress.
Click to expand...
Click to collapse
are you unsing tw stock sources for the kernel? with 7.3mb it almost looks like that.
I have tried porting it before and here is my advise, you really have to look at the errors that it gives you during compiling rather then skipping it, or ignoring it, this is the only way you will get it decently working. the rom itself is only around 100mb if i remember correctly. the ubuntu package is like 400mb on top, but thats all proprietary files so universal.
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
JustSueMe said:
Im using ubuntu tool.
So sources come from cyanogen's clone with modifications (if thats correct)
Yes I have been fixing errors hence no nfc support, but atm it's a problem with libstagefright [hardware video decoder] I was advised to remove it as not needed to make 1st boot but seems to be hardcoded in there
$ grep -r -H "stagefright" *
Click to expand...
Click to collapse
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
broodplank1337 said:
Here is the reference :good:
Code:
[email protected] /media/broodplank/linuxdatanew/AOSP-KK/device/samsung $ grep -r 'stagefright' .
./qcom-common/qcom-common.mk: libstagefrighthw \
also if you need clean sources for some particular things just use my repos from AOSP 4.3 (https://github.com/aosp-s4). it only includes the needed commits for jf devices only. way less filled with potential compile breakers like the source of cm.
Click to expand...
Click to collapse
Ah I see this seems to of cleared it up abit for me, im busy today but may get look in at code, if not then tomorrow and clean it up abit and try recompile.
If it looks like a lost cause ill jump over to your git and pull that repo.
Fingers crossed
Sent from my GT-I9505 using xda app-developers app
commit to github so we can all take a look at it
.
..
You need to copy some header files for libstagefright to compile:
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMetaData.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-
core/inc/QOMX_AudioExtensions.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/OMX_QCOMExtns.h frameworks/av/media/libstagefright/
cp hardware/qcom/media/mm-core/inc/QCMediaDefs.h frameworks/av/media/libmediaplayerservice
My cm compiled but it wont boot (after flashing .zip and ubuntu system)
hmm.. did you remove all unecessary APPS? that are only needed by android not ubuntu touch? at you it seems relating to mounting points, something in your source doesn't let the kernel mount the partitions, maybe find a different approach to mount and add it to the source tree.
http://e2fsprogs.sourceforge.net/
everyone with interest in using ubuntu
if your interested in ubuntu touch on jfltexx and want to help
your now in luck
go here http://forum.xda-developers.com/showthread.php?p=48344910#post48344910
there is the download links and a few fixes for connectivity
Here is the link to the AT&T/Tmobile rom download : http://www.androidfilehost.com/?fid=23252070760974893'
Here is the link to the how to site (now instead of the phablet download use the one above) : http://forum.xda-developers.com/showthread.php?t=2564187
Oh and you need to flash the lokidoki zip file if used for AT&T.
Had it working perfectly, it is in extreme alpha, I had the wifi working and sound only works when plugged into headphones.
This should be more than enough to get the rom started up and getting a nice UT running shortly where everything works :3
I am not responsible for whatever happens to you or your device before, during, or after this. :3

HP Touchpad Swap - The Easy Way

HP TOUCHPAD has discovered a wonderful way to speed up the old girl, but for many it's too complicated. So here's an easy way.
Download the SKZ Kernel from here
Download Swapper from the Playstore​
This creates a swapfile rather than a swap partition. There's plenty of discussion about the relative merits of each, but for normal operations, they're pretty much equivalent.
You'll need to be rooted, of course, and your ROM needs to be Dirty Unicorns. Set the swap for what you want (I used 384 MB, but you'll never need more than 1 GB). The kernel contains most of HP TOUCHPAD's changes, but I've not disabled anything in the kernel, so you can still set it any way you want.
Enjoy, and be sure and thank HP TOUCHPAD for his great work.
...
friends, I do not know how to do this, a step by step video, please refer to the step when creating the kernel installation zip file, which the user will install using TWRP.
Add a script to create the swap file and format, a video with this step please
HP_TOUCHPAD said:
__SNIP__
Add an script to create the swap file and formatted:
Working directory:
Code:
cd /boot/usr/sbin
./lvm.static vgchange -ay
./lvm.static lvcreate -l 100%FREE -C y -M y --major 254 --minor 0 -n /dev/store/swap
mkswap /dev/store/swap
__SNIP__]
Click to expand...
Click to collapse
Ok, you win. Check out my latest kernel here
...
..
HP_TOUCHPAD said:
--SNIP--
The issue it by setting the permission (set_perm), something is wrong.
Click to expand...
Click to collapse
Try this
..
HP_TOUCHPAD said:
--SNIP
Also the process of update is been done by update-binary and not busybox. The update-binary that you have is 832.7 kb the one on the Dirty Unicorn ROM zip file is 1.3 MB. I also swap the update-binary but it did not work.
I think that the reason set_perm does not work is because is not integrated in the update-binary which has all the commands to execute the update-script.
Where does the update-binary comes from? where is it generated from?
--SNIP--
Click to expand...
Click to collapse
Version with an old update-binary here. I tested it in recovery, and it seems to work, but I'm not holding my breath.
...
HP_TOUCHPAD said:
Is a good thing you did not hold your breath, other wise your skin color will be like a Smurf and not able to read this message, as you will be on the other side ;-(.
The update-binary been only 254.7 kb, is able to change the permission and also run a program and that is all we need it to do. But because the environment is not properly set in TWRP the common arguments does not work and everything must be specified. The run_program ("lvm.sh") does not work as I explained why.
Just when I thought that I knew the basics, now I am learning how Edify Code works and that is the fundamental as is the (creation), (installation) or (flashing) of everything that gets copy and executed in Recovery.
I got it working!
But I am writing everything in details to wipe out all the partitions ( a reset ) and then recreating everything including the swap partition, it should work for all models 16GB 32GB and 64GB. One single zip flash!
Will report back with the results!
Click to expand...
Click to collapse
Good luck. I'm done. I did notice, however, that you can replace the update-binary with your own shell script, but that was more than I wanted to do.
...
help!
Halloo
I'm trying to do this as my touchpad is unusably laggy using DU. I can't get it rooted though... Can someone explain the latest method? I tried various SuperSU zips, nothing works. I suspect I'm doing something wrong..
...
Thats good news! Meanwhile could you help me with the SuperSU problem?? I want to get rooted!!
...
HP_TOUCHPAD said:
--SNIP--
The swap file is not been use by the Kernel.
( keep it lean )
--SNIP--.
Click to expand...
Click to collapse
The swap file is not in use because there isn't any command to turn it on. You need to add "swapon /dev/store/swap" to the script or in the ramdisk after boot initialization.
This is where we part company. I've always wanted to provide the greatest flexibility, not the necessarily the best performance. I'm not really interested in providing the single "best" configuration since I don't know what others think is the "best". You're doing a great job - go for it. I'm outta here.
..
This is sounding good! Hope you guys are successful!
...

Categories

Resources