I hate to ask, but I have to. I'm really stuck with my phone. It will boot but sticks on the Samsung Galaxy S II screen. I am able to get into recovery, but upon a data wipe, it hangs on the same screen on first boot. I am able to get into download mode and flashed EL26 repacked via ODIN, and upon reboot, it just hangs on the same boot screen.
Now some background...
About a few weeks ago, I started having crazy battery problems. Then, a few days ago, my phone would reboot anytime I did anything to it, turn the screen on, it'd reboot sometimes, or make a call, it'd reboot, text, it'd reboot. Basically, non stop constant reboots. I assumed it was just a jacked up battery, because I had no problems with the CM10 alpha I'd been running for the past two months, and now all this. I bought and overnighted a new battery and upon trying it out, I still had the same problems. Then, last night, from bed, I mobile odin'd el26 repacked as it was the only thing I currently had on my SD card, upon reboot, it stuck on boot screen and that's pretty much it since then.
Any ideas? Again, I can get to download mode and recovery, but even flashing, even a clean wipe, it just hangs on the screen on boot.
Since you mobile odined el26 kernel and you are coming from Jelly Bean it won't boot because you need a JB kernel to boot jelly bean.. And an ICS kernel to boot an ICS kernel..
With that said, to avoid any crazy scenarios, I would just grab a One Click Odin(any one will do) ... Boot into download mode.. Connect to PC and go from there to be safe
-TeaM VeNuM Like A Boss
try going into download mode and using one-click odin to go to el29 or 26
Jesus I'm dumb. I remember reading that a few months back. I forgot the el26 was just the kernel and you had to flash to it and then flash your new rom immediately. Thanks.
Any ideas on the crazy reboots?
try a different rom..or maybe ur battery is not being held in tight by ur phone or something..try sticking a piece of paper in there
supersaeed said:
try a different rom..or maybe ur battery is not being held in tight by ur phone or something..try sticking a piece of paper in there
Click to expand...
Click to collapse
Ok got it booting into EL29 and still having reboot problems. I'm thinking it's a power button issue or something. Sometimes when I press it to turn the screen off, it pops up the power menu, and sometimes it just reboots then.
I went ahead and dropped the $100 on a refurb through Assurion bc I need my phone for work and can't keep delaying it.
Related
I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
....
FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.
I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.
I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.
Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.
So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.
That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.
I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....
I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]
Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.
I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?
after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone
I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.
I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!
So my S2 is stuck constantly rebooting before I can attempt to get the phone into download mode or back to CWM.
The best luck I've had so far is to rather consistently press the power button while the phone is trying to boot. This keeps the phone booting for the longest, and I've even made it into CWM and ODIN doing so. However anytime I stop tapping the power button, the phone will reboot.
At one point I did do a super wipe of the cache and OS, I just haven't been able to flash the phone back to stock. The same behavior occurs with a charged battery, a battery-less phone plugged into the wall, and a phone plugged into the wall with the battery in it.
I've opened up my phone to take a look at the power button placement. The plastic case is not pressing in the button, and when I press it in myself I hear a distinct click noise as normal. I've even pried away the case with no luck.
What next steps do I have? I do not have insurance with t-mobile or warranty of the phone. I do have the knowledge to solder if needed. Are there more options for me to try, to fix this issue?
EDIT: So this time I was able to get into ODIN, after letting the phone sit and do nothing for a week. No idea why it works now. I flashed back to stock. Will give it a day or two and then flash back to custom.
If you can get a computer to recognize the phone it can be fixed using adb or another method.
Sent from my SGH-T989 using Tapatalk
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
ralewis said:
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
Click to expand...
Click to collapse
what i know for sure is that it should be T-Mobile uvlh1 which im 98% sure is the standard base band when i got my phone
but other than that is your phone already rooted?
also when you go in CWM what does it say?
Does it just freeze?
So I did go through with the link and flashed back to stock. Everything seems to be working great now. I did nothing to the phone and it stopped acting up.
What used to happen is the device would act like I was holding the power button constantly. It would simply reboot, but never freeze. It felt Software independent, which worries me that it'll come back.
The problem started slowly, where my phone would reboot on its own here and there. Gradually getting worse. This happened after applying some OTA updates for CyanogenMod10. Though it didn't happen immediately after applying the updates.
Hello everyone,
My phone is NOT rooted. Earlier today it was stuck on the Samsung Screeen when I turned my phone on. I then used the power, camera, volume down button combo to bring me into recovery mode. Now everytime my phone turns on it stays in recovery mode. I can scroll up and down on my choices but there is not a key that I can press that will select a choice. Any ideas for how I can get my phone to work?
Screen I am stuckl on reads: "android system recovery <3e>
enter: OK key, Select : Vol UP/ Vol Down
reboot system now
apply update from SD cared
Wipe Data/factory reset
wipe cache partition
then theres an exclimation mark in a triangle with the android dude below that
#manual Mode#
If you don't care about existing app data, Odin would be a great choice. Either Odin-ing in a custom recovery or a fresh stock system would get you out of the situation.
Sent from Samsung Captivate Glide @ CM10.1.2
Sounds like you tried to do something and the phone didn't like it, hence you boot back into recovery on it's own.
Use Odin and reflash stock.
Much Thanks
Thank you very much for the responses, for some reason I was under the impression that your phone had to be rooted in order to use odin, much thanks!
I do not care about my personal files getting lost, but just out of pure curiosity, roughly, how would one accomplish that?
I'm try out odin now!
Back to my old problem! Any ideas?
So odin passed twice with all the stock software. Now I am back to my old problem that I had before I was stuck on the recovery screen (hardware issue? idk) When my phone boots up it stays on the samsung screen for 2 mins, then it lags like crazy on the 4g screen (sound and video), and it stays frozen at the Galaxy S screen (for over 6 mins). I need a working phone, luckily I am elgible for an upgrade, but really dont see the need to spend 250 to upgrade my phone or spend 100 for insurance to replace it!
Any ideas anyone?
Thanks again for all of your help so far
apugslovesxda said:
So odin passed twice with all the stock software. Now I am back to my old problem that I had before I was stuck on the recovery screen (hardware issue? idk) When my phone boots up it stays on the samsung screen for 2 mins, then it lags like crazy on the 4g screen (sound and video), and it stays frozen at the Galaxy S screen (for over 6 mins). I need a working phone, luckily I am elgible for an upgrade, but really dont see the need to spend 250 to upgrade my phone or spend 100 for insurance to replace it!
Any ideas anyone?
Thanks again for all of your help so far
Click to expand...
Click to collapse
Well, first boot of flashing any custom or stock rom takes a bit to fully boot. If you're stuck at the Samsung or Galaxy S screens, then you should reflash. If you have tried that and still having the same issue, then try a few more times. I've read posts of people having constant boot loops on flashes and they finally got one flash to properly stick after many tries.
So odined again and again, this time my phone eventually did turn on but it literally took 30 mins. When it did turn on I had no network connection nor could I use my touchscreen, it eventually shut off. I'ma go get robbed at the sprint store in a bit lol.
End Thread
End Thread- I got a Samsung Galaxy Note 3. My god- this phone is amazing. Kinda bull**** that I got nothing for my old phone with full insurance when it seems like it was a hardware failure!
Can't wait to play with this beast of a phone tomorrow!
My Galaxy S3 keeps shutting off during boot. I encountered this problem while running Cmod 11. Was using poweramp playing music off my 64gb exFat microsd card, and suddenly Poweramp encounters "Error too many files" and promptly shuts the phone down. (Poweramp has been giving me strange problems before this, like that error just mentioned, and scanning for changes when there are none, but this is the first time the error caused the phone to shut down).
After rebooting it, The S3 gets to the boot screen and upon opening an app, promptly shuts down again. Further attempts result in the phone shutting off during the boot animation, and finally now the phone simply shuts down right before the boot animation. (note: it doesn't reboot. It turns itself off).
I thought it might be a problem with Cmod, so I wiped everything and using CWM, installed slimkat. Same problem. so I went and installed stock android using Odin, and now I'm back to stock. STILL same problem.
When I have the phone plugged into a computer, it seems to get further than the boot animation before shutting down (sometimes it gets to the lockscreen before shutting down again).
Any idea what's causing this problem? I have no problems with erratic shutdowns during recovery and download mode.
How old is your battery? Might be time to replace it.
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
cheezyphil said:
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
Click to expand...
Click to collapse
They're not as heavy to load.
Was any modification done to your phone (software) about when that started happening?
The s3's been on and off custom roms for a year now
cheezyphil said:
The s3's been on and off custom roms for a year now
Click to expand...
Click to collapse
I mean before it started happening. Or were you on the same ROM/version of that ROM for a while when it happened.
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
cheezyphil said:
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
Click to expand...
Click to collapse
Well if you can get in recovery, I would suggest doing a clean flash. But chances are that it's your battery giving out.
If you want to test, borrow a battery from another S3. I know with T-Mobile you can go to a store and they usually have a device on hand that you can borrow one from to test it out before spending money on it. I imagine you can do this at AT&T stores as well.
had the same problem with my atnt galaxy s3
i have the same problem,,i am using cm12 ryt now,,i tried to put every single rom and same thing happens,,i also brought it back to its stock firmware,,and still the problem occurs... did u find any solution for it,already?
:crying:
OK all I am sincerely reaching out as I am out of ideas. Here is the situation...
Issue : Last evening, running most recent Liquid Smooth 4.4 (Superb ROM, I don't feel this is really at fault just relevant and thorough), I had been doing some heavy tethering when I picked up my beast and stepped out for a smoke. As I am reading up on moto360's 2 1/2 hour sellout I get a random reboot. Eh, no biggy ... it does happen. (Not often, or at all to speak of in my case just stating.) Right after reboot I hit the power button to make a forced boot cycle and it rebooted again before I pressed anything on screen!
Now SOMETIMES I will boot past the initial "NOTE II" splash (NOT often at all ... usually get reboots, splash hangs, or the phone simply turns off on its own from here) If it does make it past Note II splash it will reboot, hang, or simply turn off from here as well.
Steps Taken: I firstly, attempted a restore... no dice. I attempted a fresh install (TW, SlimRom, and DU) ... no dice dos. OK hmmmm
Now to all mighty ODIN (L900VPUCNE2_L900SPTCNE2_1561791_REV04) .... NO FREAKING DICE!!! WTF?!?!? I additionally attempted MC2_STOCK_with_COUNT_RESET-20130511 ... no bueno!
I still have access to Recovery and Download soooooooo ... I lay down at the mercy of you the community!!!
Thanks in advance and if you need more info PLEASE don't be shy!
Same issue here!!!
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??
Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.
Exact same thing
I've been running the latest nightlies of OmniRom. And yesterday, out of the blue, random reset then bootloop. No luck with anything, recovery, odin, etc.
Did Sprint deliberately brick our phones?
I'll try the odin to stock to see if I get any luck there. But if anyone else figures it out, it'd be nice to know the fix. Thanks!
No luck going back to stock. It's dead Jim.
I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
If my case, my phone would boot loop around the splash screen. on the battery power only. I could go into recovery and download mode with no issues and stay on for hours. If I connected it to, say a PC, it would boot, but would random shut off within five minutes. But if I plugged into the wall charger, it would boot with no problems. Stay on for hours. If I plugged it from the charger, it would immediately shut off and try rebooting which it would just boot loop.
Luckily, the batteries are pretty cheap at $10 to $20 on Amazon. I went with the Anker for $15 to get me by till I get my next phone, which will probably be October; I'm heavily learning towards the Note 4
Replace the battery
I had the exact same issues. I ended up buying a $10 battery on amazon and it solved the problem. I did go through all the flashing, odin to stock, etc. All was pretty good when plugged in to a good power source. It took me about 4 hours of trial, error, reflashing, etc before I realized it was probably a battery issue. The new battery has solved the problem.
lovekeiiy said:
I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
Click to expand...
Click to collapse
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?
crackrock360 said:
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??
Click to expand...
Click to collapse
I couldn't flash any of counter reset rom through anything but TWP so i have to boot into download and update away from Philz. AFTER the recovery update I started making headway. but couldn't ever seem to make it past boot no matter how much batter is charged. I was beginning to think it was something that died on the inside (heh...heh)
After reading through some of these greatly appreciated replies I am going to plug her up to the wall and try the ne2 counter reset again(12:58 am). ... AND I may go throw some cash at a battery juuuuuust in case. (I do tether 100gigs daily sooooooo it does make sense that it could have burnted up lmao!)
UPDATE 1:25AM : I did as advised and it does seem battery has taken a dive! hmmm so weird! It still shows having power and charging. But after being plugged into wall I made it booted into a fresh ODIN install!!! (keep in mind that AS SOON AS odin gave me a pass I switched to Wall outlet!) I have even performed a power cycle to confirm it wasn't a fluke! I will indeed be out first thing in the morn to get a new battery!
AGAIN I can not thank you all enough ... I would have never thought of that. (you would think it would be one of the first things but eh you live and learn.)
I will update with any new progress!
cheers!
crackrock360 said:
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?
Click to expand...
Click to collapse
'When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.' EXACT CIRCUMSTANCES AS I SIR!!!
Mine does the same and hangs .... right? HIt the power button and as soon as it lights up to start to boot then plug in the power cable. (the freezing while off and charging is a known bug in at least two roms i believe)
Congrats Rubledub!
As for me, I'm still screwed. Invested $40 in a battery (had to have it today, couldn't wait on shipping)
With the new battery fully charged I still have the same result!
crackrock360 said:
,,, Do the batteries go bad instantly?
Click to expand...
Click to collapse
There were probably signs of the battery going bad, but misread. But in my experience, it went to total crap instantly.
The signs of going bad were shorter battery life, getting stuck/freezing when trying to charge the phone when off (there's that battery graphic that shows up). Unfortunately, I did all kids of other stuff before I really figured it out, and looks like a messed up my modem and now cannot connect to 3G. Kind of irritating, but luckily, I spend 75% of my time in LTE areas. Just got to ride this out till the Note 4 is released.
Here is thread of when I was having trouble: linky/URL]. It's a lot of me trying slightly different things with no changes in results. Plus, I was a buddy's house who was in a 3G only area. The worse part, my phone did this the day before I left to spend the weekend five hundred miles away from home at a friend's house to visit.
sloanmeister said:
Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.
Click to expand...
Click to collapse
Just chiming in to say this worked for me! Thanks!
Joelski144 said:
Just chiming in to say this worked for me! Thanks!
Click to expand...
Click to collapse
Oh i agree! Thats is what had me so baffled ... Not even the odin installs were breathing life, and Odin ALWAYS works for me. If Odin isnt getting it done and neither is a battery then your problem may be far more serious???
Weird Recovery Lag and bootlooping after CM12 update
Hey guys,
I came across this thread and the issues I'm having sound so what similar, so I thought you might be able to help.
I have two Samsung Note 2(l900) and running on cm12 as of yesterday morning. I installed the new nightly manually on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
I'm back on stock rom and the device is working great but takes forever to get into manual recovery which I believe is why it is having issues booting Cm 12