I'm run a Sprint Note 3 stock rooted 4.4.2 NC5 with Philz CWM version hltespr 6.12.9. I decided to update to 4.4.4 NK4. First, thought I would skip a step by not unrooting device and just did a factory reset. Then booted into download mode and Odin flashed NK4 ( I used a fresh copy from Sammobile 1.50gb zip ). When the flash was finished ( Passed on odin ) the device tried to start and bootlooped or what some might call a soft brick. Pulled the battery and then booted into recovery, and found to my suprise that the custom recovery was still installed. The Odin flash did not completely take, so while in recovery I wiped caches, data, and system.
Now from recovery booted into download mode and Odin flashed NK4 again. This time it installed properly and so I went back and forth from NC5 to NK4 about 6 times. Why, to check various things like signal strength ( about the same with both NC5 and NK4 basebands ) GPS ( found no problem with getting GPS to lock with NK4 ) Ram footprint ( at first boot up NK4 only slightly larger than NC5 ) . Of course going back to NC5 from NK4 resulted in bootloop or soft brick at boot up, the easiest way to fix this is to pull the battery boot into recovery do a factory reset, then Odin flash NC5 again. If you are the least bit timid about bootloops and soft bricks I don't recommend doing this.
Ok, so now I have a stock, recovery status ( official ) NK4 installed. Next installed a custom recovery, went with Philz CWM hltespr v6.12.9 ( this recovery is bulletproof ). I Odin flashed Philz and booted the device everything good. Next booted into recovery and flashed Super Su v2.40. Then booted back into NK4 everything running great used root checker and the device is rooted.
Now I have stock rooted NK4, so now to debloat the device started with KNOX. Went to SuperSu and clicked ok to disable KNOX, SuperSu froze at "disabling KNOX". I rebooted the device and downloaded Root Explorer then did a KNOX search and about 25+ files containing KNOX ( more than in NC5 apparently they added a few new ones to NK4 ) did a multi-delete and then rebooted device and it bootlooped at start up.
So back to square one, flashed Nk4, Philz recovery, and tried the experimental ( BETA ) SuperSu 2.4.3 version. Device booted up fine, tried to disable KNOX and again it froze at "disabling KNOX", again I tried to remove all the KNOX files with Root Explorer and it bootlooped again at start up. At this point I'm going to wait till Chainfire has a cf-autoroot for NK4 and a SuperSu that will disable KNOX. Went back to NC5 with everything running smooth as glass, hope this info is helpful. Enjoy !!!
Now from recovery booted into download mode and Odin flashed NK4 again. This time it installed properly and so I went back and forth from NC5 to NK4 about 6 times. Why, to check various things like signal strength ( about the same with both NC5 and NK4 basebands ) GPS ( found no problem with getting GPS to lock with NK4 ) Ram footprint ( at first boot up NK4 only slightly larger than NC5 ) . Of course going back to NC5 from NK4 resulted in bootloop or soft brick at boot up, the easiest way to fix this is to pull the battery boot into recovery do a factory reset, then Odin flash NC5 again. If you are the least bit timid about bootloops and soft bricks I don't recommend doing this.
Ok, so now I have a stock, recovery status ( official ) NK4 installed. Next installed a custom recovery, went with Philz CWM hltespr v6.12.9 ( this recovery is bulletproof ). I Odin flashed Philz and booted the device everything good. Next booted into recovery and flashed Super Su v2.40. Then booted back into NK4 everything running great used root checker and the device is rooted.
Now I have stock rooted NK4, so now to debloat the device started with KNOX. Went to SuperSu and clicked ok to disable KNOX, SuperSu froze at "disabling KNOX". I rebooted the device and downloaded Root Explorer then did a KNOX search and about 25+ files containing KNOX ( more than in NC5 apparently they added a few new ones to NK4 ) did a multi-delete and then rebooted device and it bootlooped at start up.
So back to square one, flashed Nk4, Philz recovery, and tried the experimental ( BETA ) SuperSu 2.4.3 version. Device booted up fine, tried to disable KNOX and again it froze at "disabling KNOX", again I tried to remove all the KNOX files with Root Explorer and it bootlooped again at start up. At this point I'm going to wait till Chainfire has a cf-autoroot for NK4 and a SuperSu that will disable KNOX. Went back to NC5 with everything running smooth as glass, hope this info is helpful. Enjoy !!!
Written by dd
We are Creative Blogger Theme Wavers which provides user friendly, effective and easy to use themes. Each support has free and providing HD support screen casting.
0 commentaires:
Enregistrer un commentaire