Hello everyone.
Two days ago a friend of me asked if I could install Android on his "new" HTC HD2.
As I installed Android on serval HD2's I said yes, no problem at all.
But once he came to my house and I started working on it only trouble is what came to me.
The HD2 was stock so Windows Mobile was running on it.
I install HSPL4 , no problem.
Flashed the radio, no problem.
Installed cLK, no problem.
Installed recovery : PROBLEM.
The trouble started from there.
The phone did not reboot, even tough it said "rebooting phone"
So what I did is unplug the phone, Task29'd it and did everything over again.
Than, I got an error on the radio installation.
The phone rebooted and when I got to the tri colour screen I was shocked.
It said some kind of "error rom update failed"
After this nothing worked, installing a Radio failed, installing the stock firmware downloaded from HTC failed etc.
Only flashing HSPL4 and Task29 worked, so I tought I was screwed.
I readed many many threads and somewere I got to the "Chill in fridge trick"
So I putted the phone in the freezer for 10minutes, copied the nbh file from the stock Windows Mobile rom to the SD Card and TADAAA! It worked!
So, here I was, back on Windows Mobile, trying again! to install Android.
As long as I kept the phone cold everything worked, also installing cLK and Clockworkmod.
But now here the thing is: Installing and running Cyanogemod is no problem at all, Cyanogenmod boots and run fine.
But when I want to install a sense rom, it works as long as the phone is cold.
When the phone gets to normal temps it stops responding and tries to reboot.
It stays stuck on the boot, and I have to put it in the freezer again to make it work.
This problem only occures with a sense rom!!
Windows Mobile rom doe snot have any problems, also Cyanogenmod does not have any problems.
The phone does still have warranty, but as the phone does not have problem with Windows Mobile I don't think I can send it to HTC for repair, as I think this is a hardware problem.
Does any of you know what I could do in this kind of situation?
Thanks in advance!!!
Did you install magldr?
Sent from my HTC HD2 using Tapatalk
sam razzy said:
Did you install magldr?
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
no he is using clk
Looks like a hardware problem with your phone.
I don't know if this is the problem but you installed the wrong hspl.
Hspl 2.08 is the proper one
Sent from my HD2 using xda premium
it happened the same to me few days ago
try HSPL 2.08
MGldr
it should works
kylew1212 said:
I don't know if this is the problem but you installed the wrong hspl.
Hspl 2.08 is the proper one
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
I always used 2.08HSPL always worked perfect for me.
How can it be the wrong one than?
I'll give 2.08 a try, hopefully it works for that phone
Sent from my HTC HD2 using XDA App
Vinny1994 said:
I always used 2.08HSPL always worked perfect for me.
How can it be the wrong one than?
I'll give 2.08 a try, hopefully it works for that phone
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
No no your SPL version is fine I think they may have been confused with HSPL4 (the package used to flash HSPL 2.08 on WinMo ROM 3.14) so leave that alone.
Just for everyone's information I only found this out recently but in actual fact the HSPL version can be anything for cLK, but the large red writing in mskip's original MAGLDR tutorial has caused people confusion over this topic, and now most people think that HSPL2.08 is needed when any version will do.
Are you correctly adjusting the partition size when flashing the Sense ROMs? I don't know how to do this on cLK but look in kylew1212's guide in his signature, it tells you everything and probably has stuff on repartitioning.
Nigeldg said:
No no your SPL version is fine I think they may have been confused with HSPL4 (the package used to flash HSPL 2.08 on WinMo ROM 3.14) so leave that alone.
Just for everyone's information I only found this out recently but in actual fact the HSPL version can be anything for cLK, but the large red writing in mskip's original MAGLDR tutorial has caused people confusion over this topic, and now most people think that HSPL2.08 is needed when any version will do.
Are you correctly adjusting the partition size when flashing the Sense ROMs? I don't know how to do this on cLK but look in kylew1212's guide in his signature, it tells you everything and probably has stuff on repartitioning.
Click to expand...
Click to collapse
I have HSPL4 2.08HSPL installed, so not 2.08 or any other one, is that 2.08HSPL the correct one? I always use that one and it always worked.
Do I still have to try an other HSPL than?
Yes the partition size is correct, I've been flashing my own HD2 for ages, never had problems with it.
It's just this HD2 that my friend owe's as explained in my 1st post that gives problem.
Little offtopic: IMAO flashing cLK is even esier than MAGLDR with the HD2 Toolkit
I had this too. Conclusion was if it needed to be chilled it had a hardware issue. No fix.
Sent from my HD2 using xda premium
kylew1212 said:
I don't know if this is the problem but you installed the wrong hspl.
Hspl 2.08 is the proper one
Sent from my HD2 using xda premium
Click to expand...
Click to collapse
HSPL4 is the name of the program which changes the HSPL.
I agree with Gary
Freezer = Working
Normal Temp. = Bootloops & Errors
Definitely a hardware issue..
(Look for similar threads using the keywords: freezer, hd2, stuck. And you'll notice that all of them had the same symptoms & all of them turned out to be hardware issues)
Okay, well I'm dumb haha, I just assumed that hspl 4 was different than 2.08. I'm inclined to believe its a hardware issue too, sorry
Sent from my HD2 using xda premium
I would still task 29 and try flashing another radio and try magldr this time
Swyped from my Sgs2 T989
relldroid said:
I would still task 29 and try flashing another radio and try magldr this time
Swyped from my Sgs2 T989
Click to expand...
Click to collapse
Did that many many times.
I also checked for damaged blocks but there are no damaged blocks in the nand.
Sent from my HTC HD2 using XDA App
As most people (including me) think this is a hardware problem I want to ask if anyone has expierences with warranty in these kind of situations.
I know I have to put winMo back on it, but will HTC accept this HD2 for repair? As I don't have problems when using Winmo.
Will the HD2 be fixed if my friend tells HTC that the phone keeps rebooting randomly and gets really hot using Winmo?
Or do you think its best to contact HTC for this ?
Sent from my HTC HD2 using XDA App
Vinny1994 said:
As most people (including me) think this is a hardware problem I want to ask if anyone has expierences with warranty in these kind of situations.
I know I have to put winMo back on it, but will HTC accept this HD2 for repair? As I don't have problems when using Winmo.
Will the HD2 be fixed if my friend tells HTC that the phone keeps rebooting randomly and gets really hot using Winmo?
Or do you think its best to contact HTC for this ?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Honestly before reading this post I thought it was hardware as well. But if the phone works with windows mobile that makes it sound like something has gone wrong with your android install.
As for the warranty, I have t mobile. I also have the insurance plan so I pay x amount every month. A few months ago I got my phone wet and had to request a new device(I managed to actually have my phone fixed before the new one arrived and I flashed back to win mobile) but within about 2 days from the time I reported the issue I had a refurbished phone in my hands.
Edit:
I am still using the refurbished phone, and no problems. Customer service was good and everything.
kylew1212 said:
Honestly before reading this post I thought it was hardware as well. But if the phone works with windows mobile that makes it sound like something has gone wrong with your android install.
As for the warranty, I have t mobile. I also have the insurance plan so I pay x amount every month. A few months ago I got my phone wet and had to request a new device(I managed to actually have my phone fixed before the new one arrived and I flashed back to win mobile) but within about 2 days from the time I reported the issue I had a refurbished phone in my hands.
Edit:
I am still using the refurbished phone, and no problems. Customer service was good and everything.
Click to expand...
Click to collapse
Nah, I always flash this methode:
1. HSPL
2. Radio
3. Bootloader (cLK)
4. Recovery (Clockworkmod)
5. Flash Rom.
Always worked, no problems at all with my phone and all other HD2's i've flashed.
And this HD2 that gives problems, only gives them when its warm.
When it was warm, it always gave problems with flashing the Radio.
Flashing a custom radio failed, but also when I putted the nbh from the original WinMo on the SD Card and it started to flash, it failed on RadioV2.
After I chilled the phone in the freezer it worked perfectly but once it got warm again, it stopped responding.
This was only when flashing or running a Sense rom, no problems with Cyanogenmod or WinMo. Thats the strange part of the story.
I will tell my friend he has to call HTC for this problem so that they can fix or swap the phone
Related
I sold a Hd 2 to my friend. It had android with chucky Rom on it. I flashed it back to stock. No sign of Android at all. Void black sticker is on (where the screw is to access internals) and both white water damage stickers are good. Question is the touch screen stopped working while on stock t-mobile Rom. I called them and they will send me a replacement one. Will they know the Rom was ever changed and also Android was on the SD card which there not getting..so t-mobile shouldn't know it ever had android on it right? So they wouldnt charge me a huge bill.
Sent from my PC36100 using XDA App
justinnguyen said:
I sold a Hd 2 to my friend. It had android with chucky Rom on it. I flashed it back to stock. No sign of Android at all. Void black sticker is on (where the screw is to access internals) and both white water damage stickers are good. Question is the touch screen stopped working while on stock t-mobile Rom. I called them and they will send me a replacement one. Will they know the Rom was ever changed and also Android was on the SD card which there not getting..so t-mobile shouldn't know it ever had android on it right? So they wouldnt charge me a huge bill.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
If you installed Stock Rom and removes HSPL, everything is okay.
kurt-willems said:
If you installed Stock Rom and removes HSPL, everything is okay.
Click to expand...
Click to collapse
well this kinda depends. how did you flash? from sd card, hspl is gone. from usb, hspl is still there. (remove it by running hspl via usb - just reverse your steps.) (you can always check your spl/hspl by just booting into bootloader too...)
and i know this as i had to do the same thing. good luck!
jsmccabe78 said:
well this kinda depends. how did you flash? from sd card, hspl is gone. from usb, hspl is still there. (remove it by running hspl via usb - just reverse your steps.) (you can always check your spl/hspl by just booting into bootloader too...)
and i know this as i had to do the same thing. good luck!
Click to expand...
Click to collapse
The chucky roms radio flash was done from active sync but hspl and running the android (haret/clrcad) was all done from the SD card. I since then I downloaded the Stock Rom and flashed it back. it worked normal for a while but the touch screen just straight up crashed. I can boot up but touchscreen doesnt work. I doubt they will know since it shows no water damage and touchscreen fails.
flash the STOCK rom from the SD Card or else HSPL will still be there.
why would they care if you run android? that does nothing to the ROM.
justinnguyen said:
The chucky roms radio flash was done from active sync but hspl and running the android (haret/clrcad) was all done from the SD card. I since then I downloaded the Stock Rom and flashed it back. it worked normal for a while but the touch screen just straight up crashed. I can boot up but touchscreen doesnt work. I doubt they will know since it shows no water damage and touchscreen fails.
Click to expand...
Click to collapse
so....hspl might still be on your phone. you don't say how you flashed the stock rom (or did you unininstall hspl using the hspl program)? (or am i missing something? dont know you can uninstall hspl via sd card...but i could definitely be wrong here.) if you flashed the stock rom from usb and did not uninstall hspl, you still have hspl on there. they will be able to see this. anyways...you should boot into bootloader and look to be safe.
nrfitchett4 said:
why would they care if you run android? that does nothing to the ROM.
Click to expand...
Click to collapse
exactly. nothing but a program, imo. also, when they exchange phones you are supposed to keep the sd card (i got a bonus one when i did this!) they only want the phone (you keep sd card, battery, back cover...)
I got the hspl to spl so its all fine now. Sending back for a new phone!!
Sent from my PC36100 using XDA App
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse
Please mention your RADIO, HSPL and the last Android Rom in which this happened!
If your phone is booting, it's not bricked. Did you try another SD card? Have you tried doing a low level format on your SD card? If it were me I'd Format the SD card with an adapter on my PC, low level. Then I would put it back in the phone then run Task29. Then flash MAGLDR 1.1. Then Flash the CMY 1.4n Desire HD Nand build in the HD2 Nand Android Development forum. It's the most stable Nand build up there right now.
I would use the 2.15 radio that comes with the newest Tmobile ROM. You might have to download the 3.14 ROM from Tmobile and flash it first to get the Radio in there. Then Task29 after that. MAGLDR, Then the NAND build. Make sure you find the Task29.exe that doesn't have a radio paired with it. it's on this site somewhere.
lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse
hd2 running MIUI freezing up too
I'm a complete noob here so bare with me. I'm currently experiencing the same probs as lewy255 with the hd2 freezing up. It happens every now and then when I'm accessing certain apps. When the hd2 does freeze up, i have to take the battery out, wait, then boot up again. Once it tries to boot up it freezes on magldr, then i got to take out the battery again, wait, then power it on again. It seemed to happen when i first rooted my hd2. The first ROM i flashed after rooting was typhoon CM7. Currently have:
HSPL 2.08
radio 2.15.50.14
MIUI version: 1.5.27
I hope this isnt a hardware issue cause i bought this phone from one of my friends and he didn't have the receipt. Please advise on what i can do to fix this freezing issue.
Thanks
Sounds like cpu overheat freeze. When you were playing music and charging it the first time it froze, was the phone and/or battery hot?
It's very possible that it got too hot once, and now the cpu its self gets too hot much easier now that it has already happened once.
Sent from my HTC HD2 using XDA App
Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App
germotlp said:
Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.
T-Macgnolia said:
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.
Click to expand...
Click to collapse
t-mac
I tried installing setCPU and adjusted the temperature setting so if got too hot then the speed of the phone would be reduced, but still no luck.
What if i unrooted the phone and put everything back to stock? I think that way i will know for sure that its a hardware issue. I dont know much about phones but your probably right. I'll try running task29 and reinstall everything and see if that works, if not then i will un-root and put everything back to stock and test.
Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.
Kailkti said:
Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.
Click to expand...
Click to collapse
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App
i have same problem with miui roms. I think this problem is about Miui Roms. Miui developers must solve this issue, there is no way..
When i try other Roms, there is no problem like this issue..
germotlp said:
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
in my opinion and its just my opinion, but you should flash a winmo 6.5 build than boot android from sd its safer because theres no need to worry about battery dying in magldr. and if theres a nand rom you want to try out i suggest using port a droid. im using now with the new nexus 2.8 with a 1gb data.img and it runs great plus i have 3 other builds on there also.
So I have 2 hd2 phones one of witch I'm able to run nand based android on just fine. The other one witch I installed everything on just the same has serious booting problems.
I install hspl3 and cwm onto it than flash android. Than it either freezes at cwm screen or loads android and freezes there. Sometimes it will repeatedly reboot. I've done both hard and soft resets, I've also reinstalled the original rom back on it with the same results.
Is there anything someone might suggest that can help me out, or should I trash the phone? Any help would be nice.
Also before flaming me I have done alot of research and nothing I read and try seems to work. That's why I decided to finally post asking for help
Sent from my HTC HD2 using XDA App
did you task29?
That is something I haven't done. Mostly because I don't even know what it is. Or how to do it.
Sent from my HTC HD2 using XDA App
It's like formatting the NAND storage, give you a clean plate with no residue left behind from previous flashes.
http://forum.xda-developers.com/showthread.php?t=644781
So i ran task 29 and i'm still having problems.. as of rightnow phone keeps getting stuck on the 3rd loading screen. rebooted the phone 3 of 4 times and still having the same issues
Sent from my HTC HD2 using XDA App
Once you have run Taks29 you need to install a ROM, as task29 wipes the ROM area.
The best option is to flash a stock ROM (preferably not the 3.14 version, as you want to install Nandroid). Please make sure you do one allowed on your phone.
Once this is done, test the phone to make sure that there is no hardware issues.
It is advisable not to have the SD Card in the phone incase that could be faulty.
I got myself a HD2 the other day, and since i am a androidfan i wanted to get my HD into a droid rom.
This ended in a mobile not wanting to boot, got to the boot screen where i se the android sign and then it reboots. This goes on forever...
HSPL works (have tried different versions) so i can keep trying different roms, but all ends up rebooting the phone. Doesnt matter if i tryWindows 6.5, android or windows7 roms.
But another problem is that i dont know which Rom was my "original" rom, and i formatted the original sd card...
Hope one of you clebver guys have an answer and solution i can try out.
Here are som info that shows in the boot screen now:
R 2.15.50.14
G 15.42.50.50.11U
D 3.14.04666
How did you exactly try go get yourself 'into a Droid ROM'? From SD card or nand? What bootloader do you have? 2.08.Hspl or 2.08.0000? Just go in to Bootloader and flash a custom WinMo ROM or MAGLDR if you want to flash Android from NAND.
Sent from my HTC Vision using XDA App
I have 2.08Hspl bootloader now.
Have tried with Magldr with no luck. Have tried both Sd and Nand version
Still no luck
LordPalo said:
I have 2.08Hspl bootloader now.
Have tried with Magldr with no luck. Have tried both Sd and Nand version
Still no luck
Click to expand...
Click to collapse
I've tried several ROMs & each time they boot up wonderfully, whenever i encounter a problem..its usually cuz i either skipped a required step or didnt fully understand how to get that particular ROM working...So my advice 2 u is to follow the dev's instructions properly in order 2 minimize errors...feel free 2 try d build contained in my sig...With normal usage, i still squeeze out @least 30hrs+ out of my device(calls, msgs, wifi, data, sync, really low back-light, apps, games, etc)
Aaaahh!
Found the solution to my problem.
It was one of the battery contacts that was bent out.
Bent it back into place, and now the phone boots like a Dream
Let the android testing begin
I only suggested that to somebody else today and All! Haha.
Sent from my HTC Vision using XDA App
If you want NAND version, you need hspl 2.08, magldr, and cwm in order to flash rom.
I have a HTC HD2 that I had flashed with NexusHD2-ICS-CM9-V1.4 and everythinh worked fine, however the touchscreen stopped working after some damage so I flashed all except SPL back to stock and sent it to be fixed.
I've now got it back (still with HSPL 2.08) and flashed MAGLDR 1.13 back on and CWM, however when trying to boot CWM it gets to 123456 GO GO GO! then hangs, same happens with NexusHD2-ICS-4.0.4-CM9-HWA-SD V2.5 booting from the SD Card and CWM booted from the SD Card.
HSPL: 2.08.HSPL
Radio: Leo-RADIO_2.15.50.14
Bootloader: MAGLDR 1.13
Any advice would be great
JeeSe said:
I have a HTC HD2 that I had flashed with NexusHD2-ICS-CM9-V1.4 and everythinh worked fine, however the touchscreen stopped working after some damage so I flashed all except SPL back to stock and sent it to be fixed.
I've now got it back (still with HSPL 2.08) and flashed MAGLDR 1.13 back on and CWM, however when trying to boot CWM it gets to 123456 GO GO GO! then hangs, same happens with NexusHD2-ICS-4.0.4-CM9-HWA-SD V2.5 booting from the SD Card and CWM booted from the SD Card.
HSPL: 2.08.HSPL
Radio: Leo-RADIO_2.15.50.14
Bootloader: MAGLDR 1.13
Any advice would be great
Click to expand...
Click to collapse
Have you tried task 29? And doing it all over again?
Sent from my NexusHD2 using xda app-developers app
adil1508 said:
Have you tried task 29? And doing it all over again?
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
Yes, we have tried that.
I assume noone else has any ideas then?
May just have to use the stock win mobile rom...
I had the same problem. When the touchscreen wasn't working, I repaired it on a local shop. It was Back with working touchscreen and everything worked fine including Android and Windows except the accelerometer wasnt working In Android.
netchamp.faris said:
I had the same problem. When the touchscreen wasn't working, I repaired it on a local shop. It was Back with working touchscreen and everything worked fine including Android and Windows except the accelerometer wasnt working In Android.
Click to expand...
Click to collapse
i think i have the same problem at first i thought it was the rom but the touch screen not responding
JeeSe said:
I assume noone else has any ideas then?
May just have to use the stock win mobile rom...
Click to expand...
Click to collapse
try the link below, it might help
mengfei said:
try the link below, it might help
Click to expand...
Click to collapse
Hi thanks, we know how to flash it though. We had it working before I sent it for repairs, then flashed back to stock before sending to the insurance company.
Now that it has returned repaired when I try to flash it, CWM does it's '123 Go Go Go' Then just hangs and wont load....
That is the problem I am having.
Still unable to flash. Noone able to help with this problem?
bumping one last time. In the hope someone has come across this problem at some point..
In summary, CWM loads as far as '123456 GO GO GO' then it jams, and goes no further.
Any help appreciated.
I recommend trying to return WM6.5.
Then install Android.
* task 29 can hurt. Windose check the machine's memory and mark the damaged area (if any)
sb1971 said:
I recommend trying to return WM6.5.
Then install Android.
* task 29 can hurt. Windose check the machine's memory and mark the damaged area (if any)
Click to expand...
Click to collapse
Hey, thanks, WM6.5 is installed and fully functional, it installs no problem.