Related
Im really really hoping that someone can help me here
It started this morning around 10:00 or so - I took my phone out to check my messages, everything is working fine. I lock the phone and put it standby (power button) and *surprise*, it locks up and wont come out of standby
So i just re-set it (like im forced to do 20 times a day) and instead of booting it went straight to this red/green/blue screen. At the bottom of the screen it just says "Serial" but doesn't actually give a serial.
I instantly thought it was bricked, so i removed the battery and left it out for a few mins. Then i put the batt back in, and it booted normally. I used it throughout the day with no problems.
Fast forward a few hours and it does it again but now it wont boot at all (ive reset the thing like 100000 times in the last hour ive been working on it).
WTF is going on?? Im really really hoping that it isnt too screwed to fix
The last program I installed was the SPB pack, but that was over a month ago, and i use the phone every day, multiple times a day.
Oh, and to make things worse i was planning on relying on my TomTom tomorrow
and the text on that screen says:
Kais1*0
SPL-1.56.0000
CPLID-8
And at the bottom it just says "Serial" but none is given.
This blows
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Do you see "USB" instead of "Serial" if you connect your sync cable to your phone when in the bootloader?
If so, I would download the latest carrier-branded rom and flash it to your device. As long as the rom is designed for your device, then you do not need to do anything special prior to running the file from your PC.
grandpareza said:
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Click to expand...
Click to collapse
I have never flashed it but i have spilled water near it (on the counter, the phone got wet but that was months ago and has no relation to this).
Can they check if it has been wet before?
When i plug it into my computer it says USB instead of serial. Should I try to re-flash with an updated rom and see if it fixes it or just take it in?
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
GSLEON3 said:
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
Click to expand...
Click to collapse
Thanks, ill give you a buzz.
I need to finish and email a few things first (shouldnt take more than 30mins).
Actually, ill just message you tomorrow or something.
Ive been really busy this week.
well did you get it fixed? what did you do?
Yikes, that happened to a friend of mine, but he flashed his and then had to reflash it. I think there is a place on the back under the battery that they use to tell if it's been wet. I would take it back, even if flashing it fixes it, you don't want it to happen again.
oh and it doesn't mean serial like a serial number, it is a serial connection.
I havent been able to get it fixed.
I think ill try to flash it this weekend and see if that fixes it
You'll only make problems worse if you reflash. I've analyzed the MTTY output you've sent me & you have a bad NAND storage blocks.
You need to follow the directions I sent to your email account via MSN IM.
DO NOT REFLASH UNTIL YOU'VE TAKEN CARE OF THE BAD BLOCKS!!!
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
dockular said:
jackjohnson said:
dockular said:
Sup Jack, my Tilt is doing the
Kais1*0
spl-1.56.0000
cpld-8
Serial
problem that you had talked about. I read that huge thread, lots of great info in there. Although its unfortunate what happened to you, I'm really grateful of all the troubleshooting that you've done before me, so I know what works and what doesn't. Interesting to note that I have had the Tilt since the day it came out, and never cooked/ flashed my rom. I have been using the Tilt rom the whole time with no problems. Otherwise I'm a huge power user and have a ridiculous amt of software installed.
So after everything was all said and done, did you end up just replacing the device? Thanks again man
-Anthony
Click to expand...
Click to collapse
Anthony,
Yea I went ahead and replaced it. No matter what I did to reflash the original bootloader, and flash the original rom, I always ended up with that same problem. Did you notice that if you can't get it out of the bootloader, but you connect it to your computer, and while it's connect, you soft reset, that it boots? Just curious. that's what happened to me. Either that or I would have to yank the sim and battery, then try.
My tilt was working fine for about a month with a flashed rom, up until I started installing gobs of software on it. Just a thought. If I were you, I would get the device replaced. Especially if you've never flashed a new rom on it - it definitely should not be doing that.
Scott
Click to expand...
Click to collapse
My computer has been broken for a month or two. To answer your question - I haven't been connecting it to anything other than an AC outlet. Anything installed in the last couple months was installed OTA... I usually just obtain a CAB by downloading it directly onto my device.
Also, its weird but sometimes after I drain the batter with the RGB screen then recharge it (this process takes about a day) then hit the reset button, it will actually boot correctly. I am on the third time this has happened. It was bricked for a couple days, then after a combination of charging / depleting got it to boot into windows. Then it happened again, then again.
As long as I don't restart the phone it will stay in windows... If I restart then I lose it for a day or so. Interesting to note that since this has happened, phone calls connect, but I can't hear the other party and they can't hear me.
Also, I use the mini usb out to a 3.5mm stereo jack to stream shoutcast into my car stereo while driving. Last week (at the onset of my problem) the music was playing from the Tilt's speakerphone, and not going through the headphone jack as it normally would. A restart fixed this, but when it happened again a day or so later, the next restart is what got me to that boot screen for the first time.
One of us should post this in the forum...
Click to expand...
Click to collapse
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
dockular said:
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
Umm... GOOD FOR YOU!!!
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
dude i wasn't telling him to not follow your advice. was just letting him know my story. as a matter of fact, after reading your original post I have decided to check for bad blocks on my phone.
GSLEON3;2021681
[B said:
Umm... GOOD FOR YOU!!![/B]
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
Well, this has happened to one of our phones. Can you just post the fix here instead of requiring the email/IM rotuine?
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on. I don't know if it is Cyanogen or some sort of app, as I download apps quiet frequently. I am going to go through my apps now and also reinstall Cyanogen 3.4 tonight and leave my phone on all night. I guess I will have to see in the morning..
Anyways, can someone help
I ve fot sometimes the same issue with dudes cupcake which use th cygnonen kernel...
I ll be glad to have a fix
Are you overclocking the processor? That might contribute to it shutting down.
I do overclock but why do i have to 'battery pull' to make it reboot?
Yes, same issue here.
Uhh, again...
Powered up, set to standby, waited 1 min, shut down.
EDIT: I'm on Rogers Cyanigenized.
Same issue here. Complete lockup with screen off, have to pull battery to boot again. Seems to happen every 6-12 hours for me.
My Phone:
Cyanogen 3.4
radio 2.22.19.26I
Haykuro's SPL
Kernel 2.6.27.24-cm by [email protected] )
NOT overclocked, and no clocking tools even installed. Persists after several clean wipe and reflash also.
This thread's timing is great... I was just about to reset back to rc29 and build back up. Thought I was going to have to replace my phone
Rastasia said:
I do overclock but why do i have to 'battery pull' to make it reboot?
Click to expand...
Click to collapse
This question should probably be in the Dream section and will probably get locked/moved but Pulling the battery reset the "overclock" until it boots back up. This would be why pulling the battery helps.
hey you don't havbe to pull battery just push end call start call and menu all at once it will reboot you phone
Ok, thanks to Jakob, we know, that android freezes, is doesn't shut down.
I now tested with and without overclock, it made no matter to me not to overclock, there's no difference.
But I experienced it didn't happen when it's connected to a charger..
mysterious..
This keeps hapening to me, first it was happening in Cyanogized Rogers rom, then in The Dudes 1.3 b 12, I'm flashing JAC1.62 right now, this never happened to me before I got my class 6 16gb and started using apps2sd
Just curious, does this happen to anyone without a2sd
i'm having the same problem
seems to happen in the builds using the Cyanogen kernel. I'm sure this issue will iron itself out in future releases so just sit tight.
I too am having the problem on the Cyanogen 3.4 build. Its definately a change in 3.4 as I didn't have this problem in any of the 3.3 betas. I'm doing Apps2SD as well.
One thing I have noticed as well is that networking has been acting flakier than normal.
I had this issue on the pre-cupcake radio but not as frequent, so maybe it's just an amplified version of the same problem? There was a thread about it before but I'm too lazy to search for it.
The hangs was the only reason I moved to virtududes rogers rom v3
I'm going to try and get this sorted out tomorrow. For some reason the OOM killer kicks in sometimes and kills a critical process like zygote.
atleast you don't have this problem!
I've reflashed,wiped,formatted and apps2sd2 or sdpsplit, so many times already... trying different ways for each. But same thing always happens... my memory card gets damaged then wiped all by itself.
Uninstall toggle Setting and use Reparing Ext partition with Cyonagen recovery seems to fix this issue
So happy I found this thread! I'm using Google Ion and having this issue since yesterday. So annoying. Anyone got a fix?
I`m having the same problem, the phone freeze, looks like is a hardware problem, i`m on CRC1
I have started to have this issue as well. I am currently running Cyan4.1.999. It happened yesterday while on a call, after a call, and also while the phone was on charge.
Solutions?
I can't post in the thread on SOD in the developers forum, so thought I would post my observations here.
I recently updated from CM7.03 stable (on SD card) to CM7.1RC (on SD card) on my wifes Nook.
Never had the SOD when running CM7.03 stable, but looks like I am now getting it.
Occasionally the screen wont come back on when pressing the power button. The nook appears to be on, but the screen is off. Ultimately, I have to hold the power button down until it shuts off and then restarts.
However, the last couple times this has happened, I have taken the nook and given it a heavy shake. Upon doing this, the screen turns on.
This suggests that maybe the SOD is related to the G-sensor operation?
Has anyone else tried to do this when experiencing a SOD?
Hope this helps.
Thanks for sharing. I should give it a try.
Next time I get this, I'll try it out too!
Nice, I will try this too. I have to admit occasionally I will get frustrated and shake it and occasionally it turns on but I thought it was me hitting a bunch of buttons and waking it. Volume, etc.
It's obviously still "on" since you have to do a hard power off on it. So, perhaps that's the magic?
Has anyone else had a chance to try it?
It still seems to be working for me (tried it 2x more times since I posted), but it could be a fluke.
This would be random to find out if it works. I'll try myself too next time I get a SOD.
I think it is more likely related to Wifi. Particularly, some app is not playing nice with the Wifi driver. Are you signed into Latitude in Google Maps?
It figures - now that I WANT my Nook Color to experience SOD, the damn thing is running fine!!!
I'm sure it'll happen again sooner or later (probably sooner) - I'll be sure to try the "shake to wake" idea and post my results!
Thanks for the info....
FYI - My SOD finally came and no matter how much I shook my Nook Color, it would not come back to life (boy, did I look like an idiot, though!)...
Oh well, it was worth a shot!
jtrosky said:
FYI - My SOD finally came and no matter how much I shook my Nook Color, it would not come back to life (boy, did I look like an idiot, though!)...
Oh well, it was worth a shot!
Click to expand...
Click to collapse
Darn no video of you trying that? OP should have asked for proof of people trying it. Haha
Sent from my PC36100 using Tapatalk
I just had an SOD and I shaked the Nook and nothing happened..
I just had an SOD and I shaked the Nook and nothing happened..
edit: Phiremod v7 Test.
OP is getting a good laugh thinking of all the people shaking their Nooks.
cincibluer6 said:
OP is getting a good laugh thinking of all the people shaking their Nooks.
Click to expand...
Click to collapse
LOL at all you shakers.
Oh well, it happened a few times on our Nook, haven't had an SOD since yesterday. Maybe it's a fluke or something related to our nook.
Oh well, I was hoping it would have been a solution.
At least I can get a laugh out of everybody shaking their nooks as if it were an etch-a-sketch.
Hmm, on the latest nightly, I noticed that I sometimes get a pseudo-SOD! The screen will not come on, but if I repeatedly push the volume up/down buttons, I can tell the Nook is still running (it beeps when you press the vol keys). I've found that when this happens, I just wait a few seconds to a minute and try turning it on again and it comes on (did NOT reboot either). I had this happen to me about 3 times within an hour today!
Now there is another SOD-related problem? Or maybe related to the original SOD problem? Try pressing the vol buttons the next time you think you have SOD and see if they beep. If so, give the nook a minute or two and try turning on again... just curious if anyone else is seeing the pseudo-SOD issue as well...
Thanks.
Just great. Now that I want it to have SOD so I can test this out, it's working awesomely. Maybe I should say i don't want SOD and it will sod.
In my best Steve Jobs voice: "You aren't shaking it right"
Hey,
I have Verizon droid 3 running up in Canada, and its been working fine...however it recently started having issues with the touchscreen.
Basically the screen works normally 3% now, otherwise it only works when the keyboard is open to just above the first row of keys.
If I touch the screen while the keyboard is fully open it wont respond, but when I go back to the working position it will respond to a touch made while fully open (ie; I pressed ok after typing, it didn't submit until I closed the keyboard to the working position, like a delayed response).
It seems like a software issue, but I already hard reset.....
Any ideas? I don't want to change this phone after only 5 months (no Verizon warranty here!)..
Thanks,
--CP
Sent from my XT883 using xda app-developers app
CrazyPhil said:
Hey,
I have Verizon droid 3 running up in Canada, and its been working fine...however it recently started having issues with the touchscreen.
Basically the screen works normally 3% now, otherwise it only works when the keyboard is open to just above the first row of keys.
If I touch the screen while the keyboard is fully open it wont respond, but when I go back to the working position it will respond to a touch made while fully open (ie; I pressed ok after typing, it didn't submit until I closed the keyboard to the working position, like a delayed response).
It seems like a software issue, but I already hard reset.....
Any ideas? I don't want to change this phone after only 5 months (no Verizon warranty here!)..
Thanks,
--CP
Sent from my XT883 using xda app-developers app
Click to expand...
Click to collapse
Which ROM are you on, stock or a custom one?
Its a long shot, but I have odd touchscreen issues when plugged into cheap power sources (inverters, etc). You may want to check the battery - pop it out for a bit, put it back in, maybe try someone else's, etc...
Sent from my DROID3 using xda app-developers app
Phibernaut said:
Its a long shot, but I have odd touchscreen issues when plugged into cheap power sources (inverters, etc). You may want to check the battery - pop it out for a bit, put it back in, maybe try someone else's, etc...
Sent from my DROID3 using xda app-developers app
Click to expand...
Click to collapse
Haha ya I have odd touchscreen issues when I get to 100% battery and am still plugged in :cyclops:
adamskub said:
Which ROM are you on, stock or a custom one?
Click to expand...
Click to collapse
I believe it's stock-ish, I don't remember what I flashed 5 months ago, think I just changed the radio.img:
57.1.60.XT883.ChinaTelecom.en.CN
XT883
2.3.4
n_16.18.16s
2.6.35.7-g790a33c / [email protected] #1
SLNCT-57.1.60
Thanks,
--CP
CrazyPhil said:
I believe it's stock-ish, I don't remember what I flashed 5 months ago, think I just changed the radio.img:
57.1.60.XT883.ChinaTelecom.en.CN
XT883
2.3.4
n_16.18.16s
2.6.35.7-g790a33c / [email protected] #1
SLNCT-57.1.60
Thanks,
--CP
Click to expand...
Click to collapse
Oh ok, then I'm not really sure. I would, if you want, try and flash right back to complete stock and see if your having the same troubles. If you are then it's almost guaranteed to be a hardware problem. However, if the problem doesn't persist then it could have just been some weird bug or glitch that happened. I've had some weird things happen a week or so after a flash and it was software related.
But all this would be having you do a reflash either through CWM/Safestrap or sbf and then you lose everything you have (Though you can backup & restore apps via Titanium Backup). So if you don't end up reflashing I understand
Also does this happen only at certain times/intervals say when your charging? Hope this helps!
Edit: I looked at the orig post at work and forgot to look at it again. A hard reset should be able to fix it, but you never know. I would recommend a reflash and see what happens. Sorry I can't be more help
I hate you. I read your post yesterday and thought "huh, that's really weird and unfortunate." I woke up today and the same thing is happening to me. I haven't flashed anything since April. It was totally out of the blue.
Mine only works when the screen is slid open bout half a centimeter, not even enough to force the screen to rotate.
Sent from my DROID3 using xda premium
That's exactly what's happening....It's been like this for a week. However, it sometimes works when I left it for the night to charge...or randomly, but full functionality lasts only a few minutes.
has there been any update on this status? im trying to fix a friends with the same problem.
Chaunton said:
has there been any update on this status? im trying to fix a friends with the same problem.
Click to expand...
Click to collapse
I think that is bad luck and your digitizer is stopped working.
ugynok said:
I think that is bad luck and your digitizer is stopped working.
Click to expand...
Click to collapse
I'm in the same train
It's strange.
Yesterday my touchscreen it was completely unresponsive the whole day.
stock rom, everything untouched
i rebooted it a million times. closed or open make no difference.
today, it is working amazingly
what was the difference? nothing at all! it layed on my desk all night
i don't understand how the digitizer can go between perfect condition and not working as it wish.
Hi everyone.
I would like to report a pretty fightening situation I faced with my ONE this morning.
I was at a coffe shop conected with wifi and at some point I tried to run Antutu (which I had done lots of time since the 31st of October that I got my One) the dvice gave me a notification that Antutu didnt work and If I wanted to report the problem.
I did click on the report the problem and the phone became unresponsive.
I pressed the power button to see if I can restart the phone but instead the screen became black and would turn on.
Pressing power button long the capacivity buttons were flashing and thats all.
I returned home and I connected it to the charger but the LED light didnt come on.
I tried immediately to turn the device on and to my delight it did boot and worked fine.
I also noticed tryibg quadrant benchmark this afternoon did not work.
Almost performed the test but then it stopped of course I didnt push harder and uninstall quadrant and antutu as well.
Has anyone faced this before?
If that happens again how can I reboot the phone to escape the frozen screen?
That sounds like defective hardware. I think you need to exchange for a new one or send to HTC to be fixed.
Sent from my HTC One using XDA Premium 4 mobile app
gtg465x said:
That sounds like defective hardware. I think you need to exchange for a new one or send to HTC to be fixed.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Since its working and its fully functional I think I can leave without the prety much useless benchmark apps.
Funny part is that this is a replacement phone from HTC Europe because my HTC ONE X had a BSOD problem after they replaced my mainboard and battery after another problem.
All in all it was a deja vu for me to see my almost 10 days old HTC ONE do the same problem the HTC ONE X displayed.
Maybe there is some kind of curse on me.
There is an ex-girlfriend I suspesct........
:laugh:
I have a similar problem with my HTC One, which i bought back in July.
Sometimes the phone refuses to wake up, i have to hold the power key, together with the home key to make it reboot.
Other times the screen refuses to turn off and only rebooting as described above helps.
I waited for the upgrade to Android 4.3, hoping the problem would be fixed.
Unfortunately it didn't help. I also tried to hard reset and initialize the phone a couple of times, also without luck.
I also tried to run the phone without my apps to be sure the problem was not caused by any one of them.
Yesterday i initialized again and the phone worked without problems, so this morning i added WhatsApp.
Everything worked ok for a couple of hours, so i added 2 more apps (news reader and an app to control the heating).
After a few hours the problem reoccured so i removed the last 2 apps and rebooted. After a couple of minutes it got stuck again.
Since i'm struggling with this problem for some weeks now and it seems to become worse, i decided to request HTC to repair or replace my phone.
Two of my friends also own a HTC One and don't have this problem.
Maybe you should also consider to get in touch with HTC.
Good luck!
What rom's and kernels are you all running?
You should be finding some girls in the coffee shop but you try to run Antutu instead?
snowblind2142 said:
What rom's and kernels are you all running?
Click to expand...
Click to collapse
Mine is all standard.
Kernel: 3.4.10-gfa33c1e
[email protected]#1
SMP PREEMPT
Build-number
3.62.401.1CL264544 release-keys
Android-version
4.3
Sense-version
5.5
The problem also occured with the previous Android version (4.2).
IINexusII said:
You should be finding some girls in the coffee shop but you try to run Antutu instead?
Click to expand...
Click to collapse
Well the place was pretty boring in that area which explains why I was playing with the phone.
I thought that was apparent.....
snowblind2142 said:
What rom's and kernels are you all running?
Click to expand...
Click to collapse
Stock ROM android 4.3 Sense 5.5
I sent it to HTC for repair a week ago.
I will post their finding after it has been returned.