Database Info

[Q] Seriously need help with unlocked ATT One X

Alright guys, I am posting out of desperation.
I am no pro when it comes to rooting/unlocking/ROMming Android phones but I have read myself to death and I am not getting anywhere. I am almost willing to send this phone to someone who knows what they are doing. I really don't feel like buying another phone. In hindsight, I should've made sure I was getting a true unbranded HOX.
I bought an unlocked, AT&T One X from Amazon while I was in Afghanistan. Received the phone via APO, put in my Roshan SIM card, and was working fine. I traveled extensively in the past few months, all over the Middle East and South Asia, phone was working fine, I just picked up a local sim card and off I went.
Well then I went back to the US for the first time with this phone. Put in my TMobile SIM, and was working fine as well. Well now I left the country again, and now I can't pick up any networks at all. I have changed the radio via the USSD to GSM, WCDMA, everything, but can't pick up any networks. Keep in mind I also still have my SIM card that I bought when I was here. I insert the card, it says preparing sim card, etc, but won't find any networks.
How do I know if the phone is still SIM unlocked? Woulnd't it prompt me for an unlock code when I insterted the foreign SIM again? Do I need to root? Does my bootloader need to be unlocked to use any SIM?
What I was figuring I would try to do was flash a different ROM so I don't have to worry about this being an AT&T phone anymore. When I boot into the bootloader, it says LOCKED at the top with S-ON. There has never been an update done to the phone since I got it.
Things i've tried:
Any root for 1.85 ( I have tried every root for 1.85 you can search for on here)
RUU to update to 2.2 (says main battery power low, but it isn't)
Factory Reset
I really don't care so much to get a new ROM, I just want my phone to work. Here is what I get in the info page on the phone:
The bootloader says HBOOT 1.09 is installed
Kernel Version:
3.0.8-01155-gca24d1e
[email protected] #1
SMP PREEMPT
Build Number
1.85.502.3_R2 CL63811 release-keys
Sense 4.0
Android 4.0.3
Software Number
1.85.502.3 710RD
If you need any more info let me know but I am dying here

Sim unlock and bootloader unlock are two different things. I don't think either has anything to do with the other.
Assuming you bought this from a legit seller on Amazon, factory unlocked is factory unlocked. I've never heard of a phone getting sim locked from putting in a sim card. If you didn't get a "input unlock code" the first time, your phone isn't sim locked and is not locked down to AT&T.
Before you can root, though, you have to unlock the bootloader. That's why your root attempts keep failing. You want to stay on 1.85, trust me--later firmware is more locked down.
Are you sure there's nothing wrong with the other sim card you got? Have you tried a new one?

iElvis said:
Sim unlock and bootloader unlock are two different things. I don't think either has anything to do with the other.
Assuming you bought this from a legit seller on Amazon, factory unlocked is factory unlocked. I've never heard of a phone getting sim locked from putting in a sim card. If you didn't get a "input unlock code" the first time, your phone isn't sim locked and is not locked down to AT&T.
Before you can root, though, you have to unlock the bootloader. That's why your root attempts keep failing. You want to stay on 1.85, trust me--later firmware is more locked down.
Are you sure there's nothing wrong with the other sim card you got? Have you tried a new one?
Click to expand...
Click to collapse
Really? The bootloader has to be unlocked before you can root? I definitely thought it was the other way around. I guess that would explain it, then..
What I actually ended up doing was repeatably trying the RUU, and finally got it to take the 2.2FW upgrade. As soon as that happened, I was pulling down 4G like nobodies business. Though, now that i've read your post, I kind of wish I would've stuck with trying to get a new ROM on it, instead of upgrading. I really have no idea why a FW upgrade made the radio start working like magic, or what would casue that at all.

Frosty288 said:
Really? The bootloader has to be unlocked before you can root? I definitely thought it was the other way around. I guess that would explain it, then..
What I actually ended up doing was repeatably trying the RUU, and finally got it to take the 2.2FW upgrade. As soon as that happened, I was pulling down 4G like nobodies business. Though, now that i've read your post, I kind of wish I would've stuck with trying to get a new ROM on it, instead of upgrading. I really have no idea why a FW upgrade made the radio start working like magic, or what would casue that at all.
Click to expand...
Click to collapse
Progress is swift. I rooted using the 2.2 xfactor exploit and then unlocked the bootloader with the spoofed CID, now as soon as I figure it out I will install CleanROM 5.1..Hope I don't brick it!

Frosty288 said:
Progress is swift. I rooted using the 2.2 xfactor exploit and then unlocked the bootloader with the spoofed CID, now as soon as I figure it out I will install CleanROM 5.1..Hope I don't brick it!
Click to expand...
Click to collapse
As long as you stay in this forum, these phones are tough to brick. The only way to do it is to flash roms for the international (Tegra 3) version.
Note that on 2.20., you have to flash the boot.img in fastboot when you flash a rom.

Youll never brick your phone as long as you have access to the bootloader or recovery lol
Sent from my HTC One X using xda app-developers app

If he wants cleanrom he won't have to be confused with fastboot. Just download rom and flash that sucker
Sent from my HTC One X using Tapatalk 2

Do NOT RUU to 2.20! (never mind too late).
Looks like you figured things out.

[Q] Checking for a Sim lock? No Service on any sim

I have a European LG P500. The problem I have is that no matter what SIM I try to put in it, it always says "No Service". I'm thinking it is either the card reader or a sim lock at this point. Before I spend 10 euro on an unlock code, is there a way to check if it is locked to a certain company for sure? Is there any other reason as to why this phone says "No Service" no matter what. By the way, I have rooted and flashed the device with no results. Would changing basebands help? Where can I find 64 bit drivers?
thanks in advance

There is fix below in my signature. Flash the first link.
If you stil face this issue.. download the first link.. unzip and and paste it in /system/lib using root explorer.
Mount r/w in root explorer.
After pasting 3 libs.. set permission x.x.-, x.-.-, x.-.-.
PM if you have doubts.

I have already flashed this zip. I downloaded and flashed cyanogen mod 7, and this fix was listed there for the older baseband users. The problem is, this phone didn't read sims even before I flashed it. It has nothing to do with the rom. I can safely conclude it's either the baseband or some other part of the firmware, the sim reader, or an internal hard-coded sim lock. Please help Thank you

I updated the baseband to Gingerbread 2.3.3 and now it acknowledges the sim but it insists that I am making calls "outside of service area". In other words I cannot make any calls. I take it this is its way of saying i'm simlocked to a certain carrier. can anyone confirm or disprove this?

Check if you have balance to make calls.
Check with other sim cards.
Stil you face this problem.. you need to get ALL GSM unlock code. Search.
To use the unlock codes.. you need to flash a stock rom.

(SOLVED) Sim not detecting/Insert a valid sim card on your phone

Hello there, I am not new to xda but this is my first post. I've a question regarding my M8 Verizon bought from ebay. Its been a year now and everything was going well since one day I accidentally did s-on and locked the bootloader while using HTC ONE M8 Toolkit by Squabbi.
Then I again s-off'd my device using Sunshine method (firewater didn't worked as it was discontinued). So I paid 1600₹ to get my device s-off'd and unlocked bootloader. But since then I am unable to use any Indian sim whether airtel, idea or any other. I tried many possible solutions found on the internet as well as here on xda. Like I flashed firmware (old and new both), flashed radio firmware files old and new both but no luck. Either I restored my device to stock Verizon rom using the RUU provided by Dottat. But I couldn't find any luck and I'm still unable to use my sim card. My phone is unable to detect it. My device doesn't even pops up any notification for sim card now. Please Help. :crying:
Is there any solution for this? I'm in a need of this.
Waiting to be helped as soon as possible.

Hi,
I do not know if same pb...
Phone is working fine on Lollipop on european Gsm/LTE (sometimes going back to cdma by itself, a bit boring), and is asking for SIM pin number.
When going to marshmallow (by RUU or by OTA) the sim is deribed to be absent or invadid, and It did ask for the SIM pin number
I did not find any clue...
regards

After a lot of tries, it finally worked. And the sim is now detected. Thanks to Me.

shad.man92 said:
After a lot of tries, it finally worked. And the sim is now detected. Thanks to Me.
Click to expand...
Click to collapse
Hello! I have same problem. I can`t use my sim card. Can you tell me how did you solve this problem?

User 1 said:
Hello! I have same problem. I can`t use my sim card. Can you tell me how did you solve this problem?
Click to expand...
Click to collapse
I disassembled my M8, then replaced the sim reader inside the phone, then removed and reinserted the flex on the board. Then turned on the phone, and edited the system file located inside root/system/customize/ACC/default.xml to change the value of sku_id and region located at last in the file default.xml

You can search on google for SKU LIST XDA. It will show you the list for all regions.

Phone network locked after flashing through Odin?

Hi,
I have a Samsung S8+ which I bought unlocked to any network, I have used it on EE and Vodafone. I had rooted the phone, flashed different roms etc no problem. After I got my new phone, I tried to get the sim out of the S8+ and the tray was stuck, left with no choice I forced it out but this broke the sim card reader as it wouldn't read any SD or Sim.
I flashed a stock 9.0 pie UK version (Unlocked) to the phone through Odin and got the sim card tray replaced, now it reads SD cards and my sim but it says network locked and is asking for the NUC code, the phone was unlocked before and now it isnt. I've contacted Vodafone for a NUC code but the code isn't working (says incorrect code), I've tried flashing stock 8.0 too, also not working and still asking for the NUC. Strangely, it isn't working on either EE or Vodafone Sims now.
Could the sim card tray being replaced effect this? Is it the software flashed through Odin?
Any help will be appriciated please.
Thanks
Sam

Is it possible not only the SIM tray but the whole motherboard was replaced? It would make perfect sense then. Check whether your IMEI and S/N match what was on the box the phone came in.

kernel.killer said:
Is it possible not only the SIM tray but the whole motherboard was replaced? It would make perfect sense then. Check whether your IMEI and S/N match what was on the box the phone came in.
Click to expand...
Click to collapse
If he sent it to samsung it may not be. I got 2 replacements from samsung identical IMEI as my orig. And they messed one up and sent back my original as well. Once so i had and technicly still have as i sold to my neighbor legit s8s cloned same imei from samsung direct

Thanks for the replies. Same IMEI which is strange, I've tried all UK sims and it's still locked. It says sim locked enter unlock code now but on every sim

xSam-H said:
Thanks for the replies. Same IMEI which is strange, I've tried all UK sims and it's still locked. It says sim locked enter unlock code now but on every sim
Click to expand...
Click to collapse
It is strange normally sim unlocks are not undone by odin flashing. Sim unlocks lie in a non flashed partition

Galaxy Note 10 VZW Flashing Firmware to Bypass Sim Lock SM-N970U to SM-N970U1

Hi All,
Been at this for several hours today and feeling a bit frustrated. Here's the context.
I bought a used Verizon Galaxy Note 10 and took it to another country.
I arrived and put a sim card in *(the phone is intended to stay here)
4G signal appeared and text messages came in
Phone blocked signal and said "sorry, your device cannot be activated on another Network right now" then it says to call Verizon.
I call Verizon and ask how to unlock.
After transferring to multiple agents, the answer is that the phone is not locked in their system and that upon inserting a SIM from another carrier, I should be prompted to put in a code and it will be "00000000" to unlock the phone
The phone never presents this option and is perpetually unable to activate because of this sim lock.
At this point, I started reading up on how I could get around this and settled on using odin to flash firmware for a different carrier and maybe having to flash the SM-N970U1 packages because that should allow me to have different stock firmware.
So I proceed to download various different images.
Here is the TMB image for SM-N970U that I downloaded:
https://samfw.com/firmware/SM-N970U/TMB/N970USQU6FUBH
I also figured maybe I would be able to flash the verizon base image and get around this lock:
https://samfw.com/firmware/SM-N970U/VZW/N970USQU6FUCD
So then I proceed to use Odin3_v3.14.4 and place all of the 4 files in their corresponding fields in odin. The file list is as follows for one of the packages:
BL_N970USQU6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
AP_N970USQU6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
CP_N970USQU6FUD9_CP19049000_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
CSC_OMC_OYN_N970UOYN6FUD9_CL21599467_QB39871099_REV00_user_low_ship_MULTI_CERT.tar.md5
I click start, the phone is recognized and then the flashing appears to occur successfully until it says pass at the end.
I reboot the phone and I notice right away that the signal is present, but then disappears and as the phone initializes the VERIZON message appears again.
Immediately I'm thinking, ok, I've just reflashed it with the TMobile image but the phone boots and says verizon and the sim lock is still there, so I probably didn't do something right.
So I factory reset, try again, no changes, I try adding the USERDATA and it also does nothing different.
At this point I'm willing to try the U1 firmware, so I download from here:
https://forum.xda-developers.com/t/n970u-and-n970u1-firmware-links-here.3957705/
But when I run the odin flash, I get model mismatch, yet the thread says they're compatible as U1 is just the samsung unlocked version. so I try the odin patch b found here:
https://odindownload.club/download/197/Odin3-v3.14.1-3B-PatcheD.zip
And it fails to write.
I am in desperate need of help as I've been unable to find more specific information, typically in threads people may say they've resolved the issue, but then they don't actually indicate what steps they took, or any of the details surrounding the resolution. If I can get help getting this resolved, I can document the exact steps i've taken in explicit detail so that others can follow them and achieve the same result.

Update:
Downloaded FRIJA to get the latest firmware, am going to explore doing a nand erase and repartition, followed by flashing tmobile firmware to see if that gets around it.
following:
https://technastic.com/odin-nand-erase-samsung/

@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...

Verizon has a 6 month unlock policy. if the phone is free of debt and older than 6 months it should be automatically unlocked. phone them, you bought the phone in good faith.

jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
That's why I am thinking of wiping the NVRAM and just re-partitioning. Then I'll flash a non-verizon system onto it. Could be that this resolves it.
Thoughts?

3mel said:
Verizon has a 6 month unlock policy. if the phone is free of debt and older than 6 months it should be automatically unlocked. phone them, you bought the phone in good faith.
Click to expand...
Click to collapse
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.

4rg3ntum said:
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
Click to expand...
Click to collapse
With AT&T they give you requested then they gave you an unlock code, it's not automatic. At least it was like this a few years back.

4rg3ntum said:
I spent 2 hours on the phone with them and spoke to 3 different representatives. They all confirmed the phone was not locked in their system. I read it was 60 day unlock policy.
Click to expand...
Click to collapse
sorry yeah, 60 days is the right period.

jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
So this appears to be true.
I loaded up ADB and turned on USB debugging and started passing shell commands through and found these files in the system with nvram in the name:
/sys/module/dhd/parameters/nvram_path
/vendor/firmware/nvram.txt_ES03_semco_b0
/vendor/firmware/nvram.txt_1rh_es13_b0
/vendor/firmware/nvram.txt_CS01_semco_b1
/vendor/firmware/nvram.txt_ES02_semco_b0
/vendor/firmware/nvram.txt_1rh_es43_b1
/vendor/firmware/nvram.txt_1rh_es41_b1
/vendor/firmware/nvram.txt_1rh_es32_b0
/vendor/firmware/nvram.txt_ES00_semco_b0
/vendor/firmware/nvram.txt_ES01_semco_b0
/vendor/firmware/nvram.txt_1rh_es12_b0
/vendor/firmware/nvram.txt_1rh_es42_b1
/vendor/firmware/nvram.txt_1rh_es11_b0
Makes me wonder if the value for locked/unlocked is editable in one of those files.
a sample of what is in the /vendor/firmware/nvram.txt_ES03_semco_b0 file:
### RSDB mode Parameters(Both core are active)
## 2g normal:15dB airplane:14dB
#slice/1/grip_rsdb_dynsar_2g=0xbcbc
#slice/1/grip_rsdb_dynsar_2g_2=0xb8b8
## 5g normal:13dB airplane:12dB
#grip_rsdb_dynsar_5g=0xb4b4
#grip_rsdb_dynsar_5g_2=0xb0b0
#
### FCC Mode: 10dB
#slice/1/fccpwrch12=0x28
#slice/1/fccpwrch13=0x28
In any case I have an issue that I can't seem to resolve. Every guide I have found about how to change carrier firmware is pretty straightforward. Yet when I flash the firmware successfully through odin for say, the sprint version of the phone, upon reboot, in about phone still says VZW, which basically tells me the phone isn't actually flashing.
I need to understand why I can't seem to get it to have another carrier's firmware. What am I doing wrong?

jwoegerbauer said:
@4rg3ntum
Flashing a (custom) ROM on an Android phone doesn't give one SIM unlock because the SIM lock stuff is in a separate ROM chip that is not part of the normal phone storage, AFAIK the SIM lock is stored in the Radio NVRAM, but I may err as always ...
Click to expand...
Click to collapse
Maybe I can edit this with ADB?
I have seen several forums where people with the same error message simply flashed another carriers firmware onto the phone and were able to get around it.
Here is someone saying they tried the U1 firmware and it gave them the option to put in an unlock code:
https://forum.xda-developers.com/t/is-verizon-locking-s10.3908683/post-80813873
Every time I try to flash the U1 firmware odin tells me model mismatch.

Update:
I flashed the latest available ATT version of U1 firmware from here:
https://samfw.com/firmware/SM-N970U1/ATT/N970U1UEU6FUDA
Using Odin patch 3B downloaded from here:
https://www.droidmirror.com/downloading/download-odin3_v3-13-1_3b_patched-zip
Having tried many U firmware + USERDATA from different carriers and never was able to get it to say anything other VZW in the about phone section.
By going to the U1 version I was able to get the unlock code portion to pop up when inserting the sim card, the phone also claims it's model number is SM-N970U1 instead of SM-N970U now.
The code Verizon gave me on the phone 0000 0000 flat out DOESN'T work. I called again today and they had their manager use a tool to provide an unlock code because the "unlock" button in their system didn't appear for my IMEI.
That system said the unlock code is 0000 0000 just like the tech the previous day. So now, they're transferring me to the advanced technical support, but somehow I doubt they will give me a code.
In any case, what I would rather do is go through ADB and try to get some binaries or text files out (may require root for these files) and get the unlock code from the device itself.
I wish this thread was more active because there are some good opportunities here to explore the OS itself and the files in it as well as tools that can be used to read the binary.

Spoke with "Advanced" support at verizon. They had no way to generate a code to unlock the device. Basically Verizon's systems didn't automatically generate an unlock code after the previous owners had the phone activated for the minimum 60 days. Because the phone was a prepaid phone and not a post paid phone, their system deleted the history of the of the prepaid account after a certain period of time when the previous owner had sold the phone to the repair shop and it sat there for months.
BASICALLY, Verizon phones are uniquely equipped with a block that prevent legitimate purchasers of various types from being able to use their devices as they hold everyone hostage with their network locking.

It looks like I can't root the device either because of the oem unlock option not being present and the workaround of changing the date not presenting the option.
At this point I'm looking to root the device so I can inspect the OS

4rg3ntum said:
It looks like I can't root the device either because of the oem unlock option not being present and the workaround of changing the date not presenting the option.
At this point I'm looking to root the device so I can inspect the OS
Click to expand...
Click to collapse
Hello I came across your thread because I am having the same issue. I think mine is similar because thus phone was a replacement through asurion/verizon. It also says its unlocked when verszon looks and when asurion looks, but I do not have service for more than 10 secind with my new AT&T Sim. Have you found anything new?.
I also looked into rooting the phone but I don't plan to keep this phone and if I want to do the trade in process and they see the root on the back end I will not receive the trade in money.

TomHanks92 said:
Hello I came across your thread because I am having the same issue. I think mine is similar because thus phone was a replacement through asurion/verizon. It also says its unlocked when verszon looks and when asurion looks, but I do not have service for more than 10 secind with my new AT&T Sim. Have you found anything new?.
I also looked into rooting the phone but I don't plan to keep this phone and if I want to do the trade in process and they see the root on the back end I will not receive the trade in money.
Click to expand...
Click to collapse
If Verizon says the phone is unlocked, make sure to Flash the U package with Verizon bloat. Connect phone to Wifi and the unlock should happen. They only seem to unlock when on the Verizon bloat U package. Anything other than that and the phone stays locked. Once it unlocks you can flash back to whatever you want.