Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.
webmanya said:
Hello dear forum users.
I need your thoughts and advices on my problem.
I'm closely following the Android development on HD2 and learned nearly all methods accept "CLK".
What I recently realize is when I try to install a custom Anroid ROM I'm watching logcat and I mostly see that its giving some errors not always the same error but sometimes it stops after Iampc's(correct me if I'm wrong) sound script and starts bootloop and some times it installs without giving any errors but when it boots is giving lots of FC's after I entered the PIN or sometimes before entering the PIN. Some times it seems to load everything OK but when I turn my phone off and on again it is giving me the sound script bootloop, or not booting at all or sometimes it starts checking or reinstalling the .apks.
I've tried tytungs NexusHD, Tyween's CM mod, ponster's Hyperdroid, crawlingcity's UD etc... I tried lots off android roms and errors are the same.
I'm doing task 29, magldr 1.13, CWRmod, althoug I've fromatted the sd and partitioned it wih CWR I also did wipes of factory reset, cache and dalvik, than rom installation but results are the same.
I tried with different micro sd's and partitioning with cwm and under linux etc. etc..
I tried installing without the sd-ext partitioning and its still the same.
I've tried installing the winmo rom Energy and it setups and loads ok.
I really don't understand what is causing this and it is really making me angry.
I don't think it is related to the hardware because than winmo should give me the same kind of errors but it is not.
Does anyone faced this kind of behaviours? Please share your ideas and thoughts. Thank you.
Click to expand...
Click to collapse
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers
silverwind said:
Maybe your problem is like mine
I had posted similar problem, you can check my threads here: http://forum.xda-developers.com/showthread.php?t=1000190
Pay special attention to post #42
Cheers
Click to expand...
Click to collapse
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.
webmanya said:
Thank you for your advice. I don't know but I'll try to see if its really about the bad blocks. Thank you again.
I don't think my problem is about the bad blocks in the nand. Because what is funny is that I can flash the imilka's ROM's without any problems.
And one more think I realized is that I'm facing this problem with the gingerbread ROMs. I guess they are sharing something and I can not delete them so I'm facing these problems. I think it is really about that you can not delete the nand fully or format it with task 29.
Becuase I realized that when I change ROMs although I've wiped several times I'm getting errors but If I flash the ROM after flashing the original HTC ROM I don't get the same errors. So I guess what we really need is a better tool to wipe and format the NAND for us.
I don't know if this is possible.
Click to expand...
Click to collapse
In fact, I still can use Imilka's, Rafdroid and few other Nandroid ROM
But, I dont want to make it worse knowing that there is some badblock(because I want to sell it)
So, I am back with Winmo and SD Android. It is much safer for me
Cheers
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!
Hello,
I recently had my HD2 setup with MAGLDR 1.11 and a stock DHD ROM, however this froze constantly and seemed to get worse over time, as well as all together failing to boot sometimes.
So I updated MAGLDR to 1.13 found a nice rom "Typhoon CM7" I believe, downloaded the radio it sugested and flashed it, downloaded CWM and flashed it, and then flashed the ROM from SD using CWM.
Sadly however this has not fixed my freezes/failures to boot, im starting to think it might be hardware related.
So what I am asking is does somebody have a ROM that is working really well for them that they could sugest to me?
Thanks,
Alex.
everyone has different opinions, do you want a version with or without sense?
personally i like sense so am using imilkas ram hd version ,its fast and very stable
Well i usually tend to go for ROMs without sense, but i am pretty impartial to it.
alexhope21 said:
Well i usually tend to go for ROMs without sense, but i am pretty impartial to it.
Click to expand...
Click to collapse
Which ROMs have you tried already, and what was wrong with them?
I have tried one of the many DHD stock ROMs and Typhoon CM7, as well as Raphroid and Ultradroid.
I frequently get a freeze at "GO GO GO" in MAGLDR 1.13, and then once the ROM does eventually succeed to boot, it often locks up.
Some ROMs seemed to do better then others overall however, Typhoon CM7, successfully booted most frequently.
In all cases I have used recommended radio's.
However the greatest hassle has been flashing them as I can only get CWM to boot 1 out of 20 times after multiple reflashings, it often gives me an error stating "FATALHIT 1".
Does everyone get behaviour like this?
Hmm.
That's Weird I Have Tried Lots of these roms and they all seem stable and fast on my hd2
crabtreebrandon29 said:
That's Weird I Have Tried Lots of these roms and they all seem stable and fast on my hd2
Click to expand...
Click to collapse
Could you please give me some specific information of what version of MAGLDR, CWM you were using, as well as a link to the Radio and ROM?
Im starting to think my hardware might be bunged.
Thanks,
Alex.
i am too having a lot of problems when booting up from maglrd. It freezes or gets hit fatal error. Do anyone know a good stable rom that doesn't freeze when booting up,and has great battery life?
thi713 said:
i am too having a lot of problems when booting up from maglrd. It freezes or gets hit fatal error. Do anyone know a good stable rom that doesn't freeze when booting up,and has great battery life?
Click to expand...
Click to collapse
All of them. End of story. This is due to user error. Not build related
alexhope21 said:
I have tried one of the many DHD stock ROMs and Typhoon CM7, as well as Raphroid and Ultradroid.
I frequently get a freeze at "GO GO GO" in MAGLDR 1.13, and then once the ROM does eventually succeed to boot, it often locks up.
Some ROMs seemed to do better then others overall however, Typhoon CM7, successfully booted most frequently.
In all cases I have used recommended radio's.
However the greatest hassle has been flashing them as I can only get CWM to boot 1 out of 20 times after multiple reflashings, it often gives me an error stating "FATALHIT 1".
Does everyone get behaviour like this?
Click to expand...
Click to collapse
i assume you are changing the CWR partition each time you change from a dhd rom to a non sense/GB rom ?
Richy99 said:
i assume you are changing the CWR partition each time you change from a dhd rom to a non sense/GB rom ?
Click to expand...
Click to collapse
Yeah, Im starting to think my hardware is damaged, I used to use the SD RAM rom that Dark Forces released, and I guess it did not benifit my device, as it would frequently get quite hot after 20min of straight use.
How does this ROM run with the 2.15.50.14 radio?
If it is also laggy and has bugs, then I think your phone might be broken.
For me all roms using SD-EXT are laggy as hell and i personally stopped testing those roms as I'm already used to the smoothness of Gingerbread... I'm searching almost everyday though these topics to find somebody who says "This is a really smooth Sense rom!". But never seen a comment like that.
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
fxdstudios said:
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
Click to expand...
Click to collapse
Hi. I am not sure , but you can try to formar the SD card, because with the phone seems to be O.K. I am formatting always with Panasonic sd formatter , before flashing.
fxdstudios said:
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
Click to expand...
Click to collapse
Hi,
It sounds like your CWM partition is too small .
Are you sure you are flashing the correct CWM size according to your ROM's [OP]?
Try using KSUBEDI's TOOLKIT (Don't forget to thank him).
It's a simple way of partitioning your CWM.
yes i make sure CWM is correct partition size
Yes I always make sure I use the recommended partitioning in the op of the rom I choose.
I have formatted my SD-card with the panasonic tool
as far as the toolkit. It may be something I did wrong but this started with my phone after my FIRST USE of the toolkit.......PROBABLY NOT THE TOOLKIT although I would love to know what I did to my phone.
I just flashed another HD2 about 10 minutes ago and no issues at all.
The only thing I can think of is possibly nand corruption but then again all things I try to do complete 100% except booting nand.
yes i make sure CWM is correct partition size
Yes I always make sure I use the recommended partitioning in the op of the rom I choose.
I have formatted my SD-card with the panasonic tool
as far as the toolkit. It may be something I did wrong but this started with my phone after my FIRST USE of the toolkit.......PROBABLY NOT THE TOOLKIT although I would love to know what I did to my phone.
I just flashed another HD2 about 10 minutes ago and no issues at all.
The only thing I can think of is possibly nand corruption but then again all things I try to do complete 100% except booting nand.
fxdstudios said:
Yes I always make sure I use the recommended partitioning in the op of the rom I choose.
I have formatted my SD-card with the panasonic tool
as far as the toolkit. It may be something I did wrong but this started with my phone after my FIRST USE of the toolkit.......PROBABLY NOT THE TOOLKIT although I would love to know what I did to my phone.
I just flashed another HD2 about 10 minutes ago and no issues at all.
The only thing I can think of is possibly nand corruption but then again all things I try to do complete 100% except booting nand.
Click to expand...
Click to collapse
Hi,
Did you transfer the ROM by cable or card reader?
Corruption can occur with cable(USB)transfers.
card reader in my laptop.
Like I said I have done this numerous times. Close to 100 times I would guess. I do two hd2s for friends today. no issues with either. although mine is still giving the error no matter what I do.
First time I have seen this error and I do not care about my data or backups or anything of the sort.
I have done EVERYTHING to try and rectify this issue I am having to no avail.
I am stumped at this point
bump I am unsure of what to try now
Did you find a solution????
I also have the invaild boot image header error.
This used to be my phone, but i have handed it down to an employee.
He has caused a fault where it force closes with android.process.media, especially when i go to market.
I thought i would update the rom and hopefully "delete/overwrite" the problem.
One thing i did was a backup with ROM manager and upgraded that to 4.
This phone will boot into the existing ROM - Nightlys typhoon 3.2.8, but if i try to go into recovery I get the error.
Anyone found the answer????
fxdstudios said:
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
Click to expand...
Click to collapse
well i dont think that 135 is the exact partition ....135 is used for nexus hd2 but for typhoon rom or hyperdroid rom u must use 150 mb systeme partition with 5 mb cach ...try from the start with task29 to clear everything and flash angain i'm sure it will work
Are you still having this? I seem to be having the same problem now. If I restore a backup it will give me "invalid boot image header". If I put a new ROM over my backup it works fine. I have task 29d. Loaded cLK, CWM, and then a new ROM. Backed this up and then immediately restored it and got the same error when trying to boot. I can get into recovery fine. I have tried different cLK partition layouts too. ):
I did it too, this is the problem and the fix
http://forum.xda-developers.com/showthread.php?t=1040564
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!
Hi, I'm using tmo hd2 and have been flashing Roms and getting my feet wet for a few months now, something happened between flashes that is preventing me from using wifi tether on all my favorite Roms, dorimanx, hyperdroid, ndt miui and more, I know I had it working before fine on hyperdroid and ndt miui but now doesn't want to work, same Roms same versions worked before, I tried reflashing maglrd and cwm partition, full wipe, reinstall. Ect but no luck, anybody else run into this or have any ideas where I should be looking? Thanks for your help, this is my first post but I appreciate this forum a lot and am very thankful for all the guides and. Tutorials here!
I would task 29 reformat my sd card and try again from scratch (saving my data first of course ).
It might be worth reflashing your radio of course, but ensure you flash a compatable radio or you can brick the phone
loveandelectrik said:
Hi, I'm using tmo hd2 and have been flashing Roms and getting my feet wet for a few months now, something happened between flashes that is preventing me from using wifi tether on all my favorite Roms, dorimanx, hyperdroid, ndt miui and more, I know I had it working before fine on hyperdroid and ndt miui but now doesn't want to work, same Roms same versions worked before, I tried reflashing maglrd and cwm partition, full wipe, reinstall. Ect but no luck, anybody else run into this or have any ideas where I should be looking? Thanks for your help, this is my first post but I appreciate this forum a lot and am very thankful for all the guides and. Tutorials here!
Click to expand...
Click to collapse
I had this problem once, go to "Fix for random malfunctioning of WiFi tethering ability."thread and see if that helps you out.