Database Users

[Q] Wait... What? Kitkat on V-Note3?

So taking a look around the net today, I came across an article that states that you can flash Kitkat onto N900 (Galaxy Note 3) using Odin... Does/Would this also include the Verizon version of the Note 3? I was under the belief that Verizon's bootloader didn't allow for KitKat installations because of some kernel compatibility issue or something keeping it from working... But would this allow for a Kitkat working install on (non-dev-edition) Ver-Note3? And if so, would this allow lay the groundwork for devs to be able to create install-able kitkat roms for said device? Any and all info/help on this would be greatly appreciated, as I'm sure there's a great deal of want for people with the Verizon Note 3 to be able to have KitKat, myself included!

TToTT said:
So taking a look around the net today, I came across an article that states that you can flash Kitkat onto N900 (Galaxy Note 3) using Odin... Does/Would this also include the Verizon version of the Note 3? I was under the belief that Verizon's bootloader didn't allow for KitKat installations because of some kernel compatibility issue or something keeping it from working... But would this allow for a Kitkat working install on (non-dev-edition) Ver-Note3? And if so, would this allow lay the groundwork for devs to be able to create install-able kitkat roms for said device? Any and all info/help on this would be greatly appreciated, as I'm sure there's a great deal of want for people with the Verizon Note 3 to be able to have KitKat, myself included!
Click to expand...
Click to collapse
This applies to the international version only sm-900 witch has a unlocked bootloader. I'm almost positive someone here tried it and bricked their phone.

[Q] Stable CyanogenMod for Verizon Note 3

I'm very interested in switching from my stock Verizon Note 3 ROM to CyanogenMod, but after a great deal of research I cannot tell with absolute certainty if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizon Note 3. Is it the correct ROM?
Additionally, if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizone Note 3, how do I work around their posted notice as follows? Such as, are there specific instructions for using ODIN?
"If you've applied the 4.4.x update to your hlte device, it is possible heimdall will have communication issues with your device. This is a filed bug already on the heimdall page and this warning will be removed when it is resolved. In the meantime, ODIN still works."​

Karine said:
I'm very interested in switching from my stock Verizon Note 3 ROM to CyanogenMod, but after a great deal of research I cannot tell with absolute certainty if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizon Note 3. Is it the correct ROM?
Additionally, if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizone Note 3, how do I work around their posted notice as follows? Such as, are there specific instructions for using ODIN?
"If you've applied the 4.4.x update to your hlte device, it is possible heimdall will have communication issues with your device. This is a filed bug already on the heimdall page and this warning will be removed when it is resolved. In the meantime, ODIN still works."​
Click to expand...
Click to collapse
If you are on RETAIL VZW N3, there is NO WAY to have anything but a stock or cutsom stock ROM.
If you are on a DEV EDITION VZW N3, check here.

I have the retail Verizon Note 3, and all other resources I've encountered indicate that the link I provided is a universal ROM for all Note 3.

Karine said:
I have the retail Verizon Note 3, and all other resources I've encountered indicate that the link I provided is a universal ROM for all Note 3.
Click to expand...
Click to collapse
That is universal for the international versions, which there are many. Without an unlocked bootloader, we cannot flash aosp, aokp, or cm based roms.

The bootloader issue is what prevents compatibility with the CM installer, but I don't believe it prevents ROM flashes through other means. And I've seen several threads that specifically state that universal covers Sprint, Verizon, etc.

Karine said:
The bootloader issue is what prevents compatibility with the CM installer, but I don't believe it prevents ROM flashes through other means. And I've seen several threads that specifically state that universal covers Sprint, Verizon, etc.
Click to expand...
Click to collapse
Ok. And why isn't this info blowing up the Verizon Note 3 forums? If I'm wrong, I'll admit that. But many smarter people that me have stated time and time again that it's not going to work. And I have seen no information that will lead me to believe otherwise. Can you provide links to where it's being stated we can flash this?

That's why I'm here, to sort whether it will work as all the information available seems unclear and split.

Ok, I got ya. There is info burried here. But as I understand it the ability to install custom roms requires an unlocked bootloader. When we got that leak of kk nc2, we obtained a locked bootloader the had a few "holes" in it (for lack of a better term). With that bootloader, there is the possibility of some exploits that can be applied in order to give us the ability to flash a cm rom amongst other things. But we're not there yet.
Best I can give you is to watch this thread for any news or development:
http://forum.xda-developers.com/showthread.php?t=2812650

Many thanks for the link.

I'm gonna back up Lefty here.
The retail version has a locked bootloader, which means we can't install a custom recovery or an alternate kernel, both of which are required to install non-touchwiz ROMs. (Not the case for the dev edition, which you would know if you had)
This is Verizon's doing. Samsung will provide phones with unlocked bootloaders to cellular companies, but verizon wants them locked down. I believe the only US company that sells bl-unlocked phones is T-Mobile. Lots of international carriers are bl-unlocked.
CM is mostly "universal" across ALL devices, because its based on AOSP straight from Google, and just has to be tweaked slightly for hardware differences. That's why CM builds for a note3 are "universal" -- the hardware is all the same. This comes at a price... last I've heard, the s-pen is just emulated as a mouse input, which is a bastardization of the technology. This is just an example. There are several compromises to running AOSP roms.
Sent from my SM-N900V using Tapatalk

Thanks for the great information. It's a shame that Verizon or anyone else locks the bootloader. It should be no matter to them what ROM I run.

G900V CID 11 Running CyanogenMod 14 - Unable to make phone calls/Use sms

Hi, in an attempt to unlock Wifi Tethering capability on my phone, I installed [G900F]CyanogenMod 14.0-20161020-UNOFFICIAL-klte, and now I'm unable to make phone calls or use SMS/MMS.
Is there anything I can try to get service back?
I've tried installing a new modem with no success, using Odin, FlashFire, Terminal Server. I'm not confident I was doing it correctly though, or even if I was using the correct modem files.
I was able to root the phone with Stock firmware, but Mobile Hotspot/Wifi Tether wasn't built-in, and I had no success with any of the apps... FoxFi, Wifi Tether Router, Barnacle Wifi.
Some more information on the phone:
It's the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V. I took it to the Verizon MVNO PagePlus and they were able to activate the phone, and everything was working perfect, until installing CM14.0.
A roadblock I found out, that might be the root of some of the problems, is the phone may not have the ability to unlock the bootloader, possibly limiting some modding methods. When looking at /sys/block/mmcblk0/device/cid, it starts with 11, designating a Toshiba eMMC chip.
I'll take any suggestions, or alternatives... I don't mind using the stock firmware or any other Roms. The main feature I'd like to have is the ability to use Wifi Tether and the basics, make calls, send sms.
Thank you.

I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?

leotakacs said:
I know this is off topic, but how in the world did you get CM14 running on G900V-CID11?
Click to expand...
Click to collapse
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.

You will not be able to run any version of Cyanogen on your Toshiba S5 properly. Your best course would be to install FlashFire from the play store and use it to install a TouchWiz ROM such as Moar (5.0) or Phoenix (6.0).

TechFellow1 said:
I'm not entirely sure, but someone had an idea they mentioned to me, that it might've been possible to get CM installed from a very outdated Android version, from before CID 11 was locked. The previous stock Android version the phone came installed with was 4.4.2. It was the StraightTalk variant made for TotalWireless MVNO. The phone's Stock firmware said it was the S902L Samsung S5 variant, but under the battery FCC ID of the device is actually just a G900V.
Click to expand...
Click to collapse
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip

Hariiiii said:
no, no, no. don't listen to any of these other people. if your phone boots CM14 then your bootloader is unlocked. this has nothing to do with bootloaders. you installed the wrong ROM for your phone. CM14-kltevzw is the correct variant for your phone, not CM14-klte.
see here:
https://archive.org/download/cmarchive_nighlies/cm-14.1-20161225-NIGHTLY-kltevzw.zip
Click to expand...
Click to collapse
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?

leotakacs said:
He said his phone has a CID11 Toshiba chip. @OP, are you positive you have a Toshiba chip (11)?
Click to expand...
Click to collapse
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.

Hariiiii said:
It doesn't matter. He is on a straight talk phone. The bootloader is unlocked by default. The firmware is different.
Click to expand...
Click to collapse
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol

KaptinBoxxi said:
generally correct. best way to know would be to take a cid 11 based device, and flash twrp same way you would cid 15.
as far as i know though, most straight talk phones i see at work that i've repaired software wise have had unlocked bootloaders... which makes recovering/backing up files a breeze lol
Click to expand...
Click to collapse
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.

TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?

TechFellow1 said:
I think that is correct. Here's the final solution I came up with and everything's working perfectly now.
I flashed the kltevzw 14 version with TWRP and had no luck getting service, then I tried flashing the kitkat factory ROM with ODIN to see if that would fix it, but ODIN failed after many attempts. Finally I flashed with the lower but stable release kltevzw CM13, instead of the nightly, and everything worked again. I'm thinking I must be extremely lucky to have gotten a Straight Talk S5 variant with an unlocked bootloader, but it's interesting that even though my CID definitely starts with 11, the bootloader is unlocked. Not all hope is lost on CID 11 S5's.
Click to expand...
Click to collapse
Delgoth said:
Are you able to dump your boot and bootloader partitions somehow? The "dd" command from adb shell somehow?
Couldnt we just use a diff program to compare yours with one of the Locked 11's?
Click to expand...
Click to collapse
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.

Hariiiii said:
No, all hope IS lost on CID 11's. You have a different phone provided by a different company. It is loaded with a different software and hardware configuration. There is no bootloader signature verification. Yes, the configuration is very similar to that of a G900V, but the bootloader comes unlocked. This is phone specific. This has no value for an actual G900V.
Click to expand...
Click to collapse
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively

KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).

Hariiiii said:
I say this because I have tried it and I know how it works. A bootloader needs to have the right signature that is recognized by the hardware. The reason the dev edition bootloader works on non dev edition is because they are the same phone, but with different bootloaders installed. The signature of the straight talk bootloader will not be recognized by the G900V hardware. Again, I have confirmed this personally. The straight talk is almost the same hardware as the verizon G900V, but it does not have bootloader signature verification enabled (and the bootloader that comes installed is unsecured).
Click to expand...
Click to collapse
alright, that makes sense. Thanks for explaining. Always interested in these things since i don't QUITE understand exploits at that level. I do mainly apk modifications and software dev

KaptinBoxxi said:
well if that's correct, then why does the dev edition bootloader work on the non-dev edition? Sure, its still a g900v, but never hurts to find a way and try
a little optimism can go a long way in life. don't think so negatively
Click to expand...
Click to collapse
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD

Legitsu said:
because you don't have a clue about how the CID exploit works
the reason you can flash the dev aboot on a CID15 is because you can change the CID to match that of a dev edtion aboot checks the CID to see if a device as a dev edtion or not
the CID is a sort of serial number for the flash-chip and normally its write once and then read only value ,but because samsung was sloppy we can use some custom Samsung NAND vendor commands to change it so secure-boot thinks you have a dev editon and permits the flashing of a unsigned image
this is flat not possible on CID11 devices(toshiba NAND) there is no hope for cid11 devices with this method the commands needed simply do not exist PERIOD
Click to expand...
Click to collapse
I understand plenty enough to know the difference in the flash chips cid's with such like that... The fact of the matter i was trying to get at is that most Straight Talk phones are unlocked entirely without a care in the world, regardless of their CID/branding. Without the proper commands and 3rd party support, I get that there won't be a way. That's why I check my CID's first before buying S5's or Note 4's

S5 AT&T help

Hello guys, I'm posting this for first time.
My girlfriend is having a Samsung S5 from AT&T and I want to root it as she told me system apps from AT&T are taking too much space on her phone and so I was thinking can I flash any custom rom on it?
As I see the AT&T thread separate, I want to ask some things
Does Network provider has to do something with it ?
I can flash custom rom on her phone or not?
And same odin thing works ? Like unlocking bootloader and fishing custom recovery
I have never rooted any Samsung phone ever
I'm having a oneplus and HTC.
If anyone can tell me what all do I need to do, I would appreciate it a lot .

Att version has locked bootloader .... Root is possible and there a few roms but they are all based off the stock rom just tweaked a bit ...

cpt.macp said:
Hello guys, I'm posting this for first time.
My girlfriend is having a Samsung S5 from AT&T and I want to root it as she told me system apps from AT&T are taking too much space on her phone and so I was thinking can I flash any custom rom on it?
As I see the AT&T thread separate, I want to ask some things
Does Network provider has to do something with it ?
I can flash custom rom on her phone or not?
And same odin thing works ? Like unlocking bootloader and fishing custom recovery
I have never rooted any Samsung phone ever
I'm having a oneplus and HTC.
If anyone can tell me what all do I need to do, I would appreciate it a lot .
Click to expand...
Click to collapse
You should consider two things:
1. ATT phone may be sim-locked (locked to their network), but it has nothing to do with custom firmware. This problem may be solved more or less easily.
2. ATT phone (SM-G900A) does have a locked bootloader. This is a real problem.
That's why you're limited to touchwiz-based ROMs and stock kernels.
This means, in it's turn, that you cannot have root on 6.0 and above, you cannot have custom recovery, LOS, etc.
If it was my device and I was going to use it as a smartphone (to communicate with others) on a GSM network, I'd install this ROM in unrooted variant and the latest firmware (boot, modem, kernel).

bbsc said:
You should consider two things:
1. ATT phone may be sim-locked (locked to their network), but it has nothing to do with custom firmware. This problem may be solved more or less easily.
2. ATT phone (SM-G900A) does have a locked bootloader. This is a real problem.
That's why you're limited to touchwiz-based ROMs and stock kernels.
This means, in it's turn, that you cannot have root on 6.0 and above, you cannot have custom recovery, LOS, etc.
If it was my device and I was going to use it as a smartphone (to communicate with others) on a GSM network, I'd install this ROM in unrooted variant and the latest firmware (boot, modem, kernel).
Click to expand...
Click to collapse
It's been over 2 years for her phone, unlocking bootloader won't be an issue ( we can unlock it right?) . And she will be using AT&T only because she is using family plan.
If you dare saying the real problem is locked bootloader then we can just unlock it , or I understood it wrong

cpt.macp said:
It's been over 2 years for her phone, unlocking bootloader won't be an issue ( we can unlock it right?) . And she will be using AT&T only because she is using family plan. If you dare saying the real problem is locked bootloader then we can just unlock it , or I understood it wrong
Click to expand...
Click to collapse
I believe that the following thread may help you out with this. It's S5 AT&T device specific.
https://forum.xda-developers.com/showthread.php?t=3516196
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Upgrade confusion. Note 3, N900A stock to 7

Trying to update my Note 3 to android 7 but running in circles.
Progress:
Downgrade from 5.0 to 4.5
Rooted device
Uploaded rom to SD card*
Boot recovery mode, select ROM file
Run install
This is where I keep going in circle.
It keeps telling me cannot verify file, verification failed. (does this twice)
Then says update successful, wipe data, format etc.
Reboots back to same old V4.2 again and of course the apps I installed to work on phone gone and have to re-register with Play store to get them back.
How do I solve the error "Unable to verify file"
( also is there a way to stop it wiping data every time if it has failed to update anyway?)
*ROM
lineage-14.1-20180110-nightly-hlte-signed.zip ( this may be wrong rom but the names are often confusing me because the links in upgrade note 3 take me to that rom among others so I assume it is for a note 3)
Any help pin pointing the ACTUAL, CORRECT ROM welcome.
Specs:
Samsung Galaxy Note 3
Qualcom MSM 8974
Snapdragon 800 / 2.27GHZ 4 core cpu.
krait 400
r2p0
Pre-downgrade V 5.0
AP N900AUCSE0C3
CP N900AUCSE0C3
CSC N900AATTE0C3
Below current after downgrade
AP: N900AUCUCNC2
CP: N900AUCUCNC2
CSC: N900AATTCNC2
Bootloader: N900AUCUCNC2

Step one
Post in the forum for your model .This is note AT&T forum .
Phone has locked bootloader .
Links to forum or at the bottom of this forum.
https://forum.xda-developers.com/showthread.php?t=2574886

JJEgan said:
Step one
Post in the forum for your model .This is note AT&T forum .
Phone has locked bootloader .
Links to forum or at the bottom of this forum.
https://forum.xda-developers.com/showthread.php?t=2574886
Click to expand...
Click to collapse
What am I looking for on that post? I have phone rooted.

The AT&T Note 3 sm-n900a has a locked boot loader and can only run custom ROMs created from a stock Samsung lollipop ROM.

Update:
It was my understanding (perhaps wrong) that Safestrap was a way to work around the locked bootloader (ATT) The video on the main topic on this talks about a Verizon phone even though the topic is specific to the ATT note 3. Are they identical with regard to Safestrap etc?
As of now I have Safestrap installed and working. Boots with open lock/Custom on boot screen.
My confusion arises from conflicting videos at YouTube one suggesting Safestrap won't install a custom ROM followed by another that says it will?!?
If it won't exactly what is the purpose of even installing Safestrap if you are still stuck with the exact same android version and all the ATT bloat?
-edit-
FYI currently phone no SIM not provisioned but was used on ATT then switched T_Mobile service (consumer cellular so I can switch between those two. ATT and T-Mobile service suck here but at least with T-Mobile I have WiFi calling on my J2 which avoids poor signal issue at home. Hoping to move back to Note 3 if a good update can make it Wifi Calling enabled )
So far the only reply here has been to tell my my bootloader is locked. Since instructions include using Safestrap as a work around that really does not help me.
At the start the guide was to upgrade the phone to Android 7. Things seem to break down for my understanding of all this if the only work around is Safestrap and if that cannot install a custom ROM how do I get from here to 7/Nougat?
SIDE QUESTION but important.
Having downgraded from 5.0 to root device, I am not getting a request to accept update from ATT ( back to 5.0 I assume ) which I deferred for now. The question regarding this is, if I permit the ATT push back to 5.0 on my rooted device will I lose that root access and have to start all over again? (Darn I don't want that)
Sigh...so confused.

EDIT
I'm reposting an edit to last because I can't figure out how to get the edit/addition to appear. LOL
-edit-
FYI currently phone no SIM not provisioned but was used on ATT then switched T_Mobile service (consumer cellular so I can switch between those two. ATT and T-Mobile service suck here but at least with T-Mobile I have WiFi calling on my J2 which avoids poor signal issue at home. Hoping to move back to Note 3 if a good update can make it Wifi Calling enabled )

ROMS
audit13 said:
The AT&T Note 3 sm-n900a has a locked boot loader and can only run custom ROMs created from a stock Samsung lollipop ROM.
Click to expand...
Click to collapse
So the whole topic of upgrading Note 3 to V.7 is a dead end? I'm stuck with a phone downgraded to KitKat from 5.0 after having rooted etc? Will a custom ROM for lollipop let me delete bloat then upgrade to Nougat?
The whole topic of upgrade to v.7 for note 3 is confusing because after two days of reading and trying options I seem to get no where and cannot even find a definitive answer regarding actually upgrading this phone?

There are no nougat ROMs for the n900a.
Safestrap is only good for certain roms and twrp can't be installed on an n900a with a locked bootloader.

Useless phone?
audit13 said:
There are no nougat ROMs for the n900a.
Safestrap is only good for certain roms and twrp can't be installed on an n900a with a locked bootloader.
Click to expand...
Click to collapse
Okay so I wish the whole topic on installing V7 on Note three just started saying if you have an ATT Note 3
READ NO MORE, all hope is lost!
I read numerous posts on numerous sites telling me I can upgrade this phone and none stated up front ( Does not apply to ATT versions ) leaving me to saving a text file full of instructions, links, a folder of downloaded files etc. all aimed at my N900 phone...none of which is valid.
I guess I will just restore to factory and sell in eBay if it is a useless phone other than to put on ATT or T Mobile as a plain old phone full of bloatware.
That or just load my music library on it and bluetooth it to my stereo as a juke box.
*sigh*

You are on the wrong forum.
Ask your question In the AT&T forum.

update
JJEgan said:
You are on the wrong forum.
Ask your question In the AT&T forum.
Click to expand...
Click to collapse
Actually I believe I posted this topic under the forum for the phone in question, Note 3? I was inquiring about the actual device not about ATT per-se.

how about a link?
JJEgan said:
You are on the wrong forum.
Ask your question In the AT&T forum.
Click to expand...
Click to collapse
How about a link...cannot find such forum.
Search gives me a google result all over the web.
ALL FORMS gives me hundred of specific phone models but did not find a forum for AT&T here?

paulckruger said:
Actually I believe I posted this topic under the forum for the phone in question, Note 3? I was inquiring about the actual device not about ATT per-se.
Click to expand...
Click to collapse
As AT&T has a locked bootloader it has little relevance to Note 3 International model.
---------- Post added at 07:04 PM ---------- Previous post was at 07:02 PM ----------
paulckruger said:
How about a link...cannot find such forum.
https://forum.xda-developers.com/galaxy-note-3
Bottom of the page or the link i posted earlier .
OR Direct link ,
https://forum.xda-developers.com/note-3-att
Click to expand...
Click to collapse

update
JJEgan said:
As AT&T has a locked bootloader it has little relevance to Note 3 International model.
Click to expand...
Click to collapse
So if I obtain an international GSM version I should be able to update ROM?

I don't think the international version supports LTE in North America.