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
I know I shouldn't be posting here because I'm not a dev, but I'm trying to be. I figured this is the best place to ask.
So I picked up a USC galaxy s3 for $20. I fix phones so I figured I'd just use it as parts. USC has left from my area. So the phone is basically useless. I'm on a gsm carrier now so I don't want to flash it.I figured why don't I mess around with it and use it as a learning experience. I want to unlock the boot loader and gsm. I don't care if I brick the phone. This is my test dummy for better understanding android and EFS.
What I have tried so far:
Bricked the phone trying to flash vzw vralec boot loader.
Recovered the phone using a recovery sd
I got a stock Verizon rom running on the phone and hoped I would be able to update through that.
Flashed a sprint radio and a *2 connected to sprint
Tried using casual and EZ1.4 to unlock bootloader.
I realize now this was all a waste of time.
Aboot.mbn is the boot loader right? When the bricked phone connects as QH-Load that is when the device connects as the boot-loader? I’ve bootloader unlocked my CDMA xperia R800x play before using se-tool. Can you do this on the R-530U when using SGTool? Where do you start with unlocking the bootloader? How did the guy who developed casual figure it out? How do you bypass these checks? Can someone explain in-depth the security checks that are in place. If I manage to unlock my boot loader would I then be able to install a different one like of a sprint or verizon device? I have CDMA workshop and se-lg fusion box.
I’ve seen this guide:
“If you root it then upgrade to AOKP 4.1.2 custom ROM or any other custom or stock style ROM thats 4.1.X (Jelly Bean), then there is a REALLY easy trick. I know it's harder for US Cellular only because they are still using 4.04 ICS which doesn't support the menu you need to do this, you need JB for this trick, if you have it stock like on T-mobile then no rooting or upgrading needed, but US Cellular it is. I used it to unlock my tmobile, and my friend and mom both have us cellular. After you Unlock it you can always go back to stock if you want, just make sure and after you root but before you upgrade the ROM you do a nandroid backup to go back to. After you have a Jelly Bean ROM installed,
1. Type *#197328640# and it brings up the factory service menu (very usefull)
2. Select (1) UMTS
3. Select (1)Debug Screen
4. Select (8) Phone Control
5. Select (6)Network lock
6. Inside the Network lock menu, Pick option (3) Perso SHA256 off, Passed that is a screen that says something like "no options in this menu, current command is 11863", Wait for 30-60 secs, from there hit the menu button on bottom left of phone to bring up options, Select "Back".
7. The last command should have brought you back into the Network Lock menu, at the bottom is (4) NW Lock NV Data Initialize, Select it. You might be asked a saftey are you sure, some people not, after it begins that process wait a good 60 sec the reboot. Thats it! Phones Unlocked
It would be good for you to root and upgade a custom JB 4.1.x or higher ROM anyways as they have support and menu options for working on all CDMA/GSM/LTE Networks. Even if you unlock your phone using the IMEI number and paying 20$ for the unlock code, you will still need JB. They also have apps on the play store specifically for galaxy s3's, capable of unlocking for allot cheaper if your phones rooted.
Good Luck!”
But it doesn’t have the options for USC. Here’s my plan: Bootloader->Flash Sprint Bootloader->Flash Sprint ROM/Radio-> Follow above steps for GSM Unlock
Am I out of my mind or is this possible? Again I don’t care if I brick the phone. I’m using this as a hands-on learning experience instead of just reading things and not understanding them. Essentially an i535, R530, and L710 are the exact same physical device, just running different firmware?
I don't think your gs3 has a locked bootloader plus a CDMA phone cannot become gsm.
Sent From My Smoking Hot Galaxy SIII
Haha I used to be a r800x user too!!!!
Sent from my ATT Samsung Galaxy SIII using TapaTalk
The S3 is a global phone so it does have the hardware for GSM networks, you need a SIM card for that network though obviously.
Ignore me... I'm apparently a blithering idiot who can't read ^_^
The Verizon S3 is able to use GSM, But you will only have Edge (Go to mobile network settings and change it to global). Another downfall is if you upgrade OTA you will have a locked bootloader.
Hello Community!!
Noobiest noob here. Please forgive my ignorance.
Sony Xperia TL [LT30at] AT & T phone.
Android version: 4.1.2
Build: 9.1.F.1.120
Here is my issue:
I now need to use this phone in India with a different network provider, but i don't want to spend money on unlocking the phone for a new sim card. I read a bit about flashing a custom ROM and watched Jeremy Phan's video: "3 ways to root your (xperia) android: tool kits, kernel flashing, recovery"
I installed sony's pc companion and update service, i also installed the flash tool on my machine.
a) will flashing the phone do the trick?
b) if so i'm having a tough time finding the right firmware for this phone. Please link me to a robust and hazel free firmware for my phone.
thanks a ton
micky
Hi Micky,
You cant unlock your phone (remove SIM lock) from the operator by reflashing it. You will need an unlock code for that. A legal way is to obtain it from AT&T if your contract is ended, the other one is to buy it, e.g. on eBay. Once you'll get it, just enter a simple key combination to get into service menu, go to appropriate menu item and enter that code there, after that your phone is unlocked, no reflash needed.
Hope that helps.
Hi summer,
Thanks a lot for your insight. I've been searching all the corners of the internet for a while now, with a vengance I think it should be time to drop those efforts.
Please bear with me, i'm trying to think out loud here - Is there no way i can tweak the phone to accept any sim card? Like by disabling a few settings or hard coding some part after gaining root access?
Buying an unlock code is not an option for me at this point, and i don't want to use the phone just to check email and take pictures
many thanks
SIM lock information is not stored somewhere in firmware, which you can access by gaining root permissions. I assume there may be some tricks similar to Turbo SIM in iPhone where you can emulate the correct SIM, but its definitely not worth it.
I'm rooted via ODIN with TWRP. I got a browser hijacker that put my browser home page to some stupid ad, so I tried to get rid of it using the AVG antivirus program. That program recommended I disable "developer mode" on my phone ... and like a total idiot I followed their instructions.
Next time I tried to boot ... I get the "Custom Binary blocked by FRP Lock" message.
I am on vacation and I REALLY need my phone. I can't believe Samsung can just lock me out of my own phone like this. I can get into download mode. Do I try to reflash with Odin or what?
ANY help would be greatly appreciated ...
EDIT: forgot to mention I was on Nougat stock ...
Haints said:
I'm rooted via ODIN with TWRP. I got a browser hijacker that put my browser home page to some stupid ad, so I tried to get rid of it using the AVG antivirus program. That program recommended I disable "developer mode" on my phone ... and like a total idiot I followed their instructions.
Next time I tried to boot ... I get the "Custom Binary blocked by FRP Lock" message.
I am on vacation and I REALLY need my phone. I can't believe Samsung can just lock me out of my own phone like this. I can get into download mode. Do I try to reflash with Odin or what?
ANY help would be greatly appreciated ...
EDIT: forgot to mention I was on Nougat stock ...
Click to expand...
Click to collapse
No one is willing to advise me on this ... ?
Odin back to stock seems to be the only way forward? At the same android os level or higher?
flash back stock firmware and next time never disable oem unlock in developer options on rooted phone
Haints said:
No one is willing to advise me on this ... ?
Odin back to stock seems to be the only way forward? At the same android os level or higher?
Click to expand...
Click to collapse
You need to call T-Mobile and request that they help you because this FRP lock deals with stolen phones, which I'm not accusing you of. Just saying.. If you Odin back it's going to ask for the original Google account info and password and if you have that just enter it into the phone and then you'll be able to get back into the phone to enable it again. But if you don't have the Google account and password, that's a problem.
AntonPres said:
flash back stock firmware and next time never disable oem unlock in developer options on rooted phone
Click to expand...
Click to collapse
I just finished doing exactly as you describe when I checked back here to see if anyone had responded. So even though I had successfully reflashed my phone before I saw your advice, I still appreciate you're willingness to help and the fact that your solution is the correct one.
I've been rooting my phones for years and had never heard of the developer mode warning or run into FRP lock before. I won't forget either now, though.
In case anyone else runs into this issue:
I found my exact stock tmobile rom on sammoble ( sign up, use free download mode, takes forever but it is free) and downloaded the tar/mdf file.
Used Odin3 v3.11, select AP then find your tar/mdf file.
Put phone into download mode and when Odin recognizes it, hit start.
I thought it looped at the tmobile logo but it just took a while so be patient.
Not only do I have a fully working phone again, but contrary to what I had read--that the only way to defeat the FRP lock would entail losing all my data--I lost NOTHING. My phone is EXACTLY the way it was before, including the fact that Developer mode is now enabled AGAIN. How is that possible? I don't know, but I'm very very happy that all I lost was time.
you only lost root, flashing same version explains that you didn't lost your data
MrMike2182 said:
You need to call T-Mobile and request that they help you because this FRP lock deals with stolen phones, which I'm not accusing you of. Just saying.. If you Odin back it's going to ask for the original Google account info and password and if you have that just enter it into the phone and then you'll be able to get back into the phone to enable it again. But if you don't have the Google account and password, that's a problem.
Click to expand...
Click to collapse
When I Odin'ed back it didn't ask me for anything--my phone was exactly the way it was before.
Phone is not stolen. I bought it used off craigslist and had the seller meet me at a tmobile store to verify that it was clean before I bought it. I
This happened while I was on vacation and I really, REALLY needed a working phone. Called samsung and the first rep I spoke to in India--as soon as she heard "FRP Lock," she basically said: "You're ****ed." She also said it was my fault that I had a crippled phone because I never should have rooted it in the first place. When I argued that the root hadn't crippled my phone,--I'd been using it rooted for months with no issues--but that the FRP lock had crippled it, she said FRP lock wasn't Samsung's fault, but Google's fault, and if I needed a solution to FRP lock, I should talk to Google. Classic buck-passing mode. Like Google would have helped me.
Second rep I spoke to was much more helpful, even though she couldn't really help me. She eventually suggested I get the IMEI from tmobile, then send my phone into Samsung and they would fix it--at my cost, presumably.
Thanks to the power invested in me by the internet, however, I didn't have to find out what would have happened if I'd sent my phone to Samsung.
Happy, happy day, and good luck to anyone who runs into this issue in the future!
Haints said:
When I Odin'ed back it didn't ask me for anything--my phone was exactly the way it was before.
Phone is not stolen. I bought it used off craigslist and had the seller meet me at a tmobile store to verify that it was clean before I bought it. I
This happened while I was on vacation and I really, REALLY needed a working phone. Called samsung and the first rep I spoke to in India--as soon as she heard "FRP Lock," she basically said: "You're ****ed." She also said it was my fault that I had a crippled phone because I never should have rooted it in the first place. When I argued that the root hadn't crippled my phone,--I'd been using it rooted for months with no issues--but that the FRP lock had crippled it, she said FRP lock wasn't Samsung's fault, but Google's fault, and if I needed a solution to FRP lock, I should talk to Google. Classic buck-passing mode. Like Google would have helped me.
Second rep I spoke to was much more helpful, even though she couldn't really help me. She eventually suggested I get the IMEI from tmobile, then send my phone into Samsung and they would fix it--at my cost, presumably.
Thanks to the power invested in me by the internet, however, I didn't have to find out what would have happened if I'd sent my phone to Samsung.
Happy, happy day, and good luck to anyone who runs into this issue in the future!
Click to expand...
Click to collapse
What I meant by Odin back was you can get back into the phone and just re-enable the OEM unlock in developer settings and you won't have to worry about the FRP crap again.. And you're right I highly doubt Google would have given a crap and gave you the run around again.
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.