[Official] Note 3 Verizon Bootloader Unlock

[audit2]

I found this number on the Web for Verizon SMSC +316540951000 fill the input line with it , good luck!!![emoji2]

Thanks for your help but the input line won't let you type in anything, Its just a drop list like you have in the screenshot.

Thanks

 

[hasansabuz]

anything for our att note 3 ... plz

 

[DeliriousSyntax]

I'm running Music of life v9 is 5.1.1 N5 port, running very well, I unlock my OF1 bootloader being on Jasmine 6.1; then install TWRP ; I flash MoL v9 no reboot; then flash idleKernel-hlte-vzw-6.6.5-note5port, for last flash super Su 2.46, all is running really fine [emoji2]

Sent from my SM-A710Y using XDA-Developers mobile app

That's awesome! if you could make some specific directions for getting the rom to install that would be greatly appreciated

 

[mightysween]

That's awesome! if you could make some specific directions for getting the rom to install that would be greatly appreciated

Let me know and I will add it to my "working VZW ROMs" thread...and we can keep the unlock thread a little cleaner that way too

 

[MayoRamirez]

Let me know and I will add it to my "working VZW ROMs" thread...and we can keep the unlock thread a little cleaner that way too

I want to make a post with all the files and instructions, I already contact dev to ask for the team permission as soon as I get will made and let you know, audit2 had a trouble with SMSC, since I don't use Verizon network and use GSM /LTE network looks like didn't affect me, I been trying to find a way to modified that for Verizon, but I need someone with the ROM test it in Verizon net.

That's awesome! if you could make some specific directions for getting the rom to install that would be greatly appreciated

As soon as I get permission for MoL Team to use their links I will make a post with step by step it's to simple but will be easy with the right links to the files [emoji2]

Sent from my SM-A710Y using XDA-Developers mobile app

---------- Post added at 05:22 PM ---------- Previous post was at 05:11 PM ----------

I found this number on the Web for Verizon SMSC +316540951000 fill the input line with it , good luck!!![emoji2]

Thanks for your help but the input line won't let you type in anything, Its just a drop list like you have in the screenshot.

Thanks

Did you already rollback to Jasmine right? I was trying to find a way using service mode to modify SMSC with no luck, but this morning while I was trying, I corrupt my network so(no signal, no SMSC, and no options in settings to replace it anymore all was gone no Lte/gsm/CDMA option in menu [emoji17]) , to fix that I make some research on the Web to access hidden menu from any app and voaila advanced signal status app grant me access so I recover the Lte/gsm/CDMA option in menu and could place my network SMSC manually; I strongly believe this will be the solution for Verizon network on this ROM.

Sent from my SM-A710Y using XDA-Developers mobile app

 

[DaninVT]

I ran this and everything worked fine. I had to ODEN back to 5.0 and lost the bootloader. I ran it again and it unlocked, etc... Now my SIM card wont work. After checking the CID, it still shows the CID it was changed to, not my CID.

Any idea how I can switch it back to my CID?

Hi, this is my first post. I followed the LordLugo Youtube video on unlocking the bootloader and installing CM13 and my SIM card stopped working as well. I'm using Straight Talk on the Verizon network. I had to call Straight Talk technical help and after 45 minutes or so the helpful fellow got my phone's SIM card working again. It sounded like my phone was put on some "Prohibited" list or something. I didn't get a detailed explanation (nor did I ask), but it sounded like Verizon had blocked my SIM card. The gentleman from Straight Talk needed to contact Verizon to get my SIM card unblocked. I had to give him my physical address (and last four IMEI numbers and a few other details) so that he could locate my phone I don't know if that helps anyone. I went back to using Jasmine ROM and am fearful to try unlocking the boot loader again.

 

[davekaz]

He is on at+t. That's why that cm 13 works for him..are you unlocked still..I'm on Verizon and have a link for Verizon cm13 that a member of this community edited to make it work with verizon


Sent from my unknown using Tapatalk

 

[audit2]

[/COLOR]

Did you already rollback to Jasmine right? I was trying to find a way using service mode to modify SMSC with no luck, but this morning while I was trying, I corrupt my network so(no signal, no SMSC, and no options in settings to replace it anymore all was gone no Lte/gsm/CDMA option in menu [emoji17]) , to fix that I make some research on the Web to access hidden menu from any app and voaila advanced signal status app grant me access so I recover the Lte/gsm/CDMA option in menu and could place my network SMSC manually; I strongly believe this will be the solution for Verizon network on this ROM.

Sent from my SM-A710Y using XDA-Developers mobile app

Never heard of hidden files but that could be the reason I my menu didn't match yours. I'll reflash later.

Thanks

 

[MayoRamirez]

That's awesome! if you could make some specific directions for getting the rom to install that would be greatly appreciated

HI mate I make a thread with all info and instructions for flashing this ROM
http://forum.xda-developers.com/showthread.php?t=3363367

Sent from my SM-A710Y using XDA-Developers mobile app

 

[davekaz]

So this works with 900v with Verizon sim card?

Sent from my unknown using Tapatalk

 

[Quickpaw]

Confirmed that it works!

I can confirm that the .apk from post #29 works!

I was originally on JasmineROM v5.0.1 with root with Safestrap. Nothing fancy. I'll quickly do a rundown of what I went through, as some people seem to have similar issues:

• ATTENTION 1: The .apk requires an external microSD Card to be installed. BE SURE TO BACKUP BEFORE YOU DO THIS.
• The unlock .apk does require Busybox and Root/SuperSU. JasmineROM had it built in, so I was good on that end.
• Lookout Security did flag the unlock .apk on my phone, but I turned it off, and it installed.
• When I ran the unlock program, it asked for SU permissions, I granted it, and it ran.
• Terminal did not open with an option to choose "YES", so after reading a few posts, I found out I had to uninstall my version of Terminal Emulator from my phone.
• I re-installed the .apk, it installed, and after about 20 seconds, it automatically opened it's own version of Terminal, and gave me the "YES/NO" option. I typed "YES", and it started.
  ----------------------------------------------
• ATTENTION 2: As stated before, you need to have a external microSD Card installed (larger than 1gb, I believe) before this can successful complete. BE AWARE THAT THIS WILL SCREW UP YOUR PARTITION/DATA. It did for me.
• Once completed, my phone turned off, I started it back up, shut down again, went into Download mode (Down Volumn + Home + Power), and sure enough, it says I'm in Developer Mode.
• I installed TWRP (twrp-3.0.2-0-hltevzw-4.4.img) using Flashify (from Google Play Store), and then installed JasmineROM v6.1 (I wiped Cache/Data/System before installing. And the ROM only, no partial firmware packages for Odin). Everything is working great so far! Yes, I'm still unlocked! Also, I formatted my external microSD from the Android storage menu after everything was done, for good measure.

 

[audit2]

So this works with 900v with Verizon sim card?

Sent from my unknown using Tapatalk

Sms doesn't work on Verizon. I'm still trying to sort it out but no luck.

 

[davekaz]

OK thanks

Sent from my unknown using Tapatalk

 

[MayoRamirez]

Sms doesn't work on Verizon. I'm still trying to sort it out but no luck.

Did you install the advanced signal status? Once there, hit additional info/ device info there get your network best network settings and set manually or refresh your SMSC

Sent from my SM-A710Y using XDA-Developers mobile app

 

[bradg24]

I rooted, then installed busybox, then took one of the one click apk. All looked good so far as it asked yes. So I typed yes as it shut down I powered it back up, then followed the op in download a debug app to check to see if 15 was the first number. Now flashed twrp with flashfy and bang softbrick with the triangle sign..
Is there another way to check to see your unlocked before you flash twrp? I followed direction as I thought it was written.

Sent from my LG-VS985 using Tapatalk

 

[BackCheck]

I rooted, then installed busybox, then took one of the one click apk. All looked good so far as it asked yes. So I typed yes as it shut down I powered it back up, then followed the op in download a debug app to check to see if 15 was the first number. Now flashed twrp with flashfy and bang softbrick with the triangle sign..
Is there another way to check to see your unlocked before you flash twrp? I followed direction as I thought it was written.

Sent from my LG-VS985 using Tapatalk

Boot into download mode (hold volume down + home during on power up) and see if it says "MODE: Developer".

 

[stoph8n24]

I rooted, then installed busybox, then took one of the one click apk. All looked good so far as it asked yes. So I typed yes as it shut down I powered it back up, then followed the op in download a debug app to check to see if 15 was the first number. Now flashed twrp with flashfy and bang softbrick with the triangle sign..
Is there another way to check to see your unlocked before you flash twrp? I followed direction as I thought it was written.

3 or 4 posts above yours had a step by step with the one-click. Just check after the process by going to Download Mode and seeing Developer mode in top left.

 

[bradg24]

Thanks..

Sent from my LG-VS985 using Tapatalk

 

[bftb0]

@ryanbg

You are a beast, sir. I just casually dropped in here after a very long absence and saw this. Your persistence is remarkable. If I end up doing this you've got some beer money coming your way. (Believe it or not I am still using MJ7 and Safestrap - didn't want to give up the tether bug.)

I went over to @beaups github repository and read through the code, and looked at some constants & blob values in your binary.

I'm sort of mystified by the SD Card backup - it happens on the 2nd invocation of the program, just before the dev_sig blob is kanged into ABOOT. Is it used following the second reboot? Maybe the kanging somehow trips the "boot from SD card and overwrite mmcblk0 with it's contents" mode?

I assume that your dev_cid and dev_sig are a matched pair from a legit VZW dev phone & that there is no currently known means to avoid having all users of this method share the same CID value. (I vaguely remember that all dev edition users had unique sig blobs, indicating that the signing operation occurs with a either with a unique hardware private key on the phone itself - or one-time only at the factory, so that use of ODIN on a dev phone destroys the "dev edition" status)

Not a huge deal unless big red decides to squash all users of a single CID... including the dev edition owner with the legitimate device.

Ignoring the obvious need of the ioctl to be present in the phone's kernel (& root privilege), does this method implicitly require a specific release, or is the cid <==> sig pair sort of independent of the contents of aboot/tz/sbl1 etc?

Thanks for your hard work and everything you have done for the wider Galaxy community.

bftb0

 

[beaups]

@ryanbg

You are a beast, sir. I just casually dropped in here after a very long absence and saw this. Your persistence is remarkable. If I end up doing this you've got some beer money coming your way. (Believe it or not I am still using MJ7 and Safestrap - didn't want to give up the tether bug.)

I went over to @beaups github repository and read through the code, and looked at some constants & blob values in your binary.

I'm sort of mystified by the SD Card backup - it happens on the 2nd invocation of the program, just before the dev_sig blob is kanged into ABOOT. Is it used following the second reboot? Maybe the kanging somehow trips the "boot from SD card and overwrite mmcblk0 with it's contents" mode?

I assume that your dev_cid and dev_sig are a matched pair from a legit VZW dev phone & that there is no currently known means to avoid having all users of this method share the same CID value. (I vaguely remember that all dev edition users had unique sig blobs, indicating that the signing operation occurs with a either with a unique hardware private key on the phone itself - or one-time only at the factory, so that use of ODIN on a dev phone destroys the "dev edition" status)

Not a huge deal unless big red decides to squash all users of a single CID... including the dev edition owner with the legitimate device.

Ignoring the obvious need of the ioctl to be present in the phone's kernel (& root privilege), does this method implicitly require a specific release, or is the cid <==> sig pair sort of independent of the contents of aboot/tz/sbl1 etc?

Thanks for your hard work and everything you have done for the wider Galaxy community.

bftb0

The backup is triggered after the first reboot (cid change) and before aboot is modified. Its just a safety mechanism.

--beaups