I'm pretty new to all this, I had a Rogers Captivate that had been crashing on me. Everything suggests that if I changed my software it would work.
So I managed to to flash a newer AT&T ROM on to the phone via Odin. (I was pretty chuffed with myself)
However, as soon as I put my sim into it, it became locked. I paid an online service to get an unlock code, but the IMEI number I delivered to them didn't match the network, so I messed that up.
Now I've noticed that I could flash a rooted ROM via Odin, which should save me having to unlock, right ?
I went to the thread http://forum.xda-developers.com/showthread.php?t=1621350 and looked for a suitable ROM (preferably supported).
I went for the PAC ROM, but noticed there is no tar file in the download.
The other ones I wanted to try either suggested it was flashed by another method than Odin (I might be wrong) or the download links for the files themselves were no longer working.
Also, there is talk about Gapps. What is this and what is the process for installing it ?
Thanks in advance for any help you can give me.
Hi there,
You'll need to specify that the phone is still on the Rogers network, as that's how they access the database. Ie., if you have a phone that was supplied to Rogers, the IMEI will be associated with Rogers and if you tell them it's ATT, they won't be able to find it - regardless of what ROM you're running.
Unfortunately, as far as I'm aware you do have to pay to unlock the ROM again but I'm not an expert on this - I know that I had the same problem you did and they told me to put it in as Rogers instead - that got me my unlock code.
I have a rooted Milestone 2 which is running JB now, and it is still operator locked unfortunately.
Apparently the GalaxSim Unlock tool is good but I don't know if it retains your IMEI - I know it does back up your EFS though. Maybe it's worth a try?
Before doing anything with your IMEI i suggest you to backup your efs folder. There's a software for this too.
[sent from my awesome Samsung Captivate Glide]
[AT&T rooted stock ROM]
thank you
Thanks for the feedback, I've reapplied for my unlock code.
What I'd really like to know now is which rooted ROM should I choose to flash via Odin ?
pardoning edeaoh
hkcharlie said:
Thanks for the feedback, I've reapplied for my unlock code.
What I'd really like to know now is which rooted ROM should I choose to flash via Odin ?
Click to expand...
Click to collapse
Hi hkcharlie,
Have a look at the below thread to unlock your sim card. I used it on mine and my friend's S3.
http://forum.xda-developers.com/showthread.php?t=1846451
I suggest reading the "everything about captivate glide" thread here:
http://forum.xda-developers.com/showthread.php?t=1621350
I use CWMR (ClockWork Mod Recovery) from this post:
http://forum.xda-developers.com/showthread.php?t=1458153
You have to flash this acording to ODIN. Afterwards, you can download .zip files directly to your device for flashing, or download them on your computer and copy them to the devices SD card. Select them in recovery mode and they will install.
These two roms I've had a lot of success with:
http://forum.xda-developers.com/showthread.php?t=1945558
http://forum.xda-developers.com/showthread.php?t=2021374
They're both ICS. There is a cm10.1 JB (4.2.2) build as well, and it's *awesome* - but it is missing a few critical features so I won't recommend it for your first time.
Almost any ROM you flash from this forum will already be rooted. Being 'rooted' just means having a kernel that supports it (both ICS rom's above include a root-capable kernel) and a /bin/su and appropriate superuser apk.
Of course, back up your EFS - there are some apps on the market that will help you do this. And backup everything. And test your backup. And your warranty is void, your phone may explode, or impregnate you with mogwai. (do not get wet, do not feed after midnight.)
Happy flashing!
I have a sprint galaxy note 2 that I bought on eBay and had it flashed to boostmobile the phone is working fine but I want to get rid of the little green circle with a check mark that says it's trying to do a hands free activation I want to know if it is possible to remove it.....someone please help
You need to be rooted then use a root explorer program navigate to system/app and rename Sprint DM apk....just add ".bak" or something to the ".apk" then reboot
Or, if you want to completely solve it, there's a guide out there by garwynn.
http://forums.androidcentral.com/sa...-activation-errors-chameleon-fcs-ljc-lk8.html
You're going to need to know how to use Odin, your device is going to have to be rooted, and it's also going to have to have a custom recovery. IIRC, you need to downgrade to an earlier version of an L900 firmware (such as LJC) and flash the appropriate fix in TWRP/CWM. NOW, if you're flashed, FLASH THE DEVICE ON THE EARLIER FIRMWARE. If you load the earlier firmware, apply the patch, update to the latest version, and try to flash, you'll run into the same problem. If you load the earlier firmware, flash, apply the patch (and make sure everything is OK), and update to the latest version of Android you won't get Chameleon errors and Hands Free Activation loops.
Happy hunting.
I'm really frustrated. I've been trying to update this Galaxy S3 for days now with no success. Currently I am running on Slimkat 7.0. It's sometimes slow and buggy and needs some updating.
For reference, this is the phone at its current state:
- Bootloader: i747ucalh9 (literally taken from the fail message when trying to update to any other bootloader)
- Modem/firmware (?): I747UCLH9
Here's what has happened, greatly summarized (note I'm using CM6.0.4.7 for all of these operations, and when I say "update", I mean "flash"):
- I tried updating to Slimkat 9 but received no signal. I gave up on it entirely for a while
- I tried installing various LP ROMs, including CM12.1.
- I had 12.1 running for a bit, but I had no connectivity. LTE, 3G,H+ nothing.
- I tried installing a newer modem (this thread. Finally at MJB, I could actually get connectivity in some of the newer ROMs (including Slimkat 9)... but it was very erratic. It would just randomly oscillate between LTE and 3G and H+. This also broke CM12.1 entirely.
- Again, the above problem was always present. Most of the LP ROMs would just bootloop me, though. The only one that worked was Cyanide L... which I didn't really like.
- I thought maybe the issue was the bootloader. My bootloader is still i747ucalh9. So I tried updating it to various bootloaders from here, but none of the updates will work. Literally, they give me error 6 or 7 and pretty much essentially tell me that I can't do it.
- So after repeating the cycle of "let me try to update this" several times and having the update fail on me, I'm still stuck at Slimkat 7 as the only thing that worked on LTE (note the past tense). Worse yet, I tried simply downgrading my modem to match my current bootloader version, but that made things worse than better. I am now stuck at 3G... which just recently went back to LTE. Talk about erratic.
- I also tried going full stock by flashing this: http://forum.xda-developers.com/showthread.php?t=2363882 But it expects 5 arguments for format, and got 3... or something. Failed hard.
So, I'm pretty much at the end of my rope here. I really might just go and grab a new phone at this point. I just really don't want to because this thing still works fine.... I guess I got unlucky and am at a version of the bootloader that is difficult to update from. I can't seem to go anywhere with this thing. Anyone have any ideas? Do I need to use a different recovery?
Thanks...
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
jason2678 said:
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help! I actually did/tried a majority of this an hour or two before you posted that, except the latest firmware update link you supplied. I knew it existed and I had seen that thread before, but I couldn't dig up the link again before I had to go to work. Thing is I kind of wanted to avoid Odin for some reason but I finally gave up and used it. And yeah I already knew my bootloader version. The phone told me when it failed to update the bootloader lol.
Here's what happened thus far:
- I used Odin to flash the sammobile 4.1.1. The flashing worked just fine, but booting into it did not. It hung on the Samsung logo. So, OTA updates were out the window.
- I have no idea why, so I just used Odin to flash TWRP onto it afterwards (from here)
- I tried one of the ROMS. Data still didn't work.
- I used the thread you linked to update to MJB bootloader and whatnot. The update went fine.
- Tried another few ROMs. Data worked, but LTE was still erratic.
- Updated to NE4 and then grabbed the deoxed stock ROM.
- The deoxed stock rom failed to boot (stuck at ATT globe logo). For some reason my phone can't use stock ROMs.
- So again used Odin to put TWRP onto the phone
- Installed various LP ROMS. Again the data was erratic and plus the battery life was horrid.
- Tried getting the ktoonsez kernel. My service was murdered.
- Gave up on LP. Tried Slim 9.0. Erratic data.
- Tried Liquidsmooth 4.4.4 instead.
Currently that's kind of where I'm at. The LTE data works fine (takes a bit to get up and running after reboot though) and thus far everything is okay (though that can quickly change considering I haven't done much of anything), so I don't even know if I want to mess with it anymore. It looks like this specific ROM includes a custom kernel. So I'm guessing it's an incompatibility between the kernel and the firmware version on the other ROMs. It seems like most of the LP roms have horrible battery life (back of my phone feels like a furnace on them), so I'm not even sure if I want to do that last firmware update to use them.
It'd be kind of nice to use the OTA but apparently my ability to go stock in any form or fashion is just totally borked.
Thanks for the post though, that's pretty gold. I'm sure someone in a situation like me where they have a super old firmware will find this thread of some use as it has actual instructions and links to what you need to do to get up and running. Before you posted that, I had to go digging around pretty much everywhere figuring out what and where was going wrong.
Glad you've got it mostly working.
You might have been able to get that stock ROM to boot if you had booted into the stock recovery and run a full wipe. Touchwiz ROMs can be tough to get running after being on AOSP. As a general progression try to format internal storage with TWRP (the wipe where you have to type "yes" to confirm), if that doesn't work try a wipe with Philz, and if that doesn't work nothing, not even Odin, is effective as a wipe in the stock recovery.
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Yep. You've got it. If you're on the latest and greatest firmware I think the towelroot exploit has been patched, unless geohot has retaken the lead in that arms race.
Easiest way to root on this phone since the bootloaders are unlocked is to just use Odin to flash a custom recovery then use the custom recovery to flash SuperSU. There's just a little trick to it. Store SuperSU.zip somewhere on your phone before flashing the custom recovery. Uncheck everything but f.reset time when you use Odin; don't let it auto reboot. Upon success pull battery. Replace battery and boot straight into recovery with vol up + home + power. If you mess up and boot into unrooted stock ROM with a custom recovery it will get overwritten with a stock recovery and you'll have to Odin custom recovery back onto it and try again.
I would do this to root your stock ROM just to execute this command in a terminal app or adb shell before any more serious flashing:
Code:
su
reboot nvbackup
That fixes a derp and gives you a working efs backup on a few backup partitions built into your phone instead of a blank one. Highly recommended before doing any ROM flashing. This will just look like a pretty normal reboot. You might see a quick flash of tiny blue text if you're watching for it.
Then you're ready to make a nandroid backup (just in case), wipe, and flash away. Take a look at LiquidSmooth if you're looking for a good lollipop ROM.
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Thanks for the suggestion on the ROM but I think I'll stick to official cm12.1 it's not my phone and that should be a nice readily updatable bland flavor of lollipop.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Click to expand...
Click to collapse
At the Android 4.3 update it was noticed that flashing a custom recovery would be overwritten by the stock recovery on the initial reboot unless following the method Jason described. Another solution was to delete two lib or .so files. On devices still on stock recovery, stock recovery does not overwrite itself.
There is a blank EFS partition on the device intended for a backup. The nvbackup command populates that partition with an image which will rebuild your EFS if it is lost during a modem update or ROM flash. The loss of EFS does happen. I believe wanam, of the xposed module fame, created an EFS backup tool for Samsung devices. I don't believe he updates it any longer because he rolled the functionality into a partition backup tool, the later is in the PlayStore listed under a different creator name, yet it's still him.
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
coolwhipp420 said:
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
Click to expand...
Click to collapse
Since you are on LK3 you may want to considr applying the free sim/carrier unlock method before upgrading; that is if you are on stock LK3 and you have not previously carrier unlocked your device.
There was an OTA release for the MG2 stock ROM, I believe that was 4.1.2. You may want to go to that before MJB. Did you make the nvbackup suggested by Jason?
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
There is a command to manually trigger the restore routine. I think it's
Code:
reboot nvrestore
but don't hold me to that. I'd never execute that command except if in dire need. The problem with this phone is there is an automatic routine that can be triggered in the event of a bad flash that will overwrite your nvram with the backup, even if the backup is blank. I don't think the backup stores anything modem specific, but I've never been able to confirm that. So I've always done it again after updating modems (only had to once).
Having the phone sim unlocked can be nice if you plan on traveling internationally. Otherwise, potential future carrier hopping or added resale value are the only reasons to do it.
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
If you will never be switching carriers, nor ever sell/give/trade the phone to someone who will switch, then it is an unecessary step to do the carrier unlock.
I see Jason beat me to answering both of your questions.
I thought I'd put together a basic survey to possibly help others with their Unlocking/rooting questions.
Please only answer if you have successfully completed the steps and have your bootloader unlocked and phone rooted based on information provided by THIS thread. If you don't currently own a Verizon Retail Note 4, respectfully, PLEASE DO NOT post a reply. Thank you.
If you reply, it is assumed that you have completed the process and have successfully turned your Retail Phone into a Developer Phone. If you are still "tinkering" with your phone after the conversion process, feel free to reply and update your reply as needed, to help others.
Before you began:
Your Android Version?
Your build number?
Did you Odin or Flash to get the above Build Number?
What version of KingRoot did you use to Temp Root your phone?
After Converting to Developer Mode/Rooting (Some questions - If Applicable):
SINCE converting, what Android Version/Build Number have you upgraded from/to? Was the upgrade via OTA or Odin?
What confirmed working root apps are you running (other than Root Checker)?
What have you installed onto your phone that requires an unlocked bootloader that are confirmed to be working?
Has this process changed (made better or worse) how your phone reads extended batteries? State which external batteries you have tested, since the root process was made available this week.
Here's my experience.
STARTED WITH:
Your Android Version? 5.0.1
Your build number? BOG5 Safe Upgrade
DOWNGRADED TO (Because I thought I had to which might've been a mistake)
Your Android Version? 4.4.4
Your build number? ANJ5
Flashed via Odin 3.10.7
Results: After starting the HOWTO Guide on converting from Retail to Developer Mode, I got stuck on THIS step, which gave me an error message
Code:
./samsung_unlock_n4-2
Later, I was told that others had reported issues trying to convert from KK. I then took the Safe Upgrade to BP1. Be sure that you are installing the RETAIL version of the ROM, not the Developer Version. You are not there, yet.
Once you are on BP1, download eMMC Brickbug Check from the Play Store. Verify that your CID begins with 15 followed by a bunch of random numbers. Then, follow the steps on the HOWTO Guide on converting your Retail phone to Developer.
After you do this:
Boot to Download Mode (VOLUME DOWN+HOME+POWER) and flash TWRP 2.8.5 recovery via Odin
If you haven't, already, get your MicroSD card, plug it into your computer and load SuperUser and the kernel (see this reply) onto it. Put it back into your phone
Boot to TWRP recovery (VOLUME UP+HOME+POWER)
Install the two files you just loaded
I this point in time, you SHOULD have BPA, Developer Mode AND root.
With that said........
Your Android Version? 5.0.1
Your build number? BP1
Flashed via Odin 3.10.7
What version of KingRoot did you use to Temp Root your phone? KingRoot 4.8.5
Rather than answer my own questions, I'll just state what so far does work that I've tried:
I've installed CM13 via TWRP. I currently do not have root, but that's about to change.
Before you began:
4.4.4
ANJ5
Don't remember
4.8.5
After rooting:
(If applicable) Have you taken an OTA or Flashed via Odin to a more updated build number? If so, what build number?
Upgrade to 5.0.1 N910VVRU2BOG5_StockRestore.tar.md5 using Odin.
Followed directions to unlock Developer mode.
Flashed N910VVRU2BPA1_StockRestore.tar.md5 to get 5.1.1 through Odin.
Reflashed TWRP and rebooted.
copied MultiSystem-Kernel_LP-5.1.1.zip, BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip, and xposed-v75-sdk21-arm-arter97-snapdragon.zip to phone and flashed them through TWRP. Wiped cache and Davlik cache. Rebooted.
(If applicable) What confirmed working root apps are you running (other than Root Checker)?
Titanium Backup, SD Maid, Xposed Framework, TWRP Manager, Call Recorder, BusyBox Free.
(If applicable) What have you installed onto your phone that requires an unlocked bootloader that are confirmed to be working?
You couldn't install TWRP without an unlocked bootloader, so...
(If applicable) Has this process changed (made better or worse) how your phone reads extended batteries? State which external batteries you have tested, since the root process was made available this week.
Haven't tested yet, but I think the MultiSystem-Kernel_LP-5.1.1.zip and screen auto brightness settings are draining battery less. Too soon to tell.
So I followed a tutorial to unlock bootloader and root the Note 4 from Verizon (SM-N910V). First off I am gong to say that it was definitely challenging and time consuming. Mainly due to the inconsistencies in the tutorials. You got a few that claim it's unstable or that something wasn't mentioned or left out... Which is true. I not only encountered the lags and freezing, but also the "reboot cycle", that occured after the first round of unlocking bootloader. Now I am not trying to claim that I am better or that the authors are dumb, because as difficult as this "hobby", everyone has their own an unique style...
I was able to unlock bootloader and flash TWRP recovery, but was unable to flash any CF-AutoRoot, SuperUser, or any custom Rom. Along with that any "Stock" firmware I downloaded and tried to flash via ODIN or through TWRP was unsuccessful. Thankfully to persistence and a lot of research I was able to find a workable set of Firmware files on none other than an XDA_Forum.
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
The above link contains the necessary files required for any unfortunates that may occur while unlocking/rooting note 4. I used ODIN to flash files in this order. Recovery image, kernel image, and then Firmware image... I did download Modem file but was not needed as the Firmware image already contained it. NONE!!! I repeat... NONE of this was done through TWRP, once you flash the recovery image TWRP recovery is over-written and the familiar Android Factory Recovery System is now in place. Also I would like to note that I onriginally started with 5.1.1, the image/tar files I flashed are 6.0.1. I know for a fact that just like any upgrade, while you do have some bugs and fixes... it is doable and actually lesser of a headache than one might guess.
Ayways I hope that the information I have provided was helpful and beneficial to SOMEONE out there in the world... GOOD LUCK EVERYONE!!!