So I rooted my International Galaxy S3 GT-I9300 about 8 months ago with CWM and started running CM 13 on it. Went smooth till about a few days ago, when I was taking some pictures using CamScanner and my phone just turns off. No message, nothing. Just goes blank instantly. Since then, it's stuck in a bootloop whenever I turn it on. I can get into both download mode and recovery currently. No nandroid backup (Extremely stupid of me, I know). And for some reason, my PC doesn't recognize my phone both in recovery and in Odin/Download mode. Thinking that it might be a bug in the ROM, I did a factory reset and flashed CM14.
PS : Couple of bits of info, dunno whether relevant, but anyway :
1. Very weak battery - Percentage fluctuates wildly.
2. I've been running Xposed for quite a while now, however, I had just installed Greenify and set most apps to force hibernate.
3. I've already wiped the cache and Dalvik cache.
4. I already had the drivers installed on my PC; I regularly used to connect my phone to it.
5.I had USB Debugging enabled when the phone went off.
6. A couple of times after the phone went off, I was able to switch it on if the charger was connected, but switched off immediately when I disconnected the charger; it was like a pc going off when you cut off the power supply - no message, nothing at all - just went blank.
7. Dunno why, but my phone refuses to charge unless I use a particular cable and hold it at a particular angle.
I've been trying to find a solution for this for the last one week, but this seems to be a unique case. Please help!
Issue resolved. Turns out, it was a battery issue
Related
SGS2 I9100 with Ressurection Remix ICS_v2.4_AOKP-B39-4.0.4
Device was working fine, battery was low (<5%) so i connected my charger; went to sleep, woke up and tried to turn display on - couldn't ... i thought that maybe phone was battery dead when i connected it so i long-press the power button to start it up but nothing was happening.
Disconnected the charger, took out the battery, waited 20s then put it back, connected charger and tried to power on => sgs2 splash screen .... .... ... showing desktop screen w/o icons and after 5-10s device shows "Shutting down" vibrates and shuts down.
Rebooted into CWM recovery, reinstalled ROM => no change
Rebooted into CWM, wipe data/factory reset => no change
Any ideeas what is going on? is the battery malfunctioning?
Try a new battery in the first instance. If it still happens once you've done that then we can look at other causes. Also, if you feel so inclined, do a clean install of stock & see if that fixes the issue to rule out something in your current setup (rom/kernel/etc) causing the problem.
thanks, been thinking the same about trying another battery but that is something i cannot do today
MistahBungle said:
Try a new battery in the first instance. If it still happens once you've done that then we can look at other causes. Also, if you feel so inclined, do a clean install of stock & see if that fixes the issue to rule out something in your current setup (rom/kernel/etc) causing the problem.
Click to expand...
Click to collapse
tried another battery, same.
flashed a stock, os load doesnt pass "S" screen
also i recharged battery on another phone and when i use it in mine, it gets drained quickly
guess the problem is the "power supply"
So I rooted my phone 3 months ago. Using the external 64g card trick and everything went perfect.
Had SU installed, and titanium running.
January 1st my phone battery died while riding home on my motorcycle or was close. I had it on the charger when it died. The phone went into a reboot mode. It has the battery, with the circle in the middle and vibrating every few seconds.
I can get into the recover mode when plugged into the samsung wall charger. But I can only get into download mode on usb with computer.
Using odin 3 v3.09.
I loaded it up with the jflte_usa_vzw_16g.pit file in the pit section.
Then loaded up all_i545vruemk2_i545vzwemk2_1937946_rev06_user_low_ship_muti_cer.tar.md5 in the AP section
Thinking the above would be the most up to date. I'm traveling and need the phone and not worried about root anymore.
So it went through the md5 checking. Good
Then without changing any other settings I hit start.
13 minutes later, I get a reset above the id:com
I let it go with out touching the phone.
Then it gives me a pass without any errors.
So I unplugged my phone off the usb cable, pull the battery. Reinstall after 30 seconds. Nothing.
I plug into the usb and it goes back to battery icon and circle like nothing happened.
I can get into download on usb to computer
And recovery only on wall charger
I did try a factory reset and cache reset
Looked like it worked
But phone unchanged.
I then tried the kies firmware and initialization mode.
Loaded up my sch-i545 then my IMEI,
It conects, downloads, installs, finishes, no errors
Unplug and dead, plug in usb, battery icon and circle,
Plug to wall, recover mode,
So phone seems like its taken both updates without errors. But acts unchanged.
Would the vibration from my handle bar mount cause a sudden issue? I've been running this set up for months without issue.
I'm at a loss. I read is you can get it into download mode it should be able to get recovered.
Tried all I know and have read about.
So now with phone plugged into the samsung wall charger.
I went to download mode, selected re-start
Phone booted,
Samsung, unlocked padlock
Samsung blue purple splash screen. (Blue led light)
Verizon screen almost fully loaded (blue led light)
Then phone shuts off, goes back to battery icon with circle.
twinscrollgt35r said:
So now with phone plugged into the samsung wall charger.
I went to download mode, selected re-start
Phone booted,
Samsung, unlocked padlock
Samsung blue purple splash screen. (Blue led light)
Verizon screen almost fully loaded (blue led light)
Then phone shuts off, goes back to battery icon with circle.
Click to expand...
Click to collapse
did you ever find a solution for this? This seems like the exact same problem I am having with my phone. Everything was working until it lost power. Now the power button will not turn device on. It will only turn on when connected to usb computer or wall charger and just shows an empty battery sign. It seems to reboot every 15 seconds from this. If I go into download mode and chose restart phone it gets to the white verizon loading screen and reboots. I can get to both download and recovery mode and flashed the stock full wipe and PIT file and this process succeeded but the phone is still doing the same thing.
fuzzywarbles said:
did you ever find a solution for this? This seems like the exact same problem I am having with my phone. Everything was working until it lost power. Now the power button will not turn device on. It will only turn on when connected to usb computer or wall charger and just shows an empty battery sign. It seems to reboot every 15 seconds from this. If I go into download mode and chose restart phone it gets to the white verizon loading screen and reboots. I can get to both download and recovery mode and flashed the stock full wipe and PIT file and this process succeeded but the phone is still doing the same thing.
Click to expand...
Click to collapse
My i545 is a similar phenomenon.
I am afraid to say, that as far as I know, with the Knox bootloader, it disallows any upgrading what so ever. I have heard of this bricking devices. The only way out of this is to see if you can reflash the most current ROM, but I am unsure if even that will work.
Hi, everyone. I've seen the other threads and no one had a problem quite like mine.
Yesterday I've upgraded my Alcatel OT-997, ICS 4.0.4. with Kuano's TWRP and now it's:
Alcatel OT-997D, JB 4.1.1. - (details in this thread, 5th post) http://forum.xda-developers.com/showthread.php?t=1981692&page=89
D means I can now use two SIM cards, which is cool.
The problem is the damn thing doesn't charge when it's turned on. It shows the lightning bolt over the battery icon, but in settings shows that charger is not connected. However, when it's turned off it charges, normally. I tried different settings in USB menu: Mass storage, MTP, Camera mode and Charge. Tried with and without Debugging mode. All of those work when connected to a computer in the sense that I can use internal storage, access both SD cards, and so on. But it doesn't charge.
I have tried 3 different cables, 3 wall outlets, and 2 PCs so it's not that. I suppose it's not a hardware problem otherwise it wouldn't charge properly when it's turned off.
So now I use schedule to turn it off before I go to sleep, and to turn on before I wake up, so it would charge while I'm sleeping. Anyone's got any ideas how to fix it?
Bump
Well I solved it with reinstall
Finally I've lost my patience so I tried the only thing that was left.
First I did a backup with TWRP.
Then, factory reset from TWRP.
Then, restore system from One Touch Upgrade 2.8.0 - lost the DUAL capability, software restored to 4.0.4.
Now comes the interesting part. It had the same problem as before, did not charge while on. So I tried a solution I found online a while ago but I never tried when on 4.1.1: Turn it off, connect charger, remove battery, wait a bit, press power button for approx 10 sec (nothing hapens), wait a bit, instert battery, turn it on and there it is. I'm not sure if it was this procedure that did the trick or it simply needed a reboot after update but it worked. It showed "charging" in battery stats.
Finally, restore with TWRP as Kuano explained in his post. Mind you, when I did the restore it was connected to my PC all the time.
Now two things I you should know:
First, before I did all this I connected it to my PC while turned off i.e. (PC - ON, phone - OFF). I noticed this: it was constantly connecting and disconnecting (the "piano chord" notification was coming from the computer speakers every 5 sec) like I was pulling the cable in and out. That is all I know about this, I didn't have the nerves to work on it.
Second, now that it is restored and charging, when I connected it to PC it couldn't change USB setting from Charge to MTP. It reported an error something like "service stopped". This happened only once and I did not try to do it again, I just don't have the energy for any more problem fixing right now. It charges, and I use airdroid for file transfer, that is all I need for now. If and when I get around to take a look at it I'll post here if there's something interesting.
Hi all
I tried going to a Lollipop ROM on my S2 but I only managed to change the recovery, the ROM didn't work (boot loop) so I used ODIN to revert back to the stock ROM (i9100XWLSW) wiped both the data and dalvik cache. I did also have Kingroot installed during all this and I installed it again after flashing the stock ROM but I've since removed that too with another write of the stock ROM via ODIN.
The problem I'm having now is Whatsapp and other apps won't actually do anything if the device is asleep. The WiFi appears to be connected, logo is present at the top if i wake the device but it takes about 10 - 30 seconds of being inside an app (such as Whatsapp) for anything to happen. I'm not sure if this is a WiFi issue or some sort of app issue across the board? I woke up today at 9am checked my phone there was nothing on it. It was only at 10:30am when I went to send a Whatsapp message to someone and opened the app manually that i had messages come in from 8am that morning. I also use Whatsapp Web and some times it won't connect to the phone via WiFi even if the device is awake. I have to reboot and try again. Although if it's connected via Whatsapp Web and asleep messages come in no problem at all both on the PC and the phone??!!!!
It's doing it constantly now, at the start it was touch and go but now it's all the time i have to constantly check the app for messages to come in. This happens on other apps too.
What's going on? Have i damaged my device some how from the flashing process? I'm pretty familiar with ODIN as I used to flash my old Galaxy Apollo all the time but never had this problem.
I was going to get a new phone but I actually really like my S2 and it actually keeps up with most of the phones in my price range and in some cases (camera, AMOLED screen, storage, sometimes RAM) it is better than the new stuff!
Any idea's please?
Never mind went and got myself a nice Note 3 instead...
Thanks guys.
I got my Xiaomi Redmi 3 in the middle of october 2016. Since then i've been using it every day. It had minor problems, like music app sometimes turns off by itself, data connection didn't want to turn on only with phone restart, but nothing major, that couldn't be temporarily fixed. But a few days ago i just wanted to browse instagram, i opened the app, and it just turned off instantly. So i tried reinstalling it. Nothing changed. I then tried to install an older version of the app. Still no change. So i decided to leave it be. I was talking to my father, that it should be reflashed because there is something wrong with it. He just pressed regular restart on it, but after that the phone died. I mean it died. It does not respond to charging, connecting to usb, pressing any existing combination of the three buttons. The screen and the status LED does not light up even for a bit. I tried to reflash it anyway with methods specifically for this situation, but it doesn't work either. In the flash tool installation of the rom just does not start. I think it's because my pc does not accept the driver, even from the official website, it just says in the device manager, that it's Android and it has that little yellow triangle. So it is visible for my PC through USB but no driver is accepted. What should i do?
Replace to new phone or carry your phone to customer service, but hey it's xiaomi
This wont help with your phone, but just wanted to leave a note for others. I was having the same issue with the Instagram app. I reinstalled the app, wiped caches, upgraded my ROM, downgraded the app, every tried a entriely differnet ROM. Nothign worked. Instagram would just crash a few seconds after opening. Really weird.
Heres how i fixed it: go to Airplane mode, open the app, logout, turn off airplane mode, log back in.
rarely fc it's okay. but when got often it's a major issue. might be emmc needs to be fixed