yashsingh1/xdaforums huggingface dataset:
[Droid Incredible General] tomlang:
Conap,

Just curious (not knowing how this all works), but would it be possible for the four roms stored in emmc to use the same file that contains the user applications and data for the user applications? It would be great if we could install a blank rom and have all the applications already in place. It would save time and space.

I haven't been able to try again, but I thought the first time I installed a rom, then flashed and installed a second rom into emmc, when I went back to the first emmc rom, many of the applications were no longer there. Is this true or was I seeing things?

Thanks
[Droid Incredible General] Conap:
I have found that anything that is Sense Froyo or AOSP works pretty good. The only one's that have lag issues for me are the GB Sense ports. I haven't tested the stock GB but it might work ok since it doesn't have all the heavy sense 2.1/3.0 stuff. If your worried about lag then stay away from putting those on the emmc for now. I personally have Nil's Business sense( the froyo one) cause i've used it for a while and really like it. Then I have CM7 which I also like. I've been running the Kingdom Stock Sense 3.0 port and it's a good rom too but of course is laggy on the emmc and then I threw MIUI on there. I'm not a huge fan of MIUI myself but it's nice to have a variety available if for no other reason then to make other phone users jealous when I'm out lol....
[Droid Incredible General] Conap:
All the rom's operate independently. If you install an app on rom1 then it won't be installed to rom2,3 or 4. You can't really share that data between rom's cause different versions of android store that information differently.

Edit: Unrelated to this question but FYI to everyone I just loaded RLS2 of Kingdom Stock Gingersense 3.0 and it's a huge improvement over RLS1 even on the emmc for me at least. It's a great rom for those looking to try some of the new Sense out. It's super smooth installed to the actual phone of course.
[Droid Incredible General] pk2018:
how to normally boot from phonerom especially rom-X1234 is down

what i mean if you boot in rom1~4, u can select boot from others or phone rom

but but if you cant boot in anything or just want boot from phonerom next time

what can i do?

otherroms i have got boot-x.img can be flash from rec...

but i have not bootphone.img

that all of mine

big thanks for respon...
[Droid Incredible General] mikesincredible:
here goes nothing..... hopefully i can get this right, i suck at following instructions but even then i still surprise myself...

ok i put cm7 on rom1 slot, make a few changes, flash a new kernel..and to save those changes, I just flash the rom1upgrader and that will "remember" what i just changed??
[Droid Incredible General] Ruggerxpunk:
Sure enough I had Uber Kingdom 3D and MIUI on emmc. Both lagged severely. Wondering if I made either of those my phone ROM, then put CM7 onto emmc...
[Droid Incredible General] mikesincredible:
i seem to be having an issue, maybe its something simple but ive done everything stated in the OP...I was using uber kingdom, i flashed it as my phonerom, that booted and did everything properly I guess...so after I set that up, .i flashed createimg1..i then flashed cm7, set it up to my liking, then i flashed the rom1installer...once that is completed the phone reboots and stays literally frozen at the splash screen, i let it sit for 15 mins..still splash screen, so i tried flashing the boot-rom1.zip and still holds up at the splash screen...what am I doing wrong? i deleted everything all the EMMCS created and started from scratch and still does it.
[Droid Incredible General] Ruggerxpunk:
I found this helpful:
[Droid Incredible General] mikesincredible:
still freezes at splash....my only diff is i have cwm 3.0.7..but that shouldnt matter..its 3.x.x
[Droid Incredible General] Ruggerxpunk:
Do the rom1 first then reboot. Then do the phone Install zip last
[Droid Incredible General] mikesincredible:
i decided to flash 3.0.8 cwm, and everything is working now. Ive loaded up cm7, uber3d, and miui as my phone...thanks rugger for your help man
[Droid Incredible General] nfiniti9:
After a ton of testing, for me anyway, it seems 3.0.0.8 with Caulkins format all scripts work best. 3.0.0.7 isn't doing something write flashing some roms. Based on the code changes Koush said it only added the slcd for .8 but something has to be different.
[Droid Incredible General] mikesincredible:
no matter what I tried with 3.0.7 it would not go pass the splash screen. 3.0.8 is it from now on..I use to flash roms with this cwm before I read .7 was for amoleds...to my initial question, lets say a new kernel comes out for the 3.0 sense roms, if i wanted to add to the rom I have on slot(1), i load that slot, make whatever changes, then do I flash the rom1upgrader? or just reflash the rom1installer?
[Droid Incredible General] Conap:
sorry guys I was out of town on a bus trip and left my phone on the seat of my vehicle when i got on the bus lol....glad you got it working. I have cwm 3.0.8 but I too assumed there were no changes from the 3.0.7 besides the slcd support. Right now to flash any updates such as a kernel or flashable theme you want to flash whatever version of the rom you have in slot 1 then flash the kernel or update then flash the rom1upgrader. The only difference between the upgraders and installers is that the installer's wipe your data giving a fresh start. As far as kernel's though tiny4579 made some zip's like the any kernel updater that you can just drop your kernel and modules in and flash it without having to refash the rom and use the other zips so that will make it much easier to change kernel's....hopefully we can get them posted up soon.
[Droid Incredible General] Conap:
Yeah I never thought to make a boot.zip for the phone rom. I will try to make one up. Alternativley till then you can take any of the bootX-rom.zip and open it then open up the script you see inside it you will see a line that says :

flash_image boot emmc/romX/boot.img

just change romX to phoneRom and it will flash the phone rom's boot.img instead. Also if you have a nand of the rom you have on the phone you can just do advanced restore and choose to restore just the boot.img.
[Droid Incredible General] caleris:
I have been using the latest version of this tool. My experience is that you succeeded in removing the lag. I have four ROMs loaded, one Froyo and three GB (one being MIUI) and they all seem to be running very well. In fact the highest Quadrant score on my phone was seen tonight running the ROM in slot4.

Nice job, kudos to you.
[Droid Incredible General] mikesincredible:
thanks for the reply! luckily there are some helpful members on this site, I did figure out how the romupgrade1 and rominstallers work..i learned whatever rom is in the slot you want to upgrade, thats the rom that needs to be the one thats flashed via CWM, you cant flash to the IMG thats running, and thats where the nandroids come in because I can just load that nandroid, alter it, then flash the upgrade.... ..its cake now, i even creating a bigger slot for sense roms through ADB, but this whole process did take me a couple hrs, and reading, and stressing people out ;)...i did have to use the boot.zips a couple times..as far as lags, this is the first time using this program, its seems responsive...? i dunno, works fine for me.
[Droid Incredible General] pk2018:
its so cool and awesome that i like it very much......

My question now is:

How can i force boot from phone while needn't reflash or resintall or restore my rom with many apps used before?

thanks for response!!!
[Droid Incredible General] pk2018:
sorry for read floor#251 after send my question

and i'll try what you said " choose to restore just the boot.img

thanks for reply ! Conap ... its a great job DRX2 for diyer around the world

and wishes for your boot.img go on......

NICE DINNER......
[Droid Incredible General] hyrific:
So all works normal for me except when I want to boot to the phone rom it just boots to rom 1? I can't boot back to the phone unless I install a new rom or do a nandroid backup.

Anybody else having this problem?
[Droid Incredible General] pk2018:
actully i'm puzzle about how can i free boot from 5roms anywhere

" I can't boot back to the phone unless I install a new rom or do a nandroid backup."

simulally mine, after update to v5 and v6

i am confused
[Droid Incredible General] trickster2369:
Easy question of the day:

Can I restore a nand and then flash installer? Or do I have to start from a new ROM flash? Or both?
[Droid Incredible General] tomlang:
Conap, thanks again. this is the greatest thing since sliced bread.

would it be possible to create a means of directly flashing a .zip rom file into one of your emmc images instead of first needing to flash it into the phone?
[Droid Incredible General] Conap:
After you flash or restore the rom your going to leave on the phone you need to flash the phoneinstaller.zip so that it will make a copy of that boot.img so that you can boot back to it later.

Yes you can restore a nand then flash the installer or do a new rom flash. Either way is fine.

Possibly still working on it though.
[Droid Incredible General] tomlang:
Way cool. This is the best thing imaginable for avid rom flashers like me.

Now for an off the wall question. Since these four images along with the fifth phone image contain the current state of the phone when in use, would it be at all possible to on-the-fly switch from one to another? Near instant switching from an ASOP rom to a sense rom would be fantastic, but would it be possible?
[Droid Incredible General] caleris:
This is slicker than snot on a wet doorknob. I am using Skyraider, OMFGB, MIUI, and Inc-Deck ROMs.
[Droid Incredible General] trickster2369:
Been trying to get v6 loaded on my phone. After not having much luck, I looked into the zip files and noticed the following:

createimagerom1(2,3,4,phone) are v2

installrom1(2,3,4,) are v6

update-rom1(2,3,4) are v6

I dl'd from the op, is this right?

Everything appeared to work properly, but when I tried to flash into rom1, or 2,3,4, it said no rom installed.
[Droid Incredible General] Conap:
To do a quick boot like that the boot.img and kernel don't get reloaded which is how this switches rom's. Since alot of the kernels are specific to sense or aosp it's probably not possible but someone smarter then me might no more :)

Yes that's right...the v2 zips just didn't need updateing cause there weren't changes. Make sure you have the img's there by flashing the createimg.zip then install your rom in recovery like normal then flash the rominstaller.zip. So far this only seems to be working with CWM 3.0.8 so you might want to check your version of CWM.
[Droid Incredible General] jdog94:
so i loaded this followed directions uber kingdom on rom 1

buss ginger sense on rom 2 and miui on phone

then from miui i didnt have the app to switch roms and when i tried to install is said not enough room

so i moved miui to rom1 and uber to phone and then from uber i opened the app and choose rom 2 so i could go to gingersense and it took me to bootloader and that wha it

so where did i screw up?
[Droid Incredible General] Conap:
Well things to check would be:

1. Make sure you have CWM 3.0.8

2. Make sure the system, data, datadata, cache, and boot.img's are in emmc/romX folders and they are the right sizes.

3. Make sure you are wiping between installing the different rom's and then installing rom and running romXinstaller.zip.

It sounds like datadata.img is not being made or not being mounted correctly.
[Droid Incredible General] trickster2369:
3.0.0.8 was the answer. Thanks for the quick reply, and keep up the good work.
[Droid Incredible General] tomlang:
Conap,

Could you include a .zip file to force the phone to boot from the phone instead of an emmc rom image? I am having trouble where the phone gets stuck in recovery and won't boot from the selected rom, restarting recovery each reboot.

Thanks, Tom
[Droid Incredible General] jdog94:
well i got miui on rom 1 working great and uber kingdom on phone rom running great

i have tried niles business ginger sense on rom 2 and it would boot to white htc screen and just set there or boot to white screen and loop

any ideas?

if try to boot them from the app it goes to bootloader
[Droid Incredible General] caleris:
I wonder if the ginger sense roms are not too big for the emmc partitions as set up in Conaps zips.
[Droid Incredible General] Conap:
I added a zip to boot to phonerom with the other bootrom.zip's in op...link here too http://www.multiupload.com/FBBQJ06VP4

Did you try reinstalling it? It sounds like it did not make the boot.img correctly. The boot.img may be too big.
[Droid Incredible General] jdog94:
ive tried a couple times
[Droid Incredible General] Conap:
Is there the img's in emmc/rom2? there should be system.img data.img datadata.img cache.img and boot.img. If they are all there then I will have to try and flash it....i don't think I've tested that rom.
[Droid Incredible General] pk2018:
Conap

could you make a app boot phone first some like drx5.zip and then we can select it to boot to 1-5 rom anyone?
[Droid Incredible General] jdog94:
yes they are there
[Droid Incredible General] caleris:
Conap, just sent a contribution your way. Thanks for this tool.
[Droid Incredible General] skorpios1027:
Conap & all involved in bringing this to us,

Thank you for the great work!

I noticed that in your createimg scripts, you set the cache image size to 120MB when the phone's cache partition is roughly 190MB. I didn't use your script to create the initial img files, I did that manually, adjusting the cache.img to 200MB. I don't know if having the cache.img smaller would affect anything, but I wanted to be on the safe side and made all the .img files slightly larger than the phone's equivalent partition size.

This has been working flawlessly for me. Thanks again!
[Droid Incredible General] jdog94:
has anyone had any luck with gingersense roms?

i have tried synergy

bus gingersense

and uber kingdom

and they either just sit on the white htc screen and bootloop to the htc screen

miui works great
[Droid Incredible General] zwade01:
I've had success with Uber Kingdom (v6), but I had to make it the "phone rom," otherwise it was extremely laggy.
[Droid Incredible General] trickster2369:
I have successfully loaded newts hybrid and shift roms, and synergy. Hybrid does not like the emmc much at all, works but very laggy. Shift and Synergy both do well, but you will notice a performance loss.

This has been my experience, anyway.
[Droid Incredible General] jdog94:
well the only thing i have been able to get to boot on emmc is miui
[Droid Incredible General] tiny4579:
I think I might have found a good tweak for sd card speed.

Credit goes to Calkulin for the original script. I actually did not come up with the original idea, I just added a second speed tweak to it. Just make sure to chmod 777 after copying the attachment to /system/etc/init.d and removing the .txt

I think 179:0 is either sd or emmc and 179:8 is the other.

Feel free to tweak the read_ahead_kb value as needed but remember to save in Unix format or it will not run.
[Droid Incredible General] zwade01:
MIUI, cm7, and SkyRaider 4.0 all work on emmc for me. The only other one I've tried was Uber Kingdom which lagged, but ran fine for the phone rom.
[Droid Incredible General] Conap:
It's hard to say without looking at your stuff. If you want to send me the boot.img that get's put in emmc/romX after you run the installers and also pull the recovery log...after flashing all the zips back out to the main screen of recovery where the reboot option is and do:

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

then just send me those 2 files and I can take a look. If they are booting but are boot looping you could also send a logcat of the bootloop.

I posted instructions a while back for this tweak(I thought you had tried it lol) I may have missed something that the tweak does though. The only thing is when you are booted into an emmc rom then it's mounted on 179:8 or any of the numbers. It get's mounted as dev/block/mmcblk0p3. Also it's not really on the sdcard so that tweak script doesn't affect the emmc "internal sdcard" speeds.
[Droid Incredible General] tiny4579:
I did both so emmc and sdcard should be affected. I did see your post and tried it. I thought I would give setting read_ahead_kb for the whole device a try to see if it improves. Although the improvement I see in may be related to the filesystem tweaks such as ext2 and the noatime and nodiratime. Well, I'll test this tweak with a Sense 3.0 ROM to see if it helps.

PS. Quadrant Score 1581 (no overclocking) with the tweak and on emmc with CM7. So I am definitely happy with CM7 performance on EMMC.
[Droid Incredible General] tiny4579:
Tested on Uber Kingdom 3D and it seems to be working fine with virtually no lag after the boot settles. ~1600 Quadrant (yes I know it's not a great benchmark)
[Droid Incredible General] Conap:
cool sounds good...still unsure about the tweak though...try adb shell mount and I don't think you will see anything mounted on 179:0 or 179:8...our phones actually mount the sdcard on 179:9 and emmc on 179:0 at least on my phone but those are automounts by the vold system so maybe they just go to what's available at the time? My scripts make emmc mount on dev/block/mmcblk0p3 so it's unavailible when vold attempts to mount on 179:0....at least that's what i'm seeing from my output.

Edit: just read that post and I sure did use the word mount a million time :)
[Droid Incredible General] jdog94:
well i got miui or rom 1 and cm7 on rom 2 both working fine

now ill see if uber kingdom will work as reg phone rom (it has been fine)
[Droid Incredible General] jermaine151:
Awesome Mod Conap! Thank you! :)

I've looked through these posts and haven't seen this issue. I finally decided to try this yesterday and got MIUI on rom1, CM7.0.3 on rom2 and Optimized shift on the phone.

The problem I had was 2 out of the 3 times that I booted to the phone rom, my sdcard was unmounted. The only way to get it to work was to remove the cover and reseat the sdcard. If I didn't do that and rebooted into recovery or a different rom, the sdcard mounted fine. I ended up nandroiding back to just shift until I can figure out the cause. I wondered if it might be the pause that was added to allow emmc to be available.

Any suggestions?
[Droid Incredible General] tiny4579:
Just a theory but some gingersense has /system/app as a symlink to somewhere on data which may contribute to some lag as data is still ext3.
[Droid Incredible General] Conap:
The zip's should do anything to the rom on the phone. It stores the boot.img on the emmc but does not edit it and it installs the app but just like a regular app so that shouldn't affect the sdcard either. Not sure what the issue there could be.

You are right. I had not thought of that. Should probably just go to ext2 for all of it. I know all apps are extracted to data/data and I thought they ran from there but maybe they still pull info out of the actual apk. There is always something new to learn in android....
[Droid Incredible General] TheWhiteBandito:
Conap, I tried this with SkyRaider 4 the other night and still wouldn't get past the white screen. I was using v6 files too. What would you edit in the boot.img that's created to make it work? I'll probably give it another try tonight, but just the fact that it's failed the past 2 times is not a good sign.

Just a side note, sometime between the first and second time I tried this I even formatted my internal storage using a stock froyo rom as I read that that would maybe help, but it looks like nothing is working for me :(
[Droid Incredible General] trickster2369:
You might already know this, but CWM 3.0.0.8 is the ticket.
[Droid Incredible General] TheWhiteBandito:
Is it strictly 3.0.0.8? I'm on 3.0.0.7 which I figured would work just the same (I use it because its better for amoled screens).

Sent from my HTC Incredible
[Droid Incredible General] TheWhiteBandito:
Conap,

You need write in huge red letters that this will ONLY work with recovery 3.0.0.8! I was pulling my hair out on 3.0.0.7, and I'm sure it was many other people's problems too. But now it works flawlessly! Thank you!
[Droid Incredible General] unCoRrUpTeD:
Glad to see you're still putting out dualboot ROM's.

I'm waiting patiently for June 24th to get my hands on an Evo 3D and will have some big things for dual-booting once we get it rooted!

Oh yeah, I'll be trying to work my magic with dual booting between android and Windows 8.
[Droid Incredible General] Conap:
Sorry...Took care of that in the OP...

Cool...I'm working with someone to write an app that will install the rom's and handle all the rebooting without needing recovery right now. Hopefully it will work out for multiple devices.
[Droid Incredible General] dmeadows013:
If an update becomes available for the phone rom, can you update that?
[Droid Incredible General] caleris:
Conap, could you please show me the adb commands to make a custom set on the emmc? Thanks.
[Droid Incredible General] Conap:
Yes you can update the phone rom as normal. If you change the rom then you should reflash the phoneInstaller.zip again but if it's just an update you probably don't need to as long as the DRX2 app is still installed.

cd emmc/rom1 (or rom folder of your choice)

dd if=/dev/zero of=system.img bs=1M count=X

dd if=/dev/zero of=data.img bs=1M count=X

dd if=/dev/zero of=datadata.img bs=1M count=X

dd if=/dev/zero of=cache.img bs=1M count=X

X is the number in mb's that you want the size of the img to be. On a few rom's the dd command does not calculate the size correctly so if your img's come out really small then put busybox in front of each dd command.
[Droid Incredible General] dmeadows013:
Even if you have to wipe the data/system to update? For that would you just recommend deleting/remaking the partition? Also, does the phone/rom1/rom2/rom3/rom4 installer wipe whatever is currently installed in that slot? If not, how would one do that?
[Droid Incredible General] Conap:
Your saying you want to update the rom on the phone? You don't make any partitions for the phone rom. If you wipe system and data you will need to re run the phoneInstaller.zip to reinstall the app to the rom.
[Droid Incredible General] caleris:
Thanks, will give this a try tomorrow. I did notice when I tried this with the instructions in the OP a couple of weeks ago, that the sizes did seem really small, so I will go with the busybox in front of the dd.
[Droid Incredible General] Conap:
Yeah i should add the busybox instruction to op...thanks for pointing that out. Some rom's the dd command will make it in bytes instead of megabytes.....
[Droid Incredible General] caleris:
Yes, I think that is what happened when I tried it before.
[Droid Incredible General] mmtoman:
so the shell commands and adb work is optional? I read the OP like 10 times and couldn't clearly understand if they are only needed if wanting to make custom sizes.

Also does this affect performance in ANY way. It wouldn't be worth it for me even if it had a tiny bit of performance decrease.

Seems like a great idea and really want to try this!!! I hate having to nandroid back and forth from miui and cm7 because i love both but can never ever decide!!!!
[Droid Incredible General] mmtoman:
Another question I have is that if I want to flash a new rom to one of the EMMC slots I have to wipe my phone like I do for switching from a SENSE rom to an AOSP rom?

If this is correct should I just make a nandroid then do all the flashing and then revert to the nandroid I made?

Sorry for all the questions I'm just a bit confused on this.

Thanks a bunch
[Droid Incredible General] rpz3.14:
Would there be any way to move roms on the EMMC back to the phone? If so, I think this would be really useful to update roms like CM7 where it's really easy to flash over the old one.
[Droid Incredible General] caleris:
The ADB commands are only if you want to make partitions of a different size than the create zips do. My experience with performance is that there is no perceptible lag right now. At least for non-Sense 3.0 type ROMs.