yashsingh1/xdaforums huggingface dataset:
[Droid Incredible General] Conap:
Yeah try using v4...what kind of error were you getting?

I don't know that anyone has booted either of those on the phone. Most of the time people just chroot into ubuntu on the phone. I've messed with it some but I should look more into it.

You don't need to flash the createimg zips again. Once the img's are there your good. just install the new rom to phone and flash the installer zips.

Yes you can just copy the img's to your pc to keep as a backup. You can rename them if you want or zip them up so they take less space. Just make sure you name them back to system.img and data.img when you put them back.

I had not tested CM6 but I'll look at it. The img's take up the same amount of space on the emmc wether there is a rom installed or not. Installing a rom does not take up any more space. If you use your emmc for other things besides this it's probably best just to stick with 3 rom's on emmc to leave some space.

I'm using it with Remix B4 and it's working ok for me. Maybe try uninstalling and reinstalling the app itself. Only way it would go directly to fastboot is if it's not flashing the new boot.img after removing the old one. When the rom install's it extract's the flash_image binary to use to flash the boot.img. I guess it's possible that the binary did not get the right permissions set. You could also try from command prompt :

adb shell chmod 777 data/data/com.conap.drsettings/flash_image

see if that helps

If you have old method installed then use the zip i posted in the old method to uninstall DualRom. Then just flash the createrom1img.zip flash your rom like normal the flash rom1installer.zip. Repeat for additionall roms you want. It's fairly simple!!
[Droid Incredible General] jesssiii:
Conap, thanks for this awesome app! I'm constantly tinkering with my roms, but just moving them to phone, then reflashing the script putting it into one of the 4 (in my case 3) rom folders will automatically overwrite the older version with the tweeked one, correct?

I'm digging SalvageMod right now. It doesn't recognize the EMMC internal storage. Will that be a problem putting it on dualromX?

BTW, Your Carrier Name Change app is still getting lots of use since I prefer aosp roms. Thanks for that too!

DInc + Zeam Launcher

Chad's Incredikernel

CM7 Nightlies
[Droid Incredible General] todd3835:
For some reason, when I boot into one of my DRX2 roms, my "phone rom" appears to be gone..... when I try to boot into my "phone rom", it thinks it isn't there..... This happens from CM7 and Optimised GingerSense..... And I didn't see a reboot phone zip file.....

Edit: Turns out it's hosing my boot partition booting into one of the other roms on EMMC. Not sure why, but that's what's happening.....
[Droid Incredible General] deficitism:
I cooked up a new sense v3 ROM. Runs fine on the phone. Runs like poo on the EMMC. Seriously unusably slow. I'm not sure what the deal is. I'm going to have a look at your scripts and see if we can't make this run a bit smoother.
[Droid Incredible General] Conap:
If you use the rominstaller.zips it will erase the img's before installing the new rom. If you use the upgraderzips it will only erase the system img and keep your data. So if you want to update and existing rom. Flash that rom to your phone, install any updates or add-on's the flash the upgrader.zip for that rom slot.

Emmc not working on salvage mod should not affect it's use in this setup so you should be fine.

It's not exactly hosing the boot partition it's rewriting it on purpose. That is how it boots into the differen't roms. To use a rom on the actuall phone you need to flash the rom then run the phoneInstaller.zip so that it creates a backup of the phones boot.img for the app to use when you want to boot back to it.

This system doesn't alter the rom's at all. It only changes the boot.img to redirect it to the img's on emmc. There may be some loss of speed due to the speed of the emmc or the fact that it's using an img mounted as loop? I'm not sure if loop would cause loss of speed or not. I haven't noticed any huge loss in any of the rom's I use. The emmc read/write speeds should be ok since it's the same memory the phone normally uses for data/cache just a differen't partition.
[Droid Incredible General] corypaul:
tha mytouch 4g doubleshot rom works, and the stock kingdom rom works with this
[Droid Incredible General] todd3835:
Ok, I got it working now. I originally started with the v3 scripts. That zip file didn't have the phoneInstaller.zip inside, otherwise I'd have looked around for it's use. Can you update the OP to include that? It's not in the instructions, which is part of why I couldn't figure it out. It may have been in the thread somewhere and I just happened to miss it.

Also, do you have to run phoneinstaller.zip every time you move/copy a rom? Say for instance I have CM7 on the phone, Install the phoneinstaller, then move it to rom1. Do I need to install phoneinstaller.zip again? Or just if I flash a different rom? My thought was if it has to be done every time, why not put that into the rominstaller files. Still kinda new to this, so I'm just wondering.
[Droid Incredible General] Conap:
Sorry didn't realize I left it out of that zip and the op...oops!! No you only need to run the phoneInstaller.zip on the rom that you leave on the actual phone. Any rom's that you move to the emmc img's have all the boot.img stuff taken care of in the installer.zips. Sorry for the confusion.

Edit: Added that info to the op. Thanks for pointing out that it wasn't there!!
[Droid Incredible General] todd3835:
NP, I was going crazy at first, thought it was the rom I was using, it really screwed up my boot partition to the point where I had to wipe the boot partition. Like even flashing a new rom wasn't working, that's why I said it hosed it lol. Glad it's all figured out now =]
[Droid Incredible General] Treken:
I couldn't get it to work. I flashed the createimgforrom, then the rom, then the rominstaller and when I reboot it goes into a boot loop. Also, I saw boot-Rom zips and didn't know what they were used for. Can you tell me what I may have done wrong? I tried wiping cache and dalvik, and even user data prior to trying this app. I tried it more than once wuth the same results. I tried Flashing the latest miui rom found here. I also have tried flashing the Liberation rom during the process as well.
[Droid Incredible General] rpz3.14:
I have it running with SkyRaider 4.0 as ROM1 and Liquid Metal (New UI) as ROM 2. I'll probably put one of the new sense 2.1 or 3.0 ROMs on 3, maybe MIUI on 4, and CM7 on the phone, but that's for a future day.

Great work!

EDIT: I have GingerSense ReMixed (B4) as ROM 3 and it's still doing great. This is easily the coolest development for the Incredible.
[Droid Incredible General] jesssiii:
Conap, I've been using version 1 but see you're up to version 4 now. Do I have to start from scratch, or is some fancy reshuffling all that's needed?

I'm using 3 folders plus the phone rom folder. I have CM7, SalvageMod, and Ruby in rom folders 1, 2, & 3, respectively, plus Ruby still on the phone for now.

Thanks!

DInc + Zeam Launcher

Chad's Incredikernel

CM7 Nightlies
[Droid Incredible General] Conap:
If you've already flashed the createimgforrom.zip then you just need to install miui to the phone(wipe phone, flash miui) Then flash the rominstaller.zip. Make sure you wipe data and cache before flashing the miui rom(or any rom) You can try booting miui from the phone to make sure it installs correctly. Once it boot's up you can boot back to recovery and flash the rominstaller.zip and reboot.

No real need to start over from scratch as long as your rom's are functioning ok. None of the changes were really major. For future install's or upgrades to current installs just use the latest versions I posted and you should be good to go.
[Droid Incredible General] Conap:
Awesome and thanks....I'm also running Gingersense Remixed B4 and really like it as well....
[Droid Incredible General] todd3835:
I've had one minor issue after using the installrom zip files, of my boot image getting messed up on the phone rom. This can be fixed by flashing the phoneinstaller script (before booting the rom), or you can also go and format boot before installing the rom, just to be safe. Either way, you need to install the phoneinstallerv2.zip after the rom, so that you have access to the phone's rom should you boot to one of the others!
[Droid Incredible General] Conap:
This whole system uses all the phone's partitions to install the rom's to the img's including the boot partition so it will overwrite everything from the phone rom. You should either install your phonerom last and flash the phoneinstaller after that or make a nand and restore it after you finish the other rom's and flash the phoneinstaller on it. You are right that you need to flash the phoneinstaller to be able to boot back to the phone rom. The phoneinstaller.zip copies the phonerom's boot.img so that the app has access to it when you want to go back to the phone rom. The system works by replacing the boot.img everytime you want to boot to a different rom. Personally I don't even install a rom to the phone so that it's always available for me to use to install rom's to my 4 slots on emmc.
[Droid Incredible General] rpz3.14:
I do really like the Remixed ROM, but I was referring to the DualRom setup as the best thing on the Inc. This is amazingly awesome!
[Droid Incredible General] Coderedpl:
So wait, I'm not sure if I'm understanding correctly here, so forgive me. I've read through the pages but im still confused.

So basically this is what we do:

From recovery, we flash the createimageforrom1.zip (2,3,4) to initially create the images.

From there we wipe, and whatnot just as if we were installing a new rom on its own. Then we do rom1installer.zip, then essentially we can wipe, and install a new rom and use say rom2installer.zip, and etc?

From what i understand we DONT need a "5th" rom, or rom besides whats on emmc?

I'm also guessing to be able to switch between roms, from each rom, we also have to flash phoneinstallerV2 to each rom when we set it up?
[Droid Incredible General] Treken:
Thanks Conap. I'll try it again when I get some time.
[Droid Incredible General] todd3835:
1. Nandroid

2. Setup your spaces, createimageforromX.zip for each you want to setup.

3. If your current rom is one you want to keep, run romXinstaller.zip to copy that wherever you want. Or skip if you have a Nandroid of what you want as your "phone" rom.

4. Wipe, flash next rom. Flash romXinstaller.zip

5. Repeat #3 for each rom.

6. Wipe+Flash what you want as your normal phone's rom. Optionally restore from a Nandroid.

7. Flash phoninstaller2.zip so that you have access to the phone rom.

On a side note, for wiping I'd recommend the VR_Superwipe. Can be found at: http://www.virusrom.com/Tools/VR_SUPERWIPE.zip
[Droid Incredible General] Conap:
Everything you said is right except for the phoninstallerv2.zip. It only needs to be flashed on the rom that you leave on the actual phone.

Yes this is very concise and exactly the steps to be taken. Thanks.
[Droid Incredible General] caleris:
I spent a couple hours reading through the instructions to make sure I understood all.

This tool is amazing and is working really well. Thank you so much for your work.
[Droid Incredible General] Conap:
Thank you for A. The feedback and B. Reading first:D

Also for those who have other phones I think I'm close to implementing a universal set of these scripts that should work for multiple(possibly all) android phones. The universal method will use sdcard since most phones don't have the emmc storage though so I suggest that Inc users stick with these scripts.
[Droid Incredible General] trickster2369:
Reading in these forums is priceless. After all, isn't that a big part of why they exist? That being said, we'll see how well I read this thread. I am currently waiting for my phone to restore, then will reboot to check out this kick a@# idea. Fingers crossed.
[Droid Incredible General] todd3835:
NP. The OP is sooooooo full that I was a bit confused at first. Glad I could help!

If you go 5 posts up, I gave super-simplified instructions (assuming you've flashed before). Should get you up and running!
[Droid Incredible General] Coderedpl:
So im guessing leaving something on phone is required. Correct?
[Droid Incredible General] trickster2369:
I have flashed plenty, and those instructions are perfect.

I dl'd and copied files to my phone.

I flashed the createimg1.....zip.

The CM7 rom I had on my phone is one that I want to use, so I flashed the install1rom.zip.

I then wiped, wiped, wiped, and restored Newts Optimized Gingersense Beta3.

Booted it and it booted fine, so I went back to recovery and flashed the phoneinstaller2.zip to keep that as my phone rom. Rebooted. Everything seems to have worked fine. I opened up the app from the app list, opened fine.

Now for the test...

I pressed rom 1 to boot CM7

Stuck at splash screenhttp://media.xda-developers.com/images/smilies/mad.gif

Battery pull, hboot, recovery, reboot, would not boot phone, stuck at splash screen.

Battery pull, hboot, recovery, restore CM7 from before, reboot, booted fine.

Tried the whole senario again, same results.

What did I miss?
[Droid Incredible General] todd3835:
I'm running CM7 And Newt's Gingersense on EMMC, so I can confirm they work. Have you tried the bootX.zip? That will force it to load those the next time you boot. Not sure why it's not working for you, it's working great for me! Although I'm totally pimpin the Synergy Rom, it's the best Gingersense out! Nightly for 6/3 is borked, but 6/1 (no 6/2) is running great! I haven't even booted my other roms since I started using Synergy yesterday! Either way, I know those 2 particular roms work with DRX2 because I have them running on mine. Try doing a fresh install of CM7, install to EMMC and see what happens, just for the sake of trying.....
[Droid Incredible General] trickster2369:
Thanks for the response. Sounds like I'm doing things correctly, will try boot*.zip and/or reflash tonight.
[Droid Incredible General] Conap:
Your not required to leave anything on the phone. I don't run any rom's on my phone so that it's easily available should i want to update or change one of the emmc rom's

Sounds like your doing it right. Check that your flashing the same rom number for the createimg.zip and installrom.zip. If you can do adb logcat you can see if it's looping or if it's not finding the system partition. It's possible that the boot.img did not build correctly. Try running the installrom1.zip and rebooting before restoring your nand to see if it boots. Flashing the boot-rom1.zip is really doing the same thing as the app just doing it from recovery.
[Droid Incredible General] tiny4579:
I seem to be having an issue with Business Gingersense occassionally force closing on emmc at boot. For me, phone has force closed sometimes on boot and system force closed on boot once. After a few minutes everything starts itself up fine though. I know it works great on phone, so I wonder if something didn't copy over correctly or if there was a particular modification. I posted a logcat in the page for the ROM.

I might try Synergy tonight when the 6/4 nightly drops.

Also, I don't think the updater.zip will work that great for some of these gingersense roms as they install some apps to data and symlink to system for space. I know Business Gingersense does for sure.
[Droid Incredible General] Conap:
Android force closes things when they time out because it thinks they are unreponsive. It's possible also that if speeds are slower due to being mounted as loop that it's force closing due to just loading to slow. Also all the symlinks and data partitions are also copied over at install so the symlink's to system apps should not be an issue.
[Droid Incredible General] tiny4579:
I guess it could be the combination of mounting as loop and the huge size of 2.1/3.0 Roms.

So the force close is no cause for concern? That's good.

However my question still stands about the update.zip. I believe you mentioned that the updater zip just replaces system leaving data intact and the ROMS that install the apps to data and symlink to system would not have updated apps. Correct me if I'm wrong here.

And the backup img to PC came in handy when I ran rominstaller1.zip to upgrade CM7 instead of romupgrade1.zip and I just restored data and cache img files. However I did have to reflash gapps and I ran the upgrade zip that time and it worked fine.
[Droid Incredible General] Conap:
If the force closes are only when you first boot up and then go away after it get's fully loaded then I wouldn't worry about them. If they continue to pop up all the time you might need to try reflashing.

The zips leave the data.img intact(don't delete anything) but it will still copy over new stuff from data so it would update the system apps. Not sure that was tested so I can't say there won't be problems with that but it will copy the new system apps over.
[Droid Incredible General] Coderedpl:
So then where would I put phoninstallerv2.zip?
[Droid Incredible General] Conap:
You don't need that zip if your not gonna install a rom on the phone.
[Droid Incredible General] RegnierD:
But then we can have five roms at once and just restore Boot under Advanced Restore to get back to the phone rom once we have all our roms picked out. :D
[Droid Incredible General] Conap:
Yes if you want 5 roms you can restore a rom at the end. Restore the whole rom though not just boot. Then if you flash the phoneInstaller.zip on the restored rom it will install the DRX2 app and also it will dump the phone rom's boot.img to the emmc so that the app can use it whenever you want to boot back to the phone rom.
[Droid Incredible General] trickster2369:
Finally had time to try again this morning. Started by deleting all emmc partitions previously installed. Deleted multirominstaller zip(which was installed from my computer. Re-downloaded directly to my phone. Unzipped.

Flashed img for rom1, 2, 3, 4

Wiped data, cache, dalvick(cwm3.0.0.7)

Formatted data, system, cache, boot(cwm3.0.0.7)

Restored CWM7.0.3(which has been my daily driver last 3 weeks)

Flashed rom1installer.zip

Booted...

Stuck on splash screen for 10 minutes plus.

Battery pull

boot into hboot/recovery

Flashed boot-rom1.zip

Booted....

Stuck on splash screen

Am I not waiting long enough for it to boot?

Seems that I might be missing something. Looking for that "WELL DUH" moment.

I'm kind of stubborn, and won't give up until I get it to work.
[Droid Incredible General] Rom-Addict:
Ican only install 1 rom slot + phone rom or emmc is filled. ifi try any more i get loops. not sure why there's not enough room.

Inc
[Droid Incredible General] T-Keith:
Hey Conap, thanks for the great work here.

<edit>

seems like I got it to work now.

thanks,

-Keith
[Droid Incredible General] tomlang:
not working for me

:confused:

First I USB connected the memories via CM7's status bar menu, and deleted everything in the 8GB mounted drive.

Then I used the zip files to create all four image files.

Then I used the zip file to install my CM7 on image 1. It quit after a few seconds. I tried again, same result.

I rebooted and again mounted the two drives on my home computer. I don't see the new images on the 8GB drive.

Back into recovery, I re-created image 1. Again tried installing to image 1. The firs time, it quit after 10 seconds, the second time it took a reasonably long time.

I rebooted, but still appear to be running as before. No image files on the 8GB drive, and no sign of the program file needed to select ROMs.

What am I doing wrong?
[Droid Incredible General] i5aac:
Same issue here...
[Droid Incredible General] Conap:
Can you do an adb logcat while trying to boot it? If you see things happening then it's booting but if it's not mounting them right then it will say something like system/bin/sh not found. I think there is a possiblility that some of the phones don't mount the emmc fast enough so it's not finding the img's therefore it would give system/bin/sh not found error. I will upload a new version in a few minutes that should take care of it if it's your problem.

Do you have other stuff installed or saved on the emmc? when you mount it to your pc does it show if there is any free space?

Sounds like the createimg.zip's are corrupted and not creating the img's. Try redownloading or recopying them to your sdcard. Delete them off the sdcard first then copy over a new copy. Also I would try copying them while in recovery. I've found the file's get corrupted more easily when copying them when the phone is booted.
[Droid Incredible General] i5aac:
I have tried this every which way. I read the OP several times and felt fairly confident....I mean, its just flashing a few .zips--how hard could it be??

Anyway, regardless if what I try, I choose to pick a zip from SD card, navigate to createimageforrom1.zip and clockwork acts like its unpacking the update (or whatever it says), but after ten seconds or so, bounces me back to the main menu (reboot system now, etc....)

Noteworthy:

Clockwork 2.5....whatever...thought I read in the thread it had been tried with this, so shouldn't be an issue??

I have tried unzipping the files on both my phone and laptop, always w/ same result.

After, the createimage.zip fails, my SD card is useless until I reboot my phone. I can still mount it via usb in recovery and my pc can see it, but I can't edit, move, delete, or generally access the files on it. Additionally, I cannot flash a new zip (rom, etc...) Or perform a nand restore. Strange, right?

This issue is not Rom specific...duplicated this across several roms.

Also, my emmc is virtually empty....not that I received a space-related error, but read that it could be, so I cleaned 'er out.

Any other ideas? Currently running synergy 6/4, but tried with several others in the "known-to-work" list.

Thanks in advance...
[Droid Incredible General] Conap:
hmm...it may be an issue with clockwork 2.5...i tested my original scripts with the 2.5 cwm temporary zip but i've made alot of changes since i tested with that. All the testing since then has been down with cwm 3.08. I'm not sure why it's causing the issue with the sdcard but it sounds like recovery is mounting the sdcard to read the zip and then becomes the "owner" of the files which is why they are locked when you remount it. Probably because the zip is failing. The createimgforrom1.zip is fairly simple script but maybe cwm 2.5 doesn't have the resources to run it. If you don't want to upgrade your recovery you could try making the img's manually and then see if the installer.zip's work with cwm 2.5.
[Droid Incredible General] Conap:
for those that said it seemed to be installing correctly but then would hang on the splash screen try the updated version in the op.
[Droid Incredible General] tomlang:
still no luck.

using V5 and cwm v2.5.1.2

create appears to run ok

install quits soon after starting with some error

is says Status 0

I looked inside all the zipped files, and they appear to all be there
[Droid Incredible General] Conap:
are the img's being created on the emmc? check to make sure there is a data.img system.img and cache.img in a folder named rom1, rom2, etc....if they are there then if you can get me a log that would help.

flash rom1installer.zip...let it fail...flash it again...let it fail then :

adb pull cache/recovery/log > towhereeveryouwantittosaveonyourpc/log.txt

then attach log.txt here. It's probably an issue with the older recovery though I can't think of why it would be...
[Droid Incredible General] tomlang:
there are a few files on the emmc, but nothing that looks like your images.

I'm not set up for ADB right now, but just to get this going, were can I get the latest CWM ? Rom Manager thinks what I have is the latest.