Develop Bugs

Sim unlock?

Hi guys I am running into a delema here ive been searching and searching for a way to unlock this thing.
Im now running latest cwmr and have installed a custom 4.4.2 rom ....came from stock 4.4.2 so I already had a problem with unlocking do the locked bootloader....anyhow I have tried changing the modem via a thread right here in the forum I download all 6 modems he had listed but every time I get installation aborted.
Ill keep searching but am wondering if anyone can give me any pointers.
Thanks, Carl

Shortbus-Driver said:
Hi guys I am running into a delema here ive been searching and searching for a way to unlock this thing.
Im now running latest cwmr and have installed a custom 4.4.2 rom ....came from stock 4.4.2 so I already had a problem with unlocking do the locked bootloader....anyhow I have tried changing the modem via a thread right here in the forum I download all 6 modems he had listed but every time I get installation aborted.
Ill keep searching but am wondering if anyone can give me any pointers.
Thanks, Carl
Click to expand...
Click to collapse
1) the SGHI747 comes with unlocked bootloader. (bricked my first trying to "unlock" it. lol. now anyways).
2) do you know your current bootloader/modem version ?
3) you know this is the att thread , right?
"all i can really do , is stay out of my own way and let the will of heaven be done"

Its running the bootloader for 4.4.2 it was already upgraded to kk all ive done sofar is to root it and flash a custom 4.4.2 rom on it.
Yes its the att s3 its actually a friend of mines phone hes on tmobile but his mother is on att from which he got the phone from.
I had no problems doing this to my note 2 but this s3 seems to be a little bit more finicky

We talked to att customer service just a few minutes ago and they said his mom needs to be the one to fill out the form online which is an option.....but he really needs his phone up now and att csr said it will take another 3-5 days to get the code.....I jist figured I could do it easily and faster lol since i am a flashaholic and unlocked many of the other GS phones

I have found a thread about a modified downgrade firmware to odin back to 4.1.2 that will allow me to unlock from there....

Shortbus-Driver said:
I have found a thread about a modified downgrade firmware to odin back to 4.1.2 that will allow me to unlock from there....
Click to expand...
Click to collapse
well if bootloader is NE4 or NJ1 all i've ever read says that to downgrade will brick the phone. but..... if you can get to 4.1.1 there is a code to enter from the dial pad that will unlock. if someone has found a workaround to downgrade that would be awesome. save a lot of people a lot of trouble. if you dont mind please post results and the link to the thread.:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

I'm also on KK. My device is a I747M. I tried the 4.1.1 downgrade few minutes ago. The Service mode code works but one option is not available because modem cannot be downgraded.
Screenshot 1 > 4.1.1 with KK modem. modem downgrade gives :baseband unknown"
Screenshot 2 > Under Network Lock, "NW Lock NV Data INITIALLIZ" option not available
mrrocketdog said:
well if bootloader is NE4 or NJ1 all i've ever read says that to downgrade will brick the phone. but..... if you can get to 4.1.1 there is a code to enter from the dial pad that will unlock. if someone has found a workaround to downgrade that would be awesome. save a lot of people a lot of trouble. if you dont mind please post results and the link to the thread.:good:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse

Hmm not good.....yea im on ne4 and was hoping that worked....guess my buddy is going to have to go the other route.
That was the way I was planning to go....downgrade and use the menu code

Downgrade from 4.4.2 to 4.1.1 i747
does any tried downgrading from this? 4.4.2 to 4.4.1
im using i747 kitkat 4..4.2
can i downgrade it using samsung kies3?

In order to unlock, you need to be running the 4.1.1 bootloader. Once the phone is running a 4.3 or higher bootloader, you can't downgrade the bootloader.

Thats where Sammy pisses off its main users

At&t sent him the unlock code but its not working and also has the warning that if you try 5 or more times that the device will be permanently locked to at&t.
Any ideas there?

Are you getting the prompt to enter the unlock code? Are you running a stock dialler?

audit13 said:
Are you getting the prompt to enter the unlock code? Are you running a stock dialler?
Click to expand...
Click to collapse
Yes the phone gets the promt to enter the code .
He has a custom 4.4.2 tw rom....I dont recall which one but he wanted as close to stock as possible with s5 feel so thats what I installed.
This one ... http://forum.xda-developers.com/gal...x-4-0-touchwiz-4-4-2-ucufne4-8-12-14-t2848080

Maybe try this one: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006

Thanks ill give that a shot

[Q] A little guidance for a galaxy newbie

Hello,
I just bought my first Galaxy device (had a CDMA LG for a while, and I have a Nexus Tablet), and I am looking at how to get this new phone set up right. I bought my i747 retail, so I was unable to unlock it. However, now I'm struggling with finding the right method for upgrading, rooting, etc. I know nothing about knox or any of these Samsung intricacies. Could someone please give me a little guidance on how to go about getting to the OS and status that I'm looking for? This is what I've done so far:
Came unrooted with 4.1.2 stock rom
Unlocked using legit unlock code
Tried OTA updates, but none were available (must be because of unlock)
Rooted w/ ODIN using 4.1.1 file based of MrRobinson method. (http://forum.xda-developers.com/showthread.php?t=1739426)
Now I keep getting popups like process. ... .acore,media, etc. stopped.
I'm looking to ideally get a custom recovery (either CWM or TWRP, whichever is better) and either kitkat Touchwiz or possibly kitkat nexus stock (I read somewhere that it was possible). Also, i just bought it, and have the code still, so I don't mind deleting everything if needed. Regardless, I'd like the ability to get it back to pure stock with no flash counter (I have a manufacturer's warranty I want to use if need be).
Could someone please just give me a little guidance? I'm pretty capable with rooting, etc., so you'd only need to lead me to other threads, etc. that will take me where I want to go. Thank you very much.

Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.

audit13 said:
Before flashing or doing anything else, confirm the bootloader on your phone. Download and install the Samsung Phone Info app from the playstore and post your bootloader.
Click to expand...
Click to collapse
Well, the bad news is I already flashed using MrRobinson's instructions, and now my phone is barely workable, as things like process.android.media and Touchwiz keep crashing. I was able to install the info app though, and my bootloader is listed as I747UCDLK3. Thanks again though, and let me know what else you need from me.

I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.

audit13 said:
I recommend starting over by flashing the stock AT&T 4.1.1 firmware from sammobile. Once flashed, boot the phone and make sure your phone is sim unlocked. If it isn't sim unlocked, unlock it using the free method or your unlock code.
http://www.sammobile.com/firmwares/database/SGH-I747/
After sim unlocking, run OTA updates until you have the latest stock AT&T ROM on your phone. Upgrading the phone's bootloader and modem is the easiest way to do it for someone that is new to the phone and custom ROMs.
Click to expand...
Click to collapse
Thank you, but wouldn't OTA updates install Knox, which would basically void my warranty if I tried to flash anything after that? And, I've checked for OTA updates twice, once on 4.1.2 and on 4.1.1, and both times it said my software was up to date.
I spoke with StoneyJSG about my situation, and he suggested that I go to stock 4.1, root w/ saferoot, then flash a kitkat custom rom without Knox through TWRP. That way, I could use triangle away and flash stock unrooted if I needed to send it in.
Although, I'm not sure if I should do that, as I thought I read that you need to update the radio and bootloader first before you can install a custom kitkat rom from jelly bean, but I'm still not entirely sure how that works.

The most recent release of many custom ROMs will not work but you may not have a signal without an updated modem and you should not be running updated modems on an older bootloader. Doing this could brick your phone.
With a rooted system, OTA updates will not work.

Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.

jateed said:
Thank you again for helping walk me through the minutia around this phone.
I think I have a much better understanding of everything now. I read the following article on Knox (http://omegadroid.co/wanted-knox-void-warranty-0x1/) and with an understanding of that, I get now that there is no way to load any custom rom on 4.3 or higher without losing my warranty.
So, basically my options are to stay at 4.1 and flash whatever, using triangle away to erase my tracks. Or, I could update to 4.3, but only be able to use saferoot/towelroot, otherwise I'd trip the warranty void. But, if all I did use was towelroot (no custom recovery or rom), then I could just unroot the phone using the full unroot option in SuperSU and send it on in for service if needed, right?
Also, I did unroot my phone and did a factory reset, so it's back at 4.1.1 and unrooted. Yet, I still do not see any software updates available from Samsung. I even plugged it into Kies, and nothing (http://i.imgur.com/E0xPGpf.png). Does anyone know why this could be? Does it have something to do with my not having a carrier for the phone yet? I'm sorry for all the questions, but I do appreciate your help.
Click to expand...
Click to collapse
What is your cell service? If not AT&T, you will never get OTA.

Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.

audit13 said:
Whether you get OTA can vary from carrier to carrier and phone to phone in my opinion.
I have a Rogers HTC One X that gets OTA updates from HTC even though I am on the Bell network.
I have a Bell S3 that is running on the Rogers network and it receives OTA updates from Bell even though it has a Rogers sim card in the phone.
I have a Telus Moto G running on the Bell network and it received the Telus KK OTA update while connected to the Bell network.
Click to expand...
Click to collapse
Well, I have an AT&T model which I unlocked and will be putting on Cricket at the end of the week (when my plan month is set to end). Right now there's no SIM in it, and I've been doing everything over wifi. I looked up whether the carrier had something to do with the OTAs, and I was told that Samsung sent the updates out, not AT&T, so I figured that the carrier info was irrelevant. I now wonder what my options are.
Can I manually flash 4.3 stock without tripping the knox warranty void?
Does Towelroot/Xposed framework trip the Knox void flag?
If I can update to 4.3/4.4 and root without tripping the knox flag, I might just manually update and just run towelroot and xposed to modify my OS the best I can until my warranty runs out.
If I can't root it at all once I'm on 4.3+, then I'll just sit on 4.1.1 for a few months until I can't stand it anymore and just void the warranty anyway.
Thanks again everyone. This whole knox/binary counter thing is not something I dealt with on my CDMA LG or Nexus, so I was totally in the dark about how it all worked. This is also my first GSM phone, so all those intricacies are new to me too. Once I know about manually flashing stock and running towelroot/xposed, I think I'll be in good shape.

Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.

audit13 said:
Flashing the stock 4.3 ROM should not trip the counter as long as you do not need to install a custom recovery to flash it.
Apparently, the latest KK stock ROM cannot be rooted using Towelroot.
If you want a custom ROM, use one that will work with a 4.1.1 bootloader and modem. Once on 4.3 or higher, it's a little harder to recover from a soft brick.
Click to expand...
Click to collapse
Excellent. If I did flash stock, i would just use ODIN, then factory reset to wipe the caches. And that's good to know about the KK rom, as I would probably update straight to 4.4 if at all (I've read a lot of bad things about 4.3 on the S3), but not if it means I cannot root safely and cleanly.
I'll check out the custom roms for 4.1.1. I know that flashing the rom and/or a custom recovery will trip the binary counter, but I can just use triangle away to clean that up. Do you know if there is a list of custom 4.1.1/4.1.2 roms somewhere, or do I need to scour the older threads here?
Thank you very much audit13 (thanks to StoneyJSG and pre4speed as well). You have been immensely helpful and really brought me up to speed on everything surrounding S3 customization. Needless to say it's way more complicated than what I've dealt with from LG and Google/Asus. (I mean, i could root my nexus with a single click using Wugfresh's toolkit)

4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.

audit13 said:
4.1.1 is the only complete stock ROM that AT&T released for flashing via Odin.
4.3 ROMS and higher were prepared by XDA members for flashing in either a custom recovery or Odin.
Click to expand...
Click to collapse
Oh, so what other way can you flash a stock rom, if not through ODIN or a custom recovery? Regardless, it seems as though I really should not dive into 4.3+ until I'm ready to concede that my warranty is over. There are just too many potential pitfalls and headaches.
On the lighter side, I've found a few 4.1.2 based custom roms that have some promise. I'm going to post them here in case anyone has opinions on them, or if someone else in my situation sees this thread and wants to go custom 4.1 too:
Hyperdrive RLS16
http://forum.xda-developers.com/showthread.php?t=2176793
Slim Bean-d2
http://forum.xda-developers.com/showthread.php?t=1865262
Jedi Academy
http://www.teamandroid.com/2013/12/...oid-412-jedi-academy-jelly-bean-custom-rom/2/
Jelly ‘Beans’
http://www.teamandroid.com/2013/04/...ndroid-412-att-galaxy-s3-sgh-i747-custom-rom/

I was also torn when I got my s3 that was running 4.1.2. I downgraded to 4.1.1, sim unlocked the phone, used it on stock 4.1.2 for about a week to make sure everything was working, hardware wise, upgraded to stock 4.4.2, installed a custom recovery and a custom ROM. I wasn't too concerned about the warranty since I got the phone as a free upgrade and had no intention of using the s3 as my daily phone. I kept it as a backup until my niece needed and phone and then it went to her. It's been over a year and there are still no problems with the phone.

HardBricked i747 after UCUFNE4

I've got a different issue here. I was running SlimKat 4.4.4 with BMS kernel on my d2att. I was on the CUEMJB Bootloader and Modem, so I thought that I can directly flash the rom. First, what I did was flash UCUEMJB_to_UCUFNE4_Firmware_update.zip. It flashed perfectly till the end. Then I flash the I747UCUFNE4_Stock_Rooted_Deodex_3-31-15.zip, which had an error that I had forgotten. It apparently is caused by my BMS kernel, so I went on and reinstall SlimKat 4.4.4 to remove the kernel. It flashed perfectly, but when I rebooted my phone, it did not power on. I was thinking, what's inside the UCUEMJB_to_UCUFNE4_Firmware_update.zip, are they the bootloaders and modem for CUFNE4 ? If so, is my phone dead like all the others who flashed 4.4.2 modem over 4.3 ? Please, I need my phone bad.

Did you follow this thread: http://forum.xda-developers.com/showthread.php?t=2789917 ?
Since you were already on the mjb bootloader, you flashed the UCUEMJB_to_UCUFNE4_Firmware_update.zip file? Any errors when flashing this?
Before installing NE4 firmware, did you do a full wipe as instructed in step 3 of the thread I linked?

audit13 said:
Did you follow this thread: http://forum.xda-developers.com/showthread.php?t=2789917 ?
Since you were already on the mjb bootloader, you flashed the UCUEMJB_to_UCUFNE4_Firmware_update.zip file? Any errors when flashing this?
Before installing NE4 firmware, did you do a full wipe as instructed in step 3 of the thread I linked?
Click to expand...
Click to collapse
Hey yeah. No errors occurred when I flashed it. The only I have gotten was from the OTA update zip itself. I can't remember what it is, but it prevented me from updating my phone to UCUFNE4. So I reinstalled Slimkat and booted properly but at the time I've rebooted, it's all dead.

And also, yes. That is the post that I've followed. I checked if my bootloader and modem are CUEMJB, and they are. So I figured that the firmware update should've not ruin it.
NOTE : I am running on a debrick card UCUEMJB if that helps with the information. I can't seem to boot off the eMMC itself, so I always kept the SD card on the slot. That, until it died.

I really think that my bootloader is messed up because of the UCUEMJB_to_UCUFNE4_Firmware_update.zip. I think it borked my bootloader, that's why I can't use any debrick images to recover it. Please, help. I'm short on funds, and losing this phone is a big cut on my budget.

I heard that the i747m users recovered theirs by pulling out the 128mb file. So if any of you i747 users running at the NE4 version could just pull out the bootloader partition, that would be great. enewman's debrick doesn't seem to work for me.

The bootloader for the i747 and i747m are not compatible even though they phones appear to have the same hardware.
So the phone does not boot at all with the mjb debrick image?

audit13 said:
The bootloader for the i747 and i747m are not compatible even though they phones appear to have the same hardware.
So the phone does not boot at all with the mjb debrick image?
Click to expand...
Click to collapse
It does not. Not even with the 4.4.2 debrick image. Help

If it used to boot with the debrick image and it doesnt boot now, a jtag service may be the only way to revive it.

May I just know what happened to my phone before it had gone bananas? A little information might help. Also, Im planning to buy a board for T999. Will it fit with the I747 chassis ?

I really don't know what happened to cause this problem with your phone. When flashing a phone, there is always an element of risk. I have pooched a few phones in my life too. I even damaged a couple of sim slots by using sim adapters too.
When your phone was able to boot with the debrick image, you could have tried reflashing the mjb bootloader and modem but it's a moot point now.

No Sim detected after flashing Custom ROM

Hey guys... Been a LONG time since messing with an S3, and I don't want to brick it... SO, figured I'd reach out and ask before doing anything...
I downgraded a friend's S3 to UVDLJC to sim unlock it and it seemed to work fine on stock ROM. I then rooted the rom, flashed TWRP and factory reset the device and then flashed a custom ROM (this version is SlimKat but I had tried CM13 as well.. both have the same issue, no SIM detected)...
Anyway, I assume that it is a modem/radio issue and I should just be able to flash the modem firmware and be fine.. Problem I'm having is I'm not sure what to use... The phone is a T-999L Which, as I understand it, is the LTE GS3, but the software that was on it was based on the non LTE version (not sure if I'm correct about this)...
Anyway, looking to get this phone working for the friend's daughter (it was supposed to be a christmas present )...
Any and all help is appreciated.
Additional Info:
Phone model is T-999L
Boot loader is T999UVDLJC
Build version reports 4.4.4
Rom is currently SlimKat
Unified tools reports model as SGH-T999, type as d2tmo
Not sure what other info can help, but happy to provide.

RBThompsonV said:
Hey guys... Been a LONG time since messing with an S3, and I don't want to brick it... SO, figured I'd reach out and ask before doing anything...
I downgraded a friend's S3 to UVDLJC to sim unlock it and it seemed to work fine on stock ROM. I then rooted the rom, flashed TWRP and factory reset the device and then flashed a custom ROM (this version is SlimKat but I had tried CM13 as well.. both have the same issue, no SIM detected)...
Anyway, I assume that it is a modem/radio issue and I should just be able to flash the modem firmware and be fine.. Problem I'm having is I'm not sure what to use... The phone is a T-999L Which, as I understand it, is the LTE GS3, but the software that was on it was based on the non LTE version (not sure if I'm correct about this)...
Anyway, looking to get this phone working for the friend's daughter (it was supposed to be a christmas present )...
Any and all help is appreciated.
Additional Info:
Phone model is T-999L
Boot loader is T999UVDLJC
Build version reports 4.4.4
Rom is currently SlimKat
Unified tools reports model as SGH-T999, type as d2tmo
Not sure what other info can help, but happy to provide.
Click to expand...
Click to collapse
Odin'ed back to LJC original firmware... still shows no Sim card.

The latest custom ROMs require the latest bootloader and modem to function properly so the phone probably needs an update. Once the phone is running a 4.3 or higher bootloader means the bootloader cannot be downgraded in the future.
I don't see the LJC firmware for the T999L: http://www.sammobile.com/firmwares/database/SGH-T999L/
I see LJC for teh T999: http://www.sammobile.com/firmwares/database/SGH-T999/

audit13 said:
The latest custom ROMs require the latest bootloader and modem to function properly so the phone probably needs an update. Once the phone is running a 4.3 or higher bootloader means the bootloader cannot be downgraded in the future.
I don't see the LJC firmware for the T999L: http://www.sammobile.com/firmwares/database/SGH-T999L/
I see LJC for teh T999: http://www.sammobile.com/firmwares/database/SGH-T999/
Click to expand...
Click to collapse
Yeah, I'm thinking the phone is a T999, not a T999L. In my best estimation, the motherboard was swapped to a T999L case/screen. The sticker shows T-999L, the phone reports T-999. Additionally, under settings, the IMEI differs from the IMEI reported on the sticker. (Neither He, nor I was the original owner of the phone... so who knows it's history... For all I know, I really am working with a T-999L and someone flashed a different IMEI (worst case scenario I guess).
Is there any way to know for absolute sure? and should I go ahead and just flash 4.3? is there any downside to doing it other than that the boot loader can't be rolled back afterwards?

Personally, I would go by the model # shown with the phone in download mode.
Did it ever detect a sim card after unlocking restoring to stock?

It detected a sim when we got it (on 4.1.2), it detected a sim when i downgraded to 4.1.1, it detected a sim when i unlocked the sim, it did not detect a sim after flashing CM13, it did not detect a sim on SlimKat, and now it does not detect a sim after 4.1.1 (flashed via Odin) (LJC) and Download mode shows T-999 (NOT T-999L).
audit13 said:
Personally, I would go by the model # shown with the phone in download mode.
Did it ever detect a sim card after unlocking restoring to stock?
Click to expand...
Click to collapse

The 4.1.1 firmware came from sammobile? The baseband under settings is also LJC?

audit13 said:
The 4.1.1 firmware came from sammobile? The baseband under settings is also LJC?
Click to expand...
Click to collapse
Correct and correct.

This is bizarre because I don't understand why it would suddenly stop working. Did it say SGH-T999 on the download screen before flashing to 4.1.1?
I assume the stock ROM boots without issue?
Also try this: download and install the Samsung Phone Info from the play store to confirm the bootloader and baseband currently on the phone.
When flashing from a custom ROM to stock 4.1.1, did you perform a factory wipe?

audit13 said:
This is bizarre because I don't understand why it would suddenly stop working. Did it say SGH-T999 on the download screen before flashing to 4.1.1?
I assume the stock ROM boots without issue?
Also try this: download and install the Samsung Phone Info from the play store to confirm the bootloader and baseband currently on the phone.
When flashing from a custom ROM to stock 4.1.1, did you perform a factory wipe?
Click to expand...
Click to collapse
Stock rom boots without issue...
Yes i did a factory wipe between flashes. (Although, first flash of CM13 I did not, it ran weird, i rebooted, factory reset, flashed again then it worked fine minus the sim card issue).
Phone Info confirms SGH-T999, type: d2tmo
Boot loader: T999UVDLJC, Baseband: T999UVDLJC

Not sure what else to suggest other than reflashing the LJC ROM and performing a factory wipe from stock recovery before the phone's first boot of LJC.

audit13 said:
Not sure what else to suggest other than reflashing the LJC ROM and performing a factory wipe from stock recovery before the phone's first boot of LJC.
Click to expand...
Click to collapse
Nope...no go.

Hmm, I'm out of suggestions because you did everything I would do other than either flashing the latest stock 4.3 since the phone is now sim unlocked or running OTA updates. on a stock ROM.
The sim card in the phone works properly in another phone? Is it possible the sim reader was damaged in some manner? I know it can happen when using micro/nano sim card adapters.

audit13 said:
Hmm, I'm out of suggestions because you did everything I would do other than either flashing the latest stock 4.3 since the phone is now sim unlocked or running OTA updates. on a stock ROM.
The sim card in the phone works properly in another phone? Is it possible the sim reader was damaged in some manner? I know it can happen when using micro/nano sim card adapters.
Click to expand...
Click to collapse
Oh... adapters is a good suggestion. Yes, when I originally unlocked the phone, I used an adapter as my sim is a nano sim... Whats the damage look like? and is it fixable? I'm assuming just bent pins?
Is flashing an LTE Rom a possible solution? or is that a hard brick result?

You could try flashing TWRP and an older build of CM that will work with a 4.1.1 bootloader and modem just to see if the sim card is detected.
The metal housing on top of the sim pins is difficult to remove so it may be easier to just buy a replacement sim/sd card reader.

audit13 said:
You could try flashing TWRP and an older build of CM that will work with a 4.1.1 bootloader and modem just to see if the sim card is detected.
The metal housing on top of the sim pins is difficult to remove so it may be easier to just buy a replacement sim/sd card reader.
Click to expand...
Click to collapse
The posts aren't real specific... do you know which CM is 4.1.1 friendly?

I would try the latest cm10 or cm10.1.
https://download.cyanogenmod.org/?device=d2tmo&type=snapshot

dang you rock @audit13. as always :thumbup: , aint enuff. happy good new year for you and yours sir.
"all i can really do is stay out of my own way and let the will of heaven be done"

Any luck getting the phone to recognize the sim card?
@mrrocketdog, thanks

audit13 said:
Any luck getting the phone to recognize the sim card?
@mrrocketdog, thanks
Click to expand...
Click to collapse
Sorry for the delayed response... Yes, I finally got it to recognize (last night) ordered a new sim card tray.. interesting way to mount it by the way...
Anyway, seems as if the guess at the adapter damaging the original was correct... new one seems to be good to go.

AT&T Galaxy Note 4 N910A 5.1.1 Root for CM?

Hey,
Still a bit of a noob to the whole rooting process and navigating XDA forums, so I'm having trouble finding the information *I think* I should be looking for. Basically, my phone's just begun crashing periodically, multiple times a day: anything from Camera, Process System, Touchwiz Home Launcher, or Samsung Apps have "stopped working" / "not responding" before. Of course, my phone's warranty has expired, but my contract isn't up so an AT&T Store wont re-image it for me :crying:
Even I can tell, at this point, that it's either my OS that's failing, or it's my hardware. I figured the easiest way to test this would be to put some stable CyanogenMod on it.
The information I'm looking for is: "is this possible?"
AT&T Samsung Galaxy Note 4
SM N910A UCU2DOI2
Currently @ 5.1.1
Thanks for reading,
~Vita.

No it is NOT possible to use any form of custom firmware or to root this device. It has a locked bootloader that has yet to be cracked open and the future of that happening os very bleak to non existant.
As for reimaging the device go to the note 4 at&t general section on the forum and read up on using odin and the 5.1.1 image posted there it will wipe the phone and format yhe system and data partitions and reinstall it like a new phone just like at&t would do or the manufacturer if you sent it to them.
Good luck

Thanks for the response.
Sorry for the dumb question, but isn't Odin able to flash any firmware onto a device? The "locked bootloader" means that only the stock OS may be reinstalled? Why is this...
Also, it seems unlock progress is being made on the N910V. Maybe hope?
Thanks for mentioning Odin, I'll try re-imaging the phone.
~Vita.

Ricovita said:
Thanks for the response.
Sorry for the dumb question, but isn't Odin able to flash any firmware onto a device? The "locked bootloader" means that only the stock OS may be reinstalled? Why is this...
Also, it seems unlock progress is being made on the N910V. Maybe hope?
Thanks for mentioning Odin, I'll try re-imaging the phone.
~Vita.
Click to expand...
Click to collapse
Well the problem is the kernel the bootloader prevents the devs from using an unsecure kernel (one not created and signed by at&t) on the phone if one is used the phone stops boot and says it is an unsecure non at&t kernel and to take thenphone to at&t store.
Odin can only write the firmware versiom that is currently on this phone in this case it is 5.1.1 if you flash any other note 4 versoin such as 4.2.2 it will brick.
Sm-910a flash example
Update ver Official at&t 5.1.1 / currently on phone 5.0.1 or 5.1.1 = good
Update ver (downgrade)oficcial at&t 4.2.2 / currently on phone 5.0.1 or 5.1.1 = brick not good or odin fail
Update from another carrier such as tmobile or verizon for 910t 910v 910g = fail (do not attempt)
Until oir boot loader is unlocked there is nothing we can do to mod or use custom firmware on this phone any attempt leads to a brick requiring using odin to re-flash the latest firmware (5.1.1 at this time) in order to make the phone functional again.

giga8547 said:
Until oir boot loader is unlocked there is nothing we can do to mod or use custom firmware on this phone any attempt leads to a brick requiring using odin to re-flash the latest firmware (5.1.1 at this time) in order to make the phone functional again.
Click to expand...
Click to collapse
So from what I understand, I could use Odin to flash the 4 files which correspond to the specific AT&T 5.1.1 SM-901A version of my phone (which is exactly what I have) to re-image the device and make it functional again. The problem is, I cannot find these devices on sammobile D:
Could someone direct me to these files? Or are they not out because AT&T sucks? Or, what.
~Vita.

Ricovita said:
So from what I understand, I could use Odin to flash the 4 files which correspond to the specific AT&T 5.1.1 SM-901A version of my phone (which is exactly what I have) to re-image the device and make it functional again. The problem is, I cannot find these devices on sammobile D:
Could someone direct me to these files? Or are they not out because AT&T sucks? Or, what.
~Vita.
Click to expand...
Click to collapse
Look in odin files in progress thread.
Sent from my SAMSUNG-SM-N910A using Tapatalk

Is it possible to downdraft from 5.1.1 to 5.0.1

firebird7880 said:
Is it possible to downdraft from 5.1.1 to 5.0.1
Click to expand...
Click to collapse
I think so, I don't know for sure but we've been able to Odin from various 5.0 Lollipop releases back to KitKat so should be fine.

downgrading from 5.1.1 or 5.0.1 to kitkat is possible but with many many problem but form 5.1.1 to 5.0.1 i don't know maybe phone will stuck or boot loop
thanks finitetime for your reply
other question are there any news about root for 5.1.1 n910a

help
my att note 4 is unlocked and it still won't let me install custom rom's

mouseman1 said:
my att note 4 is unlocked and it still won't let me install custom rom's
Click to expand...
Click to collapse
I am sure that you are referring to a sim unlock. A sim unlock and unlocked bootloader are two completely different entities. To flash a custom rom you will need to have your bootloader unlocked, which is something that a few of us are currently working on. Until then, no custom roms can be flashed on the att variant Note 4s. Take care

the boot loader says Qualcom secure boot : disabled ?
in the boot loader screen ?

mouseman1 said:
my att note 4 is unlocked and it still won't let me install custom rom's
Click to expand...
Click to collapse
Your phone is SIM UNLOCKED which has NOTHING to do with root, bootloader, or custom roms.
Sent from my SAMSUNG-SM-N910A using Tapatalk

mouseman1 said:
the boot loader says Qualcom secure boot : disabled ?
in the boot loader screen ?
Click to expand...
Click to collapse
Sorry, was off the forum for the weekend. Spexwood was correct, that is sim unlock. Qualcom is for the sim IE network. Take care.

Root is possible btw
Root is possible if youre willing to dedicate 10-30 hours of repititive root fails

How?
Press Buttons said:
Root is possible if youre willing to dedicate 10-30 hours of repititive root fails
Click to expand...
Click to collapse
How is root possible? What's the process ?