Hi been using viper x for a couple of years on both of our phones - love it, awesome rom, never had a single issue. However my wife's phone has now developed a strange problem, initially it stopped charging and started randomly rebooting. I've had the USB port fixed last week and it's charging fine now, but still rebooting. The techy guy who fixed the USB says there's no sign of anything been wrong internally (could argue he's bound to say that)
I've tried factory reset, full wipe and reflash, running in safe mode and removing all user apps, including xposed framework. It doesn't seem as bad, but it is still rebooting and I'm out of ideas. The phone is running stock kernel.
Can anyone lend a hand and come up with what could be wrong?
Graham2075 said:
Hi been using viper x for a couple of years on both of our phones - love it, awesome rom, never had a single issue. However my wife's phone has now developed a strange problem, initially it stopped charging and started randomly rebooting. I've had the USB port fixed last week and it's charging fine now, but still rebooting. The techy guy who fixed the USB says there's no sign of anything been wrong internally (could argue he's bound to say that)
I've tried factory reset, full wipe and reflash, running in safe mode and removing all user apps, including xposed framework. It doesn't seem as bad, but it is still rebooting and I'm out of ideas. The phone is running stock kernel.
Can anyone lend a hand and come up with what could be wrong?
Click to expand...
Click to collapse
This could indicate a hardware problem (faulty battery perhaps).
To eliminate that, have you tried a different kernel or a whole different ROM entirely just for testing purposes?
Or maybe a different cable or charger?
Related
Hey Guys,
So i've done some research all evening here and I've done nothing different than i'd do any other day with the phone and all of a sudden today around 6 PM eastern the phone started acting up. I came home from work plugged it in and it started to lag and then froze, finally unfroze and got that error " Unfortunately, %1$S %2$S has stopped running. I only have the option to click (ok) So I would do that and I thought all was well, turns out this is not the case. When this error pops up it also disables the phone from charging. I unplug and plug back in, the phone starts to freeze and the error comes back. I've been doing some online re-search some people say it's a synch issue with google and to turn synch of, did so, still same error. Some people have said unplug charger, power off phone wait 10 seconds, plug charger back on and boot up, this also did not resolve my issue. I will say that if the power cable is not in the device, it works fine. After about 2 hours of trying different things, I plugged it back into the charger and the phone started acting out really strange, changing from screen to screen and indicating " The dock is connected" I don't own a dock and the phone has never been into dock. I'm using the stock charger that came with the Note 2.
I will say I have TWRP installed and I've been using the JEDI X Rom for this phone without any problems. I thought, okay well none of this is working maybe it's the rom acting up, so I decided to go into recovery wipe all cache & system and re-installed the rom, same thing. The dock is connected, phone freezing and Unfortunately, %1$S %2$S has stopped running. So, I re-did everything again, wiped all cache systems, fixed permission and put the stock rom back on the phone. Now the phone is indicating in stock mode that the "dock is connected" when really it's just the charger. The phone is going into the time out then pops back on automatically all by it's self. Not getting the Unfortunately, %1$S %2$S has stopped running anymore though. the phone is 3 weeks old, and i'm at a loss here as to what I should do next.
Any suggestions, if not, Is there away to erase the phone "call" time so I can get it down to below 30 minutes so I can return this one for a new one?
Thanks,
Well, after hours of reading, I came across this post for an Android EVO phone and it mentioned something about a connect point of the charging port in the phone and said slightly bend the charger cable when it's attached inside, I tried this at a last cause and everything fixed itself, I re-flashed Jedi X and all errors have cleared itself. I find it strange because I'm very gentle with inserting/disconnecting these cables...
Thanks,
I'm not surprised. I've had similar issues with a S2 and other Sammy phones. In fact my brothers Galaxy S as well. He had to get the whole board replaced. I hate MicroUsb. Although its nice to have a generic sync port that is the same across almost all Android devices, this port needs to change.
Just my $0.02. Glad to see you figured it out. Knock on wood my Note2 hasent had these issues yet.
Sent from my SGH-I317 using xda app-developers app
Hey Guys, I have been beating my head against a brick wall trying to fix my phone.
Yesterday I was on a call with someone and suddenly I lost service (not uncommon for where I was since I have weak service there), but this time the phone was frozen. The dialer screen was on but was frozen. My phone would not react to anything. So naturally I pulled the battery and rebooted the phone. The phone started up as normally it would but then after 5 minutes of the phone running it froze again. During those five minutes I never received any cell signal.
The most recent "work" I had done on my phone was change the kernel to the AK Kernel on the guide here. This was done 3 days before anything started happening. I tried a new kernel because ever since upgrading to Paranoid 3.0 my phone was acting slow and occasionally I would get a screen of death typically about once a day. The 3 days that I had the new kernel, everything was working great (phone was faster, responsive and no SOD).
I tried restoring a nandroid before upgrading the kernel and it made no difference. Ever since the first time my phone down freezes after 3-5 mins after booting up. Nothing that I have tried has fixed the issue.
I have done a clean install, tried locking and re-rooting, tried a different kernel. All to no avail. Please help I am thinking there is something seriously wrong and may need to take it back to verizon. I am trying to restore my device to stock but am unable to do so. I have been using this guide: Restore to Stock. Any suggestions to make it "clean" enough to get verizon to replace it?
I'm going through withdrawals, please help!
Could not fix it, so I contacted tech support and explained everything that I did to try to fix and they just sent me a warranty replacement. I hope that it was a device error and not something that was caused by other ROMs or Kernels.
Hello everyone! I own a Galaxy Nexus that's running one of the Cyanogenmod 4.4 snapshots. While watching a youtube video my phone froze up and shut itself off. I rebooted and after a few moments the same thing happened. When I power up my phone one of two things happen. It either reboots while booting and automatically attempts to boot again or it manages to turn on for a short while and then turns itself off.
I believed the issue was a battery or hardware one at first but after leaving my phone booted in recovery for half an hour with no ill effects I think something else might be up. What do you guys think is the best course of action? The only thing I've done is a factory reset that has done nothing.
Anyone?
Stryking said:
Anyone?
Click to expand...
Click to collapse
Factory Reset and reflash the rom. If that doesn't work try flashing another rom like Vanir. If your phone still shuts off...well unfortunately this may be a hardware related issue, nothing you can do if that's the case. Unless it's your battery which I highly doubt.
I think it's the same thing that happened to me a year ago, check this out:
http://forum.xda-developers.com/galaxy-nexus/help/bricked-phone-t2306672
for me it was a hw related problem, i had to send the phone back to assistance and have it repaired (it was still under warranty).
Good luck :good:
Thank you all for your ideas. I'll report back my findings later today.
Same problem over here. Tried a lot of roms (custom and stock from Google page), took it to assistance (no warranty though) was told is a hardware issue. Since replacing the mainboard its the same price as a new phone... well you know.
But a curios thing happened: tried to flash the Ubuntu Touch rom, same problem (reboots at Ubuntu start screen) and the Firefox-OS, that one worked (considering it's limitations obviously)!
I'm using a T-Mobile Samsung Note 2 w/ Gummy Nightlies installed currently
Gummy: M3.0-09-02-14-NIGHTLY-t0ltetmo
The problem I'm running into happens consistently but not at predictable intervals. When the phone powers on, every so often while I'm using the phone, whether it be using the internet, browsing through Instagram or Twitter, or just scrolling through the apps my phone will perform a soft reboot.
I've tried multiple ROMs, stable releases, ROMs that aren't CM11 based, nothing seems to fix this issue.
Can anyone shed some light on what might the problem be and possibly a fix?
I'm not sure what else to include that might help anyone with diagnosing the problem, but if there is something that I forgot, I could definitely get you that information.
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Coug76 said:
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Click to expand...
Click to collapse
It hadn't happened on TouchWiz ROMs, but this just started happening about 2-3 weeks ago. I havent used a TouchWiz ROM in months. I've gone from OmniROM to LiquidSmooth to PacMan, to the most recent Gummy. From what I can remember its happened on the two latter ROMs.
It's strange because, I've called T-Mobile to have them send out a replacement battery, I figured that was the issue. I've had no issues with soft reboots while the phone was plugged into the charger, only when unplugged.
T-Mobile decided to just send me a new phone, so I reflashed to stock and im using my phone to send this message with no issues. So maybe AOSP problems?
What can I do to fix this?
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Coug76 said:
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Click to expand...
Click to collapse
The funniest thing just happened, it did it on the stock Firmware. My best guess would still be the battery. Good thing T-Mo sent the phone via Priority Next Day Air. I'll have it some time tomorrow
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
_lolzack said:
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
Click to expand...
Click to collapse
Did the new battery work?
I've got a similar issue ...
I was running Liquid Smooth 3.2 (4.4.4) with TWRP v2.7.0.1 and up until about a month ago, my 2 OEM batteries worked fine.
I was going to head out for the night, so I swapped to battery #2, it went into a boot-loop.
I thought it was a ROM issue, so I reflashed the ROM and still had the boot-loop, even after charging the battery to 100%
It wasn't until the next morning that I re-installed battery #1 and the phone booted fine.
Every time I swap to battery #2, the phone goes into a boot loop.
I ordered another OEM battery from Amazon and the phone goes into a boot loop as well.
The battery contacts on the back of the phone look fine.
I used the following procedure to delete the battery stats and it didn't help:
http://forum.xda-developers.com/showpost.php?p=38500258&postcount=8
I also switched to the JEDI Open Source Project (4.4.4) ROM and only battery #1 works.
I just removed battery #1 from the phone with it plugged into a charger and it remained powered up. I then installed battery #3 and it worked fine. When I rebooted the phone it went into a boot-loop again.
Woke up one day to experience multiple issues with my phone. Il list the ones that are happening frequently.
Earpeice not working. (speakerphone does)
Mic not working.
Calls dont start dialing.
Phone doesnt recognize headphones plugged in. Once restarted its fine but when I unplug them the phone still thinks they are connected (icon in status bar)
After rebooting sometimes within a min il get a prompt (factory reset)and it reboots to recovery.
A reboot solves it but only for a few mins and its back to the same bs again. I have wiped the phone, cleared cache and I even even installed two separate roms but all the problems remain. Back on O OS
biggyk said:
Woke up one day to experience multiple issues with my phone. Il list the ones that are happening frequently.
Earpeice not working. (speakerphone does)
Mic not working.
Calls dont start dialing.
Phone doesnt recognize headphones plugged in. Once restarted its fine but when I unplug them the phone still thinks they are connected (icon in status bar)
After rebooting sometimes within a min il get a prompt (factory reset)and it reboots to recovery.
A reboot solves it but only for a few mins and its back to the same bs again. I have wiped the phone, cleared cache and I even even installed two separate roms but all the problems remain. Back on O OS
Click to expand...
Click to collapse
Throw your phone away.
biggyk said:
Woke up one day to experience multiple issues with my phone. Il list the ones that are happening frequently.
Earpeice not working. (speakerphone does)
Mic not working.
Calls dont start dialing.
Phone doesnt recognize headphones plugged in. Once restarted its fine but when I unplug them the phone still thinks they are connected (icon in status bar)
After rebooting sometimes within a min il get a prompt (factory reset)and it reboots to recovery.
A reboot solves it but only for a few mins and its back to the same bs again. I have wiped the phone, cleared cache and I even even installed two separate roms but all the problems remain. Back on O OS
Click to expand...
Click to collapse
have you installed any mods like viper4android?
hellcat50 said:
have you installed any mods like viper4android?
Click to expand...
Click to collapse
No when the issue was happening. I was stock with locked bootloader.
biggyk said:
No when the issue was happening. I was stock with locked bootloader.
Click to expand...
Click to collapse
I know this is such a generic answer, but you can try a factory reset of your phone.
If this didn't help, I would suggest you use the unbrick tool, which may fix your issue: https://forum.xda-developers.com/oneplus-3/how-to/unbrick-phone-msmdownloadtool-v3-0-6-t3575801
If you still have this issue after you tried these things, It is probably hardware related (means it is a hardware defect)
hellcat50 said:
I know this is such a generic answer, but you can try a factory reset of your phone.
If this didn't help, I would suggest you use the unbrick tool, which may fix your issue: https://forum.xda-developers.com/oneplus-3/how-to/unbrick-phone-msmdownloadtool-v3-0-6-t3575801
If you still have this issue after you tried these things, It is probably hardware related (means it is a hardware defect)
Click to expand...
Click to collapse
Well I tried this and it restored the phone all the way back to Oxygen 4.0 but still lost all audio (mic, ear piece, speaker) and now I seemed to have lost video recording capabilities. I already bought a new phone in the meantime but I really wanted to figure this out. Oh well.
Similar problems
I have similar problems. It started six weeks ago with the headphones that could not be detected. Then calling stopped working. Back then I rooted my phone and all the problems where gone. Until last Sunday my phone app crashed. Now all the problems are back again. I tried wiping all my data (also internal storage) and installing a custom ROM. This did not help. Does anyone has any suggestions? I really like the phone and it is still in mint condition.
Thanks in advance
nilladef said:
I have similar problems. It started six weeks ago with the headphones that could not be detected. Then calling stopped working. Back then I rooted my phone and all the problems where gone. Until last Sunday my phone app crashed. Now all the problems are back again. I tried wiping all my data (also internal storage) and installing a custom ROM. This did not help. Does anyone has any suggestions? I really like the phone and it is still in mint condition.
Thanks in advance
Click to expand...
Click to collapse
Yeah I'm still trying to figure it out even though I have new phone already. I can say it seems my front camera is completely disabled now no matter what I do.
Sent from my Mi A2 using Tapatalk