My sgh-i927r got sim locked for the second time. Earlier i got it repaired at a shop...
It keeps on asking "ENTER NETWORK LOCK CONTROL KEY"
This time I deleted 'nv_data.bin' and '.nv_data.bak' files from 'efs' folder as suggested on a post here at XDA.
This unlocked the phone but due to the generic IMEI i still cannot use calls, but the packet data is working fine.
When i replace the backed up files in 'efs' folder the phone again gets locked...
Is there any other way of unlocking it with the original IMEI no.??
As far I'm aware the original IMEI is now obsolete as far as unlocking the phone is concerned.
We only unlock phones using codes so unfortunately I can't really help with the rest of your post.
Related
Hi guys,
This is my very first post and Glaxay Gio(S5660M) is my very first android phone!
I got this phone brand new from Bell. Wanted to unlock it to use on Rogers. Found out that the phone doesn't register any valid IMEI!
I press *#06# and IMEI shows up blank. The same happens when I go to setting->Phone status->IMEI. Nothing is there. The box and the lable underneath the battery show a valid IMEI number but nothing is registered INSIDE the phone.
Now, I tried a Bell SIM card and the phone works fine. But no luck with any other SIM card. How is it possible to operate a cell phone without IMEI?
Is it still possible for me to root and flash this phone to original Samsung firmware?
I have no experience in rooting or flashing but I don't mind trying the methods explained in this forum.
Please advise.
Cheers,
Seems you used the STL5 method to get the unlock code. That method is out of date and causes a large percentage of corrupt EFS. There's no known way to restore it right now; you have to take it back to your shop and act dumb.
Welcome to forums
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
This phone is brand new. It was never activated through Bell Canada nor was it unlocked or tampered with.
I believe the IMEI is there but Bell's firmware blockes it from being displayed before activation. Is it possible?
I called Bell and they said I should activate the phone, then their system loads the new phone number and the IMEI into the phone so I can use it.
Now, with a valid IMEI in the system, I can go ahead and unlock the phone using tested methods, right?
Please advise.
Could someone please help me out here?
This phone is prepaid by Bell Canada. The phone is not activated by Bell so there is no phone number associated with it. It is brand new.
I check the lock status of the phone and all gategories show as "OFF" but it does not work with any SIM card except Bell!
IMEI shows as two small empty boxes. No number or anything. Eveything else looks fine. All apps run well.
Now, what should I do? Can I root, flash and put the official firmware on it? Is it possible to do so? Some say the EFS is corrupted if no IMEI is showing. But how come the phone works with Bell SIM card?
Please help!
I recently purchased a samsung galaxy s6, locked to Bell Mobility (my sim is rogers). I bought my unlock code through onemanwireless, but I made a very stupid mistake and followed the instructions for t-mobile phones and installed the factory firmware found here, http://onemanwireless.com/TMobile_Galaxy_S6_Edge_unlock.htm. After I realized my mistake I reinstalled the factory firmware for Bell, which I found on this, http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841.
However, the unlock code was still unsuccessful, so I followed the other three solutions found on onemanwireless, http://onemanwireless.com/instructions.php#samsung.
When I dialed *#197328640#, I was in the debugging screen, but I didn't have the eight option for phone control.
When I dialed *2767*3855# and *7465625*638*#, nothing happened.
I've checked the IMEI and it's the correct one for my s6. Also, I have installed root checker basic, and it tells me root access is not prorperly installed on the device. I've already gotten the network code incorrect eight times, so I want to know if I'm limited to a specific number of tries before my phone cannot be unlocked again?
Any help would be very much appreciated.
s6 edge 128gb ? Rogers to Virgin. Issues
hi,
i think i do have the similar situation but got unlocked and found your post on googling my phone solution.
i am having s6 edge 128gb initially from rogers two weeks ago from now. my network is Virgin and all initial attempts failed to unlock and now faces some problems ( hopefully can fix and can help each other)
please tell is your model 128gb?
My name is Samir and from Brampton.
May be you can contact me at [email protected] and we can discuss further as you like and can share more info.
Hope to hear back from you soon.
Get your unlock code from your network.
Mine is a Bell 32gb model and the #7465625*638*# code from dialer worked just fine I punched in my unlock code and I unlocked successfully
Hi guys need some help! :'(
I bought a N920-T from shop which was Unlocked and Working for other carriers on Kit Kat rom.
I then installed stock Marshmallow using Odin/Rooted and TWRPD it. And it was fully working with my international SIM. I made a backup of my fully working unlocked Marshmallow with all the items checked (EFS and MODEM too).
Today, somehow my rom got stuck and crashed and I decided to Restore it using backup which I made. Restore got through and everything was back EXCEPT I see "Network Lock:" screen on first time boot up after restoring it.
"The device can be remotely unlocked if eligible. Please use "Device Unlock" application to unlock the device."
Please help! What should I do? Should I launch the T mobile device unlock application and continue it with wifi and see what happens?. Or what?. My device was unlocked and fully working on Kit Kat and Marshmallow too. It means it was officially unlocked right?. PLEASE GUIDE.
rektbloodells said:
Hi guys need some help! :'(
I bought a N920-T from shop which was Unlocked and Working for other carriers on Kit Kat rom.
I then installed stock Marshmallow using Odin/Rooted and TWRPD it. And it was fully working with my international SIM. I made a backup of my fully working unlocked Marshmallow with all the items checked (EFS and MODEM too).
Today, somehow my rom got stuck and crashed and I decided to Restore it using backup which I made. Restore got through and everything was back EXCEPT I see "Network Lock:" screen on first time boot up after restoring it.
"The device can be remotely unlocked if eligible. Please use "Device Unlock" application to unlock the device."
Please help! What should I do? Should I launch the T mobile device unlock application and continue it with wifi and see what happens?. Or what?. My device was unlocked and fully working on Kit Kat and Marshmallow too. It means it was officially unlocked right?. PLEASE GUIDE.
Click to expand...
Click to collapse
It would not hurt anything or make things worst for you if you tried the Tmobile Device Unlock,
it will either network unlock your phone or it won't.
I used Device Unlock on my Tmobile Note 4 and my Tmobile S6 Edge+ and in both cases it
worked fine and unlocked my phones.
Good luck,
Have a great day!
rektbloodells said:
Hi guys need some help! :'(
I bought a N920-T from shop which was Unlocked and Working for other carriers on Kit Kat rom. .
Click to expand...
Click to collapse
First off the phone shipped with Lollipop not kit Kat. Second a true Sim carrier unlock is permanent and can't be undone as far as I know.
I do remember when you use the device unlock app their is an option to temporarily unlock, I wonder if that's what you had?
Sent from my SM-N920T using Tapatalk
re ubnlock>??
i had both of my n920t note 5sunlocked well i decided to mod thyem and the unlock was taken away. well i re downloaded the devicxe un lock an was told this feature is not availlable for ths device. now t mobile is refusing to unlock them because i left them and the new comapany im with is bootleg. what can i do
Brooklyn911 said:
i had both of my n920t note 5sunlocked well i decided to mod thyem and the unlock was taken away. well i re downloaded the devicxe un lock an was told this feature is not availlable for ths device. now t mobile is refusing to unlock them because i left them and the new comapany im with is bootleg. what can i do
Click to expand...
Click to collapse
Unlocking the carrier lock is permanent
No amount of modding would change it
See if your phone is eligible to unlock: Mobile Wireless Device Unlocking.
From that Application list, tap Device Unlock.
Tap Continue.
Wait while the device connects to the server.
Choose the desired device unlock type:
Permanent Unlock: Permanently unlocks the device.
Temporary Unlock: Temporarily unlocks device for 30 days.
Note: Temporary unlocks must be performed with a mobile data connection. Wi-Fi will not work.
Wait while the device requests the unlock.
If successful, restart the device to apply the settings
Click to expand...
Click to collapse
Sent from my SM-N920T using Tapatalk
Well it did
---------- Post added at 03:53 AM ---------- Previous post was at 03:52 AM ----------
I can't even use smart switch to go back to stock
The T-Mobile app didn't work. Permanent and Temporary Unlock said my device is "not eligible". I am confused, when I bought the phone it was working with other Sim and was on Lollipop/Rooted and then I installed Marshmallow T-Mobile Stock Rom via Odin/Rooted and it was still Unlocked then back up which I created was with EFS and MODEM checked in TWRP of Marshmallow. I think the EFS and MODEM option in backup creation and restoring it messed my phone up. But I am still wondering how was it unlocked?. T-Mobile says my mobile is ineligible, maybe shop owner used Z3X Box Samsung Tool Pro or something?
UPDATE:
I decided to use unlock services online. The one I used was unlockbase they have a software that unlocks the phone on-the-go and it requires internet connection. I got my phone unlocked and international SIM working. The question is that if I backup my EFS and MODEM now using TWRP and later restore it will it break the UNLOCK?.They guarantee that their unlock is permanent and modding won't do anything.
Because the unlock they do is of course by altering the EFS/FILES and in that case backing up EFS and MODEM is a safe way to UNLOCK my phone again in future if it somehow gets LOCK again, right?.
For Developers: I have my before/after EFS files backups. Before unlock and after unlock, if some developer wants it for research purposes, I can send it to you for the sake of development.
rektbloodells said:
Hi guys need some help! :'(
I bought a N920-T from shop which was Unlocked and Working for other carriers on Kit Kat rom.
I then installed stock Marshmallow using Odin/Rooted and TWRPD it. And it was fully working with my international SIM. I made a backup of my fully working unlocked Marshmallow with all the items checked (EFS and MODEM too).
Today, somehow my rom got stuck and crashed and I decided to Restore it using backup which I made. Restore got through and everything was back EXCEPT I see "Network Lock:" screen on first time boot up after restoring it.
"The device can be remotely unlocked if eligible. Please use "Device Unlock" application to unlock the device."
Please help! What should I do? Should I launch the T mobile device unlock application and continue it with wifi and see what happens?. Or what?. My device was unlocked and fully working on Kit Kat and Marshmallow too. It means it was officially unlocked right?. PLEASE GUIDE.
Click to expand...
Click to collapse
ask the gentleman to unlock it on xda he's awesome! Never restore it'll cause you to loose unlock under all cercumstances I've learned not a big deal
UPDATE:
I have Saved my UNLOCKED EFS and Modem Files, and upon restoring those using TWRP my phone gets unlocked, tried purposely after locking my device and it works, you just gotta save them EFS Files (unlocking services like via box or online tools edit these files in order to unlock) , they are the real deal lol. Made Several copies of my Unlocked EFS/Modem Files xD
So after hours of trying to unlock this brick, I didn't succeed.
I've deleted modemst1 and modemst2, this rendered the device without imei, wifi and bluetooth. After creating the partitions all returned to normal, including sim lock, so the method from OnePlus 6T doesn't work with us.
And there's an app inside called com.oneplus.factorymode.qualcomm.ClearTelcelnetlock that just refuses to open.
If anyone managed to unlock it, please help me out.
Note: I can't unlock through Tmo since I'm not the original owner and I can't contact the previous one.
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.