Database Users

What's The Best Way To Revert To 4.3 & Block OTA?

I just updated to 4.4 yesterday, now battery life is horrible and tethering is broken. This is the weakest update I've seen since I moved to Android with the N1 launch. Other than the boot animation and a slight boost in wifi speeds I'm really not seeing any redeemable qualities in Kit Kat. I want to go back to 4.3 and block the OTA. What's the best way to do it? Is there any way to stay really close to stock rooted and do that? I'd prefer not to use any highly customized and buggy ROMs but if I have no choice I'll do what I have to.
Any suggestions?

GorillaPimp said:
I just updated to 4.4 yesterday, now battery life is horrible and tethering is broken. This is the weakest update I've seen since I moved to Android with the N1 launch. Other than the boot animation and a slight boost in wifi speeds I'm really not seeing any redeemable qualities in Kit Kat. I want to go back to 4.3 and block the OTA. What's the best way to do it? Is there any way to stay really close to stock rooted and do that? I'd prefer not to use any highly customized and buggy ROMs but if I have no choice I'll do what I have to.
Any suggestions?
Click to expand...
Click to collapse
I'm no expert but surly this would be a case of using something like Wugtool kit and revert to stock, then simply unlock the bootloader and flash a custom recovery this will block the update.

slugger09 said:
I'm no expert but surly this would be a case of using something like Wugtool kit and revert to stock, then simply unlock the bootloader and flash a custom recovery this will block the update.
Click to expand...
Click to collapse
I was already rooted and had a custom recovery on stock 4.3 but read that OTA would still be applied unless a custom kernel was installed or other major differences. I also couldn't tell whether the OTA will just fail and not be applied or if the error encountered would fubar my phone.

GorillaPimp said:
I was already rooted and had a custom recovery on stock 4.3 but read that OTA would still be applied unless a custom kernel was installed or other major differences. I also couldn't tell whether the OTA will just fail and not be applied or if the error encountered would fubar my phone.
Click to expand...
Click to collapse
as long u have custom recovery, the ota will still popup but no install, if i remember to block ota popup u need custom kernel
edit: the error on ota install would háppen b4 the ota would do anyting to the phone.

you do know that you can not judge battery life from one or two of the first battery cycles with a rom, right? first boot is when the device does most of its syncing, and you will get the worst battery life. not until the 3rd or 4th battery cycle will you actually see what the battery life is really like. and tethering isnt broken, the default tethering option works fine. third part tethering apps could be broken in 4.4, until they fix things.

opssemnik said:
as long u have custom recovery, the ota will still popup but no install, if i remember to block ota popup u need custom kernel
edit: the error on ota install would háppen b4 the ota would do anyting to the phone.
Click to expand...
Click to collapse
Thanks! What I needed to know.
simms22 said:
you do know that you can not judge battery life from one or two of the first battery cycles with a rom, right? first boot is when the device does most of its syncing, and you will get the worst battery life. not until the 3rd or 4th battery cycle will you actually see what the battery life is really like. and tethering isnt broken, the default tethering option works fine. third part tethering apps could be broken in 4.4, until they fix things.
Click to expand...
Click to collapse
I'll give it a few days on the battery unless it's out of control. My biggest concern was that it was charging at a slower rate. For the first 8 hours it couldn't do more than maintain current charge level while charging with my MBP. It seems to have overcome that now. I checked usage and couldn't see any heavy syncing.
Many thanks on the tethering. I was using stock tethering but couldn't get any traffic to get to the phone or past it but DHCP was working. After reading your comments I tried again, this time with another Android device and it worked. I want to say I had a similar problem before tethering a Win8 system so I will investigate that more.
Thanks again for all the replies. Really appreciate it.

Update
I thought I was OK with KitKat until I saw the stock email app had been updated to look just like the awful Gmail app. K9 won't work with my exchange accounts so after failing to get the earlier stock email (4.1) to work in KitKat I went back to 4.3. After a week I got nagged by OTA alerts. For others in search of a fix for BLOCKING OTA UPDATES ON THE NEXUS 4, I BLOCKED OTA UPDATES by following this great thread http://forum.xda-developers.com/showthread.php?t=1998378
I installed FOTAKILL, changed permissions, wiped the caches in recovery and renamed the otacerts.zip in /system/etc/security/ (using ES with root and mounting system with RW - plenty of other ways to do this) and no more hard update notification that you can't swipe away. There's a service manager you can try out also but reviews seemed spotty - read the linked thread for more info. Best of all I can use my phone and not be forced to use $h!tShat and I don't have to spend hours researching ROMs and kernel combinations and their respective bugs. Hope this info helps someone else. I couldn't get any hits searching for fixing the OTA problem with the N4 but the Nexus7 instructions have carried over to the N4 pretty well.

[Q] Problem after Rooting

Hi everyone
I have an international version of Note 3. The problem I'm facing is, after rooting my phone and installing Lidroid Custom ROM, the battery on my phone started draining badly. To get rid of the problem I reinstalled Stock ROM on it and also unrooted the phone. But the problem is still there.
Even without using the phone, the percentage drainage is about 1% every 10-15mns. Have removed all third party application from the phone, but to no avail.
Can something be done about this? I'm at wits end and need a solution badly. Please respond ASAP.
Thanks in advance.

anirmj said:
Hi everyone
I have an international version of Note 3. The problem I'm facing is, after rooting my phone and installing Lidroid Custom ROM, the battery on my phone started draining badly. To get rid of the problem I reinstalled Stock ROM on it and also unrooted the phone. But the problem is still there.
Even without using the phone, the percentage drainage is about 1% every 10-15mns. Have removed all third party application from the phone, but to no avail.
Can something be done about this? I'm at wits end and need a solution badly. Please respond ASAP.
Thanks in advance.
Click to expand...
Click to collapse
Get wakelock detector from Google play see if it's a app draining the battery

Get into recovery mode and clean your cache, whatever bad bug went on with the custom ROM flash is still there. Once you clear it you should be OK.

Why does my S4 keep rebooting? [Log Inc]

EDIT: Here's a verbose log that was being recorded before the device rebooted as explained below. It happened 2 seconds after I locked the screen with the lock key...
http://www.fast-files.com/getfile.aspx?file=74248
I know it's a big file, and it's long but it does open in regular Notepad, just wait 40 seconds. Hopefully you can find the cause at the bottom of the log. I can't make sense of it.
---------------------------------------------------------------------------------------------------------------
Hey guys, any idea how to find out why my S4 seems to be rebooting every few hours, mostly after being woken up?
Some tech info:
Baseband: I9505XXUGNE5
Stock Kernel
SE For Android: Enforcing
Build Number: KOT49H.I9505XXUGNE5
Phone is rooted & Xposed installed
Quick bit of info:
It seems to happen 90% of the time when the screen goes off. By this I mean, the screen can go off no problem and then I can turn it back on without an issue. However if the phone does reboot, it seems to be when the phone is woken up after being locked/asleep. However it does happen sometimes whilst I am using the phone. Though very rarely.
It's also important to note that the phone does a 'fast reboot', not a regular one. Like it skips the 'Samsung Galaxy S4' screen and just goes straight to the spinning logo. It does reboot very fast, but it is really annoying.
However I don't have to put my SIM PIn in again, it just asks for my phone PIN and then starts to load apps as normally.
Is there some sort of App I can install that will log all errors right up to the point where it crashes. Then I could view the log and work out what caused the crash? I have the Donate of aLogcat but it doesn't seem to allow me to do this...
Any ideas guys? Any info would be absolutely awesome.

I really don't mean to bump guys but I've flashed 3 times now and still get reboots...
Could I need to flash a new boatloader or something?

The download is to slow. Just post your log in pastebin and post the link here.
What I would do in your case is to fully wipe (also wipe your sd card) and return to a clean rom. Don't install any apps, dont restore backups and see if the problem persists.
If even with a fress install you have to issues, then it's a hardware issue.

Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.

leijonasisu said:
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
Click to expand...
Click to collapse
I updated the post HERE if somebody is interested. More KNOX remains to freeze or delete

leijonasisu said:
Hi, thanks for the reply. It seems that it could be a bad official release actually:
http://forum.xda-developers.com/showthread.php?t=2761933
I added my 2 cents at the end here. Hopefully freezing everything KNOX related (as KNOX was updated in this version) will fix the issue.
I'll report back and say if it does anything.
Once again thanks a lot for the reply. Fingers crossed this works and that it isn't a hardware issue.
Click to expand...
Click to collapse
I would suggest performing a factory reset before freezing the Knox stuff. That way you have a clean start.

I'm also experiencing the same issue ( random reboots) but let's make one thing clear; this is happening ONLY after rooting. No reboots if you do NOT root, all works fine. Another thing I would like to establish when you guys say delete Knox apps, do you aside from doing search in Titanium Backup and deleting all apps entries, also do a search in the root folder with Root Explorer and delete every Knox entry? Because in my experience if you do that, the phone will not boot beyond the Samsung logo.
What i also experience is a freeze when the phone asleep/idle for a while or after a battery recharge the lock screen will open but the home screen is frozen you have to turn the screen off/on for the home screen to react. God knows how many times I have reflashed this rom, at least a dozen times. One thing is sure, its absolutely perfect when it's not rooted, no problem at all. Here is what I install after rooting
:
SdFix
AdAway
Root Explorer
Rom Manager
Titanium Backup
* I also experimented with TWRP, CWM, PhilzTouch (all latest versions) and rooted with Cf-Auto root and Via update SuperSU v1.97, v1.99.r2, v1.99r3.
So there you go, my analysis is that without root all is fine. But I and I think all of here want root, so I hope someone gets to the bottom of this. I already sent the venerable Chainfire my experince with this rom. Fingers crossed.

wild wadi said:
I'm also experiencing the same issue ( random reboots) but let's make one thing clear; this is happening ONLY after rooting. No reboots if you do NOT root, all works fine. Another thing I would like to establish when you guys say delete Knox apps, do you aside from doing search in Titanium Backup and deleting all apps entries, also do a search in the root folder with Root Explorer and delete every Knox entry? Because in my experience if you do that, the phone will not boot beyond the Samsung logo.
What i also experience is a freeze when the phone asleep/idle for a while or after a battery recharge the lock screen will open but the home screen is frozen you have to turn the screen off/on for the home screen to react. God knows how many times I have reflashed this rom, at least a dozen times. One thing is sure, its absolutely perfect when it's not rooted, no problem at all. Here is what I install after rooting
:
SdFix
AdAway
Root Explorer
Rom Manager
Titanium Backup
* I also experimented with TWRP, CWM, PhilzTouch (all latest versions) and rooted with Cf-Auto root and Via update SuperSU v1.97, v1.99.r2, v1.99r3.
So there you go, my analysis is that without root all is fine. But I and I think all of here want root, so I hope someone gets to the bottom of this. I already sent the venerable Chainfire my experince with this rom. Fingers crossed.
Click to expand...
Click to collapse
It's doubtfull that rooting has anything to do with it. You are using the Chainfire root and from what I remember is that it doesn't change anything in the kernel that would result in those errors you descripe. Did you try rooting and not installing those apps? Also did you try other roms?
My guess is is that it's SdFix that is causing the lags.

Lennyz1988 said:
It's doubtfull that rooting has anything to do with it. You are using the Chainfire root and from what I remember is that it doesn't change anything in the kernel that would result in those errors you descripe. Did you try rooting and not installing those apps? Also did you try other roms?
My guess is is that it's SdFix that is causing the lags.
Click to expand...
Click to collapse
Chainfire asked in another post people who are experiencing these reboots to list their installed root apps which I sent to him.
http://forum.xda-developers.com/showthread.php?t=1538053&highlight=random+reboot&page=551
Maybe it is SdFix. I will check that out but, I would like to know if others who are experiencing reboots here have SdFix installed or maybe to list their installed root apps (like Chainfire suggested) so we can compare notes as to who is and who is not experiencing random reboots.

I9505 random reboots

Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks

juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
You have to uninstall every Knox app, that will stop the reboots
Sent from my Galaxy S4 using Tapatalk

juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Remove all Knox related apps via "Titanium Backup" and you are good to go. :good:

there is also an xposed module that deals with these random reboots, but personally i think the best way is to revert to an earlier firmware. fnb8 is rock solid.

I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.

Yes
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to xxufnb9 ?

I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
nm8 said:
I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.
Click to expand...
Click to collapse
wuwinso said:
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to UGNF ?
Click to expand...
Click to collapse

juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
yup same here after reading this thread and removing all knox crap.... phone has not had a self reboot reboot for the day...

Revert
Had to reflash the old XXUFNB9, it was useless with all those restarts. Downgrade went okey, however need to delete the Media Storage `s cache because it will keep crashing. Testing now if it solved the problem.
Update 1: after 2 hours later no restart so far..
I recommend this solution who doesn`t want to loose everything and risking if a factory reset will solve this issue. There is a problem with the KNOX 2.0 update (XXUGNG8) ...
Update 2: Link for the firmware, for whoever choose to do this way: http://www.sammobile.com/firmwares/3/?download=31852

Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...

juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
nm8 said:
Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...
Click to expand...
Click to collapse
Stabil for 3 hours or 2 days - well that's for sure great ....
You both must be joking - take older NB8 and you can have an uptime of > 1 month without any problem,
All newer version are worse -
As s.o. mentioned, there is an Xposed Modul made by Thomas Hofmann that tries to solve this. This is not a Knox problem but seems to be in AOSP itself - although might mainly be triggered by Knox 2.0 (NB8 is still Knox 1.0). In general situation goes worse the more processes are started, i.e. with heavy load. It is said to happen not only with S4 but e.g. also with N3.
As Thomas Hofmann stated: "I figured out that actually the system server process crashed due to an ArrayIndexOutOfBoundsException"
If you want to know details plz have a look at Thomas's blog. With his modul he mainly catches a faulty parameter value that would otherwise cause a certain method to crash. As a result he manages to avoid the reboot but of course the real problem goes deeper, so to fix this for real Google / Samsung are needed.
=> I want a 4.4.4 rom with towelroot fixed, without those ArrayIndexOutOfBoundsExceptions and as solid as NB8 - but I doubt Samsung is able or willing to do this.

I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......

Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
nm8 said:
I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......
Click to expand...
Click to collapse

no random rebooting anymore xugng8 firmware
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
i have sorted my i9505 to the xugng8 firmware by re-installing with latest odin...download fresh stock firmware xugng8 firmware and i re-installed 2 weeks now no reboot ,but make sure before you do these steps usb debuging mode is selected ,rest you all know

nm8 said:
I don't use towelroot because I don't have to.
Click to expand...
Click to collapse
Yes, many think this to be a nice 'feature' to get root, but that rediculous. Towelroot (plus the older Exynos bug - but that was Samsung specific) is the biggest bug in Android since many years. Using a kernel that is not hardened against this (this unfortunately includes the otherwise almost perfect NB8 rom) could mean you couldn't be save anymore from someone taking over your phone unnoticed using root authorization.
---------- Post added at 02:20 PM ---------- Previous post was at 02:08 PM ----------
juzzy16 said:
Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
Click to expand...
Click to collapse
As said those reboots most certaintly are caused by a bug in AOSP code itself - but in fact they seem to be mainly triggered by Knox 2.0. Otherwise a lot more phones other than S4 or N3 should be involved.
As we will never know fpr sure if and when Google/Samsung will solve the real reason of this problem and "removing" Knox 2.0 seems to help, it would be very nice of you (juzzy16, nm8, sneazy) to perhaps add another comment in 2-3 weeks about reboot behaviour again including the rom version you are using and what exactly of Knox you had removed.:good:

Service Provider Update after Root

I have followed the guide to flash the unlocked firmware and root my S7 Edge (http://forum.xda-developers.com/ver...de-flashing-sm-935u-firmware-verizon-t3415145) and all has been working well this weekend. This morning my phone gives me a persistent popup notification about a service provider update and "my device will restart to configure features supported by new sim card." The only option is to press ok and allow it to reboot. I cannot use my phone while this notification is active, and I am unable to kill it in any way. When the phone reboots to recovery, the configuration fails with "dm-verity verification failed". I then reboot system or power off and the endless cycle continues.
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.

I wasn't getting any notifications however i did have some strange behavior going on and rebooted only to get the dm-verity verification failed and was no longer able to boot it would just sit at the Samsung splash screen I then had to factory reset re-post and re-setup everything, hopefully your experience won't need that since you are still able to boot!
Sent from my SM-G935U using Tapatalk

Thank you for the response, it's always nice to know someone has had similar problems. Looks like I will have to try reflashing the firmware. After your re-setup, did you do anything to prevent the issue from reoccurring?

Everything is again in working order. If anyone finds this and has the same problem, after flashing the Verizon fixes the phone is identified (in the about device setting) as the SM-G935V version again and is set to download updates automatically. I unchecked this option and I hope this should prevent it from happening again.

Not really wasn't sure exactly what happened the first time but thankfully (knock on wood) ??? it hasn't happened again.
Sent from my SM-G935V using Tapatalk

mine did it too. had to reinstall the whole thing.

drmatthews1 said:
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
Click to expand...
Click to collapse
shawnten said:
mine did it too. had to reinstall the whole thing.
Click to expand...
Click to collapse
I encountered this issue today and found a solution:
http://forum.xda-developers.com/galaxy-s7/help/whats-package-service-provider-update-t3425169

This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!

Dameon87 said:
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Click to expand...
Click to collapse
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?

thedrizzle said:
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
Click to expand...
Click to collapse
This has been my experience, as well as a few others. I'm not 100% sure it's that setting in particular, but I am 100% sure that it is caused by a setting in xTouchWiz. I had the issue once before, and it was a clean install save for xTouchwiz and me running through all the options. Since then, I've limited the choices in xTouchwiz and have not experienced the issue since. When I have some time I'll run through it and see if I can replicate the behavior again, since I'm working on a ROM.

There is a simple fix...
I agree, XtouchWiz drops a bomb when installed and it will cripple your phone. I never played with DVFS, I personally though it was the disable TIMA that set it off. An easy fix for anyone who stumbled on this. Power off your phone, remove the sim card, power up your phone, freeze a service called AutoPreconfig, power down and insert sim, good to go.
More info http://forum.xda-developers.com/gal...ge-service-provider-update-t3425169?nocache=1
Shout out to Wired4Fun for this easy fix.