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
Related
Hi there, i was trying to run Debian on my pro, but i cant install it! i try two methods, the Linux installer Beta 1.7 (say kernel dosnt have ext and loop support) and the SU terminal emulator way (cant chmod to 4755 any file, even using the su command - from here: http://www.talkandroid.com/android-forums/android-development/1091-install-debian-android.html )...
My pro is ROOTED with latest z4root, i even do a factory repair with pc companion...
Any advice???
Regards!
I tried this as well... no loop is no loop ( required for chroot type runs )
works on a Samsung i5700 I have at work tho...
thnx for the reply, so i can add loop and the ext thing? or we need a custom kernel? , what rom have the samsung?, in other hand i dont know why i cant chmod the files, even using root explorer! regards...
needs a new kernel yes.
i5700 is running samdroid cooked ( forget which version, but added multitouch )
damn :/
now why i cant chmod the files using su terminal emulator or root explorer? maybe is because my sdcard is formated in fat32, regards!
fat32 knows nothing about *nix style permissions, in a way though... all files on a fat32 are set 0777, but not really... heh
For what it's worth, I've just had Debian running in a chroot on my X10 Mini Pro, using the instructions at talkandroid.com, as mentioned by the original poster. Sorry, but as a new poster, I'm not allowed to link directly to those directions. This is with stock ROM, upgraded to Android 2.1, rooted with SuperOneClick.
A few modifications are necessary to make it work. I'm going to try to describe what I've done, but I am working backwards, so it's entirely possible that I'll leave something out and you could suffer disastrous consequences. So please be sure you back up all crucial data before proceeding, and be prepared to accept the possibility that your phone could be destroyed in the process.
First of all, the instructions tell you to run scripts from your SD card, which isn't going to work unless the card has a partition with a Linux-compatible file system. I suggest following the directions as far as step 4. Then replace the "bootdeb" file in the "debian" directory with the modified version attached to this post. Rename it "bootdeb". Then you will have to run the following commands manually, preferably using adb shell, but it can be done in a terminal on the phone. Either way, using the ash shell helps by providing command completion and history.
As root (su):
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
mkdir /data/local/mnt
cd /sdcard/debian
cp bootdeb /data/local/bin #note: you may need to mkdir /data/local/bin first
cd /data/local/bin/
chmod 4777 bootdeb
You should now be able to run the bootdeb script to start up Debian.
The installation file says, "Be sure to run /scripts/onetime.sh as root from the shell after your FIRST 'boot'." This will prompt you to set a root password.
At this point, the Debian installation is command line only and root only. The image file needs to be resized before much can be added.
The other files in the Debian directory may be useful, but they all need to be modified before they can be used.
This is only a beginning. I don't know that I'm likely to get very far with it, so anyone else who's inclined to jump in and make this work better is welcome to do so!
edit: correcting grammatical error
Just in case anyone else shares my obsession -- I mean interest in getting Debian to run on an X10 Mini Pro, I thought I should report my progress. Or lack thereof.
Actually, as I said in the previous post, command line Debian works, and that's a lot of power to have available. But it would be nice to get X working, despite the lack of video drivers.
There's a lot of information out there about setting up X with a VNC server on an Android phone, then running a VNC client to access the graphic environment. The source of most accounts seems to be a thread at the androidfanatic forums, with the title "Gnome, KDE, IceWM or LXDE Desktop on your Android!"
(Sorry, I'm still too new at this to be allowed to post links, so this is the only way I can indicate where to find the information.)
I've tried lots of variations on those directions, trying to adapt them to the X10 Mini Pro. And I've had a little success. I can get to the Icewm or LXDE desktop and run the terminal program, but I can't start any programs that use X. Invariably, I get this error:
Error: Can't open display: :1.0
I've run out of ideas, so I'm taking a break from the project. If anyone else is interested enough to try, good luck to you!
For what it's worth, the most recent and comprehensive account of running Debian with X on Android phones appears to be at lanrat.com, in the "android" directory, filename "debian".
@RobbH
Very interesting! I'm waiting a new 8gb card so that I try it! Should you come up with any new progress please report here
Hi, I cant download or transfer apps to my sd card! people say that if i download astro it will fix but it didnt! So im looking for a way to fix it. can anyone help me
Sent from my MSM using the XDA mobile application powered by Tapatalk
x12CHRIS18x said:
Hi, I cant download or transfer apps to my sd card! people say that if i download astro it will fix but it didnt! So im looking for a way to fix it. can anyone help me
Sent from my MSM using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
If you're referring to USB Mass Storage in FRX07, then don't hold your breath.. unfortunately, it's a known issue.
maff1989 said:
If you're referring to USB Mass Storage in FRX07, then don't hold your breath.. unfortunately, it's a known issue.
Click to expand...
Click to collapse
It's unfortunately an issue with the loop'd mounts. If you create dedicated partitions for at the very least data - USB mass storage actually does work. hyc did some patching on this, not sure if that's in FRX07 or not. I haven't tried 07 on dedicated partitions yet.
Droid Explorer does a pretty damned good job of faking it tho...
arrrghhh said:
It's unfortunately an issue with the loop'd mounts. If you create dedicated partitions for at the very least data - USB mass storage actually does work. hyc did some patching on this, not sure if that's in FRX07 or not. I haven't tried 07 on dedicated partitions yet.
Droid Explorer does a pretty damned good job of faking it tho...
Click to expand...
Click to collapse
Ohhh I see thanks for the correction.
I noticed in the default rootfs.img for FRX07 that the init does in fact check for a dedicated data partition, although I'm not sure if it puts that partition to use as the data partition (that coding looked a little confusing :\). I assume it would otherwise it wouldn't make sense to check if there's no mount commands following...
It sounds intriguing, though.. May give the dedicated data partition a try; could help with performance, let alone fix USB MS
EDIT: Seems this idea has already been put into effect for FRX07... http://www.neopeek.com/viewtopic.php?f=14&t=7441
maff1989 said:
Ohhh I see thanks for the correction.
I noticed in the default rootfs.img for FRX07 that the init does in fact check for a dedicated data partition, although I'm not sure if it puts that partition to use as the data partition (that coding looked a little confusing :\). I assume it would otherwise it wouldn't make sense to check if there's no mount commands following...
It sounds intriguing, though.. May give the dedicated data partition a try; could help with performance, let alone fix USB MS
EDIT: Seems this idea has already been put into effect for FRX07... http://www.neopeek.com/viewtopic.php?f=14&t=7441
Click to expand...
Click to collapse
Indeed, but CWM of course uses different mount points than XDAndroid...
so XDA:
p1 - fat32
p2 - rootfs
p3 - system
p4 - data
CWM from Neopeek:
p1 - fat32
p2 - system
p3 - data
p4 - cache
So you can certainly setup dedicated partitions and use XDAndroid's rootfs. If you use CWM, just be wary, the layout is different. CWM is easier because it installs Android to these partitions for you - otherwise you have to move the data to the partitions yourself .
arrrghhh said:
CWM is easier because it installs Android to these partitions for you - otherwise you have to move the data to the partitions yourself .
Click to expand...
Click to collapse
By this, you mean copying, say, the rootfs.img to the second partition, or would the rootfs need to be extracted to the partition? I assume the latter..
maff1989 said:
By this, you mean copying, say, the rootfs.img to the second partition, or would the rootfs need to be extracted to the partition? I assume the latter..
Click to expand...
Click to collapse
Yes, the latter. Same with system.ext2 and data.img - these need to be expanded onto the dedicated partitions.
What I did was mount the system.ext2 file (looped) on my Ubuntu server. Mount a data.img (looped) as well. Then I stuck a mSD -> USB converter plug in the server, and formatted the card with fdisk assigning the partitions. Mounted those partitions in Ubuntu, then tar'd the data over (IIRC there's issues with cp, doesn't preserve permissions).
Code:
cd /dir1; tar cf - . | (cd /dir2; tar xf -)
is how I tar'd it.
arrrghhh said:
Yes, the latter. Same with system.ext2 and data.img - these need to be expanded onto the dedicated partitions.
What I did was mount the system.ext2 file (looped) on my Ubuntu server. Mount a data.img (looped) as well. Then I stuck a mSD -> USB converter plug in the server, and formatted the card with fdisk assigning the partitions. Mounted those partitions in Ubuntu, then tar'd the data over (IIRC there's issues with cp, doesn't preserve permissions).
Code:
cd /dir1; tar cf - . | (cd /dir2; tar xf -)
is how I tar'd it.
Click to expand...
Click to collapse
Oh wow... that's a bit different than I anticipated, although your information is very much appreciated the dir1 and dir2 refer to the mount points for the system.ext2 and data.img, respectfully, correct? And it's two commands in one, separated by the "|" correct?
Off-topic.. What's IIRC?
And also, I can comprehend that "tar'ing" files means copying them in some way, shape, or form, but how would that preserve permissions over simply cp'ing them from the mount point in Ubuntu to the partition on the SD card? Or perhaps even manually copying the files to the SD partition? Considering these actions are performed in Ubuntu, I would assume permissions wouldn't be altered :\
maff1989 said:
Oh wow... that's a bit different than I anticipated, although your information is very much appreciated the dir1 and dir2 refer to the mount points for the system.ext2 and data.img, respectfully, correct? And it's two commands in one, separated by the "|" correct?
Off-topic.. What's IIRC?
And also, I can comprehend that "tar'ing" files means copying them in some way, shape, or form, but how would that preserve permissions over simply cp'ing them from the mount point in Ubuntu to the partition on the SD card? Or perhaps even manually copying the files to the SD partition? Considering these actions are performed in Ubuntu, I would assume permissions wouldn't be altered :\
Click to expand...
Click to collapse
IIRC = if I recall correctly
Yes, that's all one command and dir1 is the system.ext2 mount or the data.img mount (the source), dir2 is the mount point on the card (destination).
I don't know why cp doesn't preserve permissions - there's probably some switch you can pass that will preserve perms. I'm not an expert here, I only know I had a boatload of issues when I just used cp... Talked to some experts, and they gave me that tar command - which worked perfectly.
Idk what you are talkin about! so is there way to fix this situation?!
x12CHRIS18x said:
Idk what you are talkin about! so is there way to fix this situation?!
Click to expand...
Click to collapse
You can fake USB mass storage with Droid Explorer. That's really the only option on looped mounts.
Where can I get droid explorer?
Sent from my Touch Pro II with Froyo
x12CHRIS18x said:
Where can I get droid explorer?
Sent from my Touch Pro II with Froyo
Click to expand...
Click to collapse
Here, let me Google that for you...
Haha thanks man! But I'm still having trouble.... I downloaded droid explorer then it told me that I have to download android sdk tool so I did and its still telling me that I have to download android sdk tools
Sent from my Touch Pro II with Froyo
x12CHRIS18x said:
Haha thanks man! But I'm still having trouble.... I downloaded droid explorer then it told me that I have to download android sdk tool so I did and its still telling me that I have to download android sdk tools
Click to expand...
Click to collapse
So... did you click the link to "do it for me" or whatever it says during install, or did you pick a manual install? You should just let the application do it for you, otherwise you have to download it yourself and then point it to whatever directory you installed it at... Oy.
I downloaded the zip file
Sent from my Touch Pro II with Froyo
x12CHRIS18x said:
I downloaded the zip file
Click to expand...
Click to collapse
Ok, would you like a cookie?
I still have a problem, droid explorer doesn't recognize my phone. i have my phone in debug mode
x12CHRIS18x said:
I still have a problem, droid explorer doesn't recognize my phone. i have my phone in debug mode
Click to expand...
Click to collapse
Did you get an 'XDA' device in device manager? Did you read the FAQ and install PDAnet if the drivers with Droid Explorer don't work?
yeah i got XDA but it wont let me install it, it keeps on saying "cant find device". Do I have to download PDAnet if i cant install it?
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 ?
WARNING: This script can be dangerous if you do not know what you're doing!!! I am not responsible for any of your files or hard drives that are deleted if the script is used the wrong way.
The following Bash script (built for Ubuntu) is a simple script that I wrote that does the following:
1. Lets you chose any non-SD ROM.
2. Lets you chose the drive to partition. (WARNING: This ONLY ignores /dev/sda as it assumes that it's your main hard drive. If you have more than one hard drive, do NOT use this unless you know what you're doing!!!)
3. Automatically partitions a Boot partition, a system partition (large enough to hold some BIG ROMs...), a data partition and the rest of your SD card (whatever size it may be) is partitioned as a standard FAT32 space.
4. It modifies both the ramdisk and the vold to boot from the SD and to see that 4th partition as the SD card.
5. If the ROM doesn't have gapps built in and uses the install script to copy them from your last ROM (like CM and MIUI do), it will download and install the gapps.
6. It creates all the required symlinks.
I've only tested it with my 8GB microSD and with MIUI. The permissions are not set up correctly for now due to a bug of sorts... but the ROM that I tested boots and works fine. (Set it all to 777 for now.)
This is only the first version. I just wrote it today. If you find bugs or have a better idea on how to do certain things (like ONLY display USB drives and SD cards) PLEASE let me know here.
If nothing in this thread makes sense, it's because I'm tired...
Update: Adding a bit more info.
Its a really good idea, but not many people can try it unless it's ported to Windows or Mac.
ikingblack said:
Its a really good idea, but not many people can try it unless it's ported to Windows or Mac.
Click to expand...
Click to collapse
I know most people use Windows but Windows isn't very well equipped to do the stuff that this script does. I could always try to make an actual program (make it in c or something) but that would require a complete rewrite. I mostly wrote this for myself (to make my life easier while I'm porting a ROM to the Nook) but figured someone else might be able to use it. (Mostly the people who make the SD img's for everyone else, not the general public.)
ivanmmj said:
I know most people use Windows but Windows isn't very well equipped to do the stuff that this script does. I could always try to make an actual program (make it in c or something) but that would require a complete rewrite. I mostly wrote this for myself (to make my life easier while I'm porting a ROM to the Nook) but figured someone else might be able to use it. (Mostly the people who make the SD img's for everyone else, not the general public.)
Click to expand...
Click to collapse
Well yeah, it is pretty hard. Anyways, your script works for me. Its really nice.
You can run bash in Windows using Cygwin
What's the benefit from using this script on the pc and not using verygreens installer on the nook?
joej said:
You can run bash in Windows using Cygwin
Click to expand...
Click to collapse
Does Cygwin include parted, mkfs.ext4 and mkfs.msdos?
TDO said:
What's the benefit from using this script on the pc and not using verygreens installer on the nook?
Click to expand...
Click to collapse
What installer? I didn't realize he had an installer that would let you install any "non-SD compatible" ROM into an SD card and make it SD-compatible. >.<
Just look at the thread directly below this one ... ;-)
http://forum.xda-developers.com/showthread.php?t=1000957
I am using it in this setup: http://forum.xda-developers.com/showthread.php?t=1022786
as alternate boot option.
TDO said:
Just look at the thread directly below this one ... ;-)
http://forum.xda-developers.com/showthread.php?t=1000957
I am using it in this setup: http://forum.xda-developers.com/showthread.php?t=1022786
as alternate boot option.
Click to expand...
Click to collapse
Reading that it looks like the differences are:
Mine:
Can do all that in the PC without having to touch the nook.
It's all automated. (Like downloading the gapps.)
You run the script then just pop the SD card into the Nook and go.
Meant more for devs who are testing new builds left and right or who are building an image for others to use.
His:
Doesn't require Linux nor any Linux experience (to choose the correct drive from the drive list that the script gives you.)
Meant for the average usage who wants to be able to easily update their ROMs and install new kernels without "wiping" the SD card's data partition.
ivanmmj said:
Reading that it looks like the differences are:
Mine:
Can do all that in the PC without having to touch the nook.
It's all automated. (Like downloading the gapps.)
You run the script then just pop the SD card into the Nook and go.
Meant more for devs who are testing new builds left and right or who are building an image for others to use. <snip...>
Click to expand...
Click to collapse
I like this... Thanks
I am using verygreen's installer on my Nook right now, but I am going to start playing with this script
P.S. Linux rocks, everyone should have it...for those who don't want to let go of Windows, you should at least have Linux installed as a virtual machine on your box using VirtualBox.
So I was playing with this for a few moments on my Mac at work today. Am I copying the ROM archive, say MIUI_us_encore_1.8.5_Eng_Deo_ZipA_Signed_andmer.zip or cm_encore_full-163.zip, into the same location as the Install2SD script?
Or am I to uncompress these roms into their respective folders and copy that folder into the same location as the Install2SD script?
I have yet to get another uSD to play with, so I have obviously not gotten to far with this just yet. I will be back to my Ubuntu machine after I get home from work with a new uSD to play with.
cdaters said:
So I was playing with this for a few moments on my Mac at work today. Am I copying the ROM archive, say MIUI_us_encore_1.8.5_Eng_Deo_ZipA_Signed_andmer.zip or cm_encore_full-163.zip, into the same location as the Install2SD script?
Or am I to uncompress these roms into their respective folders and copy that folder into the same location as the Install2SD script?
I have yet to get another uSD to play with, so I have obviously not gotten to far with this just yet. I will be back to my Ubuntu machine after I get home from work with a new uSD to play with.
Click to expand...
Click to collapse
I haven't tested to see if this works on a mac. That said, just run the script and it will tell you where to put the files (in linux (in nautilus to be exact...)) If not, when you run it the first time, it will create the necessary folder and you can put the files there.
UPDATE: With the new release of Kali Linux, I started playing around and got their raw disk image put into a mountable img. Download can be found at https://www.cubby.com/pl/kaliarm_mod.img.7z/_f9cd8b50b18b441da2969053cb15c71c. The Kali image is not exactly resizable, and will require 5 gigs of space. I haven't tested it yet, but hypothetically if you name it the same, and put it in the bt5 directory, it should work the same. Report back if you have issues.
I spend a good few hours today working this out. I have been a long fan of Backtrack, and was unable to get it to work on the DNA reliably, until now. Here are the modified scripts.
YOU MUST BE ROOTED AND HAVE BUSYBOX FOR THIS TO WORK, I RUN DSB'S KERNEL AND UKB, WORKS FINE FOR ME. I TAKE NO RESPONSIBILITY FOR THESE INSTRUCTIONS OR SCRIPTS ON YOUR PHONE, USE AT YOUR OWN RISK.
Included:
bootbt - starts up the loop device, and mounts all the needed partitions
ubt - unmounts the partitions, and sets your path variable back to normal
Instructions:
Download the ARM img file from Backtrack's site, Copy the bt5.img and other files (EXCEPT the bootbt) onto your sdcard into a folder named bt5.
Open terminal emulator and type su. cd to /sdcard/bt5 and type sh bootbt. Profit.
The bt image file is about 4.9 gigabytes. Technically it doesn't need to be that large, as the file structure is only about 2.5 gigs of space in use. If you want to resize it, you need to open up a Linux based VM or be on a linux machine and do the following terminal commands as root. (IE Sudo/SU)
This will create a blank image file that is about 3.2 gigs with 1 meg blocks
Code:
dd if=/dev/zero of=/path/to/new/btsmall.img bs=1m count=3300
This will create an ext file system for said image, make sure to say yes when it warns about being a special block.
Code:
mkfs.ext4 /path/to/new/btsmall.img -N 35000
This will create mounts to open the two image files
Code:
sudo mkdir /mnt/btlarge
sudo mkdir /mnt/btsmall
This will mount the two files, then copy one into the other, recursively
Code:
mount -o loop /path/to/large/bt5.img /mnt/btlarge
mount -o loop /path/to/small/bt5.img /mnt/btsmall
cp -Rfpv /mnt/btlarge/* /mnt/btsmall/
Once they are done, unmount
Code:
umount /mnt/bt5large
umount /mnt/bt5small
From there, copy over to your storage and make sure the file path reads /sdcard/bt5/bt5.img as that's what the scripts are meant to read.
Nice! If only we had HDMI out...
For anyone else who had no idea what the heck backtrack 5 is, it's a unique GNU/Linux distribution
http://forum.xda-developers.com/showthread.php?t=1079898
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
Is that dual boot or it comes instead of the android os?
Have you tried monitor mode on the wife card?
Sent from my HTC6435LVW using xda app-developers app
desheh said:
Is that dual boot or it comes instead of the android os?
Have you tried monitor mode on the wife card?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
No, it's a VM, it just mounts the .img file and pushes you into the command line of it. For the most part, I've played with it using command line, VNC is annoying to set up IMO.
As for monitor mode, no, airmon isn't even included in the image. I'm still looking for a way to get git working so I can update metasploit, as they moved away from svn.
Though, it looks like someone else managed to tweak the Galaxy SII and Nexus One chipsets to allow it
http://forum.xda-developers.com/showthread.php?t=1892535
If anyone knows our chipset, please do feel free to post it.
I misread your post and thought that the new Kali image you posted could be resized... not really as the kali FS is about 4.1 ~ 4.2 gig. The problem I have is that both my internal and external SD (I am actually on a Galaxy Note) are formated vfat(fat32); thus file size is limited to just over 4 gig. Sucks as the other options for kali I have tried have fallen through and I was hoping your image would work well.
linuxonandroid(app on market): basically just a debian install with all apt sources pointing to the kali repo's
my own rootfs I built: wont boot
Linux Deploy(app on market): doesn't work right either
chroot:can't execute:
I have problem on chroot command it shows chroot:can't execute:/bin/bash: file or directory not found..any help..please