Okay before anyone starts to flame or start saying "Oh God" to the screen, this isnt the typical "When are we going to get Android to boot from HD2" question.
I know we all boot Android from our SDCard, but I went looking to see if there was any google pages on why the sd card? Being that we have an HD2 and it has alot of space (My phone says 768mb free internal storage), would it slow Android and the experience down if we had the "Android" folder copied to our phone instead? I know currently it probably wouldnt work, but being that the avg Android folder is 230mb to 260mb thats more then enough space to put the folder in, and possibly change maybe the daily useage or app installations onto the sdcard. If this was just a general rule of thumb that it was decided to be put on an sdcard across the board because not all phone had the room then is there no way to change that now since most phones are coming out to have larger internal space opposed to older ones?
And again, would it be slower to run this way or not?
AngelDeath said:
Okay before anyone starts to flame or start saying "Oh God" to the screen, this isnt the typical "When are we going to get Android to boot from HD2" question.
I know we all boot Android from our SDCard, but I went looking to see if there was any google pages on why the sd card? Being that we have an HD2 and it has alot of space (My phone says 768mb free internal storage), would it slow Android and the experience down if we had the "Android" folder copied to our phone instead? I know currently it probably wouldnt work, but being that the avg Android folder is 230mb to 260mb thats more then enough space to put the folder in, and possibly change maybe the daily useage or app installations onto the sdcard. If this was just a general rule of thumb that it was decided to be put on an sdcard across the board because not all phone had the room then is there no way to change that now since most phones are coming out to have larger internal space opposed to older ones?
And again, would it be slower to run this way or not?
Click to expand...
Click to collapse
hi
Haret cannot currently read from NAND, its code reads and searches for Data IMG and Rootfs and kernal in SD ONLY .....
hence NAND is so very different from HARET.
well Magldr is what would do the trick
I'm assuming your talking about nand as to boot from the phone like as if you are powering it up and windows loads, Im not actually talking about that. I'm actually talking about how it currently loads, except, instead of placing the Android folder on the SDCard and running clrcad and haret, instead placing the folder into the root directory of the phone and running clrcad and haret from there, same exact way we are running it now, except changing the location of the folder from card to phone.
AngelDeath said:
I'm assuming your talking about nand as to boot from the phone like as if you are powering it up and windows loads, Im not actually talking about that. I'm actually talking about how it currently loads, except, instead of placing the Android folder on the SDCard and running clrcad and haret, instead placing the folder into the root directory of the phone and running clrcad and haret from there, same exact way we are running it now, except changing the location of the folder from card to phone.
Click to expand...
Click to collapse
hi
Well firstly NAND does not necessarly mean booting from start, NAND= Internal memory, in fact cotulla's MAGLDR can boot android of the SD straight from power up whilst having WIN MO on NAND.
So to answer your question again,
HARET CANNOT READ NAND (INTERNAL MEMORY), it always looks for SD for everything , in some cases RAM, as in the new RAM builds that are popping up by devs.
the code for HARET cannot handle NAND at the moment and i dont thing it will ever be implemented.
I'm neither a dev or a hacker, this is just what i ahve understood from reading, i'm open to corrections,
best regds
I have to admit, this idea is very cool.. If haret could "see" the nand memory after WinMo is loaded, then all you need is a WinMo rom stripped down to the maximum and Android folder burned in it (at least the system part). if if if i am not sure, if its technicaly impossible for haret to see the nand memory after booting WinMo or if its impossible at all..
greg17477 said:
I have to admit, this idea is very cool.. If haret could "see" the nand memory after WinMo is loaded, then all you need is a WinMo rom stripped down to the maximum and Android folder burned in it (at least the system part). if if if i am not sure, if its technicaly impossible for haret to see the nand memory after booting WinMo or if its impossible at all..
Click to expand...
Click to collapse
guys remeber HARET is a bootloader for LINUX, its crazy enough its helping us boot android from SD, I think the possible reason HARET is not designed for reading NAND is the potential damage it could do to SPL leading to a BRICK, now we dont want a brick do we ?
mally2 said:
guys remeber HARET is a bootloader for LINUX, its crazy enough its helping us boot android from SD, I think the possible reason HARET is not designed for reading NAND is the potential damage it could do to SPL leading to a BRICK, now we dont want a brick do we ?
Click to expand...
Click to collapse
never say never and expect the unexpected, thats what life teached me
phone wouldnt get bricked if you just read nand, but writing into it could do damage, i agree on this.
OK, so when I first read the OP, I thought he meant booting Haret from the phone's internal storage memory, not NAND.
Though the NAND Haret idea is really not bad, I couldn't see it corrupting the bootloader as long as it behaves the same way as it does from the sd. I mean, the phone is already booted WinMo, so HaRet and Android have no need to touch the bootloader, just as when running from sd. It would be more or less a startup.txt change/ rel_path = NAND/Android (not exact, but general idea). Seems alot different to me from MAGLDR, maybe there is just confusion about this
But if the NAND idea is not workable, wouldn't it be possible to run HaRet Android from the phone's internal storage memory, yielding a performance speed increase and less wear on the sd?
Clearly we couldn't do like I have now, a ton of builds with exceller, all running from internal storage, obviously we don't have 16gb internal. But what about just loading our daily driver from internal, and testing/less commonly builds from sd?
I like the idea because it could mean less wear on the sd, and possibly performance increase
BTW 300th post
Thats exactly what I meant, once WinMo is loaded, we normally go into the sd card thru file explorer and then go to android and then run clrcad and haret, winMo is already loaded and doesnt corrupt winmo, but if we could run the core system from the phones storage space, (Putting the android folder into the main directory, and then running clrcad and haret, this way the core system would load and any user installable files would just end up on the storage card, cause obviously we wouldnt be able to load all our apks into the phone (Some might, others like us go nuts).
But the concept is not a bad one, especially if there was a way when installing the apk's it asked for the location to add.
AngelDeath said:
Thats exactly what I meant, once WinMo is loaded, we normally go into the sd card thru file explorer and then go to android and then run clrcad and haret, winMo is already loaded and doesnt corrupt winmo, but if we could run the core system from the phones storage space, (Putting the android folder into the main directory, and then running clrcad and haret, this way the core system would load and any user installable files would just end up on the storage card, cause obviously we wouldnt be able to load all our apks into the phone (Some might, others like us go nuts).
But the concept is not a bad one, especially if there was a way when installing the apk's it asked for the location to add.
Click to expand...
Click to collapse
I would say that if HaRet was pointed to the correct place correspondingly, either NAND or storage would work as I previously mentioned. I am unsure about any performance gains to be had, but it would surely save on sd card wear.
People say that going from NAND would corrupt bootloader, but since WM is already booted using HaRet, there is no reason that the bootloader is touched, even if it is all stored to NAND. MagLDR is different, that is going for a cold-boot of Android, no WM involved at all. HaRet and MAGLDR work different and I think that if Haret was made to look for /Android in NAND, it could work just the same as if off of sdcard.
And booting from the phone's storage memory would be even safer, as no far-fetched idea of HaRet corrupting the bootloader is even conceivable, as NAND would never even be touched at all.
I honestly believe though that if a version of Haret was released that looked to NAND memory for /Android, that WM chefs could bake lite version WM ROMs with popular Android builds already built into NAND, maybe in the \Windows directory. The chef could even cook in a modified version of Exceller's Android loader which would look to \Windows for the Android folder.
Since Android development is so far along, and there are so many builds that are 100% or near 100% stable, I do think that going this route is a viable option, I mean there are already WM builds that will install an Android build to the sd card all by themselves after you boot them up the first time. This seems a natural progression of that concept to me.
Maybe somebody could contact Netripper, and ask him more about this idea, and see if he would be kind enough to build a HaRet version to look to NaND memory, and another to look to internal storage space, the rest could be done by the end user, as there are WM kitchens available, and most ppl here could make a .cab to install \Android to internal.
That's my $0.02
huggs said:
I would say that if HaRet was pointed to the correct place correspondingly, either NAND or storage would work as I previously mentioned. I am unsure about any performance gains to be had, but it would surely save on sd card wear.
People say that going from NAND would corrupt bootloader, but since WM is already booted using HaRet, there is no reason that the bootloader is touched, even if it is all stored to NAND. MagLDR is different, that is going for a cold-boot of Android, no WM involved at all. HaRet and MAGLDR work different and I think that if Haret was made to look for /Android in NAND, it could work just the same as if off of sdcard.
And booting from the phone's storage memory would be even safer, as no far-fetched idea of HaRet corrupting the bootloader is even conceivable, as NAND would never even be touched at all.
I honestly believe though that if a version of Haret was released that looked to NAND memory for /Android, that WM chefs could bake lite version WM ROMs with popular Android builds already built into NAND, maybe in the \Windows directory. The chef could even cook in a modified version of Exceller's Android loader which would look to \Windows for the Android folder.
Since Android development is so far along, and there are so many builds that are 100% or near 100% stable, I do think that going this route is a viable option, I mean there are already WM builds that will install an Android build to the sd card all by themselves after you boot them up the first time. This seems a natural progression of that concept to me.
Maybe somebody could contact Netripper, and ask him more about this idea, and see if he would be kind enough to build a HaRet version to look to NaND memory, and another to look to internal storage space, the rest could be done by the end user, as there are WM kitchens available, and most ppl here could make a .cab to install \Android to internal.
That's my $0.02
Click to expand...
Click to collapse
Very possible,
Haret needs to be modified for that,
not sure who can do it.
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
greg17477 said:
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
Click to expand...
Click to collapse
spot on
NAND = Internal memory
greg17477 said:
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
Click to expand...
Click to collapse
Well true except the TMOUS, which is 1024 mb, so it should be plenty then to run Android this way right?
Even with just 300 left after WM ROM, Android could still be done conservatively, without much apps installed, or with some kind of a2sd functionality, Froyo has inbuilt app to sd functionality, albeit not as good as a2sd ext2 or ext3 setup.
Guys I think you are missing the point, If this was possible, viable or worth it, it would have probably already been tried and tested and released along time ago.
The fact that this hasnt been done already tells me that its been thought about and rejected for good reason.
PS. NAND ..IS.. Internal memory guys so the running loading of kernel and files from internel memory instead of nand is a moot point.
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
hmmm,
well in that case, kernel could be programed to create Data IMG on SD, if you have been following the Rhodium Nand Project , you will see what i mean, a few components are on NAND and a few on SD
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
Its not about putting the whole Android folder into nand, but for example only the system partition, just like in the RAM builds. All data and user stuff goes to sd.
Btw what do you mean by "...*could* be possible to put Android on internal storage(NOT NAND)." ? nand is the internal storage (memory). Or you guys are using different terms do you mean by "nand" the reseverd space where roms are stored and by "internal storage" the free space left (still in nand)?
TheATHEiST said:
Guys I think you are missing the point, If this was possible, viable or worth it, it would have probably already been tried and tested and released along time ago.
The fact that this hasnt been done already tells me that its been thought about and rejected for good reason.
PS. NAND ..IS.. Internal memory guys so the running loading of kernel and files from internel memory instead of nand is a moot point.
Click to expand...
Click to collapse
Actually your part right, it was tested and released in the initial phases of the Rapheal (aka Fuze) and ran smoothly from what I read, yes there were hiccups, but that was due to the build being still in the alpha stages.
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
This is where your part wrong as well. if you use a pre-set data.img file, yes for the most part you cant use anything larger then possibly 512mb on a TMous, 256 on others, definitely could not use the 1gb img file thats for sure, but the other part of this your missing is that if you dont put a pre-set data.img file, during the initial loading of android, android will create the file itself, and IF I am right the file will be sort of dynamic, dynamic in the sense it will expand as needed, I seriously doubt it shrinks. And on top of this you would then use the function a2sd, which in then would install your apk's to sd card. As of right now how much bigger is your 1gb data.img file that everyone added to their SDCards? Bet still the same size.
mally2 said:
hmmm,
well in that case, kernel could be programed to create Data IMG on SD, if you have been following the Rhodium Nand Project , you will see what i mean, a few components are on NAND and a few on SD
Click to expand...
Click to collapse
Actually after doing some reading, neither the kernel (if I read correctly) nor is haret.exe the cause of pointing the boot location. I did some searching (Mind you I am NOT a LINUX person), but reading some of the files, I am guessing that the key file which controls the loading of Android, is located in the "init" file in the rootfs.img file. I mounted this file in windows to look thru it and view files, and that file seems to have a major role in it, how it works I dont know yet.
To All, please I am not trying to cause a stir here, I am merely looking at possibilities, and unfortunately I cant test them out since I dont have a spare SDCard as of yet (Will ina couple of days, 32GB SDCard for $40, woohoo), and then I have nothing to loose to try, cant brick the phone, since winmo is the default loading OS anyway. One of the reason it might not have been put on the phone as I said, could be speed, I dont know how much faster internal phone storage would be opposed to sd, but another reason why could be cause then the installation would put folders on the root file system of the stroage card and make it messy. Also alot of people constantly flash new builds, this would also hamper your android install being on the phones storage. And remember our normal HD2 roms are between 225 and 250mb stock or custom, where lite versions or stripped down version would be considered better for taking up less space.
One thing to keep note, during all this, I have an HTC Aria (Liberty) as well that I just recently got as an upgrade to one of my ATT lines, and I checked the internal storage of that phone, its stock with ATT's build of Android, and it has ONLY 168mb of storage available, and it came with a 2gb sd card. Now think about that when saying that the files would get to big, obviously the HTC Aria doesnt have anywhere near the capacity of the HD2.
And again to anyone else, let's be clear, yes the phones storage is a NAND, but just to make clear, we aren't talking about doing a cold boot of android, I know how sometimes that can get confusing.
Sorry guys, yes internal storage is NAND memory, the reason I drew a distinction was to make a distinction between loading from internal storage and ROM space. I only meant to illustrate the difference between the two and demonstrate my opinion that both are possible. I think with further investigation and testing, advantages of booting this way will begin to emerge. For example we will be able to remove the sd card while Android runs, not a great benifit, but you get the idea. But yeah, I should have used the term 'ROM Space' instead of NAND, I only meant to show difference between the 2 places to boot from.
Sorry if i caused any confusion.
Sent from my... whatever
Hi all
Since Magldr is out,
I used to think this was possible
WINMO on NAND + MAGLDR running android from SD
So if i wanted winmo i just boot straight into my phone if i want android choose it from MAGLDR and boot straight into it
Am i missing something ...
mally2 said:
Am i missing something ...
Click to expand...
Click to collapse
Actually yeah I thought I remember somewhere you could still use windows on nand and android on sd, or android on nand and sd.
TheATHEiST said:
Actually yeah I thought I remember somewhere you could still use windows on nand and android on sd, or android on nand and sd.
Click to expand...
Click to collapse
EXACTLY ...
its on the wiki page :O
Yeah you're missing something alright.
the MAGLDR enables the ability to load Android from the NAND instead, wiping out WinMo.
Psygnosis84 said:
Yeah you're missing something alright.
the MAGLDR enables the ability to load Android from the NAND instead, wiping out WinMo.
Click to expand...
Click to collapse
yes i know that very well,,,
did you happen to read this
http://htc-linux.org/wiki/index.php?title=Leo/Magldr
may be cotulla can shed light on this
Keeping WinMo and Having direct boot of Android of sdcard sounds good to me. I read in gauners and cotullas builds that sdcard was faster for reads/writes than nand? Did I read that right?
Also, can anyone answer why you can't have both Android and Winmo on Nand dual booting? I am sure there are good reasons, I just don't know what they are? Is it like in a hard drive where you have the 'active' partition?
pablo71 said:
Keeping WinMo and Having direct boot of Android of sdcard sounds good to me. I read in gauners and cotullas builds that sdcard was faster for reads/writes than nand? Did I read that right?
Also, can anyone answer why you can't have both Android and Winmo on Nand dual booting? I am sure there are good reasons, I just don't know what they are? Is it like in a hard drive where you have the 'active' partition?
Click to expand...
Click to collapse
I am perfectly happy with MAGLDR the way it is now,,,
But i was under the impression that WIN mo could be in NAND and Android of SD with MAGLDR we can directly boot android of SD
mally2 said:
But i was under the impression that WIN mo could be in NAND and Android of SD with MAGLDR we can directly boot android of SD
Click to expand...
Click to collapse
Yes, I read that on the wiki that was linked above. I like booting Android off sd, but what has me concerned is people a few people saying that sdcards can only handle about 1000writes per block before they go bad. Not a big deal, but someone also wisely said that 'electronics die at the worst time.'
I would really like to know if this is possible
RUN ANDROID, WP7, AND REG WINMO 6.5 on NAND???????
or at least have some way off keeping WINMO 6.5 while being able to use WP7 AND ANDROID
please no has yet to answer this!
Title says it all
I am wondering that question as well..., how do you access the data/files on ya SD inside Android/NAND Android?
Well there's always file managing apps like Astro, but I'm not sure if it works that way, so, if someone could put kill our question!
Android is Linux based so there should be a similiar command to ls -a where you can see the files and be able to run SD Roms? Or I'm kinda hoping there is..., in SU maybe???
Thanks for the feedback bro, appreciate them.
We just need a response from actual experience; surely trying to run Android off SD wouldn't harm the device in any way.
I don't think we can boot an android build from an android build seeing as how clrcad and haret was build for winmo. >.> but looking at the magdlr notes, if i'm wrong, it has an option to boot android from SD or to boot from NAND, so guess that means you can have an android build in SD and NAND.
NEVER MIND... it failed the second time.
Yes but the build has to be built like a nand build. So you can't just boot the ones you have now.
http://forum.xda-developers.com/showpost.php?p=10202441&postcount=146
buzz killington said:
Yes but the build has to be built like a nand build. So you can't just boot the ones you have now.
http://forum.xda-developers.com/showpost.php?p=10202441&postcount=146
Click to expand...
Click to collapse
I just tried..., I done what I would normally do for an SD Build and used the NAND boot menu to try to run the SD Build. Even though there is an option which says you can run from AD SD..., it doesn't happen.
http://forum.xda-developers.com/showpost.php?p=10202441&postcount=146 <-- This makes sense ( no pun intended )
I understand that a Nand build on SD card will work the same as Nand build on phone, that makes perfect sense.
Question is, is the SD card memory used for application files or will it use up all the memory on my phone like Nand on phone does? Is it possible to use a data.img. Of course, the perfect solution would be to add the option in Magldr (Nand) to boot into recovery so the SD card could be partitioned for files and ext3 for extra application system files like we can with a normal Android phone. Then the need to add another Android rom onto the SD card just for extra storage would not be needed for us European users.
Sent from my HTC HD2 using XDA App
I haven't bothered installing the MAGLDR yet because I am very comfortable with my setup, I have windows mobile 6.5 with android SD, however would it be possible to dual boot Windows Phone 7 with android or Windows Mobile 6.5 on the Nand? Like for the TMOUS1024 devices? I've read on the chinese site for the DFT that its possible but the instructions are very hard to understand. I can't be the only one wondering this or wanting this? Any ideas guys?
I too would love the ability to dual boot, whether it be dual-nand, or WP7 as an SD build (and Android NAND).
Any chance of this happening, devs?
Right now u can dual boot Android NAND and Android SD.
Windows 7 NAND and Android SD but this is too complex. u need to make two partitions on the SD card.
I too would like to still run wm 6.5 as my main os and boot WM7 and Android from my Sd cards. I would also like to know if this is possible.
Is it possible to boot a SD android version via magldr?
Mine freezes if I choose Boot Android SD :/
Using 1.12
kelvin_swe said:
Right now u can dual boot Android NAND and Android SD.
Windows 7 NAND and Android SD but this is too complex. u need to make two partitions on the SD card.
Click to expand...
Click to collapse
I would love to try "Windows 7 NAND and Android SD" even If it is complex. Do have a detailed instruction on how to do this, or know where I can find one?
Thanks.
i think in the future u should be able to dual boot both from nand if u have the 1024leo because the windows phone 7 rom only uses half of the nand
WOOZ!E said:
I would love to try "Windows 7 NAND and Android SD" even If it is complex. Do have a detailed instruction on how to do this, or know where I can find one?
Thanks.
Click to expand...
Click to collapse
darrengladysz wrote a good tutorial explaining that. here is the link to that thread.
http://forum.xda-developers.com/showthread.php?t=913815
Someway of dual booting wm 6.5 and wp7 would be awesome.
Wraith_17 said:
Someway of dual booting wm 6.5 and wp7 would be awesome.
Click to expand...
Click to collapse
Yeah, that's what I'm talking about. Is WP7 only available on NAND?
Hey...
Yeah, darren wrote an excellent tutorial, it`s pretty simple to dual boot with that (the partitioning only takes loooooooong)
http://forum.xda-developers.com/showthread.php?t=913815
I will add the link to a tutorial I made afterwards which includes his tutorial and adds the instruction how to boot Core Droid HD 0.4 as an option for an android build to actually dual boot.
http://forum.xda-developers.com/showpost.php?p=10689007&postcount=1106
I used this build (http://forum.xda-developers.com/showthread.php?t=801607) for over a month and all I can say is that this is the best Desire HD Sense build I've tried!!! (fast and stable)
So enjoy WP7 Nand and Android SD TOGETHER!!!
Greetz
Dom
masondoctorjt said:
I too would like to still run wm 6.5 as my main os and boot WM7 and Android from my Sd cards. I would also like to know if this is possible.
Click to expand...
Click to collapse
thats exactly what i want too, does anyone know if this would be possible?
Dual boot from NAND only
Well, just the question I wanted to ask (OP, not the hijacking posts):
WM 6.5 (or WP7) NAND partition 1, Android partition 2.
At least that's the idea. Two OS's from the faster NAND memory, rather than the slower SD. Only applicable, of course, to the 1024MB version of the HD2. I know this is difficult, but if the chinese are doing it, why can't we ? This would just make this phone more awesome than it already is.
Can anyone answer if this is possible or not, and if not, why?
hondoslack said:
Well, just the question I wanted to ask (OP, not the hijacking posts):
WM 6.5 (or WP7) NAND partition 1, Android partition 2.
At least that's the idea. Two OS's from the faster NAND memory, rather than the slower SD. Only applicable, of course, to the 1024MB version of the HD2. I know this is difficult, but if the chinese are doing it, why can't we ? This would just make this phone more awesome than it already is.
Can anyone answer if this is possible or not, and if not, why?
Click to expand...
Click to collapse
What chinese are doing it? I've never seen 2 OS's both on nand on a phone anywhere... even those cheap chinese fakes that claim to run both wm and android are just running android off the sd.
I, too, hope one day someone makes this possible... but not sure if it will happen or possible yet.
Also, HD2 NAND is not faster than a good quality SD in most cases. You might get a little better random access speed from nand, but if you find a good sd, even that is probably about equal. Even WP7 is now using SD cards as internal memory, now, but you need a good SD card that matches the NAND speed for it to work right. SD Android builds run at the same speed as NAND builds in most cases, but most SD builds aren't updated like NAND builds are.
But anyways, I agree that I would like to see 2 OS's from NAND on our phones.
WOOZ!E said:
I would love to try "Windows 7 NAND and Android SD" even If it is complex. Do have a detailed instruction on how to do this, or know where I can find one?
Thanks.
Click to expand...
Click to collapse
I have a nice tutorial on how to do this. You have to be careful to choose the right SD Android Builds which you can use. There are only a few which are compatibe with SD Magldr. In my thread there are some of the more popular ones which has been converted to work with more coming shortly.
When Nand first came out there were a tutorial which I came across to convert SD Builds into Nand so in theory reversing the process you might be able to convert Nand back to SD and convert that to work with Magldr. It is something I have been wanting to look into for a few weeks now so I might just make it a priority of mine cause any build to dual boot with WP7 would be pretty awesome.
I think its possible, but its difficult because Windows properity OS may conflict with Androids OS so someone would have to configure it so that they both won't conflict with each other.
Thanks for the participation! That chinese bit was mostly to just stir the pot a bit .
Part of the beauty of having WP7 on NAND and Android on SD is that you can have as many Android ROMs as you can fit on your card and you can boot into any of them as you please. But say I want to install Android on NAND. Can I still be able to have that one Android ROM on NAND, but multiple other Android ROM's on SD?
Simple... If I want to be able to boot into more than one OS, must I have WP7 on NAND? If so, is there any guide for this? I cannot find one in the main sticky.
Good question, It would be good if you could switch and chang based on mood.
You can have Android on NAND and as many sd builds as you want, same as with WP7. Until my HD2 broke a few days ago, thats just what II did, a DHD build, a MIUI build, and a CM7 build on sd, with UD on NAND. Just have to choose your AD SD directory in magldr's 'services', and then boot AD SD.
Sent from my T-Mobile myTouch 3G Slide
I do not think you can due to the fact that you have to run the HARET program. It only runs under Windows Mobile as Android does not run .EXE files.
Yes you definitely can. Check my sig
Sent from my T-Mobile myTouch 3G Slide
how_weird said:
I do not think you can due to the fact that you have to run the HARET program. It only runs under Windows Mobile as Android does not run .EXE files.
Click to expand...
Click to collapse
Well, I saw several builds in the NAND Android forum that specify they support MAGLDR. No need for haret. Here's some of them: LeoRCMix, JW MIUI, HardDroid2. So I didn't think that was a limitation.
huggs said:
You can have Android on NAND and as many sd builds as you want, same as with WP7. Until my HD2 broke a few days ago, thats just what II did, a DHD build, a MIUI build, and a CM7 build on sd, with UD on NAND. Just have to choose your AD SD directory in magldr's 'services', and then boot AD SD.
Click to expand...
Click to collapse
How do you partition your card for this setup? Is there a guide somewhere you can link here please? Or is it the same procedure you use to partition your card when you're running WP7 on NAND and Android on SD (which I've followed before)?
Any advise whether NAND build or SD build is better? In terms of performance I mean.
NAND builds will usually be faster.
As far as partitioning your card, with Android it's not necessary, you can do everything on a single Fat32 partition, unless you want to use A2SD then you'll want a single (primary) Fat32 and a single (primary) ext3 or ext4 partition for your apps/dalvik-cache. I recommend using DarkTremor's A2SD script with your NAND ROM, and if you use the DHD build in my sig, then it will automatically detect your ext3 and you'll automatically have the installed apps from your NAND on your sd build.
Sent from my T-Mobile myTouch 3G Slide
sd android builds for magldr will work if you have another android in nand,but the kernel for sd build must not be a nand kernel.for example if you have a sense build in nand and you go to start from sd a build that has tytung r10 or rafpigna kernel the kernel will start but for some strange reason it will load the nand build and not the sd build.then if you go to settings you`ll see that the kernel is changed and you have error wifi because of different kernel modules.this at least happens to me,every time i tried to start a magldr sd build with another android in nand.at first times i thought that i was pushing wrong button on magldr
Great advise, guys. I'm going to play with this soon. Thank you!