So I tried one of the framework mods that changes the battery icon but unfortunately it didn't work. I wiped everything and decided to start from scratch. Now the battery gets stuck. It would show like 30% and it will stay there until the unit is restarted or if it dies. I tried reflashing the firmware and clearing all my data but nothing is working. Any help?
From the Tab.
www.twitter.com/ayman07
Deleting data/system/batterystat.bin seems to have done the trick.
Edit...
No it didn't.
From the Tab.
www.twitter.com/ayman07
Related
Ok, this is a fun one...
I was up late last night (too late to be doing anything on my nook apparently) and I opened CWM to see if there was an update for it. I noticed it could check for updates to my ROM, so I found the new nightly (160) with it. I decided to install it to see if that would be an easier way then manually downloading and flashing. It cam up with options to wipe cache and such, and I did not realize until too late that the Data and Cache options were one in the same.
So I set it to do a backup, then wipe the data/cache, and dalvik cache. When it booted back up I had lost everything...obviously. So I rebooted into recovery, and restored my backup. Once finished, the screen went blank and did not come back on.
Now I get nothing, no response from the screen. Today I DID plug it into the usb on my work computer and it tried to install drivers so I think it may be on...
Anyone have any ideas?
Anybody?
I'm hopin it is on and that the battery will die...but I am not sure that will solve anything.
Any suggestions would be appreciated.
Go here and start again: http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Make sure you use the latest version of CWR (3.2.0.1)
The problem is actually that I get no response from my screen. It does not turn on, flash like it's going to work, DO anything. That's what has me so worried
dna_d said:
The problem is actually that I get no response from my screen. It does not turn on, flash like it's going to work, DO anything. That's what has me so worried
Click to expand...
Click to collapse
It is fully charged and you get nothing with a bootable SD card installed? Have you tried this while still plugged in to the a/c current?
I do not know about being fully charged...but I HAVE tried it plugged into USB on my computer. Still nothing.
Ok, I got it on! Not sure if this was it but now it complained about low battery. I had previously plugged it in for a whole night and got nothin. I think I will use your previous link to just wipe it all and start from scratch.
-------------
Edit: I am back up and running, thanks for your advice!
This is on two standard Galaxy S5's, with standard ROM, etc - not rooted, or anything else.
Every time I turn off WiFi, or enable Mobile Hotspot, I get 'Unfortunately System UI has stopped'.
To fix I have to Power off/on the phone.
(Turning on WiFi is no problem, just turning it off.)
I have gone into 'Safe Mode', and same issue, so it looks to not be a bad App.
I have also uninstalled 'Google' updates, and again no change...
Any thoughts?
All of a sudden my S5 showed the exact same error message for no aparent reason... I didn't do anything, and now I can't use my phone at all because of that bug. It happens on every boot so I can't even unlock my phone. Tried reinstalling everything, ROM, recovery, kernel, with/without root = still same, what just happened here??
EDIT: Same thing if I'm in Safe Mode -_-
Seeing noone knows a solution here's what I did yesterday.
1. Backed up all my stuff from internal storage to the sd card
2. Did factory reset in TWRP recovery
3. Flashed completely stock official firmware from Samsung
4. Waited for it to boot up and try to restore some of my settings (it restored all folders on their places, made same amount of home screens as I had before the reinstall and downloaded all of my previously installed apps from the Play Store, ofcourse without the cracked ones, and it also restored most apps' data as well so it's not as bad as you may think to factory reset and reinstall everything)
5. Started rooting, flashing TWRP again, installing Dolby Audio, Xposed and everything I had before, took me one full day to set it up as it was before.
Now when I set it up I always make a nandroid backup from when things are working fine, in case it goes crazy for no reason again... Good luck!
when the wifi radio is acting weird, a dirty flash of your current ROM susually fixes is as its probably a radio issue. Id do that before doing anything drastic like the boot-n-nuke Odin flash and starting from scratch (which will fix that issue)
I don't think I have a ROM issue, as I have two S5's, and both have the same issue... and both are standard ROMs.
I will do a factory re-set on one at some point, but this looks to be a 'simpler' issue.
I have tried a full Cache delete, as well as other 'clean' processes.
Nothing works.
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
koragg97 said:
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
Click to expand...
Click to collapse
well, you can wipe cache, and dalvik 3x each (not kidding about the 3x each), then dirty flash the rom, pray to the gods of android, reboot. If failure occurs, its Odin Nuke time unless you want to try to flash an individual radio file by itself (not recommended)
Hi guys
i have a custom rom, nougat 7.1 installed and its been working fine. last night i installed an aftermarket battery replacement as the other wasnt holding a charge. after turning on by simply pressing the power switch it went straight to twrp recovery and kept doing so. this morning i cleared the cache and data to start again which was a bit of hassle and it then booted fine. however, i just restarted again and its in the same loop.
i have checked for any obvious obstruction under the rear case that could be pressing against the volume keys but there isnt anything.
any ideas?
cheers
Did you try to reflash everything, e.g. also the ROM?
AndDiSa said:
Did you try to reflash everything, e.g. also the ROM?
Click to expand...
Click to collapse
i didnt really want to do that unless i really had to. as i say, before the battery swap it was fine
But if you cleared already cache *and* data all your data is already lost, e.g. it's like a factory reset. So flashing a new ROM will not worse the situation ...
AndDiSa said:
But if you cleared already cache *and* data all your data is already lost, e.g. it's like a factory reset. So flashing a new ROM will not worse the situation ...
Click to expand...
Click to collapse
well, i just went to restart and was going to reinstall but it booted properly. i then did a restart and again it booted fine. i dont get it.
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.
Hi everybody.
Dis morning I woke up and I realized that my phone was gone. I used AOSP Extendend ROM when it happens. At first, the rom completely froze. I thought it was a bug, so I rebooted the phone, but after did dis, the phone kept on rebooting and froze on first screen and I couldn't do anything. Touch didn't respond, nothing worked.
So I tried to go on recovety, but nothing.
At the end, I gave up about take back my data and try to install the stock ROM through MiFlash. I tried different stock ROM, but at the first they works, but during the installation guide they froze again and reboot. I can't even finish the setup!
So I tried again, unlock bootloader, flash TWRP, but still there:
- only TWRP v2.0 works, other versions won't start
- even with TWRP v2.0, after did wipe everything and format, when I tried to install a custom ROM, even TWRP froze and reboot the phone
- TWRP is pretty useless, it keeps on froze and when I boot recovery again, TWRP is locked and I have to format everything again, but still don't work.
Someone could tell me what happened to my phone? Any suggestions about what I could to to install something on my phone?
Pls help me, I am completely lost and disperate
You may in deed have a serious hardware problem.
What you can do without opening it up is to try charging it overnight, and see how it works tomorrow.
You have tried everything else you can think of, I assume, like wiping & formatting everything you can in TWRP, and possibly "repairing file system" if there is such an option.
The next thing I would try is opening it up and disconnecting the battery for a while, then connecting it again to see what happens.
cobben said:
You may in deed have a serious hardware problem.
What you can do without opening it up is to try charging it overnight, and see how it works tomorrow.
You have tried everything else you can think of, I assume, like wiping & formatting everything you can in TWRP, and possibly "repairing file system" if there is such an option.
The next thing I would try is opening it up and disconnecting the battery for a while, then connecting it again to see what happens.
Click to expand...
Click to collapse
Ok, I will listen your tip. Yeah, I have tried everything but nothing. Technically, I bought this phone last december, so it's still covered by warranty, but I have to send it to China, I would avoid that if I can.
I hoped there would be something that I didn't but...nothing.
Thanks anyway dude