Related
What is the difference. Is it just ppp. Seems like magldr I'd the easiest way to install android or update anything that I've ever tried, never really had any problems with it at all. Just looking for some feedback
tigerz0202 said:
What is the difference. Is it just ppp. Seems like magldr I'd the easiest way to install android or update anything that I've ever tried, never really had any problems with it at all. Just looking for some feedback
Click to expand...
Click to collapse
Haven't tried clk, but there is another thread re this same Q, might be of help?
http://forum.xda-developers.com/showthread.php?t=1010125
cLK has few extra options. Charge while phone is powered off. Reboot to recovery. Faster boot time. Rom manager works.
But if you're happy with magldr, don't upgrade to clk.
It's not worth it
Thanks for the feedback guys, don't think ill be switching, just didn't wanna miss out on something better if it was, thanks again
drinizi said:
cLK has few extra options. Charge while phone is powered off. Reboot to recovery. Faster boot time. Rom manager works.
Click to expand...
Click to collapse
Phone with MAGLDR on cannot be charged when the phone is off? What happen if I accidentally used up every drop of the battery and the battery does not have enough juice to power up the phone? Perhaps cLK is a safer route?
Yup that's the flaw of magldr. But I haven't read in anyone who has actually had to replace their battery because of such so you should be fine.
My hd2 ran out of battery last week so I just plugged it into the charger and after one failed attempt to boot up, it booted all the way.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Ok this is my run down or two cents.
MAGLDR is way more user friendly as far as flashing CWM. It has several useful options, but a lot of those options are not needed if you have CWM. MAGLDR can boot Android and Windows Phone 7, but is not as elegantly as a native device of the corresponding OS. Size wise MAGLDR is bigger than cLK. MAGLDR uses RMNET for it's data connection. No charging while the device is off. (I theories the no off charging has some kind of correlation to the digitizer going out so often)
CLK is not as user friendly to flash CWM, as it is not just a click, click, click, click, click and flash. CLK makes your HD2 truly feel like NATIVE Android device. You can only boot Android from NAND with cLK. MAGLDR is a bigger size bootloader then cLK and uses PPP for a data connection. You can charge your HD2 while nit is off
I have used both MAGLDR and cLK, currently cLK. I think both are just amazing pieces of work. But in my honest opinion cLK is the better bootloader for someone that just wants to run NAND Android on their HD2. I just like the way cLK works better than MAGLDR. I will have to flash MAGLDR again coming soon as I want to try out the freshly released WP7 ROM with NoDo. ( yes I said with NoDo )
I love everything about CLK except the fact that it uses PPP. With Cedesmith's b4 wrapper, it's bearable, but I still get about 10 data drops per day minimum (just tried today). The problem doesn't seem to occur too much in strong reception areas. For now, I'm back to MAGLDR. Love CLK, but I will take a significantly more stable data connection.
This is my experience only. Several people do not get data drops at all with the b4 wrapper.
T-Macgnolia said:
I will have to flash MAGLDR again coming soon as I want to try out the freshly released WP7 ROM with NoDo. ( yes I said with NoDo )
Click to expand...
Click to collapse
Where, where, where????
Is this the rom you are talking about??
http://forum.xda-developers.com/showthread.php?t=953078
cLK
cLK has more benefits than MAGLDR and feels a lot more native than MAGLDR.
So pro cLK.
About the new WP7 builds:
The camera in flash mode is again green tinted and you need an activation code for the live service or sideload apps. Just wait for Mango update later of the year than I give WP7 a try.
T-Macgnolia said:
Ok this is my run down or two cents.
MAGLDR is way more user friendly as far as flashing CWM. It has several useful options, but a lot of those options are not needed if you have CWM. MAGLDR can boot Android and Windows Phone 7, but is not as elegantly as a native device of the corresponding OS. Size wise MAGLDR is bigger than cLK. MAGLDR uses RMNET for it's data connection. No charging while the device is off. (I theories the no off charging has some kind of correlation to the digitizer going out so often)
CLK is not as user friendly to flash CWM, as it is not just a click, click, click, click, click and flash. CLK makes your HD2 truly feel like NATIVE Android device. You can only boot Android from NAND with cLK. MAGLDR is a bigger size bootloader then cLK and uses PPP for a data connection. You can charge your HD2 while nit is off
I have used both MAGLDR and cLK, currently cLK. I think both are just amazing pieces of work. But in my honest opinion cLK is the better bootloader for someone that just wants to run NAND Android on their HD2. I just like the way cLK works better than MAGLDR.
Click to expand...
Click to collapse
This describes it best.
I will revive this thread:
I am really not interested in using Win7 and would like to try out CLK. I would like to ask 2 questions:
1) Pros and cons of using RMNET and PPP. I live in Bulgaria, Europe, if this matters in any way. I am very concerned about data drops.
2) Is there a way to swap MAGLDR with CLK in a easy way : via clockworkmod or something: I dont want to install Win 6.5 rom and all that to get it
Thank you
clk is for more advanced people imo.
deckoff said:
I will revive this thread:
I am really not interested in using Win7 and would like to try out CLK. I would like to ask 2 questions:
1) Pros and cons of using RMNET and PPP. I live in Bulgaria, Europe, if this matters in any way. I am very concerned about data drops.
2) Is there a way to swap MAGLDR with CLK in a easy way : via clockworkmod or something: I dont want to install Win 6.5 rom and all that to get it
Thank you
Click to expand...
Click to collapse
Here you go.
What about installing it - Do I have to go all the way flashing official WM ROM and so on...
I've written a clk guide if you decide to switch. It may answer questions as well
Sent from my Transformer TF101 using xda premium
dung8604 said:
I love everything about CLK except the fact that it uses PPP. With Cedesmith's b4 wrapper, it's bearable, but I still get about 10 data drops per day minimum (just tried today). The problem doesn't seem to occur too much in strong reception areas. For now, I'm back to MAGLDR. Love CLK, but I will take a significantly more stable data connection.
This is my experience only. Several people do not get data drops at all with the b4 wrapper.
Click to expand...
Click to collapse
Have to say that seems to be android issue in poor reception areas. I live in area that struggles to get any kind of data connection. I've had a few android devices now, all that all drop data connection regularly when in my local area or other poor reception spots.
Awesome question
Sent from my HTC One X with Beats Audio using xda app-developers app
I don't know why some peopls ask or say that you must flash wm6.5 if you wanna swap between MAGLDR/CLK
you can go between them at any time without losing any data or apps here is what i did
i was in MAGLDR 1.13
Full backup via recovery
flashed CLK via SD (copy CLK "LEOIMG.nbh" to sd root then reboot the device while holding vol down ) then press vol up to perfotm the flash
you're now in CLK, it's time to flash recovery image
download your favorit HD2 recovery.img file
download QtADB from here
go to recovery tab then brows the recovery.img and flash it ( it's easy i think )
now reboot your phone and you're in recovery
partition your NAND exactlly as it was in MAGLDR
flash your ROM (yes FLASH it not from the backup)
i repeat FLASH THE ROM FROM THE ZIP
now goto advanced backup option from recovery then restore the rest of the partitions one by one
FOR THE LAST TIME, DO NOT RESTORE SYSTEM IMAGE FROM BACKUP
wipe dalvik and fix permissions then reboot
your done
i allready tested this methode and it workd fine i migrated from MAGLDR to Clk safely
check my signature to view my current phone config
ThanX
Rom manager now has a clockwork mod recovery for the HD2.. is it safe to flash roms now with magldr installed?
Sent from my HTC HD2 using XDA Premium App
My phone is still showing up in ROM Manager as a Desire. I uninstalled and reinstalled RM and have modified my build.prop to show my phone as a HD2.
Sent from my HTC HD2 using XDA App
huggs said:
My phone is still showing up in ROM Manager as a Desire. I uninstalled and reinstalled RM and have modified my build.prop to show my phone as a HD2.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
in rom manager when you click on flash recovery do you get a list of phones to choose from? you should see "HTC HD2" on the list.
I take it yours worked as well... were you able to reboot into recovery?
Sent from my HTC HD2 using XDA Premium App
Didn't look there, just opened the list of roms. I'll check it out tonite, busy now.
Sent from my HTC HD2 using XDA App
LeoTheRomRasta said:
I take it yours worked as well... were you able to reboot into recovery?
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
Just downloaded the free version of ROM Manager and it would not reboot into recovery, I tried twice. I also tried flashing Clockwork Mod Recovery (even though I already have it flashed to my HD2) becausecevery thing besides reboot into recovery and flash Clockwork Mod Recovery give me a message saying I need Clockwork Mod Recovery before I can use it. But when I tried to flash Clockwork Mod recovery it did list the HTC HD2 in the list but it said it incountered an error while flashing Clockwork Mod Recovery, again I tried twice and same message both times. But I checked and I do still have Clockwork Mod Recovery on my HD2. Maybe you have to use cLK with ROM Manager cause in the information on the ROM Manager when you find it in the Android market says for this.
HTC Users: Flash recovery not working? Try fastbooting a recovery on.
Click to expand...
Click to collapse
You only use fastboot with cLK, if I still had a functioning laptop (LCD screen not working) Iwould test this. But this is not possible for me at the moment.
T-Macgnolia said:
Maybe you have to use cLK with ROM Manager cause in the information on the ROM Manager when you find it in the Android market says for this.
Click to expand...
Click to collapse
ROM Manager currently only works with cLK bootloader.
zach.antre said:
ROM Manager currently only works with cLK bootloader.
Click to expand...
Click to collapse
Thanks for the confirmation. I kinda figured that when I seen fastboot mentioned in the trouble shooting for the app on the market. I just did not want to just assume it worked with cLK or only worked with cLK without being able to test it first. I try hard not to give out false information in the forums. Thanks again though.
zach.antre said:
ROM Manager currently only works with cLK bootloader.
Click to expand...
Click to collapse
hi,
Do you know when it will start working with magldr?
I updated it and bought the premium version, because I was trying to update the boot loader.
I clicked on flash clockworkmod recovery and it updated to 3.0.2.5.
But when I tried to load a d recovery,I just got an error
So I presume it has installed clk?
Don't know how I'm going to get my ad recovery back.i guess I'll have to read up on that.
I did check online for some instructions on ROM manager, but no joy.
Flashed from my fingers to your face
malybru said:
hi,
Do you know when it will start working with magldr?
I updated it and bought the premium version, because I was trying to update the boot loader.
I clicked on flash clockworkmod recovery and it updated to 3.0.2.5.
But when I tried to load a d recovery,I just got an error
So I presume it has installed clk?
Don't know how I'm going to get my ad recovery back.i guess I'll have to read up on that.
I did check online for some instructions on ROM manager, but no joy.
Flashed from my fingers to your face
Click to expand...
Click to collapse
I don't know about it flashing cLK to your HD2 bit if you want to flash cLK PM me and I can help you with it. Cause cLK is not as easycas MAGLDR.
It works!
LeoTheRomRasta said:
Rom manager now has a clockwork mod recovery for the HD2.. is it safe to flash roms now with magldr installed?
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
+1
Installed rom manger and when i tried to flash cwm, HTC HD2 appeared on the devices list for the very first time (i tell you what, it felt great really great), this was the last thing needed to make HTC HD2 fully compatible with android os.
Updated cwm and did a nandroid backup from within rom manger, without a single problem, how cool is that?
This my dear friends was the icing on the cake (sort of speak) for this great piece of hardware and its long road into running android as well as any other native "made for android" hardware. This is it.
Thanks a lot to the devs and their testers who for making this all happen, thank you guys, you did make the impossible, possible, here is proof to that.
Thank you cedesmith for your "not so little" cLK.
Thank you pongster for your amazing roms.
p.s. Hyperdroid GBX is already available to download from rom manager, what do you say to that?
THX
azer0 said:
+1
Installed rom manger and when i tried to flash cwm, HTC HD2 appeared on the devices list for the very first time (i tell you what, it felt great really great), this was the last thing needed to make HTC HD2 fully compatible with android os.
Updated cwm and did a nandroid backup from within rom manger, without a single problem, how cool is that?
This my dear friends was the icing on the cake (sort of speak) for this great piece of hardware and its long road into running android as well as any other native "made for android" hardware. This is it.
Thanks a lot to the devs and their testers who for making this all happen, thank you guys, you did make the impossible, possible, here is proof to that.
Thank you cedesmith for your "not so little" cLK.
Thank you pongster for your amazing roms.
p.s. Hyperdroid GBX is already available to download from rom manager, what do you say to that?
THX
Click to expand...
Click to collapse
Almost makes me want to switch to cLK, but I hear of data and cell problems.
malybru said:
hi,
Do you know when it will start working with magldr?
I updated it and bought the premium version, because I was trying to update the boot loader.
I clicked on flash clockworkmod recovery and it updated to 3.0.2.5.
But when I tried to load a d recovery,I just got an error
So I presume it has installed clk?
Don't know how I'm going to get my ad recovery back.i guess I'll have to read up on that.
I did check online for some instructions on ROM manager, but no joy.
Flashed from my fingers to your face
Click to expand...
Click to collapse
Well... as much i have figured out ROM Manager is not available for MAGLDR yet because of the /boot partition formating.
cLK is formating /boot partition with different file system of MAGLDR which allow ROM Manager to work on cLK.
Now if you would like to change from MAGLDR to cLK it is actually very easy and simple.
Here are the steps:
download cLK 1.4 from here
(cLK is managing the partitioning of the disk therefore you will see different filenames. I use the System:130M / Cache:5M for Ultimate Droid Rom)
The flashing of cLK is done same way as you flash WinMo (with CustomRUU). Just place in the same folder CustomRUU.exe and RUU_signed.nbh and run as administrator.
Ofcourse you have to be in bootloader mode (you know the screen with the 3 colors that shows the HSPL version)
After flashing cLK you need to have installed the adb drivers. On my expirience in Windows 7 are automaticly installed.
After that you have to download the necessary files for the fastboot commands to work from here
Extract the file to i.e. c:\android
Then you have to download ClockWorkMod Recovery for cLK from here. Download from attachements CWM for cLK.
Place the cwm *.img in the same folder as fastboot.
Now, in order to install the cwm to cLK you need to:
Run cmd
Navigate to c:\android (on cmd)
and
Code:
Type "fastboot erase recovery" (<- not really necessary; just to make sure), followed by enter
Type "fastboot flash recovery cLK_recovery_3.0.2.5.img", followed by enter
Type "fastboot reboot" for rebooting your phone
Once rebooted hold down the home button and you will enter CWM
The rest you know what to do.
I use UD Rom 3.2.5 v2 for cLK with a fix for PPP which is actually very stable from here. You can copy/paste this fix to /system/lib with the use of terminal (you must reboot after and must not clear cache)
If you don't care about the internet connection stability so much... cLK is a must for you.
PS: If you need more info about installing read the cLK and CWM thread
timekeeper said:
Almost makes me want to switch to cLK, but I hear of data and cell problems.
Click to expand...
Click to collapse
only data problems.
zach.antre said:
Well... as much i have figured out ROM Manager is not available for MAGLDR yet because of the /boot partition formating.
cLK is formating /boot partition with different file system of MAGLDR which allow ROM Manager to work on cLK.
Now if you would like to change from MAGLDR to cLK it is actually very easy and simple.
Here are the steps:
download cLK 1.4 from here
(cLK is managing the partitioning of the disk therefore you will see different filenames. I use the System:130M / Cache:5M for Ultimate Droid Rom)
The flashing of cLK is done same way as you flash WinMo (with CustomRUU). Just place in the same folder CustomRUU.exe and RUU_signed.nbh and run as administrator.
Ofcourse you have to be in bootloader mode (you know the screen with the 3 colors that shows the HSPL version)
After flashing cLK you need to have installed the adb drivers. On my expirience in Windows 7 are automaticly installed.
After that you have to download the necessary files for the fastboot commands to work from here
Extract the file to i.e. c:\android
Then you have to download ClockWorkMod Recovery for cLK from here. Download from attachements CWM for cLK.
Place the cwm *.img in the same folder as fastboot.
Now, in order to install the cwm to cLK you need to:
Run cmd
Navigate to c:\android (on cmd)
and
Code:
Type "fastboot erase recovery" (<- not really necessary; just to make sure), followed by enter
Type "fastboot flash recovery cLK_recovery_3.0.2.5.img", followed by enter
Type "fastboot reboot" for rebooting your phone
Once rebooted hold down the home button and you will enter CWM
The rest you know what to do.
I use UD Rom 3.2.5 v2 for cLK with a fix for PPP which is actually very stable from here. You can copy/paste this fix to /system/lib with the use of terminal (you must reboot after and must not clear cache)
If you don't care about the internet connection stability so much... cLK is a must for you.
PS: If you need more info about installing read the cLK and CWM thread
Click to expand...
Click to collapse
Hi,
Firstly ,thanks for the tut.
I'm not sure I'm ready for clk right now.My only gripe was that it wasn't overly clear that ROM manager was only for clk,not magldr.
If you,or anyone else on magldr, care to read this thread:
http://forum.xda-developers.com/showthread.php?t=1040564
you can see that I wasn't the only one with this problem.
Having said that,all's well that ends well.
I bought the program because it looked like a great app.
It probably is,but not for me just yet.
At zach.anger why did you say if internet connection stabilitycis notcan issue then cLK is a must. Does cLK cause problems with keeing a data connection?
Also educate me on what PPP is please? I have been reading all through the cLK thread and CWM thread and have not seen an answer.
T-Macgnolia said:
At zach.anger why did you say if internet connection stabilitycis notcan issue then cLK is a must. Does cLK cause problems with keeing a data connection?
Also educate me on what PPP is please? I have been reading all through the cLK thread and CWM thread and have not seen an answer.
Click to expand...
Click to collapse
PPP is 'Point to Point Protocal', it is the alternative to RMNET type of data connection. clk doesn't support RMNET, which some consider to have a steadier data connection (no data drops) at a bit of a cost in data speed. But really ppp has come a long way since we first started having Android on our HD2's. I use ppp on a ROM that was originally on RMNET, and I never experience data drops, but some folks still prefer RMNET, or even can't get a data connection at all ob PPP.
As far as clk being a must, if you have no data issues with ppp:
clk is more like having a native Android device, it enables you to use fastboot commands from adb, and since there's no MAGLDR menu in the way between the OS and recivery, you can use the Advanced Shutdown menu built into some ROMs to boot directly from Android into CWM. That's also why ROM Manager works with clk and not MAGLDR.
Sent from my HTC HD2 using XDA App
huggs said:
PPP is 'Point to Point Protocal', it is the alternative to RMNET type of data connection. clk doesn't support RMNET, which some consider to have a steadier data connection (no data drops) at a bit of a cost in data speed. But really ppp has come a long way since we first started having Android on our HD2's. I use ppp on a ROM that was originally on RMNET, and I never experience data drops, but some folks still prefer RMNET, or even can't get a data connection at all ob PPP.
As far as clk being a must, if you have no data issues with ppp:
clk is more like having a native Android device, it enables you to use fastboot commands from adb, and since there's no MAGLDR menu in the way between the OS and recivery, you can use the Advanced Shutdown menu built into some ROMs to boot directly from Android into CWM. That's also why ROM Manager works with clk and not MAGLDR.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks for the info.
I knew about RMNET not working with cLK, even though I do not know what it is yet lol, I have not googled it yet. Bit I had tried Googling PPP and came up empty using several search terms, well not empty but not the answer I was looking for.
I also knew about being able to enter the ADB fastboot commands using cLK. I have been doing a good bit of research on cLK as I am wanting to add it to my guide in my sig. I am still wondering one thing though. I accidently busted the LCD on my laptop so I can not test this myself. But can you use the fastboot commands to flash a Android ROM just like you usecthem to flash CWM. I mean it seems to me all you have to do is type in the below command into the command promt.
fastboot flash (name of the .img file for the ROM).img
Am I correct in thinking this?
Pretty sure it will work. But I dunno 100% for sure, as I'm still using magldr. clk looks so attractive, butmy current setup is so stable, and I'm a bit lazy to switch
Sent from my HTC HD2 using XDA App
T-Macgnolia said:
Thanks for the info.
I knew about RMNET not working with cLK, even though I do not know what it is yet lol, I have not googled it yet. Bit I had tried Googling PPP and came up empty using several search terms, well not empty but not the answer I was looking for.
I also knew about being able to enter the ADB fastboot commands using cLK. I have been doing a good bit of research on cLK as I am wanting to add it to my guide in my sig. I am still wondering one thing though. I accidently busted the LCD on my laptop so I can not test this myself. But can you use the fastboot commands to flash a Android ROM just like you usecthem to flash CWM. I mean it seems to me all you have to do is type in the below command into the command promt.
fastboot flash (name of the .img file for the ROM).img
Am I correct in thinking this?
Click to expand...
Click to collapse
As said before RMNET and PPP are 2 different connection protocols.
RMNET is stable and supported by MAGLDR and not by cLK
PPP is supported by cLK but not stable as RMNET.
Concerning the benefits of cLK it just makes your HD2 a native android device, with all the benefits of it... Thats all.
About the command you are right. You can use the commands to flash any partition table as following:
"fastboot flash [partition to flash] *.img"
for example you only want to flash a new boot.img (kernel & init.rd) you just need to type:
fastboot erase boot
fastboot flash boot boot.img
you can also flash specific files from within an img but i don't remember the exact commands right now.
Hi,
I have troubles with my HTC HD2.
Im trying to install this version
http://forum.xda-developers.com/showthread.php?t=933951
(25.May.11][MAG/cLK]TyphooN CyanogenMod 7 Nightly v3.3.3[2.3.4][A2SD][tytung r10]
This is my installation step by step.. So...
- Install HSPL 2.08
- Task29
- Radio
- Magldr 1.13
- CWM (3.0.2.5) 150MB
-partition SD Card 1024 and 0
-ext-sd format
- installation of the ROM
- fix permissions
- reboot
And my Android stuck at GO GO GO screen. I dont know what I have done badly, because if I use CWM 3.2.0.0 Android boots nicely, but I hear RoboVoice when I try to call. On the other hand if I try to install the old version of Android via CWM 3.0.2.5 everythink works. I mean the same version of Android but 3.0.6. - no RoboVoice, no bugs with falling applications.
I want to have updated system, but it is impossible for me and I dont know why.
So what is the problem?
thank you
Some details:
SD Card Kingston 8GB class 4
Windows 7 64-bit
maybe this will help ?
http://forum.xda-developers.com/showthread.php?t=945427
Yes, thank you.
But I think the problem is somewhere else. I really keep tutorials and manuals. The problem must be at version of Android. One big different between new and old version is AD Recovery CWM. For old it is for example 135MB, for new version it is 150MB. So I use 150MB as they write at thier thread and it is still not working.
If I use 3.2.0.0, Android(3.3.3) boots, but with bugs.. RoboVoice and so on..
If I use 3.0.2.5, Android freezes at GO GO GO.
Hey,double-confirm if u ain't flashing a CLK build as MAGLDR?
Try using this CWM flasher...it contains version 3.0.2.8...All u have to do is connect phone 2 pc in usb flasher mode (MAGLDR), run the setup.exe as admin, select 150MB partition, flash away...
Alternatively u can just copy out the recovery-raw.img file out and use it 2 replace the recovery-raw.img in the official 3.0.2.5 folder which was recommended in the ROM thread and flash away...
P.S. Try both methods first (performing a task29 each time) and if it still doesn't help then its best to seek help in the ROM's thread...Get help from its users.
MAGLDR of course
Ill try CWM 3.0.2.8. Thank You
99TheDude99 said:
Yes, thank you.
But I think the problem is somewhere else. I really keep tutorials and manuals. The problem must be at version of Android. One big different between new and old version is AD Recovery CWM. For old it is for example 135MB, for new version it is 150MB. So I use 150MB as they write at thier thread and it is still not working.
If I use 3.2.0.0, Android(3.3.3) boots, but with bugs.. RoboVoice and so on..
If I use 3.0.2.5, Android freezes at GO GO GO.
Click to expand...
Click to collapse
First of all are you using cLK or MGLDR?
For robo voice, it is only on the first call, just reboot, call anyone or any number and just hit end call.
If you have GO GO GO screen, you are using MGLDR, so why are you repartitioning your ROM? The MGLDR, already comes with its own partition built in, no need to change anything.
Im using MAGLDR, not cLK.
Ill try your tips, so wait for my report
And what about falling applications?
I click on Internet application or Facebook app. Maybe 3 seconds it works then falls to Home Screen. Thank You
I have used CWM 3028. The problem with RoboVoice is resolved.
However, I have troubles with applications. Internet, Facebook etc.... still falling when I click on them. But at version 3.0.6 everthing works OK.
I dont know why ..
I tried everything
I have successfully installed TyphooN_CM7_v2.9.2-cLK about 8 motnhs ago & been using it but fancied a change.
I am lucky enough to have two HD2's so decide to try installing another nand on the other phone.
I tried TyphooN_CM7_v3.7.0-cLK & DFT_LEO_NAND_Android both using Task 29 & using CWM with CM7 & the USB flasher (as per instructions on the page) for the DFT one. No luck with either they both install but I get an error "Process system is not repsonding" which won't go away with the DFT one & its just keeps booting into Magldr with the CM7. I have installed NexusHD2-Gingerbread_V2.9_NAND_(Android-2.3.5) which is working & installed fine but just can't get either of the other two to work.
I wanted the CM7 to upgrade the current Typhoon I have a wanted a Desire nand on the other phone as a change.
Any ideas what I'm doing wrong?
Help much appreciated
Thanks
Edit:
Following this thread for the CM7 http://forum.xda-developers.com/showthread.php?t=933951
& this for the Desire nand http://forum.xda-developers.com/showthread.php?t=893620
Till now you are used nand android ... so you have the important things (HSPL2.08, radio 2.15.50.14, MAGLDR).
And you installed NexusHD2-Gingerbread ... this means that everything is OK.
I think you can try to download the other things for CM 3.7.0 again.
I've had problems with installing when the .zip is corrupted or something ...
With the typhoon version I would check to make sure that you downloaded the magldr version and not the clk version as it is the magldr that you keep booting into. If you try installing clk to a magldr loader it will not load and just go into magldr loader. With dft one it is probably a bad download or perhaps it is that the rom is an older rom.
There is a lot solutions/problems. Which rom u try to install? Magdlr or clk?
Sent from my HTC HD2 using Tapatalk
Same here
I have exactly the same problem, the only zip NANDs i can install are NexusHD2-Gingerbread. All others install ok but when i reboot it states "Kernal Open Failed" If i install other NANDS via USB flasher they seem to install fine, but then i no longer have AD Recovery Clockworkmod, which is very useful for backups. I appreciate that this is an additional statement but i also have the issue of my phone rebooting 6-10 times a day, hence wanting to change my NAND for testing. I have today however made a complete re-install and using a different SD card, still can't load other ZIP NAND's though.
Hey XDA,
I wanted to know how to change the partition size of my HD2. I am running the hyperdroid rom and have a 150mb CWM partition. In order to run the ICS nexus rom i need a 165mb partition. So do I just flash a new one over the existing one or use task29 and start all over again?
I searched the forum but to no avail.
Any help is GREATLY appreciated.
adil1508 said:
Hey XDA,
I wanted to know how to change the partition size of my HD2. I am running the hyperdroid rom and have a 150mb CWM partition. In order to run the ICS nexus rom i need a 165mb partition. So do I just flash a new one over the existing one or use task29 and start all over again?
I searched the forum but to no avail.
Any help is GREATLY appreciated.
Click to expand...
Click to collapse
You dont have to task29, just flash the new partition size. Use the HD2 toolkit for easy partitioning in Magldr. cLK 1.5 has partitioning on the go - you can partition the phone from the bootloader itself, and a computer is not needed.
ph03n!x said:
You dont have to task29, just flash the new partition size. Use the HD2 toolkit for easy partitioning in Magldr. cLK 1.5 has partitioning on the go - you can partition the phone from the bootloader itself, and a computer is not needed.
Click to expand...
Click to collapse
I use the CWM DAF.exe. I can change the partition size from there by editing the flash file. So is it still the same. Just flash it as per normal?
adil1508 said:
I use the CWM DAF.exe. I can change the partition size from there by editing the flash file. So is it still the same. Just flash it as per normal?
Click to expand...
Click to collapse
Short Answer - Yes
Alternate Answer - DAF method is old and can potentially cause problems owing to the connectivity between computer and the phone (drivers, port, cables...). However, for Magldr repartitioning, that is the only way - even HD2 Toolkit uses it. Using cLK 1.5 (boot loader and partitioning) and ClockWorkMod (flashing ROMs) is the safer and better way, provided you do not have any data drop issues with cLK. I have been using cLK for a long while - ever since v1.3 came out and have never had a data drop problems in Gingerbread as well as ICS.
ph03n!x said:
Short Answer - Yes
Alternate Answer - DAF method is old and can potentially cause problems owing to the connectivity between computer and the phone (drivers, port, cables...). However, for Magldr repartitioning, that is the only way - even HD2 Toolkit uses it. Using cLK 1.5 (boot loader and partitioning) and ClockWorkMod (flashing ROMs) is the safer and better way, provided you do not have any data drop issues with cLK. I have been using cLK for a long while - ever since v1.3 came out and have never had a data drop problems in Gingerbread as well as ICS.
Click to expand...
Click to collapse
I don't think that first part is strictly true. Yes, DAF is an outdated method, but I've never had any issues with connectivity and I've flashed new partitions a decent number of times. I think that as long as the DAF.exe method worked for you the first time around, it tends to work every single time after that. I've probably jinxed it now though, haven't I?
ph03n!x said:
Short Answer - Yes
Alternate Answer - DAF method is old and can potentially cause problems owing to the connectivity between computer and the phone (drivers, port, cables...). However, for Magldr repartitioning, that is the only way - even HD2 Toolkit uses it. Using cLK 1.5 (boot loader and partitioning) and ClockWorkMod (flashing ROMs) is the safer and better way, provided you do not have any data drop issues with cLK. I have been using cLK for a long while - ever since v1.3 came out and have never had a data drop problems in Gingerbread as well as ICS.
Click to expand...
Click to collapse
Thanks man, I will stick with the dar.exe method for now. Will try the toolkit though.
Sent from my HD2 using XDA
just like the way how you flash the recovery, first use the app "notepad.exe" to edit the file "flash.cfg", change "system ya 260M" to "system ya xxxM" what size you needed, second flash the recovery again