Battery Drains Very Quickly. - Galaxy Tab 2 Q&A, Help & Troubleshooting

So, I have a Samsung Galaxy Tab 2 7.0 P3110, but for the past month I have been experiencing battery drains very quickly. For instance, I would charge the tablet to 100%, but when i take out the charger I would experience a large loss of batter such as in 2 minutes I would lose about 20 % of the battery. So I wanted to replace my battery so I went to the Samsung Store in Westfield, where I went to the 'Smart Team' who I would thought replace the battery for me, but however they decided that they thought it was a firmware problem which I knew it wasn't, they took it to recovery mode where i had a custom recovery so they used that as an excuse, how that is the reason i'm experiencing this. I really wanted to go hell on that guy, since I had been rooted for over a year I was still on an official firmware. So I want to unroot this tablet and just go back to how it genuinely came out, i can't find a guide or somehow if someone can, just post it here please.

Harnessful said:
So, I have a Samsung Galaxy Tab 2 7.0 P3110, but for the past month I have been experiencing battery drains very quickly. For instance, I would charge the tablet to 100%, but when i take out the charger I would experience a large loss of batter such as in 2 minutes I would lose about 20 % of the battery. So I wanted to replace my battery so I went to the Samsung Store in Westfield, where I went to the 'Smart Team' who I would thought replace the battery for me, but however they decided that they thought it was a firmware problem which I knew it wasn't, they took it to recovery mode where i had a custom recovery so they used that as an excuse, how that is the reason i'm experiencing this. I really wanted to go hell on that guy, since I had been rooted for over a year I was still on an official firmware. So I want to unroot this tablet and just go back to how it genuinely came out, i can't find a guide or somehow if someone can, just post it here please.
Click to expand...
Click to collapse
You can download the stock firmware from a website such as Samsung-updates.com and flash it using Odin to unroot. Just make sure after you flash the firmware you wipe data factory reset in the stock recovery so you don't get a boot loop.

Skazzy3 said:
You can download the stock firmware from a website such as Samsung-updates.com and flash it using Odin to unroot. Just make sure after you flash the firmware you wipe data factory reset in the stock recovery so you don't get a boot loop.
Click to expand...
Click to collapse
And if the flash counter had been tripped then you'll want to use triangle away to reset it.
jrc2
Sent from my T-Mobile S2 using Tapatalk.

Related

[Q] Rooted Verizon Galaxy S4 Problem

Hi.
I made an account just to post this because I honestly don't know where else to go. I'm new at rooting so please explain everything in simple terms.
I rooted my Verizon Galaxy S4 a few days ago and everything was great. I did a few soft mods with Xposed and Wanam and everything was still great. I thought I would wait until the weekend to do some custom ROM flashing and whatnot since I knew it was a time consuming process.... MAN was it a time consuming process. Mainly because I messed up my whole phone.
I installed Safestrap v3.71 (CWM Recovery wasn't compatible with my phone or something...?) and flashed Hyperdrive RLS13 to my MK2 build Verizon Galaxy S4 on ROM Slot 1. It worked great but I saw that all my free space in my internal memory was taken up because of my Stock ROM being too large. So I proceed to wipe data from the Stock ROM slot after backing it up and putting the backup on my computer. I factory reset the Stock ROM and hit reboot. I think the error occurred because I forgot to reselect the ROM Slot 1. Or maybe factory resetting like that isn't supposed to happen... I don't know.
But now my phone won't boot up all the way. It's stuck on the Samsung Galaxy S4 screen. I tried booting into recovery but it just takes me to the stock recovery. Apparently Safestrap is unable to be booted into directly or something... so i tried to factory reset from there and it did.
Now my phone won't even go into recovery mode. If I try it will say "Recovery Booting" but the screen will go black and reboot again and get stuck on the Samsung Galaxy S4 screen.
I HAVE LOOKED EVERYWHERE ON THE INTERNET and nothing directly applies to me or is simple enough for me to understand... I am currently downloading the NO-WIPE method stock ROM or something for what I think applies to me from http://forum.xda-developers.com/showthread.php?t=2578209 so I can put that into Odin which I downloaded (but don't really know how to use) and it says it will take 3 hours to download. GREAT. More waiting. I would like something quicker if possible.
SO MY QUESTION IS:
WHAT THE HELL DO I DO???
Specs of my phone again:
Verizon Galaxy S4 SCH-1545
Android 4.3
Build MK2
Kernel Mk2
(I'm not even sure what all that means but there it is)
ALL HELP WILL BE GREATLY APPRECIATED BECAUSE I DON"T KNOW WHAT TO DO!
Thank you. So. Very. Much.
Ditto
the immunity said:
Hi.
I made an account just to post this because I honestly don't know where else to go. I'm new at rooting so please explain everything in simple terms.
I rooted my Verizon Galaxy S4 a few days ago and everything was great. I did a few soft mods with Xposed and Wanam and everything was still great. I thought I would wait until the weekend to do some custom ROM flashing and whatnot since I knew it was a time consuming process.... MAN was it a time consuming process. Mainly because I messed up my whole phone.
I installed Safestrap v3.71 (CWM Recovery wasn't compatible with my phone or something...?) and flashed Hyperdrive RLS13 to my MK2 build Verizon Galaxy S4 on ROM Slot 1. It worked great but I saw that all my free space in my internal memory was taken up because of my Stock ROM being too large. So I proceed to wipe data from the Stock ROM slot after backing it up and putting the backup on my computer. I factory reset the Stock ROM and hit reboot. I think the error occurred because I forgot to reselect the ROM Slot 1. Or maybe factory resetting like that isn't supposed to happen... I don't know.
But now my phone won't boot up all the way. It's stuck on the Samsung Galaxy S4 screen. I tried booting into recovery but it just takes me to the stock recovery. Apparently Safestrap is unable to be booted into directly or something... so i tried to factory reset from there and it did.
Now my phone won't even go into recovery mode. If I try it will say "Recovery Booting" but the screen will go black and reboot again and get stuck on the Samsung Galaxy S4 screen.
I HAVE LOOKED EVERYWHERE ON THE INTERNET and nothing directly applies to me or is simple enough for me to understand... I am currently downloading the NO-WIPE method stock ROM or something for what I think applies to me from http://forum.xda-developers.com/showthread.php?t=2578209 so I can put that into Odin which I downloaded (but don't really know how to use) and it says it will take 3 hours to download. GREAT. More waiting. I would like something quicker if possible.
SO MY QUESTION IS:
WHAT THE HELL DO I DO???
Specs of my phone again:
Verizon Galaxy S4 SCH-1545
Android 4.3
Build MK2
Kernel Mk2
(I'm not even sure what all that means but there it is)
ALL HELP WILL BE GREATLY APPRECIATED BECAUSE I DON"T KNOW WHAT TO DO!
Thank you. So. Very. Much.
Click to expand...
Click to collapse
REPLY:brother I do feel ya..I have S4 SCH-1545...Was messing around with root..Didn't know I had it 100% cause of the whole kingo super user app...Any who I ended up soft brick in in Bootloop mode..Red Verizon Screen wouldn't get past it..So I found similar firmware NO Thanks to SamMobile..Verizon 5.0 lolipop..1545pp...Not sure what the pp after 1545 stood for either...so I lemme explain how I got in to Bootloop mode..I downloaded kingroot and it literally broke my fone..Maybe it was to much to handle...kingroot and kingroot plus superuser app..and twrp as well...So I flashed some firmware I found online with Odin and it worked...Took a good couple if minutes but it worked..

[Q] HELP! Weak signal issues and a hot mess.

Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
It all started I guess when I had my phone on CM 10.2 (stable) when the signal would NEVER go past 3x. I thought that was just some error on the phone. The way I flashed the CM 10.2 was some bullcrap because I wasn't getting a certain instruction right where SuperSU/User was playing some Whack-A-Mole game where it would pop in and pop out. Because of all this bullcrap I didn't even think to use EZ Unlock to unlock the bootloader, although I think I didn't see it in the Play Store at the time and some of the Youtube videos I was watching didn't mention it. Eventually all was well though, and although 3x was slow looking back, the ROM was really stable with some minor crashing.
Earlier this past week though, I was tired and clicked away on an update to CM 10.2.1 and then another Cyanogenmod update pops up to the CM 11 snapshot. Just trying to get notifications to go away and I dirty flashed it to CM 11 by the Cyanogenmod updater and got an "Update 7" error when installing it, so I just went back into my downloads folder and re-flashed it to 10.2.1. Being in CM 10.2.1, I wasn't getting anything in terms of reception and later found out the problem was that the SIM wasn't checked under mobile networks in the settings tab, but this had resulted in my phone not getting mobile data past 1x.
Now fast forward to today and I update my CWM because of the "Update 7" error and re-flashed it to CM 11, only to find that there were times that the bars would go up to 5 and the LTE would flair up, but then it would crash down; I messed with both the Global LTE (there was a little more successes in this one in terms of the number of time LTE and better bars popped up, but didn't use it because I was scared to see if I was gonna get charged with Data Roaming) and Regular CDMA LTE (kept having 1x and bars would go up and down...), which is where it's at right now.
Okay, so then I re-flashed it to Verizon's 4.3 (finally Verizon is giving us i535 some love! right?) in an attempt to clean flash it but I had put in the VRALEC bootchain in first and softbricked me out of the recovery partition where it gave me that "Take back to Verizon store" yellow triangle warning and it was stuck for a long time at the Verizon logo until I odin'd a stock recovery 6mb tar and w00t, my phone is back, BUT I still have the same figity signals as the CM 11 and all. At this point though, my triangle count is at 4. Also in this state, my Google Play was acting hell-ish (I also got this in CM 11 too, but didn't care too much for it before); I kept getting this "Error retrieving... [RPC:S-3]" when trying to install apps and I did force stop and clear the info, but it wouldn't work. I've also gotten the RPC:S-7 too. Right now, after my mobile and signal bars being finicky as hell, it's sort of stabilized for 4 minutes (longest it's been ) to 4/5 bars with 4G LTE, but I don't know how long this will stay for.
So being very descriptive and maybe loosing some of you, here's the questions for the tl;dr for the questions.
- How can I get this reception to stabilize? It's never been this bad when my phone was stock around here. (now done with this long blob, the 1x has appeared again!)
- Any other ways on getting that RPC:S-3/S-7 in Google Play Store to go away?
- I'm planning on going to CM 11, once it gets a stable release. Kitkats are too irresistible, pun intended... Can someone please set the stone in how I should go about rooting and unlocking the bootloader? Some of the guides I used months ago were a little outdated, and I'm concerned that the old practices are over with.
Rezey said:
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
that the old practices are over with.
Click to expand...
Click to collapse
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
buhohitr said:
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
Click to expand...
Click to collapse
Hey, thanks for the reply!
A little update; last night I used SUA.exe with Kies drivers which re-flashed it with the factory Verizon's 4.3 and factory reset it, but now my phone will not get any sort of internet bands up and it's stuck on voice roaming which lead me to put my phone on airplane mode so that hidden charges wouldn't sneak up on me. I've even set my Mobile Network options to CDMA-LTE-EVO, but it will not get off of it.
I was just about to go onto one of the other threads and just re-root my phone, until you had told me about the locked bootloader... I'll look more into the safestrap, but this is irritating.
As with the PIT file, do I have to Odin all the VRALEC and other (I've seen a couple of odin to stock and I know rooting requires this) bootchains, to PIT file, and then 4.3? I'm not sure how that step goes... And if it did mess up my efs, what's my next step? I mean I think the i535 might be under warranty, but I'm at 4 triangle counts and I can't get those away unless if I get root permission, but I feel like having a locked bootloader might restrict me from rooting my phone, but I can be just worrying too much...
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Rezey said:
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Click to expand...
Click to collapse
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
buhohitr said:
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
Click to expand...
Click to collapse
Actually I used the Verizon utility tool from that very thread to clean root back to 4.3 and had Google Play connection error, Voice-roaming only, and no mobile data whatsoever.
I also just did saferoot on my phone and triangle'd away all my counters but yet still nothing. Did I fry my sim card? And with voice roaming always on, won't this put charges on my bill?

Samsung GS7 Extreme Battery Drain After Root!

Hello,
So I tried rooting the GS7 recently. It was successful but I kept getting an 'Unauthorized Actions' error. I tried everything I could to get the warning to go away but couldn't resolve it. I've unrooted and have reverted back to stock and did a factory reset. However, now I'm seeing that my battery is draining faster than it charges. I booted into recovery mode and after the "downloading" screen I see an android lying down with a yellow exclamation point over his head. It goes to recovery and at the bottom it says supported APIs: 3 which I've never noticed before. I'm in way over my head and really regret trying to root. I just wanted to access my hosts file so I could block some websites. I'm not sure what to do now and am seeking some advice. I just want my old phone back. =' (
Thanks!
This happened to me after rooting, i experienced battery drain when my galaxy s7 G930F was idle, about 2%-5% per hour drain, there doesn't seem to be a wake lock as I've checked all my apps. what i would recommend doing is make a backup, check your device baseband version and remember it, then through recovery format data of your entire phone, then use odin to install a stock rom from sammobile (it should be the one that matches your baseband version).
if you have trouble just search in google for "install stock rom s7 odin" check if there is a tutorial for your model of galaxy s7!

Boot loop. Is it bricked?

Hi.
I have an SGS7 G930F
I updated from Superman-Rom 1.15.0 to Superman-Rom v1.15.5 six days ago.
Phone worked great.
Two days ago the phone lost signal to the phone network. This was in an area with bad signal, so it's normal to loose signal.
After a short time, I desided to reboot the phone to see if I got signal faster.
But the phone went in boot loop.
I was abel to get in both "download mode" and "recovery mode". Since I had both Superman-Rom v1.15.0 and v1.15.5 (on sd-card) I tried to reflash the rom. Tried both of them. But installation got stuck at 25%.
After that I downloaded stock Samsung rom, and installed with Odin. But still boot-loop.
So what to do?
I guess it's no point of RMA because of "custom binary count"?
jfm91 said:
Hi.
I have an SGS7 G930F
I updated from Superman-Rom 1.15.0 to Superman-Rom v1.15.5 six days ago.
Phone worked great.
Two days ago the phone lost signal to the phone network. This was in an area with bad signal, so it's normal to loose signal.
After a short time, I desided to reboot the phone to see if I got signal faster.
But the phone went in boot loop.
I was abel to get in both "download mode" and "recovery mode". Since I had both Superman-Rom v1.15.0 and v1.15.5 (on sd-card) I tried to reflash the rom. Tried both of them. But installation got stuck at 25%.
After that I downloaded stock Samsung rom, and installed with Odin. But still boot-loop.
So what to do?
I guess it's no point of RMA because of "custom binary count"?
Click to expand...
Click to collapse
Factory reset from recovery?
Yes. full wipe on everything
jfm91 said:
Yes. full wipe on everything
Click to expand...
Click to collapse
How long did you wait for it to boot after flashing stock with ODIN?
It can take quite a long time for first boot
With ODIN, flash BL, CP, AP and CSC (Not HOME_CSC)
CSC Should reset the phone after the flash too
*Detection* said:
How long did you wait for it to boot after flashing stock with ODIN?
It can take quite a long time for first boot
With ODIN, flash BL, CP, AP and CSC (Not HOME_CSC)
CSC Should reset the phone after the flash too
Click to expand...
Click to collapse
After you replied I tried to flash again.
Flashing took 3 mins.
After that the phone went straight to boot loop. I have now waited 15 minutes, and still no boot. The screen have turned black, and blue led indicator is on
Sounds like something else is wrong if it still loops after flashing CSC, that contains the PIT file, which repartitions the phone, and also resets it
Got a MicroSD card in? Try removing that in case it's faulty, otherwise hopefully someone else has some ideas
Could try flashing the Nougat Beta as a test
I have removed SD-card. (Have it in my backup phone now.)
Could it be hardware issue?
I'm considering to contact my insurance company, for a new phone
Could be, but sounds more like a firmware issue
Tried Smart Switch firmware recovery?
*Detection* said:
Tried Smart Switch firmware recovery?
Click to expand...
Click to collapse
Doesn't help either
Any suggestions?
Do I need to make up a "home-accident" story for my insurance company (contents insurance?)?
I had a similar issue with my Samsung s7.
Randomly crashed, went into reboot loops, got very hot.
I tried flashing via Odin and Smart Switch but at the end it was a hardware fault which Samsung repaired at their repair center.
Problem is that I have "custom binary count"
jfm91 said:
Any suggestions?
Do I need to make up a "home-accident" story for my insurance company (contents insurance?)?
Click to expand...
Click to collapse
Mabey you should try flashing an older firmware like PE1 and then updating later!
http://www.theandroidsoul.com/download-galaxy-s7-firmware
using Odin but first try only flashing the AP, CP, and CSC don't do the BL. If that fails then try doing a flash with the BL included. Hopefully this works!
If worst comes to worst, if your knox isn't tripped, then send in or warranty.
Did you put a custom recovery on it?
Insurrance company have given me money to buy a new S7.
But now I am considering to use one of my old phones (Sony Z3C, Galaxy S4 or Galaxy S5) until the release of Galasy S8
jfm91 said:
Insurrance company have given me money to buy a new S7.
But now I am considering to use one of my old phones (Sony Z3C, Galaxy S4 or Galaxy S5) until the release of Galasy S8
Click to expand...
Click to collapse
better question. Can you last on your old phone til Galaxy 8 comes out for sale?
Alikhan821 said:
I had a similar issue with my Samsung s7.
Randomly crashed, went into reboot loops, got very hot.
I tried flashing via Odin and Smart Switch but at the end it was a hardware fault which Samsung repaired at their repair center.
Click to expand...
Click to collapse
Did you manage too solve this issue ? I am facing the same problem.
Cheers
Hi,
Samsung repaired the phone for me so the issue was solved.
Do you remember what the issue was about and how much it costed you ?
Thanks.
Since the phone was in warranty and I never rooted it, it was repaired for free. They arranged to come collect it from my house and I had it back within 3 days. They replaced the motherboard in my case.

Really need help with possible kernel, last time tried TWRP caused bootloop :(

Hey Guys,
Long story short, I had my Sprint Note 5 rooted a while ago! due to some apps screwing me over and not allowing to use them due to being rooted I unrooted (via supersu)
Realized ever since I rooted my battery was totally crap and figured after I unroot it would help (it didn't) read about how it trips the Knox and it affects the deep sleep of the phone (thus **** battery life)
I read on here to just load a kernel in order to fix the deep sleep issue. I've rooted and loaded kernels before on other phones (no issues everrrrr).
When I looked up the TWRP version to use and flash via Odin it said successful. Phone restarted and it never came back up again. I downloaded literally all of the TWRP versions they had on their site, flashed all of them via odin and none of them would get me out of the boot loop. I got completely screwed and had to load a stock firmware from that sam site to get my phone working again. Everything was completely lost on my phone. pics that were never backed up
Due to that, I have been totally hesitant to try this again as that was the only way to fix my phone. I am willing to try again but really want to go into this prepared and have it be a smooth process ( I already backed up ALL of my files on my computer) I don't really care for TWRP or Kernels but I just want to fix the stupid deep sleep issue. I read somewhere on here that people having bootloops from twrp on note 5s was due to not being rooted first? I've also seen (as I did this almost 8 months ago) there are new TWRP versions since then, but afraid to even do those.
Is there a solution I can do to just fix the damn deep sleep issue? phone literally last 2-3 hours idle. Willing to donate via paypal to someone to help walk through it. This is a sprint variant note 5
thanks in advance

Categories

Resources