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!
Related
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...
Hi,
My VOX sometimes gets shutdown automatically. It happens at least once in two days. And whenever it shutsdown, I can feel that the handset has become slightly hot. I need to remove the battery and put it back to turn on the phone again.
But one strange thing I noticed is that, if the bluetooth was on when the phone went down, I can see the bluelight blinking even when the phone seems to be shutdown.
Do you guys know what could be causing this?
My Radio Version is 4..13.41_02.88.90 and OS is 5.2.1236 (Build 17741.0.2.1)
Thanks pals!
Sounds like it's over-heating possibly? If the BT LED is blinking blue, then the device is still on, I think you have some software that is either causing it to run at full load or causing a soft reset.
hum, maybe this has something to do with the problem already reported in some posts of some VOX's
the screen goes black, but the phone remains on
normaly if you wait a couple of seconds, and try to mess with the phone again, it will be alright,
sometimes i even have to remove the battery
some say the problem could be overheating as u say, but until now, i havent found any solution for this, i also am facing the same problem
Same problem for me when turning on the Wifi, but the phone turns off completly and the battery showing empty after turning the phone on, I have to remove the battery each time!
But when it's connected, my phone runs perfectly.
Maybe I have to change my battery, no?
I don't think in my case the phone is on (except for BT light blinking). Otherwise it should be in a big hung state where it is not able to respond to keyboards, power key or any interface at all.
Next time I encounter this problem, I will try calling my own number to see whether the radio is on.
I have been using this vox since last 8 months, but in the last couple of months I have encountered quite a lot of problems like radio repeatedly getting turned off, first call after restart hanging (not consistent but happens most of the time I restart the phone and try to make calls with in the first 20 seconds after bootup) etc.
Do you think an upgrade 6.1 would do any good?
Thanks again!!
I was having that problem too. I tried upgrading to WM6.1 and upgrading the radio, nothing worked. I sent it in and they replaced the mainboard, but now it seems to be worse. I just got it back though, so I haven't called them about it yet. I'm just looking around to see if it could be a battery issue.
My phone restart issue was mainly a hardware or loose contact issue. Once the phone fell down and after that whenever there was a long press on 0, * or # keys, the phone would restart.
After two days my phone fell down once again from my hand and this issue got resolved forever. Lucky me!
My S710 HTC original, shut down every day at 00.16. In the past was at 02.46, and I discover it since during my trip in asia I found the phone off.
More over the alarm is not reliable and cannot be used for this reason.
The following application are installed:
- Customisation from HTC for my operator TIM
- microsoft Office mobile upt
- pmCleanSP
- spWZTools
- Skype
- Tom Tom
HTC service told me to flash it with Rom update.
Any suggestions?
Thanks
Hello forum members,
would you please help me have the BT HTC S710 Original ROM? I have only seen the BT HTC S620, which when I tried to flash with to rebrand, blanked my HTC S710 screen. When I turn it on, only the two green lights come on either side of the phone ear piece.
It means that a hard reset is not visible on my screen, there is no tri-colour display either.
I have tried other ROMS, and get invalid id errors and error 270. I have tried Dr Gonzo and related ROMS.
It's now three days, no phone no pim, I am lost.
Thanks for your attention.
YOSEFE.
PS. You may PM me if convenient.
Hi YOSEFE,
I have the same problem
I tried the 620 rom and just have the 2 green LED's. I cannot get a bootloader screen and attempts to flash new roms get to 3% and then I get errors.
Did you ever sort this problem out?
Paul.
Have you unlocked ur USPL in ur phone?
You tried to flash a S620 ROM to a S710???? Look in the Wiki, there is a link to the official ROMs on the ftp...
frauhottelmann said:
You tried to flash a S620 ROM to a S710???? Look in the Wiki, there is a link to the official ROMs on the ftp...
Click to expand...
Click to collapse
Yes, I'm afraid I did, by mistake, flash 620 ROM to the 710 [feels rather stupid!]
Not happy with BT’s [mobile operator] own ROM and software that went on the phone, I successfully flashed Dr. Martin Gonzo’s Windows Mobile 6.1 v1.1 and have been using it for a couple of months but when BT launched their new phone software, I decided to try it but because it won’t work with WM 6.1, I needed to then revert back to BT’s old ROM and this was the only one available that I could find [feels rather stupid again].
The screen is completely black; only green LED's on each side of the earpiece shows any sign of life.
Connecting the phone via ActiveSync shows “HTC-S620 Connected” and I am able to browse the files on the phone but not having a display on the phone, I am limited to what I can do.
I have tried running RUU_Vox_HTC_WWE_1.34.405.1_4.1.13.54_03.10.90_Ship.exe but ActiveSync connection is lost and I hear the Windows hardware removed sound shortly after the progress bar is shown.
I’m at a loss as to what to try
Paul.
Shut it down, then hold down camera button and plug in the usb cable. The boot screen should appear and you should be able to flash the normal ROM!
I cannot get the boot screen, or any screen for that matter.
I have tried taking the battery out to make sure the phone is off. Reinserting that battery then holding the camera button down and then inserting the usb lead. The keypad lights up for a few seconds then goes out. ActiveSync then connects but the screen is still black
Paul.
[Edited: Sorry duplicate post]
Sorry for replying to my own post but a quick update...
I have managed to bring the phone back to life and reinstall Dr. Martin Gonzo’s Windows Mobile 6.1 v1.1 on it again.
This is partly assumption and not particularly accurate but the original poster (YOSEFE) might find this useful.
By installing the S620 rom on the S710, not only did I make the screen go blank, I think all the keys ended up remapped and mixed up, therefore any attempt to install Gonzo’s rom ultimately ended in failure because when the phone beeped and wanted a keypress to continue, pressing the left softkey for ‘OK’ or ‘Yes’ did not work because it had been remapped to do something else.
What worked for me is that when the phone beeped during the uspl_116_jockyw.bat install, I pressed the X or C key (I can’t remember the exact one now). One of these keys must have been the ‘OK’ or ‘Yes’ key after the S620 rom muddled things up. I only know this by trial and error over the period of today.
To my glee, the backlight lit up on the display and after a bit of tinkering, I’m back in action again
I won’t be installing a rom designed for another model again!
Paul.
Bat 'n' Ball,
sorry for not returning here to see your post. I will remember the possibility of pressing "X" or "C", should I make the same mistake as before, although like you, I should never do that ever again. However, technology being what it is, who knows?
In the end BT got me sorted out.
Thanks for sharing.
I have a 4155 that has developed the following problem: most of the times it doesn't turn on correctly. I press the power button, I see the backlight coming on but the screen stays grey (blank). Eventually I can get it back on, but only after performing a hard reset, then many, many soft resets (anywhere between 10 and 30). Then it works again for a little while, and the whole thing happens again.
The only way to avoid it is to have the screen stay on all the time, i.e. keep it plugged in and have it not turn off while on AC. If I allow the screen to turn off, chances are I'll have to do the whole reset procedure again, and it takes up to 30 minutes each time. It doesn't matter at all how well charged the battery is, and it even does it if I allow the screen to turn off while plugged in.
Of course in its present state it's just a little more than a paperwewight, not a PDA. I know that underneath it works correctly, just the display has this weird bug. I opened it up and poked inside, put it back together - no change. Does anyone have any idea? I'd really, really like to make this work again.
Thanks for any help!
(I should mention that I flashed the ROM once: I got it cheap off eBay because it was the French language version, and I flashed it with the English ROM. Worked like a charm for many months, then it developed the problem above. Don't think it's related to flashing, but thought I'd mention it anyway)
Bump. .
I'm not sure how many people, if any, have experience with this phone, but I'm taking a shot in the dark because I am completely out of options here. The phone is similar to the Cect M88, and the other Cect iPhone-clones available, although I'm not sure how similar the button layout is.
I installed PCM Keyboard last night, and all was working fine until this afternoon, when all of a sudden, my phone wouldn't wake up. I ended up having to pull the battery in order to get it to restart, but then it wouldn't boot past the Windows Mobile screen (the first one - didn't even make it to the second screen).
After several attempts to hard reset (top volume button + camera button + power button), I was able to get it reset, but even though active sync was running, folders weren't showing up properly on the phone itself. I did a soft reset, and folders then showed up, but this time active sync wouldn't load on the phone. Several more soft resets did nothing, but I kept trying, and finally... the phone froze up again to the point where it hung on the Windows Mobile screen again. Now, despite all attempts, I can't even get it to hard reset. When I push all buttons from an off state, the screen will turn blue (which seems to indicate some kind of resetting is going on since it normally goes straight to the WM screen) and then a few seconds later, the Windows Mobile screen will come up and hang. I've tried every combination of buttons possible, and I've tried hard resetting probably a good 20-30 times since this happened. I've removed the SIM card, removed the SD card... I've basically tried hard resetting seemingly every way possible, and yet it still will not reset and load up WM 6.0 pro like it should.
Any ideas on how I can get this thing to at least move past the WM screen? If I'm totally unable to hard reset, what would be the next best course of action? Since this is an off-brand phone with no support or any kind of warranty, are there repair places out there that can restore the OS? Is that something I can do myself? (Phone didn't come with any software or anything.) I'm at a loss here... I really don't want to end up with a $200 blue flashlight/paperweight. I know I took my chances when I bought it, but well... this stinks.
worked
hey man i know its old and hopefully you still have your phone.. ok what you need to do is let the phone die completely so you may have to keep the blue screen on and keep turning it on till your phone does this like you i have hard reseted serveral time to no avail but when the phone died i took out the battery plugged it in to the wall charger placed the battery in the phone let the red led light by the camera light up then i turned it on and before the screen could show the splash i did the hard reset phone is aye ok !! hope this helps man.. your post helped me..
eric