Nc5 to nk4 - Sprint Samsung Galaxy Note 3

Nc5 to nk4 - Sprint Samsung Galaxy Note 3

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.

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.

Related

HELP

I was originally on MK2 and decided to take the upgrade + root to NC2. After missing Hyperdrive for some time I downgraded back to MK2 via Surge's method and flashed Hyperdrive. I then upgraded to NC5 from Surge's instructions and everything worked well. Today I flashed through SS 3.72 the dark themed play store in the theme and apps section and my wifi stopped working. I edited the build prop to try and fix it but that did not work. So I rebooted and entered SS 3.72, wiped data/cache/dalvik cache, and restored a backup of NC5 to regain wifi. It failed because it couldn't mount the system? And now I am stuck in safestrap.....I tried to do the uprgrade to NC5 again but it went into a bootloop. And I don't have the files on my sd card to downgrade to MK2. The only thing I can think of to do now is to odin to stock unrooted NC5, downgrade back to MK2 and then upgrade to NC5....any suggestions?
Edit: Flashed stock unrooted NC5 successfully in odin

Reply
falalalala said:
I was originally on MK2 and decided to take the upgrade + root to NC2. After missing Hyperdrive for some time I downgraded back to MK2 via Surge's method and flashed Hyperdrive. I then upgraded to NC5 from Surge's instructions and everything worked well. Today I flashed through SS 3.72 the dark themed play store in the theme and apps section and my wifi stopped working. I edited the build prop to try and fix it but that did not work. So I rebooted and entered SS 3.72, wiped data/cache/dalvik cache, and restored a backup of NC5 to regain wifi. It failed because it couldn't mount the system? And now I am stuck in safestrap.....I tried to do the uprgrade to NC5 again but it went into a bootloop. And I don't have the files on my sd card to downgrade to MK2. The only thing I can think of to do now is to odin to stock unrooted NC5, downgrade back to MK2 and then upgrade to NC5....any suggestions?
Edit: Flashed stock unrooted NC5 successfully in odin
Click to expand...
Click to collapse
I would definitely go for a full wipe if it cannot mount the system properly. Here is the link:
http://forum.xda-developers.com/showthread.php?t=2578209

mcbeat257 said:
I would definitely go for a full wipe if it cannot mount the system properly. Here is the link:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
Thank you!
Sent from my SCH-I545 using Tapatalk

[Q] safestrap 4.3 update to RLS15 gone wrong

Ok so i rooted my Me7 sch-1545 on 4.3 and installed Synergy rom with safestrap when it 1st released last fall (or whenever it was)
was moderately satisfied with this rom but by now i assumed there where better options so i decided on hyperdrive rls15.
so basically im an idiot and decided to operate off of what i remembered of how to flash a rom instead of reading anything (genius right?).
downloaded
Safestrap-JFLTEVZW-3.70-B01.apk from xda installed and then installed the updated recovery via app
rebooted opened safestrap recovery went though to system reboot and restarted my phone.
then proceeded to download
Hyperdrive RLS15 S4.zip
moved the zip to ext sd card then booted into recovery
so right here is where im pretty sure i bricked my phone :laugh::good:
selected install in recovery, selected the rls15 zip and drumroll.... selected the STOCK rom slot
went though the hyperdrive setup deleted cache and dalvik selected a few different options mostly left it as what was already checked.
agreed to terms etc and proceeded to install it everything was working well installation completed
selected to reboot
"samsung s4 splash screen"
then blackscreen with a "pulsating" dimming and brightening blue light left it like this for 20 minutes as it stated could take an extended amount of time on first boot
with no option of booting back into safestrap at any point
so after that wasnt doing anything opted to try out the stock recovery power home vol up
this method immediately takes me to odin mode
Odin mode
product name:sch 1545
current binary:samsung official
sytem statusfficial
csb-config-lsb: 0x30
write protection enabled
Downloading do not turn off target!!
and cannot access any other options
tldr: sch-1545 me7
flashed rls15 rom to stock rom slot in safestrap recovery
can no longer boot the phone or into safestrap or stock recovery only ODIN mode
So basically is she done for or do i have any options?

download mk2 odin flash. reinstall safestrap and install into a rom slot not stock. it will work just fine

thanks
evilryry said:
download mk2 odin flash. reinstall safestrap and install into a rom slot not stock. it will work just fine
Click to expand...
Click to collapse
trying this out now :victory:

my liege i am bound to thee
evilryry said:
download mk2 odin flash. reinstall safestrap and install into a rom slot not stock. it will work just fine
Click to expand...
Click to collapse
so help
much fix
wow

At my wits end installing CWM on rooted verizon s4 with mdk

So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.

Cwm from rom manager hasn't worked in awhile. Use philz touch if you really want cwm. Or use flashify to get twrp

hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
Like Josh said just use Flashify https://play.google.com/store/apps/details?id=com.cgollner.flashify
It's still updated and works great. To many have had issues with ROM manager or Goo.
Sent from my SCH-I545 using Tapatalk

hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!

sdsurferbob said:
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!
Click to expand...
Click to collapse
Thanks guys. I tried all of this with the flashify. Even started off freshly reinstalling stock Mdk and then rerooting with the same method I mentioned earlier. Installing cwm through flashify. And though I can make and restore a backup of my stock rooted Rom. I get the same errors I've been getting trying to flash a custom Rom. I'll try to post a screenshot of the error I get in can when flashing.

[Q] Software not authorized by VZW

I have a i545 that used towel root on and have tried everything too get a rom on it but to no avail.It takes the rom and on reboot it has the the yellow Verizon not authorized warning used a recovery tar.md5 and unbricked in Odin, What in the world am I doing wrong this has happened 3x my build is 4.4.2 @ NC5 Thanks

try safestrap 3.72 the one for kitkat. install roms on stock side only. you cant use anything for recovery except for safestrap because of our locked bootloader.

Stuck on Downloading screen

Got rooted bu when I went to install a custom recovery , it HAD stock recovery until I tried installing CWM and TWRP. Neither of those worked, AND, I can't get stock recovery back, just the DOWNLOADING screen with the following:
Could not do normal boot (red text)
ODIN Mode (red text)
Product name :SCH-1545
Binary: Samsung Official
System Status: Custom
CSB CONFIG LSB: 0x30
write protection : enable (grey text)
eMMC Burst mode: enabled (grey text)
Suggestions how to correct this, and what recovery SHOULD I be using on this device (I am on build NK4)

You can't install cwm or twrp on nk4. Locked bootloader.
You'll have to Odin back to nc5 (download nc5 stock Odin tar and pit file from surges thread..) and Odin 3.09 or 3.10 and then flash back to nc5 and root with towel root.
Then you need to install safestrap. (Busy box first depending on the version of safestrap)
You may be able to install flash fire but I don't know if it works on kitkat.

Thanks. Got Odin to get back in and do a soft wipe only issue is now i get the android.process.acore has stopped message that pops up immediately after I say OK - can't get past it.
reliant_turbo said:
You can't install cwm or twrp on nk4. Locked bootloader.
You'll have to Odin back to nc5 (download nc5 stock Odin tar and pit file from surges thread..) and Odin 3.09 or 3.10 and then flash back to nc5 and root with towel root.
Then you need to install safestrap. (Busy box first depending on the version of safestrap)
You may be able to install flash fire but I don't know if it works on kitkat.
Click to expand...
Click to collapse

Better Mobile App

welcome