JB update screw up - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Just thought I'd pass along my experience with upgrading to JB.
I have an international GT-N7000 which I was running the last ICS from Samsung, and with the Speedmod .13 kernel.
I never flash anything other than an official release.
I updated via pc-odin to the April DBT version downloaded from Sammobile.
After updating, I uninstalled SU, then loaded the Speedmod kernel for this release (LT4), via pushing it through recovery.
After rebooting, the splash screen lit up, then went blank, but the sound continued. NO video, or button lights.
Pulled battery, no go. I then downloaded (what I thought) was the Philz kernel for this version, rebooted. Everything
came up, along with the nags about not being rooted for some reason. I turned around to do something, and noticed
that 2-3 minutes later the battery was down 15% than 2-3 minutes earlier, and, the back was WARM. Pulled battery,
rebooted, still no go. Reflashed the entire machine, pushed Philz for (what I thought) this version (LT4), rebooted,
and again, slow, battery diminishing, back warm). Ran quad, score was 1/2 of what it was before the flash.
Did some more checking and there it was, I didn't upload the CORRECT kernel. Once I downloaded the CORRECT
kernel, rebooted, charged it up, and the back is not warm, battery sips juice, quad score back where it should be.
With all the roms, kernels floating around, might want to WAIT til daylight to update, instead of after a long day
at work, dealing with idiots, and before 10pm at night...ESPECIALLY if you are in your 50's
That or grab some red bull or something, and double check those kernels.
Might help someone dealing with battery drain, slow, freezing displays, poor quad scores etc...

Related

[Q] Something is wrong with my N1...

Over the past 12 hours I've had to pull the battery 3 times...
The phone was running fine all day (and generally is always very stable for the months I've had it). I put it down last night before I went to bed and when I picked it up again for some bedtime browsing the screen wouldn't come on. I pressed both the trackball (I have CM6 on it) and power button, nothing. I then plugged it in (I knew it was low, but not low enough to power off) and nothing, no light, nothing. I then got a touch scared. I pulled the battery, put it back in and it rebooted. It was fine for the rest of the night...
I plugged it in for the overnight, and when I woke up the light was still orange. The screen again wouldn't turn on. Battery pulled, it rebooted, and it was usable (full charge). I left the phone alone for about 20 mins (unplugged) and now it's back to being unable to turn on the screen.
- I've had CM6 final on it since soon after release with no issues
- I generally use Pershoot's kernels and I think (think) I updated to the latest .35 kernel yesterday. Again, I've never had an issue really in the past
- Updated TBA Pro, added the screen calibration apk, and removed quick office.apk via Root Explorer.
That's about it for "new" stuff I did yesterday.
Gonna put on Pershoots latest .34 kernel (I really don't think that's the issue) and see if that makes a difference (I always use the .35 kernels). I also wiped the dalvik cache. If that doesn't work, I'll remove the calibration app.
Any other opinions? Possible battery pooched? I charge it nightly, but other than that there hasn't been an issue. Certainly would be the first time I killed a battery in a phone...
tomedic said:
Over the past 12 hours I've had to pull the battery 3 times...
The phone was running fine all day (and generally is always very stable for the months I've had it). I put it down last night before I went to bed and when I picked it up again for some bedtime browsing the screen wouldn't come on. I pressed both the trackball (I have CM6 on it) and power button, nothing. I then plugged it in (I knew it was low, but not low enough to power off) and nothing, no light, nothing. I then got a touch scared. I pulled the battery, put it back in and it rebooted. It was fine for the rest of the night...
I plugged it in for the overnight, and when I woke up the light was still orange. The screen again wouldn't turn on. Battery pulled, it rebooted, and it was usable (full charge). I left the phone alone for about 20 mins (unplugged) and now it's back to being unable to turn on the screen.
- I've had CM6 final on it since soon after release with no issues
- I generally use Pershoot's kernels and I think (think) I updated to the latest .35 kernel yesterday. Again, I've never had an issue really in the past
- Updated TBA Pro, added the screen calibration apk, and removed quick office.apk via Root Explorer.
That's about it for "new" stuff I did yesterday.
Gonna put on Pershoots latest .34 kernel (I really don't think that's the issue) and see if that makes a difference (I always use the .35 kernels). I also wiped the dalvik cache. If that doesn't work, I'll remove the calibration app.
Any other opinions? Possible battery pooched? I charge it nightly, but other than that there hasn't been an issue. Certainly would be the first time I killed a battery in a phone...
Click to expand...
Click to collapse
That happened to me once when I installed one of IR's .35 kernel. I reverted to pershoot's and all was fine. (IR's new kernels are fine too)
ctbear said:
That happened to me once when I installed one of IR's .35 kernel. I reverted to pershoot's and all was fine. (IR's new kernels are fine too)
Click to expand...
Click to collapse
Ya, maybe... I put on the kernel in the morning though and all was fine all day. I installed his latest .34.7 kernel and wiped dalvik cache. So far so good...
Cheers, had the same issue and sofar this seems to have fixed it

[Q] Phone turns off when charged

So it seems that my phone won't stay on when fully charged. If i leave it plugged in, once it gets to 100% it will shut itself off. I recently upgraded to CM10.1 nightly and have tried 3 different days. I've also found something about using setCPU, but that didn't seem to help either. Also, i can't turn it back on unless it is unplugged from the wall.
To make things worse, i noticed today that when i turned it back on (it turned itself off over night), it was at only 7% battery life. So now i have no idea what is going on.
Thoughts??
Griff43081 said:
So it seems that my phone won't stay on when fully charged. If i leave it plugged in, once it gets to 100% it will shut itself off. I recently upgraded to CM10.1 nightly and have tried 3 different days. I've also found something about using setCPU, but that didn't seem to help either. Also, i can't turn it back on unless it is unplugged from the wall.
To make things worse, i noticed today that when i turned it back on (it turned itself off over night), it was at only 7% battery life. So now i have no idea what is going on.
Thoughts??
Click to expand...
Click to collapse
SoD.
There are quite a few things that can trigger it (like deep idle) but first I'd need to know what changes/mods you made.
So i was running CM 7 when decided to finally update to 10.1 nightly. That was major change and it started happening. Last night i downloaded setCPU, and configured that to keep minimum @ 200MHz when screen is off (hoping to keep it running and not going into deep sleep).
Griff43081 said:
So i was running CM 7 when decided to finally update to 10.1 nightly. That was major change and it started happening. Last night i downloaded setCPU, and configured that to keep minimum @ 200MHz when screen is off (hoping to keep it running and not going into deep sleep).
Click to expand...
Click to collapse
Did you go back to stock and factory reset first? Also, did you restore any system app or data with TiBu?
Are you running with stock kernel? If so, you could try flashing Semaphore.
I do not have a stock kernel, but it was the same one from when i was using CM7. I also updated from CM7 to 10.1 (no from stock), but i did do a factory reset. ANd no programs were restored, i freshly installed them all from the play store. I will try flashing Semaphore tonight and see how it goes.
Griff43081 said:
I do not have a stock kernel, but it was the same one from when i was using CM7. I also updated from CM7 to 10.1 (no from stock), but i did do a factory reset. ANd no programs were restored, i freshly installed them all from the play store. I will try flashing Semaphore tonight and see how it goes.
Click to expand...
Click to collapse
Kernels for GB are quite different than for JB 4.2. When you flashed CM10.1, it most likely also flashed their stock kernel. This is what I meant by stock kernel.
any possibility that you've got a battery that is failing? or if the third pin is dirty, the power management chip could do that, even if the battery isn't fully charged. when the battery was at 7 percent after 'charging', what was the battery level before charging.
have you cleaned the batt terminals on both battery and phone?
hope this is helpful.
Sent from my SGH-I897
To make things even more confusing ... every time i reset the phone it comes up with a new battery level (anywhere from 5 to 17 to 60). new battery time?
Griff43081 said:
To make things even more confusing ... every time i reset the phone it comes up with a new battery level (anywhere from 5 to 17 to 60). new battery time?
Click to expand...
Click to collapse
Indeed, new battery time!

Shutting down problem

Hi,
I'm experiencing this problem more than 1 month. I'm on CM10 with kowalski kernel. It seems my phone sometimes wrongly read battery status and drop battery level percentage from some value to 0 immidiatelly...and shut down occurs at the moment. I thought it could be caused by old battery, but it's not - I buy the new one and the problem still persist and it's VERY irritating...Any solution?
Thanks Jiri
Hello,
It happens also for me but only when I am around 15% and when somebody call me sometimes it fail down sometimes.
It seems that the deep sleep do not allow the system to read a correct battery value when screen came back and the system shutdown because of a too low voltage.
I did not found any solutions in several type of ROM.
Mike
This is a known problem..if i remember correctly tonyp and pengus will fix it in the neew 4.2.2
Sent from my LG-P990 using xda premium
But it's annoying as hell, for me, it starts when my batter is on 50% and low.... 5 - 10 times a day a have to turn on my phone...I cannot use alarm at all....
Andy HOT said:
This is a known problem..if i remember correctly tonyp and pengus will fix it in the neew 4.2.2
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Mmmhhhh I actually cant remembet them stating that it will be fixed. I remember tony mentioning that its a low priority rom bug. It might be fixed with 4.2.2 but i am not really sure. Regarding the issue I do experience it too but only once every few weeks.
Sent from my LG-P990 using xda app-developers app
I also have this shut down problem. A lot. Maybe 5 times a day and its also driving me nuts. Mine does not happen while phone is in charger - so its probably the "battery reporting wrong charge" problem. Im on new bootloader. I've seen it go from over 50% to 0% battery in an instant.
It might have happened before but much less frequently than now. I started noticing the problem a few weeks ago on Pengus CM10 rom with kowalski kernel (before reading about it). I reflashed the kernel a few times and upgraded the kernel once or twice during that period.
I switched to PA 2.6 - 10 without improvement (KK-116). No apps installed (except Antutu)
I even had the problem in TonyPs TWRP 2.4.3.0 when trying to backup my rom once. Phone shut down while running the backup. Plugged wall charger in while phone still being off and saw that i still had battery left - probably 30-50%. The LG charging graphics icon showed this (you know, the one that shows up if your phone is off and you plug in the charger).
I Tried the following using AIO v5 tool without luck:
1) Reintalled unlocked ICS bootloader
2) Reverting to Old bootloader / partition - then back to new bootloader. Then installed ROM.
I have also tried installing Django Manouche X 1.6.1 (KOB 0.7 kernel) and running Antutu a few times (right after first boot + reboot) with the same result: shutdown. No apps installed.
I can always reproduce the issue: run Antutu benchmark 1-5 times in a row manually on battery. Plugged in, this does not happen.
It happens with or without OC/UV.
I havent tested it extensively, so I cannot be sure, but it seems to me that the rom/kernel isnt the problem since it also happened (once) in TWRP. Could it be the bootloader? Granted this is only a guess, since i have NO knowledge of Android programming or inner workings. Or maybe this is what happens when the LG battery is dying? I got the phone just as it came out.
Edit: BB 30A
I guess i have the same problem but either worse or something totally different.
Regularly around 70%, my battery just drops to 0% and my phone shuts off. It can happen anytime for me and it usually happens just after about 10-15mn of using my phone.
This morning it shut off at more than 90% and then got stuck in a bootloop i presume because it says it doesn't have battery.
Update:
I tried reflashing 30A BB. Didnt help.
Tried Django Manouche X 1.6.1 with kernel without zRAM or ramhack mod. Didnt help.
I Also tried PA 2.6 - 11 on old bootloader, and the battery-jump shutdowns continued when running antutu.
Flashed (completely stock - no rooting etc) ICS 30A with 30A BB through AIO v5. Didnt help. No tweaks or apps (except Antutu) installed. On Antutu run number 5 the phone restarted (with bootloop). Had about 36% battery. Pulled battery, rebooted, phone shut down before booting ROM. Plugged in charger, booted into ROM, showed 100% battery for 10 seconds before showing 30% battery. Tried with quadrant and 30% battery: phone shut down on run 2. Pulled battery, rebooted. Messed around with camera and gallery for 5mins at 26%: phone shutdown.
Im totally lost ... if its not the battery (as indicated by the first post (OP)) i have no idea whats going on. Maybe some other piece of hardware inside the phone is to blame. A piece of hardware that is only called upon when on battery and not when on charger. Maybe a power regulator (or some such thing) is broken?
Next test: Stock GB with GB BB
Edit: Well, the GB ROM + GB BB didnt work either: Gueste2X GoodBye v2.0R + 20L BB rebooted at 75% battery running Antutu. It showed a pop up about low battery and shut down shortly after. For the first time the battery icon still showed 75% when it shut down though.. And this time it showed 21% (not the usual 0% battery) when rebooting to ROM.
I think Im throwing in the towel regarding the software.
My dad also has an o2x, so i will try and swap the batteries and test both phones. I will ofcourse run antutu several times on my dads phone before swapping the batteries..
Update 2:
So i tried my dads O2X battery in my O2X. I Ran Antutu quite a few times and my phone didnt shut down. So I'm pretty certain my battery is messed up which is the reason my phone shuts off "randomly" showing a sudden 0% battery.
Through a google search i found a guy stating that the battery often starts "bulging" when its messed up like mine. His test was to lay the battery flat on a hard even surface and spin the battery. If it keeps going for a couple of seconds it might be messed up. My battery is definitely "bulging" and spins for much longer than my dads. His spins for less than a second. Mine spins for maybe 2 seconds. Not very scientific, but i could definitely see a difference. And i can see the excessive bulging on my battery if i look at it from the side.
So Im ordering a new battery tonight - the originals dont cost much thankfully.
Hope my walls of text can help others in the same situation.
Last update (promise):
Got the new original battery today. Charged it to 100% and used my phone for various tasks until the battery hit 70%. (This was my old batterys absolutely certain "breaking point" when running Antutu benchmark. On my old battery Antutu would crash on first or second run every time when battery is at 70%.)
On the new battery i quit running Antutu after the 13th run in a row without a "battery low" shutdown. The battery was at 40% after the 13th run.
I lay the old and the new battery flat on my smooth metal mousepad and spun them around. The new battery spun for less than 1 second. The old battery spun for almost 4 seconds on one side - almost 3 seconds on the other side.
Two working batteries (my dads 2+ year old battery and my own brand new one) performing equally and at the same time differently to one defective battery. It lends some credence to "the guys" theory that battery defects might result in "bulging" of the battery.
Which means, your battery can be defective but not "bulge". If however, your battery is "bulging" something likely is or will be defective. Fantastic knowledge to posess, if true.
It might seem like a "well duh, thats obvious" revelation, but Ive held my old battery in my hands a lot the last 2 years (especially lately) and I did not notice the "bulging" at any time.

[Q] Weird unprovoked Jellybean Samsung logo brick question

Hi,
A few days ago I upgraded my Note from a very ancient (stock) Gingerbread ROM to (stock) Jellybean. I hadn't been getting OTA updates because the Gingerbread was originally German rather than UK, so quite a long time had passed without any updates. Anyway, because of the no OTA, I used Odin. Everything went fine and I had a nice few days of usage, although the battery consumption seemed to suddenly be quite high, mainly due to additional wakelocks from the new Google Search it looked like. The night before last at about 3% the phone turned itself off, which is unusual as normally the battery will run itself lower than that. BTW, it's an official battery bought just a few months ago to replace the one before, which was getting old.
Yesterday evening when I went to use the phone it was dead. Completely unresponsive. It wouldn't charge either. (The battery had been at about fourteen percent I think, so it should have still had a lot of juice left.) Turning it on would leave it stuck on the Samsung logo only. Recovery mode didn't work, but I could get download mode up, so I installed the Philz kernel as people have said, and then did a reset using that, and all was okay again and after reflashing the ROM I could use the phone again, although because of the reset I had to set everything up again.
Just wondering what people think caused it. Just a weird coincidence, or something else? As far as I'm concerned, the problem has been sort of mitigated for now, but definitely not fixed, because what's to stop it happening again? Has anyone heard of strange things going on with Jellybean? I know there's an issue with flashing/resetting from ICS, but I never used that so I don't think that's an issue, and it looks like it was just a soft brick only. Still, a bit weird and worrying. Does anyone have any ideas?
That was caused by an unexpected shutdown of your phone - if you remove the battery without it fully turning off then you will get it and yeah, blame samsung.
The only way not to have it again is to flash philz kernel with the bootloop fix BEFORE you get the bootloop. Alternativly, if you get it again then you can try what is in this post:
http://forum.xda-developers.com/showthread.php?t=2186229
XxPixX said:
That was caused by an unexpected shutdown of your phone - if you remove the battery without it fully turning off then you will get it and yeah, blame samsung.
The only way not to have it again is to flash philz kernel with the bootloop fix BEFORE you get the bootloop. Alternativly, if you get it again then you can try what is in this post:
http://forum.xda-developers.com/showthread.php?t=2186229
Click to expand...
Click to collapse
I didn't take the battery out though. It was low but not dead.
Since then it has happened once again, a few days ago, this time at 93% full. I was doing nothing at all taxing to the phone. I was just in a shop listening to an mp3 with the screen off, and then it stopped and the next thing I saw was the bootloop. Luckily (thanks to the new kernel?) I could just delete cache/dalvik and be back up and running again without having to reinstall everything. Today my screen temporarily went a weird purple colour like in this thread: http://forum.xda-developers.com/showthread.php?t=2216867 . Sounds like it's just dying in general really, rather than anything else. My phone contract upgrade date is in two days. Purely a coincidence of course. Weird how phones tend to last about the length of a mobile phone contract. Until then I'm just running on power saving mode and hoping for the best.

Kernel Wakelock 6.0

Im running stock rom 6.0 with various kernels (lately code blue, but used to be HC). Im rooted.
Ive dealth with these kind of system related wakelocks many times espeicially in 5.0, and even reflash to stock wouldnt help sometimes. So i know what to do to find the culprits of wakelocks but not this one.
Android stats dont know whats up, but the wakelock is not consistent, it comes up for a minute at a time then takes a one minute break and then starts up again. its as if something tries to sync and fails then tries again. i went through the entire phone in crazy detail couldnt find anything that could possibly do it.
Gsam says its the kernel. so i reflashed the kernel, nothing. reflashed stock kernel and then flashed a different kernel. nothing. tried using stock kernel (no encryption) wakelocks still there.
I have no clue what to do other than reflash the factory image. the wakelocks are going on no matter what and i loose about 1% every 25 minutes even though my phone is laying there on the table for 5 hours.
any ideas?
thanks
EDIT:
Did some more reading and im going to assume its a wlan_rx wakelock, because its happening for 2 days straight and the only thing that has changed is that im now at school for 9 hours on their wifi network. at home this issue does not happen (i think)
russian392 said:
Im running stock rom 6.0 with various kernels (lately code blue, but used to be HC). Im rooted.
Ive dealth with these kind of system related wakelocks many times espeicially in 5.0, and even reflash to stock wouldnt help sometimes. So i know what to do to find the culprits of wakelocks but not this one.
Android stats dont know whats up, but the wakelock is not consistent, it comes up for a minute at a time then takes a one minute break and then starts up again. its as if something tries to sync and fails then tries again. i went through the entire phone in crazy detail couldnt find anything that could possibly do it.
Gsam says its the kernel. so i reflashed the kernel, nothing. reflashed stock kernel and then flashed a different kernel. nothing. tried using stock kernel (no encryption) wakelocks still there.
I have no clue what to do other than reflash the factory image. the wakelocks are going on no matter what and i loose about 1% every 25 minutes even though my phone is laying there on the table for 5 hours.
any ideas?
thanks
EDIT:
Did some more reading and im going to assume its a wlan_rx wakelock, because its happening for 2 days straight and the only thing that has changed is that im now at school for 9 hours on their wifi network. at home this issue does not happen (i think)
Click to expand...
Click to collapse
Just wanted to say I fixed this issue on my phone and it was caused by the app "Gasbuddy" uninstalled it and everything is much better now

Categories

Resources