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

WP7 Install on HD2 T-Mobile Version TIPS

My Guide to Installing Windows Phone 7 on HTC HD2 TMOUS(T-Mobile US) edition
I’m sure there are lots of guides out there and I am noting other threads and give ALL CREDITS to where credit is do. I CLAIM NOTHING BUT UNDERSTANDING OF THE PROCESSES AND THE PAINS OTHERS HAVE ALREADY ENDURED TO GET THIS WORKING.
Most of the directions were pretty straight forward but just felt that they didn’t highlight things that you needed to know. I found that this knowledge and method of doing things made it easy and the best chance for you to get it working the first time around.
I USED THE INSTALL GUIDE FOR XBmod-Yuki located http://forum.xda-developers.com/showthread.php?t=1246040 to actually walk through the install. Below is simply the consolidated knowledge I learned from countless hours of research in the forums and the REAL work done by others. I am hoping this post helps to eliminate the constant posting of the same issues where the answers are often buried within pages of postings. This is not from an expert but from someone who spent days trying to get WP7 on the HD2 because I wanted to use it.
MicroSD TIPS
First off: REMOVE MicroSD MEMORY CARD. Simply put you don’t need it till you update to MANGO (build 7720 of WP7 software) using Zune. All it does is cause hundreds of forum postings about why people can’t get it working.
Secondly, NOT ALL MicroSD MEMORY CARDS ARE EQUAL. After much research in the forums and all the problems I had with trying to get this working, I can honestly say that I still do not know that there is a single source of the problem. What I can say is that MicroSD MEMORY CARDS that work get easier to find as you update. We could go on for hours about this topic and people will say all sorts of things but this is what I found to work for me. FOLLOW RULE #1 from above then stick with quality brands with at least a Class 4 rating (the number in the small circle on the card). People recommend SanDisk above all else, other cards do work.
Third, the use of a MicroSD card with WP7 OS will lock the card and encrypt it. You CANNOT use this card with anything else until it is unlocked. TONS of guides on this but there are three methods to it.
• Using some form of disk destruction or partitioning software such as KillDisk to remove the lock
• Using your phone to unlock by side loading an app on your phone and booting into WP7 after Hard Reset and unlocking. I USED this method after many hours trying other things and not understanding how this worked, therefore I will elaborate on this more in just a bit.
• Using a special Nokia phone/camera that does low-level formatting of any media inserted. There’s a list of devices that are known to work in the forum.
Expansion notes of using phone to unlock:
You can put WP7 on your phone without a memory card in it at all. DO THIS FIRST. Once you get WP7 up and running you can use Zune to update your phone to where it tells you have the latest release (NOT MANGO YET), the build is 7392 (NODO) update. Google this to find build number or I will edit it in eventually. Side load the unlock app as outlined in the install guide. Once you have this you must understand the way the process works. WP7 encrypts and preps any MicroSD card at time of first boot. With that said you MUST USE the same WP7 ROM to get this to work. So if you locked your card using the XBmod-Yuki ROM then you have to use it to unlock it. I tried HD2O ROM and then went back and realized the card was not only locked to WP7, it was locked to that build. I was successful at flashing the XBmod-Yuki release back into place after flashing the HD2O and was able to use the MicroSD and unlock if I needed to. Which I did since I used like 10 cards before figuring out Rules #1 and #2 of MicroSDs.
THE TRICK TO SUCCESS:
After having the same WP7 ROM you locked your MicroSD with installed and updated to NODO, the unlock app installed, you can simply do a HARD RESET.
What is a “HARD RESET”: Simply put either use WP7 – Settings -> About -> Reset or using the Vol up and down where you it counting in MAGldr, 1,2,3,4,5,6. When you hold the Volume Up and Down it will present you with a white screen and you simply press Volume Down twice to do the same thing that using the menu item in WP7 does. The great thing is that first time you boot into WP7 it doesn’t seem to care about the memory card much. You can run the unlock app and then do a battery pull and remove the card. At this point Windows on your PC will see the card and you will be able to format it. If you have more than one card simply insert the next card and use the Volume button reset method. It will make you go through the initial WP7 setup screens each time but heck you unlock the card without much effort. I found this method to be the most useful and easy method.
Remember you will need to HARD RESET after each memory card change including once you are done unlocking all the cards you locked trying to get this working and have the card you will be using.
Remember your MicroSD card must be inserted before WP7 boots. Easiest way I know of was to simply pull the battery out when done unlocking or before HARD RESETTING.
INSTALLATION NOTES/OUTLINE FROM FORUM POST REFENCED ABOVE WITH CHANGES THAT I SAW SINCE THEIR WRITINGS
1. READ READ READ the Install Guide and follow the guidelines above
2. HARD SPL v2.08, when using the install tool simply select the one with .HSPL at the end NOT .0000, the HSPL means HARDened. This simply allows you to be sure you can get the tricolor boot screen (get to by holding Volume Down) no matter what you do to the phone. The Tricolor screen allows you to fix most damage that I saw.
3. Radio – Just simply use LEO_RADIO_2.15.50.14, it supports all HD2 versions so it doesn’t matter if you have TMOUS or EU edition of the phone. The rest of the radios listed are older and for the general user are not useful for this process.
4. MAGldr 1.13 is the NEWEST VERSION for the boot loader. Install this. Why, because it allows your phone to actually load WP7. You can use it for Android too if you wish to dual boot but I don’t cover that as you won’t be using these notes if you are that advanced with things.
5. Windows Mobile 6.5 Stock ROM, I honestly have no idea why you use this but I can follow directions and so should you. Install it and move on.
6. Zune, just simply install it, you will need it to update. MAKE SURE IT IS CLOSED AT ALL TIMES OTHERWISE. If not it will interfere with installing using other methods.
7. WP7 Update CAB Sender. You will need this. It is a very simple program to use. Whatever CAB files you stick the folder with the .bat file it will install on the phone. Be sure you pay close attention to adding and removing CABs from the folder as they are needed.
8. To Get to MANGO you must do the HD2-7720fix and the DeviceProvisioning.CAB steps (#11 and 12 from post #4 of the install guide), Zune will take you directly to MANGO 7720 instead of 7712 which I am assuming changed since the guide was made. No need to complete the #14 step from what I can see since Zune seems to be able to install RTM version of 7720 automatically. This may change at some point where as long as you got 7392 update and a working MicroSD you don’t need the fix part or the device provisioning cab but I could be wrong. I just did steps #11 and #12 and got MANGO to shop up as the update.
9. HARD RESET IS YOUR FRIEND, it cures most issues with MicroSD issues, including lockups, freezing and crashing.
I hope this helps you get your WP7 loaded the first time. READ READ READ the install guide fully and before each step be sure you know what you are to do and you will be successful.
If can sticky this or reuse it eslewhere to aid in the install guides please do so. PLEASE "THANKS" ME SO I MIGHT GROW IN RECOGNITION AND HELP FURTHER!

Hi
the new Hd20 (v1.22) cannot see any wi-fi (both wpa2 protected and unlocked).
Can you tell me how you got it to work ? I see that most of the posts are from
outside the US (probably using the EU version of HD2). I have the TMOUS version
and in the US.
thx
z

Very nice work. I have been planning to get my hands back on my HD2 that I had given away to my dad a few months back, and have been trying to read up on all that is there to know about having WP7 on the HD2 and I have to say that this is the best post out there that I have come across.
Thanks a bunch !

Hi,
Would you consider changing the format of your tutorial? As in... varying fonts, using paragraph spacing, bold where applicable, and maybe indentations? Right now, it looks information, but a giant mass of words with no visual separation.

anseio said:
Hi,
Would you consider changing the format of your tutorial? As in... varying fonts, using paragraph spacing, bold where applicable, and maybe indentations? Right now, it looks information, but a giant mass of words with no visual separation.
Click to expand...
Click to collapse
^ I agree with this.
Very useful info, but would be easier to follow if formatted for better organization.

waiting for 1 day the T-Mobile HD2 can use the full 1024ROM, even don't need the extend card....may it be ?
"At current moment LEO1024 supported, but only 512 megabytes of NAND is used. "

bount said:
waiting for 1 day the T-Mobile HD2 can use the full 1024ROM, even don't need the extend card....may it be ?
"At current moment LEO1024 supported, but only 512 megabytes of NAND is used. "
Click to expand...
Click to collapse
Not sure what you mean by this comment.

I'm testing to see if I can replicate this issue, I do not have this issue as far as I can tell.

I revised my post, is it better or do you have suggestions to make this better? Is there a better place for my notes to go? i.e. different post or thread? Referenced in a STICKY? I am happy to help however I can.

That is so much easier to read now. Thanks for making it pretty!!!

Originally Posted by bount
waiting for 1 day the T-Mobile HD2 can use the full 1024ROM, even don't need the extend card....may it be ?
{
"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"
}
"At current moment LEO1024 supported, but only 512 megabytes of NAND is used.
​
azon21 said:
Not sure what you mean by this comment.
Click to expand...
Click to collapse
The USA T-Mobile HD2 has 1GB ROM and 576 MB RAM, whereas the Asian and European versions have 448 MB RAM (576 MB of RAM enabled by Special Radio) and 512 MB ROM. NAND is the internal flashable memory here, or the ROM in the phone. bount is wondering if the full 1GB of ROM can be used on the USA T-Mobile, rather than using the SD card. A more likely scenario might be having Windows Phone 7 and Windows Mobile on partitions in the 1GB of ROM, and Android on the SD card..............

Awesome this post is awesome........
Sir make a new post where we can get dual boot process WM7.5 & Android
Thanks in Advanceeeeeeee

SOHOM said:
Awesome this post is awesome........
Sir make a new post where we can get dual boot process WM7.5 & Android
Thanks in Advanceeeeeeee
Click to expand...
Click to collapse
You can find all the information you are seeking on dual booting in this thread. I hope you find the information you need in that thread.

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

Q&A/T thread for "Resurrection [MAG/cLK][NATIVESD][DATAOnExt] MIUI"

[SIZE=+3]This thread has been created strictly for
Questions & Troubleshooting[/SIZE]
[SIZE=+2]Specific for "Resurrection [MAG/cLK][NATIVESD][DATAOnExt] MIUI"[/SIZE]
{
"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"
}
​
[SIZE=+2]This thread has been created for people to share issues, questions and help
while using this version of "Resurrection [MAG/cLK][NATIVESD][DATAOnExt] MIUI"​[/SIZE]
Resurrection [MAG/cLK][NATIVESD][DATAOnExt] MIUI
[PLEASE make sure to thank developer for the dedication to this ROM
Please do not clutter the Development thread with non development-related chatter
See post two for FAQ​

FAQ​
Q Why a special Q&T Thread for a specific ROM??
A The bigger a ROM development thread gets, the greater the chance that posts are being placed in this thread that are not related to the ROM development itself, e.g. problems with flashing, installation, bugs, things not working etc. However this is understandable, it's not according to the guidelines of XDA for Development sections. Therefore the main goals of the ROM specific Q&T threads is to avoid this cluttering of the original develpment thread with these OT posts by redirecting the posters to the ROM specific Q&T thread and also to relieve the developer from answering these post, so he can dedicate his time to developing.
Q How to move my post to the Q&A/T thread?
A Copy the text of your post in the dev's thread, got to the Q&A/T thread and paste it there. After having done that, go back to the dev's thread, edit your post and change the text into: moved to Q&A/T thread, preferably accompanied with a link to this thread.
Q When I'm asked to move my post to the Q#A/T thread, do I have to do that?
A When you're asked to move your post, there will always be given an explanation by the OP of the Q&A/T, e.g. your post is not development related (f.i. SD card problems, etc), so please be so kind to move your post. If you want to help the dev to keep his original thread as clean as possible from OT posts, then the answer is, of course, YES. Although we cannot force you to move your post, it's highly recommended to do so
Q Where can I download this ROM and How do I install?
A You can find the link to download and installation instructions HERE.. Pay close attention to this post, everything required for a successful flash is listed right here. If you fail to follow the instructions or meet the requirements for installation, you could run into some problems.
Q How’s battery life?
A see this question asked repeatedly across all ROMS. Honestly there is no way to give you an answer based on a ROM. There are too many variables in question and results vary from user to user and device to device. Battery life is going to depend on age and condition of your battery, your use habits with your device, installed apps, tweaks, settings, etc...
Q How do I...
A Ask your questions and report your issues in this thread. You will receive a response and hopefully get you back up and running this ROM to it's fullest

Nice job, thank team of RC's!
Welcome every MIUI Flashaholics!
Place your Q&A Troubleshooting here so as keep the main thread clean! Thank you!

THANHVO31 said:
Nice job, thank team of RC's!
Welcome every MIUI Flashaholics!
Place your Q&A Troubleshooting here so as keep the main thread clean! Thank you!
Click to expand...
Click to collapse
Hi my friend,
would you also be so kind to post this message at the end of your thread???
In addition to THAN's post:
This thread has been created, in accordance with the owner of the original development thread, to keep his thread clean from Off Topic, e.g. non-development related, posts.What are OT posts? Examples:
1. I want to install this ROM, how to do that?? This is a question you can find in the first post of the thread.
2. I want to use a specific app with this ROM, will this work with it. Not development related., etc . etc.
3. Posts about WiFi/BT that are working for you, while others have no problems with that.
4. SD Card related problems, etc
very best regards, Kuzibri

NativeSD Random Freeze - SOLVED.
NativeSD Random Freeze - SOLVED.
Quote:
Originally Posted by runuts View Post
I recently switched from NAND to Native SD on a T-Mobild (1024 MB) HD2. The ROM and apps are just too big to be used with everything on NAND. Not a complaint, just an observation.
Clean install to a a SanDisk Ultra® microSDXC™ UHS-1, 64 GB Set the EXT4 partition to 4 GB. Install seems to go fine and after first boot, the phone runs fine; however, I am experiencing random freezes during the day that require removing the battery. Running a second phone using a Samsung 32 GB, Class 10 and NexusHD2-JellyBean-CM10.1 V2.1 on Native SD with no problem.
At this point, I'm not certain whether the issue is related to the SD card, the build, or an incompatible app running in the background. Last evening, I went through all of the apps on the phone, starting using, and then closing. None triggered the freeze. It seems to occur after the phone has gone to sleep. It just won't wake-up, requiring pulling the battery and restarting.
I had been running the prior releases on NAND without issue other than the aforementioned memory problems. Any comments, suggestions appreciated.
Over the weekend, I replaced the SanDisk Ultra® microSDXC™ UHS-1, 64GB card with a Samsung Pro Extreme Speed 64GB and reinstalled. So far, the problem appears to be solved and was related to the SanDisk Card. Performed a second installation using a Microcenter store brand 32 GB, Class 10 card and it too seems to be running flawlessly. The SanDisk cards are headed back to the store. I may simply have had a bad card, but wanted to share my experience.

[Q] How to add power key to sofykeys in MIUI roms after V3.3.13 & onforwards
Softkeys is great option for HTC HD2 as it has poor brittle key pad
MIUI roms gifted from you dear thanhvo31 (http://forum.xda-developers.com/show....php?t=1019092) are great & bieng regulary updated, but unfortunately the newly released roms havin miui V5 version dont have power key included in softkeys, i tried to search a method to add power key but no benefit
Tried this thread (http://forum.xda-developers.com/show....php?t=1407003) even but didnt work
thanhvo31 can you explain how to add powerkey, or plz post the versions having powerkey
Thanks

Need Help
Hi,
I really need some help to understand better the way of flashing this rom.
I may have been doing something wrong.
But first i need to say I LOVE MIUI ROM.
I have an HTC HD2 Leo (EU) 512MB
My SD Card is not of a good brand, it is 8gb class 6 card, that came with my first HTC HD. It has some years now.
I have installed this ROM via ClockMod 1.5 and created a FAT 32 and an EXT4 partition.
Everything runs excellant in the ROM, but after a few days, the phone starts to freez and in a point i start losing APPS.
It is really anoying to do it all again, all is backuped with Xiamomi Account and Google account, but it is really boring to put everything again on SD card, and flash it all over again.
Do you think it might be a problem with my SD Card?
Help is much apreciated.
I really want to use this ROM.
Thank you,

hollowprod said:
Hi,
I really need some help to understand better the way of flashing this rom.
I may have been doing something wrong.
But first i need to say I LOVE MIUI ROM.
I have an HTC HD2 Leo (EU) 512MB
My SD Card is not of a good brand, it is 8gb class 6 card, that came with my first HTC HD. It has some years now.
I have installed this ROM via ClockMod 1.5 and created a FAT 32 and an EXT4 partition.
Everything runs excellant in the ROM, but after a few days, the phone starts to freez and in a point i start losing APPS.
It is really anoying to do it all again, all is backuped with Xiamomi Account and Google account, but it is really boring to put everything again on SD card, and flash it all over again.
Do you think it might be a problem with my SD Card?
Help is much apreciated.
I really want to use this ROM.
Thank you,
Click to expand...
Click to collapse
Hi,
1. for installing instructions for this ROM see page 1 of this thread: http://forum.xda-developers.com/showthread.php?t=2255056
2. IMJO you should buy a new SD Card cause that might be the cause of your problem(s). When was the last time you formatted your SD Card? I format it every two weeks to prevent the Card is the cause of problems, like freezes, instability, battery drainage, etc.
kind regards, Kuzibri

Hi...
I ve quest ... about nand and native SD.
Im new to jb. Still me using miui GB.2.3.7
My quest is ... for jb install .. Rom partion 380 MB along with SD card 2 Gb extra partition..... ?
I could not understand jb install...do i needs more space ..
How to go about ....it?
Why Magdlr ? CLK not enough to install jb. ?
Plz explain ...
Sent from my HD2 using xda premium

selvag said:
Hi...
I ve quest ... about nand and native SD.
Im new to jb. Still me using miui GB.2.3.7
My quest is ... for jb install .. Rom partion 380 MB along with SD card 2 Gb extra partition..... ?
I could not understand jb install...do i needs more space ..
How to go about ....it?
Why Magdlr ? CLK not enough to install jb. ?
Plz explain ...
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
I see you have a lots of doubts ... Search one by one ..he he

Me figured out Some stuff ...to install..
planning these processes step by step
1. Using Hd2 tool kit
- wipe with task 29
2. Custom Partition with 380 MB
3. Install Clk.. recovery or extended twrp v2.5.03
4. Install Rom
Here I ve quest in 3rd step ... which one? I should install...
In 4th step do I need to select ext partition 2gb in sdcard or what...
I thing bit confused nand and native SD..
Guide me plz
Thanks
Sent from my HD2 using xda premium

selvag said:
Me figured out Some stuff ...to install..
planning these processes step by step
1. Using Hd2 tool kit
- wipe with task 29
2. Custom Partition with 380 MB
3. Install Clk.. recovery or extended twrp v2.5.03
4. Install Rom
Here I ve quest in 3rd step ... which one? I should install...
In 4th step do I need to select ext partition 2gb in sdcard or what...
I thing bit confused nand and native SD..
Guide me plz
Thanks
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
You need to search and read, these questions are not for development thread.
Sent from my HTC HD2 using Tapatalk 2

Hi! I have installed this ROM but it is very laggy. I did every step it was need:
-bootloader: MAGLDR
-system partition size: 400mb
-ext4 partition size:1GB
-method: dataonext
-yes,i flashed it properly
-yes i fixed permissions after first boot

Hi all,
Some days ago I bought a HD2 with Windows Mobile and today I managed to flash MIUI on it. Everything seems to work flawlessly except for the internet connection. No data (H in the status bar is displayed) and no Wifi connection (it gets stuck at "obtaining IP address"). But I can receive and make calls and the SIM card works in my Xperia Z (I use it with an µSIM -> SIM adapter, but this works in my G1 ).
So what do I do wrong? APN is also correct...
Thanks in advance,
Lunch
PS: I have already tried #7 out of this thread:
http://forum.xda-developers.com/showthread.php?p=10433749#post10433749 (7th)
And another SIM card shows exactly the same problem.
EDIT2: after this I flashed another ROM (NexusHD2) and all mobile data related issues are gone.

Lunchbox115 said:
Hi all,
Some days ago I bought a HD2 with Windows Mobile and today I managed to flash MIUI on it. Everything seems to work flawlessly except for the internet connection. No data (H in the status bar is displayed) and no Wifi connection (it gets stuck at "obtaining IP address"). But I can receive and make calls and the SIM card works in my Xperia Z (I use it with an µSIM -> SIM adapter, but this works in my G1 ).
So what do I do wrong? APN is also correct...
Thanks in advance,
Lunch
PS: I have already tried #7 out of this thread:
http://forum.xda-developers.com/showthread.php?p=10433749#post10433749 (7th)
And another SIM card shows exactly the same problem.
EDIT2: after this I flashed another ROM (NexusHD2) and all mobile data related issues are gone.
Click to expand...
Click to collapse
Hi Lunch,
I met the same problem with a certain Android ROM. What I did to solve it, is remove every WiFi connection it detected and added them again manually which gave me the possibilty to enter the key of the Router. After that WiFi worked without any probs. Maybe this will work for you too!!
kindest regards, Kuzibri

Thank you, maybe I'll try MIUI once again and I'll look through it.

Any answer for softkey power button
Refer to my previous post, Any answer for softkey power button???

cant boot this rom after instllation ( dataonext)
Hi
it is more than 3 days i am searching and flashing this rom, (almost 10 times) but what ever i do i stuck at loading screen (MI XIAOMI.com)
i followed this guide http://forum.xda-developers.com/show...5#post25781675
except i copied the chief guides from here (370 mb system and ...)
i have 512 hd2 and i installed this with these options
DataOnExt( i manually partitioned my sd with mini tool and created ext4 partition)
plz guide me
thanks

GPS problem and SOD on lock screen
I installed this rom (current ver 3.4.19) and all in all I think it is best HD2 Android ROM on JellyBean 4.1.2.
One problem exist since first 4.1.2 release of this rom (gtbluesky on miui.com). It is a GPS problem, that seems unsolved yet. It is difficult to search original forums on miui.com for solution, because of chinese, of which I dont understand any word.
Anyway, I'm sure that all freezes I have had are due to this particular gps isssue, because phone freezes with SOD only while in sleep (lock screen), and I think it is because one of the app (system or user) trying to get GPS data freezes the phone and lock screen is then locked for sure with famous black screen of death with only hard key's light on.
I came to this conclusion because I installed app "GPS status" from market and tried forceing gps just to test my phone GPS radio. After launching, app waited (as usual for gps apps depending on my location, satelites position, gps cacche etc) and finally when gps was captured with correct data, then freezed the phone leaving me with no other option but to reset the phone with pulling out the battery.
I repeated this several times and got freezed almost every time.
Google maps freezes phone also, as soon as location is fetched from satelites, not from AGPS.
If anyone noticed this, or had this same problem, please post some advice or solution how to fix this.
My HD2 is:
MIUI 3.4.19 with DataOnExt
bootloader: MAGLDR
recovery: cwm
memory: 512 (EU)
SYS partition: 370 MB
cache partition: 5MB
SD card : SanDisk 16Mb class 4
ext4 partition: 2048

Hey there guys. I recently installed this ROM and everything works fine, didn't have any major problems. The only thing that bothered me was the camera, as it was a bit buggy. So I then decieded to use the one from my Titanium Backup (from a previous rom installation). It worked just fine.
Yesterday I wanted to take a picture and the camera icon was gone. If anything both were gone, by that I mean that after the ROM install there were two camera icons (before the TB one). I retried to restore the one from TB, to no avail. I just wanna know what the problem is, or should I just install a camera from the Playstore? Thanks for a wonderful ROM!:good:
My Install details are as follows:
MIUI 3.5.3 with DataOnExt
Bootloader: MAGLDR
Recovery: CWM
Ext4 partition: 4GB
Swap size: 256mb
Memory: 512 (International)
SYS partition: 380 MB with 5mb cache
SD card: SanDisk 16GB Class 10

[ROM] [NIGHTLY] [JB] [4.3] CyanogenMod 10.2 nightlies

{
"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"
}
Welcome to the unofficial CyanogenMod 10.2 nightlies​
The releases will co-inside and the build start time is at 03:01 UTC every night and should be uploaded soon after. If at anytime the builds are not there, then there was a problem building the ROM, and we will have a look at it ASAP.
Buildbot resources are needed for newer builds. Please upgrade to CyanogenMod 11
http://forum.xda-developers.com/showthread.php?t=2542353
These builds are compiled from the latest CyanogenMod repos and device repos on device, kernel and vendor files and are based on the awesome work by jcsullins, Dorregaray, flintman and drmarble.
Attention: REPARTITIONING REQUIRED.
Jellybean 4.3 takes up a tad more space than 400mb. Resizing your system partition to 500mb is advised. Also, this build is a datamedia build - this means that we utilise an emulated sdcard on the data partition and both share the same partition thus space. Yet, the sdcard partition is also mounted and can be used for file usage (deprecated). Resizing the sdcard partition (/dev/media) to a rather small size and allocating the remaining size to /data is recommended.
What is datamedia? Click here.
Advised partition layout:
system - 500mb
cache - 200mb
media - 400mb
data - [remaining space] (i.e. ~11.5gb for 16gb TouchPads)
easiest way to resize partitions is by using tailor in webOS (install with preware et al)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Datamedia CWM required to properly support emulated sdcard storage in 4.3
Download
Click to expand...
Click to collapse
Click to expand...
Click to collapse
And as always: I take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, dead kittens, etc.
Download builds here
Click to expand...
Click to collapse
Download Google Apps
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changes
Upstream changes
Devicetree commits
Kernel commits
Wifi driver commits
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Issues
Issuetracker
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Thanks/Credits
Click to expand...
Click to collapse
James Sullins (jcsullins) - for his awesome work on the TouchPad
Tomasz Rostanski (Dorregaray) - for his work on many parts on Android for the TouchPad (esp. camera)
David R. Marble (drmarble) - for supporting the CM10.1/CM10.2 port, many great ideas and sdcard partition mounting with the new fstab
William Bellavance (flintman) - for getting around mr2 quirks of audio and wifi, further development and fixes
Arne Coucheron (arco) - for his work on the legacy QC userspace drivers
Erik Hardesty (Erik Hardesty) - for the initial kernel work
eyeballer, verygreen and all other TP Devs - for their innovative and collaborative work
Steve Kondik (cyanogen) - for starting this great project
Google - for an awesome OS
Let me know if i omitted you and i will add you here asap
IRC channel
Click to expand...
Click to collapse
Visit us in #cyanogenmod-touchpad (general) or #cyanogenmod-dev (only dev related talk) on freenode

Known bugs / caveats:
wifi turns off in suspend -> uncheck "wifi optimisation" in advanced wifi settings
camera aspect ratio

Great!
Looking forward for the latest and greatest on our beloved Touchpad :fingers-crossed: !

Maybe it's a silly question but what is the difference between this rom and evervolv ?

Can't wait to give this a shot! Thanks for the continued development
EDIT: Quick question, is it possible to completely remove WebOS and use just this?

maxexcloo said:
Can't wait to give this a shot! Thanks for the continued development
EDIT: Quick question, is it possible to completely remove WebOS and use just this?
Click to expand...
Click to collapse
Are you sure you want to remove WebOS? Cause I think if you'll do this and if your TP will be bricked you won't be able to unbrick it via WebOS Doctor and/or WebOS system.

Awesome!!
Now how does one go about repartitioning?

Is this already Tablet UI, or will it need to be patched?

GnatGoSplat said:
Is this already Tablet UI, or will it need to be patched?
Click to expand...
Click to collapse
Datamedia CWM required
e.g. http://goo.im/devs/milaq/tenderloin/...a_20130903.zip
Located at top..

airtower said:
Awesome!!
Now how does one go about repartitioning?
Click to expand...
Click to collapse
you can boot into webos and use tailor. thats by far the easiest method.
will also include a hint to it in the first post.

Awesome CM10.2 Nightly Builds!
Awesome CM10.2 Nightly Builds! I notice that you are recommending a larger partition size for this Rom. 500MB vs ACME3's 400MB, time for ACME4? I may need to make a little video about using tailor to help get the ball rolling. Perhaps I should try cutting down the size of the gapps package too, hmmmm. Time for testing, Thank you Milaq!

Camera launcher
Focal wouldn't connect to a camera. I tried a NEXUS 7 camera launcher and that wouldn't work. Is there a recommended camera launcher?

the build runs very smooth, much smoother than the 10.1 builds.
i enlarged the partition size as recommended from 400 to 500 mb using webOS' tailor.
what about the other recommendations concerning the datamedia build?
when i open tailor i see the following partitions with their corresponding size:
USB (media): 25.336 GiB
Android (system): 512 MiB
Android (cache): 200 MiB
Android (data): 1.5 GiB
Unused Space: none
do you mean to reallocate the space to Android (data)?

So once we repartition appropriately and flash datamedia CWM (presumably via a dd command?), we're good to flash the build straight away? No ACME necessary?

airtower said:
So once we repartition appropriately and flash datamedia CWM (presumably via a dd command?), we're good to flash the build straight away? No ACME necessary?
Click to expand...
Click to collapse
no acme necessary!
- repartition
- wipe data
- flash datamedia cwm
- flash 10.2
- flash gapps
that's the way it worked for me

Gapps Mod and Media removal
Hey Guys,
So I reduced the size of the gapps package by removing the optional face-lock stuff, Google+ and Quick Search. Both of those apps are rather large and can be installed from the Play Store.
Download update-gapps-jb-lite-20130813-signed.zip(55.52MB):
This leaves me with a System storage size of 22.79/394MB
Then I did this...
How to monitor free System Storage space(Optional):
-You can use a free app,Quick System Info PRO, to check the size of your partitions and remaining free space, it should be = 387MB or 402MB. Either of these is acceptable and indicates that the ACMEInstaller3 worked correctly.
-Having a system size of 387Mib = 400MB and is perfectly normal after using ACME3
-Users report having a size of 394 after flashing to a new Rom. This is also acceptable.
-If your partition is an odd size or you get random reboots,then you may have encountered problems due to flashing you Rom.
Quick System Info PRO Video Link:
Quick System Info PRO Play Store Link:
How to free up System Storage space on the HP TouchPad(Optional):
I believe I have located about 15.89MB of data we can safely delete. Android in space videos and Phone Ring tones are located @
root/system/media/videos & root/system/media/audio/ring tones.
X-plore File Manager, use this app to delete the files:
Note* X-plore needs to be given Root Permissions by clicking the 3 dots in the corner and choosing configuration. Here check your Root Access settings. SuperUser + Mount Writable, this is what it should say. Next you may need to reboot before it takes effect.
Now I have a System storage size of 38.73/394MB.
I hope this helps people get it installed. Its running very well for me. The audio has been playing with the screen off. I have a low battery drain or -6ma with deep sleep so far, Stats still being generated. Looking like a great first build! :good::good:
Note: I just tested attached the TouchPad via the USB cable. It now shows both Internal Storage and the SDcard, very interesting! See the screenshot below.
Note: Here is a great thread that talks about using Tailor
How to guide for changing your system, data, and cache partition sizes(how to use Tailor): (Gradular)

ok but how to resize partitions??? Tailor installed buy no instruction
ok...by myself
1)Mount Android (system) partition
2) Check filesystem
3)resize

milaq said:
Known bugs / caveats:
wifi turns off in suspend -> uncheck "wifi optimisation" in advanced wifi settings
ui sounds not playing
wifi region code does not stick
buzzing noise audio on suspend -> toggle (non-working) bluetooth once
no bluetooth
camera aspect ratio
Click to expand...
Click to collapse
Just a few observations, the WiFi region codes have not stuck since the first CM10 the best I can remember. This is not even available on non-rooted my Samsung GS3 or Asus Infinity. Wonder if it works on rooted ones? I don't believe CM9 or 7 even had that feature.
What are UI sounds?
I don't believe WiFi turning off when one suspends(turns off) the screen is a bug. WiFi optimization is a feature added by the CM guys as a power saving feature. That is why unchecking WiFi optimization corrects the issue, ie. turns off the power saving feature.
I think I read over on Evervolv's thread that he finally got a working Rom that fixed the "buzzing noise audio on suspend ".
Why are you pushing this emulated SD card that requires all this repartitioning and using the datamedia CWM instead of doing it the traditional way it's been done over all the previous versions of CM on the TouchPad? I remember you doing a poll and best I remember, you did not get that much interest in the idea. You might want to consider a traditional build that does not require all the "hoop jumping" to get it installed and save all the fancy stuff for the more technically adept.
It's your Rom and you do it the way you want. But I suspect that you won't get the same interest from the average users with all this technical stuff that has to be done to get it working. I'm also with Roland on his idea for a new ACMEInstaller4 to set the /system partition to the correct size. And just a reminder, sometime in the not too distant future, HP is going to take down the WebOS servers, so unless one is prepared for that eventually, installing Preware and Tailor may not be possible unless one already has it installed or has prepared for life after HP support.
I also seem to remember reading somewhere, either on Evervolv's thread or on Rootzwiki that unless a newer 3.XXX kernel gets finished, that JB 4.3 on the TouchPad may not be completely feasible for various reasons.
Update: Found the post from Dr. Marble:
" I admit that I am not convinced it is worth running cm10.2. It is fun to make it work but I don't really see any advantages over 10.1 for what I do. Our kernel doesn't support fstrim. I don't use or really understand selinux. The sound is still flakey. I will keep working on it but I really think we are maxed out at cm10.1"
Maybe getting BT working on the CM10.1 nightlys and squashing any remaining bugs would be a more fruitful endeavour.
You know the work you guys do is awesome. What you have managed to get running on our lowly HP TouchPad rivals many other dedicated Android tablets in speed and stability. I recently purchased an Asus TF700T Infinity, OTA'ed it to Android 4.2.1(the latest update from Asus) and have been comparing various apps and functions side by side with my TouchPads, yes I have two. And I can honestly say that the Infinity is only marginally faster in certain areas and the TouchPads keep up with it nicely in most others. The only advantages I have with the Infinity is a new device, quad core processor, 12 core video and for now a warranty. I'm not going to unlock or root it for now.
With all that said, we may finally be seeing the sunset of our orphaned device. It's two and one half years old, we don't know how much longer the batteries in them are going to last, they have to be getting worn out. They are a pain it the ass to change. No one seems to be able to get a newer kernel built for it. The A6 firmware and bricking issues are always lurking to jump up and bite when least expected. Of those users that are still hanging on, many are not happy unless there is some kind of bleeding edge development going on and when there isn't, they start whining about ETA's. How much longer can you keep the hounds from nipping at your heels, or even want to?
I hope none of you take this as a negative statement or a big whine. I think I am just stating the obvious. Technology and innovation moves on and the TouchPad is not going to be able to keep up much longer. My hedge against that is my recent purchase of the TF700. I may even eventually sell my TouchPads before they are unsellable, ie. dead battery or something else going wrong. Who knows, they may last a couple of years, or only to next week.
Comments invited, flaming is not.
---------- Post added at 04:19 PM ---------- Previous post was at 04:10 PM ----------
RolandDeschain79 said:
Hey Guys,
So I reduced the size of the gapps package by removing the optional face-lock stuff, Google+ and Quick Search. Both of those apps are rather large and can be installed from the Play Store.
Download update-gapps-jb-lite-20130813-signed.zip(55.52MB):
This leaves me with a System storage size of 22.79/394MB
Then I did this...
How to monitor free System Storage space(Optional):
-You can use a free app,Quick System Info PRO, to check the size of your partitions and remaining free space, it should be = 387MB or 402MB. Either of these is acceptable and indicates that the ACMEInstaller3 worked correctly.
-Having a system size of 387Mib = 400MB and is perfectly normal after using ACME3
-Users report having a size of 394 after flashing to a new Rom. This is also acceptable.
-If your partition is an odd size or you get random reboots,then you may have encountered problems due to flashing you Rom.
Quick System Info PRO Video Link:
Quick System Info PRO Play Store Link:
How to free up System Storage space on the HP TouchPad(Optional):
I believe I have located about 15.89MB of data we can safely delete. Android in space videos and Phone Ring tones are located @
root/system/media/videos & root/system/media/audio/ring tones.
X-plore File Manager, use this app to delete the files:
Note* X-plore needs to be given Root Permissions by clicking the 3 dots in the corner and choosing configuration. Here check your Root Access settings. SuperUser + Mount Writable, this is what it should say. Next you may need to reboot before it takes effect.
Now I have a System storage size of 38.73/394MB.
I hope this helps people get it installed. Its running very well for me. The audio has been playing with the screen off. I have a low battery drain or -6ma with deep sleep so far, Stats still being generated. Looking like a great first build! :good::good:
Note: I just tested attached the TouchPad via the USB cable. It now shows both Internal Storage and the SDcard, very interesting! See the screenshot below.
Note: Here is a great thread that talks about using Tailor
How to guide for changing your system, data, and cache partition sizes(how to use Tailor): (Gradular)
Click to expand...
Click to collapse
Did you resize your partitions using Tailor?

Oooooo, looks like I have something to do tonight. Awesome.