Related
Hello Everyone,
I have a Cingular 8125 with the original 2.25ROM. Every once in a while (about once a day), when I try to press the power button to return my phone from standby, the screen will not light. The green LED light showing that the phone is powered on still keeps blinking, but the screen will not turn on, and I have to soft reset my phone with the reset button on the side, or remove the battery in orer to get my phone back working.
I have done a hard reset and this problem has not changed. Does anyone have this problem, or seen a fix for it? I am thinking it might be a problem with some of the reg tweaks I have done, or with a program.
The problem programs I am thinking may be contributing to this are Wisbar Advance due to memory leaks, or PPCProfilesPRO. The only real reg tweaks I have done are Molski's Customizing tweaks and the A2DP hack. Could it be a hardware issue? Any help would be much appriciated.
Thanks.
Sorry I cannot help more, but I remember Wisbar Advance doing that to my h6315 WM2003 based device. Then again, it would sometimes do it on it's own too (but very rarely w/o W.A). I hacked it to make A2DP work, and it did not cause such problems on it... but again, totally different device, but similar CPU.
Help!! - I somehow registered Omapclock at 300mhz and now my MDA simply reboots all the time. A few times I was able to randomly pound the keys to get to the today screen, but then the device would turn off and reboot. I usually get to a few seconds of the Windows Mobile screen before it starts all over again.
I thought I could try to just reload the stock T-Mobile rom, but Active Sync will not recognize the machine in time before it reboots. Is there a way to reload the stock T-Mobile rom from the Mini SD slot. Do you think it is rebooting so quick because the MDA is heating up so much quicker because of the higher mhz speed now?
Is Omapclock even causing this or is it possibly something else (I did nothing else except the omapclock mhz screwup).
All I want to be able to do is either get to the Omap unregister screen or reload the stock rom. TIA
Two options to try...
1) Hard Reset
2) Put the phone in bootloader mode (Turn it off, hold down the camera key and then turn it on) and flash a new rom (active sync won't connect but you can still flash a rom)
I knew about the hard reset via software, just discovered the 2 button / soft button reset. Kind of hard to do with my uncoordinated fat fingers, but finally got it a hard reset and clean slower rom. No more 300 mhz for me!!! Thanks for the quick reply!!
Be glad that you were able to perform the hard reset. A few Wizards have known to become bricks due to extreme overclocking.
I'm happy that your's wasn't, at any rate.
hi
I like to know how to "hard reset via software" .
and hardware
can you please tell me?
Hi Everyone,
I'm having some issues with my P3600.
Sometimes (to many times in the past days) while making something on it, the image on the screen suddenly mess up (freezes and weird image) and hangs. Then after the soft reset, somethimes the image stays black, and finally on the 5\6 try it boots fine...
Also noticed that this occurs more while connecting the usb cable jack to sync...
Already make some hardresets and some rom upgrade tests... Also tryed some wm61 cooked rooms, no luck.
Anyone already got this? I think there's must be some problem on the flat cable that connects the lcd-board. Can anyone help me whit some more ideas... before I decide to open it?
Thanks In advantage
SteelwarrioR
it happens the same to me... the pixels all messed up... i dont know wath is the problembut i think its the flat cable ... becouse i have open it one time 3months ago and now its fine. now yesterday have done the same thing
sorry my english
Ok, I open it last night based on the service manual I found somewhere on the Internet, the flat cable looks fine... Now this morning this same situation occurred again, this time while unplugging the usb charger. I Think there's must be some problem on the usb connector. The usb connector is part of the main board so it could be a hardware board issue? Anyone got this on problem on Trinity? Any troubleshooting tips ideas will be appreciated...
SteelwarrioR
hi,
same here. trinity hangs up after some time, screen stays black, when i try to wake it up.
have to hard reset several times and it wont boot for some trys, then with luck the windows sometimes finaly starts. I already changed the simcard and removed the sd-storagecard.
The vodafone hotline adwised me to send it in. Seems to me like a hardware issue.
My trin is about 1 year old.
(sry for my bad english)
Andi
No solution Yet???????
hi,
same here. trinity hangs abouth 3 or 4 time a day, screen stays black, when i try to wake it up.
have to hard reset several times and it wont boot for some trys, then with luck the windows sometimes finaly starts
hi, the same to me... it's like the rom's, after a few soft reset couldn't find the necessary files to start again.... and sometimes, after meny tries, it starts well... it's like the ppc processor gets tired and goes to stand by..... it starts freezing the display, and loosing some pixels. so the only things to do is soft resetting the device... any solution? thanks
same with my htc - it appears to me that the errors occur when the trinity was used for a while and the processor was getting warm. the files and folders on the sd-card show strange symbols. but i have also problems when i stick out the sd-card completely.
i will send it to htc repair center - i just hope that they will not send it back as the errors occur only frequently.
so long,
bjoern
solution solved
take taste power and center ok reset take few sec to powering and phone starting
or power and run and stop call reset and phone starting on factory powering
not solved at all
sorry no - this is not the point - i think all guys here have (hard- and soft-) reset their Trinity more than 50x!
the problem is that once the software has crashed you can`t reset it for about 20min - it seems that the processor has to cool down or something like that - after a while (if I´m lucky) my P3600 boots as normal.
I already flashed several new roms - same problem with all of them - I`m pretty sure it`s a hardware failure.
Hello, i don't have any such problem, my Trinity runs very stable even with cooked roms. but sometimes Mobile navigator 7 takes too much memory so the System becomes instable and i have to softreset it.
Hi, mine bug also, and that's begin 2 or 3 days after I have flash to the 1.56.70.11 Radio Rom....
mine worked fine for about 1 1/2 years but suddenly it crashed continous. i havent flashed it and allready hard reseted several times on different days. sometimes it worked for a while but hangs if i started a bigger app like tomtom. vodafone told me they will exchange my p3600. now im waiting for their call
E: Got a new one today which works perfectly so far!
Hi guys,
has anyone had this issue solved without swapping the device?
I have the same problem.....
Bye
Petz
Same problem here...
I have to sftreset or hard reset several times to get it runing again...
In my opinion its some kind of problem with the processor...
Stiil i'm hoping this is a software insue... so that sone one have a hotfix for that...
For my part, when my Trinity crash, I remove the mini-SD, the SIM card and the battery. I just re put the battery, restart (soft reset until WM has realy start, and no more touch or screen freezes), I replace the sim, restart again.. and finaly I replace the mini-sd. It's very long, but generally works well
EDIT:
Finally, I better make my tongue and keep my method for me because at evening begin, my trinity crashed and impossible to turn it on until I finally come back house and have no need more...
my hand that it will crash tomorow morning juste after leave to works
hi, i started getting the same problem.
only thing different is I upgraded to wm6.1 (Mary SL)
I took it back to wm6 which was still locking, then down to wm5.
1week later no issue!
maybe the wm6+ os's needs more cpu than wm5 and causes it to overheat!
just a thought!
xpuser8334 said:
maybe the wm6+ os's needs more cpu than wm5 and causes it to overheat!
Click to expand...
Click to collapse
I don't think so because I downgraded my Trinity to original WM5 and, even if there were less crashes, it crashed anyway.
Now it's still with WM5 but it doesn't start anymore, only backlight.
Ciao
Petz
I want to let you known that my Trinity has run ok for 5 hours without any issue after putting some paper between battery and metallic plate under the battery.
I had to press a little over the rear cover to have it placed correctly because the battery is higher than before.
Keep in mind that it stopped running completely 3 monthes ago, it didn't start anymore and it didn't even go into bootloader mode.
Now I'm using WinMobile 6.5 beta........
Ciao!
Petz
Hi Guys , i have Trinity P3600 in Egypt ,,, it worked perfectly for more than 2 years , but last month it make the same problem like mentioned b4 , hangs , stuck in boot image , or mess in pixel ,,, and i tried to downgrade but no luck, i tried to use different Radio ,, it works sometime , but after a week no , i tried to take out the battery and wait for 3 hours , then back again , so it works but again it hangs if i start my GPS (IGO8) or heavy programs/.
any solution pls
Thanks
Cero92 said:
Hi all, i just got a Qtek 9090 with WM2003 (ITA). I upgraded to WM6.1, but now it has some strange problems: first of all, when it goes in standby, sometimes it doesn't wake up. If i have to reset it, most of times it doesn't boot (it shut down before WM loads) or i get R: None G: None and i have to reset again (otherwise the phone won't work).
The lock at the boot doesn't happen when the phone is connected at the USB port (i think that's because it charges, maybe it's a battery problem?)
Another thing is that i can't turn it off: if i hold pressed the power button, it deactivate the backlught but the device stays on, and if i make another long press, i get the backlight back again... I had this problem also with WM2003, maybe it's normal?
What do you think? Whan can i do?
Click to expand...
Click to collapse
Have you make a HardReset?
The correct HardReset, not only reset and press Power button!!!
See in my HowTo Section...
and why not WM6.5.5 see here
yep, hard reset is a good start, but about your other problems:
the device does not really turn off, like other phones. pressing the power button makes it go to hibernate, the display turns off, depending on your settings, it locks the hardware buttons and it shuts off wi-fi, it hardly uses any energy but gsm/gprs stay on.
the device seems to be off, yet the phone is one and you can be called. that is the closest you get to switching it off. when you turn on airplane mode, the battery consumption is even less so there is not really a need to turn it off.
pressing and holding the power button always was for the backlight. many other devices open up a shutdown menu when you do that, that would allow you to turn it off, soft reset, or switch off the backlight, but for the BA, that is not the standard. however, if i read it right, d-two is working on remapping the power button, probably for that cause.
the R: none G: none issue is known and not a problem with your phone, whenever you run out of power or remove the battery for a second, the next boot will be w/o radio (R and most roms don't allow booting without it. that's why you get stuck there and have to perform a soft reset. back in the days of wm2003 i used to remove the battery when the device froze to reset it w/o the stylus, because it didn't matter then. with cooked roms, it is different, just like the booting splash screen or the way to perform a hard reset, many things change on a cooked rom.
the issue with waking up from standby, or the SOD (standby of death) is an issue, that most likely has something to do with a backup, restored after flashing another os, or maybe you didn't perform a hard reset, as stated by d-two. you should do that, now that the device is still new, you have nothing to lose
also, read through the tutorials posted by d-two and myself, whether you missed anything while flashing.
The "real" hard reset is the one i can get by pressing camera + record button and reset? If so, i already did it after flash (i use d-two 6.1 Manila ROM in WWE)
It shows me 3 options, i put on YES "Clean Registry Hive" and "Format Storage" then i press the mail button, the screen become white for a while and the next boot al seems to be ok.
It seems, because after some time i get again the "standby of death" and, if i press the reset button, the most of time it won't boot up again (it turns off before i can get to WM), if it works phone doesn't. All these boot problem can be avoided by connecting the phone to the usb cradle, so maybe it's also a battery problem, i think...
@ d-two: i'll try your new ROM, however before i've tried your 6.1 ROM
I've already read your guide because i've got Windows 7 and i couldn't flash without your tutorial
NEWS: installed d-two new ROM, after flash i made the hard reset selecting the second and the third options, then i get the blank screen and, when viewing the htc screen, it shut down itself like it did before
As always, with the usb connected, it has no problem :\
It can be battery power - battery is old, and it doesn't provide current [A], or voltage drops [V] and phone think, it's empty.
Maybe you can try with new battery, or buy 2 nokia bl-4c batteries and repair orginal battery (somewhere on forum there is a tutorial about that - but use bl4c, not bl5c like in tutorial - bl5c are too thick to fit)
n0rbi666 said:
It can be battery power - battery is old, and it doesn't provide current [A], or voltage drops [V] and phone think, it's empty.
Maybe you can try with new battery, or buy 2 nokia bl-4c batteries and repair orginal battery (somewhere on forum there is a tutorial about that - but use bl4c, not bl5c like in tutorial - bl5c are too thick to fit)
Click to expand...
Click to collapse
That's what i was thinking (and that's i hope it isn't)... Now with another recharge cycle it seems to be good also with cooked ROMs, i hope it's solved
Maybe you just have to charge/discharge it for 4-5 times, and it will restore it's capacity. Mine BA was turning off when battery indicator was showing ~60-70%, and now I'm waiting for new battery (i destroyed original )
"charge/discharge it for 4-5 times" does not have an effect on Li-ion kind of batteries. This is probably a software problem. When you turn your phone on (after removing a battery) it always shows "None" for R and G, so just press Reset button and it will be ok. I use Reset to power it on Then you can flash 6.5.5 which doesn't have problems, and do a hard reset. There should be no problem at all..
I also got the problem with the stock ROM :\
The R: None G: None error is the less important problem
Got any luck fixing it? I've had similar problems before, sometimes it turned itself off when the battery was at 60% in WM2003. Did you update to d-two's 6.5.5?
Yes, now i'm running d-two's 6.5.5 ROM.
No, i still had the problem Yesterday i called to the assistance service and they said me to remove the battery and after a while recharge it.
I put off the battery yesterday at 16 and i put it again in the phone this morning at 8, i charged it but i still have the problem
This evening i called again and they said me that i have to send it back, i'll flash the original ROM and send it on monday.
That's a shame, i really like this device, even if it's not mine, my sister uses it and she's not a pro user, what a waste
Didn't understand, what "assistance service"? This is very old phone, I just can't believe it has some kind of warranty
I have another battery, and using it the device turns it off sometimes while it's in the stand-by mode! Don't know why, the voltage on it is fine, I have measured it while working...
marko_serb said:
Didn't understand, what "assistance service"? This is very old phone, I just can't believe it has some kind of warranty
I have another battery, and using it the device turns it off sometimes while it's in the stand-by mode! Don't know why, the voltage on it is fine, I have measured it while working...
Click to expand...
Click to collapse
I bought it on an eBay market and it offered 60 days warranty. It's not official HTC/Qtek warranty, but it doesn't make difference, as long as the device will work
If for you it happens only when it's in standby, maybe you just have the standby of death, the problem Chef Tony was talking about at post 3?
Cero92 said:
I bought it on an eBay market and it offered 60 days warranty. It's not official HTC/Qtek warranty, but it doesn't make difference, as long as the device will work
If for you it happens only when it's in standby, maybe you just have the standby of death, the problem Chef Tony was talking about at post 3?
Click to expand...
Click to collapse
My Roms have no SOD
This is when vbase32 have all 01000000 base adress !!!
Search about SOD!!
No, this happens only with my old battery. I'll try it out now with this new ROM!
I was trying to understand his problem
Just to know, what kitchen do you use?
Cero92 said:
I was trying to understand his problem
Just to know, what kitchen do you use?
Click to expand...
Click to collapse
First i have create my own kitchen but then i have found the OSBuilder and this is the best kitchen ever
With this kitchen you can look the Vbase32 for SOD!!!
Well, i trust you that your ROMs doesn't have SOD problem, in fact this happened to me also with the shipped WM2003 ROM, it's a real hardware issue
Cero92 said:
Well, i trust you that your ROMs doesn't have SOD problem, in fact this happened to me also with the shipped WM2003 ROM, it's a real hardware issue
Click to expand...
Click to collapse
I think so, sorry
d-two said:
I think so, sorry
Click to expand...
Click to collapse
No problem, i'll send it to the assistance on monday, i hope it won't take too much time :\
Cero92 said:
No problem, i'll send it to the assistance on monday, i hope it won't take too much time :\
Click to expand...
Click to collapse
good luck But very cool that you have warranty
Touchscreen dead!!!
I was working normally with an android build (cedesmith desire HD) making a phone call; when i finished the screen was normally locked; i tried to unlock but the screen didn't respond however the buttons did respond.
Since i couldn't access the menu to make a reboot i removed the battery to relaunch windows than the build and i was shocked when i found that the touchscreen is no more working in Windows also!!!
I had bad signs before of that, because the screen did freeze completely in the morning (but with buttons working) so i restarted and everything worked well!
I tried to:
-restart many times that didn't work
-removed both sim card and SDcard to see if they are the problem but they weren't
-removed battery for 3 hrs and then reinserted it and that didn't work after reboot
-wiped the windows data (complete format Volume up+Volume down+power buttons)
ALL of that and the touchscreen is not responding!
Any help please!?! Could the build have had damaged the touchscreen somehow?! Coz i am so delicate to the phone and it didn't fall or anything similar!
HELP PLEASE!!!
Try doing a task29 then install either a different WM rom or original rom and see if that fixes it.
dubbingt said:
Try doing a task29 then install either a different WM rom or original rom and see if that fixes it.
Click to expand...
Click to collapse
Can i do a task 29 without the need to use the phone?! (sorry but i ever did it before; i will be reading a bit )
over heating problem
the same has happened to me on 3 phones all u can tell you that there is no fix unless you change the digitazer..when running android in some builds the phone heats up n that can bring this kind of problems. i used to download big files (ROMS) using the phone while charging...the phone at times was warm, but many times it got very hot. my advice send the phone to repair, but first make it stock.
This happened to me about a week ago. Had to have it replaced. There is no other way.
This happened to me as well, but I had my phone undervolted and underclocked. So it isn't just the heat produced when running Android.
Could everyone to whom this has happened please report 2 things in this thread, so that we can determine if Android really is causing long-term damage to our phones:
- What the symptoms were
- Whether or not you were overclocking your phone
pkchips said:
This happened to me as well, but I had my phone undervolted and underclocked. So it isn't just the heat produced when running Android.
Could everyone to whom this has happened please report 2 things in this thread, so that we can determine if Android really is causing long-term damage to our phones:
- What the symptoms were
- Whether or not you were overclocking your phone
Click to expand...
Click to collapse
-The symtoms were:
-The screen froze twice in android, so i had to remove battery and it went all good until it froze finally
-No overclocking, no underclocking... nothing, just the default config with the default kernel
However i am pretty sure that it's not the screen itself that is faulted! It's something that powers the screen, maybe a sensor or i dunno what! That is because:
-from every 10 restarts that i perform the screen works once and perfectly normal and smooth even with just a slight fingertip!
-no good reason that the screen itself goes bad: it didn't fall, it didn't get water or anything, i didn't twist it or push hard, it didn't got hot (at least as far as batstat apk shows)...
What could it be!?!? that's the question....
Besides i have no warranty, and one store said it would replace the screen for 85$ (others said 100 and 150!!)
i had same problem , its not hardware fault OR software , it seems like a driver command bug , i dunno , im not a technician , but odly the touch interface will work 1% of the time , to make it awaken more easy is to hold the volume up button while pressing a hardware key when the screen is OFF , this seems to tell the phone to use the touch drivers , i dunno why but it works for me , personally i blanme the cold weather for causing some kind of hardware/driverr bug