Hey all,
I've got my wife's galaxy note 2 here, and its doing something I've never seen in all the time I've been rooting and custom roming Android devices. Her battery is at 0%. When you plug it in, it will show the charging status while the device is powered off like normal, however, after about 5 seconds it will show the boot animation. No splash screen or anything. When it boots into system, the lock screen shows charging 0%. You can unlock, do anything, only it powers off after around 15 seconds, and starts the process all over again.
She has a missed text message, and everytime it boots, the OS thinks its a new message. So it shows 64 missed text messages, however when you open messaging, its the same one over and over. I can't boot into safe mode, nor can I boot into recovery. Usually you do the button combo, and when you see the splash screen you release power. There is no splash screen, it skips straight to boot animation. I've tried everything I know how, no download mode, no recovery, no safe mode.
Now you should know that this phone is no longer rooted or running a custom rom. It is running the latest OTA from AT&T. Knox re-enabled. Its been running smoothly for about 2 months now, and it just started about 2 hours ago. Tried 4 different chargers. What should I do? Is it time for a new device? My wife doesn't mind change, however she would prefer not to. She LOVES her note 2. Bought her a new phone, and we had to return it because she missed the Note.
Related
Running new LVSW version of WM6. Working smooth as glass for 3 days now and this morning I turned on the phone, checked my email, adjusted call volume and the thing locked up HARD. I tried everything but nothing worked so I just pressed the reset button on the bottom. It rebooted but hung on the boot splash after displaying the red version numbers on the bottom. After a minute or so the green wireless light began to flash so I thought it was just slow booting, i left it like this for 15 min and it never proceeded to finish booting so I pressed reset again. Same result, stuck in boot splash forever. Since it was just going to sit and run down the power I unseated the battery to turn it off (the power button wouldnt do a thing.) Finally I get to work, I figure I'll put it in bootloader and hopefully just reflash it. As soon as I plug it into the USB cable and boot it up, it came up fine. Anyone have ANY idea what the heck is going on? Thinking now of trying the new WM Black edition v1.2 but with the recent strangeness of the current rom I'm wondering if I'll wind up bricking it. Any advice is greatly appreciated.
[email protected] said:
Running new LVSW version of WM6. Working smooth as glass for 3 days now and this morning I turned on the phone, checked my email, adjusted call volume and the thing locked up HARD. I tried everything but nothing worked so I just pressed the reset button on the bottom. It rebooted but hung on the boot splash after displaying the red version numbers on the bottom. After a minute or so the green wireless light began to flash so I thought it was just slow booting, i left it like this for 15 min and it never proceeded to finish booting so I pressed reset again. Same result, stuck in boot splash forever. Since it was just going to sit and run down the power I unseated the battery to turn it off (the power button wouldnt do a thing.) Finally I get to work, I figure I'll put it in bootloader and hopefully just reflash it. As soon as I plug it into the USB cable and boot it up, it came up fine. Anyone have ANY idea what the heck is going on? Thinking now of trying the new WM Black edition v1.2 but with the recent strangeness of the current rom I'm wondering if I'll wind up bricking it. Any advice is greatly appreciated.
Click to expand...
Click to collapse
Was your battery fully charged?
yep
Yes, 100%, had just taken it off charge about an hour before....
It has happened to me twice
The first time that I couldn't igure out what to do I simply Hard reset the device
The second and last time that happened to me (2 days ago)
after 3 consecutive soft reboots the thing came back to normal operating status..
I suspect that this has to do with ROM
Anyways I sure hope this is fixed with the new release...
Which I may flash later on today...
I'm your average custom ROM flasher, so I know my way around basic ROM flashing stuff.
The situation that I'm about to describe happened on:
GT-I9250 maguro running Xylon 2.1.1 (Feb28), on AK 710 kernel, with a Feipusi 2200mah battery.
The device was connected to a charger that was plugged into a wall. This is a charger that I bought a few days ago and have had no problems since.
I was browsing on xda on the device and tapped on a download link for a ROM, when there was a sudden flash at the bottom of my phone and my phone force shutdown and rebooted. Since the Gnex has the notification LED at the bottom, I don't know if the flash was a notification coming in. If it was indeed the notification LED, then I have no reason to be worried. However, if the flash was caused by the charger, then I'm worried. But I don't know the cause of the sudden flash. After the flash, the phone rebooted, but. ot stuck right after the Cylon (AK Kernel) logo that appears after the Google logo, and kept showing a black screen. In short, like this (Google logo - Cylon logo - black screen). So I pulled the battery, popped it in again, and tried to boot the phone again. The black screen happed again. So I went into CWM Recovery and did a Nandroid restore (Vanir Feb 25 v4.002b). Booted fine. But this whole thing scared me out a bit, so if anyone could tell me what happened it would be really appreciated. Thanks.
Note: I acquired this phone approximately two weeks ago, and the original owner says to have been using the Feipusi battery without problems. I'm saying this because the battery seems to be the only 'unofficial' component in the device.
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
dubbz84 said:
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
Click to expand...
Click to collapse
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
GiantJay said:
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
Click to expand...
Click to collapse
Well i just placed the battery back in, it started on it's own without my pressing anything again, and i've been timing the last 5 minutes. but it seems like it will stay a black screen indefinitely. unless i remove the back of the phone, or snap it back into place, or any kind of micro impact movements it seems, when I do that it vibrates like it's first being turned on, and shows the samsung screen, then the samsung galaxy s3 screen, then it will go black again.
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
topherk said:
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Not picking it up on adb.
dante32278 said:
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
After the first odin flash i was thinking the same thing. But that's the thing, it won't stay on the download mode screen long enough for me to even try to flash anything else through odin. I'm also noticing when connected to the charger, if i make a slight impact against the phone with my palm, the screen will briefly show the battery icon as if the phone is charging when it is turned off, then the screen will go black again. When it is unplugged, is when it will show the samsung screen, then the samsung galaxy s3 screen, then go black again.
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
To me it sounds like maybe your power button is stuck "down"
If you didn't know, the power button has a fail safe reboot that happens after holding for about 10 seconds. So no matter what, if you phone is frozen or whatever, holding power more than 10s will cause it to reboot. That would also explain why its turning itself on as soon as you pop in the battery.
toolegit said:
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
Click to expand...
Click to collapse
not recently, and if it was ever dropped, it would be in it's case... But i had noticed that while it was in it's power glove case, sometimes i would have to use more than normal pressure on the power button to get the phone to respond. I was wondering if something was stuck, just haven't read anything like that happening to anyone, and when I used the jig the first time the screen stayed on.
Hi, this morning I was charging my phone, received a call, and phone shut off. It literally did a single ring and then off. I went to turn on the phone, thinking it was just overheated, noting it was cool to the touch. When I went to turn the phone on, it vibrated on boot like normal, except nothing was displayed on the screen. Further waiting (approximately 2 minutes) led to nothing. I attempted to power on again, with the same vibrate, same thing. I removed the charger, then the battery for about a minute. Replace battery, left out charger, same thing. Replace charger, same thing. I had been running AOKP fine previously. Before that I had been running stock AT&T 4.1.1 . I followed Tasks' instructions in his post, I'm not new to this process. I've been following him since the S2 (SGH-I777), never had any kind of brick at all. I've also compiled CM and AOKP myself before and am not new by any means to linux. But I have no clue what just happened here and no kind of recovery or bootloader is available from what I can see on the phone and through ADB. It simply will not power on. I don't have a multimeter to rule out the battery but it seems unlikely to me that in just under 8 months of use the battery died on me. I'm not a heavy user, and typically get 3 days use out of a single charge. Anyone heard anything on the grapevine?
EDIT: I put the wrong release date in the title when I went to look at his releases. It's the 7/9/2013 release.
EDIT #2: I pulled out the SIM card to place in a backup phone and I tried booting the phone again. It started up, got to the loading screen, shut off, and now its back where it was. Considering playing with my SIM in the phone to see if I can trigger anymore activity.
EDIT #3: Success, flipping the SIM seemed to trigger something, I was able to put the phone in Download successfully. Flashing new recovery now, stay tuned.
EDIT #4: When I was able to boot the phone after flashing Jiangyi's AIO (From tasks post). I immediately booted into recovery, flashed 7/20b and 7/14 gapps, looking good so far.
Hi, hoping someone can help.
Having a major problem with my P605 (Hong Kong version), It just will not start up anymore.
Current State:
At the moment, with just the power button, it shows the samsung galaxy note 2014 logo. Then a few seconds later the startup sound will play. Then a few seconds later the samsung boot animation plays. Then once the animation stops and just displays the samsung logo, nothing else. It stays on that, and can stay on it for hours.
Note: The Samsung boot animation has a very pink hue to it, like the cyan and yellow are no longer there. More on that later.
With the Power + Home + Vol Up it says recovery mode is starting, then resets and boots as above.
With the Power + Home + Vol Down it goes into download mode no problem.
Background (Some of it may or may not be relevant, just putting it on here in case it is):
Up until a couple of weeks ago it was stock, but rooted JB (IIRC), then it was accidentally dropped (not by me). It is in a Trident Krakhen case, but that did not stop damage being done, the damage being the backlight stopped working. I followed a Youtube guide and removed/reinserted the ribbon. Put it back together and switched it on, and worked, sorted!
Now I thought as the seal of freshness has been popped, I may as well upgrade it to Lollipop so I can play Pokemon Go. As Lollipop has not been released for HK p605's I used the Irish (I think) firmware. Upgraded using Odin, no problem. So then I wanted root access, so I used the method described on XDA to root Lollipop using "CF-Auto-Root-lt03lte-lt03ltexx-smp605.zip". Again, flashed with Odin, no problem. But the root didn't take, a few programs randomly lost root access, others would not ask for access and just say the tablet was not rooted, etc. I reflashed the file at least 6 times to try and get it to take. Eventually it did.
Forward to the next day, I go to unlock my tablet and the screen has gone all pink, same as above, like Cyan and Yelow have gone. And a black shadow is over the left half of the screen. I restarted the tablet, colours came back, yay. All fine up until yesterday, the pink and shadow were back again. This was late at night while I was in bed, so not near the computer. I restarted the tablet. This time the pink stayed. OK, so I thought I will wipe the tablet back to factory and see if that helps (not done a wipe or anything else up until this point) so I try to go into recovery mode. It showed the logo and the little blue recovery text, then black screen, then normal boot logo and back into the OS. Tried a few times to get into recovery mode, but just kept resetting back to OS. So I told ROM toolbox to force a recovery restart, big mistake! It went into recovery boot loop. Just Galaxy Note 2014 entering recovery" then blank, repeat. No sound, nothing. I think that perhaps if I can turn it off, it may reset the whole thing, I put the tablet into download mode, then go to sleep. In the morning, the battery is dead. Great! Plug it in, instantly recovery boot loop. Fudge! From this point I don't know the battery level of the tablet, so that MAY be causing issues. I plug it into the PC to flash with Odin. Flashed stock lollipop, restarted, flashed stock bootloader, flashed CF auto root. Multiple times in each. Nothing seems to bring it out. The closest I got to something was the tablet telling me recovery was screwed and I needed to use Kies recovery. I left it plugged in for a few hours to try and build up some battery power, the PC does not provide enough power to charge, it makes the screen flicker rapidly when the battery is empty, but all the time while charging it is boot looping and the screen is on full brightness so I don't know how much I gained.
Finally flashed stock KK, and now it just hangs on the Samsung animation logo as above.
Is there anything I can do?
Does the pink hue and black shadow mean hardware is affected? The colours seem fine in download mode.
If anyone could help that would be great as I am scratching my head here.
EDIT 1: OK, I took the casing off, found that the little push on connector next to the usb connector had pried itself loose, I reattached it, and removed/reinserted the screen ribbon cable. All while the tablet was powered on (my old electronics teacher would have had a fit!). Restarted, the pink tinge has gone and the boot animation came up at the same time as the audio. Good signs. But still froze on the 'glow' effect. Tried recovery and YES it went into recovery, although the little android fell over with an exclamation mark over him. But still, progress. So now I am reflashing stock, will see how it goes.