Develop Bugs

[Q] Updated to 4.3, now GApps continuously force closes

I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?

Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.

Random Restart Issues

I have been having issues with my Note3 ever since the kit kat update back in April. It worked flawlessly on Jelly Bean and I had no issues for over 3 months. I updated to kit kat via Kies with everything completely stock. Since then I get completely random reboots, it could happen when launching an app or even unlocking the screen, and it happens 2 or 3 times a day. So far I have tried 2 factory resets, clearing dalvik cache, and replacing the battery with an Anker replacement. I have tried turning off auto-updating of apps, and turning off wifi scanning. I have also tried running the phone with no apps installed. So far nothing has worked.
I have read several posts with people blaming the stock kernal for these reboots, but there is no definitive solution to this problem. I am looking for any and all help the community has to offer.
Some additional info:
Running latest stock rom- rooted via effortless method
Stock Recovery
Knox is still 0x0
No sd card in phone

Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs

icenight89 said:
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
Click to expand...
Click to collapse
Thanks, I'll give this a try. Last night I uninstalled a bunch of bloat ware with titanium backup to make sure it's still not an app issue. If it reboots again I'll reflash the firmware. Since I'll. Be flashing stock it shouldn't trip knox right?

No, latest firmware complete stock will not trip Knox, as long as you're either doing a parallel upgrade NF9 > NF9 or NB4 > NF9. A downgrade will either fail or trip.

For anyone reading this, i tried to reflash the stock nf9 kernal to see if that was the issue, but i got a restart about 4 hours later. I am going to reflash the firmware via odin and report back.

I am having this issue for a long time. i have done everything, and finally i gave up, as i think it is a hardware issue. what make me confuse is the problem start since the day i upgrade to kit-kat. with every firmware come out i have a new problem. the latest "NF9" my phone just hang and black screen untill i press the power button for 30 second, then will restart. what make crazy is that it shuts off at night, and when i woke up i miss the alarm.

I'm sad to report that the reflash didn't work. I reflashed the NF9 firmware using odin about 4 days ago and it was fine for awhile, but I got 2 reboots today. I'm not sure what is causing this, but I am still open to suggestions. I don't think its hardware related since it didn't do this before kitkat. I still have my samsung warranty until february I believe, so if worst comes to worst then ill have to send it in, but i'm not sure what they will do about it.

The only thing I havent tried is replacing the sim card. Could a sim card cause a reboot issue like this?

i have already done it, even the SD card, still same problem.

Is there some kind of log feature in android that logs crash events or errors somewhere so i can maybe figure out what the problem is?

by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.

makki666 said:
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
Click to expand...
Click to collapse
I do not have busybox installed, and SuperSU is up to date. Also, the restarts happen with or without root ie without SuperSU. I still dont think its an app problem.
Just an update for anyone reading this. I have installed SetCPU to manage cpu clock speeds. I have had it installed for about a week and have not had an update with my custom profiles. It seems the restarts occur when cpu speed is at about ~675MHz. Not sure if its hardware or software yet. Any help is appreciated!

Update. I sent my phone in to samsung for repair. It looks like they just reflashed the firmware. After having it up and running again for 15 minutes the phone rebooted again. I contacted samsung and they recommended sending it in again. I'm not sure if it's worth it to send in again or if i should break my warranty and flash a custom rom. Any suggestions are welcome!

I get restarts because the modem crashes... its a known issue apparently

gtharea said:
I get restarts because the modem crashes... its a known issue apparently
Click to expand...
Click to collapse
I cant believe its taken over a year for this issue to get fixed. Im almost positive its a software issue since it never happened on jelly bean. It's strange that not a lot of people have this problem though. A lot of people must have already flashed custom roms I may send it in again since I still have knox 0x0 and see if they do anything else besides reflash the firmware this time. If they only do a reflash again i will just flash a new rom and hopefully everything will be fixed

Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:

_bhaves_ said:
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
Click to expand...
Click to collapse
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.

meoshe said:
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
Click to expand...
Click to collapse
I would get reboots even without an SD card put in the phone, so I don't think that would have helped me. I havent had a reboot since I've had the device back

[Q] Help! What have I done to my Pro 10.1

Here's the story. I purchased a factory refurb'd Tab Pro 10.1 (SM-T520NZKAXAR) on Woot a few weeks back. I live in Canada, but it is a USA tablet, if that matters. It came with a 90-day Samsung warranty. As soon as I got it, I started looking at custom ROMs. I have experience with custom ROMs on my HTC One m8 (and old m7), but not with any Samsung devices. I wish I had kept it stock for a few weeks first to check it out, but here we are.
I created a nandroid backup of the stock firmware, however I quickly deleted it during a wipe when flashing my first custom ROM, which was GraveD's v3.0. It seemed to go OK, but then it would start to freeze up and reboot on it's own. This seemed to happen mostly under load, and especially when trying to install apps from the Play store. I tried going back to the stock kernel, thinking that could be the problem. It stopped the crashing, but then wifi wouldn't work. So I could choose between having a tablet that crashes all the time, and has difficulty installing apps, or one without wifi. Both were basically useless.
I tried installing another custom ROM, GigaWatts Pro. Again, flashing seemed to go well, and the ROM also seemed to work very nicely for a couple of days. No random reboots, and wifi worked great. I spent a few days downloading all of my apps and getting things set up the way I like, when yesterday something went wrong. Perhaps the tablet lost its root (is that possible?). All of a sudden, apps are crashing all over the place (Unfortunately, [insert app name] has stopped). Titanium backup hangs at "Asking for root...". Installing apps is also difficult again. The tab doesn't reboot on it's own, but Play Services crashes constantly. Whenever I try to get into developer options, the Settings app crashes. I'm not even 100% sure USB debugging is enabled right now, although I'm still able to flash using ODIN.
I tried doing a factory reset and re-installing GigaWatts. Same problems. Tried making sure the root was OK. Same problems. I've tried using twrp 2.8.0.0 as well as 2.7.1.0 with no luck.
Right now, I've downloaded the stock firmware for Canada T520UEUANI1 4.4.2 (although the tab was bought from a USA site). I assume this also installs it's own Kernel. It shows Kernel version:
3.4.39-2776001
[email protected] #1
Mon Sep 15 17:44:40 KST 2014
I'm experiencing the same problems. Google Play Newsstand crashes every 10 minutes or so. Settings is almost useless. Installing apps is problematic.
Can anybody tell me if there's something I'm missing? Anything left to try? Does it sound like a hardware/ROM/kernel problem? If it's hardware, can I still utilize the Samsung warranty after trying to flash custom ROMs? I'm going to try to download another Cellular South stock ROM, but it seems like the problems are persisting regardless of which ROM i have installed, so I think it's something else (kernel or hardware-related).
Any help is GREATLY appreciated. My new tablet is basically useless, and I've run out of ideas.

Try this latest firmware since you mentioned your tablet is the XAR model the firmware should be cellular south (wifi)
http://www.sammobile.com/firmwares/download/39630/T520UEUANK1_T520XARANK1_XAR.zip/
If that doesn't help then it could just be a bad tablet .
(btw when you flashed a custom rom you probably tripped the hardware knox flag and voided any warranty it had, I guess you could play dumb if they ask and say it came like that since it was refurbished, and hope they still repair/replace it)

I just tried the USA cellular south firmware. Still experiencing the exact same issues. I'm completely out of ideas. Does anyone else have any ideas? Otherwise I'm going to have to try warranty service and hope for the best. Is there anything I can do to restore the Knox flag before I send it in?
Also, in download mode the tab is recognizing the system as custom. Is this normal after flashing a stock image?

So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.

k8108 said:
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
Click to expand...
Click to collapse
I've tried the Cellular South firmware to no avail. I'll be trying to warranty the tablet now. Fingers crossed!

[Q] tab3 7.0 210R constant rebooting/poor wifi

looking for some suggestions as to what I can to to correct these issues. I have a 210R that I screwed up probably flashed something I should not have... to restore I went to sam mobil and downloaded the latest firmware ( T210RUEU0COB1), installed using Oden and restored the Tab. since I have done this (and yes I redownloaded the firmware and reinstalled to make sure it was a good file and installation) the tab now will boot up fine, but will come up with the error messages Process com.androis.systemui has stopped and often com.sec.android.flashbarservice has stopped as well clicking ok will sometimes let me continue, other times will simply reboot. If it lets me continue whatever app I am using will quickly stop as well and the tab reboots. in addition to this the WiFi barely recieves any signal unless I am almost on top of the router. it is currently stock. Any suggestions or help will be greatly appreciated.

Having the same problems minus wifi issues
jdsatyr said:
looking for some suggestions as to what I can to to correct these issues. I have a 210R that I screwed up probably flashed something I should not have... to restore I went to sam mobil and downloaded the latest firmware ( T210RUEU0COB1), installed using Oden and restored the Tab. since I have done this (and yes I redownloaded the firmware and reinstalled to make sure it was a good file and installation) the tab now will boot up fine, but will come up with the error messages Process com.androis.systemui has stopped and often com.sec.android.flashbarservice has stopped as well clicking ok will sometimes let me continue, other times will simply reboot. If it lets me continue whatever app I am using will quickly stop as well and the tab reboots. in addition to this the WiFi barely recieves any signal unless I am almost on top of the router. it is currently stock. Any suggestions or help will be greatly appreciated.
Click to expand...
Click to collapse
Dude my tablet is in the same state I use. The many reboots. All apps/process stopping for no reason. Funny thing is this started happening to me after I received an OTA update for 4.4.2 and flashed it. So basically the official update released by samsung messed up my phone. Somebody please respond with suggestions/solutions.

Sigh.... guess I'll just use it as a paperweight ..

Dead Tab ? Help ! - Free beer

I've searched far and wide, but nothing seems to resolve my issue.
The case:
I have 2 Galaxy Tab S(T800).
One, the oldest, has always run a stock rom + Root
One, I have on LOS 7.1.2.
The oldes one rebooted spontaniously. After searching, i thought it was the battery. On the web people say it often happens with this device. So cracked up de back and checked everything. Thing were looking fine (similar to the working one). Also: in download mode or recovery, it doesn't restarts.
So it has to be software, right? RIGHT ??
I've wiped everything. Factory, Data, Cache. No luck.
Installed the stock rom; no luck. And TWRP then LOS; no luck.
Here is where i loose my mind: Odin gives a pass. The Tab starts perfectly, but upon booting, it quits. On 4.4.2, 5.0.1, 6.0.1. The furthest i've come was the startscreen of LOS, but upon Wifi settings, it reboots again.
Tried to re-partition with the .pit file : no succes either.
HELP wanted. Maybe I can do something with my other, still working tablet.
A free beer for my saviour!

quintinliono said:
I've searched far and wide, but nothing seems to resolve my issue.
The case:
I have 2 Galaxy Tab S(T800).
One, the oldest, has always run a stock rom + Root
One, I have on LOS 7.1.2.
The oldes one rebooted spontaniously. After searching, i thought it was the battery. On the web people say it often happens with this device. So cracked up de back and checked everything. Thing were looking fine (similar to the working one). Also: in download mode or recovery, it doesn't restarts.
So it has to be software, right? RIGHT ??
I've wiped everything. Factory, Data, Cache. No luck.
Installed the stock rom; no luck. And TWRP then LOS; no luck.
Here is where i loose my mind: Odin gives a pass. The Tab starts perfectly, but upon booting, it quits. On 4.4.2, 5.0.1, 6.0.1. The furthest i've come was the startscreen of LOS, but upon Wifi settings, it reboots again.
Tried to re-partition with the .pit file : no succes either.
HELP wanted. Maybe I can do something with my other, still working tablet.
A free beer for my saviour!
Click to expand...
Click to collapse
It looks like a failure in the EMMC .. they were defective in these plates (Toshiba brand) mine has that problem and every 3 days they start restarting and I have to reinstall ..