Database Users

[Think Tank]Dual Boot

So I was thinking...
df -h
/dev/block/mmcblk0p25------402.6M-----124.5M----257.3M-----33%---/system
/dev/block/mmcblk0p26------1.3G--------356.0M----886.5M----29% ---/data
/dev/block/mmcblk0p27------198.3M------35.7M----152.4M-----19%---/cache
Click to expand...
Click to collapse
We have roughly 2 gigs internal on our phones. Using CM7, my /system partition is over 60% empty. Why not install another rom beside it?
My idea is to partition the storage space into multiple directories that symlinks back to the original partitions only when booted.
For example, The partitioning could look like this:
/system------5M
/data--------5M
/cache------5M
/system1----200M
/data1------650M
/cache1-----100M
/system2----200M
/data2------650M
/cache2-----100M
Click to expand...
Click to collapse
The system would boot past splash1, where a screen similar to this could show up:
{
"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"
}
Depending on your selection, it would boot with either /system1 or /system2, symlinked to the original /system.
I know that it is possible to change your mtd partitions, it is a very commonly used hack on the G1 developed by Firerat and lbcoder (thread). If we can take this concept and take it a step further and create our own partitions, this seems feasable.
Some thoughts/concerns:
-both roms would have to use the same kernel as the kernel is one of the first things to boot.
-space for apps might be a bit tight for some, so A2SD might need to be used
-we would need a modified recovery image in which you have to specify which /system a rom would be copied to
-sharing /data and /cache might be possible, but might lead to problems with dramatically different roms.
-how would we go about setting up the screen to select which rom to boot?
-the closest thing to dual booting that we can do now would be /sd-ext based roms like old HD2 roms or Enomther's rom from before we had perm root
My programming knowledge is limited to HTML and flash, and I am a linux noob so I can't do much more than build a rom from source or changing out/modifying some png's for a theme.
If my idea seems feasible somebody else would have to code it. If you can come up with a better idea for dual boot, then by all means, share

mejorguille said:
So I was thinking...
We have roughly 2 gigs internal on our phones. Using CM7, my /system partition is over 60% empty. Why not install another rom beside it?
My idea is to partition the storage space into multiple directories that symlinks back to the original partitions only when booted.
For example, The partitioning could look like this:
The system would boot past splash1, where a screen similar to this could show up:
Depending on your selection, it would boot with either /system1 or /system2, symlinked to the original /system.
I know that it is possible to change your mtd partitions, it is a very commonly used hack on the G1 developed by Firerat and lbcoder (thread). If we can take this concept and take it a step further and create our own partitions, this seems feasable.
Some thoughts/concerns:
-both roms would have to use the same kernel as the kernel is one of the first things to boot.
-space for apps might be a bit tight for some, so A2SD might need to be used
-we would need a modified recovery image in which you have to specify which /system a rom would be copied to
-sharing /data and /cache might be possible, but might lead to problems with dramatically different roms.
-how would we go about setting up the screen to select which rom to boot?
-the closest thing to dual booting that we can do now would be /sd-ext based roms like old HD2 roms or Enomther's rom from before we had perm root
My programming knowledge is limited to HTML and flash, and I am a linux noob so I can't do much more than build a rom from source or changing out/modifying some png's for a theme.
If my idea seems feasible somebody else would have to code it. If you can come up with a better idea for dual boot, then by all means, share
Click to expand...
Click to collapse
Lol that's pretty cool idea
Sent from my Liquid Metal using XDA App

Bounty in place for this! I really share your dual boot vision. Very badass idea. If someone will work on it, im in bounty $20
Sent from my HTC Vision using XDA App

That would be difficult. bcoz,
1. Need WP7 drivers for G2/DZ devices
2. source/ROM compatible for G2/DZ (WP7 is not open, hehe m$)
3. A botloader.

Innocent Devil said:
That would be difficult. bcoz,
1. Need WP7 drivers for G2/DZ devices
2. source/ROM compatible for G2/DZ (WP7 is not open, hehe m$)
3. A botloader.
Click to expand...
Click to collapse
Lol who said I wanted windows 7? The picture up there is an example of a dual boot solution for old windows mobile phones. I was more interested in being able to run CM7/MIUI/liquid metal etc at once with minimal effort to change between them. And I'm pretty sure that WP7 doesn't use /system, /data, and /cache partitions.

Very cool idea .if you deside to do it I will be more than happy to help out in any way I can . Even if its not likely to work . It's still going to be a lot of fun trying .lol .cm and sense together . Or meego perhaps?
Sent from my HTC Vision using XDA App

mejorguille said:
Lol who said I wanted windows 7? The picture up there is an example of a dual boot solution for old windows mobile phones. I was more interested in being able to run CM7/MIUI/liquid metal etc at once with minimal effort to change between them. And I'm pretty sure that WP7 doesn't use /system, /data, and /cache partitions.
Click to expand...
Click to collapse
BAM!! +1000
Sent from my Liquid Metal using XDA App

awesome idea

I think this is a genius idea, and would have incredible implications if achieved. I also would be willing to donate to anyone who pulls off a functional and reproducible dual boot.

bahmanxda said:
Very cool idea .if you deside to do it I will be more than happy to help out in any way I can . Even if its not likely to work . It's still going to be a lot of fun trying .lol .cm and sense together . Or meego perhaps?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Me wants!!!! 2.4 as a daily,.... 3.0 for the eye candy!!!
Is there anything you genius'/genii/clever people can take from Kendon's Dualizer? http://www.villainrom.co.uk/forum/s...Dualizer-Dual-Boot-System&highlight=dual+boot

mejorguille said:
So I was thinking...
We have roughly 2 gigs internal on our phones. Using CM7, my /system partition is over 60% empty. Why not install another rom beside it?
Click to expand...
Click to collapse
Excellent idea!
My idea is to partition the storage space into multiple directories that symlinks back to the original partitions only when booted.
For example, The partitioning could look like this:
The system would boot past splash1, where a screen similar to this could show up:
Depending on your selection, it would boot with either /system1 or /system2, symlinked to the original /system.
Click to expand...
Click to collapse
There is already a multiboot bootloader installed on the phone which selects from two boot partitions... "boot" and "recovery". There is virtually no difference between them except for what is actually stored within the partitions.
I know that it is possible to change your mtd partitions, it is a very commonly used hack on the G1 developed by Firerat and lbcoder (thread). If we can take this concept and take it a step further and create our own partitions, this seems feasable.
Click to expand...
Click to collapse
You certainly could add or remove partitions from an MTD device using that approach, UNFORTUNATELY THOUGH, Vision does NOT HAVE an MTD device. It has an eMMC.
The eMMC also happens to be a bit of a WEIRD one. At the front of the eMMC there is a *fake* partition table, which is defined by the SPL. I am not aware of any way to alter this partition table except by modifying the SPL.
So repartitioning may not work.
However, symlinks WILL work.
Some thoughts/concerns:
-both roms would have to use the same kernel as the kernel is one of the first things to boot.
Click to expand...
Click to collapse
Nope. Put one kernel in the boot partition, the other one in the recovery partition. When you want to boot the second system image, simply boot into "recovery".
-space for apps might be a bit tight for some, so A2SD might need to be used
Click to expand...
Click to collapse
Easy
-we would need a modified recovery image in which you have to specify which /system a rom would be copied to
Click to expand...
Click to collapse
Trivial
-sharing /data and /cache might be possible, but might lead to problems with dramatically different roms.
Click to expand...
Click to collapse
Cache shouldn't be any problem, just wipe it on boot. Userdata would have to be manipulated in the exact same manner as system.
-how would we go about setting up the screen to select which rom to boot?
-the closest thing to dual booting that we can do now would be /sd-ext based roms like old HD2 roms or Enomther's rom from before we had perm root
Click to expand...
Click to collapse
Already answered. Boot recovery to boot the second system.
My programming knowledge is limited to HTML and flash, and I am a linux noob so I can't do much more than build a rom from source or changing out/modifying some png's for a theme.
If my idea seems feasible somebody else would have to code it. If you can come up with a better idea for dual boot, then by all means, share
Click to expand...
Click to collapse
Ok, now how I would do this is actually fairly simple to implement;
The boot image contains the basic structure of the root filesystem and sets up and mounts system and data.
It simply needs to be changed like this;
Destroy mountpoints "/system" and "/data".
Create new mountpoints "/base-system" and "/base-data".
Change the mounts for the system and data partitions to be mounted at the new mountpoints.
Create SYMLINKS "/system" --> "/base-system/system1" and "/data" --> "/base-data/data1" on the *first* boot image (to be installed to the "boot" partition), and "/system" --> "/base-system/system2" and "/data" --> "/base-data/data2" on the *second* boot image (to be installed to the "recovery" partition).
And that should basically do it.

This can also be used to boot Maemo/MeeGo.

This guy is already working on it, it is suppose to release soon.
http://forum.xda-developers.com/showthread.php?t=847423
I can't wait.

bahmanxda said:
Very cool idea .if you deside to do it I will be more than happy to help out in any way I can . Even if its not likely to work . It's still going to be a lot of fun trying .lol .cm and sense together . Or meego perhaps?
Click to expand...
Click to collapse
Not likely to work?!?! lol that's not very encouraging
DarkPyroGuy 09 said:
This guy is already working on it, it is suppose to release soon.
http://forum.xda-developers.com/showthread.php?t=847423
I can't wait.
Click to expand...
Click to collapse
Nah, booting from the sdcard isn't what I'm trying to accomplish. I want something on internal NAND, it would perform better (Look at the HD2).
riahc3 said:
This can also be used to boot Maemo/MeeGo.
Click to expand...
Click to collapse
It could, but as far as I'm aware there is no active effort of porting meego to the G2. Development stopped on the HD2 port, and now that nokia is out of the picture I imagine meego will die down.
There is already a multiboot bootloader installed on the phone which selects from two boot partitions... "boot" and "recovery". There is virtually no difference between them except for what is actually stored within the partitions.
Click to expand...
Click to collapse
Very good point, but would getting rid of a functional recovery be very practical? How would you approach rom upgrades? a PC based update system like ODIN for samsung phones? Fastboot? Or maybe you mean installing a new, separate boot partition.
You certainly could add or remove partitions from an MTD device using that approach, UNFORTUNATELY THOUGH, Vision does NOT HAVE an MTD device. It has an eMMC.
The eMMC also happens to be a bit of a WEIRD one. At the front of the eMMC there is a *fake* partition table, which is defined by the SPL. I am not aware of any way to alter this partition table except by modifying the SPL.
So repartitioning may not work.
However, symlinks WILL work.
Click to expand...
Click to collapse
Yeah we definitely don't want to mess with the SPL. I remember all the bricks from haykuro's SPL for having an incompatible radio/spl/recovery combination.
Nope. Put one kernel in the boot partition, the other one in the recovery partition. When you want to boot the second system image, simply boot into "recovery".
Click to expand...
Click to collapse
Again, I really wouldn't be happy loosing the recovery image. I mean, if you screw something up, boot to recovery, wipe, and reflash and you are good. If we replaced the recovery, to fix a problem you would have to be near a pc, boot to fastboot, wipe all, flash a recovery, boot to recovery, install a rom (or directly a PC10IMG.zip). I.E., the process would not be very noob friendly.
Cache shouldn't be any problem, just wipe it on boot. Userdata would have to be manipulated in the exact same manner as system.
Click to expand...
Click to collapse
When you wipe cache it takes considerably longer to boot, so maybe we should create separate cache partitions.
Already answered. Boot recovery to boot the second system.
Ok, now how I would do this is actually fairly simple to implement;
The boot image contains the basic structure of the root filesystem and sets up and mounts system and data.
It simply needs to be changed like this;
Destroy mountpoints "/system" and "/data".
Create new mountpoints "/base-system" and "/base-data".
Change the mounts for the system and data partitions to be mounted at the new mountpoints.
Create SYMLINKS "/system" --> "/base-system/system1" and "/data" --> "/base-data/data1" on the *first* boot image (to be installed to the "boot" partition), and "/system" --> "/base-system/system2" and "/data" --> "/base-data/data2" on the *second* boot image (to be installed to the "recovery" partition).
And that should basically do it.
Click to expand...
Click to collapse
Thanks for the detailed post dhkr234, you bring up a lot of good points and your method would be the easiest to implement, but unless I'm understanding something wrong, it would be not very friendly to the end user with no recovery image.

[QUOTE
Yeah we definitely don't want to mess with the SPL. I remember all the bricks from haykuro's SPL for having an incompatible radio/spl/recovery combination[/QUOTE]
I disagree... I think this is exactly what needs to be worked on. The devs eventualy got the G1 safe to flash the spl... and what's a few bricks if it means we can resize any and every partition on the device! Some one with some real skill with spl programing can figure it out... I have faith!
On a side note if we could "hack" the spl and re-partition the eMMC maybe we could reformat it to a faster file system... like they did at the factory and why our 4gig turned into 2... I would gladly trade that for 1gig if it is twice as fast! (Especially if I could change back)
Sent from my HTC Vision using XDA App

TheNewGuy said:
[QUOTE
Yeah we definitely don't want to mess with the SPL. I remember all the bricks from haykuro's SPL for having an incompatible radio/spl/recovery combination
Click to expand...
Click to collapse
I disagree... I think this is exactly what needs to be worked on. The devs eventualy got the G1 safe to flash the spl... and what's a few bricks if it means we can resize any and every partition on the device! Some one with some real skill with spl programing can figure it out... I have faith!
On a side note if we could "hack" the spl and re-partition the eMMC maybe we could reformat it to a faster file system... like they did at the factory and why our 4gig turned into 2... I would gladly trade that for 1gig if it is twice as fast! (Especially if I could change back)
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah, but on the G1's we have JTAG to bring it back to life. And the eMMC partitioning the 4 gigs in 2 is irreversible. CM7 already increased its efficiency though EXT4 instead of EXT3

mejorguille said:
Yeah, but on the G1's we have JTAG to bring it back to life. And the eMMC partitioning the 4 gigs in 2 is irreversible. CM7 already increased its efficiency though EXT4 instead of EXT3
Click to expand...
Click to collapse
Yea that's basically were I got the idea.... but there has to be something like Jtag for the G2. I mean our phones aren't born with all this great stuff! LOL they start out completely bare and the OS,spl,bootloader,and who knows what else gets added on.. so it has to exist. And I know the 4gigs to 2 is irreversible but what about formatting the 2gigs we have down to one? With the right partition layout( I don't use any where near the 1.3 gigs I have on apps) we could cut it in half and still have enough room. And this would all just be one of the possible things to do if we had a hacked spl like the G1.
But I am no dev and I can't complain(or help)... just thinking out loud.
Sent from my HTC Vision using XDA App

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...

[TUTORIAL] ClockWorkMod Recovery Navigation for Noobs

Hi
It just occurred to me that in all the instructions I've seen posted on using ClockWorkMod Recovery no-one has actually said how to navigate the menu system and when I was a noob it took me a little while to figure it out so I thought I would post here for others who may be experiencing the same.
Therefore I decided to write a tutorial on the subject.
===========================================================================================
First of all you need to get into ClockworkMod recovery. You do this by either pressing and holding the power button for 2 seconds and selecting recovery or press [vol +] + [vol -] + [home] + [power] together.
Once booted into ClockworkMod recovery this is what you see:
{
"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"
}
You can navigate these options by using the Volume-Up and Volume-Down keys to highlight an option and the ‘Home’ key. Use the ‘Back’ key to go to the previous item.
Let’s review each of these options and their sub-menu options in detail.
reboot system now
This one is self-explanatory.
apply update from sdcard
This can be used for installation of any official or unofficial update, ROM, kernel, theme etc. that is in a zip format installable from recovery, as long as the file is named update.zip and it has been placed on the root of your SD card (i.e. not in any sub-folder). Selecting this option (and most of the options featured below) will bring up a rather annoying confirmation prompt but this will save you from a lot of trouble caused by accidental key presses!
This is what we are talking about:
wipe data/factory reset
This option wipes all user data on the device as well as cache. Doing this will leave your phone in the state it was in when you bought it or when any custom ROM was first installed. It will also wipe any sd-ext partition that you might have setup (more on this later).
wipe cache partition
Wipes the cache partition of the device to clear all the data accumulated there through use. This is often used before or after installing a new ROM, app, kernel or any similar mod via recovery.
install zip from sdcard
This option brings up the following sub-menu:
apply /sdcard/update.zip
This one is essentially the same as the ‘apply update from sdcard’ option of the main menu.
choose zip from sdcard
Lets you install any zip file (with any name) from any location on your SD card. The file can be for a ROM, a kernel, an application, a theme or any mod as long as it is in recovery-flashable zip format. Entering this option will bring up a screen that will allow you to browse your SD card for the zip file and select it for installation as in this screenshot:
toggle signature verification
Turns the signature verification on and off. When signature verification is on, you will not be able to install any custom ROMs that haven’t been signed by the developers (most custom ROMs aren’t signed). Switching it off skips the signature verification check and proceeds with the installation.
toggle script asserts
Simply turns script asserts on or off. If you don’t know what these are don’t change this option.
backup and restore
Undoubtedly one of the most important features provided by a custom recovery, the backup and restore feature – also known as Nandroid backup – allows you to take a snapshot of your phone’s entire internal memory including all partitions, and save it on the SD card. This what it looks like :
Backup
Takes a Nandroid backup, as explained above.
Restore
Lets you restore a previously taken backup. Entering this option presents you with a list of existing backups from the SD card that you can choose from for restoration.
Advanced Restore
This option is similar to the Restore option but once a backup has been selected to be restored, this option allows you to choose what parts of it to restore. You can choose to restore the boot, system, data, cache and sd-ext partitions, as shown here:
mounts and storage
Allows you to perform maintenance tasks on all the internal and external partitions of your android device
mount/unmount /system, /data, /cache, /sdcard or /sd-ext
These options let you toggle between mounting or unmounting these respective partitions. Most users don’t usually need to change these options.
format boot, system, data, cache, sdcard or sd-ext
These let you directly format any of these partitions. This should be used with extreme caution as formatting any of these partitions will result in losing all data on them, especially the boot and system partitions. Formatting the system partition will remove your ROM and leave your phone without an operating system while wiping the boot partition may brick your phone unless you restore or flash another one before rebooting your device.
mount USB storage
Lets you enable USB mass storage mode for your SD card right from recovery so that you can connect it to your computer via USB and transfer any files to/from it without having to leave recovery.
advanced
This section contains a few options most users will not require, although wiping Dalvik cache, for example, is usually required when flashing a new ROM. Here are the options from this section:
Reboot Recovery
Lets you directly reboot from recovery straight back into recovery. This is a useful option for certain back-to-back installations that require the device to at least boot once between them.
Wipe Dalvik Cache
Allows you to wipe the cache for the Dalvik virtual machine (the custom-built Java virtual machine for Android) as mentioned above
Wipe Battery Stats
Wipes the saved battery usage statistics and effectively recalibrates the battery - useful when your ‘phone isn’t showing correct battery levels.
Report Error
In case of errors, this feature can be used to save a log of recent ClockworkMod recovery operations on the SD card that you can later post in the forums if you have a problem.
Key Test
Lets you press any of the hardware keys to see if they are properly functioning, and to see their key codes.
Partition SD Card
This option provides an easy way to partition your SD card properly for use with ROMs that support data2ext (a very handy hack for low internal memory devices that enables an /sd-ext partition on the SD card to be used as the internal user data storage i.e. as the /data partition – see mizch’s post @ http://forum.xda-developers.com/showthread.php?t=999856&highlight=data2sd). Once this option is selected, you will be given options to choose the sizes for the /sd-ext partition as well as an optional /swap partition on the SD card, and will then automatically format it for you, leaving the remaining space for normal SD card usage. This option will wipe all data from your SD card so use it with caution!
Fix Permissions
Fixes the file permissions for the internal memory partitions back to default. This is very useful as a fix for several errors and Force Closes that start appearing after you or an application you installed and provided root access end up messing up the permissions of important files.
Hope this helps to save someone the same embarrassment I suffered trying to work things out

Sharpy1964 said:
Hi
It just occurred to me that in all the instructions I've seen posted on using ClockWorkMod Recovery no-one has actually said how to navigate the menu system and when I was a noob it took me a little while to figure it out so I thought I would post here for others who may be experiencing the same.
Basically once you have restarted your phone into CWM recovery mode you scroll through the menu options using the up/down volume keys, select menu options using the centre 'home' key and go back using the right 'back' key.
Hope this helps to save someone the same embarrassment I suffered trying to work it out
Click to expand...
Click to collapse
nice.... i would suggest elaborate this thread and explain what each option actually does...... would help noobs.......

thanks Anant - working on it
EDIT: Tutorial added to first post in thread

* *

Thanks sharpy it a great help..as i m a noob..but can you please tell me how to get on this recovery screen??

hadi_xman said:
Thanks sharpy it a great help..as i m a noob..but can you please tell me how to get on this recovery screen??
Click to expand...
Click to collapse
You need a rom with CWM to get to it..
If u have it then press the power button for 2 secs and select recovery..
Or switch the phone off.. press HOME+VOL UP+VOL DOWN and start the phone..

hadi_xman said:
Thanks sharpy it a great help..as i m a noob..but can you please tell me how to get on this recovery screen??
Click to expand...
Click to collapse
[vol +] + [vol -] + [home] + [power]

Very good thread. Thank you

Wat do u mean by tht i m noob i told you..
it that rom with root..?

i did that but i got screen with written downloading and bar..

hadi_xman said:
Wat do u mean by tht i m noob i told you..
it that rom with root..?
Click to expand...
Click to collapse
Install one of the custom roms from dev section and yes they are rooted

Rapier07 said:
Install one of the custom roms from dev section and yes they are rooted
Click to expand...
Click to collapse
can i root my stock rom..?
please chk this thread i have post..
http://forum.xda-developers.com/showthread.php?t=1168610

hadi_xman said:
can i root my stock rom..?
please chk this thread i have post..
http://forum.xda-developers.com/showthread.php?t=1168610
Click to expand...
Click to collapse
Yes you can root your rom using z4root or superOneClick..
But rooting an eclair rom is no good..upgrade to froyo or better, a custom rom instead..

Rapier07 said:
Yes you can root your rom using z4root or superOneClick..
But rooting an eclair rom is no good..upgrade to froyo or better, a custom rom instead..
Click to expand...
Click to collapse
hhhmm i try to use z4root once it have 2 options temporary or permanent it tries temporary but noting happened it create supernova user but when i tried to goto the recovery mode the download screen appears..

Temporary doesn't work..try permanent

need somebody to answer this!!! does our cwm backups and restore the rom..?? anyone tried it>>

neo1691 said:
need somebody to answer this!!! does our cwm backups and restore the rom..?? anyone tried it>>
Click to expand...
Click to collapse
Yep it does
Just convert data to rfs before backup or it won't restore it

Rapier07 said:
Temporary doesn't work..try permanent
Click to expand...
Click to collapse
yeah i rooted my device using z4root but i can use rom manger, terminal emulator..but i dont have option to reboot into recovery
and i try manual method Power + Vol down + home but open download screen again..
how can i get into recovery boot..?

Type this in terminal emulator
Su
Reboot recovery

I have rooted my cell using z4 root (permanent root) but I have some issues and questions..
1)i can't get to the recovery screen by pressing the button (vol +) + (power) + (home)..when I press these buttons I got downloading screen..how to got recovery boot by pressing theses buttons..?
2)when I root into recovery using Rom Manager I don't get nand backup options..how to get that option..?
PLEASE GUYS HELP ME OUT..

Can't change from WP7 to android

Hey guys, I have been goosechasing all over the internet for the past 6 hours trying to figure out how to fix this issue, but due to the fact that files are taken down here and there, and guides are out dated, I have gotten nowhere. I can't flash the MIUI 2.2.10 rom to my HD2. Here are the steps I've taken:
1. Downloaded MAGLDR 1.13, Stock WinMo 6.5 rom from T-Mobiles website, downloaded all sort of HD2 recoveries, and lastly the MIUI rom
2. Flashed back to WinMo 6.5 through executing the "T-Mobile_HD2_MR_Software_3.14.531.1.exe" which is the stock rom through MAGLDR
3. Was not able to boot into MAGLDR WinMo 6.5 booted up. I held down the Power Button all the way through the boot, nothing. Tried several times, and then I flashed MAGLDR again. This gave me the error: "SD Kernel Open Failed" or something to that effect, but then it booted into MAGLDR. I decided to continue the next step of
{
"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"
}
, and went to 5. and let the drivers install. Then I put the MIUI rom in the same folder as DAF.exe and whatnot. I tried DAF.exe and ROMUpdateUtility and neither worked at all, gave me the error: “Error Description: USB init failed Info: .\RSPL\RSPL.cpp(723)
4 Became very frustrated with my life
Click to expand...
Click to collapse
What do I do? Please help ASAP!

Bumping, I really need help on this one!

bump
heres your 10char

How about flashing back to stock windows mobile 6.5?
Can you boot that? I can't really figure out what you mean in your OP.
Then, download and install HD2 Toolkit
http://forum.xda-developers.com/showthread.php?t=1090783
1. Task 29
2. Install MAGLDR
3. CWM recovery partition
4. Install ROM
5. Voila

KrewsialNL said:
How about flashing back to stock windows mobile 6.5?
Can you boot that? I can't really figure out what you mean in your OP.
Then, download and install HD2 Toolkit
http://forum.xda-developers.com/showthread.php?t=1090783
1. Task 29
2. Install MAGLDR
3. CWM recovery partition
4. Install ROM
5. Voila
Click to expand...
Click to collapse
I did flash back to WinMo 6.5.... but I did not install HD2 tool kit. I downloaded it, but how do I install?

Ok, I got it to boot into CWM but none of the mounts are mounting. /system, /cache etc because it failed to find /system, /cache etc. What do i do?

gerbetta33 said:
Ok, I got it to boot into CWM but none of the mounts are mounting. /system, /cache etc because it failed to find /system, /cache etc. What do i do?
Click to expand...
Click to collapse
Question: Which section you are original from, wm6, android nand,android sd or wp7? Installed wm6 rom correctly!

- Flash Stock WinMo 6.5 build
- Install HSP 2.08
- Task 29 & Radio 2.15.50...
- Install Magldr
- Partition your NAND (with HD2 toolkit or with the DAF.exe included in the recovery files)
- Boot into CWM and install zip from sd card
I missed any mention of HSPL in your previous comments, but the above stated should work just fine.
Remember that you have to rework your sd card, as far as I know WP7 does strange things to the sd card, so you would have to revert that as well.
Never used WP7 on my phone, but I don´t see why the above mentioned procedure shouldn´t work, the links to some of the files needed are in my signature.

When you do get into MAGLDR.
1.) Go to USB flasher and flash the CWM.. (Clockwork Recovery Mod) (you might want to right click DAF.exe and run as administrator)
2.) After reboot the phone should go into MAGLDR and thereafter scroll to option AD recovery and press "call"
3.) You have entered CWM. Now, format your SD card and then mount your SD card.
4.) Copy the MiUI zip file from computer to phone..
5.) Go to install Zip from sd card and install MIUI.
You're done..

gerbetta33 said:
Hey guys, I have been goosechasing all over the internet for the past 6 hours trying to figure out how to fix this issue, but due to the fact that files are taken down here and there, and guides are out dated, I have gotten nowhere. I can't flash the MIUI 2.2.10 rom to my HD2. Here are the steps I've taken:
What do I do? Please help ASAP!
Click to expand...
Click to collapse
gerbetta33 said:
Ok, I got it to boot into CWM but none of the mounts are mounting. /system, /cache etc because it failed to find /system, /cache etc. What do i do?
Click to expand...
Click to collapse
I'm not being sarcastic or anything but ...
Why are you posting this in the development forum?
Why are you even posting it in the WP7 section while your question is totally concerning Android? (because you were on WM6.5)
Why were you trying to mount /system or /cache ? you don't have a rom installed yet !
From the CWM menu, select "install zip from sdcard" and choose your MIUI-rom.zip file and select yes, and now it will flash your rom. Make sure you have had the correct partitions set beforehand .

Marvlesz said:
I'm not being sarcastic or anything but ...
Why are you posting this in the development forum?
Why are you even posting it in the WP7 section while your question is totally concerning Android? (because you were on WM6.5)
Why were you trying to mount /system or /cache ? you don't have a rom installed yet !
From the CWM menu, select "install zip from sdcard" and choose your MIUI-rom.zip file and select yes, and now it will flash your rom. Make sure you have had the correct partitions set beforehand .
Click to expand...
Click to collapse
I posted because i need an answer ASAP and that was the forum with the most recent active posts. Sorry, I'm in the wrong on that one. I flashed the rom and everything, but then it just reboots back into CWM everytime, it won't boot into the room, more specifically, it boots into MAGLDR which automatically boots into CWM. I have HSPL 2.08 installed already. I haven't repartitioned anything. How do i do that?

sudeep6258 said:
When you do get into MAGLDR.
1.) Go to USB flasher and flash the CWM.. (Clockwork Recovery Mod) (you might want to right click DAF.exe and run as administrator)
2.) After reboot the phone should go into MAGLDR and thereafter scroll to option AD recovery and press "call"
3.) You have entered CWM. Now, format your SD card and then mount your SD card.
4.) Copy the MiUI zip file from computer to phone..
5.) Go to install Zip from sd card and install MIUI.
You're done..
Click to expand...
Click to collapse
I tried DAF.exe and it doesn't recognize my HD2, then gives me the error I mentioned in the OP, even after running as administrator.

I can't beleive that senior member act like tootal noob. What do you think that this forum is? Online support? Bump whenever you want and expect answer in a minute? Will you pay somebody for the answer? Let me remind you that people here DISCUSS about HTC HD2 Windows Phone 7 Development, so please delete your useless topic and go bother somebody else!

Maybe try unchecking allow USB connections from active sync..

gerbetta33 said:
I tried DAF.exe and it doesn't recognize my HD2, then gives me the error I mentioned in the OP, even after running as administrator.
Click to expand...
Click to collapse
May i also suggest you cut your signature, its rather long, and slightly ironic and a bit offending to be honest

dddrko said:
I can't beleive that senior member act like tootal noob. What do you think that this forum is? Online support? Bump whenever you want and expect answer in a minute? Will you pay somebody for the answer? Let me remind you that people here DISCUSS about HTC HD2 Windows Phone 7 Development, so please delete your useless topic and go bother somebody else!
Click to expand...
Click to collapse
I thought that after some of the things I did for this community, I might be able to get immediate help in my time of need. Do you mind pointing me to the nearest direction of "Bricked HD2 online support"? I already said I was in the wrong for posting the question here, but you fail to understand that without my phone, I can't do my job and support myself. Troll harder next time.

dazza9075 said:
May i also suggest you cut your signature, its rather long, and slightly ironic and a bit offending to be honest
Click to expand...
Click to collapse
Are you referring to the quote? It was a troll response someone gave me when I brought a mistake to their attention. I thought it was humorous.

gerbetta33 said:
Are you referring to the quote? It was a troll response someone gave me when I brought a mistake to their attention. I thought it was humorous.
Click to expand...
Click to collapse
oops, those bloody like/reply buttons again!
lol, yes but it doesnt come across that way to anyone who doesnt know that
But i was meaning the length of it, when your sig is 3 or 4 times the size of your post it kinda looks a bit daft. anyhow...

gerbetta33 said:
I thought that after some of the things I did for this community, I might be able to get immediate help in my time of need. Do you mind pointing me to the nearest direction of "Bricked HD2 online support"? I already said I was in the wrong for posting the question here, but you fail to understand that without my phone, I can't do my job and support myself. Troll harder next time.
Click to expand...
Click to collapse
Guys, give the guy a break. He's already admitted that he was wrong.
Back on topic, I recommend using the HD2 toolkit by ksubedi (Thanks to him)
Just follow this guide written by me : http://forum.xda-developers.com/showpost.php?p=16528026&postcount=7 (Very short and straight-to-the-point with no blabber guide)
Modify step 8 with the rom you are to install as well as step 10 with the required partition size (can be obtained from the thread of your rom).
Good luck.

Marvlesz said:
Guys, give the guy a break. He's already admitted that he was wrong.
Back on topic, I recommend using the HD2 toolkit by ksubedi (Thanks to him)
Just follow this guide written by me : http://forum.xda-developers.com/showpost.php?p=16528026&postcount=7 (Very short and straight-to-the-point with no blabber guide)
Modify step 8 with the rom you are to install as well as step 10 with the required partition size (can be obtained from the thread of your rom).
Good luck.
Click to expand...
Click to collapse
You are a gentleman and a scholar. Booting into MIUI right now. Thanks you so much!!

[Guide][EASY][Marshmallow] Disable Force Encryption - No Ugly Corrupt on Boot

I seen a lot of Discussion On this topic, and found a really simple way to disable Forced Encryption and it also removes the warning at boot. This in NO WAY is my work at all. I am sharing this [FIX] FED-Patcher v7 (ForceEncrypt Disable Patcher) which was posted by @gladiac. Absolutely make sure you head over to his forum and hit the Thanks button. This works great
Screenshots Below
I have the option to encrypt the phone as you can see circled. I went into system with Root Explorer and was prompted for R/W access and obviously I granted it. Everything is working great!
{
"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"
}
Preparation
Before proceeding, enable Developer options and MAKE SURE USB DEBUGGING IS ENABLED!!!
1. Download fed_patcher_v7-signed.zip and check here to verify the latest version
2. Download [BETA][2015.10.10] SuperSU v2.52 by @Chainfire
3. Download Whatever ROM you are going to use. I am currently running [ROM]【6.0】LightROM - Marshmallow【MRA58K】- 10/08/15
Instructions
1. Backup your SD Card, during this process, everything will be erased during the process
2. Reboot into TWRP, this is important that you actually have TWRP
3. Perform a Full Wipe by doing the following:
Press Wipe
[*] Press Advanced
[*] Click every check Box
[*] Wipe 3x for good measure
[*] Press Home button
[*] Press Wipe
[*] Press Format Data
[*] Type yes in the box to perform the format
[*] Perform this 3x for a good full wipe
4. Reboot TWRP (Do Not Install Super Su Yet)
5. Once Back In Recovery, On the computer, open My computer
6. Navigate to and open the Nexus 6 Drive
7. Drag the Zip files below to your Phone -
1) fed_patcher_v7-signed.zip
2) BETA-SuperSU-v2.50.zip
3) ROM Zip
If You are Having Trouble, take a look at the screen shots below
You Want to make sure you mount data if it is not, and make sure MTP is not disabled! Thanks @jamiejames and @aliasferno
8. Flash your ROM 1st (DO NOT BOOT AFTER FLASHING)
9. Wipe Dalvick Cache/Cache 3x
10. Flash fed_patcher_v7-signed.zip
11. Wipe Dalvick Cache/Cache 3x
12. Flash BETA-SuperSU-v2.52.zip
13. Reboot and Enjoy with no more red error sign during boot and no encryptionhttps://source.android.com/devices/tech/security/verifiedboot/verified-boot.html#user_experience
Supported Devices
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
[*]v2 - Added Motorola Nexus 6 (shamu) support
[*]v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
[*]v4 - Added support for signed boot-images
[*]v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
[*]v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
[*]v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What Do I need To Make This Work?
A supported device (Your nexus 6)
[*]An unlocked bootloader
[*]An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
[*]A recovery that includes busybox (TWRP, CWM)
How Do I Use it?
Follow Instructions above - This is the basic need to know information
[*]Make a thorough, conservative backup of your data if there is any on your device
[*]Go into your recovery (TWRP, CWM)
[*]Flash fed_patcher-signed.zip
[*]If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is It Dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
All Thanks To:
@gladiac - For Putting the OP together for the Nexus 9 and sharing this
[*]@rovo89 - for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
[*]@pbatard - for making (un)mkbootimg (dunno if he is on xda)

good work mate

Danvdh said:
good work mate
Click to expand...
Click to collapse
Thanks Bro...Thanks for the ROM, I saw it's already updating. Thanks

Thanks for this! :good:

Herk718 said:
Thanks for this! :good:
Click to expand...
Click to collapse
No Problem...

@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!

TY you for this info. Exactly what I was looking for. Thanks a milion

spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I am decrypted, I have super user ...I was able to restore with titanium backup, I will see if I can edit the build.prop or just mount rw
edit: I was able to mount rw successfully in root explorer no issues
simunovic said:
TY you for this info. Exactly what I was looking for. Thanks a milion
Click to expand...
Click to collapse
No problem
Sent from my Nexus 6 using Tapatalk

spunks3 said:
@gladiac mentioned he wasn't able to get system R/W access with v7. I'm not sure which SuperSU he was using earlier in the day but can you confirm? I'd like to make a couple edits to build.prop. thanks!
Click to expand...
Click to collapse
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me

bdorr1105 said:
I posted a few screenshots in post# 1, I could mount R/W from the system folder in Root Explorer, everything is working great for me
Click to expand...
Click to collapse
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose

spunks3 said:
Very much appreciated!!! Now I wonder if Android pay works.. Something I'll test out later this week I suppose
Click to expand...
Click to collapse
It won't work unless you remove root
Sent from my Nexus 6 using Tapatalk

Moved this from the development forum as there is no development, this is not your work, and it is a guide for this; this is better suited to a General forum.
Thread reopened on the basis that this is a guided collection of work.

Ok, this OP is more of a guide on how to use this tool, I am going to edit the OP and redirect it to the Forum that was in the Nexus 6...There was a mis-understanding on my part, I did not realize this was in the Nexus 6 Android Development already, this is just how to run it, and the steps to successfully flash and get rid of the warning before booting Android 6.0 and having a force decrypted set up form boot...

bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse

atrix4nag said:
bdorr1105 said:
QUOTE]
As per Light Rom description it says Forced encryption is disabled. So If I install Light ROM, them there is no encryption right? or am I missing something?
Click to expand...
Click to collapse
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse

bdorr1105 said:
atrix4nag said:
There is no encryption, this is just an extra layer, if you flash kernels to make sure it doesn't force encryp, but you should be fine and not have to do this. This gets rid of the warning message at boot
Click to expand...
Click to collapse
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse

atrix4nag said:
bdorr1105 said:
Just now installed light rom, installed custom ROM, and format data. so no more encryption on my phone, but I have the warning message at boot.
so following this method, I wont be having warning message, is that right?
Click to expand...
Click to collapse
I do not have the warning at boot doing this method. So yes, you should no longer have the warning
Click to expand...
Click to collapse

If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.

Hucklebury said:
If i follow the steps correctly and change my kernel will the corrupt boot screen return?
my plan is to use Xtrasmooth rom with Elite kernel.
Click to expand...
Click to collapse
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again

bdorr1105 said:
I am not 100% sure if it will or not, with the kernel there is a chance it will, but I think you will be ok.. The splash screen is really more of an annoyance than anything else, but I think it will be ok.
At any rate, all you would have to do is flash just the fed_patcher_v7-signed.zip again
Click to expand...
Click to collapse
ok, thanks for the reply. i have tried many times to get rid of that ugly screen without success, ended up going completely stock M.