Hi guys!
I took a HD2 by a friend that have installed Cyano on it, but sometimes it freeze and i have to remove the battery, so i tried some other ROMs installing CWM and flashing ROMs by the recovery.
Now I have these problems: a lot of times MAGLDR stucks after loading the ROM when says GO GO GO.
When the system could load it freeze after some using, sometimes after 5 min sometimes after 5 hrs.
The CWM I installed is 400MB, it's good for this ROM [Jan 10/01/2015][KK 4.4.4][ LiquidSmooth][Official] Kernel 3.0.101 [ION]? Or it could be this the problem?
I tried many times to start from the beginning of the porting process (HSPL, task29, MAGLDR, recovery, ROM), but nothing, it doesn't work..
Thank you for help!!
(Sorry for my bad english)
beast33 said:
Hi guys!
I took a HD2 by a friend that have installed Cyano on it, but sometimes it freeze and i have to remove the battery, so i tried some other ROMs installing CWM and flashing ROMs by the recovery.
Now I have these problems: a lot of times MAGLDR stucks after loading the ROM when says GO GO GO.
When the system could load it freeze after some using, sometimes after 5 min sometimes after 5 hrs.
The CWM I installed is 400MB, it's good for this ROM [Jan 10/01/2015][KK 4.4.4][ LiquidSmooth][Official] Kernel 3.0.101 [ION]? Or it could be this the problem?
I tried many times to start from the beginning of the porting process (HSPL, task29, MAGLDR, recovery, ROM), but nothing, it doesn't work..
Thank you for help!!
(Sorry for my bad english)
Click to expand...
Click to collapse
try using a system partition of 380 MB , also try to change recovery to ext4
EvilMegaDroid said:
try using a system partition of 380 MB , also try to change recovery to ext4
Click to expand...
Click to collapse
To use a 380 mb recovery can I change the space value from 400 to 380 in flash.cfg?
What do you mean with try to change recovery to ext4? I made a partition on my SD about 2GB ext4..
Thank you!
beast33 said:
To use a 380 mb recovery can I change the space value from 400 to 380 in flash.cfg?
What do you mean with try to change recovery to ext4? I made a partition on my SD about 2GB ext4..
Thank you!
Click to expand...
Click to collapse
hmm yes you can do that , about the recovery grab a SD version of ext4 and run it from sdcard as a second recovery to try it out , or you can download a nand version and replace it with recovery.img
EvilMegaDroid said:
hmm yes you can do that , about the recovery grab a SD version of ext4 and run it from sdcard as a second recovery to try it out , or you can download a nand version and replace it with recovery.img
Click to expand...
Click to collapse
Hi, I've tried your suggestions and it worked for one day and a half, then it freeze again. And after, when i managed to turn the device on after a lot of time it's stucks on GO GO GO, it freeze again after android lockscreen or a bit after, once one time it worked but without sim. It could be the SIM the problem? It is a 4g sim, but i think not.
Thank's you a lot!
hmm well i don't think its a sim problem , why don't you try to install the rom in nativesd and see if it works that way , check the nativesd instructions for more info how to do it
good point about nativeSD, it would eliminate nand bad blocks from the equation.
beast33, try getting a dmesg;
when stuck on magldr gogogo, push the red reset button under battery cover (don't pull battery)
go to magdr 10 services > dmesg to sd
on your sdcard look for file dmesg.txt and post it here.
to see if you have bad blocks and where they are.
Robbie P said:
good point about nativeSD, it would eliminate nand bad blocks from the equation.
beast33, try getting a dmesg;
when stuck on magldr gogogo, push the red reset button under battery cover (don't pull battery)
go to magdr 10 services > dmesg to sd
on your sdcard look for file dmesg.txt and post it here.
to see if you have bad blocks and where they are.
Click to expand...
Click to collapse
With nativeSD it's normal that the boot is longer than nand?
Now it seems working, it freeze only one time, but it stucks on GOGOGO more times than nand...
Attached there is the dmesg.txt file when the phone boot normally, I post the file also when it stucks on GOGOGO to see the difference.
Thank's a lot because this phone is very good even though is quite old and i love to use it like principal device!!
EDIT 04.02.15
Yesterday night i tried to stree a little the device and while installing WA it freeze and doesn't boot anymore, it always stucks on GOGOGO... I don't know what to do anymore, it's possibly that something inside is brocken?
Another little question: wich light and fast rom do you suggest for a every day use (possibly with italian language)?
END EDIT
beast33 said:
With nativeSD it's normal that the boot is longer than nand?
Now it seems working, it freeze only one time, but it stucks on GOGOGO more times than nand...
Attached there is the dmesg.txt file when the phone boot normally, I post the file also when it stucks on GOGOGO to see the difference.
Thank's a lot because this phone is very good even though is quite old and i love to use it like principal device!!
EDIT 04.02.15
Yesterday night i tried to stree a little the device and while installing WA it freeze and doesn't boot anymore, it always stucks on GOGOGO... I don't know what to do anymore, it's possibly that something inside is brocken?
Another little question: wich light and fast rom do you suggest for a every day use (possibly with italian language)?
END EDIT
Click to expand...
Click to collapse
I can't see any attachments
It does not sound good for the phone, but let us see what the dmesg(s) tell us.:fingers-crossed:
Sorry I forgot to post it
This is when the phone boot normally, when it freeze and not boot i post the other one!
It's normal that now with NativeSD the phone seems a lot slower than nand? (SD class 10)
beast33 said:
Sorry I forgot to post it
This is when the phone boot normally, when it freeze and not boot i post the other one!
Click to expand...
Click to collapse
No worries.
That one didn't work. It sometimes happens, especially if there was a long delay between pressing the reset button and getting the dmesg. Good luck with getting another one.
Robbie P said:
No worries.
That one didn't work. It sometimes happens, especially if there was a long delay between pressing the reset button and getting the dmesg. Good luck with getting another one.
Click to expand...
Click to collapse
This one work?
It's normal that now with nativeSD the phone is a lot slower than nand?
well it depends on what rom your using and also sdcard class , for example a class 10 sdcard is way faster than a class 4 sdcard , also what do you mean by slow , UI lag ? if that it happens to me too and maybe (i don't really know) its cuz your acessing data on the sdcard in the same time
beast33 said:
This one work?
It's normal that now with nativeSD the phone is a lot slower than nand?
Click to expand...
Click to collapse
It is better, I can see it is -pixelfreak-'s compiled 3.0.101 kernel, so assume the rom is liquidsmooth KK, but the dmesg stops before the nand bad blocks are listed (if there are any). I can't see anything causing reboots, others may know better. Try again
Robbie P said:
It is better, I can see it is -pixelfreak-'s compiled 3.0.101 kernel, so assume the rom is liquidsmooth KK, but the dmesg stops before the nand bad blocks are listed (if there are any). I can't see anything causing reboots, others may know better. Try again
Click to expand...
Click to collapse
Yes the rom is Liquidsmooth, do you suggest another lighter?
I can make dmseg also when the system boot normally? Or only when it stucks on GOGOGO?
Thank you for your patience!
beast33 said:
Yes the rom is Liquidsmooth, do you suggest another lighter?
I can make dmseg also when the system boot normally? Or only when it stucks on GOGOGO?
Thank you for your patience!
Click to expand...
Click to collapse
a dmesg after normal boot should show your nand bad blocks, if any, so would be good.
a dmesg immediately after it gets stuck on gogogo might show why it gets stuck, so would be good too
Robbie P said:
a dmesg after normal boot should show your nand bad blocks, if any, so would be good.
a dmesg immediately after it gets stuck on gogogo might show why it gets stuck, so would be good too
Click to expand...
Click to collapse
A little question: to make the dmesg after normal boot i have to boot magldr, make dmseg and then boot nativesd, right?
beast33 said:
A little question: to make the dmesg after normal boot i have to boot magldr, make dmseg and then boot nativesd, right?
Click to expand...
Click to collapse
Only difference is after a normal boot, you don't need to use the reset button, just switch off normally, then get your dmesg (dmesg to sd).
reset button gets you out of the hanging bit without removing battery, and thus the dmesg is still in memory when you use magldr to put it on the sdcard.
Not sure why you need to boot nativeSD after you put the dmesg onto sdcard, unless you are using usb to get the dmesg.txt onto pc and therefore onto xda, or are posting it using android via tapatalk. Note that unless you rename dmesg.txt, it will be overwritten the next time you put a dmesg to sd.
Robbie P said:
Only difference is after a normal boot, you don't need to use the reset button, just switch off normally, then get your dmesg (dmesg to sd).
reset button gets you out of the hanging bit without removing battery, and thus the dmesg is still in memory when you use magldr to put it on the sdcard.
Not sure why you need to boot nativeSD after you put the dmesg onto sdcard, unless you are using usb to get the dmesg.txt onto pc and therefore onto xda, or are posting it using android via tapatalk. Note that unless you rename dmesg.txt, it will be overwritten the next time you put a dmesg to sd.
Click to expand...
Click to collapse
This dmesg is after stuck on GOGOGO i hope it could help!
Related
Hi there
i've had a search through the forums and google, but havent come up with anything...
the isue is, after flashing a new CWM NAND ROM on my HD2, the rom will load perfectly the first time. however the issue is when i try to reboot the phone... it loads through cwm, but hangs on loading the rom...
this has happened on several different rom's, and after several task29/mgldr/cwm re-flashes...
Any ideas?
Cheers
Gav
fatmcgav said:
Hi there
i've had a search through the forums and google, but havent come up with anything...
the isue is, after flashing a new CWM NAND ROM on my HD2, the rom will load perfectly the first time. however the issue is when i try to reboot the phone... it loads through cwm, but hangs on loading the rom...
this has happened on several different rom's, and after several task29/mgldr/cwm re-flashes...
Any ideas?
Cheers
Gav
Click to expand...
Click to collapse
Have you tried doing absolutely nothing after first boot, other than skipping through the setup wizard? What I'm wondering is what you may be installing / doing that could be causing this.
One thing that could help is to run logcat with the phone connected during bootup and you could see what is causing it.
Digital Outcast said:
Have you tried doing absolutely nothing after first boot, other than skipping through the setup wizard? What I'm wondering is what you may be installing / doing that could be causing this.
One thing that could help is to run logcat with the phone connected during bootup and you could see what is causing it.
Click to expand...
Click to collapse
hi there
cheers for the suggestion. i tried a re-flash and skipping the setup wizard, but still the same issue.
attached is a logcat capture.
any help appreciated.
cheers
gav
fatmcgav said:
hi there
cheers for the suggestion. i tried a re-flash and skipping the setup wizard, but still the same issue.
attached is a logcat capture.
any help appreciated.
cheers
gav
Click to expand...
Click to collapse
Yeah, looking at your log, you are definitely in a boot loop. Android keeps restarting after what looks like initializing the audio... looks like some files are missing.
What ROM are you using? Have you applied anything (updates) else at all through CWM other than the ROM? Does the ROM you are using require an SD-EXT partition? Is your SD card in the phone?
Digital Outcast said:
Yeah, looking at your log, you are definitely in a boot loop. Android keeps restarting after what looks like initializing the audio... looks like some files are missing.
What ROM are you using? Have you applied anything (updates) else at all through CWM other than the ROM? Does the ROM you are using require an SD-EXT partition? Is your SD card in the phone?
Click to expand...
Click to collapse
hi
i've been trying "skink_Clean_Desire_v1.1_update_signed" and "NexusHD2-Gingerbread_V2.2_NAND_update"...
SD was partioned and formatted using cwm, with a 1Gb ext partition... SD card is present as am flashing using cwm zip from sd...
cheers
gav
fatmcgav said:
hi
i've been trying "skink_Clean_Desire_v1.1_update_signed" and "NexusHD2-Gingerbread_V2.2_NAND_update"...
SD was partioned and formatted using cwm, with a 1Gb ext partition... SD card is present as am flashing using cwm zip from sd...
cheers
gav
Click to expand...
Click to collapse
Which version of CWM are you using? Is it 1.13? Whatever it is, what size did you flash (the partition layout) for your system partition?
Digital Outcast said:
Which version of CWM are you using? Is it 1.13? Whatever it is, what size did you flash (the partition layout) for your system partition?
Click to expand...
Click to collapse
I'm using the latest versions of Magldr and CWM. I flashed a 250Mb system partition.
Gav
Are you sure that is a large enough partition? Is that what the ROM developer recommends?
Digital Outcast said:
Are you sure that is a large enough partition? Is that what the ROM developer recommends?
Click to expand...
Click to collapse
250 is the recommended size on the cwm thread...
not been able to confirm from the 2 rom threads though...
however i have got a mdj rom whuch flashed succesfully on this size...
fatmcgav said:
250 is the recommended size on the cwm thread...
not been able to confirm from the 2 rom threads though...
however i have got a mdj rom whuch flashed succesfully on this size...
Click to expand...
Click to collapse
just use the "daf" folder that comes with the build once you unzip it.
it has the CWR setting configuration all done ready for the build
just flash it.
My issue is: When phone loads android from NAND (sometimes it freezes in GO GO GO) I can use it some unpredictable time. FE. When I switching Mobile Network on it(after 1-2 it freezes). I even upgraded radio to 2.15. No changes still freezes. Second point is, when I turn off radio module and starting using dev. (FE while playing Angry Birds) it freezes again, with the noise on spekers. In my case I detaching battery and waiting for a while (because if you put battery again after a second) it freezes on GOGOGO again. WTF with device. Maybe it is a physical problem?
Dev is TMOUS HD2 16gb.
ps. When I used Android via SD same freeze always happened only with Angry Birds. In WinMo I didnt recognize such issues. Oooh. One more thing. When I tried to go back to WM 6.5 off.ROM. nothing happened after upgrade. I think my device will always live with Android till the end of the days. Thank you in advance!
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
joostnl said:
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
Click to expand...
Click to collapse
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Buy her an iphone, then she can't pull the battery! :-D
Sent from my HD2 using XDA App
malybru said:
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Click to expand...
Click to collapse
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
lol, hahaha
joostnl said:
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Click to expand...
Click to collapse
ive seen a few posts where people have struggled with getting past boot logo, think it was fine after using a different partition in recovery but as your device is for the sd build am not quite sure how that works as Ive never had sd android or if having sd requires clockwork mod recovery? if so try different partition as i said earlier if not hang on till someone has the answer
johnerz said:
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
Click to expand...
Click to collapse
haha great answer, my girlfriend doesn't touch my hd2 or she gets alot more than a double dose with the tazer method, HD2 is not the solution for a women... you take the hd2 of her and buy her a iphone surly they are women material.
Ignore Post
Problems almost always occur after a few weeks or months of use for me, just reflash the ROM, and you'll good to go.
removing the battery is not recommended, it can corrupt files on the sd-card. Try to boot without sd-card and see if it helps. If your ROM does boot, it means the SD card is corrupted, you can try to backup the SD card and restore it after completely wiping the sd-card.
If your rom doesn't boot, than it meant there's something else going on, maybe corrupted flash, so reflash and try again. This will delete all your data, so be careful
if your girlfriend is not an daily flasher also might i suggest using a daf build. All the configuration is done for you. if you are using a sd build from magldr than make sure you change the name of the build than edit the startup txt like this "rel_path=whatever you name the build(example: "rel_path=MIUIROM nand_boot=1") the 1 for magldr 0 for windows 6.5. the reason for me saying this is all android builds create a folder android when they boot up with all your info like data and cache is in there. So its best to separate the two just in case you want to boot up more than two builds from sd.
Same here.
could be a bad block in your NAND memory. you can check this with cLK and fastboot.
see this post: http://forum.xda-developers.com/showpost.php?p=13600733&postcount=9
i checked mine and there was a bad block in the userdata. i think that is wy my phone was freezing.
now i have flashed cLK and untill now its working great!
Someone please help me!! Before all i problems my phone kept freezing in boot and i tried everything by cleaning my sd, ad hard reset and changing builds and the same boot freeze kept happening. So after getting tired of that and having to hard reset everyday i eventually flashed TMOUS stock rom then after tried to do the magldr 113 isntall. I got magldr installed on my phone and then i choose the ad recovery. When i do i get this message "no boot source". I tried looking up on these forums and can't find anything to fix my problems. Someone please help me with a step-by-step guide. I don't want to own an hd2 running the crummy wm6.5 :/ I NEED ANDROID
download hd2 toolkit. afterward install magldr update recovery, follow the prompts to install and your done. in a nutshell...you were missing clockwork recovery. let me know if this helps
danielfc741 said:
Someone please help me!! Before all i problems my phone kept freezing in boot and i tried everything by cleaning my sd, ad hard reset and changing builds and the same boot freeze kept happening. So after getting tired of that and having to hard reset everyday i eventually flashed TMOUS stock rom then after tried to do the magldr 113 isntall. I got magldr installed on my phone and then i choose the ad recovery. When i do i get this message "no boot source". I tried looking up on these forums and can't find anything to fix my problems. Someone please help me with a step-by-step guide. I don't want to own an hd2 running the crummy wm6.5 :/ I NEED ANDROID
Click to expand...
Click to collapse
do this...depending on the recommended recovery size (typically 5-150-5 for non sense versions) download a recovery from here ..then restart you phone...go into magldr...go to flasher...once the usb is linked to pc run daf.exe from the recovery (extracted folder)...u will then have recovery installed
gdsbalaji said:
do this...depending on the recommended recovery size (typically 5-150-5 for non sense versions) download a recovery from here ..then restart you phone...go into magldr...go to flasher...once the usb is linked to pc run daf.exe from the recovery (extracted folder)...u will then have recovery installed
Click to expand...
Click to collapse
YOU SIR ARE GREAT!!! thanks so much!!!!! i can now use android! im glad it works.
Welcome...glad it worked
Sent from my HTC HD2 using XDA App
gdsbalaji said:
do this...depending on the recommended recovery size (typically 5-150-5 for non sense versions) download a recovery from here ..then restart you phone...go into magldr...go to flasher...once the usb is linked to pc run daf.exe from the recovery (extracted folder)...u will then have recovery installed
Click to expand...
Click to collapse
Great ! I will try it out as well. I have been getting this error for the last few times. I am not sure why this happened.
I installed a WP7 rom and then went back to android (hopeless battery drain with my SD card ... not sure if I can ever do something about that). I could not get back to AD recovery.
Thanks again !
gprash said:
Great ! I will try it out as well. I have been getting this error for the last few times. I am not sure why this happened.
I installed a WP7 rom and then went back to android (hopeless battery drain with my SD card ... not sure if I can ever do something about that). I could not get back to AD recovery.
Thanks again !
Click to expand...
Click to collapse
If you loaded WP7 it may have locked your SD Card - need to format in a Nokia phone. Or reduced the usable size to 200mb - this can be fixed with a partitioning tool from PC
when go back and forth between WP7 and Android the nand is overwritten ... thats why you loose your AD recovery.
REMEMBER - if you ever try WP7 and come back to Android dont forget youll need to task 29 (to clean out that nasty M$ dirt!), flash magLDR, flash recovery ( i usually stick with a 200 mb partition, as i usually run Hyperdroid, AND that way there are no worries about bad blocks), and then the rom.
although its not NECESSARY its recommended buuuut to avoid weird restarts, FCs, and any other random glitches that may occur down the short road ITS NECESSARY! :-D
good luck
hello everyone! I just installed android on my HTC HD2 successfully but when the phone reboot, shows me the MAGLDR says me that android booting from start and I have to setup android everytime I reboot the phone from the start. someone help me passing this step. thankyou in advance
Hello everybody,
I can't seem to find an answer to this, though it seems to be a rather basic question.
Is it possible to run two different Android roms on one HD2?
I am currently running Hyperdroid cm7 (Clk-version) and would like to try either a MIUI Rom or a beta-ICS SD-Version, anyone know if and how this would be possible?
Thanks in advance, JW
sure is, through magldr, choose boot ad sd to boot to sd android, or boot ad nand to boot to nand. then, in magldr - services, you can set which you preffer to auto boot, or you can set it to always show the magldr menu and let you decide which to boot.
Thanks for the answer, though I'm not sure I'm willing to go back to Magldr, i like being able to charge my phone while its off.
Thank you though
and just how often is your phone off? mine hasnt been off for, oh, 18 months,,,
You are right on that one, but when I was used Magldr I used to be paranoid about my battery dying since I would have to somehow turn my phone on so it can charge (I am not sure if that would even be a problem, but I feel safe now ) - hope you understand what I mean - in my head it kinda makes sense^^
hehe, in teh event of a dead battery, an old usb cable with teh end cut off, red and black wires bared and held to the battery + and - for 60 seconds will give the battery enough juice to start booting and charging starts halfway thru booting.
JimWest7997 said:
You are right on that one, but when I was used Magldr I used to be paranoid about my battery dying since I would have to somehow turn my phone on so it can charge (I am not sure if that would even be a problem, but I feel safe now ) - hope you understand what I mean - in my head it kinda makes sense^^
Click to expand...
Click to collapse
i have been using Magldr only since nov11. everytime my phone out,just plug it it,n it will auto boot.
nwy got a problem here,
i've been using ICS beta on NAND, then tried to install sense on SD.but after bootanimation finish,its not running sense(SD), its running the ICS.
do u guys now whats the problem??
I have been considering dual booting from SD and nand. Is it possible to have it automatically boot from the rom on the SD?
Sent from my HD2
oroo708 said:
i have been using Magldr only since nov11. everytime my phone out,just plug it it,n it will auto boot.
nwy got a problem here,
i've been using ICS beta on NAND, then tried to install sense on SD.but after bootanimation finish,its not running sense(SD), its running the ICS.
do u guys now whats the problem??
Click to expand...
Click to collapse
Did you boot into MAGLDR, select AD SD Dir then boot into AD SD? If not, try booting into MAGLDR then selecting boot AD SD, should work
michaelnv710 said:
I have been considering dual booting from SD and nand. Is it possible to have it automatically boot from the rom on the SD?
Sent from my HD2
Click to expand...
Click to collapse
Yes, just go into bootsettings in Services (in MAGLDR) then select AD SD.
oroo708 said:
i have been using Magldr only since nov11. everytime my phone out,just plug it it,n it will auto boot.
nwy got a problem here,
i've been using ICS beta on NAND, then tried to install sense on SD.but after bootanimation finish,its not running sense(SD), its running the ICS.
do u guys now whats the problem??
Click to expand...
Click to collapse
I was running WP7 and SD AS for long time and wanted to try NAND but when I tried to boot from SD again it would boot loop NAND boot screen. I flashed WP7 back to NAND and SD works, so I think there is something in the boot partition to allow for SD boot in WP7 build and not in the NAND since most of them use SD-EXT.
I also want to try out ICS, but need easy access to my daily SD (ACA)
I had the same problem. I learned only few Kernels are able to boot SD Builds via Magldr, as described in following thread: http://forum.xda-developers.com/showthread.php?t=1375554
I changed to a different Kernel that actually worked for me. But now I stuck at another problem. I wanted to apply a glitch fix but it seems that broke my SD AD .
war_child said:
I had the same problem. I learned only few Kernels are able to boot SD Builds via Magldr, as described in following thread: http://forum.xda-developers.com/showthread.php?t=1375554
I changed to a different Kernel that actually worked for me. But now I stuck at another problem. I wanted to apply a glitch fix but it seems that broke my SD AD .
Click to expand...
Click to collapse
War_child,
Which kernel should be changed then, i'm little confused. The NAND or SD. This might be a dead end since I would like to try ICS on NAND instead of WP7
You have to change the Kernel in SD Android
war_child said:
You have to change the Kernel in SD Android
Click to expand...
Click to collapse
have u tried hastarin kernel??
war_child said:
You have to change the Kernel in SD Android
Click to expand...
Click to collapse
Hmm, so the SD kernel boots fine when WP7 is in NAND but the same kernel doesn't when Android is in NAND. Interesting
oroo708 said:
have u tried hastarin kernel??
Click to expand...
Click to collapse
I tried 3Dak's R2.9, but I think as I now have to reinstall SD AD I will try hastarin.
... Hmm, so the SD kernel boots fine when WP7 is in NAND but the same kernel doesn't when Android is in NAND. Interesting
Click to expand...
Click to collapse
Seems like the other Kernels are scanning NAND for Android and only if nothing is found they boot from SD. But I'm no dev so it's just a guess
Well I am on the TBD v 2.5
I choose power off since I wanted to copy some data to my SD card
Usually on MAGLDR the phone should reboot when its plugged in but my phone did not, it was charging on off mode in MAGLDR
Anybody else had this experience..???
htcfreak said:
Well I am on the TBD v 2.5
I choose power off since I wanted to copy some data to my SD card
Usually on MAGLDR the phone should reboot when its plugged in but my phone did not, it was charging on off mode in MAGLDR
Anybody else had this experience..???
Click to expand...
Click to collapse
:O please be serious
htcfreak said:
Well I am on the TBD v 2.5
I choose power off since I wanted to copy some data to my SD card
Usually on MAGLDR the phone should reboot when its plugged in but my phone did not, it was charging on off mode in MAGLDR
Anybody else had this experience..???
Click to expand...
Click to collapse
(after you have done freaking out)
Remove cable, orange LED still on?
If yes, probably was just stuck for some reason and I doubt it was actually charging
Otherwise .... " please be serious !" !
just tried it and phone turns on
so no its not working
cLK
Thats why I use cLK. Sometimes need to conserve battery as much as possible and charge my phone while its off. cLK also seems to boot faster, as in their is no waiting to watch magldr's script run.
kylew1212 said:
Thats why I use cLK. Sometimes need to conserve battery as much as possible and charge my phone while its off. cLK also seems to boot faster, as in their is no waiting to watch magldr's script run.
Click to expand...
Click to collapse
And you can use CWM Recovery to flash ANYthing in NOtime
matoflash said:
And you can use CWM Recovery to flash ANYthing in NOtime
Click to expand...
Click to collapse
I do use CWM it makes everything a breeze! I usually do task 29 anyway.. ive been reading about bad blocks on our phone :/ i need to check mine..
Sent from my Transformer TF101 using xda premium
kylew1212 said:
I usually do task 29 anyway.. ive been reading about bad blocks on our phone :/
Click to expand...
Click to collapse
more task 29's = more read, erase, write cycles for the nand = more chance of bad blocks.
That's why i always shudder at advice that starts ' do a task 29, return to stock rom, reinstall magldr, reinstall radio, blahblah.,,, 9 times in 10 they aren't necessary, and in the process you triple the number of cycles the process takes. Simply flashing a new cwm layout is enough to clear the nand 999 times in 1000. As for flashing a new (nandroid) rom, choosing wipe data/factory reset in cwm is also usually enough.
Exactly, don't get why people do that sort of full cycle? Just wipe data then flash new CWM partition (if needed) then ROM is what I would do (as of now I've only actually flashed Typhoon and updated, but if I were to change ROMs this would be how).
samsamuel said:
more task 29's = more read, erase, write cycles for the nand = more chance of bad blocks.
That's why i always shudder at advice that starts ' do a task 29, return to stock rom, reinstall magldr, reinstall radio, blahblah.,,, 9 times in 10 they aren't necessary, and in the process you triple the number of cycles the process takes. Simply flashing a new cwm layout is enough to clear the nand 999 times in 1000. As for flashing a new (nandroid) rom, choosing wipe data/factory reset in cwm is also usually enough.
Click to expand...
Click to collapse
exactly, finally someone has a clue
on top of that, people should stop task29ing when they have bad blocks, because the blocks are 'usually' marked as bad and blocked. Every task29 makes it worse.. but what do i know people, better ask google..