yashsingh1/xdaforums huggingface dataset:
[Droid Incredible General] Leshy01:
I know this is a terribly old thread, (and I posted on the wrong one earlier today) 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 General] Conap:
Well I'm not exactly sure what type of filesystem is used in the img's made from the cwm backup's but they might work. The biggest issue with that is that there would be no room for data to grow since it only makes img's large enough to hold the data that's there. You could always try it out and let us know but you would still have to run the script to modify the boot.img which in turn will copy the rom's over anyway so I'm not sure you would gain anything by using the backups. One option I hadn't thought of before now was that if you have nand's of multiple rom's setup how you like you could restore them one at a time and use the installerzips to move them to emmc so they would go from being nands to being useable roms.
[Droid Incredible General] jesssiii:
Yes, that's exactly what I'd planned to do. But my question was this:

Why bother using your method when I already have the backups I can restore? If I want to change the backup, I can restore, make changes, then re-nand it. And with RomManager I can name them.

Please don't missunderstand. I'm not criticizing, only trying to understand. I find this very impressive. And slightly intimidating.

EDIT: After rereading your reply, I see you said they go from being nands to useable roms. So what you have is a way to change between different roms on the fly, so to speak?

DInc + Zeam Launcher

Chad's Incredikernel

CM7 Nightlies
[Droid Incredible General] Conap:
Feel free to try but I'm not sure the nand img's will even boot and then your problem is that your images will be full so you won't be able to add anything...there will be no room for the phone to save all the data it incurs through normal use. The rom's that get copied to the img's on the emmc are bootable..they aren't backups. Maybe I'm reading your post wrong but this is not a system of backup and restore. It is allowing you to boot between differen't roms.

Edit: after rereading you edit lol I realized what your saying. No this is not creating backups this is creating multiple rom's that you boot back and forth between using the app I wrote to do so.
[Droid Incredible General] jesssiii:
If I delete apps or receive sms's while in one rom, then boot into another, will the changes be reflected or will I just pick up where I last stopped using the other rom?

DInc + Zeam Launcher

Chad's Incredikernel

CM7 Nightlies
[Droid Incredible General] tiny4579:
I love the simplicity of this for installing ROMS and that you can boot more than 2 :D
[Droid Incredible General] Conap:
It will just pick up where it left off....all the rom's are independent of each other.

After all the fun you had with the original I figured you might like this a little better lol.
[Droid Incredible General] Pithism:
Thanks

And wanted to give you a heads up on the roms im using that work

-skyraider 4.0

-uber GingerSense RCMIX S B 1.0

-OMFGB 1.2.0

-Uber Kingdom B 1.0.1 Sense 3.0

-Warm z two point two as my main phone rom

also i have a question?

If i want to update a rom in one of my emmc slots all i have to do is boot up the rom i need

to update go into recovery and update the rom to the newest version then reboot and ill be back to the new update

so for example wanna update cm7 and its in slot 1 boot into slot 1 go into recovery and update cm7 then reboot and il have a new version cm7
[Droid Incredible General] justjayhere:
I believe that once you place a Rom on the EMMC you can't "flash" updates or Mods.. so it would be best to put "Finalized" versions on EMMC and leave the Beta you are currently playing with as the phone Rom to flash updates and or tweaks. Plus.. you can still backup multiple Roms like before and use this multiboot solution at the same time.
[Droid Incredible General] Pithism:
so i can just make nand backups and put those backups in emmc slots?
[Droid Incredible General] justjayhere:
[Bug] I have the GingerSense RCMixHD Rom as my "phone" Rom and flashed the zip to install the DualRomX2 app and though it appeared to flash successfully.. it didn't install the app.

[Tip] So; using RootExplorer, I extracted the zip and installed manually and it works fine.
[Droid Incredible General] Pithism:
yea i did the same thing happened to me and i did the same thing was going to tell people too but you beat me to it!!! :D
[Droid Incredible General] justjayhere:
From what I gathered reading earlier post.. you should be able to boot Rom from Emmc, nand backup, wipe data & cache, restore (which would now make it the phone Rom), flash update/mod's, then move back into a slot.

Edit: I was mistaken... you can't nand backup a Rom once it's on Emmc
[Droid Incredible General] justjayhere:
Ok: my setup...

Slot 1-UberZ

Slot 2-CM7

Slot 3-MIUI

Slot 4-SR4

Phone-RCMixHD (beta3)

Plus: WarmZ 2.2 nand backup

This is awesome... now switching Roms is as easy and quick as rebooting my phone... everything is just as I left it... no need to backup before switching... NICE!
[Droid Incredible General] Pithism:
yea that actually makes a lot of sense actually, ill test it later when a rom i have gets an update

****also another tip to everyone like justjayhere stated on post 50, that some roms dont install the app, i think its gingersense roms with sense 2.1, 3.0 or combo of both that have the problem so just go to post 34 and the app is there. I have two of those roms in my emmc and they didnt boot with the app***
[Droid Incredible General] justjayhere:
[Tip] For those that already have nand backup's...

After installing your slots: just wipe data, restore nand, then move into one of the slots For each backup.
[Droid Incredible General] justjayhere:
Also I noticed: on these same Roms.. the "bootRom1(or2,3,4).zip" option from recovery doesn't work either (put me in a bootloop).. so I pulled battery.. booted into hboot..then into recovery.. booted into one of the non-gingersense Roms.. then using DualRomX2 App.. booted into the GingerSense Rom (then manually install DualRomX2 App as listed in my post above) and all works great.
[Droid Incredible General] Pithism:
Yea im not to worried about dealing with minor bugs like these along the way (i had similar problem but with skyraider 4.0 but i think i didn't work for me because i didn't install the createimageforrom1.zip and rom1installer.zip properly the first go around [forgot to wipe in between] )

the bugs dont seem that hard to work around, and plus as easy as it is to do this setup i wouldn't recommend a newcomer to do this that isn't flash happy, so for a normal flash addicted person i think that they will be able to figure out how to fix these minor bugs when they occur.

but good tip and thanks overall your really coming up with great tips so far keep it up
[Droid Incredible General] justjayhere:
Wow... just ran Quadrant benchmark on UberZ in slot 1 and scored 1754... nice.
[Droid Incredible General] renzo.olivares:
its not nice its UBER lol
[Droid Incredible General] Lexus One:
How do I do Market application updates on any particular ROM, and then save those app updates so that the next time I boot to that ROM I have the current updates?

I assume you can't do this because each ROM is NOT a virtual machine..?
[Droid Incredible General] justjayhere:
Right...... lol :-)
[Droid Incredible General] Conap:
Ok lots of questions overnight so I'll try to cover them...first Lexus One these aren't virtual machines they are actuall roms so any updates/changes you make will get saved for next time you boot into that rom.

About the Gingersense rom's not installing the app I did notice that late last night but I'm not sure exactly why it's doing that so I will take a closer look. Although you guys seemed to figure it out on your own that you can just install the app yourself.

Edit: After looking at Gingersense rom it looks like they don't use a system/app at install which is where my script is trying to put the app. I'll change that up when i get a chance. You can also extract the DXR2 app from any of the rominstaller.zip's in the app folder.

So the bootrom1.zips do NOT work for gingersense roms? I will have to look at that too. I think I might know why that doesn't work. I guess as long as they get you into at least one of the rom's so you can get back to the DRX2 app they are doing thier job.

As far as the Nands I think there is confusion. If you do a nand it will only back up the phone rom that's it. If you really want a backup you can just copy the img's from your emmc to your pc then to restore them just copy them back to emmc. Just make sure they are in the same emmc slot.

If you want to update a rom at this point you will pretty much have to do a fresh install. I can probably make some zips that only copy the system partition so that your data does not get wiped. I'll put that on the list of ideas.

Alright If you asked a question that I didn't answer in this post please re ask it cause I missed it. If my answers aren't clear feel free to ask more questions...thanks for the feedback guys....
[Droid Incredible General] Conap:
Do you remember any more info on this error like what slot/rom you were booted into before you flashed the bootRom1.zip and do you remember if it was bootRom 1,2,3 or 4? I just went from CM7 to recovery to bootRom.zip which is Gingersense and it booted ok so it might be a problem from going from a specific boot.img to a Gingersense boot.img.
[Droid Incredible General] corypaul:
So tha last rom. You install will have to be your phone rom
[Droid Incredible General] justjayhere:
Well technically speaking you do not have to have any rom on your phone.. however if you do wanna make changes and flash mods to a particular rom that Rom will have to be on the phone..not in one of the slots on Emmc. 4 example.. beta's that you know you'll be making lots of changes to etc.
[Droid Incredible General] Conap:
Yes you will have to flash or restore a nand of whatever you want on the phone after setting up the emmc's. Personally 4 rom's is plenty for me so I'm just leaving the phone available to use for installing other rom's to emmc. It's just easier that way. If you keep a rom on the phone then you have to make a nand and then restore the nand after doing the other rom's which is time consuming.

On a side note I think I have a way to upgrade rom's and install add-on's...should be uploading soon.
[Droid Incredible General] rberry88:
A couple questions, but first what I did:

I installed 4 roms to the 4 emmc slots and all works, below are the roms:

1. nilsP Business Sense Desire w/ Lou's #8 kernal and stock sense mod

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

3. Incubus's Stock 2.0

4. MIUI 1.5.27

For each one I flashed the createimg.zip file for each emmc slot, flashed and booted the rom, then flashed the installer.zip, booted into the rom again and went into the DRX2 app and named the roms before continuing to the next one. Everything works as planned.

Now for my questions:

1. what is the "phoneinstaller.zip" that is inlcuded, or what is it supposed to do, I haven't gotten brave enough yet to flash it.

2. Possible user error or just bug - I had my first 3 roms setup and working and then I rebooted to recovery and flashed MIUI rom to the phone and then I had the idea to put it into slot 4 of the emmc so I rebooted to recover and flashed the createimgforrom4.zip, then thinking since the rom was already on the phone and booted once, I decided to go to the next step and since I was already in recover just flash the installimgrom4.zip and then rebooted the phone. It booted back into MIUI (it was the rom on the phone), when I went into the DRX2 app in MIUI and selected rom 2 to boot to which worked fine. I then went into the DRX2 app in that rom and selected MIUI (rom 4) to boot to which is also the rom on the phone and it will only boot to the bootloader screen. I boot into recovery and tried the bootrom4.zip but it again boots only to the bootloader screen.

So I got 3 roms booting fine from the app and I'm not sure if it's because of the steps I took to put rom 4 into the emmc slot or that it is the current phone rom that is making it act this way. I'm going to try wiping the phone rom and re-flashing MIUI and then flashing the installrom4.zip again to see if it fixes it.

Or do you have any input on the specific steps I should take?

whew that's alot of typing.
[Droid Incredible General] Rom-Addict:
Cani flash roms one after the other in recovery? (Ie flash create img,then rom,then rom slot) or doi Havto reboot in between?

Inc
[Droid Incredible General] Conap:
It should have worked the way you did it but like I said when copying that much data around things will get corrupted some times...I would just wipe the phone reflash miui and rom4installer.zip again to get a fresh start.

No need to reboot in between just make sure to wipe the phone between flashes...
[Droid Incredible General] rberry88:
Ok, I re-flashed MIUI and booted into recovery and flashed the installerrom4.zip and everything is working fine.

Question: Is the phoneinstaller.zip file to basically flash the DRX2 app into the rom that is on the phone?

I saw my emmc size is now down to 1.60MB (yes MB :eek: ), is that too low? I haven't noticed any issues with loading any of the roms but I suspect this could cause issues. I poked around in emmc and moved the stock wallpapers to my sdcard and my size went to 4.50MB for emmc. Not sure what else to remove or should I just play it safe and stick with 3 roms on my emmc? And if so, can I just delete the rom4 folder from the emmc and all should work fine?
[Droid Incredible General] Conap:
phoneinstaller.zip install's the app to the phone rom like you said but it also make's a copy of the phone rom's boot.img so the app can flash back to it. The space on emmc won't affect the rom's cause they work inside the img's and there is plenty of room in there. The only issue you might have is that if you flash the phoneInstaller.zip it needs room to save the boot.img which is about 3mb's so as long as you have room for that you should be ok.
[Droid Incredible General] tiny4579:
Very nice so far. Should make kernel updates much easier.

Just a quick question. I noticed that CM7 on emmc is mounted as ext2 while a couple of the other ROMs were ext3. I know that ext3 is slower due to journaling but has better data integrity because of that as well.

Biggest pluses by far is that I'm not having the lag issues I had with the first version and I've been able to load any ROM I wanted to so far with ease.

The ROM's I'm running currently are:

CM7

Uber Gingersense RCMix S B1

Skyraider 4

Miui 1.5.27.1

So you can add Uber Gingersense to the list.
[Droid Incredible General] tiny4579:
What would be awesome for this is to have a central SMS storage so I don't have to keep doing a backup/restore with GO SMS.
[Droid Incredible General] Conap:
hmm...maybe i have a typo somewhere cause they all should be mounting as ext3...which slot do you have cm installed on? I would assume one from the way you listed but I thought i'd ask so I can check that.

Edit: i just checked my cm and it's mounted as ext2 also...
[Droid Incredible General] tiny4579:
I do have them listed in order.

CM is slot 1 for me. MIUI is slot 4 and also ext2.

My slot 2 and 3 ROMs are ext3.

PS. On the subject of filesystems, would ext4 provide noticeable improvement? I know the kernel I use for CM and MIUI does provide ext4 but is it worth the trouble messing with the ramdisk for it. I could mount ext4 before but I could remount the same partition as ext3 so I'm not sure I fully converted it to use all the ext4 features.
[Droid Incredible General] KJW73:
I know that I'm retarded, but will someone please explain this to me? I have downloaded all the files that I needed for this, except the createrom(1) download. I guess that is what I need. I'm truly not sure. I really, really would love to have this on my Inc. So if someone would please explain to me what I need to do to get this done I will be truly grateful and extremely appreciative. Thanks.

By the way, this is unbelievably awesome!! Thanks for the good work!!!
[Droid Incredible General] RegnierD:
I was having issues with the ADB commands, so I just opened all the IMG creation zips and edited their .sh scripts with Root Explorer, repackaged, and all worked wonderfully.

I wanted:

System = 512mb

Data = 1024mb

Cache = 256mb

Just to be safe and guarantee that there would be no issue of running out of space, especially with all the monster roms coming out.

I'm seriously impressed with how far this has come. Who'da thunk we could have five roms ready to go at the click of a button?
[Droid Incredible General] Conap:
All the files needed are in the multiinstaller.zip....unzip that file on your pc and then copy those zips to your sd card. then flash createimgforrom1.zip, then flash your rom, then flash rom1installerV3.zip and reboot ....just do the same pattern for the other rom's you want using the zips for number 2,3, and 4.

I don't know if it would be an improvement but since all kernel's don't support it at this point(i don't think) then it wouldn't be universal. I'm not sure why aosp rom's are mounting as ext2 though they are clearly mounted as ext3 in the ramdisk.

This was a good idea...never thought to just tell people to change the numbers in the zip. They are fairly easy to find. Those numbers are definitly never gonna run out of space though. It should be noted that since the rom's have to be installed to the phone before being copied to the img that they are still limited by the size of the system partition so there probably isn't a need for an img that big. It won't hurt anything of course.
[Droid Incredible General] RegnierD:
Though, if you get with devs to have their large roms (Sense 3.0, specifically) set up into these images, the images could be as large as they needed, so the need for massive thinning of the roms would be eliminated. I think a pre-packaged image for a Sense 3.0 rom with everything in it as it comes would be a pretty solid idea.

I just wanted to have plenty of space should the need for it ever arise. :D
[Droid Incredible General] Conap:
Yeah I would think if the dev was going to do a larger rom that had to run on this system then they would build it as a system.img so it can just be dropped on the emmc. I do believe this is being worked on.
[Droid Incredible General] tiny4579:
That is not necessarily a bad thing as ext2 should be faster due to not having journaling; however it should be ext3 for data integrity. As far as yaffs2 (which is used in system) vs ext3, I don't know which is better.
[Droid Incredible General] Conap:
Well I was mistaken anyway once I looked back at the ramdisk it was not specifying what to mount it as. Why aosp rom's would mount it as ext2 instead of ext3 I don't know but they are. I corrected the problem so now I just have to fix all the zips.

Edit: I uploaded the fixed installers and upgraders...if you have an aosp rom installed and it's currently mounting as ext2 it's probably ok like that. No need to rush to go through the trouble of changing it unless you start to notice problems with the rom from file errors.
[Droid Incredible General] Rom-Addict:
Can't update any apps weni switch roms any ideas? V.3. Should I start over with version 4?

Inc
[Droid Incredible General] dvdivx:
I would love this if you could just switch between Ubuntu or Meego and CM7. That would be enough for me.
[Droid Incredible General] Treken:
Thanks for making this app!! Quick question, so any time I want to change or add a rom, I would flash the createimg, then the rom, then flash the rom installer zips? Thanks again. Very valuable tool when try to test a rom and want to keep your stable rom for everyday use!!:)
[Droid Incredible General] tiny4579:
I'm not sure if flashing the createimg is needed when switching ROMs, but it won't hurt. I think the rominstaller.zip wipes the images before the install.

I believe Conap could answer that question better though.
[Droid Incredible General] rberry88:
This app is simply awesome, I never used the emmc partition for anything personal before and this makes the best use of it.

I have 4 roms on the emmc and 1 on the phone.

1. mikmik's beta 3

2. incubus's stock 2.0

3. nilsp's business sense desire

4. MIUI

phone: Uber beta 4

Yesterday when I was with friends and family, I must've booted between each one at least 3-4 times and no problems what so ever.

My only annoyance and I don't know if there is a solution:

1. SMS - I wish they were stored online like email so I didn't have to keep backing up and restoring everytime I switched roms. - on a side note: does anyone know of a sms backup app that does incremental backups/restores so I don't have to back up the whole sms history and restore the whole history each time?
[Droid Incredible General] tiny4579:
I don't know about incremental restores but I use GO SMS for SMS and it has builtin backups and it can even backup to email if you want. It does incremental backups.
[Droid Incredible General] justjayhere:
Thanks for this tip... I applied your same specs to my forth slot for the GingerSense RCMixHD Rom and it is running great with plenty of room to grow.:-)
[Droid Incredible General] tiny4579:
Any idea on a backup for this?

Couldn't I just copy the .img files onto my PC since the ROM is contained in the .img files and voila, backup? Then boot phone rom and then copy back to restore?
[Droid Incredible General] jesssiii:
I have:

ROM 1= CM7 #90 Nightly modded

ROM 2= Senseless Modded Stock 2.2

ROM 3= CM6 MODDED

Phone ROM= JagerROM

I can't get CM6 to work though. Tried two times re-adding to spot #3 but when I try using it I get bootloop. End up having to restore back to something else.

Also had to delete folder for ROM 4 due to lack of space, even though I hadn't put a Rom in it.

DInc + Zeam Launcher

Chad's Incredikernel

CM7 Nightlies
[Droid Incredible General] jesssiii:
Also noticed that the roms, at least CM7, were a bit sluggish compared to running on phone.

DInc + Zeam Launcher

Chad's Incredikernel

CM7 Nightlies
[Droid Incredible General] jtkes693:
anyone having issues using the DR app on gingersense remix B4 i used the updated rom installer zip and whenever i tried to boot up another rom it restarts into the fastboot screen then i gotta go into recovery and run the one of the boot zips to get into another rom...i can into gingersense just fine
[Droid Incredible General] asianbobo15:
Just a quote from my ROM. I haven't personally tried it, but apparently he has.

Incredible DoubleShot Espresso.

http://xdaforums.com/showthread.php?t=1039233
[Droid Incredible General] zenstitution:
Mad excited to try this out, however I'm at work and don't get much time to search thru posts. Can anyone tell me the easiest way to set up this new method from his old one?