I had Gnabo v8 running fine of my 8013. Then the battery started draining fast and would not recharge. I had the rom, SU, remove phone, and wifi fix all on my ext SDcard.
Wiped and reflashed all using Philztouch recovery.. Got back to KitKat but no wifi. Flashed the wifi fix again. Now unable to do anything. Can't get to recovery. Battery at zero, so can't use USB.
Oh well..........I am in the market for a new tablet. I might try the Note 12 pro, but not unless they release an official Lollipop version.
Try replacing the battery.
I've just replaced my N8000 battery & it looks like new now
There is always a way back. If you have odin you should be able to reflash stock with it.
If you are looking for a new battery take a look at
http://www.amazon.com/dp/B00AFJ5JF2/ref=cm_sw_r_awd_BYbPub1S17QER
A hand full of people have been saying this is an awesome deal!
All fixed
Once I got my charger/cable problem fixed, I charged, reflashed Gnabo, SU, boot, phonefix, and wifi fix.
Back in business. Ordered a backup charging cable, since I know the one I have must be positioned just right
in order to maintain contact at a break in the wire.
Thanks for all the help/comments/advice.
What a great forum.
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Sounds to me like there''s something physically wrong with the phone, probably the battery. Time for a new one anyway. Lithium batteries degrade with use. After ~500 charge cycles it'll have lost upwards of 20% of its original capacity and might show other signs of wearing out like inconsistent voltages. After 2 years of use, you'll be well beyond 500 cycles. A new battery off eBay is pretty cheap, and some sellers include the needed tools.Go to ifixit.com for a tear-down guide. A hair drier can help soften up the adhesive. The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
And FYI, the whole "optimizing app" thing is the OS rebuilding the cache. When you flash your GAPPs package or a zipped Titanium backup it has to build the cache for the new apps. Same as when you do the "wipe Dalvik and cache" part of standard flashing procedure to avoid conflicts. In order for apps to load quickly, Android stores a lot of the necessary data in cache, so when you clear it or have new apps, it has to rebuild the cache. On Lollipop this takes a loooooooong time because of the way ART works.
Planterz said:
The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
Click to expand...
Click to collapse
How can i be completely sure that it's the battery which needs to be replaced? The battery shows charge. When i plug in and boot up it shows enough battery power left.
Currently, without external power it does not go past the google screen on boot. When i plug in power while device is off, the battery meter shows just a little depletion from full charge. When turned on, battery level is 82 %
After all , all this hardware mess up can be the consequence of a bad cm flash ?
the whole "optimizing app" thing is the OS rebuilding the cache.
Click to expand...
Click to collapse
I know this. Earlier it was happening on each boot. Now it seemed to be stopped.
By any chance did you have your phone charging while flashing and booting up your ROM?
ChainFires Son said:
By any chance did you have your phone charging while flashing and booting up your ROM?
Click to expand...
Click to collapse
May be? But not the the first time
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Click to expand...
Click to collapse
Exactly same problem is started with my Nexus 4 ... I really wonder, what is causing this. Meanwhile, have it sorted for you ? is that hardware (Battery) issue?
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself...
Click to expand...
Click to collapse
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
shazR00t said:
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
Click to expand...
Click to collapse
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
I also got the same problem. I thought this is battery problem, so I replaced the battery but problem still there. I thought this is problem of lollipop, never installed CM or anything. It is always running stock android. After that I even downgrade to Kitkat stock version still it is not working. One more thing I noticed is If I don't unlock the device than it will be powered on, but as soon as I unlock it and if it is not plugged in to charger it will be switched off. Any suggestion what should I do?
I have the same thing for several month now.
Always thought it is the dying battery.
theminikiller said:
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
Click to expand...
Click to collapse
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
shazR00t said:
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
Click to expand...
Click to collapse
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
theminikiller said:
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
Click to expand...
Click to collapse
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the image files. If you did that then u don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 20:42 ---------- Previous post was at 20:41 ----------
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the images. If you did that then I don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
I m too facing the similar issues. Phone is getting turned off suddenly when not charging, on charging it is working fine. i have done factory reset and also done factory image reset to 5.1.0. i m still facing the same issues. I don't think so it is related to battery. if anyone have the solution then please let me know.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Try the very basic flash technique by double clicking the flash-all.bat. It's not the same as flashing the imgs one by one.
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
gautam.is.sharma said:
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
Click to expand...
Click to collapse
Ok so Battery was the problem!! Got it changed, phone working fine now. Thanx all!
Ok guys i confirm that this is a battery issue. I took it to the service center and the guy temporarily replaced battery to show me issue solved... But... there i saw another issue due to which i did not buy the battery. I saw half the touchscreen not working (including the navigation buttons ). The guy at the center told its a h/w issue and i would have to spend 7K on it so i left my phone dead for now. The Question is ... can this be a s/w issue.. or result of bad flash which can solve on reflashing ??
same problem with my nexus ,but one thing i noticed that the phone does not power off while in recovery...Any idea??
Guys,
I'm not even sure where to start with what I'm seeing, but maybe you can help me.
I have had Timur's ROM on my N7 2012 for a couple years. It's been crashing randomly, even though I have few things installed on it, and a good power supply. I took it out of my car and put it on an iPad 2 amp supply, and it still crashed a bunch so I knew I needed to wipe and reinstall. I also wanted to go from 4.2.2 to 5+, which I know takes away a lot of the good features I need (like power on/deep sleep).
I booted into TWRP and wiped my tablet, which appeared to softbrick it (I think I have the usage right from searching). I downloaded the Pure Nexus 6.0.1, CM13, and already had Autodroid ROMs to use. I tried to install Pure through ADB sideload, and got it installed. When I finished and tried to reboot, it said I had no OS. When I rebooted, I got the boot animation, and nothing else.
Long story short, I tried Autodroid and CM13, and using CM13 I got it back going. Unfortunately, every time I try to flash another ROM over it, it will no longer go past the boot screen. With CM13, it boots properly, but doesn't like the gapps pico I tried to install (error message when booted, keeps returning to the same pop up error).
I'm quite sure there's something I'm missing, but I don't know what it is.
Thanks!
Eric
Ok, before anyone goes nuclear on me, I think I better understand what happened. When I got ANYTHING to work, I stopped doing anything. As I understand, it wasn't functioning...it was just in a temporary mode of some sort.
After not being able to get it to work properly, I used this: http://forum.xda-developers.com/showthread.php?t=1781250 to try and restore the system. I followed all the directions, except for using the 5.1.1 version of the ROM, and used the corresponding file name for the zip file used.
After doing so, the bootloader won't go to TWRP, but goes to the pic as seen below. I did reboot the tablet, and after waiting quite a while, the tablet came on, but I don't understand what that picture means.
Thanks!
Eric
Ok...I realized that I lost root. I'm fixing it now. I had read before, but didn't understand what I saw.
Thanks,
Eric
I restarted my S4 this evening and now it won't boot past the SAMSUNG logo. I have tried a variety of things to get it going but none have worked.
1) Soft boot
2) Pulled battery and let it sit awhile
3) Tried to boot into Safe Mode (stuck on the same spot with no indication of going into safe mode)
4) Wipe cache from CWM recovery mode
5) Reboot from CWM recovery mode
Everything is pretty well backed up but after looking at my sdcard it appears that my camera reverted to internal memory about a month ago so I am after any ideas to get those images.
My phone is rooted and running an old 4.2.2 stock Android OS with USB debugging enabled. I was wondering if by re-flashing the OS it might fix the boot issue and be able to recover the images. Or maybe even flash CM. Or maybe some other thing. I found something about adb but I don't want to do anything else yet until someone more savvy than me weighs in.
Unless it's a hardware issue, then flashing a ROM might work.
The other option is to try a reflow. Reflow means heating your phone up so that the solder becomes liquid and any cracks in the solder (which can cause a bad contact), or any piece that isn't seated right, will be remedied.
did u tried to flash stock firmware using odin?
Deleted
I got it going. I first spent a number of hours getting to know adb which was a dead end because I couldn't get it to see beyond the base directory. I then just flashed the stock rom and everything was there including things that shouldn't be like apps, contacts and texts. The phone is back exactly where it was before it boot locked without having to mess with a single thing. I am grateful but a bit confused.