Just throwing an idea out there, and since it's for developers (specifically people who make their own recovery images) I assume this is the right section.
Since we have 'control' over the recovery image on our phones, would it not be possible to add a little script to an update.zip that a suitably modified recovery image could extract and run to interactively prompt the user for various Rom options? I'm thinking specifically of kernel choices, but it could be extended to almost anything that needs to be done prior to booting the installed image.
Imagine installing a rom, and during the install you got a little menu like this:
1: RamHack, BFS Kernel
2: RamHack, CFS Kernel
3: No-RamHack, BFS....
etc...
inefficient, it adds extra baggage to rom, and more things can go wrong. what would you rather downlaod a 90mb file or a 110 mb file.
Which would you rather download, one 110MB ROM or 2 90MB ROMS?
I'm pretty sure there's more than a few people who'll download different variations of the same ROM so they can see which is faster, how much easier would it be to just download one thing and then choose which options you want in there without downloading anything else.
I believe it is entirely possible. As a matter of fact, I was working on a ROM project that would have an interactive installer from the update.zip that would selectively install different features, apps, customization, themes, etc., based on the recovery menu application. It would use a lot of the /cache for temp space, though, as the installer application and its resources and configuration file, and later, the necessary parts of the ROM itself, would need to be unzipped before the install can run, if I recall correctly.
Does anyone have a good link to a reference for the command syntax for the /META-INF/com/google/android/update-script file? I'll go search for it in a few moments myself. I could probably make a simple ROM installer that chooses between ROM X and ROM Y based on a key input, as a proof of concept. I'll test it myself, I don't really mind half-bricking my device for science. (As long as I don't need to touch the SPL/Radio, that is.)
Update: Some creative searching finds me this:
JesusFreke said:
Assuming you mean update-script in an update.zip update, you will need to either look at existing update-script files for an example of the syntax, or look at the source of the recovery program in the android source
Click to expand...
Click to collapse
There's also a "make-update-script.c" file I'm seeing here and there, I'm trying to find the file in the Android source.
Update 2: From install.c at donut from cyanogen's android_bootable_recovery:
Code:
#define ASSUMED_UPDATE_SCRIPT_NAME "META-INF/com/google/android/update-script"
#define ASSUMED_UPDATE_BINARY_NAME "META-INF/com/google/android/update-binary"
and in commands.c, toward the bottom at register_update_commands is all the commands defined, and above that are all the functions they carry out.
sorry about that deicist i was sleepy when i wrote that so i must have been cranky yea i guess that is a fine idea, with just 30 more mb you have like 300mb worth of stuff. and you can pick which 90 mb you want.
markolo25 said:
sorry about that deicist i was sleepy when i wrote that so i must have been cranky yea i guess that is a fine idea, with just 30 more mb you have like 300mb worth of stuff. and you can pick which 90 mb you want.
Click to expand...
Click to collapse
Well, on the 32B platform with the Death SPL (my phone) we have the following partitions of the internal NAND memory (mtdblock*) from the df and mount command:
NAND 3: /system 92160kb - OS partition, static and read-only
NAND 5: /data 91904kb - User, system config, app config, and apps (without a2sd)
NAND 4: /cache 30720kb - OTA cache, Recovery/update config and temp
And I'd assume NAND 1 and 2 are the kernel, ramdisk, and bootloader config.
So the ROM wouldn't exceed 92MB installed (most leave some room in /system for hacks and updates). And the update process doesn't ever really "flash", per se; it just formats, copies files, and sets permissions and initialization configs, like Windows or Mac.
So the files that are common to the different ROMs being packaged don't need to be duplicated, only the ones that are changed (like a boot.img, or 32A/B compatibility, or different apps). The update script and chooser menu will decide which files to copy. Meaning the ROM package in and of itself shouldn't really need to exceed 128MB, even if choosing from a wide variety of platforms. And upon installation, the system might take less than 32 MB.
yeah, what he said ^
The scenario I was thinking about specifically was SuperD. If you look here:
http://forum.xda-developers.com/showthread.php?t=613809
There's 8 different downloads there. How many files are actually different between those 8? I guess the themes mean a lot of application files are different (due to having different resources in them) but the underlying framework files will be pretty much the same I think.
Deicist said:
yeah, what he said ^
The scenario I was thinking about specifically was SuperD. If you look here:
http://forum.xda-developers.com/showthread.php?t=613809
There's 8 different downloads there. How many files are actually different between those 8? I guess the themes mean a lot of application files are different (due to having different resources in them) but the underlying framework files will be pretty much the same I think.
Click to expand...
Click to collapse
I could download them all, and find the differences of each. It would be cool if a ROM like this were available in a single download, from which you would choose the content from the device before flashing.
Also, inspired by talking about this, I wrote up a guide on the update-script in the package file. It's still not finished, but it'll be the only guide available for that syntax yet (trust me, I couldn't find one myself ). Link's in my sig.
I'm surprised that nobody's mentioned the Droid... the sholes.info rom (now called droidmod) have used a .tgz archive instead of a .zip, the .tgz installs have always allowed this customization, droidmod makes one of the most common recovery's AND rom's. (SPRecovery/Droidmod).
It give you the option to choose what launcher to install, what theme, what apps to remove.
page here: http://droidmod.org/news/droidmod-v1-0-is-out/
how big of a ROM are you thinking about?
There are roms (WG etc...) that offer more than one kernel as update.zip you can flash over an existing installation of your rom instead of adding all the stuff to one big file. also you can download themes for several roms/for metamorph.
so why would you want some big install script instead of just downloading the files you like and flash it?
jmhalder said:
I'm surprised that nobody's mentioned the Droid... the sholes.info rom (now called droidmod) have used a .tgz archive instead of a .zip, the .tgz installs have always allowed this customization, droidmod makes one of the most common recovery's AND rom's. (SPRecovery/Droidmod).
It give you the option to choose what launcher to install, what theme, what apps to remove.
page here: http://droidmod.org/news/droidmod-v1-0-is-out/
Click to expand...
Click to collapse
Is the Droid's recovery image capable of running on the G1, and/or is it open-source enough to be cross-built to the G1? If so, we could port it here. Only problem there though, is that all the roms are in update.zip format for the G1 already, we'd need to make it dual-compatible if we don't want to split the community and annoy generally everyone ("My rom only supports TGZ recovery!" "ROMs are in ZIP format, and I will not make a TGZ one for those unfortunate enough to use the other Recovery!")
domenukk said:
There are roms (WG etc...) that offer more than one kernel as update.zip you can flash over an existing installation of your rom instead of adding all the stuff to one big file. also you can download themes for several roms/for metamorph.
so why would you want some big install script instead of just downloading the files you like and flash it?
Click to expand...
Click to collapse
Well, for one, devs need to host one file only, and users need to download one file only. The file won't be much bigger or more complex at all, really. And the way things look on the recovery side, we could probably put a selection of themes in with the updater and patch them in post-install with a Metamorph script straight from recovery. That way, the rom is as you want it out-of-the-box, no multiple reboots, etc.
Also, those scripts that usually run on first-boot, like zipalign, dexopt, apps2sd etc. should run from the recovery environment, instead of before the Android bootanimation (I do get tired of hearing "This ROM will take a LONG time on the first boot. If it's stuck at the G1 screen, just wait 10-30 minutes.")
So what would you rather have, one single ROM (G1_Android_ROM_v1.17.zip) for each version released,
or six different ZIPs to flash (G1_Android_ROM_10MB_CFS.zip, G1_Android_ROM_Greentheme.zip, G1_Android_ROM_Bluetheme.zip, G1_Android_Nowipe_GApps.zip)?
Would you rather select what you want to include at flash (and be able to change things like themes or features after flashing), or have 20 different files to choose from, wiping and flashing on each?
I am aware of the no-wipe upgrades for many ROMs, but they can get confusing (I once flashed a CFS_10MB.zip that was for a Hero ROM, stupidly thinking that it might have been for the Eclair that I just downloaded.) Needless to say, I had to wipe and reflash. Again.
TylTru said:
Is the Droid's recovery image capable of running on the G1, and/or is it open-source enough to be cross-built to the G1? If so, we could port it here. Only problem there though, is that all the roms are in update.zip format for the G1 already, we'd need to make it dual-compatible if we don't want to split the community and annoy generally everyone ("My rom only supports TGZ recovery!" "ROMs are in ZIP format, and I will not make a TGZ one for those unfortunate enough to use the other Recovery!")
Well, for one, devs need to host one file only, and users need to download one file only. The file won't be much bigger or more complex at all, really. And the way things look on the recovery side, we could probably put a selection of themes in with the updater and patch them in post-install with a Metamorph script straight from recovery. That way, the rom is as you want it out-of-the-box, no multiple reboots, etc.
Also, those scripts that usually run on first-boot, like zipalign, dexopt, apps2sd etc. should run from the recovery environment, instead of before the Android bootanimation (I do get tired of hearing "This ROM will take a LONG time on the first boot. If it's stuck at the G1 screen, just wait 10-30 minutes.")
So what would you rather have, one single ROM (G1_Android_ROM_v1.17.zip) for each version released,
or six different ZIPs to flash (G1_Android_ROM_10MB_CFS.zip, G1_Android_ROM_Greentheme.zip, G1_Android_ROM_Bluetheme.zip, G1_Android_Nowipe_GApps.zip)?
Would you rather select what you want to include at flash (and be able to change things like themes or features after flashing), or have 20 different files to choose from, wiping and flashing on each?
I am aware of the no-wipe upgrades for many ROMs, but they can get confusing (I once flashed a CFS_10MB.zip that was for a Hero ROM, stupidly thinking that it might have been for the Eclair that I just downloaded.) Needless to say, I had to wipe and reflash. Again.
Click to expand...
Click to collapse
You could just have flashed the original rom without wipe.
Would be a step forward if you could simply put roms and additional files in folders... maybe even whole zip files containing some updates and an xml like file to describe them. This would guarantee compatibility with earlier boot images (just unpack the updates in the zip). Tar might work better than zip as it is not compressed thus faster afaik.
http://droidninja.com/?p=26334
We got ninja'd. Apparently the Droid Does exactly this.
So let's get to work on porting it! Like this comment says, I'm working on finding the source code to a good Droid recovery image (sadly Droid hasn't its own forum here), and if it's closed source, I'll get on reverse-engineering a .tgz rom to see exactly how it works.
TylTru said:
http://droidninja.com/?p=26334
We got ninja'd. Apparently the Droid Does exactly this.
So let's get to work on porting it! Like this comment says, I'm working on finding the source code to a good Droid recovery image (sadly Droid hasn't its own forum here), and if it's closed source, I'll get on reverse-engineering a .tgz rom to see exactly how it works.
Click to expand...
Click to collapse
This is pretty awesome. I was going to say, we could easily run bash scripts but this is so much better.
This needs to be merged with both Amon_ra's recovery and the new 2.x based recovery...
Related
I hate to make a thread on this but would like to get started soon with learning how to root roms and add the kernel for multitouch and tethering. This is more for my personal use since I just want a stock rom with all the root benefits like jf use to and theses are the questions I have.
1. Will I have to take the update.zip file and extract everything and modify it then resign and I'm done?
2. I read some info on adding busybox and root which seem easy but when I run the chmod command and such everything will be through adb and the files will be on my pc so do I just make sure its all in the right directory and file path?
3. Where are the wallpapers stored in builds along with animations I will be looking into the framwork/framework-res.apk later but still curious
4. The modified kernel for tethering and multitouch is located where along with the market.db file?
5. What is meta.inf and how easy is it to make the cpu 528mhz standard also not sure what BFS and ASOP are haven't been keeping up.
P.S. I would really appreciate some help on this and I don't mind reading if this information is somewhere else so please provide a link and as always gotta show love to those who started this like JF, Hakuro, Cyanogen, Drizzy, and many more like daproy and kornub did a lot of helping.
I hate to make a thread on this
Click to expand...
Click to collapse
You mean you hate starting threads in the correct place?
Thats a fine line here. Although it is a question, it is specifically a development question. Its not a which rom do i choose?
Although android is "open source" these people dont give a **** about people trying to learn how to develop. They will pull the google line or something.
yeah me 2
Trying 2 learn
Im a noob, so I can only answer two of thosew questions
1. Anytime you modify your update.zip you will have to resign before trying to flash it onyour device.
5b. BFS: Brain **** (simple) Scheduler, something to do with the priority of running proccesses or something http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler. AOSP stands for Android Open Software Project, which i believe is just googles standard rom really (but I may be wrong)
I recommend you try out this rom though, kind of like JF but for Donut http://forum.xda-developers.com/showthread.php?t=538456
Very Sorry, double post
Thanks! I'm actually using that rom and its what has me so interested in this cause I hate having to flash another update.zip to get the full root benefits when JF just made everything available in one nice package but looks like I will just have to go through trial an error unless I get some more feedback cause switching between cyan 4.1.11.1 and JF1..51 is killing me and taking up space on my card.
With my little to no knowledge, replacing the boot.img and some files in system/bin with the ones provided in theofficial expansion pack should give you all that you need. With no extra apps.
yeah me 2
Yeah me too
This a simple and quick guide for everyone who wana make or just modify their own HTC DESIRE ROM's.(Rooted ones)
For example you downloaded a nice ROM from one of devs here, but they removed some application that you cant live without. Now you dont need to beg them to add those files back, simple add them your self and flash your rom.Missing APK's you can get simple by downloading any stock rom, than extract them and put them in your new ROM.
After you extracted files provided (c root recomended), you will see 2 maps
"Sign ROM" and "tools"
Signing ROM's:
After you modifed your ROM zip file, simple put it in "Sign ROM" map, and rename it to update.zip.Than run "Sign.bat" After the process is done you will get another zip called "update_signed.zip" which you can now put to your SD card and your ready for flashing. Note:JAVA SDK files are included, you only need to have normal java installed.
http://img99.imageshack.us/img99/2921/signedrom.jpg
Pushing recovery files from windows:
Now to flash your ROM you dont need linux anymore, simple enter recovery (Power button+back, than select recovery...), and than in the map "tools" run recovery-windows.bat. Than you will get standard screen where you can flash your roms, partition SD, clear data and so on..
NOTE: You need to have HTC Sync driver installed or your phone wont be detected (you can get them from HTC)
http://img213.imageshack.us/img213/1894/pushfiles.jpg
If you have any questions, suggestions or if i wrote something wrong i will be happy to answer/corect them.
http://hotfile.com/dl/43311449/92d9ee6/Desire_Tools.exe.html
http://www.megaupload.com/?d=JNI68MWZ
http://rapidshare.com/files/388849647/Desire_Tools.exe.html (Thanks pympster for link )
http://www.robertolsen.no/desire_tools.rar
(Thanks GeoTrail for link)
would this tool work for the HTC Legend aswell?
For signing roms yes, for pushing files not sure if Desire and legend use same files..
Ok this one is simple, but this is only how to add/delete several apps.
How about going little bit more deeper?
Well if you wana go deeper, you can download costom kernels with overclocks or low volatege and replace the ones in rom, or those circle battery mods or costom boot sounds and so on...Basicly your replacing/modifying original files. But this is just quick basic guide for basic stuff, let real ROM developing and costomizing to the developers who are good at it.
As far as hardware support goes is it the kernel that provides everything? Basically if I take an N1 rom (like cyanogen 5.0.6) and change to a desire kernel, is it likely to just work perfectly or are there other bits in the ROM that are likely to need changing?
Of course you can just use dsixda's Kitchen which is cross-platform and quite straightforward to use.
You just add the update.zip file you want to change, remove/add any apps you want and make any advanced changes you want too.
Select Build ROM and it'll create the new update.zip that you can flash to phone.
I've used it on my Desire without problem for adding/removing apps.
Well that kitchen is nice, but still..you need to downlaod virutal machine to make it run under windows or Cygwin tool than download JAVA SDK..setup lots of things.
My point of this thread was just vey basic and simple way to quickly add/remove/costomize files from ROM, without installling and downloading lots of tools, and quickly install it on Phone and test.
Sorry, I wasn't meaning to undermine your work. No doubt you've spent a lot of time creating this and trying to contribute to the community. It's far more than I can say for myself.
I was just pointing out there's something already out there, and more capable than this.
It's definitely good to see people helping out the members and this is definitely something useful
Everything is cool TheAshMan, and thanks for you link, im sure some enthusiastic people will try some advance things like that. But even my self im not big expert about Linux and phones, i do have great knowledge about windows and computers, but dont have much time for this area.
Screen shots on how to use this would help, I've come from cooking my own WinMo ROMs and wuld like to give this a try if possible
Also, as I use W7 x64 is it best to run the .bat files as an admin? Had issues using Windows methods in the past so have been using Linux to get rooted
I'm also using Windows 7 x64.
About running bat's as admin its not necessary unless you have some kind of UAC high settings, or running on some kind of limited user account. I never run this bats as admin and they work fine.
Basicly download some stock rom, or someones rom. And simple add or remove files inside rom.zip/system/app/
If you dont like facebook for example, just remove Facebook.apk and facebook.odex(if its present).
After your done with that, rename ROM to update.zip and put it in the folder
C:\Desire Tools\Sign ROM\ and excecute "Sign.bat" , and it will create signed rom with name update_signed.zip.
http://img99.imageshack.us/img99/2921/signedrom.jpg
This is just some base, im not gona explain you about ROM deodexing, framework, boot images kernels and stuff, because im not expert at this.
Now you can put that file to root of your SD card.
Now you can test it on your phone.
Shut down your phone. Turn it ON while holding back button.You will see Bootloader selected, press power button again. Than Recovery will appear, you can navigate down with volumen UP AND DOWN and select Recovery and press POWER button again to select it.Phone with Red triangle will appear on your phone. Now go in map C:\Desire Tools\tools and excecute "recovery-windows.bat"
http://img213.imageshack.us/img213/1894/pushfiles.jpg
And on your phone you will get that screen with green letters where you can select to 'Flash zip from sdcard' ,where your signed rom will appear.(You need to wipe data before from the same menu)
I hope i made some thing clearer im writing this from work so dont have much time
Right, got a ROM and added 2 .apk files to the /system/app folder and now got a signed_update.zip...is that it? They'll be on the device from the start?
Seems to simple to me!!
How can you add a new radio? Or change the version number in About phone>Software?
Yea thats it. About those other things..Google is your friend...
edit mate
when i flash it says:
E: Can't find update script
rom.zip/META-INF/COM/google/android/update-script
Did you touch that in ROM? If you didint, than you removed something that you shouldnt.
Can u also remove apps from rom that you don't like by this method.
-------------------------------------
Sent via the XDA Tapatalk App
Yea, thats the all point of everything i wrote here. Very simple way of very quickly removing apps that you dont want from the rom before flashing it.
Also, you need to watch out, and to a bit experementing. Because sometimes if you remove some crucial app, you will start getting random crashes of applications or random bugs. Allways make a copy of original rom.
For example if you remove HTC-IME.apk, you wont have any kind of keyboard in the rom. Making it un-usable
Somebody already asked how to add radio update, is it maybe included in Modaco r3 rom(the one without apps2sd and modaco additional stuff)?
Tnx for help
Dual Boot Support
DualBoot Helper APP is now on the market! (See bottom of this post for more info)
DISCLAIMER: I am not responsible for anything, ever. It is not my fault if you do not read. I do not explain things because I enjoy banging on the keyboard. If you do not read this entire post before jumping in then do not expect me or anyone else to be much help. By following this guide and any links YOU assume all responsibility for your device and anything that happens with it.
What is it?
Dual booting allows you to run two separate roms on your device at one time. It is done by intercepting the mount points during the startup of the device. This is accomplished by checking the sdcard for a specifically named file when the kernel first loads and uses the appropriate files to boot with the correct partitions. Reading from the sdcard is slower than reading from the internal memory of the phone so the speed of your sdcard will drastically determine the speed any rom runs. On the same note a rom flashed to the sdcard will take longer than usual on the first boot.
What does it do for me?
Running two separate roms has many uses for just about everyone. Users can use dual booting to try different roms, themes, apps, modifications, or anything while keeping their existing installation intact. The uses are just about endless. Besides testing different roms, this allows the user try these things and make sure they are compatible and stable before pushing the changes to their internal memory. Rom developers have all of the above options plus a few. Rom developers can additionally use dual booting to test builds of their roms without fear of soft bricking their device. For advanced users, you can mount the partitions of the other rom (be it sdcard or internal) and fix bad apk files or messed up files. The options really are limitless!
What do I need?
Sdcard 2GB or larger
Dual boot compatible kernel
Other things I should know...
*The kernel MUST support BOTH roms you flash. Unfortunately this means you can NOT mix froyo and gingerbread roms. Make sure you know what the kernel supports before you flash anything!
*If you compare roms, benchmarks will hold no value due to the sdcard being so much slower than internal memory.
*Faster sdcards will perform better than slower ones. Note: the stock 16GB sdcard is a class 2 which simply classifies it's minimum speed. A higher class sdcard will more than likely perform faster but the class rating is a minimum and not a maximum. It is entirely possible that a certain class 2 card can out perform a different class 6 card. Keep this in mind when researching to buy a new faster sdcard. More info in this post.
*First boot takes longer than usual. Up to 15 minutes! Please wait until the rom boots and the initial media scanner is done before you judge usability.
*Using a rom from the sdcard will cause the sdcard to wear faster. This is due to many more reads and writes of data than normal. The Epic simply does not have the internal capacity to run dual roms on the NAND. That being said the sdcard is our next option. While it may reduce the over all life of the sdcard keep in mind there are other android devices like the Nook Color and the other Galaxy S phones that have internal sdcards running the Android operating system. My personal opinion with is with other devices running off internal sdcards and with the price of sdcards getting cheaper and cheaper it was worth it to explore this option for the Epic.
Ok ok, so how do I get started?
I am going to break the steps down into sections. Please read everything to ensure you understand what all is involved in getting everything working. I recommend making a backup in Clockwork Mod and saving it to your PC before you even get started.
Section 1 - Setting up the environment
Step 1. Flash a compatible kernel (Kernel developers, PM me if you add my dual boot support to your kernel and I will update the list below) Remember you can NOT mix a eclair, froyo, or gingerbread roms and the kernel MUST support both roms!
Currently compatible kernels:
Genocide 2.0 Supported Roms: EC05, EB13, and DK28
Section 2 - Preparing sdcard
Important information!!!! This will destroy ALL data on your sdcard so if you lose pictures of your dog, cwm backups, nudies of your spouse, etc then you can't blame me. BACKUP YOUR SDCARD!
The easy way:
Reboot into recovery mode with a program like Rom Manager, Quick Boot, or type 'reboot recovery' from a terminal. (NOT 3-finger boot to recovery...this will NOT work)
The easy way WILL erase your sdcard with NO confirmation....you have been warned!
Choose one of the following flashable zips to automatically partition your sdcard
DualBoot_Partition_RFS.zip
DualBoot_Partition_EXT4.zip
The manual way:
Reboot into recovery mode with a program like Rom Manager, Quick Boot, or type 'adb reboot recovery' from a command line. (adb commands assume you have a working install of the Android SDK)
While in recovery issue the following commands:
Code:
adb shell
cd /sbin
./dbpart.sh --help
I put many hours into the partitioning script to make it as simple to use as possible. Simply follow program usage instructions.
Section 3 - Preparing a rom
Since we have blank partitions on the sdcard we need to populate them with data. There are multiple ways to accomplish this and you can choose which solution best suits your needs. I am not going to cover ALL methods here but enough to suffice any likely scenario needed.
The dd method will clone your current setup to the sdcard (these commands may take up to 15 minutes)
The easy way:
Flash this dd script: DualBoot_Clone_to_sdcard.zip
The manual way:
Code:
adb shell
dd if=/dev/block/stl9 of=/dev/block/mmcblk0p2
dd if=/dev/block/stl10 of=/dev/block/mmcblk0p3
dd if=/dev/block/stl11 of=/dev/block/mmcblk0p4
Preparation is complete. Please skip down to booting from sdcard.
The flash method is for flashing a new rom to the sdcard.
The easy way:
There is no sure fire easy way just yet. Stay tuned though.
The manual way:
This method is not that difficult so there is no need to be intimidated by it. It requires editing a few lines of the script that Clockwork Mod executes when flashing a rom or addon. For this example I am going to use a file named epicrom.zip but you can use any name you wish.
Step 1. On your PC, open epicrom.zip (I recommend using a program like 7zip)
Step 2. Navigate to the META_INF\com\google\android\ folder.
Step 3. Drag the file updater-script out of the zip to your desktop.
Step 4. Open the updater-script file with a text editor such as notepad (I recommend notepad++ or textpad)
Step 5. Change every instance of /dev/block/stl9 to /dev/block/mmcblk0p2
Step 6. Change every instance of /dev/block/stl10 to /dev/block/mmcblk0p3
Step 7. Change every instance of /dev/block/stl11 to /dev/block/mmcblk0p4
Step 8. Delete the entire line for any lines that contain /dev/block/bml7 or /dev/block/stl7 to disable flashing another kernel and breaking dual boot support.
Step 9. Save the file and drag and drop it back into epicrom.zip and let it replace the old one.
Note: If you get a status 6 or some other error when trying to flash it is likely you made a typo or your text editor did no save the updater-script file correctly. Recommended action is to correct the typo and/or use one of the recommended text editors note in Step 4.
Section 4 - Flashing to sdcard
Flashing a rom from this point is the same as you usually do. Put the modified rom on your sdcard and flash with Clockwork Mod like usual. I recommend doing a backup in Clockwork Mod BEFORE you flash in case you messed anything up by accident and end up flashing over internal memory when you meant to flash to the sdcard.
Section 5 - Booting sdcard
To boot from the sdcard place a file in the root of your sdcard called 'bootsdcard'. If you named it correctly upon reboot, the kernel will load the rom from the sdcard and not internal memory.
To boot back into internal memory simply remove this file from your sdcard and reboot.
You can switch back and forth using this method. If the file is there it boots sdcard, if the file is not there it boots normally. Pretty simple right?
Section 6 - Other flashables (not roms)
Themes, addons, and anything else that is flashable with Clockwork Mod must be modified in the same fashion as the rom. Use the same procedure documented in Section 3, The flash method.
Kernel Developers:
If you would like to add dual boot support to your kernel please refer to this commit: https://github.com/Rodderik/Genocide-Kernel/commit/a5dfd9f369ae4f2c90c1e7fc7d8995f88f72bd01
I will update this section if I push any specific changes to dual booting.
Now with an APP!
DualBoot Helper
VenumX coded up an APK to work with Clockwork Mod to run the scripts.
http://forum.xda-developers.com/showthread.php?p=15486144#post15486144
Questions, concerns, gripes, or complaints can be left in this thread. If you need to report any problems please be as detailed as possible.
woot
Thats my boy!!!! Make me proud!!!!!!!!!!
w00t! go man go!
Holy ****! This is huge! Thanks!
Sent from my SPH-D700 using Tapatalk
OMFG this is way amazing ;P
Thr genious once again with another first
Sent from my SPH-D700 using XDA Premium App
Edit
nevermind...
good work!!!!!!!!!!!!
davidrules7778 said:
I got a question...
Would i be able to run dual versions of android
Ex 2.1 and 2.2
or 2.2 and 2.3
if the kernal is compatible?
Click to expand...
Click to collapse
if the kernEl was compatible yes...but none of them are...and likely won't be
Good damn job bro.. Let's keep the dev community developing
Rodderik said:
if the kernEl was compatible yes...but none of them are...and likely won't be
Click to expand...
Click to collapse
what if u made one of the eclair kernal compatible or gingerbread whenever we get custom kernals for it?
Or is it not possible to make eclair kernals compatible?
i think i could make a GB kernel now.. but you wouldnt be able to mix gb with froyo or eclair, because a GB kernel wont boot those builds..
Awesome work bro! Amazing...simply amazing!
chris41g said:
i think i could make a GB kernel now.. but you wouldnt be able to mix gb with froyo or eclair, because a GB kernel wont boot those builds..
Click to expand...
Click to collapse
yup i'm going to help chris41g put together a gb kernel for you guys
as far as eclair...honestly who still uses eclair? and why?
Rodderik said:
as far as eclair...honestly who still uses eclair? and why?
Click to expand...
Click to collapse
Just what I was thinking.
Tested on EC05 just now. I uhh... likey? =)
to bad no multi android versions though =(
why cant the kernel read off the sdcard? do you need drivers from samsung once again?
Shoulon said:
Tested on EC05 just now. I uhh... likey? =)
to bad no multi android versions though =(
why cant the kernel read off the sdcard? do you need drivers from samsung once again?
Click to expand...
Click to collapse
well the kernel is stored in bml7 and called by sbl/param during boot so unless we can get a bootloader to intercept the initial loading of the kernel and pass it off we are stuck with one kernel at a time
Very Nice Work !!!
Hey rodd... I think you should work on an aosp gingerbread kernel ... this is a great advancement in devlopment man... right when it was slowing again
Sent from my SPH-D700 using XDA App
this is amazing, thanks for this!!
You cannot make a cross OS kernel. We cannot integrate this into GB yet because there is no GB source, no GB source, no custom kernel. This is Froyo only, and well, someone else can make an eclair only kernel, but that is stupid.
Clarification on the poll question:
Yes = The ROM stays up
No = The ROM goes down
With the permission of MildWild I bring to you
MildWild v2.9.5 Lite Final
(based on MildWild V-2.9.5)
This is NOT a new ROM! It's only a trimmed down and fixed up version of MildWild V-2.9.5.
Change Log for Final Version:
- NEW - ZipAligned all system apks
- NEW - Automatic ZipAlign of new apks on every boot
- Fixed 720p HW encoding - works for H.264 format ONLY (see link to test file below)
- Fixed SuperCharger script - now using V6 SuperCharger update 8 with Aggressive 1 Setting
- Updated GO Launcher EX v2.77
- Updated Superuser v3.0.7
- Added HTC Stock Alarms, Notifications and Ringtones to the separate Media Package; converted all sounds to OGG Vorbis.
Fallout 3 Trailer @ 720p in H.264 - test file for HW decoding
F.A.Q.
I. Why would I want to install MildWild v2.9.5 Lite?
- It's smaller so it will fit on the Alpharev Oxygen r2 Hboot meaning that you will get a larger data partition and more space to install your applications. (Alpharev Oxygen r2 partition sizes: 100MB system, 5MB cache, 332MB data; Alpharev CM7 r2 partition sizes: 145MB system, 5MB cache, 287MB data)
- It stores apps and dalvik on sd-ext so you get even more space for your applications. On the downside, the ROM may become a bit slower.
- Alternatively, you can install the version which keeps dalvik on the internal memory.
II. So, how come MildWild v2.9.5 Lite is smaller?
- Some non vital system data and system applications have been removed from the instalation package.
III. Right, so what's missing?
- These applications have been removed:
1. GMmail (Gmail.apk) - you can install it from the Market so it will go to sd-ext instead on the internal memory, hence you get more space;
2. Google Talk (Talk2.apk) - well, you have to make some sacrifices; however, I think you can install it manually from the apk package but I haven't tried myself;
3. Google News & Weather Widget - you can find a whole range of simmilar applications on the Market; or you can probably install it from the apk package but I haven't tried;
4. Stock 3D Gallery (Gallery3D.apk - I recommend QuickPic from the Market instead; it is smaller and does the same job better;
5. Stock Music Application - there is a whole range of media players on the Market; this however will break the ability to play music through the Desk Clock Application; however, you can probably install it manually from the apk package but I haven't tried;
6. Typological Clock (TypoClock.apk) - you can most likely find something simmilar on the Market; or you can probably install it from the apk package but I haven't tried;
7. Timer Widget - you can most likely find something simmilar on the Market; or you can probably install it from the apk package but I haven't tried;
8. File Manager (FileManager.apk) - you can find a whole range of File Manager applications on the Market;
9. Compass (compass.apk) - you can find a whole range of Compass applications on the Market;
- Launcher 2 has been replaced with GO Laucher EX; it's smaller, faster and I think generally better; then again, it's a matter of taste;
- All alarms, notifications and ringtones have been removed from the installation package. Instead, you can download the media package attached (see link further down), unzip it, and place the folder as it is anywhere on the FAT32 partition of your SD card and it will work just the same. The system will automatically detect these files on the SD card.
- All PicoTTS (voice output) data files have been removed from the installation package. Instead, you can either download them from the Market or download the svox package attached (see link further down), unzip it, and place the folder as it is in the root of your FAT32 partition of your SD card and it will work just the same. The system will automatically detect these files on the SD card.
IV. So what's the point if I still want these applications?
- Whatever you install from the Market will go to sd-ext so you will have more space on the internal data partition for additional applications. If you keep the dalvik internal then the application data will stay on the internal memory but you still get some benefit as the apk still goes to the sd-ext.
- On the downside you can't get some of them on the Market and they may not install properly from the apk package so if you want to use exactly these apps then you'd better stick to the fully fledged MildWild ROM.
- However, you can download the apps package attached (see link futher down) and play with the apk files.
DISCLAIMER
ALL CREDITS go to MildWild.
I am NOT a delevoper and I have NOT developed any of the apps, bins, libs, etc. included inside the instalation file. I simply unpacked MildWild's zip file and removed/replaced a couple of things here and there, and then repacked it back. You can ask me questions but I cannot guarantee that I will be able to answer. Also, the responsability of installing the ROM and playing around with it lies 100% with YOU!
Download Links
MildWild v2.9.5 Lite Final (with dalvik on sd-ext)
MildWild v2.9.5 Lite Final (with dalvik on internal memory)
Media Package including HTC Stock Sounds - OGG Vorbis (alarms, notifications, ringtones)
Apps Package (all apks that have been revomed from the installation)
SVox Package (PicoTTS data files)
MildWild v2.9.5 based on Oxygen (The Original)
NOTE! This is the LAST and FINAL version of my modified ROM.
As you may or may not know, to concentrate on the CyanogenMod version MildWild has stopped development on the Oxygen version of this ROM for the foreseeable future (see here: http://forum.xda-developers.com/showpost.php?p=22130173&postcount=2568). As such, this is also the last update from me.
Do check out the ORIGINAL!
MildWild v2.9.5 based on Oxygen
Removing a launcher and replacing it with another one doesn't make it a custom ROM. This could all be put into a flashable ZIP which has to be flashed on top of a stock MildWild ROM, so that the update-script removes all the APKs. But another topic just for a modified ZIP only causes a lot of confusion.
what is the point of this ? everyone could make this.
Chaosz-X said:
Removing a launcher and replacing it with another one doesn't make it a custom ROM. This could all be put into a flashable ZIP which has to be flashed on top of a stock MildWild ROM, so that the update-script removes all the APKs. But another topic just for a modified ZIP only causes a lot of confusion.
Click to expand...
Click to collapse
Please read the description...
expler said:
what is the point of this ? everyone could make this.
Click to expand...
Click to collapse
Constructive comments would be very much appreciated...
Not a fan PERSONALLY of this "I can unzip, remove a few apps, then re-zip and post as a new rom" attitude, but it's a case of supply and demand I suppose. At least the OP has had permission from MildWild.
Screen ? ^_^
lolitz said:
Screen ? ^_^
Click to expand...
Click to collapse
Will do later on.
In any case, appart for the GO Launcher EX bits it looks exactly like MildWild - he's the BEST! (see link below)
MildWild v2.9.5 based on Oxygen
whats the point in making this a whole new thread?
it's some deleting/adding stuff to a zip file.. nothing else.
absolutely no need for this in my opinion, 'cause everyone can open a .zip file and delete stuff they don't want, and add stuff they want.
if we continue this road, we have 20 roms based on mildwild, and 20 different threads filled with the same questions over and over and over and over and over again.
horst0815 said:
whats the point in making this a whole new thread?
it's some deleting/adding stuff to a zip file.. nothing else.
absolutely no need for this in my opinion, 'cause everyone can open a .zip file and delete stuff they don't want, and add stuff they want.
if we continue this road, we have 20 roms based on mildwild, and 20 different threads filled with the same questions over and over and over and over and over again.
Click to expand...
Click to collapse
Please vote in the poll...
If people don't like it, then I'll remove it...
horst0815 said:
whats the point in making this a whole new thread?
it's some deleting/adding stuff to a zip file.. nothing else.
absolutely no need for this in my opinion, 'cause everyone can open a .zip file and delete stuff they don't want, and add stuff they want.
if we continue this road, we have 20 roms based on mildwild, and 20 different threads filled with the same questions over and over and over and over and over again.
Click to expand...
Click to collapse
whats with the hate? it saves people time of doing it themselves if they dont know what system related stuff they can remove without causing problems
it gives more space and mildwild allowed him to do it.
if you dont want it dont use it, im sure some people would be happy to use it.
as fopr putting it on the same thread? why would he hyjack an ops thread with different work. i doubt people would but it could be seen as trying to take people away from the original ops rom or some people might be confused with it being by mildwild himself as its displayed in a rom dev format..
people need to chill out, leave the complaining to the other devs if they have an issue with it and everyone else concentrates on flashing.
i dont see you complaining about the many different varients of stock roms that are modified in a kitchen using the same kernel as every other rom and called something different.
i dont see you complaining of the clones of 3.5 sense roms that have had different apps added just to call it something different.....
grow up
The ROM was great... That's very rude of you guys
He's just trying to help the people that don't know that much about ROM's.
OP, please continue what you're doing, it's great!
I'm already using your ROM
Guizzoni said:
The ROM was great... That's very rude of you guys
He's just trying to help the people that don't know that much about ROM's.
OP, please continue what you're doing, it's great!
I'm already using your ROM
Click to expand...
Click to collapse
Thanks...
Some people really put you down sometimes...
Rastaman-FB said:
whats with the hate? it saves people time of doing it themselves if they dont know what system related stuff they can remove without causing problems
it gives more space and mildwild allowed him to do it.
if you dont want it dont use it, im sure some people would be happy to use it.
as fopr putting it on the same thread? why would he hyjack an ops thread with different work. i doubt people would but it could be seen as trying to take people away from the original ops rom or some people might be confused with it being by mildwild himself as its displayed in a rom dev format..
people need to chill out, leave the complaining to the other devs if they have an issue with it and everyone else concentrates on flashing.
i dont see you complaining about the many different varients of stock roms that are modified in a kitchen using the same kernel as every other rom and called something different.
i dont see you complaining of the clones of 3.5 sense roms that have had different apps added just to call it something different.....
grow up
Click to expand...
Click to collapse
Dito!
Thank you for the support.
I voted yes. Do not delete this thread!
Oh, I do get annoyed by all the Sense ROMs too. With all that ROMs out there it's pretty hard to see the difference, so that's a mess too IMO.
Chaosz-X said:
Oh, I do get annoyed by all the Sense ROMs too. With all that ROMs out there it's pretty hard to see the difference, so that's a mess too IMO.
Click to expand...
Click to collapse
Please vote in the poll...
do3in said:
I voted yes. Do not delete this thread!
Click to expand...
Click to collapse
Do you know if we can get Android in Romanian? I would like to add it to this trimmed ROM.
I'm a little bit confused with the poll:
Do you think this trimmed ROM is useful = yes
or I should take it off = no
how to vote yes and no...? hehe
anyway good luck with the rom and thanks for sharing
Hey guys, I made a simple script here and thought I'd share it
Many of us flash roms often and like to add things back to our /system or /data partitions afterwards.
For the longest time I had a 'flashpack.zip' file sitting on my sdcard that I'd flash right after I flashed a new rom. It added ringtones, hosts file, custom eri.xml, etc. But it was a pain to keep up to date with stuff I wanted and it sucked to have to flash two zips all the time.
If you didn't know, there are some scripts in /system/addon.d/ that survive wipes and get run by recovery. They generally have a switch statement that controls when certain things run. (when you back up, when you restore, after you flash a rom, etc)
This little script just runs after a rom install and merges in whatever you have sitting in /sdcard/flashpack/ to your root filesystem
Script/directions: http://pastie.org/7726407
Flashable zip to enable this: http://invisiblek.org/99-flashpack_enabler.zip
Feel free to modify, or do whatever you want. If you come up with something cool, share it!
Someone should find a way to apply a metamorph theme via this method...I really like the SuperuserLock from here: http://faithcry.believable.org/lockrings.html
Hi. I'm currently on CM11 Nightlies now and this script isnt working. I have other addon.d scripts that work but this one doesnt. I try to use it for some fonts, sounds and apps. I've read the instructions carefully and i don't see a reason why it wouldnt work other than the script is outdated.
anyway thanks~