Related
Hello guys!
I don't know what to do anymore...
I used to have wm6.5 Hyperdroid1.7(sd) dualboot, but it began to freeze very often to the point where i could't boot it anymore. Since I had hspl2.08 allready installed, I decided to give the relatively new TyphooN CyanogenMod 7 v2.5.2
(http://forum.xda-developers.com/showthread.php?t=933951)
a try.
Long story short, I had lots of problems with the connection but finally made it to
task29: done (used doloops exe)
radio: 2.15.50.14 done
magldr: 1.13 done
ClockworkMod Recovery v1.3 135M System/44M Cache:
installed with DAF.exe
but when I selected 'AD recovery' in magldr it came up with the
1FATAL HIT 1 error. (worked one time when I left the battery out for 25 min, but never again)
So I decided to do everything over again, task29 etc ....
Some problems occured where I had to plug out the phone because it got
stuck in flashing process of task29/radio/magldr.
And now, nothing works, I can flash radio and magldr, but it does'n seem to affect anything. When I boot I just see just the white htc screen.
Tried to flash stock HTC-wm6.5-rom (with both bootloaders) but it gets stuck @ 8% and gives the wrong comand error.
So please help me, 2 days without a phone (so far ...)
daniel
U UNPLUGGED IT!
Try a task29 .. just a task29 with a compatible radio
Once its done go into the bootloader.. if you get this far flash MAGLDR
If and once MAGLDR boots up then your good to go with Android NAND/SD or WP7
Okay,
I task29'ed it with the 2.15... radio and it seemed to work again.
But I flashed with a nand android and when I booted again:
Booting Android from NAND
ANDROID LOAD at numbers
yaffs2 part is /boot
Load zImage
Load initrd.gz
[K] .. numbers
Load done!
1EFATAL HIT 1
*stuck*
may be relevant:
when I flashed the android it did not reboot automatically.
so i pressed the red reset button on the back.
thedangeroiusd said:
Okay,
I task29'ed it with the 2.15... radio and it seemed to work again.
But I flashed with a nand android and when I booted again:
Booting Android from NAND
ANDROID LOAD at numbers
yaffs2 part is /boot
Load zImage
Load initrd.gz
[K] .. numbers
Load done!
1EFATAL HIT 1
*stuck*
may be relevant:
when I flashed the android it did not reboot automatically.
so i pressed the red reset button on the back.
Click to expand...
Click to collapse
That's an android nand issue..prob kernel related... since you used the DFT android flasher it should've restarted... either try again with the same rom or different rom OR use clockwork recovery... i personally use CWM recovery.. since it has more options like installing from zip and backup/restore entire nand build to the sdcard
also note magldr mass storage .. some people say it corrupts transfer so to safe use card reader just incase when transfering
Sent from my HTC HD2 using XDA App
Ok lets try this Remove your SD card Save only necessary files that you need to your computer. Next Format the SD card leave it out.
I would erase the task 29 and MAGLDR and partition and ROM files from your computer and reinstall (possible file corruption)
Do a Task 29
Install MAGLDR 1.13
Once you install MAGLDR let phone reboot and hold power button to boot into MAGLDR
Choose option 5 and load your partition
Next reboot into MAGLDR again and got to option 8 you will want to find wipe data/factory reset and also wipe dalvik cache.
Now if you are flashing via CWM you should have the build on the SD card so now is the time to put SD card back in and reboot into MAGLDR you can then flash the rom. If you are flashing DFT put card back in reboot phone and enter bootloader and flash DFT.
Hope you get it working please read carefully...pm if you are really stuck.
The ONLY thing you are going to flash via MAGLDR option five is your partition...Did you flash the radio via MAGLDR if so that may be your problem?
If that dont work try this:
Try and use a task29 tool provided here http://forum.xda-developers.com/show...3&postcount=19 . Extract it and run it properly ( with phone in bootloader mode ) and perform the task 29. Then flash a radio version which you can find it here http://forum.xda-developers.com/showthread.php?t=611787 . ( I suggest 2.15 )
My suggestion is to go to bootloader-tricoloured screen ( NOT Magldr ). Flash a good radio version and afterwards go back to tricoloured screen of the bootloader in order to flash a Windows Mobile ROM ( preferably a STOCK one ). Forget about NAND ROMs until you will be sure what your problem is.
PS : Read here for more information http://forum.xda-developers.com/showthread.php?t=609477
Dear Friends,
I usually flash ZIP Android using CWM, through menu no.8 in MAGLDR menu. CMW was flashed via USB Flasher menu no.5 in MGLDR menu.
But after several times of failures, I gave up. I hope somebody can inform me what went wrong.
Here is the issue:
After flashing CWM (partition layout) and try to go into recovery mode, the screen says:
"ANDROID LOAD RAW
ERROR: ERROR: Cannot read kernel image"
I tried so many attempts but always like that. I did task 29, reflashing MAGLDR, radio, I even tried to go back to Winmo and back again to reflash HSPL 2.08 and so on. But no luck
I remember that this happen after I tried flashing CWM using SD Card method (via menu no.2 in MAGLDR). If I used this method, I can go into recovery mode. I dont like this method, because I never succeeded flashing ZIP ANdroid using this method. That is why I want to go back to recovery mode via menu no.8 in MAGLDR.
Is the problem related with what i did (flashing CWM via SD Card method)? Is the NAND is damaged?
Is there a way to solve that?
Many thanks in advance
silverwind said:
After flashing CWM (partition layout)
Click to expand...
Click to collapse
what are the contents of flash.cfg? (you can open that file in notepad)
samsamuel said:
what are the contents of flash.cfg? (you can open that file in notepad)
Click to expand...
Click to collapse
Which one? is it the one with CWM partitioner lay out?
This one was flashed when I tried to flash: Ultimate Droid v.3.1.1.v2:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 30M
userdata ya|asize|hr allsize
And this one is the standard one with 150MB lay out:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 44M
userdata ya|asize|hr allsize
I used either one as per instruction in the relevant thread
hmm, and there is deffinitely a file called recovery-raw.img in the same folder? do you get any error messages on the phone screen when you flash the cwm layout?
samsamuel said:
hmm, and there is deffinitely a file called recovery-raw.img in the same folder? do you get any error messages on the phone screen when you flash the cwm layout?
Click to expand...
Click to collapse
Yes. Never happened before until I flashed cwm using ad method as explained in the following:
http://forum.xda-developers.com/showthread.php?t=987531
once you install CWM you are installing a rom from zip arent you?
if you just install cwm then it wont boot any existing rom, thats what i have found from past experience
Richy99 said:
once you install CWM you are installing a rom from zip arent you?
if you just install cwm then it wont boot any existing rom, thats what i have found from past experience
Click to expand...
Click to collapse
After flashed Recovery via AD SD boot, I flashed the ROM. But it won't boot. So, I decided to reflashed Recovery via USB FLasher (of course I did task 29, flash MAGLDR again).
After that, I went into MAGLDR menu and selected no.8 (AD Recovery). And, it wont boot to Recovery. It says ERROR cannot read kernel image.
My point is that I want to flash ROM via CWM (this CWM was flashed via USB Flasher), but the CWM itself failed to boot (after successful flashing).
I dont have problem boot into CWM if it is flashed via AD BOOT (menu no.2 in MAGLDR) and I cant flash the ROM (though the ROM fails to boot).
Any idea?
ive not used that edited/tweaked cwm, but two things come to mind.
First off, latest magldr required, check? (im not scrolling back to read, so sorry if you already said that)
and secondly, from teh error you are getting, it can only be that somewhere, (possibly when you are restoring from a backup taken when there was no recovery partition?) you are either wiping the recovery partition, or you arent loading back the contents of the recovery partition.
samsamuel said:
ive not used that edited/tweaked cwm, but two things come to mind.
First off, latest magldr required, check? (im not scrolling back to read, so sorry if you already said that)
and secondly, from teh error you are getting, it can only be that somewhere, (possibly when you are restoring from a backup taken when there was no recovery partition?) you are either wiping the recovery partition, or you arent loading back the contents of the recovery partition.
Click to expand...
Click to collapse
Yes Magldr 1.13. I didn't restore any nandroid backup. How can I restore if recovery failed to boot?
It seem this tweaked cwm did/wrote something In the NAND that cannot be erased by task 29 or by flashing stock rom. I stiil can bot recovery through AD boot (menu no.2 in magldr) the tweaked recovery show version 3.0.1.9. Maybe I
should try mtty?
think id concentrate on getting back to winmo stock with an sd card flash, wipe the lot and start over yet again.
As far as I remember, after you flash magdlr 1.13 you need to flash CWM to get the menu point 8 (ad recovery) working. Magdlr 1.13 itself doesn't have the CWM built in, but it supports CWM.
Sent from my HTC HD2 using XDA App
samsamuel said:
think id concentrate on getting back to winmo stock with an sd card flash, wipe the lot and start over yet again.
Click to expand...
Click to collapse
Like I said, I did start it all over again
But, still it didnt help. That is why I am beginning to think that task 29 does not erase all NAND or else there is a damaged/defect in the physical NAND. Should I try use MTTY?
greg17477 said:
As far as I remember, after you flash magdlr 1.13 you need to flash CWM to get the menu point 8 (ad recovery) working. Magdlr 1.13 itself doesn't have the CWM built in, but it supports CWM.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Yes I know. There are 3 methods (as I know from XDA ) to boot Recovery Clockword Mode (CWM). Firstly, flashing via USB Flasher (menu no.5) and after flashing, we should select menu no.8 to go into CWM mode (this one is the issue I am talking about), secondly, flashing via AD Boot (menu no.2), it will directly bring you into the CWM menu, and thirdly, using cLK (which I never try it).
I just wanted to try the second method and it works. However, due to the partition lay out issue (as far as I am concerned, the second method doesnt provide flexibility in providing partition lay out. it uses 150MB lay out). So, for the ROM requires different partition layout, I need to flash CWM in accordance with the relevant ROM requirement. This can only be done if we flash CWM via First method. When I flash CWM (for different partition lay out), it seems flashing successful , but when I selected menu no.8 to go into CWM mode it then says: "Error, cannot read kernel image".
Up to now, I can only boot CWM using second method. I just hope the dev of this method can provide a way to flash different partition lay out or did I miss something?
thanks
does this occur with the standard content of raiderx' recovery download, for example the 400m layout...? you can try to edit the "recovery" line inside flash.cfg: remove "filesize" and instead type "6M", so it shows
...
recovery rrecov|ro|nospr 6M recovery-raw.img
...
maybe there are bad blocks on NAND (which is normal, especially after excessive flashing, which is native to us hd2 users due to the mass of roms available for it ) which are causing this.
alternatively you can try to first delete the original "recovery-raw.img" inside the original raiderx recovery folder and then copy the new one; or to use another windows machine (or harddrive in your computer, if exist). maybe there is sth wrong...?
if all you've tried already and other tipps isn't / aren't working, it would be interesting to know if this occurs if you're using cLK; pure testing purpose
i hope you'll get this running... the sd method is no solution in my opinion.
seadersn said:
does this occur with the standard content of raiderx' recovery download, for example the 400m layout...? you can try to edit the "recovery" line inside flash.cfg: remove "filesize" and instead type "6M", so it shows
...
recovery rrecov|ro|nospr 6M recovery-raw.img
...
maybe there are bad blocks on NAND (which is normal, especially after excessive flashing, which is native to us hd2 users due to the mass of roms available for it ) which are causing this.
alternatively you can try to first delete the original "recovery-raw.img" inside the original raiderx recovery folder and then copy the new one; or to use another windows machine (or harddrive in your computer, if exist). maybe there is sth wrong...?
if all you've tried already and other tipps isn't / aren't working, it would be interesting to know if this occurs if you're using cLK; pure testing purpose
i hope you'll get this running... the sd method is no solution in my opinion.
Click to expand...
Click to collapse
Thank Bro, I will try your suggestion and let u know the result.
I also guess there is something wrong with the NAND, maybe the cluster, block, etc. Maybe need to be defragmented (is there any app for doing that?)
I use standar 150MB partion layout from Raider x and also 135MB layout for flashing Typhoon Cyanogenmod.
I still can flash using DAF, but since there is only few ROM for this method, then I would prefer to go through via CWM
thanks again
sure, no problem! one additional question: this really started out since you've used the sdcard files?
cwm is essential and really needed, especially as the most of chefs doesn't provide DAF ROMs anymore. you want to flash typhoon cm7, right? if nothing is working for you, i'll create a daf version for you, so that you at least can use this ROM. just let me know.
seadersn said:
sure, no problem! one additional question: this really started out since you've used the sdcard files?
cwm is essential and really needed, especially as the most of chefs doesn't provide DAF ROMs anymore. you want to flash typhoon cm7, right? if nothing is working for you, i'll create a daf version for you, so that you at least can use this ROM. just let me know.
Click to expand...
Click to collapse
Yes, since I tried the SD card CWM (no offense Bro )
You are right, CWM is app you cant live without it if you are an Android lover
I highly appreciate if you can provide DAF version. I only knows how to convert from ZIP to DAF but not the other way round
Many thanks
k, i will create it todays evening ~ 20:00 gmt+1; but first, pls try to test the other tipps (6M for adding "some spare blocks" and if nothing helps cLK pls).
i'll pm you if i'm ready ok?
i have to do it tomorrow; today i've painted the livingroom of a friend and didn't go home. that's ok? or is there sth new on your side? did you test cLK?
greetings
seadersn said:
i have to do it tomorrow; today i've painted the livingroom of a friend and didn't go home. that's ok? or is there sth new on your side? did you test cLK?
greetings
Click to expand...
Click to collapse
No need to push yourself mate I am patient enough to learn
For installing cLK, I will do it later because I have to learn it since I am not familiar with it (or else if you have or know tutorial for newbie, i would go for it)
I will start with flashing with Recovery with 150MB layout provided by Raider x. Currently I am using Winmo with HSPL 4.
Here is what I will do:
1. Turn of the phone.
2. Go into bootloader mode
3. Task 29
4. Flashing HSPL 2.08
5. Flashing MAGLDR 1.13
6. Flashing CWM 150MB via USB Flasher in MAGLDR menu no.5
7. Boot into Recovery Mode via MGLDR menu no.8
This is the point where i got the problem. If it works, then I can go into Recovery mode to install ZIP ROM , but if fails then it will say Error: cannot read kernel image and it will bring me back to MAGLDR screen.
EDIT:
After flashing MAGLDR 1.13, the phone reboot and I unplugged the usb cable.
It booted and the screen says:
"Booting Android from SD
Android load at 11800000
from Micro SD
Load zimage
k: / zimage
ssSD kernel open failed"
then it brought me to MAGLDR screen menu.
I thought it is normal, isnt it?
then I flash CWM using USB flasher via menu no.5
After flashing CWM complete, the phone reboot and again it showed the above screen and finally went back into MAGLDR screen.
Here is the same old problem. In MAGLDR screen, I selected menu no.8 in order to boot the Recovery mode.
But it failed and the screen says:
"LOAD ANDROID RAW
ERROR: ERROR: cannot read kernel image"
So, it happens again.
Before I continue with the next trial, I wanna hear your opinion about that.
BTW, the winmo before I started this, is ENERGY ROM.
PC I used is WIN XP SP2.
Battery is full, SIM CArd was in but Micro SD was removed.
Do you think I miss something?
Thanks in advance
First thing is first :
Radio 2.12.50.02.2
aMAGLDR 1.11
CWM Recovery 3.0.0.5
SPL 2.0.8
I was flashing from a custom nand to Hyper Droid CM7 v1.0.3. Now that I boot my phone it goes through magldr like normal but loaded zimage, says: load done ...123456 GOGOGO
Then it boots up into CWM recovery.. I tried to install the zip from here and it formats the boot and the system like normal... then copy's all the files to system. The install completes like normal. Then I reboot and it goes right back into CWM recovery. I have tried to flash other roms.. but now my phone wont active sync with my computer. I can only mount it. Any help would be amazing at this point. I have been troubleshooting this brick for the past 5 hours..
Thanks in advance for any help
I'm assuming i will have to start from scratch with wm 6.1... if so how would i flash the os to the phone is my phone doesnt sync with wmdc?
Gunblade77 said:
First thing is first :
Radio 2.12.50.02.2
aMAGLDR 1.11
CWM Recovery 3.0.0.5
SPL 2.0.8
I was flashing from a custom nand to Hyper Droid CM7 v1.0.3. Now that I boot my phone it goes through magldr like normal but loaded zimage, says: load done ...123456 GOGOGO
Then it boots up into CWM recovery.. I tried to install the zip from here and it formats the boot and the system like normal... then copy's all the files to system. The install completes like normal. Then I reboot and it goes right back into CWM recovery. I have tried to flash other roms.. but now my phone wont active sync with my computer. I can only mount it. Any help would be amazing at this point. I have been troubleshooting this brick for the past 5 hours..
Thanks in advance for any help
Click to expand...
Click to collapse
Did you try to reflash Magldr again, CWM recovery, then Android Rom again?
would i be able to do that without my phone syncing with the comp?
I tried it and it booted to CWM recovery
Gunblade77 said:
would i be able to do that without my phone syncing with the comp?
Click to expand...
Click to collapse
Yes, u should flash magldr 1.13, not magldr 1.11 because it will give stuck at GoGoGo. U need to enter bootloader to flash magldr 1.13.
Edit:sorry my bad. 1.11 wont give u stuck at gogogo, but flash 1.13 this time.
Do you actually know what you're doing? Your phone is most certainly not bricked. WMDC is useless once you don't have WinMo on your phone. I think the problem is your radio. Download and flash the 2.15.50.14 radio. It's the newest one. Then flash away and it should work. If not, task 29, reflash MAGLDR and then flash your ROM from clockwork.
Sent from my HTC Vision using XDA App
Ok i got the new mglrd and radio.. now when you tell me to flash the rom from cwm.. you mean from zip right?
ok so I installed from zip and the phone booted up into CWM yet again. Telling me that it failed to find cache/recovery/command, cache/recovery/log.
Failed to find cache partition to mount to cache.
I did update the radio and mglrd like you said.
I had the same problem I task 29'd it then flashed the build via splash mode
Sent from my HTC HD2 using XDA App
Just do the following
Below was taken from Tyween "TyphooN CyanogenMod 7 RC2+ v2.8.0"
1. Task 29
2. Flash Radio(2.15 Recommended)
3. MAGLDR 1.13
4. ClockworkMod Recovery v1.3 135M System/44M Cache/Recovery v3.0.1.9
5. Install TyphooN CyanogenMod 7 .zip with CWM
What i would do is download a stock rom, it will probably come as a single .exe file. rename the extension from .exe to .7z (if you have 7zip, im sure u can name it to what ever archieve program u have) then extract it. find the signed.nbh file and extract that. Then rename LEOIMG.nbh and put on root of sd card. power off phone and while booting hold the volume down button and the power button till you get the bootloader screen... follow prompts and then you are back to a stock hd2
I got it running now thanks for all the help guys. I just flashed a stock rom and changed the radio.
Sent from my HTC HD2 using XDA App
i think its needed to have a 2gb partition for ur sd xard befare install a rom.. partiton ur sdcard with cwm..
Sent from my HTC HD2 using XDA Premium App
Gunblade77 said:
I got it running now thanks for all the help guys. I just flashed a stock rom and changed the radio.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA Premium App
try this:
1) ensure you have magldr 1.13 loaded
2) boot into CWM
3) Do a wipe
4) re-download the ROM zip file (you could have gotten it corrupted somehow on the download)
5) put it on your SD card, load up CWM, flash choose.zip and find your ROM
6) after the flash do another wipe on CWM
7) restart your phone and from magldr load android from nand
edit: lol nvm, apparently I didn't see there was a page 2. Good job on gettin it running
orangekid said:
try this:
1) ensure you have magldr 1.13 loaded
2) boot into CWM
3) Do a wipe
4) re-download the ROM zip file (you could have gotten it corrupted somehow on the download)
5) put it on your SD card, load up CWM, flash choose.zip and find your ROM
6) after the flash do another wipe on CWM
7) restart your phone and from magldr load android from nand
edit: lol nvm, apparently I didn't see there was a page 2. Good job on gettin it running
Click to expand...
Click to collapse
lol thank you this would have helped also
JohnnyVolcom5 said:
What i would do is download a stock rom, it will probably come as a single .exe file. rename the extension from .exe to .7z (if you have 7zip, im sure u can name it to what ever archieve program u have) then extract it. find the signed.nbh file and extract that. Then rename LEOIMG.nbh and put on root of sd card. power off phone and while booting hold the volume down button and the power button till you get the bootloader screen... follow prompts and then you are back to a stock hd2
Click to expand...
Click to collapse
you're really telling him to go back to full stock, with stock spl, that's not necessary, if he has hardspl already, he doesn't have to go thru that again, task 29 will remove all traces causing issues, so all he needs is task 29, radio 2.15.50.14, MGLDR, CWM with the proper partition, and flash desired rom from clockwork.
I only update roms about once every year so I always forget how to do it the next time. I have all the radio/HSPL/MAGLDR/cLK stuff installed, I just cant get any roms to install with it. Every rom listing is pretty vague and just says stuff like "instructions: task 29, magldr, clk, GO!" which isnt very helpful.
I've been combing the FAQ's for about 2 hours now and cant find anything useful. They just diverge into endless unrelated procedures for steps that dont even apply to my situation. It also doesnt help that absolutely nothing on this site mentions Windows 7 64bit. Everything keeps talking about ActiveSync and stuff which Win7 doesnt even support.
It seems like every rom package wants you to task 29 (whatever that is), then re-install magldr from scratch (lol wtf? Isnt the entire purpose of magldr to prevent you from having to reflash bootloaders every time???), and then somehow magically push the .zip file to your phone. They dont mention using clockwork to do it, and the zip's dont have any files to install the rom with. It's purely the rom data, so what am I supposed to do here?
I'm staring at a magldr 1.13 screen with no instructions on how to actually get the zip file installing.
http://forum.xda-developers.com/showthread.php?t=945427
search this:
How to install CWM on MAGLDR (NOT CLK!)
Maybe this
http://forum.xda-developers.com/showthread.php?t=893948
Never task29 unless your phone has gone mental, its unnecessary and just increases the load on the nand chip, possibly speeding up the onset of bad blocks.
If you already have magldr you can forget activesync, firstly in win7 its now windows mobile device center (wmdc) and secondly "get an activesync connection" really just means "get a USB connection" it isn't referring to activesync the program, but the USB drivers activesync (wmdc) uses to connect the phone, and thirdly because magldr uses the android drivers. (You may need to install the android USB drivers, I think you can use the toolkit for that, or install the android sdk, or install "myphoneexplorer" on the PC, which has the added benefit of allowing sync with outlook if you need that)
Flashing
In magldr select USB flasher, connect USB, on the PC run the nand toolkit, use that to partition to the required size, which also installs clockworkmod ( clockworkrecovery, cwr, cwm, clockwork, recovery) reboot the phone, hold power till magldr appears, select ad recovery, this boots cwm, in cwm. *** select install zip from SD (assuming you already put the zip on the SD card) and follow the prompts.
*** at this step you probably wanna make an ext partition many roms require it, and it will hugely increase available storage since the system will use it as internal storage.,(only need do it once, it will completely wipe the card so backup first) choose advanced, format SD card.
PS, if available, use a 32 bit machine, 64 has been causing issues for years,, mostly it doesn't, but some people simply never get it to work right.
Ok I think I have been confusing CLK with ClockWork recovery given the similarity in the sound of their names. What is CLK?
If I have CWM installed, then am I supposed to download the MAGLDR version of the rom file and use that? Seems kinda strange since I thought magldr files were to use with MAGLDR recovery, not clockwork recovery.
RunNgun42 said:
Ok I think I have been confusing CLK with ClockWork recovery given the similarity in the sound of their names. What is CLK?
If I have CWM installed, then am I supposed to download the MAGLDR version of the rom file and use that? Seems kinda strange since I thought magldr files were to use with MAGLDR recovery, not clockwork recovery.
Click to expand...
Click to collapse
cLK is an alternative to magLDR
yes if you already use magLDR make sure its a mag compatible rom
mag = bootloader (just that) ... CWM is recovery (where you will flash or "install" the. zip/rom files)
you CAN simply flash via magLDR via a DAF.exe, however, its an outdated method and the most current chefs cook their roms to be flashed via CWM as it doesnt require a pc (you simply place the. zip rom file to the root of your sd and its easy as pie)
Magldr and cLK do the same thing, they both use cwm so you flash the roms in the same way,,,, by entering cwm and flashing the zip from SD.
cLK offers more in the way of access to the android terminal from the PC, whilst magldr is much more straightforward. (Also cLK allows charging when the phone is off.)
There are two types of rom, mag and cLK, because they both use slightly different boot partition witchcraft .... (I don't know what why where or how, but that's why there's two types.)
Ohhhhhh, yeah I thought cLK stood for like "clockwork", and that CWM was just the rom loading app that you can download from the market. Magldr runs clockwork recovery which is used to install roms, got it.
Hey,
I love my HD2, but the windows not so much.. I'm trying to put Android on it but I am too confused in how to do it.
I have looked into it for a few hours, but I have absolutely 0 knowledge about phones ): and I don't understand it.
Whenever I look in a thread for a guide, I get linked to another thread for another guide, another, and another. This goes from the rom, to a magldr, clk and hdsp and all those things.
Can anybody just tell me in what order to do these? I'll look up guides and such myself, but I have no idea which guide to follow first...
Thanks alot, Kevin.
Okay, here how it goes:
HSPL 2.08 & 2.15 Radio
Magldr
Recovery (such as CWM or TWRP)
Your ROM.
cLK
Recovery (such as CWM or TWRP)
Your ROM.
Radio 2.15 is not necessary, but you need a radio that supports MAGLDR. But 2.15 and 2.12 are the most popular.
So you should first install HSPL 2.08, after that install a radio. Then, choose a bootloader (either cLK or MAGLDR). Then flash a recovery (I recommend CWM 5.0.2.6 if you are willing to install to NAND.). Finally you flash the rom from within the recovery.
You can look for the differences between cLK and MAGLDR, but generally, the differences are:
MAGLDR:
*You can't charge the device while off.
*Supports RMNET Data connection (stable)
*Supports Windows Phone.
cLK:
*Supports charge while off.
*Supports recovery repartitioning without a PC.
*Uses PPP data connection. (Said to be fast, but it's unstable)
download - magldr, nand toolkit, hspl4, radio 2.15.50
into bootloader (stripey screen)
use hspl4 to set 2.08.hspl
into bootloader
flash magldr
into magldr - usb flasher
run nand toolkit - may need to hit the button marked drivers if you have trouble connection, , or install the PC app 'myphoneexplorer' (no need to run it) which also sets the correct drivers.
in the nand toolkit select the desired partition size (the rom you want to flash will tell you what size)
click magldr repartition
--- cwm is now installed
reboot - magldr - 8 ad recovery
cwm will now start
choose advanced - format sd - choose an ext size (512 or 1024 should be fine to get started, 2048 if you have a large card) - (This WILL delete the whole sdcard so backup anything you wanna save)
using an sd card reader, or cwm - mounts and storage - mount sd card to copy the rom.zip you wanna flash to the sd card
restart - magldr - 8 adrecovery - cwm - flash zip from sd card - choose zip from sd card - navigate to the rom.zip file and off you go.
reboot
done.
it should take less time than it took me to write that out, once you get the hang of it.
Thanks a bunch to both of you, really helpful
Oh nevermind, just took a while to boot