Develop Bugs

***Emergency Thread*** Here To Help!

I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!

In case of emergency!

Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?

Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2

...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.

Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app

lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.

Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.

I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.

heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download

Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.

Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!

frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2

Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!

frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2

Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing

Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!

http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?

Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)

ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2

Weird isuues

Just got my used t-mobile note 2 on monday.I am having issues with the phone where the screen will start scrolling on it's own and keep trying to launch media hub or the weather widget and then the screen eventually freezes and won't respond.I have downloaded the emmc program and my phone doesn't have the defective chips.I have done 2 factory resets and the problem still persists and happens as it is being reset.Any one know what could be going on?If i leave the sim out the phone works fine though.

Best guess water damage. Check the tabs. Also get a new sim.

travispittman said:
Best guess water damage. Check the tabs. Also get a new sim.
Click to expand...
Click to collapse
Did another factory reset but before that deleted some apps i had downloaded and made sure to disable samsung media hub,gps and the weaqther widget and so far the phone has been fine.

Is it factory rom and kernel or has it been messed with? I originally bought an s4. Connected it to a shady charger and changed the polarity of the board. It was hard to get to take a charge and wouldn't hold a charge for very long. Went to have it looked at by a tech. Before he knew what I was there for he offered to trade me for a note 2. He looked my phone over and we swapped. Usually when people get rid of a phone it is not because they upgraded but because something is wrong. I dislike buying used for that reason. I have had ppl try and pass off water damaged stuff and all kinds of randomness. I always boot reboot and reboot and used phone before buying, Keep them there as long as possible to see if something is wrong. Ask a lot of questions. Usually when you purchase a used phone especially an expensive one such as the note2 you want to get what you are paying for and not duped into paying a lot of money for some ones broken mess.

It's factory original rom and kernel.

same here

dukenukems said:
Just got my used t-mobile note 2 on monday.I am having issues with the phone where the screen will start scrolling on it's own and keep trying to launch media hub or the weather widget and then the screen eventually freezes and won't respond.I have downloaded the emmc program and my phone doesn't have the defective chips.I have done 2 factory resets and the problem still persists and happens as it is being reset.Any one know what could be going on?If i leave the sim out the phone works fine though.
Click to expand...
Click to collapse
This may seem silly, but have you tried to clean the screen with a microfiber cloth? This same problem happened to me (except the weather widget part), and after a spray n' clean, it all got fixed.

Well huys i was able to root my phone pretty easily but am still on the stock rom it came with.Will using other roms and stuff be a bit easy for me to install or will it be tough since this is my first rooting adventure.

dukenukems said:
Well huys i was able to root my phone pretty easily but am still on the stock rom it came with.Will using other roms and stuff be a bit easy for me to install or will it be tough since this is my first rooting adventure.
Click to expand...
Click to collapse
It's simple as long as you have the ability to read through threads prior to flashing. 98% of problems with custom software installs is due to lack of patience by the flasher. Read alot, flash a little is a safe way to get started.
Hastily spouted for your befuddlement

I've rooted it and have tryed 2 different roms already.Just sad that my note 2 still has the screen lock up allthough using spen remains fine.

Well guys my hone had started to lovk up even at the boot screen and didn't want to respond to the spen either so i went into recovery mode and dids factory reset with cwmr but after i rebooted my phone it was stuck in infinite boot loop.Just reflashed phone with it's stock rom image from this site using odin but my phone will only boot to the t-mobile 4glte screen and won't go any further.I have gone back into recovery mode and factory reset but still the same problem.Is my phone bricked?

dukenukems said:
Well guys my hone had started to lovk up even at the boot screen and didn't want to respond to the spen either so i went into recovery mode and dids factory reset with cwmr but after i rebooted my phone it was stuck in infinite boot loop.Just reflashed phone with it's stock rom image from this site using odin but my phone will only boot to the t-mobile 4glte screen and won't go any further.I have gone back into recovery mode and factory reset but still the same problem.Is my phone bricked?
Click to expand...
Click to collapse
Not sure if I am allowed to post links to other sites, but check out: galaxynote2root.com. max has a tutorial for almost everything! Also did you do a full wipe? Whenever installing a new ROM if you get stuck in a boot loop go back to recovery and do a wipe again, also wipe cache, and dalvik as well. Hope this helps!

Flashed thw original rom image with odin but the original will jsut hang at the tmobile splash screen and never fully boot.I was able to flash the phone with twrp with odin and was able to use twrp from my phone to reinstall the jedix20 rom which does install and been working since.No matter what i do with the original factory image it will always refuse to boot past the tmobiole splash screen.

[Q] Sprint Phone boots up only when plugged in. If unplugged it goes into a bootloop.

A few days ago, I flashed a 4.4.2 rom and kernel. I noticed that it was randomly rebooting so I went ahead and flashed another rom, this time without a new kernel. Everytime I flashed I did a wipe of the device. When I did this the Galaxy Note 2 splash screen would come up then the rom boot logo. But then it would go back to the splash screen and the boot loop would continue. I ultimately discovered that the phone would get past the boot loop sequence if either plugged in via USB or AC. I set up my phone thinking it was cool but once I unplug it, and start using the phone, it reboots itself and starts up the boot loop cycle again. I've gotten fed up to the point that I unrooted the phone back to a stock 4.3 rom thinking that might solve the problem but even with the stock rom the boot issue persisted. I've since then used Odin to put new recoveries in hopes that this could be the issue but still the same problem persists. I've had to start carrying around my laptop with me to and from work just to have the phone plugged in because otherwise it will eventually shutoff and start the bootloop. I'm usually pretty good at solving these issues but right now I'm without any answers. I haven't checked to see if possibly it could be a battery issue but I haven't had an opportunity to find someone with a Note 2 to try out this theory...has anyone had somewhat remotely close to a similar issue and if you have, did you solve it? Someone help...lol otherwise my Note 2 may have seen it's final days although I'm not in the market of finding another phone right now.

bkjay78 said:
A few days ago, I flashed a 4.4.2 rom and kernel. I noticed that it was randomly rebooting so I went ahead and flashed another rom, this time without a new kernel. Everytime I flashed I did a wipe of the device. When I did this the Galaxy Note 2 splash screen would come up then the rom boot logo. But then it would go back to the splash screen and the boot loop would continue. I ultimately discovered that the phone would get past the boot loop sequence if either plugged in via USB or AC. I set up my phone thinking it was cool but once I unplug it, and start using the phone, it reboots itself and starts up the boot loop cycle again. I've gotten fed up to the point that I unrooted the phone back to a stock 4.3 rom thinking that might solve the problem but even with the stock rom the boot issue persisted. I've since then used Odin to put new recoveries in hopes that this could be the issue but still the same problem persists. I've had to start carrying around my laptop with me to and from work just to have the phone plugged in because otherwise it will eventually shutoff and start the bootloop. I'm usually pretty good at solving these issues but right now I'm without any answers. I haven't checked to see if possibly it could be a battery issue but I haven't had an opportunity to find someone with a Note 2 to try out this theory...has anyone had somewhat remotely close to a similar issue and if you have, did you solve it? Someone help...lol otherwise my Note 2 may have seen it's final days although I'm not in the market of finding another phone right now.
Click to expand...
Click to collapse
I would suggest that you try another battery. Kinda sounds like an issue with the device not getting proper power supply. If I were you I would try finding a friend or coworker who has the same device and try using theirs. If it boots and runs then a replacement battery is all you need. I have had this issue with a previous phone (HTC 3d) but not this device.

jlmancuso said:
I would suggest that you try another battery. Kinda sounds like an issue with the device not getting proper power supply. If I were you I would try finding a friend or coworker who has the same device and try using theirs. If it boots and runs then a replacement battery is all you need. I have had this issue with a previous phone (HTC 3d) but not this device.
Click to expand...
Click to collapse
Thank you for the reply..I will check to see whom may have a Note 2 at work. The ones who did have other phones now I believe. I know of one co-worker who has a Note 3 but not sure if that would be something that I could try..I'll report back tomorrow with my findings...

Yeah I doubt the N3 has the same battery but hopefully you can find someone.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Odd semi brick

So I left my phone on the charger in the car because it was dying, came outside and it was stuck on the Galaxy Note II screen with the green light on. I unplugged the cord, the phone refused to come on so I did a battery pull. Upon powering it back on, I get this screen that looks like Poltergeist and phone does nothing. When in Poltergeist, I can't get the computer to see my phone, so that I can back it up before formatting. Volume up, menu, power doesn't get me into recovery mode. I can't get into safe mode either. ican however boot volume down, menu, power it into the mode where I can flash it, Odin will see it, but going straight to flashing means I lose everything.
Does anyone have an idea beforehand? I know I'm asking a lot, but these forums have gotten way over my head over the years. This is an isolated incident, so if you could even attach the file directly that I can attempt to flash vids Odin to fix my booting issue vs saying goto X thread because every thread seems to have it's own multiple files. I just wanna recover it so it'll come on, back up it and then I'll research on my own how to flash it completely. It's 6am my time and I've gotta be up by 1130am for work, so please reply for dummies as much as possible
Thank you ahead of time.
PS - phone is stock on 4.1.2 rooted using CF Auto Root and that's it.

Morning bump...no quick advice?

60 readings, no one comment? "Hey, flash XXXXX and see if the display drivers come back", etc? It'll boot into flash mode, looks normal and the compputer sees it. Safe mode or normal boot give me Poltergeist and the computer wont see it so that I can try to backup everything before flashing....that's a lot of boobies pics (just trying to get some sympathy here) to have deleted

79 views...for the love of god, someone throw me a bone here. I get it, these are old phones now, these forums are full of know-it-alls who can't be bothered (devs) and "search" nazis (me being one of them) as I should just figure it out on my own...but I'm not. I've got versions of ODIN, I've got CWM Recovery files, stock MC2 and NE2 ROM's, I even found myself a PIT file. NONE OF THEM ARE WORKING. No matter which ODIN I use, they all stick at PIT regardless of whether I have re-partition checked or not. I've tried flashing PIT, CWM recovery, stock recovery, CF Auto Root and/or stock 4.1.2 - 4.4 ROM's in just about any combination of one or two together using each version of ODIN. No bueno.
I've got a very nice and thick 24/28awg cord I'm using, I can boot into dowloader mode but can not go into safe, recovery or boot normally. I've watched brick recovery videos on YouTube, I've downloaded files from here on the forums and www.galaxynote2root.com using various downloading I have included a picture of.
Someone, somethg...

10 attempts later...
Holy crap you forget how nice the Note is when you're back on a Epic for two days while working 12hr days and going through 6 batteries each day...

m5james said:
Holy crap you forget how nice the Note is when you're back on a Epic for two days while working 12hr days and going through 6 batteries each day...
Click to expand...
Click to collapse
Did you ever get this figured out? I'm in the same boat with the L900 Sprint Note 2...

Solved it by getting a working logic board from eBay

I broke down and bought a Note 3 off Craigslist for $300 but I'd still like to fix the Note 2 to make it into my backup instead of pulling the Epic outta the box again.

Think ive killed it :/ Tab S2 T813

ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas

You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today

Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!

Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........

thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/

Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....

stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony

one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??

if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again

In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/

RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!

will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.

Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.

swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.