Hello, I am trying to dual boot Sense 3.5( and MyTouch4G ROM on my HTC HD2, the problem that I am having is that when I try to boot the the SD ROM it gets to the boot logo and then after 5 minutes or so it boots to Sense 3.5 ROM.
Device's/Software Being Used -
Windows 8 PC
Australian (512mb) HTC HD2
Original HTC HD2 Charging/Data Cord
MAGLDR
Sense 3.5 - http://forum.xda-developers.com/showthread.php?t=1316632
MyTouch4g SD ROM - http://forum.xda-developers.com/showthread.php?t=1220151
Boot_Magldr.rar - Post 3 MyTouch ROM
Here are the steps that I have used to copy the ROM to my SD card
1.Download the Part 1 and Part 2.rar files and put them on my desktop.
2.Opened Part 1.rar and open the folder "BOXMAX.GTS.V3.0" and then opened the folder called "Android" and copied to SD
3.Opened Part 2.rar and copied files to the SAME Android folder on SD Card. When asked if I want to overwrite files I press no.
4. Open Boot_Magldr.rar and copied files to the SAME Android folder on SD Card. When Asked if I want to overwrite file I press yes.
5. Turn of HTC HD2 (512mb)
6. Boot To MAGLDR and do these steps
1. Go to Services
2. Go to Boot Settings
3. Go to AD SD Dir
4. Select Android folder
5. Select Boot AD SD
7. Wait for 4-5 minutes
8. Starts to boot to NAND ROM
9. Boots to NAND ROM
10. I reboot to try again
11. Repeat steps 8 (part 5) to 8
12. BOOT LOOP
Please Help, I will/have tried to be as descriptive as possible
-Redsn0wier
I think it's to do with the same kernel being used for the NAND and SD builds. I haven't read much about it but earlier there was a thread in the Q&A in which a dev explained it (think it was 3dak) and you're going to have to use another build with an SD kernel such as Hastarin 8.6
Nigeldg said:
I think it's to do with the same kernel being used for the NAND and SD builds. I haven't read much about it but earlier there was a thread in the Q&A in which a dev explained it (think it was 3dak) and you're going to have to use another build with an SD kernel such as Hastarin 8.6
Click to expand...
Click to collapse
Now how exactly do I do that?
some of the SD build booting will be influenced by NAND build
maybe you can ask the chief about your system. But I think you can verify this by empty your nand, then see if the SD build gets normal.
sadfrog_lin said:
some of the SD build booting will be influenced by NAND build
maybe you can ask the chief about your system. But I think you can verify this by empty your nand, then see if the SD build gets normal.
Click to expand...
Click to collapse
Not much point, this is pretty much certainly your issue. And OP, just use a different build
Nigeldg said:
Not much point, this is pretty much certainly your issue. And OP, just use a different build
Click to expand...
Click to collapse
Another build of the Glacier ROM, what one would you recommend, I'm so new to the HTC HD2 stuff its so different for the Motorola Atrix
Redsn0wier said:
Another build of the Glacier ROM, what one would you recommend, I'm so new to the HTC HD2 stuff its so different for the Motorola Atrix
Click to expand...
Click to collapse
No, another ROM completely is what I meant, such as MCCM's or something. Dunno what the good SD builds are now but MCCM's used to be the best. However, if you look through the changelog for the glacier ROM and see that the kernel was changed somewhere, try using that older version with the different kernel and see if it works.
Also, a bit off topic but how good is the Atrix? My friend is getting one and he wants to know if it's a good choice, he probably won't flash anything to it though.
Related
Ok so here is my issue,
I recently installed MAGDLR and got Stock Desire ROm running and everything is perfect until I found out that I am unable to run my android ROMS from the SD card!
From the MAGDLR bootloader, i press on boot android from SD = nothing happens.
I realized that maybe haret.exe needs 2 be on the SD card root. So i moved the files.
The bootloader detects the files and boots into Android from SD but then gets stuck at the custom bootloader image of the android ROMS
Tried different ROMS but in vain.
Eversince I installed MAGDLR, I am completely unable of running any ROM from SD.
Does anyone have the same issue or is it only me?
I feel there is a very simple thing I missed and I will feel like an idiot once I know lol.
Any suggestions? I really like testing different ROMS.
Me too, i tried the MIUI ROM from SD (normal rom version) and stucked at MIUI bootloader image.
byl233 said:
Me too, i tried the MIUI ROM from SD (normal rom version) and stucked at MIUI bootloader image.
Click to expand...
Click to collapse
Did u move ur system files from folder "Android" to the root of the card like I did?
Or was haret.exe already in the root of ur card by default?
I am thinking that this file moving might have caused this
I'm not sure you need to move your files. You can actually configure the Android directory in magldr's settings.
I'm not sure current SD builds are that compatible with being launched from magldr, though. First thing I tried after installing magldr was launching my old m-deejay DesireHD build, but it would just freeze immediately after displaying "preparing sd-card".
meptik said:
I'm not sure you need to move your files. You can actually configure the Android directory in magldr's settings.
I'm not sure current SD builds are that compatible with being launched from magldr, though. First thing I tried after installing magldr was launching my old m-deejay DesireHD build, but it would just freeze immediately after displaying "preparing sd-card".
Click to expand...
Click to collapse
ya seems like old SD android ROMS are not compatible with MAGDLR. I thought they would be
Does anyone know what we or the devs can do to resolve this? My builds on SD also freeze at preparing SD card.
Sent from my HTC HD2 using XDA App
jimhaddon said:
Does anyone know what we or the devs can do to resolve this? My builds on SD also freeze at preparing SD card.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
AFAIK magdlr cant read the required settings over the startup.txt still, but it would, read the first post over the magdlr thread by cotulla, it would even load wm6.5 and wp7 builds over NAND! its a matter of time (and patience )
jimhaddon said:
Does anyone know what we or the devs can do to resolve this? My builds on SD also freeze at preparing SD card.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Same here, I installed Mgrldr 1.11 in order to use MDJ nand hd superlight 2.2, but nand is today and at this point too..... Experimental !!!!! to be use daily.
I manage to load my "OLD !" SD Android, but it stucks on homescreen while charging SD card, very frustrating...
HD2 T9193 Australia
512Kb Flash Memory
SPL-2.08.HSPL CotullaHSPL
ROM Energy Leo 29007 Sense 2.5 Jan 24
Radio 2.15.50.14
Over last few days, have download several SD builds of Android.
I Copy the android folder to root of SD card
I start the phone in Windows Mobile
I run CLRCAD
I run HARET
I get the grey window about starting/booting (cant remember exact, head spinning)
then get black screen with small writing
then get HTC splash screen and thats it.
each build I have tried, have left at boot screen from 60 to 90 minutes.
Now, 6 months ago with earlier version of Energy ROM, and different radio, I could load earlier version of SD Android.
Today I had a friend around, with an older radio and the same earlier version of energy rom that I used to have, and still no go on his.
What is happening (or not).
Do I need to have an EXT2/2/4 partition on my SD Card?
Something more simple??
Ideally, I wanted to try a Desire HD Sense ROM.
Have tried
CopesHD2GingCyan7Release1
Core_Droid_HD_V0.4_Release_Version
mattcleofroyo1.8
MDJ_FroYo_HD_v._4.6_MDJ_S78.0
NexusHD2-FRG83D_V1.8_(Froyo 2.2.1)
SuperRAM_FroYo_V1.5
Moby58 said:
HD2 T9193 Australia
512Kb Flash Memory
SPL-2.08.HSPL CotullaHSPL
ROM Energy Leo 29007 Sense 2.5 Jan 24
Radio 2.15.50.14
Over last few days, have download several SD builds of Android.
I Copy the android folder to root of SD card
I start the phone in Windows Mobile
I run CLRCAD
I run HARET
I get the grey window about starting/booting (cant remember exact, head spinning)
then get black screen with small writing
then get HTC splash screen and thats it.
each build I have tried, have left at boot screen from 60 to 90 minutes.
Now, 6 months ago with earlier version of Energy ROM, and different radio, I could load earlier version of SD Android.
Today I had a friend around, with an older radio and the same earlier version of energy rom that I used to have, and still no go on his.
What is happening (or not).
Do I need to have an EXT2/2/4 partition on my SD Card?
Something more simple??
Ideally, I wanted to try a Desire HD Sense ROM.
Have tried
CopesHD2GingCyan7Release1
Core_Droid_HD_V0.4_Release_Version
mattcleofroyo1.8
MDJ_FroYo_HD_v._4.6_MDJ_S78.0
NexusHD2-FRG83D_V1.8_(Froyo 2.2.1)
SuperRAM_FroYo_V1.5
Click to expand...
Click to collapse
Have you tried putting a blank data.img file on the sd card before the boot?
If not try that, they are usually available from the first post in the builds thread.
A few I tried wouldn't boot the first time unless I put that file in there.
I'm guessing it won't help, because some (if not all) of those builds can create a blank one for you, but it won't hurt to try.
This is the one from MDJ's 4.6 build you have tried. The link is from his thread. Extract the file using 7zip and stick it in the android folder.
http://www.multiupload.com/BJ2FXF9IRM
There's no need for partitioning or any kind of fancy stuff for running a simple WinMo6.5/Android dualboot. I suppose formatting your SD card (do it in WinMo, seems to be more effective) should solve your problems.
@MattOG: The data.img helps shortening the first boot time, I've never heard it actually fixes problems?
MattOG said:
Have you tried putting a blank data.img file on the sd card before the boot?
If not try that, they are usually available from the first post in the builds thread.
A few I tried wouldn't boot the first time unless I put that file in there.
I'm guessing it won't help, because some (if not all) of those builds can create a blank one for you, but it won't hurt to try.
This is the one from MDJ's 4.6 build you have tried. The link is from his thread. Extract the file using 7zip and stick it in the android folder.
http://www.multiupload.com/BJ2FXF9IRM
Click to expand...
Click to collapse
Thanks, tried the blank data.img, both the 512Mb and 1Gig.... no go
MattOG said:
Have you tried putting a blank data.img file on the sd card before the boot?
If not try that, they are usually available from the first post in the builds thread.
A few I tried wouldn't boot the first time unless I put that file in there.
I'm guessing it won't help, because some (if not all) of those builds can create a blank one for you, but it won't hurt to try.
This is the one from MDJ's 4.6 build you have tried. The link is from his thread. Extract the file using 7zip and stick it in the android folder.
http://www.multiupload.com/BJ2FXF9IRM
Click to expand...
Click to collapse
Why
do
you
write
like
this?
You do have enough free space on your card for it to create the data.img right??
conantroutman said:
You do have enough free space on your card for it to create the data.img right??
Click to expand...
Click to collapse
Hope so, 8gig card with just the android folder
ok thats not it then........
The only thing I can think to suggest is to try a different WM ROM... see if you can find the energy rom you used before from the energy archives....
It's my thought process. Did I offend your eyes?
Sent from my HD2 NANDroid using XDA App
conantroutman said:
ok thats not it then........
The only thing I can think to suggest is to try a different WM ROM... see if you can find the energy rom you used before from the energy archives....
Click to expand...
Click to collapse
Tried that with the mate's HD2, as it has the same, older energy rom that I used before
is it supposed to take more than 2 hours?
No.
Something must of went wrong.
Can you explain the steps you did?
i extracted to sd card
took out the usb cable
went in my storage card, opened the folder
clicked on clrcad
clicked on haret and started the load
now its reading
acr=### fl=####raac=##
The first i've tried took me about 1h, but I had to install everything Mgldr, CWM, etc. ..
Are you installing SD version or nand?
johnnyboy8707 said:
i extracted to sd card
took out the usb cable
went in my storage card, opened the folder
clicked on clrcad
clicked on haret and started the load
now its reading
acr=### fl=####raac=##
Click to expand...
Click to collapse
Sent from my HD2 using XDA App
what is rootfs?
lozonw said:
Are you installing SD version or nand?
Sent from my HD2 using XDA App
Click to expand...
Click to collapse
im pretty sure my sd card, i went through it to click HaRET
Which rom did you download or trying to install?
I haven't done sd version since nand was released.
Do you need to use windows at all?
johnnyboy8707 said:
im pretty sure my sd card, i went through it to click HaRET
Click to expand...
Click to collapse
lozonw said:
Which rom did you download or trying to install?
I haven't done sd version since nand was released.
Do you need to use windows at all?
Click to expand...
Click to collapse
ive tried shubCRAFT_v1.5_STOCK.rar
and ive tried HyperDroidV1.5.zip
Can you link me the way you did it maybe a quick step guide and a file download pleasE?
It's not supposed to take more than 2 hours, 20 mins max.
Try either of the following, a combination, or all of the following:
format your sd
rextract the android folder form the build you downloaded, into the root of your sd card
Try a different blank data image (if the build requires you to have a data image in there, some builds make their own)
If it's the case of where it makes its own, go into the android folder and delete that incomplete data image
Is it just the build you are using now that doesn't work, or does every other build give you the same problem?
Maybe you need HSPL installed, iunno
You got the latest radio?
Tried a different winmo rom?
Try reading thru this.
http://forum.xda-developers.com/showthread.php?t=881958
Kailkti said:
It's not supposed to take more than 2 hours, 20 mins max.
Try either of the following, a combination, or all of the following:
format your sd
rextract the android folder form the build you downloaded, into the root of your sd card
Try a different blank data image (if the build requires you to have a data image in there, some builds make their own)
If it's the case of where it makes its own, go into the android folder and delete that incomplete data image
Is it just the build you are using now that doesn't work, or does every other build give you the same problem?
Maybe you need HSPL installed, iunno
You got the latest radio?
Tried a different winmo rom?
Click to expand...
Click to collapse
ok im sorta lost ill try and make sense of everything, bare with me
how do i download to the root of my sd card? Maybe using nand way would be more easier
latest radio? you got a link for that? how do i check that?
HSPL how would i know if thats installed
Im running 6.5 on the hd2 right now, havent tried anything else except android
Nand is the way if you do not need windows.
Here is a guide by Mskip with links to everything you need.
http://forum.xda-developers.com/showthread.php?t=893948
Here is a link to the ClockworkMod Recovery which will be very helpful.
http://forum.xda-developers.com/showthread.php?t=898913
And here is a link to the rom I use daily, Hyperdroid which is great.
http://forum.xda-developers.com/showthread.php?t=918899
It takes me less than 30 minutes to go thru all the steps needed.
what does "failed to find rootfs on sd car. you need to unzip a rootfs zip file to the root of your sd card
[REF] A Brief guide to Installing and Maintaining Android [SD/RAM] on HD2 Despy1989 thread.
3) Android Build :
Download your chosen Android build on your computer.
Extract / Unzip the folder on the computer
Now copy into the Root of your SD card.
Folder should be labelled "Android"
Once copied into SD card you will see 2 files: CLRCAD.exe and HaRET.exe which have to be run to boot into Android.
There will also be other folders / files (Android Apps, initrd.gz, system.ext2, rootfs.img, zimage, startup.txt, ts-calibration) please leave them as they are.
QUOTE=johnnyboy8707;11737355]what does "failed to find rootfs on sd car. you need to unzip a rootfs zip file to the root of your sd card[/QUOTE]
Hi, I have just setup dualboot of wp7 and americanandroid sd through magdlr, loving it, but would like to have even more choice, i.e. have more sd builds on my sd card, so can switch between say americanandroid and deshd build. Is that possible? Please advise...
Can I have more than 1 android folder on root of my sd card, e.g. Android1 for americanandroid and Android2 for deshd build, then boot into magdlr, and manually change the android folder under services to the one i want to boot...would that work?
I don't think MAGLDR has such an option built in. If you were using winmo then you could run different android builds off one sd card, but MAGLDR cannot.
Yes it would, you just need to edit the config.txt and change the rel path I think it is, as long as the folders are obviously named differently shouldn't be a problem, been ages since I even touched an SD build!
Kailkti said:
I don't think MAGLDR has such an option built in. If you were using winmo then you could run different android builds off one sd card, but MAGLDR cannot.
Click to expand...
Click to collapse
Like he said if he manually changes the ad SD path each time he wants T9 boot a different build would it not be possible???
Oh okie, sorry about that.
bates_1974 said:
Yes it would, you just need to edit the config.txt and change the rel path I think it is, as long as the folders are obviously named differently shouldn't be a problem, been ages since I even touched an SD build!
Click to expand...
Click to collapse
which config.txt file should i change? where can i find them in sd builds?
lol i know everyone uses nand builds nowadays, but been flashing and reflashing every single day, at least with sd, i can have wp7, cyanogenmod, deshd, and miui all in one, so no more flashing daily or rather hourly lol
kag8 said:
which config.txt file should i change? where can i find them in sd builds?
lol i know everyone uses nand builds nowadays, but been flashing and reflashing every single day, at least with sd, i can have wp7, cyanogenmod, deshd, and miui all in one, so no more flashing daily or rather hourly lol
Click to expand...
Click to collapse
Um let me try think lol.
I think in the folder usually called 'Android' it'll be in there. If you open that there will be a line saying something like rel_path=Android
If you change the folder to say Android1 and make the subsequent change to that in the config.txt it will then know to load all relevant info from that folder. If I was at my pc I'd happily try for you but currently in the local beer garden. Have a go and if no luck I'll look into it tomorrow evening for you after work and pm you all the necessary instructions.
On some buids, it's startup.txt instead of config.txt
Sent from my HTC HD2 using XDA App
huggs said:
On some buids, it's startup.txt instead of config.txt
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
That is most definitely what I was looking for
Is there a possibility that we can have 2 Android OS simultaneously i.e, MAGLDR version & SD Card version..???
If so, is there a bootloader that let's us select the version as we had in the SD card ROMs..???
You can use this
http://forum.xda-developers.com/showthread.php?t=1090783
to install MAGLDR and Clockwork recovery.
Get a CWM NAND ROM and put the rom.zip on your phone's sd card and flash it via Clockwork.
Then get an sd build, extract it to your sd card, and follow all the installation steps in the thread you downloaded it from.
You boot the sd build from the MAGLDR menu by chooding AD SD, but first you must set your sd directory. To do this, in the MAGLDR menu choose Services, BootSettings, then AD SD Dir, and choose the directory of your sd build.
Once you have flashed MAGLDR and CWM, you must hold down the Power button while booting up your phone to get to the MAGLDR menu.
Make sure you flash the right partition size for the ROM you'll be flashing to NAND
huggs said:
You can use this
http://forum.xda-developers.com/showthread.php?t=1090783
to install MAGLDR and Clockwork recovery.
Get a CWM NAND ROM and put the rom.zip on your phone's sd card and flash it via Clockwork.
Then get an sd build, extract it to your sd card, and follow all the installation steps in the thread you downloaded it from.
You boot the sd build from the MAGLDR menu by chooding AD SD, but first you must set your sd directory. To do this, in the MAGLDR menu choose Services, BootSettings, then AD SD Dir, and choose the directory of your sd build.
Once you have flashed MAGLDR and CWM, you must hold down the Power button while booting up your phone to get to the MAGLDR menu.
Make sure you flash the right partition size for the ROM you'll be flashing to NAND
Click to expand...
Click to collapse
Oh, that's great..!!!
Thanks for the help, may be I missed that thread while searching..!!!
Dear all,
I hope nobody minds reactivating thread.
I'm currently trying to install an Android dual boot setup. I installed a NAND Android (TBD SensationXL v2.5) which works already quite well for me. Now I tried to start an SD Android Build via Magldr. But none except ICS Beta 5 starts. All other start showing their Boot splash but phone boots never the less to NAND Android.
Has anyone an Idea, what the problem could be?
Thanks in advance
war_child said:
Dear all,
I hope nobody minds reactivating thread.
I'm currently trying to install an Android dual boot setup. I installed a NAND Android (TBD SensationXL v2.5) which works already quite well for me. Now I tried to start an SD Android Build via Magldr. But none except ICS Beta 5 starts. All other start showing their Boot splash but phone boots never the less to NAND Android.
Has anyone an Idea, what the problem could be?
Thanks in advance
Click to expand...
Click to collapse
Your steps should be as follows
1. Download an SD Android ROM with MAGLDR contents as well
2. Rename folder to whatever you like but the startup.txt MUST have rel_path= same name as folder
3. Place folder on root of SD card
4. Go to Services>AD SD Dir>Desired folder (in MAGLDR)
5. Select 'Boot AD SD' (or whatever the Android SD boot option is)
Oh, and reactivating the thread is infinitely better then starting a new one
Dear Nigeldg,
already did all this.
I'm just wondering why the ICS SD build boots normal while every other tested SD build won't boot
war_child said:
Dear all,
I hope nobody minds reactivating thread.
I'm currently trying to install an Android dual boot setup. I installed a NAND Android (TBD SensationXL v2.5) which works already quite well for me. Now I tried to start an SD Android Build via Magldr. But none except ICS Beta 5 starts. All other start showing their Boot splash but phone boots never the less to NAND Android.
Has anyone an Idea, what the problem could be?
Thanks in advance
Click to expand...
Click to collapse
Same here...
I think the SD ROM is not suitable to Recovery..
I've tried installing SD first, after that i install CWR, n try booting AD SD but got stuck on bootsplash..
war_child said:
Dear Nigeldg,
already did all this.
I'm just wondering why the ICS SD build boots normal while every other tested SD build won't boot
Click to expand...
Click to collapse
Hmm, seems odd. Which other builds have you tried?
Nigeldg said:
Hmm, seems odd. Which other builds have you tried?
Click to expand...
Click to collapse
have tried
http://forum.xda-developers.com/showthread.php?t=1256423
and
http://forum.xda-developers.com/showthread.php?t=957652
OK I think I found the solution in this thread:
http://forum.xda-developers.com/showthread.php?t=1375554
So I now switched to 3dak's Kernel on SD Build and it booted. Then tried to apply glitch fix from this post http://forum.xda-developers.com/showpost.php?p=19025914&postcount=12 I copied files via OI File Manager in system/lib/hw and system/lib/egl but now SD Android hangs at bootscreen.
Due to my postcount I can't as this in the respective thread, so does anyone can give a detailed installation description for this fix as my solution was obviously "suboptimal".