Edit: Delete me
Heh, adding bootanim support to my kernel was something I was thinking of this weekend.
It needs initramfs hacks - check the commits for my I777 initramfs.
Entropy512 said:
Heh, adding bootanim support to my kernel was something I was thinking of this weekend.
It needs initramfs hacks - check the commits for my I777 initramfs.
Click to expand...
Click to collapse
I'm confused... I checked out your commits. It seems like essentially, what I did in my 2nd senario up there should have worked with a "bootanimation.zip". You pulled the switcharoo in initramfs and I pulled it at the file location. You off loaded execution to a shell script and I executed from the call in the initramfs.
Is there a difference in offloading to the shell script verses directly calling from init.rc?
Is there some reason I can't just make up an arbitrary name for a service? Like: I can't just call it "serviceA" and point at some daemon; in init.rc?
It seem like as long as you retain the service name "samsungani" you can point it anywhere you want? So like, the service names are set in stone?
Your solution is definitely more elegant, I think I would have gotten there if I could have just gotten a custom boot animation to load..
Thank you for the reply by the way.
Meticulus said:
Custom Boot Animations!
I'm only posting 1 for now but will post more as I have time
Need to have CMW
Method # 1
1. Download, Animod.zip and one of the animations and put them on you sdcard.
2. Use CMW to install Animod.zip and then animation. ( no need to reboot and you only need to install Animod.zip once.
3. Reboot.
Method # 2
1. Download Animod.zip and install using CMW.
2. Search the web and find a "bootanimation.zip" that you like and download.
3. Rename file "sanim.zip".
4. Connect your player and adb shell.
5. mount -o remount,rw /system
6. exit
7. push sanim.zip /system/media
8 adb reboot.
Let me know how it goes...
Click to expand...
Click to collapse
Thank you Meticulus for finding out how to use custom boot animations!
I have a Galaxy Player 4.0, so I couldn't use your CWM because it is not formatted as ext4. But here's how I did it:
1. Change /system/bin/samsungani to /system/bin/samsungani.met
2. Change /system/bin/bootanimation to /system/bin/samsungani
3. Drag sanim.zip to /system/media and reboot.
It works perfectly!
wow !!! Gotta try
thanks for your hard work
I really want to change my boot animation but I search everywhere it's said SAMSUNG use another method to change boot animation.
but if this work
I must be happy
###Edit###
after try
Method # 2
1. Download Animod.zip and install using CMW.
2. Search the web and find a "bootanimation.zip" that you like and download.
3. Rename file "sanim.zip".
4. Connect your player and adb shell.
5. mount -o remount,rw /system
6. exit
7. push sanim.zip /system/media
8 adb reboot.
Click to expand...
Click to collapse
after reboot boot animation still stock samsung
but when I try following advice from klin1344
1. Change /system/bin/samsungani to /system/bin/samsungani.met
2. Change /system/bin/bootanimation to /system/bin/samsungani
3. Drag sanim.zip to /system/media and reboot.
Click to expand...
Click to collapse
& yeah !!!! it's work
Thanks all yall !!!!
The bootanimation binary in Samsungs points to sanim.zip and not bootanimation.zip - I kanged a binary from CM7.
A CM7 GalaxyS binary should work on this device.
klin1344 said:
Thank you Meticulus for finding out how to use custom boot animations!
I have a Galaxy Player 4.0, so I couldn't use your CWM because it is not formatted as ext4. But here's how I did it:
1. Change /system/bin/samsungani to /system/bin/samsungani.met
2. Change /system/bin/bootanimation to /system/bin/samsungani
3. Drag sanim.zip to /system/media and reboot.
It works perfectly!
Click to expand...
Click to collapse
I forgot about the CWM being ext4 only I'll make one that is rfs and post it!
Entropy512 said:
The bootanimation binary in Samsungs points to sanim.zip and not bootanimation.zip - I kanged a binary from CM7.
A CM7 GalaxyS binary should work on this device.
Click to expand...
Click to collapse
Yeah, adb logcat became my friend! I was looking at the platform source code and of course Samsungs changes where not in there!
so method 3
need to install animod ??
or just do following step
just ask for anyone who will trying to do that
aillez said:
so method 3
need to install animod ??
or just do following step
just ask for anyone who will trying to do that
Click to expand...
Click to collapse
No need to install Animod for method 3. animod. does steps 1 and 2 in method 3.
RFS version is tested and working now.
This method also works on an international GP 5.0 with some tiny modification to the flashable zip.
The mount command in the updater-script is not compatible with YP-G70, but it works after I changed that to
Code:
run_program("/sbin/mount", "/system");
WT Ho said:
This method also works on an international GP 5.0 with some tiny modification to the flashable zip.
The mount command in the updater-script is not compatible with YP-G70, but it works after I changed that to
Code:
run_program("/sbin/mount", "/system");
Click to expand...
Click to collapse
Thanks man, I new to created CWM update zips. I should be able to consolidate back down to 2 files instead of 4!
Glad it works in international as well.
Thanks, worked great! No more stupid samsung bootscreen!
Related
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
racht said:
unfortunately unyaffs-x86 does NOT preserve all file permissions if image is extracted and reassembled in Linux x86.
You have to extract/assemble on the phone to keep permissions.
Or, alternatively, you can fix permissions by using xRecovery tool, there's a menu "fix permissions".
To see why exactly your phone reboots, use adb logcat from PC.
Click to expand...
Click to collapse
yess, thank you! now i found a mkfs.yaffs2 for arm processors for android. it's verry slow.
so i made my sdcard to ext2, and now i try to "extract" my img.
so ... It's used to ?
trapacska said:
hy everybody.
i try mod the system.img on ubuntu linux with unyaffs and mkfs.yaffs2, i "hacked" the symlinks(because the armv6 unyaffs doen't like) so now everything is ok, unyaffs works well. BUT:
when i flash the other sin files with flashtool, my x8 is restart after a green sony ball. i gave to all file in bin folder: rwx-rx-rx and the all other files got rw-r-r permissions.
so, i don't know what is the problem with this method.
//my system.img was flashed with a method in "clean and pre-rooted 2.1 rom" thread.//
in attachment the filesunyaffs and mkfs.yaffs2.x86)
Click to expand...
Click to collapse
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
propc said:
i've created sh script to view your current permissions.
it could be useful to re-set the permission manually to create the ROM
how:
upload to root of sdcard
run
Code:
su
cd /sdcard
sh plist.sh
it will create folder "permissions" on your sdcard.
all files permission listed there
open with notepad++
Click to expand...
Click to collapse
it's cool! thank you. now i try to debrand the oroginal x8 rom.
trapacska said:
it's cool! thank you. now i try to debrand the oroginal x8 rom.
Click to expand...
Click to collapse
you know what. i've found a better method to change permissions
1-mount original system.img
Code:
mkdir tmp/1
sudo mount -o loop /your/system.img/path /tmp/1
2-clone permissions from original system.img to your system folder
Code:
chmod -R --reference /tmp/1 /your/new/system/path
and the permission fix done!
EDIT: tested. and worked. I've finally created my own modified ROM (running on sdcard)
EDIT2: some problem with root permissions, will work on it
thank you i found a way to fix permissions too:
1. unyaffs original system.img
2. in busybox shell mount it to r/w
3. copy xrecovery and su and superuser to fresh rom.
(for me it works well without xrecovery fix permissions)
if there is some error, you can fix it with xrecovery
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
bnight said:
Hello,
Can you try to change the /system image with one from froyo ? You can find such image in the X10 forum. I thing that if we change the contents of the /system with such from froyo it should work. With the standard kernel from eclair.
Please try this and let me know.
Click to expand...
Click to collapse
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
propc said:
i tried it. no luck. too many files. where are the files that need to be edited?
/system/lib?
Click to expand...
Click to collapse
/system/framework (for a skin)((but the all folder))
trapacska said:
/system/framework (for a skin)((but the all folder))
Click to expand...
Click to collapse
thanks. will try porting from htc legend 2.2 rom later.
http://android.modaco.com/content/d...333107/honeycomb-boot-animation/#entry1614170
Big props to User Error for modifying this for the Dell Streak! Head over to Modaco to d/l.
Not the Streak, but you get the idea. Skip to 35 sec in:
Install by copying to /data/local. Full instructions from fone_fanatic:
fone_fanatic said:
3 Options to install.
First step: Extract downloaded .zip file to reveal "bootanimation.zip"
1. ADB
Navigate to the folder containing "bootanimation.zip" in terminal/command prompt.
Type the following
Code:
adb push bootanimation.zip /Data/Local
Then to test, set your device so display is in landscape (will not display properly if you have it on portrait and test it but will display fine either way on boot)
Code:
adb shell bootanimation
2. Root Explorer
Copy "bootanimation.zip" to your SD card
On your Streak open up Root Explorer (or any other app that allows you to copy paste to the internal memory)
Copy "bootanimation.zip" and paste it to /Data/Local
3. Terminal Emulator
thanks nickshertzer, his directions are for drop box but can easily be manipulated for simply copying the bootanimation.zip to your SDcard
nickshertzer said:
BTW, if you don't have / want to get out that sync cable for ADB, use dropbox & Terminal Emulator. Make sure you download the .zip using dropbox longpress first before running following command (requires Busybox / can't remember if it is installed default on Steve's ROM)
Code:
su
cp /sdcard/dropbox/bootanimation.zip /data/local/
reboot
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Enjoy
Click to expand...
Click to collapse
Oh, and Switched DownloadSquad has posted the Android 3.0 SDK Honeycomb Wallpaper grabs without need to sign up / sign in:
http://downloadsquad.switched.com/2011/02/23/download-android-3-0-honeycomb-wallpaper-images/
nickshertzer said:
http://android.modaco.com/content/d...333107/honeycomb-boot-animation/#entry1614170
Big props to User Error for modifying this for the Dell Streak! Head over to Modaco to d/l.
Not the Streak, but you get the idea. Skip to 35 sec in:
Install by copying to /data/local. Full instructions from fone_fanatic:
Click to expand...
Click to collapse
Tried installing using terminal emulator, does not work, just used root explorer to copy and paste. Liked it!
Thanks like the look of this, will give it a try and report back
works great on my dell streak. just doesn't have that blue bee.
thx alod... i love the bootanimation...
works well. would be nice if it was a higher rez though. some pixely parts here and there
Hi . I am porting various boot animations to Galaxy 3.
How To:-
Eay Way.
1- Enable usb debugging in phone.
2- Rename file to bootanimation.zip.
3- Download QtADB from here.
4- Run this command in command prompt
Code:
C:\QtADB\adb shell
#su
#mount -o remount,rw /dev/block/stl9 /system
5- Navigate to "/data/local/" in QtADB file manager.
6- Copy bootanimation.zip file.
7- Restart and enjoy.
Or
1- Copy bootanimation.zip to sd card.
2- Copy file to "/data/local/" with Root Explorer.
3- Restart and enjoy.
FIXED
More Boot Animations-
3
6
7
8
Some more....
9
10
11
12
13
14
This should be located in themes and apps section...
Dont work for me .... The bootscrenn is a black picture ....
But the phone boot....
arunmcops said:
Hi . I am porting various boot animations to Galaxy 3.
How To:-
Eay Way.
1- Enable usb debugging in phone.
2- Rename file to bootanimation.zip.
3- Download QtADB from here.
4- Navigate to "/data/local/" in QtADB file manager.
5- Copy bootanimation.zip file.
6- Restart and enjoy.
Or
1- Copy bootanimation.zip to sd card.
2- Copy file to "/data/local/" with Root Explorer.
3- Restart and enjoy.
Found some error. Fixing now...
Click to expand...
Click to collapse
MOVED TO THEAMS & APPS SECTION with a permanent link here
How to Do it.... Pics
1-Mount the system
2-Open QtADB
3-Transfer bootanimation.zip to either /data/local or /system/media.
4 Reboot
jordane1993 said:
Dont work for me .... The bootscrenn is a black picture ....
But the phone boot....
Click to expand...
Click to collapse
FIXED......
Doesn't work bootscreen always black.
Sent from my GT-I5800
abhimukesh25 said:
Doesn't work bootscreen always black.
Sent from my GT-I5800
Click to expand...
Click to collapse
Fixed. Now it's working. Confirmed on my phone.
Which one is working.
Sent from my GT-I5800
abhimukesh25 said:
Which one is working.
Sent from my GT-I5800
Click to expand...
Click to collapse
I compressed the zip by mistake ! Now i have fixed it. by the way i have tried and tested animation no. 8.
arunmcops said:
I compressed the zip by mistake ! Now i have fixed it. by the way i have tried and tested animation no. 8.
Click to expand...
Click to collapse
No. 8 its working good, and nice
Thanks!
Thanks a ton mate will try it.
arunmcops said:
Some more....
9
10
11
12
13
14
Click to expand...
Click to collapse
No. 9 is cool
Thank you.
@ arunmcops, sorry for the noob question, but could u tell in which folder to put these files into as i couldnt find /data/local/ on my cell or sd card.
coolpepe said:
@ arunmcops, sorry for the noob question, but could u tell in which folder to put these files into as i couldnt find /data/local/ on my cell or sd card.
Click to expand...
Click to collapse
Follow the new pics in 4th post.
arunmcops said:
Follow the new pics in 4th post.
Click to expand...
Click to collapse
Thanks a ton mate. Really appreciate your help.
Done it and its working great really liked the 8th one. Thanks again.
qtadb is not displaying the contents of my phone....it shows every directory empty...wat could be the problem??
apurv104 said:
qtadb is not displaying the contents of my phone....it shows every directory empty...wat could be the problem??
Click to expand...
Click to collapse
First run this
Code:
C:\QtADB\adb shell
#su
#mount -o remount,rw /dev/block/stl9 /system
Hi.
First, a disclaimer... I will not be responsible for you messing this up and bricking your device. I am only outlining a guide which I figured out and used to get my TP setup the way I wanted. DO NOT come to me for support, as I am not a dev and really have no time to save anyone from their doom...
I used RootExplorer (Paid App -
https://market.android.com/details?...sImNvbS5zcGVlZHNvZnR3YXJlLnJvb3RleHBsb3JlciJd) to do the steps outlined below. You may use any file manager of your choice, granted that it gives you root access with read/write access to /boot folder. Please make sure you backup anything you plan on changing by making copies and moving them to a safe location... Don't way I did not warn you... ^_^
With that said... I hope this helps some one... ^_^
I have just figured this thing out and soon after noticed that there is a thread with a video showing the methods to remove the extra UImage from the moboot boot menu.
The video shown here http://forum.xda-developers.com/showthread.php?t=1511050 is a great way to remove the redundant UImages from the list except I figured out a easier method and also a way to choose the default OS (WebOS or CM or CN) to load when TP boots, which the video does not get into.
Once I updated to the latest CM9 V2, I rebooted and my TP wanted to boot into the Bricked_Kernel which I did not want. I would, in this case as many of you, scroll (within 3 seconds) to the right entry to boot or else, I would be needing to reboot again.
So here is what I did.
Boot into your Rom (CM9 in my case)
Install RootExplorer from the market.
Launch RootExplorer. You will be asked to grant SU. Press Yes.
Navigate into /boot folder.
Click on the Mount R/W. This will change to Mount R/O. Now you have read and write (important) access to the contents of this folder.
Find the entry UImage.Bricked_Kernel (It might be UImage.ClassicNerd or something else).
Long press the UImage you want to delete (or modify).
Delete (rename, if you want to keep it for some reason) the UImage of the old kernel
Click on the Mount R/O to set the folder for read only access before you exit.
Now when you reboot, you will notice that the MoBoot menu is missing the entry for the extra kernel that was there before. The problem now is that the default boot selection has been set to WebOS. This is because the device is looking for the missing default entry in the boot menu. So it's just going to the top of the list. If this is what you want, you can stop here but if this is not the OS you want to load by default, follow the next few steps.
Launch RootExplorer
Navigate into /boot
Click on the Mount R/W to set write access.
Find the entry moboot.default
Long press moboot.default and choose Open in Test Editor.
The entry in this text file will show the OS that MoBoot will choose to load by default. Mine had an entry "Bricked_Kernel"
Delete the entry in this file and retype the OS of your choice. Mine was "CyanogenMod" (without the "").
Exit. You will be told that RootExplorer made a moboot.default.bak was created for safety. If you are using other file explorers you might not get the automatic backup. So please make a back up of this file before you change the entry.
Click Mount R/O to set the permissions to read only before exiting.
Reboot.
Now you will see that the MoBoot has the right OS as the default OS.
For those of you that desire to make the WebOS as the default OS you can type WebOS in the moboot.default. Well, good luck.
PLEASE DO NOT CHANGE FILES IN THE /BOOT IF YOU ARE NOT SURE WHAT YOU ARE DOING!!! Only follow this guide if you are comfortable doing so!!!
Good stuff, man.
The major difference between my tutorial and yours is that Root Explorer is a paid app, whereas my tutorial uses ES File Explorer which is free.
If you have Root Explorer though, this is definitely easier.
Choosing Default OS
Or plug in the device to computer and type:
adb shell [enter]
mount -o remount,rw /boot [enter]
ls | grep uImage [enter]
sample output:
Code:
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod
uImage.CyanogenMod
uImage.moboot
uImage.webOS
echo "CyanogenMod" > /boot/moboot.default [enter]
exit [enter]
done
nomadman said:
Choosing Default OS
Or plug in the device to computer and type:
adb shell [enter]
mount -o remount,rw /boot [enter]
ls | grep uImage [enter]
sample output:
Code:
uImage-2.6.35-palm-tenderloin
uImage.ClockworkMod
uImage.CyanogenMod
uImage.moboot
uImage.webOS
echo "CyanogenMod" > /boot/moboot.default [enter]
exit [enter]
done
Click to expand...
Click to collapse
The thing is... even though I am not a total noob when it comes to using ADB commands, it's usually not the most convenient to have to deal with connecting TP to a PC, putting it in USB mode, Command Prompt, etc... a lot of steps... What I described can be done within the TP... which was my case...
cvcduty said:
The thing is... even though I am not a total noob when it comes to using ADB commands, it's usually not the most convenient to have to deal with connecting TP to a PC, putting it in USB mode, Command Prompt, etc... a lot of steps... What I described can be done within the TP... which was my case...
Click to expand...
Click to collapse
well there's more than one way to skin a robot. i personally think it's even easier running the commands in android terminal than plugging into a pc.
what if i dont have the moboot default file?
phonetec said:
what if i dont have the moboot default file?
Click to expand...
Click to collapse
Ok... can you describe your situation with bit more detail?
Are you running CM9? Or any other ICS or GB custom rom?
How did you install your android rom?
I am not aware (since I am not a dev and no where near an expert on the matter) a way to install Android other than the CM7 or CM9 method using MoBoot to push the files to TP...
So if you can outline some details of your situation, I hope someone can shed some light for you...
im running cm9 alpha 2, installed using cwm, after using acmeinstall of cm7, it defaults to webOS when i boot up and I hate it
phonetec said:
im running cm9 alpha 2, installed using cwm, after using acmeinstall of cm7, it defaults to webOS when i boot up and I hate it
Click to expand...
Click to collapse
So if you don't have Moboot in your system anymore, I think you can push it to the TP via cminstall and get the OS chooser back.
How do you get into CWM? Do you see any UImage.Clockworkmod, UImage.Cyanogemod, etc? Are you missing moboot.default? I wonder if you can just create the moboot.default file with the CyanogeMod as it's content and see if MoBoot will read the file...
cvcduty said:
So if you don't have Moboot in your system anymore, I think you can push it to the TP via cminstall and get the OS chooser back.
How do you get into CWM? Do you see any UImage.Clockworkmod, UImage.Cyanogemod, etc? Are you missing moboot.default? I wonder if you can just create the moboot.default file with the CyanogeMod as it's content and see if MoBoot will read the file...
Click to expand...
Click to collapse
i still have moboot injstalled, but when I go in /boot I dont have a file called moboot.default
phonetec said:
i still have moboot injstalled, but when I go in /boot I dont have a file called moboot.default
Click to expand...
Click to collapse
I think if moboot is still installed, it's probably looking for the moboot.default file but since in your case, it's missing, it's booting what ever is on the top of the list of the UImages. I think you can simply create a text file and name it moboot.default in the /boot directory. As the content of the text file put CyanogenMod. Change the permissions of this file once it's placed in the /boot directory to rw_r__r__ (same as other files in the folder). Change the folder to R/O and reboot... I think it will work.
Worst case I guess you will have to push moboot via pc again...
Good luck...
yeah...that did not work....oh well, I have to send it to HP for repair anyway so i'm not going to worry too much about it
phonetec said:
yeah...that did not work....oh well, I have to send it to HP for repair anyway so i'm not going to worry too much about it
Click to expand...
Click to collapse
wait... you said you used the cm7 acmeinstaller? You shouldn't be using that if you installed cm9.
Sent from my HP Touchpad with CM9!
itsDefying said:
wait... you said you used the cm7 acmeinstaller? You shouldn't be using that if you installed cm9.
Sent from my HP Touchpad with CM9!
Click to expand...
Click to collapse
Good catch. I missed that one. He should have used the new moboot. If he used CM7 acmeinstaller he probably meant he also used the old moboot also.
Why not just edit the boot via CyBoot? Just about to try it myself.....
http://www.webosnation.com/cyboot
Well, it works after a fashion. Boot into WebOS, open up PreWare, install CyBoot. Launch it, and change the default boot to Android. Reboot, and the correct CyanogenMod entry is selected by default, but it doesn't autoboot - waits for you to hit the home key. Still, better than scrabbling for the volume key and a relatively quick way to (semi) fix the issue if you don't have RootExplorer.
dirtyfrog said:
Why not just edit the boot via CyBoot? Just about to try it myself.....
http://www.webosnation.com/cyboot
Well, it works after a fashion. Boot into WebOS, open up PreWare, install CyBoot. Launch it, and change the default boot to Android. Reboot, and the correct CyanogenMod entry is selected by default, but it doesn't autoboot - waits for you to hit the home key. Still, better than scrabbling for the volume key and a relatively quick way to (semi) fix the issue if you don't have RootExplorer.
Click to expand...
Click to collapse
Very good point. As some one said, there is more then one way to skin a cat.
I found that if you use terminal emulator and entering the following is the easiest way to set the default.
su
cd /boot
mount -o rw,remount /boot
echo CyanogenMod > moboot.default
Follow this entry exactly with the spaces them reboot, it will set your default to CyanogenMod. If you want to use another default just replace CyanogenMod with whatever you are using.
This is fast and easy.
Thank me if this helps.
travisross69 said:
I found that if you use terminal emulator and entering the following is the easiest way to set the default.
su
cd /boot
mount -o rw,remount /boot
echo CyanogenMod > moboot.default
Follow this entry exactly with the spaces them reboot, it will set your default to CyanogenMod. If you want to use another default just replace CyanogenMod with whatever you are using.
This is fast and easy.
Thank me if this helps.
Click to expand...
Click to collapse
That's perfect! The point is for people to able to fix this easily on the fly. So if you don't have access to Rootexplorer, this method can be used to change the default OS the TP would load at reboot. Thanks.
Hello all you Triple-Booters out there! I would like to introduce to you:
Convert2Dualboot-SD Tool
What is this you ask?
This is a little tool that I've put together that will convert any standard flashable roms for our Nook Color to be DualbootSD compatible. No more waiting on my lazy arse to update you guys!!! I used APK manager as a base for my script. I've written 3 different versions that will run on Linux, OSX and Android. All neccesary binaries are included with each version.
Click to expand...
Click to collapse
Can I use any kind of flashable zips?
Yes and no. You could use any standard flashable "rom" or "gapps" zips only.
Click to expand...
Click to collapse
How do I use it?
You drop a standard rom .zip into a "rom-to-modify" folder. Then execute a shell script that will give you an option to convert it for flashing to Primary or Alternate boot on the DualbootSD.
Click to expand...
Click to collapse
Can I use any CWM Recovery for flashing?
Absolutely not! Only use the CWM Recovery that was included with the DualbootSD.
Click to expand...
Click to collapse
Will you be updating this to add new features and stuff?
Not sure what features I can add, but you can always check the CHANGE LOG in post 3.
Click to expand...
Click to collapse
Can you give us step by step directions on how to use this?
Of course! See second post for more details.
Click to expand...
Click to collapse
***Disclaimer: Usual disclaimer applies here as well... you use this at your own risk, I am not responsible for anything that happens to any of your devices. You assume all responsibility when using this tool.***
Credits:
Daneshm90 for the APK Manager Script I used as a base
Pinako/Inportb/Jyio/Boss! - for his Android binaries
DizzyDen - for porting this over to DOS and his many ideas to get the script to where it's at
HacDan - for some bash guidance
If I forgot someone else, please notify me.
Convert2Dualboot-SD Tool-README
Convert2Dualboot-SD-Linux v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up terminal and cd into Convert2Dualboot-SD-Linux
4-At the termninal prompt execute the C2DSD script
Code:
$ sh convert*
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Now browse to the C2DSD folder and you can find your DualbootSD modded rom file either in "Primary-Mod" or "Alternate-Mod" depending on your earlier selection.
9-Copy that file to the /sdcard partition of your DualbootSD
10-Boot to CWM Recovery that is included with the DualbootSD
11-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-OSX v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up terminal and cd into Convert2Dualboot-SD-OSX
4-At the termninal prompt execute the C2DSD script
Code:
$ ./convert*
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Copy that file to the /sdcard partition of your DualbootSD
9-Boot to CWM Recovery that is included with the DualbootSD
10-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-Android v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-This will allow you to modify the zip files directly on your Nook
2-Extract the zip file you just downloaded to the root of your DualbootSD /sdcard partition.
3-The folder should be named c2dsd
4-In the c2dsd folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
5-Open up any Terminal Emulator and cd into the c2dsd folder which should be "/sdcard/c2dsd"
6-At the termninal prompt execute the C2DSD script
Code:
$ su
# sh convert*
7-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
8-Choose your option and wait while it does its thing.
9-Once it's finished you can exit the program by choosing "0"
10-Now you can choose to boot to CWM Recovery that is included with the DualbootSD
11-Choose "install zip from sdcard" and browse to either "Primary-Mod" or "Alternate-Mod" depending on your earlier selection.
12-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-DOS v1.3
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up command window and cd into Convert2Dualboot-SD-DOS or create a shortcut on your desktop
4-At the command prompt execute the C2DSD script
Code:
convert2dualboot-sd-dos
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Copy that file to the /sdcard partition of your DualbootSD
9-Boot to CWM Recovery that is included with the DualbootSD
10-Flash and enjoy!
Click to expand...
Click to collapse
And that's all she wrote... well he, being me.
If I've helped in anyway. Don't hesitate to hit the thanks button.
Change log:
v1.4 (6/8/2012)
-Fixed gapps being zipped with rom when converting rom & gapps together
-Added SDCacheMount to converted roms (see the SDCacheMount thread for more info)
-Fixed mkimage binary executing error for Linux version
-No DOS update yet.... DizzyDen?????
-Thanks goes to xda user "shumash" for the SDCacheMount addition into the script
v1.3a
-Mkimage error on Android Script fixed.
-Mkimage is dependent on 'libmusl.so' which I did not include and linked in the tools folder. I overlooked this tidbit because I had "BOTBREW" installed on my system so it never complained about linking to it.
v1.3
-I effed up on the script!
-RASTAVIPER kept asking me about issues with his gapps. Apparently the mod for Gapps Alt Boot had the wrong mount points inserted into the updater script. NOW I SEE IT!
-Also in the DOS version. Prep of ROM Alt Boot had the wrong mount points as well. Sorry guys.
-It's been fixed and uploaded. Please don't use v1.2 anymore. Thanks.
v1.2
-Changed up UI layout of script: Please re-read README from post 2 above for edited instructions.
-Edited script to speed up mod process (Thanks DizzyDen!)
-Added option to mod both "ROM & GAPPS" on the fly
-Android version now has a tool.img file. This makes modding quicker and safer.
-Added DOS version ported by DizzyDen! (Thank you sir!)
-Modding for EMMC dualboot version in the works???? (That's if you guys want it)
v1.1
-Added gapps option
-Cleaned up some scripting behaviors
v1.0
-Initial release
Well.. after some thought, it really didn't make sense to release this without an option to mod gapps for the DualbootSD. I mean what good is a rom without gapps?!
Convert2Dualboot-SD v1.1 is up if anyone wants to try.
Check post 3 for all changlogs.
Thanks,
Racks
Taking advantage of the opportunity to try something new, I made a dual-boot card for my sister-in-law.
This is cool. I actually haven't tested the card yet as I have my device flashed to internal and have modded the recovery some. I haven't backed up any of the changes I made (I know, I know) and don't want to have to do it again.
I may try updating the card now that you've included gapps, though. I hadn't made a bootable card since I first rooted this thing, and to be honest it was by accident even that time. So I was wondering how to get gapps, was thinking about setting an alt-recovery just for that.
But anyway, I hadn't looked at how to do the gapps yet, maybe it was easier than that. But this seems even easier.
Cool, man! I bet the dual/triple booters will love being able to make their own updates. The experience I had last night couldn't have been easier. My wife got me and her sister the Nooks at the same time, I am excited for her to see what I have been talking about the last six months.
I will be sure to try this once my NC gets here. Thanks!
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
shumash said:
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
Click to expand...
Click to collapse
DB zip? Sorry, but what are you referring to with that?
And could you also let me know which one you used? OSX, Linux, Android?
Edit: That might just be the stupid __MACOSX hidden folder that osx likes to include Forgot to exclude that and the .gitignore file when zipping. Although they aren't detrimental to running the C2DSD Tool, you can choose to delete them if you wish.
Thanks,
Racks
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
DizzyDen said:
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
Click to expand...
Click to collapse
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
racks11479 said:
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
Click to expand...
Click to collapse
Sounds like a plan... I just got in from work... and am off tomorrow.
DizzyDen said:
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
Click to expand...
Click to collapse
racks11479 said:
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
Click to expand...
Click to collapse
+1 from a meathead windows user here.
Sent from my NookColor racks tripple boot using Tapatalk 2
racks11479 said:
DB zip? Sorry, but what are you referring to with that?
And could you also let me know which one you used? OSX, Linux, Android?
--SNIP--
Thanks,
Racks
Click to expand...
Click to collapse
Sorry for being vague. I meant the modded dualboot sd zip build. But I tried it again and it was fine, so let's say no more about it, eh?
On a related note, since you're so motivated now, how about creating those separate cache1 and cache2 partitions so that we don't have to wait so long to boot between the two?
Anyone who tried the new modding option and that would like to share with us which CM9 rom (nightly) did he convert and is working fine after conversion?
spdsl said:
+1 from a meathead windows user here.
Sent from my NookColor racks tripple boot using Tapatalk 2
Click to expand...
Click to collapse
Was hoping to have something before I had to go to work this morning... didn't get it completed...
to keep as close as Racks' I will have a DOS batch file available sometime tonight...
True Windows GUI version will be available early in the week.
Keeping with Racks' desires... both will be open source and stored on his github... I use AutoIT for windows programming these things.
shumash said:
On a related note, since you're so motivated now, how about creating those separate cache1 and cache2 partitions so that we don't have to wait so long to boot between the two?
Click to expand...
Click to collapse
Racks, I just sent you a PM that might help with this issue.
shumash said:
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
Click to expand...
Click to collapse
UPDATE: I converted the latest Mirage build, and when I tried to flash it, Recovery complained that it wasn't a valid zip file. Checked it and the same weird file was in the converted flashable zip. When I ran the conversion a second time, all was good and it flashed as expected. I had deleted all the extraneous _MACOSX and .gitignore file stuff prior to running it the first time. BTW, the problem in the quoted post was when I converted an ICS build the first time, too. Racks, do you think that there is something that occurs the first time the script is run that is different on subsequent runs that might account for this?
Just installed nightly 28.4 without Opengl and then gapps which appeared in the folder Primary Mod after conversion.
After that I cant get inside shop.I click to open it and it gets me back to main menu.
Any ideas?Reflashing of gapps didnt work.
RASTAVIPER said:
Just installed nightly 28.4 without Opengl and then gapps which appeared in the folder Primary Mod after conversion.
After that I cant get inside shop.I click to open it and it gets me back to main menu.
Any ideas?Reflashing of gapps didnt work.
Click to expand...
Click to collapse
Primary mod is for Primary boot. Default primary boot was CM7, so I'm assuming you formatted /system1 & /data1 before flashing?
Could you also unzip the contents of the converted gapps zip. And check the updater script. All /system variables should be /system1.
-Racks
I didn't format anything before flashing. I thought this as an upgrade, so after conversion I just proceed to flashing.
Finally, I flashed your own gapps that you have at your dualboot topic and now everything is back to normal.
Unfortunately, even after this upgrade, I still continue to deal with FC issues of mail, Facebook and of other random apps.I think there is some problem with my card and CM9, since CM7 runs perfect from emmc or from same mem card.
Unleashed from my Revolutionized Desire HD