Hi,
I have an ipaq hx2790. Last time, it was completely out of battery ( this happened several times before, with no troubles at all). I charged it overnight.
After fully charged, I turned it on. It turned on normal. But when status bar ( the small bar running left from right when booting) run for about 1/10 of the whole bar. The screen slowly appeared small dot with different colors, and then lines, after all, it became green-dark color with vertical lines.
I tried to soft-reset, hard reset. The same thing happen. Funny thing is, when I connect this device to my computer, I can still browse it folder, SD card through Windows Mobile Based Device in My Computer.
My hx2790 is preload with WM5
First, I thought it's something to do with software. But after soft-reset, hard-reset, same thing happens. I tried to install WM5 official rom for hx2790 from HP. No thing changes. Screen ok at the very first part of boot up. Getting worse after that. I can still browse it folder from computer.
P/s: It was once, booted normal into windows mobile screen (but after about 5 seconds, its screen slowly become worse).
Anyone have any ideas what's happening?
Thanks.
You can try to flash WM6.1 for HX2000 series to see if the same thing happens:
http://forum.xda-developers.com/showthread.php?t=383173
If there's the same - then probably LCD is bad or there's something wrong with motherboard.
I'm downloading the file.
I dont know whether it's LCD problem 'cause when at the very first of booting and in Pre-BL mode, it displays perfectly. Especially in Pre-BL mode and during the ROM update process, nothing's wrong with it.
I'll inform the result with this new ROM soon
Thanks.
Ok
I have had similar problems when there is something wrong with Windows upadate (ROM) file. Screen just fades out on starup
ROM Update was successful but can't help
Related
Bonjour
I upgraded to WM6 (pdaviet) 2 months ago (I guess..), and problems started to appear a few weeks ago. First it just was hard to boot sometimes, had to reboot several times to get it up and running, but when it could start everything was fine. Then since yesterday, it became harder. And today, couldn't start it at all. Tried several times, and everytime the screen went melted, corrupted, like if it couldn't stand an o/c, but it always runs at normal speeds. I guess it has something to do with the battery and the way WM6 handles it (or at least the implementation we have on our prophet).
I tried to hard-reset, I left it a long time on the format screen (before the actual HR) and it handled it for long enough, but the same thing started while setting up WM.... too bad !
While writing this message I tought I could try to downgrade, and I did using AKU3.3-Jester-b1.
I had no problem while the phone was in guest mode after the HR.
Everything went nice during first step upgrade, but on final reset it did the same thing, and now..... it cannot start at all !!!!
Someone has an idea ? I own a G4 and it has the following roms :
IPL 2.10, SPL 2.20, GSM 2.47 (or something like that)
It won't charge (but my batteries are full, I've got an external charger), it won't start from battery nor from power, even if the battery is removed.
Damn, at least I guess I can return it like that to orange, since it cannot start one can't see the modified rom...
If anyone has a suggestion, it is more than welcome ^^
Thanks !
Niko
huh !
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
lastnikita said:
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
Click to expand...
Click to collapse
Hey LastNikita,
I had the same problem ! The white scanlines thing just after re-updating a WM6 version (pdaviet), because I was tired of the constant reset issue.. suddenly, the update went wrong, and I stupidly followed the "recovery" process, which tells u to remove the battery... bang ! screen went corrupted !
Like you, I tought it was over... but I noticed that if you connect your phone and PC with USB, and keep pressed power (ON/OFF button on side) + camera after reseting (little hole on bottom - press during 5 sec!), the PC recognizes a USB device (not the usual phone drivers...) at this moment, I launched the Jester 3.3 (step1) update, in order to downgrade from the ugly WM6 pdaviet... My phone was not yet fixed (still with white scanlines), but at least, I could hear again the WM "start" sound, the scanlines would also "move" across the screen borders when I touched the screen, which made me imagine I was on the calibrating process... also, while connected to PC, after a while, ActiveSync would launch, asking for 1st time synch... this kept me confident as the phone (software) seemed to be reacting fine although HW prob...
I completely charged the phone again (till green light) then kept on reseting the phone (until I hear the WM sound) hoping the lines would finish scanning and come back with the normal .. and guess what, it did !!! Of course, PIGHEAD as I am, I wasn't totally happy it recovered with WM5, so i digged for a better rom, and I can tell you I'm very happy with the smart1 (wizard version) which works fine, but still has some minor bugs as Live Messenger not working... but runs fine (specialy when pressing the ON/OFF button !
PS: Make sure the ALWAYS completely switch off your phone (ON/OFF for 3 secs) before removing the battery... it did happen again... when I stupidly trusted the "recovery" process, again !
DUHHHH !!!!
PS: at least, now you ALL know !
Kokiri
Finally ok for warranty )))
Thanks for sharing mate
I finally managed to downgrade to my original Orange rom, and I'm in the process of putting the original Orange splash screens back (I made the nk.nbf but I can't find the right utility to upgrade... "Update utility cannot open the requested file").
BUT I still have that HW problem afterall.... so I guess it still has to go back to warranty right ? This isn't a big deal since Orange is VERY prompt (I guess I'll get it tomorrow or monday morning, the delivery guy brings a new one and goes back wiv my phone, quite nice !), and I have a button which is stucked (from the begining) anyway ^^
While I'm writing this my phone is docked and synced, and it seems fine.... but, I guess, as soon as I will reset it will start over again.... I'll keep you posted.
Anyway, I'm no longer desesperate and that's good news (for me ^^)
++
niko
yip
ok, everything's back to original.
Actually, it works well when docked, but it freezes/melted screen as soon as I tried to use it on battery, so that I'm quite sure it has something to do wiv WM6.... I'll post that on some crossbow threads this weekend if I have time enough (there are so many of them now !)....
But once more, if YOU read this, keep that in mind.
Hope you guys won't have that kind of failure while trying it.
++
niko
confused
I am having the same problem except the screen showing white scanlines everything else is working on the handset. Could it be a LCD Problem?
Me too...
I have the same issue (black/colored vertical lines and a white screen). I think it has to do with upgrading to WM6 or with overclocking with batteryStatus, not sure. This are the suspects in my opinion....
Now I downgraded to WM5 but the problem seems to persist, I disabled batteryStatus and will see if the situation improves... crossing fingers
Uhm ... possible Overclocked!
I have read 3 threads with same errors!
how much was your highes clock? do you use it for navigation? long time on highest clock or only for speed up?
i dont have a problem with scan lines but with my prophet i use the scaling option and go max to 234 i also set to 234 when using certain apps.
is this damaging to my prophet?
at the moment trying to upgrade to PDAViet 4.0.0.0.3 with a world of pain but thats another topic!
Ok, so far I've dumped the ROM and uploaded the kaiser-HardSPL and all was going lovely. However, after most of a day of pretty much inactivity I find the device suddenly goes very slowly. By which, I mean it can take several seconds to draw the screen.
Thinking this might be a rogue application using up all the processor cycles, I poked it up the bottom with the stick. (While doing this the first time, I held in power and camera just to see the boot loader text, but then I did it again with no buttons held.) It's a Vodafone device but it sat on the Vodafone splash screen for about 2-3 minutes then spent longer than that on the Windows Mobile screen before eventually dropping me into normality.
Except it's incredibly slow normality - I clicked on "start" and after a minute, it's not done anything yet.
Next step is a hard reset unless anyone has any better suggestion?
Help!
I assume you've pulled the battery?
Never assume anything... The full answer is, "No, but I have now"... I'm not sure that's going to do anything more than a soft (poke up the bottom) reset though. I'm now just waiting for the splash screen to subside while I'm typing this.
Having left it half an hour, while it went into standby and after noticing that the clock had stopped updating, I'm of the opinion that the already slow device has got slower...
Ok between 1 and 2 minutes to move from the splash screen to the "Windows Mobile" screen.
Now there's a turn up... After a further minute or so, I get a message, which has now cleared and gone back to the "Windows Mobile" screen before I had chance to copy it here. Basically it said that it had failed to boot either because I'd turned it off improperly or I'd installed something that it was opposed to. I should press send (I guess the green button) to reset to manufacturer's defaults.
Since that's my next stage anyway, I'll re-poke it with the pointy stick and press 'send' when it pops the message up. I'll put my trusty old Nokia N73 into flight mode and take a picture of the message so I can transcribe it here for everyone's amusement.
More news as it breaks.
I've now hit the 'send' button so it's doing a hard-reset. Meanwhile, here's the text it showed me:
Code:
The device is unable to boot be-
cause either you have turned off
the device incorrectly or tried to
install an application from untrusted
source. Press SEND to reset your
device or press any other button
to cancel. This operation will delete
all your personal data and restore
the device to its factory default
settings.
Nice. Ok, I'm at the 'tap the screen to set up your device' screen now.
Wonder what triggered all that nonsense then...
If you're like the rest of us and tooling around the all the fun programs in this forum, there's no telling.
I tell folks on computers, "Every piece of software you put on a machine is a liability to the operation of that machine." We can say that applies to this nifty little devices too.
I've had my phone experience the same symptoms you have posted here. Luckly for me a battery pull fixed mine. Sounds like the luck didn't spread much. Sorry.
Keep at it though. And don't fret the crashes. They do happen from time to time when you play hard.
So, a hard reset and a restore of a backup (Yes, I made a backup a few days ago even though I've been in the trade 20 years!) later, I'm back to normality. All I've done that's weird is install pof's loader and I can't see that's anything to do with it. What I was doing at the time of the slowdown was trying to connect to the wifi network at work. I thought the networking had just got itself tied in knots somehow but as the machine was even mega slow to boot, I can't really see that. At least I can still get back to square one at the moment.
I just need to create a .nbh out of the rom parts I dumped yesterday so that I can recover from anything more major...
Meanwhile, if you do a 'boot loader reset', would you expect it to say 'serial' if the USB isn't plugged in?
I'm starting to wonder if there is a major bug in the WiFi of the Tilt. There are some other threads on AT&T's site about this, and my work with WiFi on this unit has been dicey. Hmmmmm...
Hello all,
I'm hoping this can be fixed, for my fiancée's sake, as she has alot of pictures and videos of our little boys when they were born and can't be replace on her Treo 750v, unlocked via code from Voda, it's still running WM5.
It started when she was sending a text, press sent, and randomly, parts of the list of messages starting turning into blanks, around that time it popped up saying low on memory, she deleted a installer cab for facebook, and the little busy circle appeared but did nothing and crashed the phone, so she took the battery out, put it back in and now all it does is boot with the Palm logo, goes onto the Windows Mobile splash screen then blank, pressing red brings the keyboard light on and makes the key sound, but doesn't do anything, all with the blank screen. The orange light flashs for loss of signal constantly, but the red charge light doesn't come on at all, and ActiveSync doesn't pick up anything. I can boot into the bootloader screen, which behaves as it should, getting picked up by windows. I have tried itsutilsbin, but does nothing as ActiveSync isn't initiated to try and pull the files off the device. And Google has only so much information.
So I'm pleading (nicely ) is there anyway to get files off a semi-bricked Treo? I am competent playing and messing around with flashing and upgrading, and willing to try anything to get all the files off it.
Hope someone can help!
how many photos can you fit on a palm without a memory card cant to much can it. Well have you tried ringing palm and ask them if they have data recovery. there is one very very very long shot like 1% chance that it will work and do not do this if you can not find a data recovery program for the palm is hard reset it if you can then run the data recovery software. I do repeat 1%!!!!!!!!!!!!! I say ring palm see what they say.
I've seen a few similar issues on the web with various devices... I believe mine to be a bit different though.
Before today my Blackjack 2 (Windows Mobile 6.1) worked perfectly fine, it fell today and the battery went flying out of the phone. I put it back together and it was working fine. a few hours later i realized the phone shut off on its own. Well, it does that sometimes for me since it is over 2 years old and is quite beat up, so I took it as normal behavior, i started it up, and…. it hangs on the windows mobile green splash screen.
Whenever I shut it down, the loading circle that normally pops up, shows on the screen as its shutting down. I've actually gotten it to show the status bar (signal strength, battery, etcetera, however the rest of the screen remained at the splash screen.
Bootup process: it shows the Samsung splash screen, then the AT&T animation, and then the windows mobile splash screen where it finally hangs. When I plug it into my computer using the data cable, it dings on connection, and my computer starts to connect, but then errors out.
I'd like to try to avoid a hard reset or re installation if possible… just added a bunch of contacts that I haven't backed up, and I don't know their numbers off hand, so I'd have to wait for them to call/text me or until i see them again.
Also, if I have to perform a hard reset, I'm unsure if the phone will actually work after-wards since this did appear to begin after it hit the ground.
Since installing WM 6.1 I have not installed any software/programs/apps on the device, just some new contacts. It's not the sim card, my friend has the same phone so I tried it out on his and it worked fine.
Anyone able to advise on this?
Sorry for the double post, decided to format anyways. I have a trip tomorrow and absolutely needed a functional phone. It is now functioning perfectly fine, boot time is a bit longer than usual but it does boot.
Any idea what could have caused this and how to avoid the issue in the future?
Hello,
I'm using my TP for two months and there were no serious problems with it since now. Today I was looking for some things by Opera browse, when - suddenly - SMS arrived [yeah, that sort of things happens]. Because of my ability to destroy everything connected [bad word..] with electricity, WM [original ROM, version 6.1] froze - after few minutes it was still insensitive to any touch [and button, including 'power off'], so I pulled out a battery and turned device on. And here starts the drama - Windows didn't want to boot, just showed green sreen with WM logo, part of start bar and stayed like this for long. Now, having some more resets done, it freezes on the green screen, not showing anything else.
Ok, I know that probably the best solution would be hard reset now [actually I guess, never did it before, don't even know where to get a 'new ROM' <- don't see it on included CD]. Of course, but I have some important data there! If there's any other way to do it, or - at least - to get back things from main memory [especially messages and contacts], please tell me how. I repeat once again: it's very important for me.
Thanks in advance,
m.