yashsingh1/xdaforums huggingface dataset:
[Droid Incredible General] Conap:
Good questions...not this only uses what you put on it. With all 4 rom's installed you will only have about 500mb's left though. but you could install just 1 or 2 rom's and still have a couple gb's left to use. The only "problem" i've seen is that the emmc does not mount to pc correctly but this can be fixed by using the mount emmc options in the app i provided.

No does not erase anything on the emmc...just add's the folders and img's

The rom's do get installed to the phone like a normal install and then are copied into the img's. This is so the different rom's with different updater scripts will all install correctly and then just get moved to the img's. It will erase your current rom but you could either nand the current rom(which you should do anyway) and then restore it or you could just use the rom1instaler.zip (or rom2,rom3,rom4) to move your current rom to the emmc. It will copy all of your data and stuff over too. Then you can continue to install the other roms you want. Then if you want to put a rom back on the phone normally you can do that too.
[Droid Incredible General] justjayhere:
Okay... one more question: let's say I have a Rom installed in one of the slots and I want to flash a mod to that particular Rom... how is that achieved?
[Droid Incredible General] todd3835:
Ok, so how much space does each "slot" take, just out of curiosity?

So basically you could get a rom all customized, then do the rom#installer.zip to take it completely themed and all and move to EMMC? That sounds pretty damn hot IMHO =]
[Droid Incredible General] Pithism:
so technically can we have 5 roms?

4 on emmc and 1 on actually phone?

*and to resotre nand backup to phone do we install the phoneinstaller.zip first or after the nand backup/rom we like?
[Droid Incredible General] Conap:
Right now flash all your mods before moving the rom...i'll work on some way to flash it after it's moved.

data is 1000mb system is 270 cache is 120 so about 1.5Gb...they are adjustable if you really want to save the space. and yes you can customize it and then move it.

yep 5 roms total....install phoneinstaller.zip after restoring the nand. It just dumps the boot.img so it's available to the app and installs the app so it doesn't really do anything to the rom.
[Droid Incredible General] justjayhere:
So what is the "phoneinstaller.zip" used for? Do I need To install that before moving to slot. . Or only For rom left on phone.
[Droid Incredible General] Pithism:
wow this is awesome, one of the reason why i just recently purchased a friends INC.

Cant wait to see what other roms work on this

and do we need to use that modified recovery or is cwm 3.0.0.x good enough?
[Droid Incredible General] r2DoesInc:
Conap, sick work :)

You've been busy since I first met you :-)
[Droid Incredible General] Conap:
That's only need for the rom left on the phone

CWM recovery is fine...it's what I tested with...
[Droid Incredible General] T-Keith:
Same error after flashing unrevoked forever. My clockwork is verision 3.0.0.8 installed through the ROM manager in CM7. Could I have the wrong version? Is there any "settings" I could change?
[Droid Incredible General] Conap:
Possible the boot.img's did not get rebuilt correctly. I'm assuming you don't have issues with flashing a rom or restoring a nand. I would maybe start over with cwm 3.0.8 and s-off now. Other options are once again try to manually flash the boot.img :

adb shell

mount dev/block/mmcblk0p3 emmc

flash_image emmc/rom1/boot.img

See if it gives an error then. You could try deleting the zips from sdcard and putting a fresh copy on....you could also pull the recovery log and post it after flashing the zip(flash it twice to make sure the log picks it up) then do

adb pull cache/recovery/log /location/on/pc/log.txt

and post it here.

I think there is also a format boot setting in cwm you could try also.
[Droid Incredible General] T-Keith:
I tried redownloading and reflashing, the boot zips will not flash and I keep getting stuck on the flash screen. My backup restores fine so I'm going back to that. I haven't used adb since I tried it on my Eris and couldn't get it to work. I can't run it on my main two computers,(work computer, and CR48) so I will try to set it up this week on my Ubuntu Desktop.

I did find a few thread saying it could be a bad sector on my phone storage or an incorrect recovery for the Hboot.

thanks for the help,

-Keith
[Droid Incredible General] tomlang:
I think (hope) I have it working now.

Question #1: How can I tell if I am running from an emmc image (and which one) or from the phone?

Question #2: How can a create a nandrom file from an emmc image or transfer that image to the phone for updating and creating a nandrom file?

thanks, Tom
[Droid Incredible General] Treken:
nvr mind. I figured it out. I used dual rom app to mount emmc then right click emmc on desktop(looks like sd mounted icon) and select open in terminal.
[Droid Incredible General] Conap:
Yeah it could be a bad sector in your boot. There's a few file's that get added to the boot.im which would make it slightly larger then a normal boot.img so you might just not have the space to flash it.

If you go in a terminal or adb shell and type mount it will list all the drives on your phone listed. Look and see if you see system, data, and cache mounted on loop0, loop1 and loop2 then you know your booted from the emmc img's. No way to really tell which one except by remembering which one you booted into.

You can just copy the img's over to your pc and save them as a "nandroidthe " backup. If you want to update your rom just flash the the rom to the phone and flash any add-on's or updates the use the rom1upgrader.zip's for the slot the rom is in. Example:

CM7 Nightly 90 on slot 1

Updating to nightly 91

wipe phone

flash nightly 91.zip

flash any add-on's or kernel.zips you want

flash rom1upgrader.zip

This will update your rom without wiping your data.
[Droid Incredible General] caleris:
I think that this is a great tool and want to say thanks. On my phone it causes the ROMs to lag quite a bit, can you suggest a way around that? Thanks again.
[Droid Incredible General] Conap:
I have some lag on gingerbread sense based rom's but not really on cm or stock rom's. But it's not really bad on my phone. Someone suggested earlier to format the internal storage from with in the phone settings and then reinstall. I formatted mine with parted in recovery. Overclocking may help some but I think they are getting bottle necked by the read/write speeds. I'm looking at upgrading it to use ext4 but it might not be universal as I'm not sure if the stock kernel for the inc has ext4 support? Any body know if it does? I've also messed around a little bit with the "sdcard" fix only doing it for loop device instead of sdcard. Something like this:

echo 4096 > sys/block/loop2/queue/read_ahead_kb

echo 4096 > sys/block/loop1/queue/read_ahead_kb

echo 4096 > sys/block/loop0/queue/read_ahead_kb

from adb shell or terminal. By default it's set to 128. You could try the 4096 or maybe try 2048 and see if that helps at all. If it does we would need to add it to a script to run at boot or hard code it into the init.rc which I could add that to the installers if people test it and notice a difference.

If anyone has idea's on filesystems or how to improve the read/write speeds feel free to suggest it.
[Droid Incredible General] caleris:
I just do this from adb shell? Do I need one of the ROMs booted to do this? Or can I boot into one of them after doing this? Thanks.
[Droid Incredible General] Conap:
You will need to be booted into the rom for it...it will only affect that rom and I don't think it sticks after reboot either. That's really just to see if it helps at all.
[Droid Incredible General] caleris:
I will try this a little later today and let you know what I find. Thanks.
[Droid Incredible General] caleris:
Sorry, no, the lag is the same. I am running OMFGB 1.2.
[Droid Incredible General] tiny4579:
I just made the change for all three loop systems to 4096. It can be changed with root explorer but you have to navigate to /sys/devices/virtual/block instead of /sys/block if you feel more comfortable with it. I will have to keep an eye on it to see if it helps.
[Droid Incredible General] Logiic:
I think that someone else already mentioned this, but I am also having very bad lag issues when I use DualRom to flash GingerSense ROMs, especially sense 3.0 such as Kingdom Stock and Uber Kingdom. However, when booted normally both work fine...
[Droid Incredible General] caleris:
See above posts.
[Droid Incredible General] Logiic:
Yeah I tried the fixes listed but none seemed to work for me.

I just wanted to confirm that there was another user having issues with GS based ROMs, and on multiple GS ROMs at that.
[Droid Incredible General] Conap:
I don't beleive the issue is actually a problem with GB rom's as much as it's just more visible in gb rom's because they are not as optimized for our phones as the other rom's. I think it's getting bottlenecked by the read/write speeds of being mounted as a loop img. I've tried switching to ext4 filesystem but this only works on custom kernels that have ext4 support and I don't really see a noticeable improvement. I think mounting them with the noatime and nodiratime options may help. I'm testing that now. If you guys want to test you can do adb shell then:

busybox mount -o noatime,nodiratime,remount,rw dev/block/loop2

busybox mount -o noatime,nodiratime,remount,rw dev/block/loop1

busybox mount -o noatime,nodiratime,remount,rw dev/block/loop0

I guess my next option would be to try a yaffs2 filesystem but I'm learning as I go so it takes some time lol. I don't know alot about read/write speeds but I assume it has to go through an extra step to read and write into and img file rather then a normal filesystem.
[Droid Incredible General] Logiic:
I just saw this post and I have to be up in about 6 hours for work so I'm not going to mess with it tonight but if it doesn't end up working and you think of other things to try, shoot me a pm and I'll test tomorrow for you.
[Droid Incredible General] tiny4579:
Unfortunately there's still lag. I tried applying both tweaks to see if a combination of tweaks would help. There still is noticable lag for me. This is on Optimized Shift. Synergy runs great as a phone ROM. If I figure out something I'll be sure to report.
[Droid Incredible General] :
I would really like to do this but I feel like the OP is a bit to technical and I need it a bit dumbed down :)
[Droid Incredible General] Conap:
Sorry I'm not great at explaining things try this:

Make sure you have room on the internal storage ( the 6.9gb partition that mounts to the pc like the sdcard)

In CWM 3.08 Recovery flash:

Make a nandroid backup

flash createimgforrom1.zip

wipe data/cache

flash rom.zip for the rom you want to install

flash rom1installer.zip

Reboot

Assuming it boot's ok then you can boot back to recovery and repeat the step only using the createimgforrom2 and rom2installer.zips and then same with 3 and 4 zips if you want that many rom's.

Once finished you can restore your nand and flash phoneInstaller.zip then reboot and you can open the DRX2 app that should be installed on your phone now. When you open the app you can name the rom's by hitting menu/set names. You could do this after the are all installed or each time you boot into the rom after installing. Then just hit the button for the rom you want to boot to using the DRX2 app.
[Droid Incredible General] SynisterWolf:
if i install an app on rom1 will it show up on 2 3 4?
[Droid Incredible General] tomlang:
I wish!

I'd be happy if the apps that had been moved to SD were available as-is from all the roms.

But unfortunately, you have to do the installs and moves again for each rom.
[Droid Incredible General] SynisterWolf:
so its like a nandroid manager. so does it have to flash each rom when you switch then? like if im on rom1 and go to rom2 it will boot into recovery and automatically install the rom i have selected?
[Droid Incredible General] motempo:
No, once the ROMs have been moved to emmc, they do not need to be flashed again. The DualRomX2 app, to put it in simple terms, changes the boot process so the phone will boot the images from whichever ROM on emmc, or phone, you have selected. When you choose a ROM within this app, the phone shuts down and then reboots using the image for the ROM you have selected, not having to flash anything. All data is saved within that ROM's data image, so whenever you boot back to another ROM, whatever apps, sms, mms, etc that was on the ROM the previous time it was booted will still be there. So its almost, but not really, like a nandroid manager; except it takes nowhere near as long to have to backup, restore, flash, etc. each time you want to change ROM.
[Droid Incredible General] :
When you say:

"Assuming it boot's ok then you can boot back to recovery and repeat the step only using the createimgforrom2 and rom2installer.zips and then same with 3 and 4 zips if you want that many rom's"

You are saying boot back to recovery to create a img of the next rom? But how does it know which one to pick? or do I have to have the rom I want for say "rom2" currently flashed on my phone? I guess I am confused how it chooses the img for each rom slot? Do I have to have lets say CM7 FLASHED at the time of "createimg" and then to do the next rom I want do I have to have UBER FLASHED to "createimg2".

Thank you for your support :)

EDIT: Also do I have to have all 6.9GB free? What If I only go back and forth between two roms? Can I just make sure I have enough free for them? Or does the app require all of it free?
[Droid Incredible General] Coderedpl:
This is going to be a cross post between two topics.

But yesterday/today I noticed that when I flashed Synergy Nightly 6/8 and then did the installrom1.zip for the dualromx2 thing, and then reboot it was really slow. It actually got to the point where I couldn't even use the rom. So i tried something different. I flashed the rom, booted, set it up, and THEN did the installrom1 or whatever, and it seems to be running better.

Now i'm not sure if its related to the rom or the putting the rom on emmc.

Any ideas?
[Droid Incredible General] Conap:
You only need free space for the number of rom's you want. If your just putting one on emmc then you will need a little less then 1.5 Gb's free. if you put 4 rom's on emmc it will use pretty much all of the emmc storage so you can use however much you want.

The rom that is currently flashed to the phone will get moved into the img's for that slot. This system install's the rom to the phone normally and moves it into the img's. That's why you want to do a nandroid of your current rom so that you can restore it at the end because you need to wipe the phone and flash each rom you want to install to emmc. When you flash createimgforrom1.zip it makes a empty img on the emmc, then when you flash the rom you want it install's to the phone then when you flash the rom1installer.zip it moves the rom from the phone to the img's that were created and edit's the boot.img to boot from those img's instead of the phone. Hope this clears it up a little...
[Droid Incredible General] Conap:
When you flash a rom and boot it for the first time it does alot in the background as far as writing files and setting everything up. Since you booted normally and set it up all those file's were created and then moved to the img's so that when you booted to the img's it didn't need to create all those file so it's not doing near as much work in the background. So what you noticed would be normal.
[Droid Incredible General] Coderedpl:
Hmm, I thought it might be doing something but never thought about how long it should take. Any idea on time-estimate I should give it? Just a general estimate.

I'll try it with the next slot I flash.
[Droid Incredible General] Conap:
Alot of it's done before the screen even comes up but after setup just wait for it to restore apps...booted into the phone probably just a few minutes depending on how many apps you normally have setup.
[Droid Incredible General] tomlang:
Just curious...

If I already have created and installed rom 1 and then run

createimageforrom1.zip again, what happens? Is the original image cleared or just left as-is?

Thanks
[Droid Incredible General] Treken:
Conap, your app is working beautifully now! Afa ^^^ , you did what I was doing. Don't flash createromimg more than once, it screws up something somehow(I think). After you install createromimg, just flash rom and flash rominstaller. Oh, factory reset/wipe prior to each time you flash a rom or the rom will more than likely boot loop.

Running liquid metal light on slot one, green rom on slot two, slalvage mod on slot four.
[Droid Incredible General] Conap:
It will create new blank img's and overwrite the existing ones. It's not needed more then once though unless you delete the img's for whatever reason.
[Droid Incredible General] Conap:
Progress maybe...

I think I've made some progress with lag issues. I added a datadata.img and made the datadata.img and the system.img ext2. data.img and cache.img are still ext3 to help prevent file corruptions on reboots. I also mounted all img as noatime and nodiratime. The ext2 seemed to help alot with the lag while still having the ext3 parts to prevent the data from getting corrupted on reboot. There is still some lag when the phone first boot's up but it get's much better as the phone settles down a little.

I have not thoroughly tested the zips. I used the createimg's and the rominstallers for slots 1 and 2. but haven't had time to flash 3 and 4 yet. I figured I'd let some of you try it out before I add it to op. So for anyone with the lag issues this should help. It should improve all rom's but mostly the GB sense ports. Would love to get these tested and get some feedback if possible. You will need to reflash the createimg.zip's since I changed the img's up a little bit.

http://www.multiupload.com/L9EK975UZ8
[Droid Incredible General] o0 DIDDY 0o:
To try it out with existing ROMs can you just use the upgraders or do you have to start from scratch? And if you can use the upgraders do you wipe first?
[Droid Incredible General] Conap:
you would have to start from scratch for each rom because it create's the img's differently. If you have 4 rom's set up you could leave 3 the old way and just start from scratch with one to test it.
[Droid Incredible General] o0 DIDDY 0o:
Sounds good ill give it a shot this afternoon. Thanks!!
[Droid Incredible General] tiny4579:
I will test but probably not till Sat night.
[Droid Incredible General] tiny4579:
Fyi you can mount ext3 as ext2 if the file system is clean. But it's probably best to start fresh.
[Droid Incredible General] Ruggerxpunk:
Quick question on how to use this Rom switching system.

I have CM7 as my daily right now.

So based on the OP, if I want to keep it in Slot 1, I just flash "createimgforrom1", then skip Step 2?

It's confusing because then Step 5 says to do a Nand Restore then flash "phoneinstaller".

I'm just not clear on what "phoneinstaller" does different than "rom1installer"

Thanks for any help.

PS my goal is to have the CM7 I have now as my Rom1, then MIUI Rom2, UberKingdom Rom3.
[Droid Incredible General] o0 DIDDY 0o:
Still laggy for me with V6
[Droid Incredible General] Conap:
Thanks guys....

If you want to move cm7 that's on your phone now to slot1 then you are correct just skip step two. Restoring the nand at the end would be if you wanted to keep your current rom installed to the actual phone. The rom1installer.zip moves the rom to the slot 1 on the emmc where as the phoneinstaller.zip just set's up the rom that is staying on the actual phone to work with the multiboot system. phoneInstaller.zip does not move the rom to the emmc. If your starting from scratch I would recomend using V6 found here http://www.multiupload.com/L9EK975UZ8 I haven't added it to the op yet but I did more testing this morning and everything seems to be installing as intended so you should be good to go with them.
[Droid Incredible General] Conap:
I don't think we can get rid of the lag completely. The inc uses the nand memory with yaffs2 for the system and datadata partitions. It's alot faster read/write speeds then the emmc. You can't boot a yaffs2 img as far as I could find and I don't think it would work from the emmc either way. The way I did it in v6 was the best I could find for getting the fastest read/write speed on the partitions we have available. Did you see any improvement? Mine is still laggy everytime I boot into it but if I give it a minute or 2 to settle down it's not too bad. The weather lock screen loads smoothly and unlocks smoothly for me which was a big improvement from what I was experiencing. I'm still open to idea's and suggestions but I did alot of reading on filesystem speeds and the options we had available and this worked the best out of anything I could find.
[Droid Incredible General] o0 DIDDY 0o:
The lock screen i agree is much better, If there is an improvement in speed on everyday use its miniscule. Its about 2 second wait for each app I open. Not a big deal the Pros definitely out weigh the Cons here. Keep up the good work!!
[Droid Incredible General] Conap:
Ok thanks for the feedback...hopefully as the GB sense port's improve the lag will go away.
[Droid Incredible General] o0 DIDDY 0o:
Just tried it with Newtoroots Optimized Z 2.2, it has the same lag. I dont know if that helps at all.
[Droid Incredible General] Conap:
If your familiar with adb and you feel like doing:

adb shell

mount

then post the output so I can make sure it's right I'd appreciate it. If not it's not a problem. You should see system on loop0 as ext2, data on loop1 as ext3, data/data on loop3 as ext2 and cache on loop3 as ext3. We could try mounting cache as ext2 also since if it get's corrupted we could wipe cache and let it rebuild...i'll have to test that out when I get time. Going out of town for the weekend so won't be till next week though.
[Droid Incredible General] o0 DIDDY 0o:
On terminal emulator i have : loop0 ext2, loop1 ext3, loop2 ext2, loop3 ext3

Anything else you need from the output?
[Droid Incredible General] Ruggerxpunk:
*Edit* Nevermind I figured it out

I absolutely love the idea and the effort, but with the current lag presented, it makes the ROMs on EMMC unusable.

Amazing idea though. Brilliant.
[Droid Incredible General] tomlang:
Conap, Please tell me where to get these scripts:

bootRom1.zip, bootRom2.zip, etc

I threw them out when I installed the newest set of files, then needed them when DRX2 failed to work.

Thanks again, Tom
[Droid Incredible General] Conap:
http://www.multiupload.com/NDGJPYN3F0 Sorry about that I keep forgetting to put them in the zips.
[Droid Incredible General] Conap:
No that's good...thanks...it looks like it's setup right.
[Droid Incredible General] Rom-Addict:
Thanks for your hard work!!!

love this, 4 roms!!!

CONAP=awezome
[Droid Incredible General] Conap:
What rom's did you try? The only rom's that I have an issue with lag is the new GB Sense ports. The others should do fairly well on emmc. I'll probably just stick the GB sense port on the actual phone and run it like that and save the emmc for other rom's. I think once we get the kernel source for GB kernel and we start tweaking it a little then most of the lag should go away even for the GB ports.
[Droid Incredible General] tomlang:
Hey Conap, Here's the list of roms this has been tested with, right from your OP. Which ones do you recommend to try and which ones to wait until they see kernel tweaks?

Thanks.

MIUI

CM7

SkyRaider 4.0

GingerSense Remix-B1-INC

Uber-z_RC3-1

Nil's Busines Sense

Leaked GB rom

WarmZ

uber kingdom sense 3.0 (1.0.1)

mikmik's beta 3 (sense 2.1 w/ 3.0 additions)

Incubus's Stock 2.0

mytouch 4g doubleshot rom

stock kingdom 3.0 rom