CANCELED- see second post
So, I am a regular at the kaiser forums, but i recently got my hands on an 8125. I am not a complete noob, but i don't have much direct experience with this phone yet. the problem is, the screen has a crack and displays nothing. the device turns on, and i can get it to make noises, such as the voice command and shutdown, but i cannot get it to connect to my pc via activesync. i have v 4.5. i believe this to be because the previous owner had a pin # set. I would like to do a hard reset, connect it via active sync and load soti pocket explorer so i can see how well it still runs, and whether purchasing a new screen is worth it. i have read all the posts/wikis i can find on hard resetting this device, however, they all assume you can see what is on the screen. can someone give me a detailed report on EXACTLY what happens? how long it takes, what lights flash when, etc?
thanks!
cancel
cancel that, just got soti installed. everything looks good, aside from the screen. anybody know a good place to get one, or is somebody selling one?
i have a spare wizard screen that i know works if your interested
Related
any help is gratefully received.
i was doing a rom update(pugs) and the unit has become stuck in what i think is bootloader mode. the screen is dark and displays "serial v1.01
after much searching on this forum i tried to hard reset then run maupgradeut again.
problem is that activesync no longer detects my device.
ive tried pressing power/reset/action buttons to no effect.does this mean i now have a pretty coffee coaster.
now you were at bootloader mode. try remove the device n put it back on cradle, for sure windows will detect it. after that, try run the upgrade again. The problem that you're having now are same like me when I first bought my device. The answer is good being a newbies n ready to ask question at here. hahahahah
thanks
now youve hit the nail squarely on the head. i thought i knew enough to update but when its gone boobies up realised i dont.
ive tried resetting the device and then connecting to my pc several times with no success.
anyone know how to take the device out of bootloader mode. im hoping theres a backup stored on the device that will boot...or...anyone know how to get the pc to recognise the damn thing before i launch it out of the window(all the way to an o2 shop).
im sure im not alone(can hear the voices)
took some brain power on my part. turns out microsoft activesync was the problem.
upgraded to the latest version and everything went as it should.
I've got a problem with my XDA Mini S. It's been sitting in a box in my shed for about a year, before I got it out yesterday to have a play around with it, and possibly try some software I found on it.
I put my sim card in, plugged it in to charge, and turned it on. It worked absolutely fine.
I haven't done anything with it yet, but I've turned it on now, and the colours are messed up on the screen. For example there is a red hue over the today screen, and on certain screens (like in bootloader mode) the colours appear to be inverted (I will post pictures later if needed).
I've tried reformatting the device, but this has not fixed the problem. I thought I would try reflashing the rom on it. I used to have the original o2 rom on my old laptop, but lost that when I had to reload windows.
I downloaded the original rom from here, along with the Rom Update Utility, and attempted to reflash it. It gets as far as 'verifying the information on your PDA phone', then crashes with the error: Rom update utility MFC application has stopped working.
I'm running windows vista on my laptop, and read that the RUU won't work until the drivers are updated. Following the instructions on mrvanx.org, I have downloaded the driver for vista and installed it, but i'm still getting the problem when I try and reflash the device.
I've also tried running the RUU in compatibility mode for XP as it worked fine on my old laptop which was running xp, but it still crashes, every time.
I'm beginning to wonder if reflashing it will even work though, since the colours are messed up in bootloader mode as well, which leads me to think it may be a hardware problem.
I know next to nothing about repairing these though, and probably wouldn't bother if it's a hardware problem, but until I can reflash the firmware, I won't know whether this is a case.
I'll get the photo's of what the screen is like uploaded to my server later on, and post the links here, so you can see what the problem is.
Photo's now available
I've uploaded a couple of photo's to show what the screen is like:
http://csc2ya.co.uk/images/bootloader.jpg
http://csc2ya.co.uk/images/startup.jpg
Update
i've got my old laptop out, reloaded xp on that, and attempted the flash using that. However, I get the message 'rom update utility MFC has encountered an error and needs to close'
I just want to get it to reflash to see if it fixes the screen, but so far i'm having no luck at it.
I've sucessfully reflashed it in the past with the o2 rom using my old laptop, so I can't figure out why it isn't working now.
Update: I didn't have activesync installed on my laptop which was why the updater was crashing. I've installed activesync, but now i've got another problem that is preventing me from reflashing it. I start the updater, and click through the prompts. It gets to 'verifying the information on your pda phone', stays like that for about 30 seconds, then activesync disconnects, and I get the error: microsoft activesync cannot recognize this device for one of two reasons: then the other information that the dialog gives. I'm not going to bother typing it all out, as i'm sure nearly everyone has seen it at least once before.
Additional info: No idea if this is relevant or not, but the extended rom has been formatted using the service tool.
Another update: I have now managed to get the device to reflash, but it boots up afterwards as if I had just turned it off and back on again. I have tried a hard reset afterwards, but cannot seem to get any of the o2 stuff back. It appears that the screen problem is hardware related though, as it is still present even after reflashing.
I can also no longer get it to go into bootloader mode, but the phone will still boot normally.
csc2ya said:
It's been sitting in a box in my shed for about a year.
Click to expand...
Click to collapse
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.
Myrddin Wyllt said:
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.
Click to expand...
Click to collapse
The battery appears to be fine. I charged it overnight, and it still seems to hold a decent charge.
I haven't really got the tools to dissasemble it fully, but I will give it a go sometime in the next few weeks (i've got a copy of the service manual on my computer, so that shouldn't be a problem).
I only really got it out to play around with it again, and possibly try some apps on. It still appears to work fine apart from the screen (and the o2 applications now missing due the extended rom format, but i'm not bothered about those). I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Thanks for the suggestions anyway.
csc2ya said:
I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Click to expand...
Click to collapse
Well, this certainly changes things. You have a bad screen, or a bad connection to the screen. You can get replacement for around $100USD, or you can try to get a broken unit with a good screen for less (maybe). I'd still disassemble it first, though, in case it's just a weak connection.
Hey guys, I bought an 8525 on ebay today with the following problems:
* Fail Test Call
* Bad LCD
The seller wrote "The phone Powers Up in that the light in the Upper Right Corner lights up but nothing appears on the LCD screen so I have no idea if the LCD is Good or Bad."
Do either of these issues seem like anything any of you have encountered/overcome? I'm more worried about the LCD think than the failed test call because I'm pretty sure flashing a new rom/radio will fix that issue assuming it is an issue at all. All help will be appreciated, thanks guys.
nobody? come on guys i have looked through these forums and haven't found any solutions... any ideas at all would be helpful. thanks..
chbearsrock said:
Hey guys, I bought an 8525 on ebay today with the following problems:
* Fail Test Call
* Bad LCD
The seller wrote "The phone Powers Up in that the light in the Upper Right Corner lights up but nothing appears on the LCD screen so I have no idea if the LCD is Good or Bad."
Do either of these issues seem like anything any of you have encountered/overcome? I'm more worried about the LCD think than the failed test call because I'm pretty sure flashing a new rom/radio will fix that issue assuming it is an issue at all. All help will be appreciated, thanks guys.
Click to expand...
Click to collapse
Did you try powering up by soft-resetting? My phone failed on me, only once (to date), where the normal power-cycle button didn't work. Using the stylus in the reset-hole turned it on, and I then hard-reset and restored from a backup, and everything was fine again.
To see how much of the device is working, why not hook up to ActiveSync and see if anything other than the LED is working? If so, using some remote control SW (if you can install on the device) might let you test some of the functionality. MS Remote Console Display only requires a single executable file on the device (which you could place there with AS), but I don't know how you'll get past the initial startup and setup clicks.
It sounds to me like you might have bought a device that could be more suited to parts farming, if you're not up to opening it up and doing some micro-surgery. I wouldn't gamble on the test call being fixable with a radio rom flash, but heck, it's worth a shot. But then again, I might just be being pessimistic.
Good luck in your endeavor,
-pvs
PS: You might want to have a look at this thread. Sounds like it might be a similar issue, although it has not led to a successful repair. :-(
thanks for the response! i hope that the reset button is the solution to my problems...wouldnt that be great? i'm not opposed to opening the phone up (i assumed i would have to) so if that doesn't work i will open it and make sure all of the ribbons are in correctly...not sure what else to do...thanks for all your advice though i'll be sure to follow your steps as soon as i get the device (hopefully by saturday).
i'll keep this post updated.
ok so i said i would keep this post updated (though i don't think anyone read it to begin with) so here's the update. I got the phone in the mail yesterday and it turns out that it does not turn on at all. When I plug it into the computer I get the red light (indicating no battery) but none of the fixes seem to work. I thought it would be a firmware thing but i'm now guessing that its a hardware issue, meaning i dont know where to begin. Unfortunately it looks as though its going right back on ebay...
tsk i upgraded the radio version after i fixed my phone to work invariably better from when i got it. i was so happy it was stable. i plug it in my usb and happily transferring files. i leave it and i come back decide to see what the fuss about the radio is so i decided to upgrade to the file HERM_Radinly_1.43.00 ... after successfully loading, not for long about 5 more mins plugged poof! disconnect sound. lcd faded. phone fried no red light when plugged. have two batteries so it's not the batteries. not the connections either. nothing. dead. tsk... and i was so excited.
chbearsrock said:
ok so i said i would keep this post updated (though i don't think anyone read it to begin with) so here's the update. I got the phone in the mail yesterday and it turns out that it does not turn on at all. When I plug it into the computer I get the red light (indicating no battery) but none of the fixes seem to work. I thought it would be a firmware thing but i'm now guessing that its a hardware issue, meaning i dont know where to begin. Unfortunately it looks as though its going right back on ebay...
Click to expand...
Click to collapse
I read that there's lots of tweaks for WM5 for the 8525, but then I seen mention of a WM6 available, too. I presume it's a free upgrade on the AT&T website, or elsewhere online.
Now for the questions. Which OS works best for this device? Do the tweaks made for WM5 work with WM6 as well? Should I upgrade to WM6, or stay with WM5? For the GPS (maps), does it work with both or just one of the options?
Now for other (off-topic) experiences I have with my new [reconditioned] device.
a) After inserting my SIM card, about an half hour later, I attempted to call an 800 number (to activate a new bank debit card), which it didn't fully connect the call, although the call timer was running. It wouldn't let me end the attempted call, either, so I removed the battery and reinserted it.
b) Exploring the device further, I noticed that some menus didn't close when I tap the "red X" in the corner. I even tried to expand (pull out the keyboard on) the device, but it shows the "red X" of the location from portrait. as well as from the landscape! For example, it wouldn't close the "selecting which size to send photos" option screen. After waiting about a minute, I had to remove the battery to get rid of those screens, which is a major pain to keep removing the battery!
c) Later on, the last phone call that I made wouldn't hang up (end call) -- I even tapped 'End Call' about 5 times, not to mention pressed the red phone icon on the main navigation keys about 3 times. I haven't used the device since, except to place my old Samsung Sync's memory card with pictures, songs, and videos inside it.
The device seems very slow to close/end programs, and I've just received it yesterday! [I have not hacked, tweaked, or done anything else to it, either; I've only set the time, date, and owner's info.] Is this normal for the 8525? Would installing the WM5 tweaks [HTweakC 2.1b] -- or updating to WM6 -- increase the device's response time and overall performance? Or do I have a still faulty, reconditioned 8525?
Sorry for the long questions, I just wanted to give background into the device. Thanks in advance for all help in this matter!
You seem to be way behind as you use WM5. First thing you do after reading this: UPGRADE TO WM6.1
Most tweaks of WM5 will ofcourse work on WM6. WM6 is faster and much much better.
Do you know about soft-reset? No need to take out the battery! Just soft-reset.
And most of your problems of hang-ing can be solved by newer version of Windows Mobile! WM6.1
In case if your new to upgrading, you may read my small guide. If your completely new to Pocket PC, this might help you too. Also, consider using a free taskmanager such as wkTaskMan to close applications completely.
Regards,
Carty..
Carty, thanks for the quick reply!
As a brief background, for about the past 6 months, I was infatuated with the HTC Tilt [8925], because of the built-in GPS, Wi-Fi, 3-MP camera, & media player. Later, from reading other opinions on the 8525 on this board and discovering that it was compatible with GPS services, I decided to "sacrifice" the 3-MP camera, as the 8525 was about $100 cheaper on eBay.
I am pretty new to the Pocket PC, as my cellular device; I have used computers since 1996, though. That being said, it's not even been 24 hours since I've tinkered with the 8525 (as the eBay one never worked at all). I take it that the 8525 is an older device, as I've seen posts dating back to 2006. I just bought one on eBay 2 weeks ago, and had it replaced at an AT&T repair/replace shop yesterday.
I see the reset button on the bottom of the device; I just didn't know when to use it. I presumed it could only be used if the device wouldn't turn on at all. [As you can tell, I'm overly cautious with my new cellular equipment.] Also, I read about the "hard reset" -- holding down the 2 option buttons on the front and then the reset on the bottom of the device; however, I didn't know when to use the hard reset, either.
I will read your tutorials, then will install WM6 ASAP. Then, I will return with my findings. Wish me luck!!
Now I'm having issues with the update of WM6! The device stalls at 11%, then the software returns with the following:
"ERROR [262]: UPDATE ERROR
The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the errors so you can continue with the update."
I tried the [Recovery] button 2 more times, following the screens to the letter, but with the same result . . . the software stalls at 11%.
Any ideas? This is very frustrating!!
Man, I finally got it to install WM6! I had to literally remove every single program that was running under my "name" with the XP-MC OS. I even had to "Ctrl+Alt+Delete" the Explorer program and then "open" it (via Task Manager) again! [I didn't restart Windows, though.]
So far, it's back to the align screen, so I'll hope all goes well from there! Be back with more later!
I've made one phone call so far, and it actually did the end call promptly! Thank goodness for small favors! I thought having to do the "flash" about 6 times would have fried the device!
Now that I have the WM6, how do I install the tweaks? Do I copy them to a memory card, to the cell ROM, or something else? I already downloaded "HTweakC 2.1b" but haven't done anything with it yet. What would be my next step to correctly hack the WM6 8525 that I have now? I am a novice at hacking, so talk in layman's terms and please bear with me!
Hello all.
I have a HD2 that I havent done anything with, exept getting and installing some small programs.
No new ROM, no attempt to install W7, its more or like a Virgin.
However I made a fool of me, and managed to damage the LCD and finally got it changed. Got the Phone back from the company (MBlue Ltd in UK), and tried to start it up. But No....
Pressing ON, the phone vibrates, gives some light in the screen, sort of like you see its ON its a "white glow", but you dont get any more. The Jingle comes on, theres light in my buttons at the low end of phone, and NOTHING more.
I have had it on for long time, but nothing....
When I finally sendt the phone away, the battery was discharged, but as I have a new battery I put that in, and it charges and all.
Ive studied this thread: forum.xda-developers.com/showthread.php?t=638210
But as I CAN charge I fell that Im somewhat related but not fully in the same situation as the Original Poster there.
# Could it be that my phone somewhat has gotten overheated or anything else?
# Is the only and best solution to send it to HTC and let them look on it?
Ive tried to HARD and SOFT reset, but still nothing.
[EDIT] Connecting the phone to my PC, It is recognised and its recognised as a HD2 T8585
Looking more and reading more on the Forum I suspect theres a problem in the connection between the "fx-card" and the screen. (stupid way of saying it though)
Glad for any input here. Thanks in advance.
Tom
Flattop said:
Hello all.
I have a HD2 that I havent done anything with, exept getting and installing some small programs.
No new ROM, no attempt to install W7, its more or like a Virgin.
However I made a fool of me, and managed to damage the LCD and finally got it changed. Got the Phone back from the company (MBlue Ltd in UK), and tried to start it up. But No....
Pressing ON, the phone vibrates, gives some light in the screen, sort of like you see its ON its a "white glow", but you dont get any more. The Jingle comes on, theres light in my buttons at the low end of phone, and NOTHING more.
I have had it on for long time, but nothing....
When I finally sendt the phone away, the battery was discharged, but as I have a new battery I put that in, and it charges and all.
Ive studied this thread: forum.xda-developers.com/showthread.php?t=638210
But as I CAN charge I fell that Im somewhat related but not fully in the same situation as the Original Poster there.
# Could it be that my phone somewhat has gotten overheated or anything else?
# Is the only and best solution to send it to HTC and let them look on it?
Ive tried to HARD and SOFT reset, but still nothing.
[EDIT] Connecting the phone to my PC, It is recognised and its recognised as a HD2 T8585
Looking more and reading more on the Forum I suspect theres a problem in the connection between the "fx-card" and the screen. (stupid way of saying it though)
Glad for any input here. Thanks in advance.
Tom
Click to expand...
Click to collapse
Does your computer synchronize with your phone(connecting to activesync/mobile device center)? Then it is booted in Windows Mobile, the possibility is that the screen is broken then.
I thought the Screen might not be properly connected, or broken yes.
I better get in contact with the repair company.
But if other too have opininons, please bring em on... ;-)
Returned to repairplace, they fixed it.
My best guess is thy didnt check their own repair so they had to connect/fix something.
Flattop said:
Returned to repairplace, they fixed it.
My best guess is thy didnt check their own repair so they had to connect/fix something.
Click to expand...
Click to collapse
Good point, they're responsible for their repair: it is better this way because it's possible they damaged something while repairing and that part, if needs replacement, it should be their obligation, not yours!