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
Related
broke my old hd2. insurance sent me a refurbished model. flashed hspl, then nrg sencity nov 24 to get back to my previous setup. running core_droid_evo_0.8. was impressed droid brought evrything back to the way i left it. but.... since then the phone constantly freezes. tried hard reset. 1 out of 10 times it will actually finish booting after pulling battery, then to just freez again. I didnt flash radio 2.12.50. it came with 2.15.50.14, and that sounded newer. didnt think that would make this happen tho. any clue?
i appreciate all the views this thread got but. Ive tried the famous search bar and it never works! always says try back in 30 minutes. I cant sit here staring and digging thru pages of threads to find answers. at least shoot me a link to an appropriate thread please
If its a refurb then I'd return it to stock and tell them they've sent you a faulty handset.
Are you talking about freezing in WM or when your using android??
You could try reflashing after doing a task 29. Might be worth trying a different energy rom just to see if the freezing issues are still there........
If its android freezing, did you restore old backups? try running it without any backups and see if it still freezes.
conantroutman said:
If its a refurb then I'd return it to stock and tell them they've sent you a faulty handset.
Are you talking about freezing in WM or when your using android??
You could try reflashing after doing a task 29. Might be worth trying a different energy rom just to see if the freezing issues are still there........
If its android freezing, did you restore old backups? try running it without any backups and see if it still freezes.
Click to expand...
Click to collapse
ya freezes everywhere between splash screen and droid. I cant tell what if anything is causing it to crash. Ive had new phone for 12 hours and have pulled battery at least 100 times.
Personally I'd try and get another replacement.
If you dont wanna go down that route then you should start over from scratch (task 29, stock WM), leaving some time between the different stages of setting up your device to try and see when the freezing starts to happen.
are you running android off the sdcard?
M..N said:
are you running android off the sdcard?
Click to expand...
Click to collapse
__yes______
conantroutman said:
Personally I'd try and get another replacement.
If you dont wanna go down that route then you should start over from scratch (task 29, stock WM), leaving some time between the different stages of setting up your device to try and see when the freezing starts to happen.
Click to expand...
Click to collapse
maybe its just my pc but the search tool here isnt working. which thread has walk through for returning to stock rom, rom selection and this task 29?
boltz said:
__yes______
Click to expand...
Click to collapse
Which rom? And it freezes when using android or booting winmo?
Sent from my HTC HD2 using XDA App
boltz said:
maybe its just my pc but the search tool here isnt working. which thread has walk through for returning to stock rom, rom selection and this task 29?
Click to expand...
Click to collapse
See here for returning to stock (Section 8)
Task 29 is here..
You can get the stock roms from the 6.5 ROM development section.
If you have a Tmous model then be sure to grab the right one.
Android SD card builds are sometimes a real pain in the ass for no obvious reason.
Just because one worked on your previous setup doesnt mean its guaranteed to run smoothly this time round. If you restored a backup with titanium or something similar then try running the build again from scratch without restoring and she how she handles...
i renamed and copied LEOIMG.nbh to sd card. powered on to bootloader and nothing... no instructions just color bands
boltz said:
i renamed and copied LEOIMG.nbh to sd card. powered on to bootloader and nothing... no instructions just color bands
Click to expand...
Click to collapse
if you're using a 16gb sd card this won't work, I'd flash thru RUU or use a smaller SD card.
Also on your Android ROM make sure you're not copying it via MAGLDR because it corrupts data transfer
M..N said:
Which rom? And it freezes when using android or booting winmo?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
booting energy21916sencity nov 24. then core_droid_evo_v0.8_desire.
I dont think it has anything to do with the droid version. It mostly freezes on energy splash screen.
orangekid said:
if you're using a 16gb sd card this won't work, I'd flash thru RUU or use a smaller SD card.
Also on your Android ROM make sure you're not copying it via MAGLDR because it corrupts data transfer
Click to expand...
Click to collapse
yes 16gb card is that problem. so do I flash stock rom , radio, spl all separate?
If you flash a stock ROM from the sd card then it wil overwrite SPL/Radio/ROM all in one go.
Try using a 2gb card.
If you dont have one you can always flash via USB.
boltz said:
yes 16gb card is that problem. so do I flash stock rom , radio, spl all separate?
Click to expand...
Click to collapse
flash task29 via RUU, then flash custom ROM via RUU, then radio 2.15.50 via RUU, then load the Android ROM via USB mode in WinMo or card reader, then try things out.
edit: flashing task29 takes away the need to flash stock, flashing stock then custom is pointless and actually worse than going task29 to custom, HSPL3 is probably not the problem here.
this is so frustrating!!! I've done everything to a T to get this phone back to stock and still wont boot. now stuck on "stick together" splash
boltz said:
this is so frustrating!!! I've done everything to a T to get this phone back to stock and still wont boot. now stuck on "stick together" splash
Click to expand...
Click to collapse
lol,
make sure it's the right stock, don't brick your **** flashing the wrong stock.
put it in bootloader manually by turning off the phone, then hold vol-down when you turn it on, while in bootloader hook it up to USB to PC, then run the RUU and reflash.
Personally I strongly suggest going task29 then custom, unless you want to return it to the store, just go stock.
i did the task 29 then flashed stock tmo 3.14.531 and spl and the radio 2.15.50.14 that was on it yesterday when i got it. it loaded once to stock initial setup and homescreen then froze again. this has to be a hardware issue. fuk a refurb
at least on boot screen it appears stock. requesting new phone
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.
Ok guys this is really frustrating. I have Android ROM and I want to try WP7 ROM. But every-time I install any ROM I am either stuck on GO GO GO or afterwards I am stuck on white screen with green HTC logo in the middle. I performed task29 before installing anything. I suspect on my SD-Card( I have Kingston 4 GB Class 2), so I borrow another one-Transcend 8 GB Class 6. And again the same problem, WP7 is is stuck on GO GO GO or white screen with HTC logo. What can be the possible explanation here? Anyone?
TnX
it could be a number of things, ive found the best way is to start again. SD flash an original wm6 stock ROM, then install hspl 2.08 > radio 2.15 > magldr 1.13 > os
take you SD card and download SDformatter, format it again
try again.
note that both your cards may not work and if you search you will find all of this info
Tnx mate, but I do the procedure 4 times without success. I still suspect that the problem is with the SD-Cards. Today hopefully I will try with SanDisk 16 Gb class 6. From what I read SanDisk is most used. And if this failed, I will flash stock WinMo 6.5 and reinstall everything again.
TNx
Sent from my HTC HD2 using XDA App
I have the same problem. Flashing complete in 100% but i can't pass the HTC logo when it's booting.
This is not SD fault because I have another device which is running fine...
Did task29, flashed winmo6.5, radio, hspl, magldr 1.13...
One phone simply can run wp7 and another can't ?
Ziaren said:
I have the same problem. Flashing complete in 100% but i can't pass the HTC logo when it's booting.
This is not SD fault because I have another device which is running fine...
Did task29, flashed winmo6.5, radio, hspl, magldr 1.13...
One phone simply can run wp7 and another can't ?
Click to expand...
Click to collapse
dont do the task29
SD flash WM6.5, HSPL, radio, magldr, flash OS
oh i wouldnt go with a class 6, whilst some folk have had working ones many more havent got it working, class 2 or 4 is best, just because its a class 2 doesnt mean its slower than class 6, infact many folk, myself included believe the class 2 and 4 is quicker
Did exacly what u said.
WM6.5 --> HSPL --> radio --> magldr --> flash YukiXDA'a OS
htc logo stuck
As i said i have another hd2 which is running on wp7 for a week... ive done exacly same thing to the both of them and one is not working... Is there something else what i can do?
Ziaren said:
I have the same problem. Flashing complete in 100% but i can't pass the HTC logo when it's booting.
This is not SD fault because I have another device which is running fine...
Did task29, flashed winmo6.5, radio, hspl, magldr 1.13...
One phone simply can run wp7 and another can't ?
Click to expand...
Click to collapse
Hmm, so your saying thatyou have access to 2 HD2s, running/trying to run WP7 and that one of them works with the SD card but the other doesnt work with it?
Ok I forgot to replay that I did it . In my case there was no need for stock ROM. I just:
1. Did task29
2. Installed WinMo ROM (In my case Dutty's V25)
3. Install MAGLDR
4. Install Wp7 ROM...and it works
dazza9075 said:
Hmm, so your saying thatyou have access to 2 HD2s, running/trying to run WP7 and that one of them works with the SD card but the other doesnt work with it?
Click to expand...
Click to collapse
Yep. Im doing EXACLY same thing to the 2 devices. Using the same SD card. First phone is booting and working second is not.
Tried about 5 times (to both of 'em to be sure). I have enough. This just can’t be done. Don’t know why. Maybe there is something wrong with memory? IDK... but this is extremely frustrating.
Ziaren, Do you have 2 SD cards with your 2 HD2s?
Have you tried with both sd cards on your HD2 that has this trouble?
Just a thought.
Good luck
Ziaren said:
Yep. Im doing EXACLY same thing to the 2 devices. Using the same SD card. First phone is booting and working second is not.
Tried about 5 times (to both of 'em to be sure). I have enough. This just can’t be done. Don’t know why. Maybe there is something wrong with memory? IDK... but this is extremely frustrating.
Click to expand...
Click to collapse
Have you tried to flash your stock ROM, then to re-flash everything? (HSPL, WinMo, MAGLDR and WP7)
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
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.