Database Users

Eris Dual Boot ROM

I'm posting this in General as I don't have the knowledge to port this or develop a similar version for the Slide and I don't want to clutter up the Development forum.
Team ADX over in the Droid Eris forum came up with this gem; a dual boot Eclair Sense/2.2 AOSP ROM. http://forum.xda-developers.com/showthread.php?t=824072
I don't know if this can be done on our phones, but I thought it possible as you don't need to flash a custom recovery.

man this would awesome... the best of both worlds, run and "stock" ROM so we can still receive updates and still have CM.

i was actually thinking about dual boot just the other day! i dont feel like id be switching back and forth from 2 roms but itd be a great feature for those who do. unfortunately i dont think we have that much developers :/

I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started

KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.

heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App

migueltherocker said:
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.

heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
Ok that makes sense. I thought it was pointing to the partitions on the phone telling it to format to a different size for some reason. Then what's preventing us from doing this? Just a lack of a proper script?

I have not poked around with how they are going about doing everything, but I was the one who got the ball rolling with my dual boot linux script. Conap took the basic setup and made some changes to just install them both on the phone and sdcard. Here is the basic of what it is doing....
The init.rc file found in boot.img has been modified for the froyo rom on the sdcard. The lines where it mounts [email protected] , [email protected], and [email protected] have been changed to the partitions on the sdcard (/dev/block/mcblk0px) The updater-script for froyo has been modified to flash the rom to the partitions on the sdcard. There are some gscripts which are ran from the phone that either modify or replace the boot.img for the rom you want to boot into.
The froyo ROM is running completely off the sdcard and the recovery is left untouched. The script that is required if you are using clockworks is because clockworks sbin and folder locations are setup a little different. I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. I am working on something that should run from all android phones and allow you the option of installing whatever ROM you want.
One Last Thing..
Anyone is capable of learning how to do some development work. It just takes some patience and "Google". I had no knowledge of linux or any other scripting languages, except windows batch scripts, until 3 months ago.
There is not much activity on my thread, but once I get a working version finished it will be posted there-----Dual Boot Android

When you get it done and own working, post it in development. I only posted the thread in general because I knew I wasn't going to be the one to develop it. I'm a welder by trade and java and linux are a little beyond me. Although I am trying as I'm using Ubuntu as my main OS and starting reading java tutorials.
Sent from my CM6 Slide

heybobitsme said:
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
Click to expand...
Click to collapse
If there was ever a reason to get a dev started on a project, this would be it. I would reconsider upgrading from the Slide if we had something this awesome.

unCoRrUpTeD said:
I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. [/URL]
Click to expand...
Click to collapse
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.

s off is tmobs response to....
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
The "companies" wanted s-off due to the large number of brix getting returned for handest exchange and assurion claims, just to figure out somebody pooched sumthin up trying to be a HAXOR, if you haven't done anything like this before. Id suggest peeps get a g1 or some other root & rom-o-matic type for and play with it till you take on your brand new handset trying to install some bleenin edge hack...
You gotta learn to wank off before you can try it with somebody else in the room.
I remember my early days at xda, hacking my mda, xcaliber, and esato hacking SonyEricsson fones before they jumped the shark. People who had the ability to read and follow directions (emphasis on the read part) would study till they were sure they would still have a working fone at the end. Hung out and did great stuff with there handsets. And the noobs were wary enough to investigate before they just started mucking about.
So the handset manu. Had to do sumthin and now we have s-off.
the moral of my high and mighty rant an rave, if you don't know how to do sumthing or if you understand what to do but not the why, then keep reading, read more do less

KCRic said:
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
Click to expand...
Click to collapse
In the newest builds they have 2.1 system on the phones system partition and froyo system on the phones data partition. The data is moved to the SD. 2.1 and previous Rome had no problem with extra partitions on the sdcard.froyo changed the way it mounts the sdcard and could only see 4.
I am actually releasing a dual boot method very shortly that should work on any android phone with very little setup required on your part. I am in the process of finalizing it. Anyone interested in testing please let me know as I want to test on as many devices ad possible
Sent from my HERO200 using XDA App

[IDEA] Implement Firerat's Custom MTD Partition for HD2

Hi. Maybe few words about me first. I'm not a developer, I don't know how to do it and I have to ask more experienced users. Ok that's it, to the point now. Ah, and I didn't know if this thread was proper to be posted in Development sub-forum, so it's here. If it was possible, if the thread meets requirements to be there, maybe it's possible to move it there? I'm not sure how many devs visit those section, so obviously there is greater chance for finding an answer there, but again, I wasn't sure if it was right.
While I was a G1 user one genius known as "Firerat" created very nasty script - it allowed users to manually, by simply creating a .txt file on sdcard with proper values and running a .zip from recovery, resize partitions like /system, /data and /cache on the phone. I don't know if you're familiar with G1 stuff, but previous there was only one way to chage partitions and it was achieved by custom SPL called Haykuro SPL. This modification (MTD part hack) was created because of need for even more space on /data and allowed to shrink /system and /cache to smallest value possible, so /data took up as much space as it was possible. Here is source thread in G1 Development section:
http://forum.xda-developers.com/showthread.php?t=717874
There you can dive in details, because my knowledge and understanding in this things end very quickly .
On HD2, we have come a great way. From pure Windows Mobile, it was possible to run Linux kernel from sdcard by HaRET.exe, then run Android. After few month team of gods gave us MAGLDR, a tool that allows us to replace Windows Mobile from NAND with Android system. Then after few more weeks someone made Clockworkmod Recovery possible, giving us posibilty to create partitions on sdcard, do a nandroid backup/restore. But one MAJOR thing wasn't done as it should. Recovery in theory should give us possibility to flash ROMs from sdcard without need of computer. And theoretically it's possible, but... Yes, you have to have proper partition configuration flashed by DAF.exe with PC before. Imagine what a great obstacle it is for diagnosed with ORD!
Now you realise what I'm talking about? Combine these two things and bam! I'm just asking, just giving you an idea. Maybe it is possible to adapt those scripts to HD2 and replace old habits (flashing recovery by DAF.exe on PC) with simple script and one .txt file!
Again, maybe it's not possible since we are still using old SPL from WM times. Maybe MAGLDR is build in such way that those scripts are not possible. Maybe there is a thousand reasons... but I've never seen such an idea.
So please, is there one person who are good in this stuff and can explain me wether it's possible or not?
So maybe I can rest assured that I have to cure my ORD
OR
we can move on to work on making this idea reality .

cure for ORD....
I DON'T THINK SO.
Flashed from my fingers to your face

On a serious note, though, have you looked at clk? It is supposed to be useable without a pc. Therefore you can configure the partition on your phone. Is my understanding of that correct?
Maybe T-Macgnolia can explain this better than I .
I'm still trying to get my head round it, before I commit to changing over to clk...
Flashed from my fingers to your face

raven_raven said:
Hi. Maybe few words about me first. I'm not a developer, I don't know how to do it and I have to ask more experienced users. Ok that's it, to the point now. Ah, and I didn't know if this thread was proper to be posted in Development sub-forum, so it's here. If it was possible, if the thread meets requirements to be there, maybe it's possible to move it there? I'm not sure how many devs visit those section, so obviously there is greater chance for finding an answer there, but again, I wasn't sure if it was right.
While I was a G1 user one genius known as "Firerat" created very nasty script - it allowed users to manually, by simply creating a .txt file on sdcard with proper values and running a .zip from recovery, resize partitions like /system, /data and /cache on the phone. I don't know if you're familiar with G1 stuff, but previous there was only one way to chage partitions and it was achieved by custom SPL called Haykuro SPL. This modification (MTD part hack) was created because of need for even more space on /data and allowed to shrink /system and /cache to smallest value possible, so /data took up as much space as it was possible. Here is source thread in G1 Development section:
http://forum.xda-developers.com/showthread.php?t=717874
There you can dive in details, because my knowledge and understanding in this things end very quickly .
On HD2, we have come a great way. From pure Windows Mobile, it was possible to run Linux kernel from sdcard by HaRET.exe, then run Android. After few month team of gods gave us MAGLDR, a tool that allows us to replace Windows Mobile from NAND with Android system. Then after few more weeks someone made Clockworkmod Recovery possible, giving us posibilty to create partitions on sdcard, do a nandroid backup/restore. But one MAJOR thing wasn't done as it should. Recovery in theory should give us possibility to flash ROMs from sdcard without need of computer. And theoretically it's possible, but... Yes, you have to have proper partition configuration flashed by DAF.exe with PC before. Imagine what a great obstacle it is for diagnosed with ORD!
Now you realise what I'm talking about? Combine these two things and bam! I'm just asking, just giving you an idea. Maybe it is possible to adapt those scripts to HD2 and replace old habits (flashing recovery by DAF.exe on PC) with simple script and one .txt file!
Again, maybe it's not possible since we are still using old SPL from WM times. Maybe MAGLDR is build in such way that those scripts are not possible. Maybe there is a thousand reasons... but I've never seen such an idea.
So please, is there one person who are good in this stuff and can explain me wether it's possible or not?
So maybe I can rest assured that I have to cure my ORD
OR
we can move on to work on making this idea reality .
Click to expand...
Click to collapse
Hello raven_raven,
This is indeed a good idea and can make our HD2 PC independable. I will support you as much I can.
Though I have some questions for you.
Q1: Is it possible for this script to brick our device?
Q2: Can we choose the partitions which we resize (for example I would like to resize only /system, /userdata and /cache and leave the others as is) and if yes the other partitions /boot, /recovery will be formated or data will be kept as is?
Q3: What the bootloader has to do with it?
Q4: What SPL has to do with it?
For your knowledge in HD2 their are 2 bootloaders, MAGLDR and cLK (cedesmith's Little Kernel) which makes HD2 a native android device.
In MAGLDR partitions are made along with the flashing of CWM with the help of DAF.exe
In cLK partitions are directly managed by the bootloader when flashed.

malybru said:
On a serious note, though, have you looked at clk? It is supposed to be useable without a pc. Therefore you can configure the partition on your phone. Is my understanding of that correct?
Maybe T-Macgnolia can explain this better than I .
I'm still trying to get my head round it, before I commit to changing over to clk...
Flashed from my fingers to your face
Click to expand...
Click to collapse
Tried cLK, but it can't change partitions as you would like it to, you can't change it on the go without PC.
zach.antre said:
Hello raven_raven,
This is indeed a good idea and can make our HD2 PC independable. I will support you as much I can.
Though I have some questions for you.
Q1: Is it possible for this script to brick our device?
Q2: Can we choose the partitions which we resize (for example I would like to resize only /system, /userdata and /cache and leave the others as is) and if yes the other partitions /boot, /recovery will be formated or data will be kept as is?
Q3: What the bootloader has to do with it?
Q4: What SPL has to do with it?
For your knowledge in HD2 their are 2 bootloaders, MAGLDR and cLK (cedesmith's Little Kernel) which makes HD2 a native android device.
In MAGLDR partitions are made along with the flashing of CWM with the help of DAF.exe
In cLK partitions are directly managed by the bootloader when flashed.
Click to expand...
Click to collapse
A1: No, it is not possible. Firerat is genius and he does masterpiece of scripting, those scripts are 100% safe. It will of course break you ROM, but simple nandroid backup/flashing a new ROM will fix it.
A2: We resize /system, /data and /cache. You simply put two values in text files, i.e.:
Code:
mtd 130 2
First number is how many mb you want to spend on /system, second on /cache. Rest of internal memory is used by /data. /boot and /recovery are not touched by this script.
A3: I don't know for sure, just connected it to Haykuro SPL, which also changed partitions back then.
A4: Don't know for sure, I'm simply intermediate in this stuff, just wanted to pass an idea, I don't have required knowledge and experience to make this idea come true.
I know that there are 2 bootloaders, but I don't know how they work and how far you can modify partitions from recovery by using each of them. HD2 obviously isn't a native Android phone and regarding that either this idea may be impossible to implement or has to be completely redesigned. I really don't know .
Just wanted to pass an idea, but I'm terribly dissapointed how little response I received...

Well you would have more people responsed if you were posting in development forum under the label [call for development].
cLK is modified "little kernel" for HD2...
since there is no danger of bricking our device I am going to test it and report.
Sent from my Nexus One using XDA App

zach.antre said:
Well you would have more people responsed if you were posting in development forum under the label [call for development].
cLK is modified "little kernel" for HD2...
since there is no danger of bricking our device I am going to test it and report.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Great thing to see that someone tries. Be warned though, I'm not responsible for any data loss and damages or whatever, as always . Please be sure that you read original thread and understood how this script is working.
Maybe I'll ask a mod to move this thread to Development section...

raven_raven said:
Great thing to see that someone tries. Be warned though, I'm not responsible for any data loss and damages or whatever, as always . Please be sure that you read original thread and understood how this script is working.
Maybe I'll ask a mod to move this thread to Development section...
Click to expand...
Click to collapse
Yeah i did, don't worry about it.
I have read the original thread, i have compared the different devices mount points (as much i could) and conclude that is the same.
What i have also noticed is that kernel must be patch in order for this script to work and the script checks for a specific bootloader? I'm not sure, i need to restudy that thread.
Anyway, I tried using the script but didn't happen anything.
I formated all partitions except /boot and /recovery
I first created the mtdpartmap.txt in SD root and flashed via CWM the script FR-recovery-v1.5.8-CustomMTD_S.zip
Then reboot and again to recovery
Flashed ROM and then flashed FR-boot-v1.5.8-CustomMTD_S.zip
Reboot to ROM worked fine.
I run terminal
#df
Sizes where the same as before

Exactly, first you apply new partition map to recovery, next you install ROM in those new partitions either by flashing or nandroid backup-ing, then patch kernel to work with this new layout.
Huh, it would be too easy to simply run it and bam! it works. Even Firerat made different scripts for different devices. I'm curious what's the problem. Is recovery on a different level than those in native Android devices, which means that it can't change partition size? Or is it just problem of adjusting script to HD2 like it was done for Hero or Evo? I wonder if Firerat would like to investigate, but it would be impossible to achieve it without HD2, and from what I know he does not have one.
What person should I ask to move my thread to another section?

raven_raven said:
Exactly, first you apply new partition map to recovery, next you install ROM in those new partitions either by flashing or nandroid backup-ing, then patch kernel to work with this new layout.
Huh, it would be too easy to simply run it and bam! it works. Even Firerat made different scripts for different devices. I'm curious what's the problem. Is recovery on a different level than those in native Android devices, which means that it can't change partition size? Or is it just problem of adjusting script to HD2 like it was done for Hero or Evo? I wonder if Firerat would like to investigate, but it would be impossible to achieve it without HD2, and from what I know he does not have one.
What person should I ask to move my thread to another section?
Click to expand...
Click to collapse
Well, I guess Firerat need to come by and post a thread in HD2 Dev forum since it is his work.
He could ask what info he needs for the HD2 such as partition layout and filesystem in each partition etc... I am sure many people are willing to help with that.
I also think that SPL is locking the partition tables (not sure) and the way we are flashing just overcome that. Else when i used the script should have f**cked up my partitioning.
You can ask an HD2 moderator to move this thread but first ask for Firerat permission.

[Dev] Desire HD Dual Boot

Why isn't there any Dual Boot Development on the Forum?
It would be great to run 2 ROMs, and it would be very useful for Developers.
Because you can run a Stable ROM and at the same time a beta test ROM without
wiping you Device again and again and make any Nandroid backup..
It's already possible on the HTC Droid Eris
The best option would be to run a ROM from your SD Card, is this an option?
And how difficult, do you guys think, is it to create a Dual Boot option during startup/recovery?
Check also this project, major update coming soon!
unCoRrUpTeD Dual Boot V1 (RELEASE DATE: TBA...)
http://forum.xda-developers.com/showthread.php?t=847423
[RECOVERY-BETA] Eris Multiboot recovery hack
http://forum.xda-developers.com/showthread.php?t=779274
This hack will boot a rom from SDCard. It expects to see system.img and data.img on the sdcard as well as init.rc.
System.img needs to be a disk image of a filesystem that the kernel can read(I've been using ext3) around 170MB(Thats the Eris's NAND size for system)
data.img needs to be a disk image of a filesystem that the kernel can read(I've been using ext3) as big as you'd like your data partition to be(This holds your apps etc, so a couple hundred megs is good)
init.rc needs to be the init.rc of your rom with two changes
You need to remove the lines where it mounts /system and /data.
Once you have those three files on your sdcard, and have flashed this recovery you're ready to try your first boot.
Reboot into recovery, you'll see the normal usual recovery menu(I'll add an item eventually)
connect to the recovery console with adb
run 'adb shell /bootfromsd'
It will APPEAR to have done nothing for a bit, this is normal. Its booting your rom now. Once it gets to the place in the rom where it would display the splash screen, you'll get a splash as usual. You can watch it with logcat if you like.
I've personally booted the following roms from SD.
KaosFroyo
KaosLegendary
CELBFroyo
MR4
PlainJane
Click to expand...
Click to collapse
Kendon at the VillainROM forums
i have managed to have two different android flashes on the hero, tested using VillainROM5.5.0 and SlideVillain1.1.0. it is designed to work with every rom you throw at it. it uses the /system partition for the first rom, the /data partition for the second rom, and two ext partitions for the userdata of each rom. apps2sd support is completely removed during the process, it is obvious that two roms using the same apps2sd partition would create a mess. the process is completely reversible (except for the wiping, so backup!). i have written a bash script that does the necessary steps for you, which are:
- modify the boot.imgs of the roms
- partition your sdcard
- flash the roms
- move the second rom to the /data partition
- move the two roms’ userdata to the sdcard’s ext partitions
Click to expand...
Click to collapse

love to see that

patiently waiting for this feature. keep it posting

I was just looking for something like this. Going to be keeping an eye out on the top Post to see if anything comes. Although i imagine it'll be a while before we see anything final !

alguna informacion adicional sobre este tema, gracias.
Mod edit: any additional information about this topic...thanks!

+1 woulod save time for flashmaniacs like myself

This would be great for testing purposes. I would definitely beta test this if needed.

Aye, I hope someone figures this out
Sent from my Desire HD using XDA App

Quote from iOO
[ROM] REAL SENSE - i00 ROM 5.2 - UPDATED 16/05/2011 - Android:2.3.3
THE FIRST "SYSTEM PARTITION" TRUE SENSE 3.0 ROM!
So what does this all mean?
System partition - this means that i00 ROM does not install any ROM component on your data partition; this has two advantages: it saves precious space on your data partition - so you can maximize the amount of apps you can have installed, and it allows you to factory reset the phone without having to re-install the ROM!
Click to expand...
Click to collapse
Does this mean that you can also Flash a ROM to your Data partition? This means you should only have an option in recovery to choose which ROM you want to start?!?!?!

avisador said:
alguna informacion adicional sobre este tema, gracias.
Click to expand...
Click to collapse
Please use the English language, as stated in the xda posting rules.

Thekn said:
Quote from iOO
[ROM] REAL SENSE - i00 ROM 5.2 - UPDATED 16/05/2011 - Android:2.3.3
Does this mean that you can also Flash a ROM to your Data partition? This means you should only have an option in recovery to choose which ROM you want to start?!?!?!
Click to expand...
Click to collapse
i00 answer
It is possible to dual boot android phones (some at least) with two different versions of android... not sure about doing it on the DHD...
The advantages from flashing this are as stated: to save space on the data/"internal memory" for more applications, and so you can factory reset and have your phone still work without having to re-flash the ROM.
Click to expand...
Click to collapse

Thekn said:
i00 answer
Click to expand...
Click to collapse
By "this" in my quote (in the post above) i mean "my ROM" ... just to avoid confusion...
Kris

i00 said:
By "this" in my quote (in the post above) i mean "my ROM" ... just to avoid confusion...
Click to expand...
Click to collapse
Sorry! Thanks for the explanation! Do you think you can make a Dual Boot for DHD?

Also check this out...
Kris

Also ... it isn't a user friendly process...
From what i gather:
Has only been done on the hero .. and basically involves flashing a ROM then editing another ROM to flash "purely" to the data partition...
create two update packages that each contain a mod'ed boot.img file
... one boot.img points to boot from system partition ... and one points to data partition
... then u have to flash the update file with the corresponding boot.img each time u want 2 change os'es
... only issue would be if you have, for example, sense 2.1 and sense 3.0... the /data/data/? for rosie (etc) (that holds your settings for the apk) conflict between 2.1 and 3.0... and thus would cause issues when switching between the ROMs (FC's in this case hence why you cannot upgrade to 5.0 from previous versions of my ROM).
Kris

i00 said:
Also check this out...
Kris
Click to expand...
Click to collapse
yeah i already found that link, but the link is broken and also the site is blank, couldn't find another source..

Also check this out if you are interested in editing the boot image...
Doesn't seem worth it though to me ... exp if you dont have a way to quickly jump between one OS and the other
Kris

Maybe Ubuntu
Maybe not another android rom but a real linux distro?

humbi83 said:
Maybe not another android rom but a real linux distro?
Click to expand...
Click to collapse
That's also a possibility!

i'm actually more interested in running winmo7 on my phone for a change

DualRomX2 = 4 roms on emmc(V6) 6-9-11

For those with phones other then Incredible...The new app that will replace this system and work with multiple phones is in the market. Check out my sig for our website with more info.
Does not work with CWM2.5...Tested with CWM 3.0.8 ONLY WILL NOT WORK WITH OTHER RECOVERIES
A super big thanks to xda dev drellisdee since he's the one who showed me how to mount the img's at boot time. Check out his modified recovery here http://forum.xda-developers.com/showthread.php?t=758874
Thanks also too:
Team ADX-I used my personal account to post since it has the dev privaliges but consider this a Team ADX endeavor.
Thanks to DHowett for furthering the idea of what we can do with the dualbooting
Thanks to UnCorrupted for giving me the original interest in Dual Booting roms long, long ago!!
Thanks to VZW for taking so much of my paycheck everymonth!!
Thanks to all who tested and gave feedback on my original DualRom project and to all who will do the same with this one.
Thanks to all the Dev's that give us a reason to want to use more then 1 rom.
DRX2 is an upgrade from DualRom. You can fit up to 4 roms on emmc(and one on the phone if you want) It uses the phone as an installer. I decided to go towards DHowetts idea of mounting img files on the emmc. Emmc will stay as fat32 the way it comes on the phone. This system is fairly simple and so far has worked with all rom's tested.
Tested with:
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
Post what rom's you boot successfully so they can be added to the list!!!
As you can see that's a good variety and it should work with every rom.
Does not work with CWM2.5...Tested with CWM 3+ Might work with other recoveries.
Installation
Installation is simple. The roms will be stored on emmc in folders labeled rom1, rom2, rom3 and rom4. each folder will need a system.img, data.img and cache.img. You can flash createimageforrom1.zip to setup the folder and img's for rom1 and the the same for the other roms up to rom4. The zip's i included create a 270mb system.img, a 1000mb data.img and a 120mb cache.img. If you would rather manually create these and make your own sizes do:
adb shell
cd emmc
mkdir rom1 (or rom2, rom3, rom4)
cd rom1
dd if=/dev/zero of=system.img bs=1M count=270
dd if=/dev/zero of=data.img bs=1M count=1000
dd if=/dev/zero of=cache.img bs=1M count=120
NOTE: Some rom's the dd command acts differently and your img may come out really small. If that's the case just add busybox to the beginning of the dd command.
the last number on the last three commands is the size of the image it will make. These take a while to make. If you use the zips i included expect to wait at least ten minutes for the img's to be built. Once they are built on the emmc you can flash different rom's to them without deleting/recreating them so you should only need to do this step once.
Once you have the img's setup choose your rom and your kernel or any other ad on's that you want installed. Flash the rom as normal(wipe phone, install zip from sd) NOTE: this will obviously overwrite your existing installation so if you want to keep that you will need to make a nand to restore when you are done. Next flash any ad on's or kernel zips you want installed as normal. Then just flash the zip for rom1installer that i've included. You can use rom1installer or rom2installer, etc to pick which slot you want the rom installed to. They don't have to be installed in any order. You can use just rom4 if you want just make sure you have setup the img's for the rominstaller zip you use. The installer zip will take 5 to 8 minutes to install so be patient. After that reboot your phone and it will boot to the rom you just installed. You can then use the DRX2 app to boot between all installed roms. If you restore your nand to your phone or install another rom to the actuall phone then run the phoneinstaller.zip to set that rom up to use the DRX2 app as well. So to recap and make it simple:
Does not work with CWM2.5...Tested with CWM 3+ Might work with other recoveries.
1. flash createimageforrom1.zip(or rom2, rom3, rom4) or all of them if you want lots of roms(you only need to do this if the img's are not already on your emmc)
2. flash your rom of choice and any add on's you want. (rember to wipe phone first and backup if nescasary) If you want to move the rom your currently have installed on your phone to one of the rom slots on emmc just skip this step.
3. flash rom1installer.zip (or rom2, rom3, rom4) whichever slot you want it installed too.
4. reboot
5. If you are also going to use a rom on your phone normally then flash or restore a nand of the rom you are keeping on phone. Then flash phoneInstaller.zip. This will install the DRX2 app and copy your phone rom's boot.img to emmc so the app can access it when you want to boot back to the phone rom.
Upgrading roms
rom1upgrader.zip(and rom2,rom3,rom4) can be used to upgrade your rom on emmc. These haven't been well tested. I did test with miui and a GB Sense 2.1/3.0 rom. Using these would be considered doing a no wipe update. If you want to wipe use the rom1installer.zip's. Step are as follows:
1. Wipe phone flash update and any add-on's
2. flash rom1upgrader.zip(or rom2,rom3,rom4) Make sure you flash the one where the rom your upgrading is installed
3. Reboot.
These could also be used if you want to flash add-ons. Flash the rom you currently have installed, flash the add-on, then flash the rom1upgrader. Example:
I have cm7 nightly 90 on slot1
I wipe phone, flash cm7 nightly 90 to phone, flash any add-on's i had flashed previously, flash any new add-on's, flash rom1upgrader.zip
Note: There is definitely a possiblity of typo's in one of the many scripts i had to write for this stuff so if you do have a problem that you post about please post which slot you have the rom installed too. Thanks.
DRX2 app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DRX2 works similar to DRSettings app. Push the button of the rom you want to boot too!!! simple enough right? Push menu for options to set the names of the rom's you have installed. If you set a name for Rom1 while booted in Rom1 the name will show when you boot to rom2, 3, or 4 so you only have to set the names once. There is also an option under menu to mount or umount emmc to pc. I added this because the one downfall of this system is the emmc does not mount to pc when using the mount disk drive options normally. Remember don't delete or move the img's of the rom your booted too.
Additional Scripts
bootRom1.zip, bootRom2.zip, etc...these zips are for the off chance you get stuck in recovery(i.e boot.img did not flash correctly) This shouldn't happen but I like to be safe especially if your not near a pc to fix it. You can flash these zip to boot into any of the 4 roms you have installed from recovery. Of course they will only work if you have a rom installed in the slot you are trying to boot too.
Downloads
Disclaimer-FLASH AT YOUR OWN RISK. You are responsible for what you do to your phone.
All the files you need are in 1 small package!!
V2 Changelog
DRX2 app installed to data/app instead of system/app so that GB sense rom's install it
V3 Changelog
Fixed app's not installing that i broke in v2
V4 Changelog
Fix for AOSP rom's not mounting as ext3(They should work ok as ext2 so if you already have it installed I wouldn't rush to change it. If you start to experience any data corruption then you can update those roms. These won't really affect the sense based rom's as they were already mounting as ext3.)
MultirominstallersV4.zip --old
V5 Changelog
Added a 5 second sleep on boot to give time for phone to mount the partition.
MultiromInstallersV5.zip --old
V6 Changelog
Added upgrader's in with the main package
Switched to ext2 for system.img and added ext2 datadata.img for lag improvements
Note: V6 Requires you to reflash the createimgforrom.zips because of the changes in the setup of the img's.
MultiromV6.zips --latest
Zip's to switch rom's in recovery--Now inclueds boot phone rom zip(I.E. boot-rom1.zip)
AnyKernelUpdater.zip's for DRX2 courtesy of tiny4579
tiny4579 made up some nice zips to replace the kernel on the emmc rom's. You don't even need to be booted into the rom you want to update the kernel on. Take the zImage from kernel/zImage and the files from system/libs/ in the kernel.zip that you downloaded and drop them in the same folders in these zips. These directions probably suck so if I confused you just ask!!!!
Rom1KernelUpdater
Rom2KernelUpdater
Rom3KernelUpdater
Rom4KernelUpdater
Nothing better then user contributions to a project like this so if you come up with something you'd like to share let me know!!!
Upgraders
Upgrader's now bundled in with the main package
Note: Unzip the multirom.zips to get to the flashable zips.
Does not work with CWM2.5...Tested with CWM 3+ Might work with other recoveries.
UnInstalling DRX2
If you want to install a new rom to a slot already in use then just follow the instructions I gave above. The scripts will wipe the img files at install.
If you want to completely uninstall the system just delete the folders off your emmc storage!!
Make sure your booted into a rom installed normally on the phone first!!
Additional thoughts
If the rom does not boot try installing and booting it on the regular phone first.
Any time your copying data from one place to another corruption can occur. If it doesn't work try it a second time. If you have to try again make sure to wipe the phone and reinstall the rom before re-running the installer scripts.
Install all add-on's, new kernels, flashable themes before running the installer script.
You can run the rom on the phone as normal, set it up, try it out and then move it to the emmc slots at any time by running an installer script. It will copy your data over also. In the case that you might want to check the rom out or see how a flashable them looks before installing it to one of the emmc slots.
If you have questions feel free to ask.

Nice Work im going to try it out

This looks awesome..... ! Now can keep up with all of JoelZ9614's Rom's... lol

has this been tested with sense 3.0 because it seems like .img's are too small

justjayhere said:
This looks awesome..... ! Now can keep up with all of JoelZ9614's Rom's... lol
Click to expand...
Click to collapse
lmao i bet i will have more than 4 roms

werdna87 said:
has this been tested with sense 3.0 because it seems like .img's are too small
Click to expand...
Click to collapse
I tested with gingersense remix which is sense2.1/3.0 i believe. The system.img i put was 270mb's which is larger then what's on the phone so if it fit's on the phone it will fit on this. That being said you can make the img's whatever size you want but the current install process requires that they be installed to the phone first so you will still have that size restriction.
Edit: If someone wanted to make a rom that was bigger then the phones normal partitions they could just package it in the img and just drop it onto the emmc. If any dev's have a rom that's too large for the phone and want to go that route they can contact me and I can help them make the boot.img for it. My goal was just to make install as universal and simple as possible.

Conap said:
I tested with gingersense remix which is sense2.1/3.0 i believe. The system.img i put was 270mb's which is larger then what's on the phone so if it fit's on the phone it will fit on this. That being said you can make the img's whatever size you want but the current install process requires that they be installed to the phone first so you will still have that size restriction.
Edit: If someone wanted to make a rom that was bigger then the phones normal partitions they could just package it in the img and just drop it onto the emmc. If any dev's have a rom that's too large for the phone and want to go that route they can contact me and I can help them make the boot.img for it. My goal was just to make install as universal and simple as possible.
Click to expand...
Click to collapse
ill definitely be pming you

JoelZ9614 said:
lmao i bet i will have more than 4 roms
Click to expand...
Click to collapse
I'm sure you will!
Sent from my Incredible using XDA Premium App

Fine job sir, fine job!

So does this still essentially use up all the EMMC so it's not usable for anything else? or does it only use up what it needs?

Coupled of questions.. sorry if I missed the answers to these questions:
*Does this erase the EMMC, or just adds the necessary "slots"?
*Does this erase your current Rom.. just trying to wrap my head around this...

todd3835 said:
So does this still essentially use up all the EMMC so it's not usable for anything else? or does it only use up what it needs?
Click to expand...
Click to collapse
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.
justjayhere said:
Coupled of questions.. sorry if I missed the answers to these questions:
*Does this erase the EMMC, or just adds the necessary "slots"?
*Does this erase your current Rom.. just trying to wrap my head around this...
Click to expand...
Click to collapse
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.

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?

Conap said:
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.
Click to expand...
Click to collapse
Ok, so how much space does each "slot" take, just out of curiosity?
Conap said:
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.
Click to expand...
Click to collapse
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 =]

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?

justjayhere said:
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?
Click to expand...
Click to collapse
Right now flash all your mods before moving the rom...i'll work on some way to flash it after it's moved.
todd3835 said:
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 =]
Click to expand...
Click to collapse
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.
Pithism said:
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?
Click to expand...
Click to collapse
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.

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.
Sent from my SmartQ V7 using XDA App

Conap said:
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.
Click to expand...
Click to collapse
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?

Conap, sick work
You've been busy since I first met you
Sent from my Transformer TF101 using XDA Premium App

justjayhere said:
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.
Sent from my SmartQ V7 using XDA App
Click to expand...
Click to collapse
That's only need for the rom left on the phone
Pithism said:
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?
Click to expand...
Click to collapse
CWM recovery is fine...it's what I tested with...

HD2 Partitions Limited?

I have a TMO1024 HD2, and when creating partitions, if I create a System partition greater than 447M, I get an error message (from CWR or from CWR via MAGLDR) that the partition is too large.
I would like to create a larger System partition, and was wondering whether there is a known way around this cap? A TMO HD2 has one-gig ROM storage, much of which is being wasted.
T-Mobile HD2: 576MB RAM, 1GB ROM
HTC HD2: 448MB RAM, 512MB ROM​

MarkAtHome said:
I have a TMO1024 HD2, and when creating partitions, if I create a System partition greater than 447M, I get an error message (from CWR or from CWR via MAGLDR) that the partition is too large.
I would like to create a larger System partition, and was wondering whether there is a known way around this cap? A TMO HD2 has one-gig ROM storage, much of which is being wasted.
T-Mobile HD2: 576MB RAM, 1GB ROM
HTC HD2: 448MB RAM, 512MB ROM​
Click to expand...
Click to collapse
never seen anyone do it. try with black clk. if the built in resizing doesn't work, then it's not possible

MarkAtHome said:
I have a TMO1024 HD2, and when creating partitions, if I create a System partition greater than 447M, I get an error message (from CWR or from CWR via MAGLDR) that the partition is too large.
I would like to create a larger System partition, and was wondering whether there is a known way around this cap? A TMO HD2 has one-gig ROM storage, much of which is being wasted.
T-Mobile HD2: 576MB RAM, 1GB ROM
HTC HD2: 448MB RAM, 512MB ROM​
Click to expand...
Click to collapse
im trying a 475 system partition with blk clk now..will let you know what happens
i got it to work with blk clk and touch recovery from this thread http://forum.xda-developers.com/showthread.php?t=1419733
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Kameirus said:
im trying a 475 system partition with blk clk now..will let you know what happens
Click to expand...
Click to collapse
Hi stranger! Glad to see you alive and kicking.
FWIW, I do not think that clk is relevent, but I would reconsider if it could create a 600M+ System partition...

MarkAtHome said:
Hi stranger! Glad to see you alive and kicking.
FWIW, I do not think that clk is relevent, but I would reconsider if it could create a 600M+ System partition...
Click to expand...
Click to collapse
im sick as a dog but hanging in there thank you for asking..hope you are well also
and ok ive tried with 475 and as you can see in the pic i posted in my previous post
so i will see how high i can make it and let you know
edit ..i tried 600 and 575 and the phone booted up just fine
....

Kameirus said:
im sick as a dog but hanging in there thank you for asking..hope you are well also
and ok ive tried with 475 and as you can see in the pic i posted in my previous post
so i will see how high i can make it and let you know
edit ..i tried 600 and 575 and the phone booted up just fine
....
Click to expand...
Click to collapse
I am sorry to hear that you are not feeling well. I hope that it is short-lived and wish you my best.
As for my issue, and to clarify, did you create the system partition with recovery or clk, and where is it located?
For me, System needs to be located in NAND, making use of as much of the 1G storage ROM available on the TMO1024 HD2. I use DataOnExt with all apps on Ext4, along with their dalvik counterparts. My signature indicates my current configuration.

MarkAtHome said:
I am sorry to hear that you are not feeling well. I hope that it is short-lived and wish you my best.
As for my issue, and to clarify, did you create the system partition with recovery or clk, and where is it located?
For me, System needs to be located in NAND, making use of as much of the 1G storage ROM available on the TMO1024 HD2. I use DataOnExt with all apps on Ext4, along with their dalvik counterparts. My signature indicates my current configuration.
Click to expand...
Click to collapse
thank you Mark
make a backup first then
i made them with clk ..when you boot into clk ..click on settings then click on resize partitions then click on system and adjust it to the size you
want then use the back key to go back one time then go to commit changes ..once thats done go back to the clk main menu and chose recovery and it will boot back into recovery and then you can install your backup
i actually use a 450 system part and have a 4gig ext4 part

Kameirus said:
thank you Mark
make a backup first then
i made them with clk ..when you boot into clk ..click on settings then click on resize partitions then click on system and adjust it to the size you
want then use the back key to go back one time then go to commit changes ..once thats done go back to the clk main menu and chose recovery and it will boot back into recovery and then you can install your backup
i actually use a 450 system part and have a 4gig ext4 part
Click to expand...
Click to collapse
Doing backups and restores are not as simple a task for me as it might be for you and others -- I have over 1150 installed apps at any one time (for evaluation purposes) and have high confidence in MAGLDR/RMNet/TWRP, so I would be hard-pressed to do so solely on a let's see if it works test.

MarkAtHome said:
Doing backups and restores are not as simple a task for me as it might be for you and others -- I have over 1150 installed apps at any one time (for evaluation purposes) and have high confidence in MAGLDR/RMNet/TWRP, so I would be hard-pressed to do so solely on a let's see if it works test.
Click to expand...
Click to collapse
ahh ok id be glad to test it longer for you if ya want me to since i have 2 hd2s

Kameirus said:
ahh ok id be glad to test it longer for you if ya want me to since i have 2 hd2s
Click to expand...
Click to collapse
Kameirus -- I think this has diverged a bit, based, in part, due to my lack of providing sufficient information. I am sorry for that.
Gilbert brought up clk and off we went.
I was not, at that time, considering a move from MAGLDR to CLK. RMNet is the default for Android, it may or may not be more stable, and PPP may or may not be faster. I do not know if this will ever be resolved universally, but for now, my preference is to keep with Android's default, and put the extra ROM storage wish on my back burner.
I do not want to give you any more work than you already give yourself in your community work, Kameirus. Thank you for that, but do not waste any more time on this. Others have a greater need for your skills than I do. Know that I appreciate you efforts.

MarkAtHome said:
Kameirus -- I think this has diverged a bit, based, in part, due to my lack of providing sufficient information. I am sorry for that.
Gilbert brought up clk and off we went.
I was not, at that time, considering a move from MAGLDR to CLK. RMNet is the default for Android, it may or may not be more stable, and PPP may or may not be faster. I do not know if this will ever be resolved universally, but for now, my preference is to keep with Android's default, and put the extra ROM storage wish on my back burner.
I do not want to give you any more work than you already give yourself in your community work, Kameirus. Thank you for that, but do not waste any more time on this. Others have a greater need for your skills than I do. Know that I appreciate you efforts.
Click to expand...
Click to collapse
its ok we have actually put some of the new stuff on the back burner ..1 pixel doesnt have much time now with work and his new baby on the way and 2 we are waiting to here when i have to go in for back surgery
so it would be no problem at all for me to that for
and thank you for the kind words
and the biggest reason now you have got me interested to see how far we can take this
i will gladly do this and do it with the version of twrp you are using and the rom you are using
as for the ppp i must be one of the ones that has never had any issues with it
and just maybe we can make a breakthru on something who knows lol
i hope you have a great weekend

Kameirus said:
we are waiting to here when i have to go in for back surgery
Click to expand...
Click to collapse
What did you do to your back? Sheesh! I can commiserate a bit having a couple of bulging discs (lower back), and have Rheumatoid Arthritis throughout my body (sometimes feet, fingers, shoulders, etc. -- it moves about). It was caught very early on, so all is maintained with weekly shots and daily pills. Good times when it hibernates for awhile... :fingers-crossed:

MarkAtHome said:
What did you do to your back? Sheesh! I can commiserate a bit having a couple of bulging discs (lower back), and have Rheumatoid Arthritis throughout my body (sometimes feet, fingers, shoulders, etc. -- it moves about). It was caught very early on, so all is maintained with weekly shots and daily pills. Good times when it hibernates for awhile... :fingers-crossed:
Click to expand...
Click to collapse
my L5 disc deteriorated and i have a herniated one towards the top of my spine
they tried doing the epidurel but it didnt work at all , so its on to surgery for that
and i have nerve damage on the left side of my face as well as nerve damage in both feet
and my neurologist also wants to do a procedure on my face to see if they can repair it
or not
i had no problems till i moved to Ma. i tell my friends that Ma is trying to snuff me out lol
they wont even give me pain meds the bleeps lol
i hope your issues are controlled now and cant wait till mine are fixed

MarkAtHome said:
Doing backups and restores are not as simple a task for me as it might be for you and others -- I have over 1150 installed apps at any one time (for evaluation purposes) and have high confidence in MAGLDR/RMNet/TWRP, so I would be hard-pressed to do so solely on a let's see if it works test.
Click to expand...
Click to collapse
I'm pretty new to all things Android and I have immersed myself in it these past few weeks as I have bought a 64Gb (59GB) Ultra SDXC with the sole intent of expanding the internal memory on the HD2. I've been experimenting with different ROMs and I'm currently sporting NRGZ28's EnergyROM with System and Boot on NAND and the card is set up with 43GB FAT32 and 16GB EXT4 and Data on EXT. Creating an EXT4 partition and installing the ROM to Data on EXT; that does extend the internal memory by installing apps on EXT4; yes?

re
MarkAtHome said:
I have a TMO1024 HD2, and when creating partitions, if I create a System partition greater than 447M, I get an error message (from CWR or from CWR via MAGLDR) that the partition is too large.
I would like to create a larger System partition, and was wondering whether there is a known way around this cap? A TMO HD2 has one-gig ROM storage, much of which is being wasted.
T-Mobile HD2: 576MB RAM, 1GB ROM
HTC HD2: 448MB RAM, 512MB ROM​
Click to expand...
Click to collapse
hay MarkAtHome
- i have test the TWRP and for my roms this not work. the CWM Touch have no problem.
- i have test more partition sizes with clk and magldr
- EU is 400/5 and TmoUS 450/5 this is my biggest sizes and this works good
- 1GB=1024MB and small bad blocks and you have 850MB full working blocks
i think a higher partition works with a new HD2 and not with a HD2 with 100 rom flash´s
pixelfreak