Database Users

[Q] Nexus 4 bootloop after official 4.3 OTA

Hi!
I just bought a Nexus 4 with broken touch screen which I replaced myself.
After I replaced it, I decided to start fresh and updated the device directly to stock 4.4 using fastboot commands and got stuck in bootloop (4 circles going on for hours).
Then I tried different factory images and managed to boot under official Android 4.2.2 and it worked flawlessly until I tried to update with 4.3 OTA (with radio .83)
I found out that downgrading radio from .83 to .48 (or .53) allows the device to boot under Android 4.3.
I'm now stuck at this stage because the same trick does not work after 4.4 OTA (from 4.3).
The issue seems to be acknowledged by Google but they don't seem to have an official software fix for it since they only go for a replacement.
I'm considering an RMA but since I replaced the screen myself, I'm facing the risk to be charged 200€ if my warranty gets void (if they really control the device as they say).
Anyone managed to fix this issue? It seems to be linked to the radio (can't go further than radio .48 / .53)?

Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.

neoantho said:
Just found out that the jack/proximity/light sensor wasn't properly connected, probably after the screen replacement. It now boots under 4.4.2
Found people with the same issue on this thread : http://forum.xda-developers.com/showthread.php?t=2595283
Just ended up reading it but my researches did not drive there earlier.
To conclude, bootloop under 4.3 and 4.4 can be related to a faulty (or just disconnected) sensor.
Click to expand...
Click to collapse
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!

varun037 said:
I confirm my nexus also bootloops on android version >= 4.3.0 due to faulty sensor.
Basis of conclusion:
My nexus 4 also started bootloop suddenly. I tried installing 4.4.2 and even 4.3 from factory images but everytime it stuck at boot animation. The only version currently working is 4.2. I always used a software called smart cover but it started mus-behaving. so i downloading phone tester and proximity sensor finder from play store, both the programs told me they were waiting for sensor/they did not get data from proximity and light sensor.
Question:
is there any way to update to 4.4.2 without being stuck at bootloop without replacing the sensor?
thanks in advance!
Click to expand...
Click to collapse
Did you find a solution?

Not yet. I will definitely post if I am able to find one. Researching on the topic currently.

I've got the same problem with 4.3 bootloop. Could this be fixed with custom rom?

Try flashing 4.2.2 rom - custom or stock

I'm with 4.2.2... and that's not what I asked. I want 4.4.2. Is it possible to load custom kit kat with this kind of sensor problems?

Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.

varun037 said:
Update:
I have been trying to update nexus. I tried to install radio version 98 and bootloader from 4.4.2 version to android 4.2.2 without updating system image. it works. so i think basically the issue is with the system image itself. looking for the patched system image now or a developer who can patch system image to ignore the faulty sensors.
Click to expand...
Click to collapse
I'm on 4.3 and the sensors dont work ... the proximity, gyro... nothing works... any solution?

Hello friends, i have a similar problem.
I went to replace the glass and warmed him a lot and damaged the lcd. I bought a complete lcd with touch, but when installing it the cel came in infinite boot, Flashed the 4.2.2 and booted but sensor is working by testing q I did for an app, the problem is they do not find my network and baseband ta as unknown, been through the radio's 4.2.2 (the version I am now). the motherboard was not with the screen when I get heated to the glass, were in housing with the display flex earpiece with proximity sensor and flex usb that has the microphone and led, everything is normal, the LED only that does not work. One would like some light please. I thought about buying the flex usb to see if it resolves, but does not want to risk spending for nothing. Thank you very much!
Sorry for my english, I'm using google translator

Sorry to Disturb
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif

Gloftking said:
Hello everyone I am very new to this area of computing (and this forum). However I have still ended up in the same hole as you guys are describing although it happened for a completely different reason. (BTW: I am rooted)
one day I tryed to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' error. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
Click to expand...
Click to collapse
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.

FEW
varun037 said:
You might be able to re install your android without clearing user data. Try to flash the device with Google provided factory images without the reset tag.
Click to expand...
Click to collapse
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif

Gloftking said:
Thanks for the quick responce. Could you please describe in more detail what exactly you mean and how I would go about doing this because I only vagely know what you mean by flashing.http://forum.xda-developers.com/images/smilies/confused.gif
Click to expand...
Click to collapse
Follow this. It has the reset flag removed and will not wipe your data
http://forum.xda-developers.com/showthread.php?p=53176897
Sent from my Nexus 5 using XDA Free mobile app

Hi,
I am facing the same issue .. Nexus 4 is stuck at boot loader after screen replacement .. is there any solution that I can follow to resolve this .
Regards,
Ripu Daman

The same problem with me, i did replaced my phone screen. I didn't notice that could damaged the phone. :crying:
so, theres no way to solve ??

Only way is to downgrade the os version to 4.2.2 and stay there.

nexus 4 stuck at boot loop.
Hi guys i have the same problem as you are describing, o got a nexus 4 android 4.2.2 JQRW build I've flashed it from all different ways and i just got flash cm10.2 and carbon rom but only stuff jeallybean and as someone said here i used adb sideload to push the update 4.3 and got stuck at the boot but i flash the radio 84 to 48 and my phone boot Fine but i am stuck at jeallybean yet and i want chroma rom android 7
---------- Post added at 03:00 AM ---------- Previous post was at 02:56 AM ----------
Please we need a wise man to fix this problem. I am tired of flashing stock img and custom ron for nothing.

[Q] Buttons and bottom half of screen unresponsive.

After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?

jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:

x102x96x said:
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:
Click to expand...
Click to collapse
It was an official update so short of rooting it and flashing a new firmware i don't see any other options.

jake262 said:
It was an official update so short of rooting it and flashing a new firmware i don't see any other options.
Click to expand...
Click to collapse
rooting is not necessary for flashing stock rom.

I'm having the same problems. Screen locks up often when I'm browsing in Chrome. For Gods sake this has 3gb of RAM!!!!!
Sent from my Nexus 7 using Tapatalk

x102x96x said:
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:
Click to expand...
Click to collapse
ok so i flashed a stock kitkat firnware. the problem is still there.

jake262 said:
ok so i flashed a stock kitkat firnware. the problem is still there.
Click to expand...
Click to collapse
flashed original rom via odin 3.09. Them hard reset. I have the same problem with screen. Is software problem.
Sorry for my bad English.

jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
While phone works just pull out the battery and also don't use cover. I think its just about samsungs politics. ..
Sorry for my English

Same issue
jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
I also have the exact same problem... I already did the factory reset but no luck. I increased the sensitivity but still happens...Can anyone help us? or it is caused by the recent upgrade of OS to kitkat version... Thanks.

GOOD NEWS!
I have been having this issue as well. Lots of research on the net has provided me with no real solutions. I think there is something missing in this update. I do not know what it is im not that smart but something is wrong across the board.
I have done a master reset back to factory and within minutes of the set up it started lagging/ not responding again. Figured i would give it a few days and well nothing changed so I contacted T-mobile and spoke with Tech Support located in Texas and he concluded that it is an SD card. He says that the SD card was on the phone prior to the update and is causing the issue since its old. WTF! I told him that the processor, ram, HDD, CPU are all considered old now. Personally I think its a stupid response.
I am going to give this a shot anyways. NO SD card no pictures no music.... Already within 15 minutes of no SD card issues are still there. I am really starting to hate this phone because of this update. Hoping to get a replacement (new) with 4.3 still on it. NO UPDATE for me till i know this and several issues are fixed.
I know i could root but i dont feel i should have to to fix any issues.
Has anyone else found a solution or heard of one yet?

Just try this , go to setting / general / power save , swith it on.
Then wait a moment before you try your phone again.
my wife phone got this issue because of over heating.
after switching the power save , the issue is gone.

update... contacted Tmobile within the last hour and apparently this rep said this is a known issue. She contacted Samsung and Google (could be blowing smoke up you know what) but she came back and said they are very aware of the issues and are vigorously working on a fix and your informations will be one of the first ones to get it. She was saying 4.4 (kitkat) screwed up a lot of Samsung devices. BTW she was also having the same problems. All replacement phones will come with 4.4 so exchanging is out of the question.
Regarding the power saving thing ill give it a shot. It was on before the master reset. Noticed it was off when i went in. On now so ill try then.

Problem with touchscreen since 4.4.2 update

Hey there
A friend of mine has the following problem with his Note 3 (completely stock).
Since the latest 4.4.2 OTA update, sometimes suddenly the screen does not respond to touching it with your hand. It does react to the stylus.
Locking and unlocking the screen does the job, but only for a few minutes.
I wiped the phone via stock recovery, but the problem persists.
Anyone with the same problem, or maybe a clue?
Thanks!
GT-i9300, CM11, Boeffla

joriswagter said:
Hey there
A friend of mine has the following problem with his Note 3 (completely stock).
Since the latest 4.4.2 OTA update, sometimes suddenly the screen does not respond to touching it with your hand. It does react to the stylus.
Locking and unlocking the screen does the job, but only for a few minutes.
I wiped the phone via stock recovery, but the problem persists.
Anyone with the same problem, or maybe a clue?
Thanks!
GT-i9300, CM11, Boeffla
Click to expand...
Click to collapse
Hi
Same problem here,I tried several 4.4.2 official and custom roms but not fixed and I tried these too:
I tried mega wipe and last rom in samfirmware!
I removed my external sd card
And I googled and found there are others with same problem so it shouldn't be hardware problem
p.s.When screen freezes just half of it works! And just doesn't work by fingers and it works by s_pen!
There no way to come back to 4.3 too
What should I do?
Ty in advance

Finally Solved!
Hi
I had same problem
I did everything u said like:
mega wipe and changing rom
custom roms
taking out battery when it's on ( I Did this but I don't know It had any effects on my phone or not!)
taking out external card
But I still Had the Problem
Solution:
But I had a flip cover and I separated that from phone and thanks God,surprisingly It's Fixed and it works like a charm!!! after that I used my original cover and there is no problem till now.
Good Luck

Had the same issue posted it here bit no one responded.
Solution: The flip case I had..there's a problem with it where it locks the screen even when the case is not closed. But lately I had no issue it just seem to gotten fixed by itself.
Sent from my SM-N9005 using XDA Premium 4 mobile app

[Q] Problems with screen and Back, home, menu and something else!!!

Hi guys!
I've just bought a Note3 n9005 in Singapore, starting with ANdroid 4.4.2
At first it worked very well. But after some times I restart, an error appeared immediately after the phone is on "Unfortunately...process phone.android.com has stoppped". I choosed "OK" and it wont come again if I dont restart my phone,
But it's not only all my problems. In fact I had used a fake S-view although it doesnt work with kitkat (It's a gift from Phone store, It was only used to protect the phone like a flip-cover). And a new problem appear: sometimes my phone is in LAG Touchscreen does not work, I try to drag the Notification bar down, I can do it, and then the screen displays the "notification infomation", touching is unresponsive. Home button and 2 touch buttons Back+menu does not work too. It is just solved by turn off the screen using Power button, and turn on it again.
Can someone tell me the reason about my problems? And how to fix them?
Thank you!
P/s:I'm sorry this is my first post so it can contains errors. Tell me please

Please help meeeee

Have you verified that ur phone is genuine.If yes try doing a factory reset or reflash stock 4.4.2 from odin
Sent from my SM-N900 using XDA Premium 4 mobile app

hhealso included
shine.vietnam said:
Hi guys!
I've just bought a Note3 n9005 in Singapore, starting with ANdroid 4.4.2
At first it worked very well. But after some times I restart, an error appeared immediately after the phone is on "Unfortunately...process phone.android.com has stoppped". I choosed "OK" and it wont come again if I dont restart my phone,
But it's not only all my problems. In fact I had used a fake S-view although it doesnt work with kitkat (It's a gift from Phone store, It was only used to protect the phone like a flip-cover). And a new problem appear: sometimes my phone is in LAG Touchscreen does not work, I try to drag the Notification bar down, I can do it, and then the screen displays the "notification infomation", touching is unresponsive. Home button and 2 touch buttons Back+menu does not work too. It is just solved by turn off the screen using Power button, and turn on it again.
Can someone tell me the reason about my problems? And how to fix them?
Thank you!
P/s:I'm sorry this is my first post so it can contains errors. Tell me please
Click to expand...
Click to collapse
What did you do exactly? did you root your phone and try to delete some stuff? use touchscreen test for your touchscreen to see
the problem,, you can find them on the play store.
What is your phone build number? last resort is just get the stock firmware and reflash it with odin3.09. search it over the forum.

RISHI RAJ said:
Have you verified that ur phone is genuine.If yes try doing a factory reset or reflash stock 4.4.2 from odin
Sent from my SM-N900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've verified, it's genuine bro I'm going to hard reset tonight cause I left it home :/
zonicz said:
What did you do exactly? did you root your phone and try to delete some stuff? use touchscreen test for your touchscreen to seethe problem,, you can find them on the play store.
What is your phone build number? last resort is just get the stock firmware and reflash it with odin3.09. search it over the forum.
Click to expand...
Click to collapse
its build number is KOT49H.N9005XXUENA6. I've not rooted it yet, It is running on stock rom 4.4.2 of Samsung.

shine.vietnam said:
I've verified, it's genuine bro I'm going to hard reset tonight cause I left it home :/
its build number is KOT49H.N9005XXUENA6. I've not rooted it yet, It is running on stock rom 4.4.2 of Samsung.
Click to expand...
Click to collapse
Yes, do factory reset first. Backup everything from kies since your device is not rooted. will see from there.

zonicz said:
Yes, do factory reset first. Backup everything from kies since your device is not rooted. will see from there.
Click to expand...
Click to collapse
This ^^
------------------------
If that doesn't fix it, you may have touchscreen issues. Some Note's are affected by this and need replaced.

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: