I updated from MJ4 to NAB, and then to NABD, and flashed TWRP 4.4x compatible recovery, using the directions and links from the leak thread.
When I flashed the Engineering Bootloader tar in Odin, I used "bootloader" button, and it completed and is now stuck in a bootloop.
I cannot boot into Download Mode or Recovery, they both bootloop. Did I just brick my phone?
I have done the following procedure, so far, to attempt to recover my phone to operational condition.
• I just removed my SD-card and it booted into TWRP recovery. WHEW.
• I tried to update the recovery to "philz_touch_6.12.9-hltespr" which was supposed to be 4.4x compatible, and it now has a Kernel Panic message, and engaged "Upload Mode", how should I proceed to get back to normal?
○ I've tried to flash back to stock MJ4 tar using Odin, while its in the Kernel Panic upload mode, and it fails.
○ Now trying to flash into stock NAB tar using Odin + Kernel Panic upload mode, and it fails. I'm out of options. Someone please help me.
Install this one
http://kitkatkiller.eu/Files/SPRINT GALAXY NOTE 3/TW ANDROID 4.4.2/Recovery/hltespr-recovery.img.tar
This is a dumb question but searching threads provided me with ten different ways and I wasn't sure which one to pick.
I'm currently on NE6 and have TWRP Recovery and Root. I want to upgrade to NG4 via PC Odin. How should I accomplish this and maintain root and TWRP Recovery?
Download the NG4 firmware & modem from here. Flash them both via Odin. It's good practice to do a battery pull before Odin flashing for 30 seconds, then booting into download mode. It may take a few flashes to get the bootloader to stick. Confirm bootloader after flashing by booting into your current ROM and checking 'About Device' under settings. The Baseband version should read ~NG4. If it doesn't, repeat the process (including the battery pull) until it sticks. Do a full wipe then flash Stock Root Flashable Version of G900TUVU1ANG4 (or any other NG4 variant) in TWRP.
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 !!!
jimzweb1 said:
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 !!!
Click to expand...
Click to collapse
just freeze the knox **** with titanium easier.
jimzweb1 said:
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 !!!
Click to expand...
Click to collapse
What version of Odin are you using and where did you get your tar files from? I'd like to try flashing back to NC5 from NK4 to gain root without tripping Knox until something other than cf-auto can root NK4.
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
What version of Odin are you using and where did you get your tar files from? I'd like to try flashing back to NC5 from NK4 to gain root without tripping Knox until something other than cf-auto can root NK4.
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
Read through this thread should answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440
on my thread I list micmars as he has a great XDA site for .tar files. However I got the tar. files from here http://www.sammobile.com/firmwares/. If flashing back to NC5 results in a bootloop DON"T PANIC !!!! Just pull the battery boot into recovery and wipe cache and do a factory reset. Than pull the battery and boot into download mode and flash NC5 again. One thing on the second flash be PATIENT, after odin finishes and says PASSED " DO NOT UNPLUG THE DEVICE " you will notice at this point is where a blue flash line starts that is the recovery the last thing being flashed !!! It takes about 3 to 5 minutes after you see PASSED your device screen will dim and it will start up for first time use.
Your process worked like a charm for me. Fully rooted stock NC5 from NK4 using towelroot. Is there anyway to retain root and go back to NK4?
Sent from my SM-N900P using Tapatalk 2
biggdevon said:
Your process worked like a charm for me. Fully rooted stock NC5 from NK4 using towelroot. Is there anyway to retain root and go back to NK4?
Sent from my SM-N900P using Tapatalk 2
Click to expand...
Click to collapse
No, sorry NH7 closed the exploit used by Towelroot in NC5. It has not been updated for NH7 or NK4. If you use Towelroot, cf-atuoroot, or De La Vaga root on NH7 or NK4 you will trip KNOX !!!
If your KNOX warranty is tripped like mine then root with SuperSU. Just flash in a custom recovery for any version of KitKat you want to root. If you have not already checked look at my thread http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 I changed the rooting instructions. Enjoy !!!
So is it possible to flash nc5 nh7 or nk4 tars at any time . I'm on nk4 full firmware and baseband .. just wanna make sure .. THNX FOR THIS INFO
chico260 said:
So is it possible to flash nc5 nh7 or nk4 tars at any time . I'm on nk4 full firmware and baseband .. just wanna make sure .. THNX FOR THIS INFO
Click to expand...
Click to collapse
Yes, I have done it many times now. As I stated above just be aware that a bootloop can occur going back to NC5 from NH7 or NK4. Don't Panic just follow the instructions above and it's smooth sailing. Besides the info above you can check out my flashing thread here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
jimzweb1 said:
Yes, I have done it many times now. As I stated above just be aware that a bootloop can occur going back to NC5 from NH7 or NK4. Don't Panic just follow the instructions above and it's smooth sailing. Besides the info above you can check out my flashing thread here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Click to expand...
Click to collapse
Also will the one click work going from nk4 to nc5?
Im on NH7 modem and baseband and im trying to go to Nk4 modem but I get this error on Odin 3.07
EDIT: I got it
Jocutz1987 said:
Im on NH7 modem and baseband and im trying to go to Nk4 modem but I get this error on Odin 3.07
EDIT: I got it
Click to expand...
Click to collapse
You need remove SIM card when fresh the ROM, maybe helpful. Should see all pass here instead of any fail.
have tried safestrap ( says successful, but does not actually let you push "boot to recovery) and CWM. i had safestrap working before, but got a soft brick and had to flash a stock unrooted nk1 build via ODIN. any help is appreciated.
UPDATE:
problem was busybox APK was installed, but not binaries -.-
Note 3 Running Android 5.01 from Sprint.
I've had both OC5 and OH! (I think is the new one from August)
Both Firmware I try to install CWM or TW via ODIN and its unsuccessful. When I try to get into recovery it reverts to some errors while in Downloading.
Most recent attempt I re-installed stock firmware OC5. Ran OTA upgrade to newest firmware. Used CF to root and again ODIN to install CWM. Still same thing.
What am I missing here?
FYI if I use ROM Manager to install CWM it says its successful but can't book into recovery. It will just loop the bootloader so I have to use Odin to reinstall the firmware.
What ver. Of Oden you using?
Originally I used 3.07 but aftrer coming across this issue I've wiped and reinstalled the firmware and tried again using 1.85. Both versions had no luck.
Try Oden 3.10
Missing root. Try to reroot via odin, and try twrp via odin. If no go...put stock via odin and select nand erase. You may get stuxk on sprint logo when boots, go into recovery and do wipe. The reboot stock will load. Then root via odin, and install twrp or cwm via odin. This fixes all my problems...even when i thought phone was dying