FORUMS

Google No Longer Sending Calendar SMS Notifications

In a not entirely surprising move, Google announced that it’s putting an … more

Enable Multi-Window Mode on M Developer Preview

What was not mentioned in yeterday’s keynote was Android M’s multi-window … more

I/O Summary: Google Cardboard Virtual Reality

One year ago, Google introduced cardboard. Amazingly enough, that was all it took to fire … more

Android M Preview Images – XDA TV

Android M preview images are available. That and much more news is covered by Jordan when he … more

XXUGNE5 (new Kitkat Update) random reboots.

Thanks Meter: 67
 
By MarkMRL, Senior Member on 24th May 2014, 06:19 PM
Post Reply Subscribe to Thread Email Thread
11th July 2014, 07:04 PM |#81  
wild wadi's Avatar
Member
Thanks Meter: 7
 
More
For me it's very simple; I do not freeze any app, root with CF-Root= reboots. Re-flash stock rom= no reboots. Flash with TowelRoot= no reboots. That simple : )
 
 
9th September 2014, 08:07 AM |#82  
Junior Member
Thanks Meter: 1
 
More
My Experience and FIX
sorry to resurect an older thread, but here's my fix for softbooting XXUGNE5 and others:

On a Galaxy S4 (i9505 variant) I successfully updated with a flash of I9505XXUGNE5 and later I9505XXUGNG8 (4.4.2 Kitkat) through ODIN and rooted both times;
I9505XXUGNE5 was rooted using Towelroot V3;
I9505XXUGNG8 was rooted using the CF-Autoroot method (google for instructions).

In both cases, after a successful root, and successful SuperSu update, the Galaxy S4 (I9505) became unstable, suffering random softboots, usually on system wake.

After some research, I found that the system softboots where fixable, but was disappointed that I did experience 1 softboot post the fix. I therefore set upon completely eradicating the problem causing the crash.

First off; the crash fix was identified by xxxx, who wrote an Xposed Module (SSCF) that could be loaded through Xposed Installer. This module, once installed, could prevent the crash, and log the error causing the crash. In my case, the crash log reported something to do with com.sec.knox.seandroid

Again after some research, it appears that when you first open SuperSU after rooting the device, you are asked if you wish to block KNOX, which I did, and which appeared to have been successful. However, my understanding is that KNOX will still attempt to flash error/warning messages even whilst being blocked by SuperSU, and I suspect that this message/block combination was somehow confusing the system and causing the crash.

On my device, I9505XXUGNE5 was crashing every 10 minutes, and I9505XXUGNG8 less so, but still annoyingly so.

Trawling the threads across the internet, I found a multitude of potential fixes and remedies, and decided to try them all as a combined self-defense attack against the crashing.

14 Steps to a smooth Galaxy S4 (I9505)
1. Backup any data as necessary
2. Boot the device into recovery and wipe data/factory reset
3. Flash your Galaxy S4 (i9505) with a stock firmware (Id recommend I9505XXUGNG8) using the ODIN method
4. Root the device using the CF-Autoroot method, again through ODIN
5. Boot the device into recovery and wipe data/factory reset
6. Once up and running, either before or after your data restore from backup, download the latest SuperSU by Chainfire from the google play store (worked for me)
7. Open SuperSU and when prompted block KNOX (precautionary step)
8. Download and install Xposed Installer
9. Download and activate the SSCF module by xxxx
a. This module will prevent any crashes and report the cause in the log file
10. Download and install Terminal Emulator from the google play store
11. Open Terminal Emulator and type
a. SU [enter]
b. pm disable com.sec.knox.seandroid [enter]
12. Download and install NoBloatFree from the google play store
13. Run NoBloatFree and disable ALL KNOX related files/apps [I disabled rather than delete, and the system has been stable]
14. Now your Galaxy S4 (I9505) should run smoothly, should not suffer any KNOX related crash, but if it does is set up to auto prevent and log any crashes caused by com.sec.knox.seandroid
The Following User Says Thank You to Highbury80 For This Useful Post: [ View ]
13th September 2014, 10:35 PM |#83  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Highbury80

sorry to resurect an older thread, but here's my fix for softbooting XXUGNE5 and others:

On a Galaxy S4 (i9505 variant) I successfully updated with a flash of I9505XXUGNE5 and later I9505XXUGNG8 (4.4.2 Kitkat) through ODIN and rooted both times;
I9505XXUGNE5 was rooted using Towelroot V3;
I9505XXUGNG8 was rooted using the CF-Autoroot method (google for instructions).

In both cases, after a successful root, and successful SuperSu update, the Galaxy S4 (I9505) became unstable, suffering random softboots, usually on system wake.

After some research, I found that the system softboots where fixable, but was disappointed that I did experience 1 softboot post the fix. I therefore set upon completely eradicating the problem causing the crash.

First off; the crash fix was identified by xxxx, who wrote an Xposed Module (SSCF) that could be loaded through Xposed Installer. This module, once installed, could prevent the crash, and log the error causing the crash. In my case, the crash log reported something to do with com.sec.knox.seandroid

Again after some research, it appears that when you first open SuperSU after rooting the device, you are asked if you wish to block KNOX, which I did, and which appeared to have been successful. However, my understanding is that KNOX will still attempt to flash error/warning messages even whilst being blocked by SuperSU, and I suspect that this message/block combination was somehow confusing the system and causing the crash.

On my device, I9505XXUGNE5 was crashing every 10 minutes, and I9505XXUGNG8 less so, but still annoyingly so.

Trawling the threads across the internet, I found a multitude of potential fixes and remedies, and decided to try them all as a combined self-defense attack against the crashing.

14 Steps to a smooth Galaxy S4 (I9505)
1.Backup any data as necessary
2.Boot the device into recovery and wipe data/factory reset
3.Flash your Galaxy S4 (i9505) with a stock firmware (Id recommend I9505XXUGNG8) using the ODIN method
4.Root the device using the CF-Autoroot method, again through ODIN
5.Boot the device into recovery and wipe data/factory reset
6.Once up and running, either before or after your data restore from backup, download the latest SuperSU by Chainfire from the google play store (worked for me)
7.Open SuperSU and when prompted block KNOX (precautionary step)
8.Download and install Xposed Installer
9.Download and activate the SSCF module by xxxx
a.This module will prevent any crashes and report the cause in the log file
10.Download and install Terminal Emulator from the google play store
11.Open Terminal Emulator and type
a.SU [enter]
b.pm disable com.sec.knox.seandroid [enter]
12.Download and install NoBloatFree from the google play store
13.Run NoBloatFree and disable ALL KNOX related files/apps [I disabled rather than delete, and the system has been stable]
14.Now your Galaxy S4 (I9505) should run smoothly, should not suffer any KNOX related crash, but if it does is set up to auto prevent and log any crashes caused by com.sec.knox.seandroid

I just followed everything after "10" and it seems that worked for me...

Στάλθηκε από το GT-I9505 μου χρησιμοποιώντας Tapatalk
13th April 2015, 01:56 AM |#84  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Joku1981

Im using it since Samsung released it. You can:

1. Verify you have correct baseband I9505XXUGNE5 (dial *#1234# and attach screenshot). If you have old baseband, only flash again the GNE5 firmware through ODIN.
2. Delete all entries of KNOX app in system/app with Root Explorer (In theory, SuperSU blocks KNOX app but Samsung released KNOX 2 for this new firmware):

KNOX in System/App folder:


KNOXAgent.apk
KnoxMigrationAgent.apk
KnoxSetupWizarClient.apk
KnoxSetupWizardStub.apk
KNOXStore.apk

- Reboot to Custom Recovery and Wipe cache/dalvik cache (necessary if you don't want be stuck in Samsung logo in the next boot)
- Reboot system and delete this entries:

More KNOX remains:

Folder = Data/clipboard/knox
Folder = system/container
Folder = system/etc/secure_storage/com.sec.knox.store
Folder = knox_data
Folder = system/etc/secure_storage/com.sec.knox.seandroid
File = system/tima_measurement_info ---- TIMA is a Trust-Zone of KNOX

*EDIT: I still making tests. It's working for me now all perfect. Without reboots or KNOX reminds.

really useful bro i thought it was just me. done all steps just need to wait now
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes