Related
Hello all
I purchased a Droid 2 Gloabal unlocked on eBay, got it today, thankfully everything works (well atleast for now).
Currently it's running 2.2 Froyo.
I was prompted to download the OTA software (GB), and I did. The phone then asked me to reboot, and install it, I hit okay.
The next thing is the update progress bar, all goes well, and then all of the sudden, I get a little exclamation mark on the screen, and it reboots.
Now, for some reason I have CW Recovery Mod alway running at startup, never encountered this before om another phone (non Droid, this is my first 'verizon' droid).
Oh, I live in Canada and use Virgin mobile.
Anyway, I select "reboot phone", and then it goes back into 2.2 Froyo, tells me that "Update failed".
I was looking at different roms, just can't figure out which one is the best for my setup - Canada.
The phone looks like it's rooted, I also have the Droid 2 Bootstrapper on it, however the tool gives me an error no matter what button I press in it.
Can someone point me in the right direction please
I am somewhat of a noob.
Also, does nandroid backup the whole system, kernel and all, if things go belly up, will it always fix my issue?
Thanks!
----------------EDIT----------------
So, I found out that the phone is actually not rooted, so I rooted it, using Z4root.
Now, I am at a loss. The phone that I flashed before was quite straightforward to do, this one is stragne.
As mentioned above, I can't upgrade to 2.3 since the phone is rooted (also, I renamed blurupdater.apk so now I don't get the pesky warning message to update).
What do I do to go to 2.3.x?
Since, from what I read on the forums, you can't go 2.2 -> custom rom 2.3, you have to go 2.2 -> 2.3 official rom -> 2.3 custom rom?
Any ideas?
Gingerbread Full SBF 4.5.608
http://forum.xda-developers.com/showthread.php?goto=newpost&t=1437177
Thanks for that link.
So, I can flash that over my current install of Foryo + root + Clockwork?
Also, what about the unlocked status of the phone?
I have no idea how it is unlocked (perhapps a rom that does not honor provider locks?), is there any way I can tell if the phone has been truly unlocked?
If I go to the menu to enter the unlock code (I forget what menu it is, but you get to it by dialing some number), the "Enter unlock code" still pops up?
What could this mean?
I don't want to brick my phone xD
Thanks again!
vlambrecht said:
Thanks for that link.
So, I can flash that over my current install of Foryo + root + Clockwork?
Also, what about the unlocked status of the phone?
I have no idea how it is unlocked (perhapps a rom that does not honor provider locks?), is there any way I can tell if the phone has been truly unlocked?
If I go to the menu to enter the unlock code (I forget what menu it is, but you get to it by dialing some number), the "Enter unlock code" still pops up?
What could this mean?
I don't want to brick my phone xD
Thanks again!
Click to expand...
Click to collapse
Yes you can flash it with what ever you have or don't have
You will have to reroot after with petes root tools
Once unlocked the phone is always unlocked can't be locked again
Sbfs and roms don't touch that part of phone
Sent from my DROID2 GLOBAL using xda premium
Thanks, and lastly, about Clockwork Recovery, will it need to be reinstalled as well?
Consider reading this: http://droid.koumakan.jp/wiki/SBF
The intro part should probably provide the answer to your question.
vlambrecht said:
Thanks, and lastly, about Clockwork Recovery, will it need to be reinstalled as well?
Click to expand...
Click to collapse
As I'm sure it was covered in the link from the post above mine, I'll just say this to make sure.
Yes, you will need to reroot and then flash CWM.
Hello again all!
Finally got the time to try to SBF the D2G to Gingerbread.
One question still lingers in my mind.
The phone was sold to me as unlocked, and for all intents and purposes, it is. I use my Virgin mobile SIM, and it works.
However, here is my concern. Is there only 1 way to unlock the phone? A code unlock?
Why I am wondering, it's because if you enter "#073887*" the code entry dialog still appears. Is that supposed to happen?
My fear is, that once I SBF from Froyo to GB, my phone will be locked (unless it was really code unlocked).
So, my question is twofold:
a) would entering "#073887*" ALWAYS show the code entry dialog, even if the phone has been unlocked?
b) Is there a way to determine if the phone has been code-unlocked, v.s. some sort of custom/moded rom that does not honour the provider lock?
Thanks!
Yes, the code input dialogue is displayed no matter what state the phone is in in terms of SIM lock.
There is no ROM or software tool that can avoid the SIM lock on a DROID2 GLOBAL device.
If the phone is unlocked, it stays that way. With a locked phone, all you can do to use it on GSM (besides unlocking normally) is use a TurboSIM. If you can use non-VZW/VodafoneNL SIM cards, your phone is unlocked.
You cannot enter unlock codes while on custom firmware; only stock ROM supports unlocking.
Flashing does not reset the SIM lock status. An unlocked phone stays unlocked even after flashing an SBF image.
you should add that to your wiki, good info
Thanks, that's great info!
I will SBF the phone later and let you guys know
Hey guys. So, first of all, we've got our own forum! I don't know when it happened, as I wasn't really paying attention after the first few...months...but here we are!
Anyway, some of you may know about the free unlock method posted by owl74 in the Note II forum (link: http://forum.xda-developers.com/showpost.php?p=34661189, has screenshots). This turned out to work for the SGSIII, the SGSII and SGSII Skyrocket. Well this post is to verify that IT WORKS FOR THE RELAY 4G TOO!
Before proceeding: do this at your own risk. There is no guarantee it will work for you. You MUST be running a stock ROM with a stock modem. I am using the UVMA2 stock ROM with the UVMA2 modem on T-Mobile USA.
Read ALL directions first before trying this out.
This was ONLY tested on MY phone, with the UVMA2 update and modem, on T-Mobile USA.
Without further ado, here are the complete steps toward unlocking the Relay 4G (Thanks again to OP owl47):
*NOTE:* Never use the "back" button. There is an option when pressing the menu button to go back.
First, dial
Code:
*#197328640#
in the dialer app
Hit option [1] UMTS
Hit option [1] DEBUG SCREEN
Hit option [8] PHONE CONTROL
Hit option [6] NETWORK LOCK
Hit option [3] PERSO SHA256 OFF
WAIT exactly 30 seconds.
Hit the menu button and select the "Back" option.
Hit option [4] NW LOCK NV DATA INITIALLIZ
WAIT exactly 60 seconds
There will be no prompt, but reboot your phone. It should now be unlocked.
Verify that your phone is unlocked by using a SIM card from another network. I tested it using my wife's AT&T SIM card and it connected successfully.
The prompts and the menu for the Relay 4G is a bit different from the other phones, but the screenshots provided in the original link above should serve as a rough guide for what you might see. I personally never saw the 'PERSO_NV_INIT is SUCCESSFUL' prompt, but it still worked for me.
Your mileage may vary. If someone is brave enough to give it a try on earlier versions of stock ROMs, be my guest.
For a rooted UVMA2 rom, gee one posted a link to his FTP site where he is hosting a copy of the rooted rom (should be CWM flashable):
http://forum.xda-developers.com/showthread.php?p=38623790#post38623790
Post your success/failure below!
theZenman said:
Hey guys. So, first of all, we've got our own forum! I don't know when it happened, as I wasn't really paying attention after the first few...months...but here we are!
Anyway, some of you may know about the free unlock method posted by owl74 in the Note II forum (link: http://forum.xda-developers.com/showpost.php?p=34661189, has screenshots). This turned out to work for the SGSIII, the SGSII and SGSII Skyrocket. Well this post is to verify that IT WORKS FOR THE RELAY 4G TOO!
Before proceeding: do this at your own risk. There is no guarantee it will work for you. You MUST be running a stock ROM with a stock modem. I am using the UVMA2 stock ROM with the UVMA2 modem on T-Mobile USA.
Read ALL directions first before trying this out.
This was ONLY tested on MY phone, with the UVMA2 update and modem, on T-Mobile USA.
Without further ado, here are the complete steps toward unlocking the Relay 4G (Thanks again to OP owl47):
*NOTE:* Never use the "back" button. There is an option when pressing the menu button to go back.
First, dial
Code:
*#197328640#
in the dialer app
Hit option [1] UMTS
Hit option [1] DEBUG SCREEN
Hit option [8] PHONE CONTROL
Hit option [6] NETWORK LOCK
Hit option [3] PERSO SHA256 OFF
WAIT exactly 30 seconds.
Hit the menu button and select the "Back" option.
Hit option [4] NW LOCK NV DATA INITIALLIZ
WAIT exactly 60 seconds
There will be no prompt, but reboot your phone. It should now be unlocked.
Verify that your phone is unlocked by using a SIM card from another network. I tested it using my wife's AT&T SIM card and it connected successfully.
The prompts and the menu for the Relay 4G is a bit different from the other phones, but the screenshots provided in the original link above should serve as a rough guide for what you might see. I personally never saw the 'PERSO_NV_INIT is SUCCESSFUL' prompt, but it still worked for me.
Your mileage may vary. If someone is brave enough to give it a try on earlier versions of stock ROMs, be my guest.
For a rooted UVMA2 rom, gee one posted a link to his FTP site where he is hosting a copy of the rooted rom (should be CWM flashable):
http://forum.xda-developers.com/showthread.php?p=38623790#post38623790
Post your success/failure below!
Click to expand...
Click to collapse
Already covered...
Check nocturin's portal thread. Tons of stuff there, including this
gtmaster303 said:
Already covered...
Check nocturin's portal thread. Tons of stuff there, including this
Click to expand...
Click to collapse
Whoops, you're right. I searched the forums and couldn't find anything about "unlocking" that wasn't talking about screen unlocking.
I guess this is what happens when you go for months without an organized forum and people are just cramming everything into mammoth threads...
Hi erveryone,
I am thinking about buying the Galaxy Relay, since my old phone broke, but because I live in Europe I'd have to import it. Is there any way (I could not find any using the search function) to SIM-unlock this phone without being on a t-mobile network?
_RaZziel_ said:
Hi erveryone,
I am thinking about buying the Galaxy Relay, since my old phone broke, but because I live in Europe I'd have to import it. Is there any way (I could not find any using the search function) to SIM-unlock this phone without being on a t-mobile network?
Click to expand...
Click to collapse
As far as I know, sure. I had an AT&T SIM in there while I was unlocking it. After I rebooted, it connected to the network. I don't think you need to start connected to the T-Mobile network or anything.
_RaZziel_ said:
I am thinking about buying the Galaxy Relay, since my old phone broke, but because I live in Europe I'd have to import it. Is there any way (I could not find any using the search function) to SIM-unlock this phone without being on a t-mobile network?
Click to expand...
Click to collapse
When you follow the above procedure you don't need to have a SIM card in the phone, you are not on T-Mobile or any other network.
I also imported my phone and unlocked it in Norway, it worked nice.
i bought an unlock code from an us site. seemed to be the easiest and fastest way to me.
never needed another simcard for the procedure than my T-Mobile Germany. And yes, it's specifically locked to T-Mobile USA.
A TM simcard from another country just gets rejected like any other provider's card.
This is a very handy tip for sim unlock.
I bought the phone for my cousin as he was jealous of my Relay.
Forgot about the unlock needed as neither of us or on Tmobile here in London. Happily saw this thread. 1, 2, 3 job done, for freeeee.
Thank you for finding and sharing this procedure.
:thumbup:
Sent from my SGH-T699 using xda app-developers app
Unlocking on Jelly Bean
theZenman said:
Hey guys. So, first of all, we've got our own forum! I don't know when it happened, as I wasn't really paying attention after the first few...months...but here we are!
Anyway, some of you may know about the free unlock method posted by owl74 in the Note II forum (link: http://forum.xda-developers.com/showpost.php?p=34661189, has screenshots). This turned out to work for the SGSIII, the SGSII and SGSII Skyrocket. Well this post is to verify that IT WORKS FOR THE RELAY 4G TOO!
Before proceeding: do this at your own risk. There is no guarantee it will work for you. You MUST be running a stock ROM with a stock modem. I am using the UVMA2 stock ROM with the UVMA2 modem on T-Mobile USA.
Read ALL directions first before trying this out.
This was ONLY tested on MY phone, with the UVMA2 update and modem, on T-Mobile USA.
Without further ado, here are the complete steps toward unlocking the Relay 4G (Thanks again to OP owl47):
*NOTE:* Never use the "back" button. There is an option when pressing the menu button to go back.
First, dial
Code:
*#197328640#
in the dialer app
Hit option [1] UMTS
Hit option [1] DEBUG SCREEN
Hit option [8] PHONE CONTROL
Hit option [6] NETWORK LOCK
Hit option [3] PERSO SHA256 OFF
WAIT exactly 30 seconds.
Hit the menu button and select the "Back" option.
Hit option [4] NW LOCK NV DATA INITIALLIZ
WAIT exactly 60 seconds
There will be no prompt, but reboot your phone. It should now be unlocked.
Verify that your phone is unlocked by using a SIM card from another network. I tested it using my wife's AT&T SIM card and it connected successfully.
The prompts and the menu for the Relay 4G is a bit different from the other phones, but the screenshots provided in the original link above should serve as a rough guide for what you might see. I personally never saw the 'PERSO_NV_INIT is SUCCESSFUL' prompt, but it still worked for me.
Your mileage may vary. If someone is brave enough to give it a try on earlier versions of stock ROMs, be my guest.
For a rooted UVMA2 rom, gee one posted a link to his FTP site where he is hosting a copy of the rooted rom (should be CWM flashable):
http://forum.xda-developers.com/showthread.php?p=38623790#post38623790
Post your success/failure below!
Click to expand...
Click to collapse
I wanted to ask if I updated the phone to the jelly bean version before I unlock then I tried to unlock the phone will it work?
NexusWarp said:
I wanted to ask if I updated the phone to the jelly bean version before I unlock then I tried to unlock the phone will it work?
Click to expand...
Click to collapse
I only tried unlocking before the upgrade. If you unlock before, it remains unlocked after the update. Don't know what happens if you try it after.
Just got my locked relay, used this method - now it's unlocked.
Confirmed working, I guess.
Thanks for that!
theZenman said:
Hey guys. So, first of all, we've got our own forum! I don't know when it happened, as I wasn't really paying attention after the first few...months...but here we are!
Anyway, some of you may know about the free unlock method posted by owl74 in the Note II forum (link: http://forum.xda-developers.com/showpost.php?p=34661189, has screenshots). This turned out to work for the SGSIII, the SGSII and SGSII Skyrocket. Well this post is to verify that IT WORKS FOR THE RELAY 4G TOO!
Before proceeding: do this at your own risk. There is no guarantee it will work for you. You MUST be running a stock ROM with a stock modem. I am using the UVMA2 stock ROM with the UVMA2 modem on T-Mobile USA.
Read ALL directions first before trying this out.
This was ONLY tested on MY phone, with the UVMA2 update and modem, on T-Mobile USA.
Without further ado, here are the complete steps toward unlocking the Relay 4G (Thanks again to OP owl47):
*NOTE:* Never use the "back" button. There is an option when pressing the menu button to go back.
First, dial
Code:
*#197328640#
in the dialer app
Hit option [1] UMTS
Hit option [1] DEBUG SCREEN
Hit option [8] PHONE CONTROL
Hit option [6] NETWORK LOCK
Hit option [3] PERSO SHA256 OFF
WAIT exactly 30 seconds.
Hit the menu button and select the "Back" option.
Hit option [4] NW LOCK NV DATA INITIALLIZ
WAIT exactly 60 seconds
There will be no prompt, but reboot your phone. It should now be unlocked.
Verify that your phone is unlocked by using a SIM card from another network. I tested it using my wife's AT&T SIM card and it connected successfully.
The prompts and the menu for the Relay 4G is a bit different from the other phones, but the screenshots provided in the original link above should serve as a rough guide for what you might see. I personally never saw the 'PERSO_NV_INIT is SUCCESSFUL' prompt, but it still worked for me.
Your mileage may vary. If someone is brave enough to give it a try on earlier versions of stock ROMs, be my guest.
For a rooted UVMA2 rom, gee one posted a link to his FTP site where he is hosting a copy of the rooted rom (should be CWM flashable):
http://forum.xda-developers.com/showthread.php?p=38623790#post38623790
Post your success/failure below!
Click to expand...
Click to collapse
I'm on a stock rom and stock UVMA2 Baseband, but I am rooted. Should this work? If this fails and I have a backup in recovery, can I roll back to that or might it brick my phone such that I can't even get to recovery?
jarrodlombardo said:
I'm on a stock rom and stock UVMA2 Baseband, but I am rooted. Should this work? If this fails and I have a backup in recovery, can I roll back to that or might it brick my phone such that I can't even get to recovery?
Click to expand...
Click to collapse
I tried it. It did not unlock my phone. It did not harm my phone in any way I can tell, it just didn't unlock it. I've called T-Mobile to request a sim unlock code from them.
undo
Gonna post this here just because it may be useful to someone.
I tried this unlock method - but I tried it AFTER I had done the OTA update to Jelly Bean. It obviously didnt work. I then went to T-mo and got them to give me an official unlock code. The unlock codes they gave me would not work though - just kept saying "unlock unsuccessful" no matter how many unlock codes they gave me to try. I noticed it seemed like it wasn't even going out on the network to try to validate the unlock before saying it was unsuccessful... so I did the unlock backwards kinda:
in the dialer app
Hit option [1] UMTS
Hit option [1] DEBUG SCREEN
Hit option [8] PHONE CONTROL
Hit option [6] NETWORK LOCK
Hit option [3] PERSO SHA256 ON
WAIT exactly 30 seconds.
Hit the menu button and select the "Back" option.
reboot your phone.
After I did that - I was able to get the unlock code from T-mo to actually go out and validate and unlock the phone.
I am unable to complete the instructions in the OP because the network lock menu on my Relay 4g does not have the 4th option... Only 3 options.
Failure to unlock...
Sent from my One using Tapatalk 4
reaper000 said:
I am unable to complete the instructions in the OP because the network lock menu on my Relay 4g does not have the 4th option... Only 3 options.
Failure to unlock...
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
What version of the stock rom are you using? Maybe you have to flash back to a previous version.
gee one said:
What version of the stock rom are you using? Maybe you have to flash back to a previous version.
Click to expand...
Click to collapse
Haven't begun to even play with it! Straight out of the box, not rooted, nothing. It is running 4.1.2, though. I was hoping to confirm it worked on Straight Talk before I really started to mess with roms and flashing stuff...
Sent from my HTC One using Tapatalk 4
reaper000 said:
Haven't begun to even play with it! Straight out of the box, not rooted, nothing. It is running 4.1.2, though. I was hoping to confirm it worked on Straight Talk before I really started to mess with roms and flashing stuff...
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
4.1.2 is Jelly Bean. Maybe you have to flash back to Ice Cream Sammich. See the posts above about issues with Jelly Bean.
To flash back, I think you either need heimdall or a custom recovery (although I think you need heimdall to flash a new recovery).
sent while running with scissors
Hey guys,
I just got my Relay 4G in the mail yesterday.... I was playing with it and without SIM just wifi enabled I did all the updates, then I found this thread... (oops)
I hitup www.samfirmware.com, I rolled back to UVMA2 update using Odin 3.07 (put the .tar.md5 file in PDA and flash)
Then I booted into recovery and did a factory wipe. I followed the directions in this thread, voila ... unlocked phone, it works now on my Virgin Mobile SIM card in Canada.
(Did this help you ??? There's a button for that ;0)
Succes on two phones here
Thanks for the instructions, worked perfectly!
I bought two used, one was already on Jelly Bean, and as noted above the option just is not in the menu as listed in directions. After flashing it back to the Ice Cream Sandwich stock rom I could proceed with the unlock and it worked perfectly. The other phone was ICS already and it unlocked first try. :good:
Hey guys,
It has been a long time since I have done everything with my AT&T One X and I am having some trouble. I want to carrier unlock my phone so I can use it when I travel to Israel in 2 weeks. I got the code from AT&T through their website. I am running CM-NostromoPop v2.0.4.
The directions I received from AT&T are:
1. Power off the device and remove the AT&T SIM card.
2. Insert non-AT&T SIM card.
3. Power on the device. Wait a few moments, allowing the device to fully power-up.
4. Enter the unlock code when prompted.
5. Press OK. The device is unlocked.
The only microSIM I have is a Verizon SIM I use in my Verizon tablet. It is active on a Verizon account. I put that SIM in and turned on the phone, it popped up asking for the code, I type the code in correctly and press Unlock (it doesn't say OK) and it says "unlock unsuccessful" and waits for me to put the code in again. Has anyone run into the problem? Is the problem more likely to be CyanogeMod of the SIM card? I am currently installing ViperXL on my phone to see if a stock ROM would work better but I only have 2 tries left until my phone is permanently locked to the AT&T network.
I called AT&T and they said factory reset the phone or bring it into an AT&T store. I can't do either of those without flashing back to stock and I cannot figure out how to do that. Can someone explain to me or link me to a post on how to flash back to complete stock (the latest stock version preferrably, I probably won't be rooting my phone or anything anymore)
Some info about my phone:
I am S-OFF
CID is 11111111
HBOOT is 2.15
Radio is 1.31a.32.45.16_2
Recovery is TWRP 2.8.7.1
Thank you very much in advance
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.
First of all:
I'm no Dev...just someone who likes to play lego.
From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.
I've read a good startup here.
Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.
(https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
(1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)
Anyways...here are maybe small hints to avoid a few traps.
a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
There appears a possibility of choice.
Press VolUp short: get the mobile on standby to flash the rom via odin.
Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
Of course this can possibly be done via adb/fastboot commands.
Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.
b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
Flashing the tar back to the mobile via odin was little bit tricky.
It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
I had to patch it to BL too.
Cheers
MikGx
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
MikGx said:
@boot into bootloader after unlocking it...:
Yess you are right. Thats exactly the message.
Then you can enter the Device unlock mode again (long press VolUp) to lock bootloader again (then it resets automaticaly to factory-defaults and all work is gone.)
or
continue to flash something (short press VolUp).
Dont know about the US versions. Could be that there is a difference to my EU-models.
But either i rooted nearly every every mobile since the S2
Click to expand...
Click to collapse
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
naldotech.com, the link you provide is pretty clear about the process. What it doesnt say is what to do at the end. When you untick "reboot" in odin, and you finish flashing, your phone will stay in download mode. Then what to do?. Press power and volume down to leave and restart the phone? or, power and volume down, screen goes black imediately power and volume up, enter recovery and restart from there.? please someone ?
Press the power and volume down buttons for about 7 seconds and it will reboot
beanbean50 said:
Press the power and volume down buttons for about 7 seconds and it will reboot
Click to expand...
Click to collapse
I did as you mention but it didnt work. It made me reset the system. But I Fallowed the naldotech.com guide. At the end, being in dawnload mode, I pressed power and volume down, when the screen got black I pressed power and volumen up, I entered recovery mod, cleared cache and re- started the system: Voila my phone is rooted
Hello.
Can someone pleas provide a working link for frija download? The one referring from naldotech seems to be broken (https://www.naldotech.com/download-samsung-galaxy-stock-firmware-frija-tool/)
Update: Found a link via google -> https://technastic.com/odin-download-samsung-latest-all-versions/
twistedumbrella said:
When you boot into bootloader after unlocking, is the message something about "a custom OS can cause critical problems"?
As it stands now, the only reason I have to believe the US bootloader can't be unlocked (or isn't already) was the lack of an OEM unlock button and some cranky kid on the internet saying it hasn't been possible since the S7.
It doesn't make sense why I would have a warning about a custom OS if there is no possible way to install one, though.
Click to expand...
Click to collapse
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
d0x360 said:
The USA version (snapdragon soc) can't be rooted as far as I know. There is no way to unlock the bootloader in dev options, at least on Verizon and that holds true even if you bought a unlocked phone. As soon as you insert a Verizon sim and the phone updates it's all over.
I had the same issue with the original Pixel. I bought it unlocked but before rooting it I allowed it to update like a fool. Luckily my son wanted the same phone so I gave him mine then rooted and installed TWRP before putting a Verizon sim in.
Back to Samsung...as far as I know you haven't been able to root the USA version since the note 8. The rest of the planet gets the Exynos SOC but we get the snapdragon and no root method works. My note 9, 10+ and z Flip3 didn't have an unlock bootloader option even before putting a sim in it.
Click to expand...
Click to collapse
twistedumbrella said:
I think you misunderstood what I was asking, but ended up answering it anyway.
It seems the message about installing custom OS versions may be a boilerplate for the bootloader, not any indication that it's possible.
Click to expand...
Click to collapse
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
twistedumbrella said:
I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
Click to expand...
Click to collapse
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
d0x360 said:
Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.
I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.
A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".
The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
Click to expand...
Click to collapse
You got where I said "I guess the disclaimer is misleading" right?
twistedumbrella said:
You got where I said "I guess the disclaimer is misleading" right?
Click to expand...
Click to collapse
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
d0x360 said:
I didn't see that sentence in any of the posts but perhaps I just missed it.
It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.
It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.
I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
Click to expand...
Click to collapse
Lucky? I dunno. Had I known it would cause this much trolling, I wouldn't have bothered to mention it.
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
david.siebauer said:
I have a general question. I am unfamiliar with rooting/unlocking bootloader on Samsung devices. Is it possible to revert unlocking the bootloader and going back to stock traceless?
Click to expand...
Click to collapse
Partially. I just did that: I have AfWall running on my old phone, tried to unlock the Flip with this manual here in order to use the firewall there, did something wrong - and stumbled upon Netguard while searching what might have happened and decided to give it a try first. (Unless there is a custom ROM for the phone available, I have no other need for root or an unlocked bootloader.)
From what I could find on my Flip 3, you can unlock and relock the bootloader as you like - but as soon as you install a non-genuine bootloader (i.e. one chnaged by Magisk) you will trip Knox - and this cannot be reverted.
In such a case you can still re-lock your bootloader and unlock it later (on my phone, that "7-day-no-switch-indeveloper-options" routine kicked in, but you can circumvent that) - but Knox will stay in its state. From what I read this means some things will not work such as Samsung Pay, but I do not know the details (yet) apart from that it does not bother me ;-), and the nag screen during boot is gone.
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
david.siebauer said:
Thanks for your reply. Kinda sucks. Never had problems with my former mobiles to get back totally to stock without traces. Guess I disregard rooting for now
Click to expand...
Click to collapse
Well, it's better than my Sony - there it is "once unlocked, always unlocked" with no way back at all
But I have to admit I understand the logic why the manufacturers do that, at least to the degree that they trip a fuse as Samsung does.
By rooting the phone, you shift the responsibility for the software state of the phone from the manufacturer to the user, so I think it is okay to implement something to make it clear to possible future buyers that it is or has been in that state.
(This does not include however all the other stones they put in the way of people wanting to develop or use custom ROMs!)
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features. Guess u shouldn't have bought a Samsung lol.
david.siebauer said:
I remember I also had a Xperia Z3 compact.
Main reason for me for rooting, is the ability to use tools like tasker without non root restrictions or just trying customs roms without bloat, but usefull features.
Click to expand...
Click to collapse
Oh, trust me - as soon as I hear there is a custom ROM that works as a daily driver I will root mine as well. I really hope that there will be one for this phone
david.siebauer said:
Guess u shouldn't have bought a Samsung lol.
Click to expand...
Click to collapse
Sadly there is no Fairphone mini or Fairphone Flip - or would it be Fairfliphone? ... Flipfairphone?... - yet (if ever), so the only current alternative would be Motorola. And the price tag for the Razr is simply too much, even if I personally think it looks better than the Samsung. Additionally, I do not know if they are in any way better when it comes to rooting or loading custom ROMs.