Related
I installed the kingx bfs kernel #5 and after rebooting my phone, the phone would come on and start loading the widgets and all that good stuff. After about a minute, my phone would reboot and do the same thing. well after about 4 reboots, I pulled the battery and went to bed, thinking I would just download a new kernel in the morning and things would be better. Now when I try and start my phone up into recovery, it vibrates 3 times and nothing happens. The screen doesn't come up; nothing. It will still boot the phone up and load the widgets and then reboot itself again, but I can't get into bootloader or recovery.
I am running the leaked version of froyo that came out a while back.
any ideas?
*EDIT* ok somehow I managed to get into recover... idk how but I did. wish me luck.
You put your phone into some type of Debug mode. I'm assuming you have S-Off enabled? You are fine, you just need to unplug and remove the battery for a while when that happens.
happened to me when i put the CPU clock too high.
If you can get to recovery just flash another kernel or do a nandroid backup. Should be fine.
I've noticed setCPU locks up at higher frequencies w/ KK's #5. Not sure what you are running at, but i don't go much over 1GHz.
knock 3 times....
Speculation, if it makes you feel any better:
I seem to recall in the UnREVOked notes during rooting - that when one pushes the volume button up while pressing the power button, it triggers a harmless diagnostics run on the Qualcomm processor, yielding 3 buzzes - suspect that may have been the 3 buzzes.
Agree w/ other guidance posted to get you up and running again.
FWIW, just because a kernel is capable of going 119 and we can keep it 'to the floor' the whole time by overclocking in SetCPU - it doesn't mean the device will do it, nor that it won't nag you for pushing it so hard.
Some will work reliably/consistently @ that rate.. Some will not.
thanks guys. Setcpu was automatically setting the kernel to 1.13, and I believe that's what was happening as well. I had just enough time to get the setcpu up to see it and then it would restart.
I just picked my phone up after leaving on the side for an hour and it was off and fairly hot now it wont charge, wont turn on and nothing pops up on the pc. any help or suggestions will be greatly appreciated.
oh and it has Venom Rom with Franco kernel 12
thanks it advance Steve
Edit: i managed to get it back on by holding vol- and power for about 10secs then lights flashed and booted
steveharris87 said:
I just picked my phone up after leaving on the side for an hour and it was off and fairly hot now it wont charge, wont turn on and nothing pops up on the pc. any help or suggestions will be greatly appreciated.
oh and it has Venom Rom with Franco kernel 12
thanks it advance Steve
Edit: i managed to get it back on by holding vol- and power for about 10secs then lights flashed and booted
Click to expand...
Click to collapse
it just done it again without the overheat and i had to simulate battery pull to turn it on, also my back light doesn't go out on its own, does anyone know how to fix this or should i just give in and get a new phone?
steveharris87 said:
it just done it again without the overheat and i had to simulate battery pull to turn it on, also my back light doesn't go out on its own, does anyone know how to fix this or should i just give in and get a new phone?
Click to expand...
Click to collapse
Have you unlocked the phone with HTC-Dev ?
Installed a custom rom and/or custom kernel ?
If your phone is still locked (and not relocked) you can go and claim warranty. If you are unlocked it will be more difficult (HTC needs to demonstrate it's your fault and they mainly can't... but the are the big firm...)
Give some more information about what you were doing when it overheated, gaming ?
EDIT : Oups... haven't totaly read the last sentence...
Well franco is known for massive heat... If you have left a game on during an hour (even if it only was a back-task) it could have damaged yourr phone :/ Have you bought it in a store or at a carrier shop ?
Carriers don't give much for HTC policies, they just check a bit if the phone has scratches or if it fall down and will probably change it (just try to get it back to stock !!)
ChriKn said:
Have you unlocked the phone with HTC-Dev ?
Installed a custom rom and/or custom kernel ?
If your phone is still locked (and not relocked) you can go and claim warranty. If you are unlocked it will be more difficult (HTC needs to demonstrate it's your fault and they mainly can't... but the are the big firm...)
Give some more information about what you were doing when it overheated, gaming ?
Click to expand...
Click to collapse
I did unlock it with Htc-dev and Ive installed venom Rom 1.0.1 and Franco kernel 12,
it normally gets to 50-60c wen gaming but wen this happened it was just idol on the side.
steveharris87 said:
I did unlock it with Htc-dev and Ive installed venom Rom 1.0.1 and Franco kernel 12,
it normally gets to 50-60c wen gaming but wen this happened it was just idol on the side.
Click to expand...
Click to collapse
And you are sure that there was no game rnning as a background task ?
I'm more on AOSP rom's, but I remember that when using franco's R12, my phone got so hot I could berrely take it in my hands...
First I would do is backing up data (Titanium Backup or MyBackup pro; SMS Backup & Restore and the rest being done by google account, save all your photos etc on a PC)
Try to flash a RUU to get back to stock, and look if it still gives the same issues.
If Yes -> your phone has an issue
If No -> Try again to flash a rom and a kernel (I would go with Faux 4b5 it's just perfect, working at 1100Mhz and -100mV UV, you get pretty good battery life) and look at the result.
I don't know Viper, but i cna recommand you Slim ICS or AOKP by Nycbjr and Lord Clockan, theyy are both very stable and my phone was never hot in adition with faux 4b5.
Good luck
ChriKn said:
And you are sure that there was no game rnning as a background task ?
I'm more on AOSP rom's, but I remember that when using franco's R12, my phone got so hot I could berrely take it in my hands...
First I would do is backing up data (Titanium Backup or MyBackup pro; SMS Backup & Restore and the rest being done by google account, save all your photos etc on a PC)
Try to flash a RUU to get back to stock, and look if it still gives the same issues.
If Yes -> your phone has an issue
If No -> Try again to flash a rom and a kernel (I would go with Faux 4b5 it's just perfect, working at 1100Mhz and -100mV UV, you get pretty good battery life) and look at the result.
I don't know Viper, but i cna recommand you Slim ICS or AOKP by Nycbjr and Lord Clockan, theyy are both very stable and my phone was never hot in adition with faux 4b5.
Good luck
Click to expand...
Click to collapse
Thank you for the advice ill put it back to stock shortly and see, A game might of been running in the background i dont use task killers much,
It has been fairly hot since i flashed it but not as hot as stock was.
As for warranty i bought it off ebay
steveharris87 said:
Thank you for the advice ill put it back to stock shortly and see, A game might of been running in the background i dont use task killers much,
It has been fairly hot since i flashed it but not as hot as stock was.
As for warranty i bought it off ebay
Click to expand...
Click to collapse
If I remember well, if you live in Europe, there is no such thing as "warranty cancelling" go to your local customer rights specialist/lawyer. But in fact you will need a proof of buy, haven't you got a receipt when buying from ebay ?
Alright, I have a weird one.
PROBLEMS:
First off, the phone won't stay off. If I turn it off, it reboots. If I pull the battery it obviously shuts off, but as soon as the battery is back in, it boots itself up without me touching anything.
But the MAIN problem is that it's... haunted. Without me touching it, the screen will turn on, displaying the home screen before backing out to the lockscreen. When this happens, an icon shaped like a steering wheel appears in my notification bar very briefly. Also, I get some kind of "startup, shutdown" noise, but not one I associate with any program or process I can think of. It's a doo doo DOOT. Then, DOO doo doot.
I don't even have any kind of car mode on this thing.
This happens with such frequency, it's basically a low-key strobelight. I end up pulling the battery because I feel bad for the poor thing flipping out.
WHAT WERE YOU DOING WHEN THIS HAPPENED?:
When this first cropped up, I had just finished using the phone to navigate me somewhere. It was plugged into my car charger, because it had randomly dumped a lot of charge before the trip (while I was napping...), so it was at about 12% battery.
PHONE FACTS:
AT&T SGS3, bought on launch day. Rooted, running Aristodemos III, which is an ICS ROM.
WHAT HAVE YOU TRIED?
Battery pull, turning off the gps, airplane mode, turning off all active processes, RAM dump, waiting, charging, sighing heavily. I haven't been home since this happened, but I will try flashing a new ROM later if I can't fix this - with a full wipe.
Any suggestions??
ManiacalShen said:
doo doo DOOT. Then, DOO doo doot.
Click to expand...
Click to collapse
Sounds like the old man who plays song of storms(in zelda)is haunting your phone! Quick play song of the sun! Right down up, right down up!!!
In all seriousness though, why not just factory reset? Or better yet go to your carriers store, show them, and get a new Samsung galaxy s3/send in for warranty.
AT&T SGS3 Marble White
AoCP The Collective 4.4 ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Just restore a nandroid?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
The steering wheel is most likely "driving mode" goto settings, language and input, Text to speech, driving mode.. Is it on?
Sent from my SAMSUNG-SGH-I747 using xda premium
Driving mode is indeed off, at least right now. It's probably on when the phone freaks out...
I did a factory data reset, wiped the cache and the dalvik cache, fixed permissions, and then tried installing the Hellfire ROM. No dice as of yet, am getting an "assert failed: getprop" error. I can't plug the phone in to the computer to move files around, either. It just makes the "You plugged in a USB thing!" sound over and over but never lets the phone appear on Windows Explorer. Pretty sure this is a hardware issue at this point, but I'll get this damn ROM working if I can, just to be sure.
I'm not afraid to mess with software, but ugh, I don't know where to start with a hardware problem. Might have to see what the people at Best Buy have to say, since they sold me this phone.
ManiacalShen said:
Driving mode is indeed off, at least right now. It's probably on when the phone freaks out...
I did a factory data reset, wiped the cache and the dalvik cache, fixed permissions, and then tried installing the Hellfire ROM. No dice as of yet, am getting an "assert failed: getprop" error. I can't plug the phone in to the computer to move files around, either. It just makes the "You plugged in a USB thing!" sound over and over but never lets the phone appear on Windows Explorer. Pretty sure this is a hardware issue at this point, but I'll get this damn ROM working if I can, just to be sure.
I'm not afraid to mess with software, but ugh, I don't know where to start with a hardware problem. Might have to see what the people at Best Buy have to say, since they sold me this phone.
Click to expand...
Click to collapse
Have you tried using the Odin software in the DEV section and flashing over the stock software with it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
ManiacalShen said:
Driving mode is indeed off, at least right now. It's probably on when the phone freaks out...
I did a factory data reset, wiped the cache and the dalvik cache, fixed permissions, and then tried installing the Hellfire ROM. No dice as of yet, am getting an "assert failed: getprop" error. I can't plug the phone in to the computer to move files around, either. It just makes the "You plugged in a USB thing!" sound over and over but never lets the phone appear on Windows Explorer. Pretty sure this is a hardware issue at this point, but I'll get this damn ROM working if I can, just to be sure.
I'm not afraid to mess with software, but ugh, I don't know where to start with a hardware problem. Might have to see what the people at Best Buy have to say, since they sold me this phone.
Click to expand...
Click to collapse
What you need as stated before is a complete factory restore. Not reset.restore. unless you'd rather spend another few days with these problems figuring out what it might be. find ucalg1 and flash via Odin this will fix all your problems. in case you missed the thread here you go:
http://forum.xda-developers.com/showthread.php?p=28019751
AT&T SGS3 Marble White
Team AoCP The Collective ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Dankest said:
What you need as stated before is a complete factory restore. Not reset.restore. unless you'd rather spend another few days with these problems figuring out what it might be. find ucalg1 and flash via Odin this will fix all your problems. in case you missed the thread here you go:
http://forum.xda-developers.com/showthread.php?p=28019751
AT&T SGS3 Marble White
Team AoCP The Collective ROM
KT747 10/31 OC'ed & UV'ed
Medical MJ Supporter
Click to expand...
Click to collapse
Assuming that there is no faulty hardware.
I'll try Odin when I get home from work... but I have my doubts, since my computer won't recognize the phone correctly. I can probably replace the micro USB port, though. Haven't found the instructions particular to this phone yet, but I have a few days before the part gets here.
Thanks, guys.
Don't use your car charger again!! I've had this with 2 Samsung phones. My S2 and Skyrocket. Both of them have damaged micro usb ports because of a Rocket fish car charger.
Luckily I caught the problem and my S3 wasn't damaged.
Sent from my SGH-I747 using xda app-developers app
Okay, so I got Odin to work, but I still can't connect my phone to my PC while it's awake. XD Just while it's in Download Mode. No more repetitive "USB in!" noise, just "Device not recognized." But whatever, I flashed ucalg1, installed the newest ClockworkMod, used Dropbox in the browser to put get Hellfire and the relevant CM gapps on the internal SD, wiped everything, and installed those with the now-effective CWM.
Good news is that I have Hellfire now. Yay Jellybean.
The bad news is that it's still randomly waking itself up with the car mode notification like before, AND it won't stay off, AND trying Titanium Backup's shiny new zip feature created a brand new problem where I get random popups telling me certain processes have stopped. Going to mess with that some more. Odin sure didn't fix it.
But at least it's usable as a phone right now, and maybe when/if I replace the micro USB port, some of this madness will stop.
g2tegg said:
Don't use your car charger again!! I've had this with 2 Samsung phones. My S2 and Skyrocket. Both of them have damaged micro usb ports because of a Rocket fish car charger.
Luckily I caught the problem and my S3 wasn't damaged.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ha, actually the Rocketfish charger died last month. I've been using a random microUSB cable and a car-to-USB adapter I had lying around. If you're right, though, I might need to get a new cable.
ManiacalShen said:
Okay, so I got Odin to work, but I still can't connect my phone to my PC while it's awake. XD Just while it's in Download Mode. No more repetitive "USB in!" noise, just "Device not recognized." But whatever, I flashed ucalg1, installed the newest ClockworkMod, used Dropbox in the browser to put get Hellfire and the relevant CM gapps on the internal SD, wiped everything, and installed those with the now-effective CWM.
Good news is that I have Hellfire now. Yay Jellybean.
The bad news is that it's still randomly waking itself up with the car mode notification like before, AND it won't stay off, AND trying Titanium Backup's shiny new zip feature created a brand new problem where I get random popups telling me certain processes have stopped. Going to mess with that some more. Odin sure didn't fix it.
But at least it's usable as a phone right now, and maybe when/if I replace the micro USB port, some of this madness will stop.
Click to expand...
Click to collapse
I definitely sounds like a hardware problem. Just curious have you tried other ROMS other than hellfire and the other one you mentioned in the op? Like aokp or paranoid or cm10?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Bruce Lee said:
I definitely sounds like a hardware problem. Just curious have you tried other ROMS other than hellfire and the other one you mentioned in the op? Like aokp or paranoid or cm10?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Well, from Aristodemos, I used ClockworkMod to restore to an old Nandroid backup (some other ROM), then went stock with Odin, then went Hellfire. And Hellfire is CM10-based.
So, lately my phone has been acting kinda weird.. Basically, it'll shut off on it's own, no matter what my battery level or if I'm on the charger, its pretty random. When I go to turn it on, it shows me the samsung logo and shuts off after about 3 seconds of the galaxy s3 logo. It does the same in download mode and recovery. The phone will stay off and do that for an hour or more, and then itll turn on and be all dandy again for hours or at least another day. I'm going to take off all my pictures on the sdcard and odin back to stock as soon as possible for warranty, but does this sound like a hardware failure or software? I read about the s3 sudden death syndrome, but this one isnt permanent. Any ideas?
I agree with your assessments.
I'd wonder about overheating or a bad battery.
Sent from my SGH-T999 using xda app-developers app
what's your setup as of right now?
Beware if it shuts down when your flashing back to stock in the middle of the process it may never turn back on.
Sent From My Galaxy S3 Boricua 100%
It might be the kernel that came with the ROM you installed. I used to have problem with ktoon kernel.
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
mejorguille said:
I'm running Darthstalker XI, the problem happened with both the stock kernel and the faux samsung kernel. The battery is fine, its completely flat with no bumps or humps. I managed to turn it on once yesterday but as I was getting ready to transfer over the files the phone shut off and didn't start again. I'll try to get it running tomorrow.
EDIT: Now that I think about it, the problem happened when I dirty flashed XI over X. Afterwards I did a wipe and clean install of X1 and the problem persisted. Has anyone else on Darthstalker/UDVLJA based roms had this?
EDIT2: Well after being on the charger all day, I noticed that the green samsung battery icon was on the screen, something it only does when it's about to turn on properly. I instantly pulled out the sdcard and put the latest cm10 nightly and gapps on there and I booted to recovery, wiped, and flashed them right up, no issues. I booted just fine, I signed up and I was downloading youtube, latest now updates etc (bare essentials).... and it shut off again. I'm positive now that it's a hardware failure
Click to expand...
Click to collapse
If you have an app that controls kernel voltage that is still set up for set on boot and the voltage is too low when it boots or is granted root it'll kill it in this manner. Otherwise your phone is [email protected]#
Sent from my SGH-T999 infected with AnthraX using Tapatalk 2
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
I used the phone for work, not play, no overclocking was done neither was any undervolting. I ran stock kernel settings.
Aerowinder said:
I'd wager that if any overclocking/undervolting was done, it was disabled at the onset of problems. OP seems smarter than orangutan.
Click to expand...
Click to collapse
I remember a time when XDA had helpful answers and users weren't reduced to insults. I've been around a couple years, hacked more phones than I can count and flashed hundreds of roms in my days, back when everything was still done in adb and terminal emulator. It's no wonder a lot of decent user has started moving over to rootzwiki
Hi all, I have been scouring forums & Google for the past 2 days trying to find an answer for my issue and now turn directly to you guys & gals at XDA for help...
My phone is a Rooted T989 on the T-Mo network. I was running "Sons of Android" 4.2.2 ROM. I had been using it for about a month and have not installed any new apps or app updates since a couple of weeks ago. It seemed to be 99% stable. 2 days ago I sent a text and suddenly my phone jumped to the boot logo screen. The animation was spinning, but the phone was completely unresponsive. I had to do a battery pull to restart. It booted to the logo animation, then went black & started a pulsating vibration that wouldn't stop. Another battery pull & I tried to start in CWM Recovery Mode. Anything I tried to do from recovery locked up before it was complete: CWM Wipe, dalvik cache wipe, sys cache wipe, Darkside Super Wipe, Darkside Cache Wipe. I tried these over & over, but they would all lock up, screen would go black, vibrating pulse. Sometimes the phone would actually boot up for a few minutes and I could see that no wipes had been successful. Finally, after repeated battery pulls, let sit 20 min, etc, the phone started & one of the wipes must have worked! Although it didn't stay up for long before returning to the black screen. Still, I was very excited & immediately put it into download mode, conected to the PC & used Odin3 to Unroot & Restore to a fresh version of T-Mo Jelly Bean. Odin gave a Completed Successful report, and it tries to boot up under the stock T-Mo boot screen, but all of the problems & symptoms are still there! I haven't got T-Mo JB to complete the boot process yet. I even went into stock recovery to clear everything one more time. The phone still goes to a black screen, vibrating pulse, unresponsive.
Has anyone ever seen anything like this? Please help. I have already pulled all my hair out over this so now I am just left scratching my head.
Sticky power button. Holy fkin **** I'm scared for mine now.....I've seen so many threads on this
JesusWazBlack said:
Sticky power button. Holy fkin **** I'm scared for mine now.....I've seen so many threads on this
Click to expand...
Click to collapse
Never heard of sticky power button, but now that you mention it, the power button is uber sensitive which makes it difficult to make a selection in recovery. Thank you, I will search for this... anyone else have any experience/ideas/suggestions?
ABMdesign said:
... anyone else have any experience/ideas/suggestions?
Click to expand...
Click to collapse
There are some things you can try here:
http://forum.xda-developers.com/showthread.php?t=1931310
JesusWazBlack said:
Sticky power button. Holy fkin **** I'm scared for mine now.....I've seen so many threads on this
Click to expand...
Click to collapse
meekrawb said:
There are some things you can try here:
http://forum.xda-developers.com/showthread.php?t=1931310
Click to expand...
Click to collapse
THANK YOU BOTH SOOOO MUCH! It was a sticking power button. I followed meekrawb's link. I took the phone apart and used my air compressor with a blow off tool @ 60 psi to get in all the nooks & crannies. I also scrubbed all around the power button with an old toothbrush before blowing it off again. I could already tell it felt more free. I put the phone back together & voila; I'M BACK!!:laugh::good: