yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] Conap:
The symlink for data is a link to system/data. All the files are stored in system/data we just need the symlink there so that when the system looks for the data partition then the symlink will point it too system/data where the files are located. You are mounting mmcblk0p3 as system in the updater script so it can't be mounted as data or cache but you can just extract files to system/data or system/cache which would be the same thing as mounting data and cache.
[Droid Incredible Android Development] Conap:
I guess i should have kept reading before making my last post lol...but yes this is what it's doing.
[Droid Incredible Android Development] Mr. Rager:
Yep I get it, system/data + symlink.sh = data/.Ok, ill see what kind of magic I can do. I guess ill try moving everything into the system folder, which should make the rom bigger than the phone's system partition, correct? That means we can use dualbooting for its other intended purpose, like having a rom entirely too big for normal use.
[Droid Incredible Android Development] Conap:
Correct you have 6gb's of room so put as much as you want in there....you can either just make a data folder in system in the rom and put the stuff there or you can use the updater-script to extract_dir data to system/data(don't remember the exact syntax of it off hand) but it's probably just easier to make the system/data folder in the rom. Just remember if you need to set permissions in the updater script on any of the data stuff to point it to system/data/fileyouwanttoreach
[Droid Incredible Android Development] workshed:
Busy in here yet Conap?! ;)
[Droid Incredible Android Development] Blaine_O_C:
Will this work with the new sense ported over to the inc yet? such as: http://xdaforums.com/showthread.php?t=1109355
[Droid Incredible Android Development] Leshy01:
I know this is a terribly old thread, but does anyone have the original zips or a mirror? My phone needs to go back to its original setting but the download links are broken.
[Droid Incredible Android Development] Team ADX:
I had to fix the number 2 zip becuase it wasn't giving flash_image execute permissions. Updated version in OP. If you've already flashed dualrom just boot into phone rom then boot to recovery and run zip 2 again.
[Droid Incredible Android Development] khanam:
now i want to exchange the bolt back to the inc (had given it to my daughter)... was waiting for this for a long long time - thought uncorrupted would come to the inc first.

this should be spectacular...
[Droid Incredible Android Development] notwen:
Subscribed for later reference. This opens up tons of options, let alone extends the life of my dINC. Thanks. =]
[Droid Incredible Android Development] khanam:
@conap - you got a bolt too in your team too i hope. i am going to try this on my daughter's phone but would love it if its available for the bolt too. i hated leaving the inc for the bolt since the dev community on the inc was already so good but the big screen with the fact that i got middle aged eyes made all the difference. ridiculous 4g speeds helped too but i hate hate the battery life for anybody who is curious.
[Droid Incredible Android Development] Conap:
we do have a bolt on our team and we have discussed it a little bit so keep an eye out over there...there is a huge dev community on the tbolt so I'm sure there will be plenty of good stuff once they get some of those bugs ironed out.

On a side note for those interested in the process of this what had to be done since we couldn't split up the 6.5gb partition we had to store all the files in one partition and then create symlinks to get the phone to think there was a data and cache partitions to run from. It took a little while to get it to mount and symlink things at the right time for the boot process but in the end it was much more stable then having it on an external sd card. I'm sure there will be issues that will come from having the files all together but a wider testing audience will help sort all that out. The same process should work for the bolt as it has a similar setup with the internal memory.

Edit: I just looked up edify scripts and yes that's what this has so the newer clockwork should work fine...I've been using these scripts for a long time didn't realize that was what they were called lol...
[Droid Incredible Android Development] tiny4579:
Just wanted to say it is a great idea and considering I don't currently use emmc at all as it's not well supported which means I finally will have a use for the 6.5 GB. I load CM7 right now and would love to dual boot with a custom sense rom. I could avoid flashing between ROMS once I have a favorite sense rom.
[Droid Incredible Android Development] chad0989:
Yeah, this is annoying. I had previously tinkered with trying to move some of the mtd partitions onto the emmc so that we could ditch yaffs for ext3/4 which could potentially speed things up. Hopefully its possible and we can find a way to unlock it. Not sure if its permanently partitioned or if they're just specified somewhere like the mtd partitions.
[Droid Incredible Android Development] dccoh:
Questions

Trying to wrap my head around this. I have 2 questions:

How will this affect the use of Titanium Backup, and what about kernels that are AOSP Specific and that dont behave well with Sense.

I use Chad's kernel, and love the voltage tweaking enough that I wouldnt use another kernel for sense unless it was comparable in performance/snappiness/battary.

Thanks.
[Droid Incredible Android Development] ihtfp69:
Nice work guys. Time to port the Sensation rom. :)
[Droid Incredible Android Development] pickleman77:
I hope this means that you'll be doing this and not that you're suggesting it for them! :)
[Droid Incredible Android Development] r2DoesInc:
You should hit me up, I'm doing the Tbolt bolt and started the inc port already, maybe we can work out the egl stuff together.

Sent from my ADR6400L
[Droid Incredible Android Development] shuura:
wow! this is very promising! amazing work!
[Droid Incredible Android Development] corypaul:
Let meh get this straight...Can I change the internal rom to anything I want it or do it have to be that sense froyo rom or cm7 rom he provided
[Droid Incredible Android Development] smtom:
Cool stuff! Thanks for sharing.
[Droid Incredible Android Development] Mr. Rager:
+1 and what about gallery and other apps that look for emmc in either internal or phone rom
[Droid Incredible Android Development] sitoekim:
dual boot

I have been waiting for this for a while now. As soon as i got off of work i saw that this was available and flash it flawlessly. This is amazing. I switched back and forth doing things in both the roms. This is very very cool. Thank you. Will let you know if I have any problems. The first thing I am going to do is switch up the froyo rom that is on here. This is cool!
[Droid Incredible Android Development] corypaul:
Hello!!!
[Droid Incredible Android Development] Conap:
Titanium should work find. As long as the phone is booted the rom you have booted "thinks" it's installed in the normal fashion on the phone. The rom's use seperate kernels. Flashing a kernel in recovery is only going to affect the rom installed normally on the phone.

.

Anything that looks for emmc just won't find it. It will think you are using a phone that does not have the emmc and will just default to the sdcard

No the internalrom needs to be one of the 2 i have provided. The normal rom on your phone can be changed to whatever you want.
[Droid Incredible Android Development] DHowett:
I just modified MIUI 1.4.15 to provide dualboot (or just "install to emmc and boot from it") capabilities, and I was wondering about one of your design decisions.

The initramfs can contain symlinks (cpio supports it) - so why maintain the symlinks with scripts? I added the proper symlinks to the archive, switched out the system partition and removed data & datadata mounting, and it worked. No need to change all references to /data in init.*.rc to /system/data (and the same for cache.) or mess much with mounting/remounting/unmounting.

I also idly wondered why you kept /data mounting in the Sense Froyo internalrom; you mount it and then immediately unmount it after a filesystem check. It would save a couple seconds during booting to just chop those things completely out, I imagine.

Other than those few questions/complaints, great work! This is awesome.

I worry a bit about constantly reflashing mtd@boot though. :(

EDIT:

I keep experiencing mild corruption in /system on mmcblk0p3 (I/O errors for, like, lost+found, or build.prop) - Maybe HBOOT attempts to update some FAT fields that are -ENOTEXIST in ext2/3? Just like it enforces a partition layout, that is.

OH, I wonder! Maybe we can leverage device mapper like the asec system does, and store a bunch of different system images as files in /emmc (FAT32). More than dual-boot, and DRSettings could store boot images next to them (/emmc/CM7.system.img, /emmc/CM7.boot.img, /emmc/SenseFroyo(...))

I might prototype a system like this, if that's alright.
[Droid Incredible Android Development] Conap:
I originally attempted to symlink it in the init.rc but it just never seemed to work right for me but maybe i was doing it wrong. The only reason i left the mounting of data and then unmounting is because it seemed to take some time for the phone to mount the emmc partition and it wasn't finding it at boot so i left some of that stuff in there to stall it basically untill the emmc would mount.

As far as flashing mtd@boot when I used my eris and was deving on it I must have flashed rom's 5 to 6 times a day for many months and the eris was still fine. I'm personally not booting back and forth with this constantly so it won't be any more flashes for me then i'm use to.

I had tried mounting the image files as loop when we did a dualboot for the eris but I couldn't get it myself but I am sure it would be possible....
[Droid Incredible Android Development] USSENTERNCC1701E:
This is sweetness, thanks so much :D it's great to see Team ADX on the DINC
[Droid Incredible Android Development] Mr. Rager:
I guess in order to get a different kernel. One must change the edify script. Or could adb pushing work?

Oh and for some reason my theme on cm7 doesn't stick after a reboot, and in order for the notification Widgets to appear, I have to reboot. Not that big of a problem. Couldn't overclock as high either. But I'm sure the kinks will get worked out, just pitching out some of my observations.
[Droid Incredible Android Development] wildstang83:
Conap and the rest of the Team ADX, you guys are gods. Big props for what yall did for the Eris community and now the Incredible. Thank you.

DINC¦CM7¦SLAYHER27
[Droid Incredible Android Development] Conap:
If you are booted into the internal rom and then reboot to recovery and flash a kernel it will get applied to the internal rom. The problem is that there is a boot.img on the sdcard that would have to be changed and also the boot-internalrom.zip has a boot.img where the kernel would need to be changed as well. If you flash a new kernel on the phone rom you would just need to update the boot image on the sdcard by running zip number 2.

I think I still have an issue with powering down. I guess I should be umnounting the partition at some point to avoid corruption. When you say you couldn't overlclock as high you mean it would lock up at the higher speeds or what?
[Droid Incredible Android Development] djh816:
Soooo going by that logic, can I continue to do CM7 nightly updates while I have that as the phone rom (and active)?
[Droid Incredible Android Development] Conap:
Yes whatever rom you use on the normal phone partitions can be updated at any time like you would normally do. You would just want to flash zip number 2 after updating the rom which only takes a few seconds. I tried to make it so people could use and update/change their roms like normal while still having the option to have the second rom on the interanl memory if they wanted.
[Droid Incredible Android Development] Mr. Rager:
Oh, I understand now. If you shutdown in say the internalrom, then it'll boot back to the dualrom, same goes for mods. It'll stay in that partition til the phonerom.zip is 'executed'. I found all those boot images and somehow corrupted internalromcm7, the Dr app would boot straight into the bootloader. I got a little concerned for a sec but reflashed cm7 internalrom. Which by the way doesn't save data between flashes so I guess you don't have to wipe. That's for internalrom only, though.

By overclocking, I mean it'll freeze then soft-boot in the internalrom at anything higher than 1075mhz. This phone is pretty tolerant to overclocking. My phonerom can run 1228mhz all-day on nils business sense. I can usually overclock a cm7 phonerom to 1119mhz. Its not that big of a problem really, I'm happy just being able to switch between the two in thirty seconds as opposed to three minutes.
[Droid Incredible Android Development] sitoekim:
text and phone calls

Yes you can text and receive messages then boot to the other rom and send and make phone calls from the other. I sent a message from one rom. booted to the other one and then received a message. This is great.
[Droid Incredible Android Development] ihtfp69:
I didn't mean I wanted to port it. :) I was just saying it maybe possible now. However, talking with some people, there may be some huge hurdles other than size to get past.
[Droid Incredible Android Development] DHowett:
I've got a really similar multi-ROM system working which uses loopback-mounted image files instead of taking over /emmc completely.

It requires further specialized ROMs and a FAT32 /emmc...

I'll carry on in my own thread about the matter, with a couple ROMs to start with, but I wanted to post a screenshot here as this is where the discussion started.

(I apologize if this is some sort of hijacking, either of your thread or of your project, but I mainly did this for my own fun :P)
[Droid Incredible Android Development] Conap:
Don't apologize to me lol...I don't want to corner the dual boot options market...i like the way yours sounds actually. I had attempted in the past to boot an img in the way you mentioned but it was on the eris and wasn't working out. Maybe if you use irc at all we can discuss this stuff further...i did this for my own fun too :)
[Droid Incredible Android Development] patalo:
Can I only flash those two roms for internal? Or can I push the meta-inf to a different rom? Or how would that work?
[Droid Incredible Android Development] kzoodroid:
I've been using DualROM since yesterday and while I like it there are a couple issues I'm having. First off the setup I'm using is CM 7 Stable with default kernel is my Phone ROM and I'm using the Sense Internal ROM Conap supplied.

Here are my issues so far. Playlists keep dissappearing from the Internal ROM. I used MyBackup Pro to restore them but if I switch to my Phone ROM then back to the Internal ROM the playslists on the Internal are gone. They don't disapear from the Phone ROM. Also My Backup Pro force closes on the Internal ROM after first swtiching back to the Internal ROM from the Phone ROM, a reboot fixes this. This is the only app so far that I've had a problem with.

Thanks Conap for all the work, glad to see you over here. I had an Eris for a year and enjoyed your work with it.

Edit: This appears to be random as I tired to duplicate the problem and it didn't happen a second time. I'll try doing the same thing again with the phone tonight and tomorrow to see if I can get it to happen again. Maybe it degrades over time kind of thing.
[Droid Incredible Android Development] Conap:
I've had similar problems with random things dissapearing/not working with reboot fixing things sometimes. I think like was mentioned before it that because the ext3 doesn't get cleanly umounted it's causing issues. When i get time I will add a file system check/fix to run at boot and see if that helps with the issues. I am also gonna look into umounting it before turning off but not sure if that will be an option since they system is on same partition as data. Thanks for the feedback.
[Droid Incredible Android Development] Conap:
It would take more then that. I actually put Skyraider on my internal to try it out and I have to say it's a pretty nice rom but basically if you want to put a sense based rom on internal take the sensefroyo zip i made and just copy the system folder from the rom you want into the rom i made. Then take the number 2 zip I made and extract those files and drop them in the corresponding folders in the rom. Then pull the system/bin/symlink.sh file out of the sense or cm rom i uploaded and put that into the rom and I think that's all the files needed. If your doing an aosp rom you can just use the cm7 rom as the base and do the same proccess.
[Droid Incredible Android Development] sneaky_zekey:
Where is your thread. I want to follow both threads progress lol. Awesome stuff.
[Droid Incredible Android Development] Conap:
I added a line to the init.inc.rc to check/fix the filesystem at boot each time. I'm gonna test it for a day or so and see if it helps with the random corruption issues. If you want to test it I made a zip that will replace the boot.img's for the sense rom. You can flash this from recovery and it will replace the boot.img that the DR Reboot app uses and also put a new zip on your sd boot-Internal-Sense2.2V2.zip. The just run the boot-Internal-Sense2.2V2.zip and everything will be set up with the new boot.img's. I'm gonna run it myself for a day or 2 to see if it helps and then i'll add it to the cm version as well.....

http://www.multiupload.com/88T9LSK54W
[Droid Incredible Android Development] Conap:
Lol I'm waiting for this too.....
[Droid Incredible Android Development] patalo:
Well lol I'm wanting to put miui on internal so if you could help me with that I would be forever grateful.
[Droid Incredible Android Development] kzoodroid:
Okay I'm flashing this now. There were a couple other apps that dissapeared besides MyBackup Pro, Google Maps and MyVerizon, so I think its just random what gets corrupted. I flashed the update without a problem but my battery is too low now to try and switch ROMs, I'll do it in the morning and see if its working better.
[Droid Incredible Android Development] Conap:
I don't want to go around modifying other peoples work and releasing it as that's kind of rude but since i believe miui is aosp based you could do the steps I described in post 55 and use the cm7 rom i provided as the base to start with. I'm not sure if miui has modified the boot.img or not but you could give it a shot.

Thanks I appreciate the feedback.
[Droid Incredible Android Development] DHowett:
Here it is! It's a start, at least. :D

I'm definitely interested! I hang out on Freenode (irc.freenode.net) as DHowett or DHowett_. Just PM me!
[Droid Incredible Android Development] kzoodroid:
I've done a couple switches between ROMs so far since flashing this and have not had any more issues.
[Droid Incredible Android Development] patalo:
Ill try it, thank you very much.
[Droid Incredible Android Development] Crans:
3dualbootcm7.zip is (bad) for me running cm7 stable on my Inc success for first 2 steps in recovery 3.0.0.8 also tried 2.5.1.2 for step 3 even though it wasn't an update script issue . Would love to continue with this mod.... any suggestions
[Droid Incredible Android Development] Conap:
What do you mean by bad? it won't flash or won't boot? have you tried re-downloading the file?
[Droid Incredible Android Development] Crans:
In recovery it just states (bad) update aborted.... going to download again
[Droid Incredible Android Development] Crans:
Ran it again and 3rd step states E: SD card etc.........

(bad) installation aborted.... I dunno
[Droid Incredible Android Development] Conap:
Hmm...it really seems like it's getting corrupted during download or transfer to sd. I'm redownloading it now to doublecheck that the upload was not corrupted. I'm assuming you have not edited the zip at all?

The upload seems to be ok...did you check the md5sum...it should be 9149846f0c0f3136c1464255547c88bb check it on the copy on your sdcard
[Droid Incredible Android Development] Crans:
Both step 3s are blank in root manager....... will continue trying
[Droid Incredible Android Development] Conap:
Make sure you unmount the card from the pc before unmounting it from the phone to make sure the file doesn't get corrupted.
[Droid Incredible Android Development] Crans:
I ran everything on just the phone I had to run undo and go through the steps again through 2.5.1.2 in recovery maybe should post 2.5.1.2 download.... sense booted fine, pretty quick too.. going to play now :) thanks will deff respond soon the undo.zip is a must have with this mod
[Droid Incredible Android Development] Conap:
If your running sense flash this over the sense dualrom...it seems to make it a little more stable...just haven't updated op yet...posted this a few pages back.

http://www.multiupload.com/88T9LSK54W
[Droid Incredible Android Development] Crans:
Working great here just went from stock sense to CM7 in less then a minute and at the push of one button this is great.... Thanks
[Droid Incredible Android Development] blaine91787:
So if I wipe data/cache to install a new phone rom then will that wipe my internal rom?
[Droid Incredible Android Development] Conap:
No changing your normal phone rom won't affect the internal rom
[Droid Incredible Android Development] sanamkan:
This is amazing. I've been running this with the CM7 ever since Tuesday with no issues. I may have been the only one who used the emmc, but the tradeoff is worth it. Anyway, well done.

Also, is it sad that I only switch from my Sense ROM so I can use a wiimote with my emulators?
[Droid Incredible Android Development] Crans:
Anyway to change out the phone rom you supplied? My 2 personal favs are CM7 (currently on SD)(your supplied Stock Sense on phone) and Inredibly Re-Engineered 2.4 or the Incredibly Re-Engineered 1.1 z Rom .......... Great work this mod is deff up top
[Droid Incredible Android Development] Conap:
No not sad that's actually the point of this project. No matter weather you use one rom or the other there is almost always some little thing you miss about another rom. For me I use cm7 but really prefer the camera on sense roms....now i can have both....

Not sure what your asking here. I didn't supply the phone rom. You can use any rom you want for the phone rom you just flash the number 2 zip after flashing the rom to add the files needed to boot back and forth. Both the cm7 and stock sense roms i provided go onto the internal rom space on the emmc.
[Droid Incredible Android Development] sanamkan:
Spoke too soon. My phone crashed while running my standard ROM, Uber Z, a little while ago and ran the setup immediately after reboot. Naturally, I skipped setup and received a bunch of force close notifications. When I got to my homescreen everything was fine except the HTC widgets were misssing. However any application that didn't force close on startup had its data completely wiped. Running the CM7 Internal right now, and nothing seems to have gone wrong here. I've never had the issue before, so I'm 99% sure it was due to this. Any ideas why this might have happened?
[Droid Incredible Android Development] Crans:
You provided either sense or cm7 to go on the internal memory. My question is can it be possible to put any other rom than those 2 provided in the internal memory. I'd like to have Incredibly Re-Engineered and Cm7...... duh.. it just hit me... guess I ruled out putting CM7 on internal memory instead of sd and just putting Inc Re-Engineered on sd, due to alot of existing mods possibly getting lost in the process..... okay passed that.... would it be easy just change your 2 roms to 2 others like JagerRom and MIUI?
[Droid Incredible Android Development] Crans:
I ran into that and i had to run the undo.zip before restore and reinstall the previously installed mods to your sd card need to be undone, I know this doesn't explain cause but hopefully its a cure