Database Info

Galaxy Tab constantly prompting for system update

Hey guys,
I was hoping someone here could throw me a bone on a problem I am having with a Galaxy Tab 2 I recently got for my wife. For some reason it keeps telling her there is a software update. She has tried to install it multiple times and it appears to go through successfully but the prompt to update comes back again a few hours later. If we click "Later" it gives a a maximum time of 3 hours before it reminds us to update again. i saw someone else had asked about this in another part of the forum and they were directed here but I never found an answer.
So... The numbers:
Model: GT-P3113
Android Ver. 4.0.4
Kernel version: [email protected] #1 SMP PREEMPT TUE JUL 17 23:47:56 KST2012
Build Number: IMM76D.P311UEBLG5
I've gone in through the start menu and cleared the cache, next step I am considering is starting from scratch with a wipe to factory fresh. Before i did that though I thought I would check here.
Anyone have any advice?
**EDIT**
Just for clarification, this appears to be a system update. Not an app or anything like that. If I go intot he preferences and check for a software update it immediately prompts for it.

Rooted? If so, I was told to try to browse system/app folder for the Fota.apk. delete that and reboot. I've basically got the same problem and posed the same question HERE.

Its simple root your device you will get no ota notofications as when device is rooted ota is disabled on it....
And if it still shows up Then freeze software update,fota app and you are done...
Alternatively you can try resetting your tab or flashing a fresh stock rom or any other on your device..,,

Thanks for the replies guys. :highfive:
My wife has no need for a rooted device and I'd rather leave her in the somewhat walled garden on it. Not that she cant handle it but I'd rather not tempt fate with anything. I am after all her tech support. :laugh:
So this morning I decided to run it one last time before I did a factory wipe on it and oddly it took longer to update then on previous occasions. Now when I go check for system updates it tells me no updates are available.
What is strange is that we tried it several times before and nothing changed. Now we are seeing a new Kernel version and build number:
Model: GT-P3113
Android Ver. 4.0.4
Kernel version: 3.0.8-999349
[email protected] #1
SMP PREEMPT Thu Aug 23 23:43:39 KST 2012
Build Number: IMM76D.P3113UEBLH2
Of course murphy's law decided to wait until AFTER I posted here at XDA to get the update installed properly.
Ah well... At least it is resolved.

Droidlover123 said:
Its simple root your device you will get no ota notofications as when device is rooted ota is disabled on it....
And if it still shows up Then freeze software update,fota app and you are done...
Alternatively you can try resetting your tab or flashing a fresh stock rom or any other on your device..,,
Click to expand...
Click to collapse
Actually, I've been having the same problem. One thing I've noticed is that all of the Roms out there for SGT2 appear to be for the wifi/retail models (GT-P3xxx). The verizon models aren't versioned that way. It is simply the SCH-I705 (no GT-P model designation). Therefore, and correct me if I am mistaken, there are no roms compatible with this hardware.
Also, My device is rooted, I still get OTA notifications. For my device, there is no fota.apk in the system/apps folder, so I either need to find a rom that will work with this phone, unroot/update, or do a factory reset and hope it fixes it. Right now I'm pretty frustrated with this damn thing...

[Q] Stuck in Bootloop after latest OTA Update - what now?

Hey Guys,
this morning I got offered a new OTA update for my Note 10.1.
Since I've never fiddled around with the device (no root, no custom rom and so on) this never was a big deal for me, so I just installed it as usual.
After the update my device is stuck in a bootloop.
What I tried so far:
Connecting to KIES - failed
Recovery Mode -> Cache Wipe - failed
Recovery Mode -> Factory Reset - partly failed
Recovery Mode -> Factory Reset + Cache Wipe - partly failed
What I mean by partly failed is the following:
The device boots as normal (with factory settings) but as soon as I plug it in to KIES to sync my contacts it crashes and goes to bootloop again.
Now to the weird thing:
When I'm in recovery mode I get an error which (I suppose, at least) shouldn't be there:
Apllied the CSC-code : DBT
did not match sized '/system/csc/common/system/wallpaper/lockscreen_default_wallpaper.jpg' (No data available)
This error points to the lockscreen wallpaper?! And the REAL weird thing: While in bootloop sometimes the device gets through to my wallpaper, which then is the "old" wallpaper I had BEFORE the reset. How can that wallpaper still be there after I did a factory reset? There is no SD card in my device.
Is there any way to get back to a working version? I guess it botched up the OTA-update and now has a broken firmware or something like that...
I have no experience in Android modding/flashing whatsoever, but I'm pursuing my masters degree in Information Systems right now, so I'm not a total noob for what it's worth!
P.S.: I don't care about rescuing any data, there was nothing important which is not already backup'd on the tab... I just don't want to have a 500$ paperweight laying around ^^
Thanks in advance for any help!

You can go to sammobile.com and download manually a firmware that fits your device and flash it through odin. That will wipe the tab and flash a fresh stock firmware.
What is your version of the Note 10.1? So I can help you choose the correct firmware if you need.
Also check this video by zedomax and learn all the steps to flash correctly.
https://www.youtube.com/watch?v=NsDOSvBdALg
Sent from my GT-N8013 using XDA Premium 4 mobile app

kalashenicof said:
What is your version of the Note 10.1? So I can help you choose the correct firmware if you need.
Click to expand...
Click to collapse
Thanks for the fast reply and the information.
Not sure what you need as a "version", this is all I could get before it crashes and goes back to the bootloop:
Model #:
GT-N8000 (it's the one with Wi-Fi + 3G)
Android Version:
4.1.2
Baseband Version:
N8000XXCLL1
Kernel Version:
3.0.31 - 1388206
[email protected] #1
SMP PREEMPT Wed Sep 11 13:39:10 KST 2013
Build#:
JZO54K.N8000XXCMI2
Oh, and I'm from Germany, if that information is relevant!
Thanks in advance!

Your right it's model and not version
Check this out http://www.sammobile.com/firmwares/3/?download=19291
Check if the information matches, then download and flash it via odin.
Make sure you login to samfirmware first.
Hope it helps, if you need something else just ask.
Sent from my GT-N8013 using XDA Premium 4 mobile app

Thanks man! I downloaded the firmware and flashed it according to the video.
My tab boots fine now and the error is gone aswell... It crashed one more time though, but runs stable since. I have to keep an eye on it!

Glad it works now =)
Sent from my GT-N8013 using XDA Premium 4 mobile app

[Q] GS4 Randomly Shuts Off ; Apps and Screen Glitch Out

INFO:
Model: SGH-M919
Kernel: 3.4.0-cyanogenmod-g93df44d [email protected] #1 Fri Jan 31 22:47:46 2014
ROM: CM 10.2.1-jfltetmo
Build #: cm_jfltetmo-userdebug 4.3.1 JLS36I 5ce70171d1 test-keys
Recovery: ClockworkMod 6.0.4.7
Basically, ever since I flashed AOKP a while back, my phone has been acting weird. Every once in a while the phone will freeze and black lines will appear, immediately followed by the phone re-booting. It happens completely at random. Afterwards, I flashed various ROM's and Android versions thinking that maybe the ROM was the issue, to no prevail.
Also, apps such as GoSMS, Instagram, PowerAmp, and my Camera, to name a few, bug out and either crash or freeze the phone and again it re-boots. The phone doesn't produce sound (from internal speakers or headphones, when plugged in). The Camera app will not record videos, or lag when record button is pressed, overall most of applications bug out and dont work the way they're suppose to.
My main concern is the random re-booting and what might be causing it, and what can do to fix it?
Thank You for the Help!

SlinerX said:
INFO:
Model: SGH-M919
Kernel: 3.4.0-cyanogenmod-g93df44d [email protected] #1 Fri Jan 31 22:47:46 2014
ROM: CM 10.2.1-jfltetmo
Build #: cm_jfltetmo-userdebug 4.3.1 JLS36I 5ce70171d1 test-keys
Recovery: ClockworkMod 6.0.4.7
Basically, ever since I flashed AOKP a while back, my phone has been acting weird. Every once in a while the phone will freeze and black lines will appear, immediately followed by the phone re-booting. It happens completely at random. Afterwards, I flashed various ROM's and Android versions thinking that maybe the ROM was the issue, to no prevail.
Also, apps such as GoSMS, Instagram, PowerAmp, and my Camera, to name a few, bug out and either crash or freeze the phone and again it re-boots. The phone doesn't produce sound (from internal speakers or headphones, when plugged in). The Camera app will not record videos, or lag when record button is pressed, overall most of applications bug out and dont work the way they're suppose to.
My main concern is the random re-booting and what might be causing it, and what can do to fix it?
Thank You for the Help!
Click to expand...
Click to collapse
Flash stock firmware via Odin to fix rom affected issiues.

LS.xD said:
Flash stock firmware via Odin to fix rom affected issiues.
Click to expand...
Click to collapse
I flashed the latest stock firmware, 4.4.2, via odin 3.09. The problems still stand, everything seems fine at first and then things start crashing and phone reboots. Any other thoughts on what might be causing it?

Don't worry about the rebooting my main concern are those black lines appearing I would flash to stock and claim warranty
Sent from my Nexus 5 using Tapatalk

markdapimp said:
Don't worry about the rebooting my main concern are those black lines appearing I would flash to stock and claim warranty
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I've already triggered the Knox Warranty Void

[Q] Kernel is not seandroid enforcing (CM12)

I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?

Agrajag27 said:
I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Click to expand...
Click to collapse
your bootloader detects that, so there is no way to get rid of it.
my note 4 does this but I have actually never seen it on my P900, could you give more details on your exact model, rom, and kernel? I'm curious.
one way around that, I think, would be a kernel that is enforcing at boot, then use a script or an app to toggle it back to permissive (if necessary for your purposes)
edit: oops I see now -- CM 12, but still.. are you using the lollipop bootloader from the official update?

Hmmm.... I just rooted my Note Pro last night, stock rom with TWRP (latest). And though it boots up fine otherwise, I'm also getting the "Not SEAndroid enforcing" message. Would like that gone. And it is interesting that CM12 is having the same issue, because I was beginning to think about flashing it and ditching stock Lollipop.
Specifics: I used Odin 3.10 from a Windows 7 laptop for my initial boot flash of the CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 file to the tablet. No errors were reported. I also flashed TWRP 2.8.7 that way. Again, no errors. There was a beta version of SuperSU (2.49) but I didn't install that. Think I'll try it next... and hope for the best. I did install SuperSU Pro (2.46) once I'd booted the tablet, but maybe that's not available on boot?

Sterist said:
could you give more details on your exact model, rom, and kernel? I'm curious.
Click to expand...
Click to collapse
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015

Agrajag27 said:
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Click to expand...
Click to collapse
but did you at some point OTA or odin to Samsung lollipop before CM12.1?

Sterist said:
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Click to expand...
Click to collapse
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.

Agrajag27 said:
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Click to expand...
Click to collapse
I don't think there would be a way to go back to kitkat, even if you wanted to, after having installed the lollipop bootloader (happens when you OTA or Odin to stock lollipop)
to the user it's no problem at all -- it's just a visual notification to stores when you take the device back that it's been customized / modded, and voids the knox warrantee hence "Set warrantee bit: kernel"
knox, despite popular belief, is just a form of security and productive software for corporations to rely on when giving their employees a "work phone" to use, so they know that any potentially sensitive corporate information is safe from the security risks of rooting (though virtually never exploited, rest assured)
that's the most relevant answer I can give you, without repeating what I explained in my previous post *hint* lol

Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.

Agrajag27 said:
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Click to expand...
Click to collapse
the display at boot is not an error, just a notification of sorts.
the only thing I can think of is the CM maintainer may have compiled the kernel to boot as permissive and switch back via script for compatibility.
I have seen some roms that do this. not many, nor recently. I wouldn't worry about it though, especially since it's a Wi-Fi device that doesn't have any reason to visit a carrier store.
also note that the notification will show when booting a permissive recovery kernel -- these notifications are not permanent nor need to be "cleared" or "reset" they just inform the user (or technician) of the S.E.A. mode of the respective kernel at the time of boot.

Thanks. I can live with that. I'm a bit OCD and an old QA professional so it'll give me pause every time I reboot and see it, but I'll get over it. <grin>
Otherwise, I have to say, the tablet is working better than EVER with CM 12.x. Apps that caused crashes no longer do. Bluetooth keyboard works again. It's faster. I have only a single bug (the running apps list sometimes has graphic issues).

Can rooting help me?

I have a verizon S5 and the last update March 3rd messed up my screen rotation. (all rotation, camera, web browser etc.) Verizon told me I had to wait for the next Samsung update, nothing they could do. So if I can figure out how to root it, can I turn it back to an older version to make it work again? (Also lost my step counting from S health, not sure if that is related) Everything else seems to be working ok.
I don't really know what I am doing, never rooted before.....
SM-G900V
Version 5.0
security patch 2016-02-01
Base band G900VVRU2BPB1
Kernel 3.4.0
Build# LRX2.GV900VVRU2BPB1

EddieJoe said:
I have a verizon S5 and the last update March 3rd messed up my screen rotation. (all rotation, camera, web browser etc.) Verizon told me I had to wait for the next Samsung update, nothing they could do. So if I can figure out how to root it, can I turn it back to an older version to make it work again? (Also lost my step counting from S health, not sure if that is related) Everything else seems to be working ok.
I don't really know what I am doing, never rooted before.....
SM-G900V
Version 5.0
security patch 2016-02-01
Base band G900VVRU2BPB1
Kernel 3.4.0
Build# LRX2.GV900VVRU2BPB1
Click to expand...
Click to collapse
me personally i would say to root it and flash a rom on it and if that doesnt work go back to OG5
if you run into any issues or questions feel free to pm me and ill try my best to help answer it or you can always post on here
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370 just follow these steps