Related
These are entirely unchanged from the ROMs on the thread over in Dream land below (apart from one small fix for Exchange in version 1.0)
http://forum.xda-developers.com/showthread.php?t=534479
These are JAC and Drizzy's ROMs, not mine - all I've done is unpack the ROM, change one file in boot.img to make it work on a Magic, and then repack it all and sign it. So we'll forego the sigfile saying "if you like my work please buy me a Ferrari". However, this whole thing is a bit of a faffy operation and not something that's simple to set up (although is easy enough once you have everything you need in place) so I thought I'd share and save others the grief rather than hogging all the fun for myself.
These have come about because I wanted a Hero ROM, but wasn't entirely satisfied with the best one available for the Magic (Qtek's, IMO). It worked well, but the swap version dropped SMS messages sometimes, and the Compcache version was buggy, sluggish, and wifi didn't work.
JACxHERO seems to have a number of the same issues that Qtek has - dropped SMS messages (it seems that the lack of memory on the device causes the SMS/MMS process to die), and the Compcache version has broken Wifi. I said earlier on that I thought this version was oddly sluggish, but after setting up Compcache with backing swap I am loving it. By far the best Hero ROM on my own setup so far. No Wifi is a drag but I can live with it for now.
JACHeroSki 2.7.4.r2 in contrast is an older build, and one suspects they're using an older kernel; it has a working Compcache setup, but no conventional swap at all, and no multitouch. A good call if you have a slow SD card, can live without multitouch, and positively have to have wifi.
Bottom line as I see it:
Fast SD card? Use JACxHero v1.2. But you might lose SMSes (that said, no-one's reported any yet - I just worry about lack of memory issues)
Slow SD card but need wifi, and can live without multitouch? Use JacHeroSki 2.7.4 r2.
Slow SD card and want multitouch, or you insist on Compcache for other reasons, and not interested in wifi? Use JACxHero v1.0.
I personally am running 1.0 and after not being keen initially, it is growing on me and turning into a keeper. I only ever use wifi when at home and can do without it there, so it's not a problem for me.
----
JACxHero Version 1.2 - seems fast, but no Compcache
http://www.4shared.com/file/123726235/aa3ee695/jacxhero12-pn-magic.html
JACxHero Version 1.0 - Compcache, WiFi doesn't work properly. Works well if you enable backing swap and up the swappiness. See my user.conf on page 3 of the thread.
http://www.4shared.com/file/123729537/191c816a/jacxhero10-pn-magic.html
http://www.4shared.com/file/123821706/7250ac6b/jacxhero10-exfix.html (version with Exchange fix - I haven't tested this but it should be fine)
(version 1.1 didn't seem to be enormously different than 1.2; I did try it and have a working .zip but don't see much point uploading it)
JACHeroSki v2.7.4r3 - Compcache works by default, as does wifi. Note, though, there's no multitouch in the browser, which is a bit fail.
http://www.4shared.com/file/123798395/c61c220a/jacheroski274r2-pn-magic.html
NOTE THAT ALL OF THESE NEED THE USUAL THREE PARTITIONED SD CARD! i.e. fat32/ext2/swap
why have the v1.2 no compcache?
eljuego
As a note remember that JACxHero Roms dont have Compcache enabled by default.
The first post in the Dream Forum JacxHero thread tells you how to enable it - you need to edit the user.conf file, which i think is in /system/bin, can't remember right now.
It tells you which settings to change to get each combination of linux-swap and compcache
(BTW I know as it's working for me...)
Is it for 32A or 32B?
The rom for 32a or 32b ?
dazcox5181 said:
As a note remember that JACxHero Roms dont have Compcache enabled by default.
The first post in the Dream Forum JacxHero thread tells you how to enable it - you need to edit the user.conf file, which i think is in /system/bin, can't remember right now.
It tells you which settings to change to get each combination of linux-swap and compcache
(BTW I know as it's working for me...)
Click to expand...
Click to collapse
Good spot, I should have pointed this out.
gdskp said:
Is it for 32A or 32B?
Click to expand...
Click to collapse
32B - sorry, have now edited the thread title.
eljuego said:
why have the v1.2 no compcache?
eljuego
Click to expand...
Click to collapse
No idea mate. I suspect it was because of the issues with WiFi that they removed it until they could fix it.
One oddity I've noticed - the weather widget doesn't work. i select London as a city, it has a bit of a churn saying "loading weather", and no weather ever turns up. Clicking into the weather app workable fine.
Snap judgement - it's not as fast as Qtek's Rom. Just feels a bit "off". Maybe it's just me.
Loccy, the widget are buggy you sure you have ported the version 1.2 not the version 1.1 ? In version 1.2 the widget are fixed
edit : The widget have no border, but the rom is really fast probably the fastest rom i have tested !!!!
setenza01 said:
Loccy, the widget are buggy you sure you have ported the version 1.2 not the version 1.1 ? In version 1.2 the widget are fixed
edit : The widget have no border
Click to expand...
Click to collapse
Am pretty sure I called 1.2 the right filename but I was drowning in roms by the end so it is possible I got them mixed up. Can't check until I get home now though.
Either way I'm not too impressed - more bugs than Qtek and it is eating battery (although I have been hammerring the phone more or less constantly over the few hours I've been out). I think when I get home I'm going to build the final JacHeroski Rom and see how that goes, I believe that has Compcache running.
Dazcox, how are you finding this Rom? You've been running it longer than me.
Actually I've been using QTek today... but about to install this one will let you know
setenza01 said:
edit : The widget have no border, but the rom is really fast probably the fastest rom i have tested !!!!
Click to expand...
Click to collapse
Really? It's not a patch on Qtek for me. How fast's your SD card?
Am just downloading the final release of JacHeroSki - v2.7.4r2 - and will give that a try. I wonder if some of these new releases are a little too bleeding edge to be useful. If a worthwhile update.zip for the 32B emerges I'll post it here.
dazcox5181 said:
Actually I've been using QTek today... but about to install this one will let you know
Click to expand...
Click to collapse
I thought you'd done your own boot.img hacking and were running this already..?
I have a 8Gb class 6 sdcard and it's really fast more than the qtek rom
The 2.7.4r2 good idea, you make the port today ?
Loccy said:
Really? It's not a patch on Qtek for me. How fast's your SD card?
Am just downloading the final release of JacHeroSki - v2.7.4r2 - and will give that a try. I wonder if some of these new releases are a little too bleeding edge to be useful. If a worthwhile update.zip for the 32B emerges I'll post it here.
I thought you'd done your own boot.img hacking and were running this already..?
Click to expand...
Click to collapse
now I am, tried all the other builds myself
setenza01 said:
I have a 8Gb class 6 sdcard and it's really fast more than the qtek rom
Click to expand...
Click to collapse
Ah. I have the stock 2Gb Vodafone pile of ****e (plus an "8Gb class 6" that I bought from ebay that causes a reboot loop on my Magic ). That'd probably be the problem for me.
Right chaps, here's another one for you. This is JacHeroSki version 2.7.4 r2. Someone else here has done JacHeroSki previously*, but I don't think they ever updated to the final release. It's a little behind the curve in that JAC seems to have gone on to work with Dizzy, and in a different direction, and it won't see any more development. It has working Compcache, but lacks the fancy config scripts of later builds. If you want to play with your Compcache settings, you need to edit the a2sd script in /system/bin. No conventional swap or facility for one. I'd say this is pretty much where Qtek was trying to go with his Compcache ROM though:
http://www.4shared.com/file/123729537/191c816a/jacxhero10-pn-magic.html
Am not sure I'm going to stick with this, however. I've just seen in the thread on the Dream forum that you can get Compcache working in JacXHero 1.2 by nabbing the boot.img from 1.0, so I'll give that a go too. What I'd really like is a working ROM with Compcache and swap as a backup.
edit: * speak of the devil, it's just turned up on the front page of the threads, they did do the final release, but it was for 32A not 32B. Oh, and am very disappointed to find no multitouch in the browser.
Does texting work fine on this ROM?
bhav007 said:
Does texting work fine on this ROM?
Click to expand...
Click to collapse
Honest answer? I don't know. I got a couple of text earlier when running JACxHERO 1.2, and I was hammering the browser at the time (if icanhascheezburger.com isn't going to run you out of available memory, I don't know what is). But I think a definitive answer will have to come from people who text more than I. Unfortunately texts seem to be an issue on all Hero ROMs on the G1 and the Magic 32B, because of memory - hence why my goal is to get a build with as much "memory" as possible, even if most of it is swap and compcache sleight of hand.
Loccy said:
Honest answer? I don't know. I got a couple of text earlier when running JACxHERO 1.2, and I was hammering the browser at the time (if icanhascheezburger.com isn't going to run you out of available memory, I don't know what is). But I think a definitive answer will have to come from people who text more than I. Unfortunately texts seem to be an issue on all Hero ROMs on the G1 and the Magic 32B, because of memory - hence why my goal is to get a build with as much "memory" as possible, even if most of it is swap and compcache sleight of hand.
Click to expand...
Click to collapse
Am getting a boot loop after clean flashing this rom, any ideas why?
bhav007 said:
Am getting a boot loop after clean flashing this rom, any ideas why?
Click to expand...
Click to collapse
Which one? I found I had to completely clean off my ext2 partition before it'd run (coming from the Qtek ROM). Well, actually what I did was go into the recovery console and shift everything the Qtek had left in ext2 into another directory so that this ROM didn't get confused by it
bhav007 said:
Am getting a boot loop after clean flashing this rom, any ideas why?
Click to expand...
Click to collapse
If you were coming from Qtek's Rom, like I did, It does boot loop unless you clean your ext partition first, then wipe and reinstall the rom. It runs like a champ.
to erase the ext: boot into recovery
then from adb shell : run
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/*
then do whats stated above and no boot loop anymore.
PS: Loccy thx for the port.
PPS: to get this working with compcache instructions are in the first post of the dream rom
r1tman said:
If you were coming from Qtek's Rom, like I did, It does boot loop unless you clean your ext partition first, then wipe and reinstall the rom. It runs like a champ.
to erase the ext: boot into recovery
then from adb shell : run
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/*
then do whats stated above and no boot loop anymore.
PS: Loccy thx for the port.
PPS: to get this working with compcache instructions are in the first post of the dream rom
Click to expand...
Click to collapse
Am abit new with the terminologies here . Is there a guide I can follow to do the clean wipe. If i reformat my SD card to the necesarry partitions, it should work?
bhav007 said:
Am abit new with the terminologies here . Is there a guide I can follow to do the clean wipe. If i reformat my SD card to the necesarry partitions, it should work?
Click to expand...
Click to collapse
Should do, if you use the partitioning option on the recovery image, that'll wipe everything.
r1tman said:
PS: Loccy thx for the port.
Click to expand...
Click to collapse
De nada. All I did was just change a few files.
I'm done for the night now people. I did try to get 1.2 running with 1.0's boot.img, but ended up with a ROM that had no working wifi and no apparent Compcache. I figured that wasn't any better than 1.0 proper (which I'm going to give another crack and see if I can tidy up the Compcache settings to my satisfaction - I can live without wifi for now).
I wanna know how to remove the auto a2sd scripting from running at all during boot tried to just delete it and got stuck in boot loop
i am currently trying to remove this script from the zeroxd 5.2r5
anyone who could impart some wisdom would be greatly appreciated
Its going to be tricky removing it but there is a thread that tells how to remove it easily. You may want to upgrade to ZeroXD 6.0. Only apps you install will go to sd automatically, the rest stay in internal memory. Twisted has made some great changes. Including dynamic swap. Not to sure how it works but torture testing it now. Everything still moves though if you are on a g1.
Johnny Blaze said:
Its going to be tricky removing it but there is a thread that tells how to remove it easily. You may want to upgrade to ZeroXD 6.0. Only apps you install will go to sd automatically, the rest stay in internal memory. Twisted has made some great changes. Including dynamic swap. Not to sure how it works but torture testing it now. Everything still moves though if you are on a g1.
Click to expand...
Click to collapse
on mt3g and is it out?
yes its out and runs very fast . Check the zeroxd thread
WARNING:You must Have The Correct Radio and Latest SPL! You can find them here (RADIO MUST BE INSTALLED FIRST) You can find it here
PLEASE DO YOUR RESEARCH BEFORE FLASHING ANY ROM INCLUDING MINE IT WILL SAVE YOU AND OTHERS TIME AND HEADACHE!!!
First A big thanks to Haykuro for providing the system dump of the latest known Hero build. Great contributions from Haykuro always!!! Make sure to thank him!!!
This ROM is based off the latest "HTC" ROM leak 2.83.x.x with tons of mods enjoy!!
This is the same as the build posted in the dream section,we just wanted to keep the two threads clean so all MT3G/Sapphire Q: and problems should be posted here. As of now it works only on 32B but 32A kernal is being worked on so will be coming soon give ccyrowski time he is working hard for us.
NOTE: Once you flash before you sign in do the led fix in the instructions,also we recommend using ext3 and a 64MB Linux-swap partition.
JacHEROSki 2.2r4 Remix More Specs Coming!
Fix Video audio
Added lastest tether 1.60
Added Sapphire folder
Added the new LED app By jinx10000
JacHEROSki-v2.2 - Experimental A & B
A
-2.6.29.6-jac-ski [email protected]
-BFS 240
-supports MyTouch out of the box!
-MT
-various ramconsole and usb patches
-other things I can't think of
B
-same as A with the 10MB RAM hack (10 extra MB of RAM)
-other things I can't think of
Install Instructions
First using adb I remove the ext3 and linux swap if you have them set already like this, remember the numbers will vary with the size of you card but I will show mine as an example.
In Recovery
This Removes the partitions
adb shell
parted /dev/block/mmcblk0
rm 2
rm 3
This makes the partitions ext2 and linux-swap 64MB remember numbers vary according to the size of your S.D if your not sure ask first.
mkpartfs primary ext2 3767 3901
mkpartfs primary linux-swap 3901 3965
This upgrades the ext2 to ext3
quit
upgrade_fs /dev/block/mmcblk0p2
Now with the build on your S.D
Wipe
Flash the build A or B
Now once the build loads up you may get a FC on HeroLED.apk which there is a fix that I know of for MyTouch but cant be done because the sapphire folder is not in the build and not needed the HeroLED.apk is not needed since they work without it.
Phone on as normal
Fixing the HeroLED.apk
Fix the FC on HeroLED.apk and also get your phone to read as a Magic/MT3G.
Terminal
su
rwsystem
magic
reboot
Click to expand...
Click to collapse
This is how I install my builds and have it running as smooth as I do if your not sure you can do all this don't try. I do it and my phone runs sweet, but I will not take blame for people messing up there phones because they don't know what there doing.
JacHEROSki 2.2r4 Remix: http://www.4shared.com/file/136918974/b6e7bf4c/jacheroski22r4_Remix.html
JACxHEROSki-v2.2a: http://www.justanotherdev.slackdev.com/jacheroski2.2a.zip
JACxHEROSki-v2.2b: http://www.justanotherdev.slackdev.com/jacheroski2.2b.zip
Good **** thanks manup. Will you be adding BFS-300 to this tonight?
Omg...cant wait for 32a version ....STILL !!!!!
rebooting with new remix rom
I am getting frequent reboots ( about every 30 minutes) and also am getting a force close due to leds any ideas?
oops
I found the fix for the led force close. any idea on the rebooting?
Well the rebooting I have not seen on these ROMS really I would reflash again and let me know if still keeps happening,also are you using the remix or what version?
@jabbawalkee
I will maybe drop tonight not sure its up to cc but the BFS-300 will have the 10MB hack for MT3G/Magic for those who dont know that. I know you do but some are waiting so I tossed that info in there.
@Daneshm90
I know bro I am working on getting that for you hopefully today but cc is a bit under the weather so we will see.
manup456 said:
Well the rebooting I have not seen on these ROMS really I would reflash again and let me know if still keeps happening,also are you using the remix or what version?
@jabbawalkee
I will maybe drop tonight not sure its up to cc but the BFS-300 will have the 10MB hack for MT3G/Magic for those who dont know that. I know you do but some are waiting so I tossed that info in there.
@Daneshm90
I know bro I am working on getting that for you hopefully today but cc is a bit under the weather so we will see.
Click to expand...
Click to collapse
Thanks man. I have 300, but wasn't working too well when I flashed it as an update over A...may try deleting/recreating my partitions and re-trying it.
Not sure bro I have been using it since yesterday on a fresh fromat and install and its been really good for me so yeah I would def give a fresh format and install.
manup456 said:
Not sure bro I have been using it since yesterday on a fresh fromat and install and its been really good for me so yeah I would def give a fresh format and install.
Click to expand...
Click to collapse
Are you using it on A or B?
No I use a whole ROM with it built off of 2.2r4 thats what I thought you had P.M me to see what it is your using.
manup456 said:
No I use a whole ROM with it built off of 2.2r4 thats what I thought you had P.M me to see what it is your using.
Click to expand...
Click to collapse
Check your box
Great work.
After seeing that Tweet from last night. I'm glad to see this up-and-running this afternoon.
About time the "official" build finds a home in the Sapphire Development Section.
Oh, and thanks for the hard work put in last night. I was working like a dog, testing for CC last night on that BFS-300 patch. Lol.
(not that it was "hard" work or anything.)
Glad to see you in this section though.
No prob I will be around in both sectitions because I have both G1 and the MT3G,I wanted it to not be so mixed in the dream thread people seemed to get confused there will be a update either today or tommarrow that will be real nice.
I am helping as much as I can but cc is killing it with all his new work and mods mike's user.conf is also amazing.
manup456 said:
No prob I will be around in both sectitions because I have both G1 and the MT3G,I wanted it to not be so mixed in the dream thread people seemed to get confused there will be a update either today or tommarrow that will be real nice.
I am helping as much as I can but cc is killing it with all his new work and mods mike's user.conf is also amazing.
Click to expand...
Click to collapse
Take your time tonight.
You might as well drop tomorrow, just give everything a chance to settle today.
People are hyped enough on the BFS-300 high. Lol. No need to cause a global overdose.
I'm eager to see this user.conf you speak of. Some sweet-ass options within I hope! As for the G1 and MyTouch, same here. But, I have three MT3G devices. (employee of; you guessed it.) Anyway, if you need a tester later tonight or whatev.
TWEET ME!
US MT3G w/2.2a problems
First, I have an 8GB SD card, with the standard partition sizes (7GB FAT32, 32MB Linux-Swap, and the rest Ext3)
I am using Cyanogen 1.4, and I did a wipe, and check of my ext before updating. The SD card was empty on all partitions, except the 2.2a named as update.zip
First thing I saw on startup (and every startup) is the LED notify crash, but more serious is the phone being stuck in headset mode. Tried rebooting, plugging in charger, plugging in actual headset, but it was just stuck on.
I ended up flashing back to my stock tmobile 1.5 firmware until it's more stable.
My knowledge of this device is a bit limited at this point. I know I am running the latest radio, but I am not clear on what SPL is (or ADP for that matter).
Can anyone help fill in the blanks or tell me what I am doing wrong?
tia,
-dana
I said in the first post that swap is better at 64MB and there is instructions in the first post that talks all about the FC on HeroLED all you need to do is hit o.k and follow the steps posted. Also coming from another wipe a format of the ext3 should have been done read the first post.
Does everyone have the auto-backlight option?
Same issues...
manup456 said:
I said in the first post that swap is better at 64MB and there is instructions in the first post that talks all about the FC on HeroLED all you need to do is hit o.k and follow the steps posted. Also coming from another wipe a format of the ext3 should have been done read the first post.
Click to expand...
Click to collapse
Thanks for pointing that out, I now see the instructions that I did not notice before.
I used Ubuntu to delete my partitions, and re-do them with the sizes stated in the instructions, so the partitions are clean. I then copied the update.zip (22a) to the card, and put it in the phone. Started Cyanogen, wiped, repaired ext partition, and installed the update.zip
I still have the headset indicator stuck on.
Went into terminal, but could not get a keyboard to come up. I used "better terminal emulator" instead, which should work. I followed the steps, but when I got to "magic", it came back with "rm failed for system/bin/sapphire, no such file or directory"
I still have the LED FC at startup, and am still stuck in headset mode.
Any ideas?
tia, again,
-dana
dleasman said:
Thanks for pointing that out, I now see the instructions that I did not notice before.
I used Ubuntu to delete my partitions, and re-do them with the sizes stated in the instructions, so the partitions are clean. I then copied the update.zip (22a) to the card, and put it in the phone. Started Cyanogen, wiped, repaired ext partition, and installed the update.zip
I still have the headset indicator stuck on.
Went into terminal, but could not get a keyboard to come up. I used "better terminal emulator" instead, which should work. I followed the steps, but when I got to "magic", it came back with "rm failed for system/bin/sapphire, no such file or directory"
I still have the LED FC at startup, and am still stuck in headset mode.
Any ideas?
tia, again,
-dana
Click to expand...
Click to collapse
Get 2.2r4, not 2.2a
manup456 said:
Does everyone have the auto-backlight option?
Click to expand...
Click to collapse
No auto-backlight option after installing 2.2r4 and running the magic script.
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.
Well whaddaya know, the HTC Desire has taken on a new amazing feat; it can now dual boot ROMs. While I sit here in jealousy I must ask, how is this possible? I mean is it device specific? I'd love to dual boot on myTouch, I have 3 SD Cards just laying around chilling, and they would be really useful for this.
http://forum.xda-developers.com/showthread.php?t=1173309
We're always missing out on some, this is on many htc devices I've noticed, including things like the Cwm4 recovery. I wish I could help get those things on our phones.
Sent from my HTC Glacier using XDA App
What is dual boot?
Sent from my HTC Glacier using XDA App
Google: What is dual boot? ANSWER: A dual boot system is a computer system in which two operating systems are installed on the same hard drive, allowing either operating system to be loaded and given control. When you turn the computer on, a boot manager program displays a menu, allowing you to choose the operating system you wish to use.
Click to expand...
Click to collapse
In our case it would be the device your using is partitioned for two seperate areas in which two independent Roms are installed, when you first power on the device you get a boot manager that gives you a choice to boot into one or the other.
The issue with doing this with a phone is the two Roms you choose would have to be able to run on the same Kernel. So if your running a Sense Rom and you decided to install an AOSP requiring a different kernel on the other partition you would run into some real issues.
This is completely doable on our device, the question is how important is it for anyone to have and would you mind giving up battery time for the feature, YES this will cause you to drink up some power which is something most Devs work hard on to keep consumption down.
EDIT: You can follow the same instructions here but there maybe a few things you need to do in C for this to work properly I didn't look to far into it, Also I would upgrade the SD Card as your going to have to have 3 partitions so an 8gb will get real crowded quick if you try to do this. The least I would try this with is a 16gb considering all of the files you may have already on your sd card that apps need for cache, pics, storage, ect.
I'll see what I can do with it after I pick up a 32gb sd card but it shouldn't be too hard.
Orical said:
In our case it would be the device your using is partitioned for two seperate areas in which two independent Roms are installed, when you first power on the device you get a boot manager that gives you a choice to boot into one or the other.
The issue with doing this with a phone is the two Roms you choose would have to be able to run on the same Kernel. So if your running a Sense Rom and you decided to install an AOSP requiring a different kernel on the other partition you would run into some real issues.
This is completely doable on our device, the question is how important is it for anyone to have and would you mind giving up battery time for the feature, YES this will cause you to drink up some power which is something most Devs work hard on to keep consumption down.
EDIT: You can follow the same instructions here but there maybe a few things you need to do in C for this to work properly I didn't look to far into it, Also I would upgrade the SD Card as your going to have to have 3 partitions so an 8gb will get real crowded quick if you try to do this. The least I would try this with is a 16gb considering all of the files you may have already on your sd card that apps need for cache, pics, storage, ect.
I'll see what I can do with it after I pick up a 32gb sd card but it shouldn't be too hard.
Click to expand...
Click to collapse
That was mentioned in the Desire HD thread. They say if you want to use a Sense and an AOSP ROM, you're going to have to use the Sense kernel and deal with the problems that may occur, like no bluetooth. Additionally, it seems to break Wifi for almost everyone who use it. Nevertheless its freaking awesome, and something I'd love to do.
There's not much to this and it can be implemented easily. I did it a different way, but the way the guy on that desire HD thread works much more elegant than my way did (although my way allowed for two different kernels).
To understand how this works, you first have to understand the boot process. When you turn on the phone, the bios starts the radio and then the radio starts the SPL which contains the information for partitioning, location of boot on nand, etc.
Unless you interrupt normal spl boot (which would take you to the other two boot options, spl and recovery), the spl looks for the "init" program in the specified boot partition.
This init program can be anything. From a basic linux perspective, it could be a simple script to set-up devices and then just toss user control to a command line (for basic linux usage) or, in Android's case, it runs the init scripts (device.init.rc and init.rc) and has the kernel run the whole Android stack.
What this guy did was make his own init program (I haven't looked at the thing since I'm at work) which, from what I read, is just a small binary, which possibly relies on two different init scripts to boot either from nand (mmcblk0p25) or sdcard (mmcblk1pX [depending on your partitioning]).
The disadvantage to this is that, as he stated, you can only use one kernel, since boot is still starting as normal and the spl is booting to the boot partition which only contains one kernel (you can toss in more, but only one will be started by the spl) and then his init program takes care of the rest of the bring-up.
The way I did it was having two boot images for two different builds, my regular nand rom (which would boot when booting normally) and my SD build (which would boot instead of recovery). All this requires is flashing a boot.img to recovery and then modifying the init.rc to boot from SD (mmcblk1pX) instead of nand. The clear disadvantage, ofcourse, is the loss of recovery, but by using this guy's method, I could have a menu on the SD boot to boot either the SD build or a recovery (means a modified recovery rather than a regular boot.img).
Both options are easily doable on any rooted device. The one thing lacking currently is a recovery that will allow to update.zip install to sdcard (I'd suggest using partitions 4 for system and 5 for data, since 2 and 3 are historically been used for sd-ext and swap).
So you guys can just find a recovery dev, point him to this thread, and show him my post to see if he can make such a recovery (should be easy) and it could become mainstream feature of rooted androids.
Bump. This would be amazing to port over. This would be donation worthy.
Sent from my HTC Glacier using XDA Premium App
im trying to get madmaxx to compile the mt4g into that amazing 4ext recovery he made. It's like amon_ra recovery but better!
Sent from my HTC Glacier using XDA Premium App
You can dual boot on the MT4G with Boot Manager,available in the Android Market, though it cost 2.99 but it does allow you to run two separate ROMs.
I got BootManager but i need to set everything manually and i dont know them can someone help me with these?
What is your sdcard block?
What is your system's size in mb?
What is your data's size in mb?
What is your cache's size in mb?
I have MIUI DemonSpeed 1.29 and the 8gb sdcard that comes with the mytouch
harei84 said:
You can dual boot on the MT4G with Boot Manager,available in the Android Market, though it cost 2.99 but it does allow you to run two separate ROMs.
Click to expand...
Click to collapse
is it officially supported? I have a fear of it writing to the wrong partition and fμck up the device.
GazaIan said:
is it officially supported? I have a fear of it writing to the wrong partition and fμck up the device.
Click to expand...
Click to collapse
its not supported it asks the questions i posted in the first page <
I really know nothing about the app just saw a feature about it on Lifehacker.com
It works on myTouch 4G. It is supported, but support is weird. Im beta testing one that works and for the most part everything works as it should, but the app recognizes the phone on Virtuous Unity and doesn't recognize it in MIUI. I'm triple booted at the moment (I can install 2 more ROMs, but I don't want to) and MIUI is on the SD Card and doesn't recognize my phone.
Bottom line is, it works, try it. It's definitely worth the $2.99.
Doesnt work
Sent from my HTC Glacier using XDA Premium App
I take that back it does running VI 1.31 double shot and miui
Sent from my HTC Glacier using XDA Premium App