Related
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
you can always use fastboot to go back to 5.0.1
stas333 said:
you can always use fastboot to go back to 5.0.1
Click to expand...
Click to collapse
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
simms22 said:
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
Click to expand...
Click to collapse
Hmm, I guess I am confused as to what is causing the bricks for those that downgraded? I'll go ahead and do that right now but... I've read direct quotes from others stating that downgrading a Motorola bootloader is an instant brick and others have said it has happened to them.
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
gee2012 said:
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
Click to expand...
Click to collapse
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
EmperorX said:
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
Click to expand...
Click to collapse
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
EmperorX said:
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
Click to expand...
Click to collapse
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
Click to expand...
Click to collapse
I wasn't planning on it, just curious how all these people are bricking?
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flashing anymore if an incident would occur.
Click to expand...
Click to collapse
Also, I will absolutely need to relock my bootloader per organizational policies.
EmperorX said:
I wasn't planning on it, just curious how all these people are bricking?
Click to expand...
Click to collapse
Most of them because they wiped their system and couldn`t flash a image anymore because oem-unlock wasn`t enabled as i heard.
Sweet, successful downgrade!
I saw it mentioned in another thread that now that I have successfully downgraded I may brick when I get the T-Mobile 5.1 OTA.
Is there any credence to this? I am back on 5.0.1 now, relocked my bootloader, etc. Just wanted to make sure. It doesn't seem as if that would be the case to me but... Just wanted to be safe rather than sorry.
Thanks!
Disregard! Got it handled. Thanks guys!
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
Click to expand...
Click to collapse
Couldn't agree with you more....specially on the sentence I highlighted in bold. Got into the same problem yesterday. I excitedly upgraded from LMY47D to LMY47E. Later realised it's a Verizon image. So, thought let me go down to 5.0.1 and get a OTA - the "proper" way to upgrade.
While flashing, it didn't let me downgrade my bootloader. Mistake #1.
Then continued to flash the remaining images (radio, recovery, cache, system, userdata).
Then I locked my bootloader, so that it continues to look like "fresh out of the box". Mistake #2.
Then when I rebooted, it was constantly giving the error that NFC has failed and the Phone has failed. I couldn't get past those errors. It was continuously giving me that error.
It wouldn't let me unlock the bootloader, as the new bootloader (5.1) needs the OEM unlocking enabled in Developer's options.
Then I realised that there was a slight gap of time between showing the NFC & Phone error and the next set of NFC & Phone error. Using that, with great difficulty, setup the phone - going through every tap using the gap that was available between 2 sets of errors. Then I unlocked the developer's options, then enabled the OEM unlocking and finally got my bootloader unlocked.
Torrid - Horrible task. Was scared I had bricked my phone....but through some hard work (and sleepless night - up until 6am), got this finished.
Guys - seriously suggesting you NOT to lock the bootloader, IF you have unlocked the bootloader. Speaking with experience. Learn from my mistakes.
EDIT: I realised what the problem was and why NFC & Phone were erroring out. It was because I forgot to flash the Boot image. So, Bootloader & Boot were 5.1 & the rest were 5.0.1
EmperorX said:
Sweet, successful downgrade!
Click to expand...
Click to collapse
How did you downgraded the bootloader??
Downgrade of bootloader is not possible.
Sent from my Nexus 6 using XDA Free mobile app
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
How about you just leave it on D?
What do you think you will gain by changing to M?
hi everyone,
so i flashed the twrp recovery image and then my phone got stuck in a bootloop. So stupidly I relocked the bootloader and now i can't do nothing. any ideas?
No you NEVER relock the bootloader. (unless everything is fine)
There is another thread here where they were close to a solution but I didn't see the final outcome.
Sorry man. Good luck
Sent from my Google N6 on VZ
fastboot
valapsp said:
hi everyone,
so i flashed the twrp recovery image and then my phone got stuck in a bootloop. So stupidly I relocked the bootloader and now i can't do nothing. any ideas?
Click to expand...
Click to collapse
Boot to boot loader...fastboot OEM unlock confirm unlock..let the spinning android wipe your sdcard..good to go
jamescable said:
Boot to boot loader...fastboot OEM unlock confirm unlock..let the spinning android wipe your sdcard..good to go
Click to expand...
Click to collapse
u cant fastboot oem unlock when the "allow oem unlock" box hasnt been checked.
DebianDog said:
No you NEVER relock the bootloader. (unless everything is fine)
There is another thread here where they were close to a solution but I didn't see the final outcome.
Sorry man. Good luck
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
ya i know. i was drunk!
valapsp said:
ya i know. i was drunk!
Click to expand...
Click to collapse
Did you ever ticked Allow OEM Unlock before re locking?
Check this post.
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518/page16
There is a FIX.
sotnasnauj said:
Did you ever ticked Allow OEM Unlock before re locking?
Check this post.
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518/page16
There is a FIX.
Click to expand...
Click to collapse
That's not what is being said. He is saying there *may* be a link. But only 2 people have managed to fix it with that thread and 1 of them was actually bricked first, not like this but with a broken bootloader... So actually only 1 person may have fixed it with that thread.
valapsp said:
ya i know. i was drunk!
Click to expand...
Click to collapse
LOL I have been there
Sent from my Google N6 on VZ
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.
H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.
-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.
Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.
Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
wolfnumba1 said:
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
Click to expand...
Click to collapse
reboot into bootloader mode and flash that way. OTA is the worst way to update, IMO.
mikeprius said:
reboot into bootloader mode and flash that way. OTA is the worst way to update, IMO.
Click to expand...
Click to collapse
I can't flash images with a locked bootloader or is there a way around that?
wolfnumba1 said:
I can't flash images with a locked bootloader or is there a way around that?
Click to expand...
Click to collapse
the OTA wiped your custom recovery and didn't load the ROM properly !??!?!?! Yikes....................if your phone has stock recovery and the bootloader is locked then it is bricked and you need to send it in.
Device was completely stock, including recovery no custom recovery or root or anything.
That's strange....
mikeprius said:
That's strange....
Click to expand...
Click to collapse
Lol I know tell me about it.... I am going to see if motorola will send me a replacement but not to confident they will.
did you have root before taking the ota? anyways, sounds like you have the first N brick.
wolfnumba1 said:
Lol I know tell me about it.... I am going to see if motorola will send me a replacement but not to confident they will.
Click to expand...
Click to collapse
They may....I think the big question is if they still have any in stock......anyways, let us know what happens....that's a very unfortunate situation. The first thing I did when I got my phone was unlock the bootloader and I have not re-locked it since.
simms22 said:
did you have root before taking the ota? anyways, sounds like you have the first N brick.
Click to expand...
Click to collapse
No did not have root, was completely stock.
mikeprius said:
They may....I think the big question is if they still have any in stock......anyways, let us know what happens....that's a very unfortunate situation. The first thing I did when I got my phone was unlock the bootloader and I have not re-locked it since.
Click to expand...
Click to collapse
Yea sucks, device is out of warranty so I am SOL it seems. Lol I don't unlock because it breaks android pay and other security features which I did not want to disable.
wolfnumba1 said:
No did not have root, was completely stock.
Click to expand...
Click to collapse
yea, read. i was going to post when no one else posted, but had a customer walk in. by the time i posted it was too late :angel:
wolfnumba1 said:
Yea sucks, device is out of warranty so I am SOL it seems. Lol I don't unlock because it breaks android pay and other security features which I did not want to disable.
Click to expand...
Click to collapse
This is even more unfortunate. You can use Android Pay with an unlocked bootloader. I've flashed my phone back to stock images with the bootloader unlocked and Android Pay works. It's not contingent on a locked bootloader, only factory stock images.
mikeprius said:
This is even more unfortunate. You can use Android Pay with an unlocked bootloader. I've flashed my phone back to stock images with the bootloader unlocked and Android Pay works. It's not contingent on a locked bootloader, only factory stock images.
Click to expand...
Click to collapse
Oh weird, when you check off the allow oem unlock it says disabled security features, I wonder what that means then... yes it sucks, now a very nice looking paperweight lol
wolfnumba1 said:
Oh weird, when you check off the allow oem unlock it says disabled security features, I wonder what that means then... yes it sucks, now a very nice looking paperweight lol
Click to expand...
Click to collapse
That's just a general warning. No bearing on AP.......well you may be able to sell the phone as some people may buy it. I'm sure someone out there has a way to get it back, but I'm not sure how. I recall seeing a thread where someone in Cambodia did the same thing and he took it to a shop that was able to reverse it.....
mikeprius said:
That's just a general warning. No bearing on AP.......well you may be able to sell the phone as some people may buy it. I'm sure someone out there has a way to get it back, but I'm not sure how. I recall seeing a thread where someone in Cambodia did the same thing and he took it to a shop that was able to reverse it.....
Click to expand...
Click to collapse
Lol really? Recall where?
wolfnumba1 said:
Lol really? Recall where?
Click to expand...
Click to collapse
I can't find the thread, but I did find this one:
http://forum.xda-developers.com/nexus-6/help/nexus-6-bricked-november-security-ota-t3242773
It looks like you are not the first to be bricked with an OTA update. There should be a sticky about this issue moving forward.
mikeprius said:
I can't find the thread, but I did find this one:
http://forum.xda-developers.com/nexus-6/help/nexus-6-bricked-november-security-ota-t3242773
It looks like you are not the first to be bricked with an OTA update. There should be a sticky about this issue moving forward.
Click to expand...
Click to collapse
Lol so ****ty, looks like the phone is ****ed
wolfnumba1 said:
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
Click to expand...
Click to collapse
Count me in as one of the potentially many more that bricked his phone while trying out the Beta program via OTA...
sorry to tell you this , but with locked bootloader , your phone is hard bricked, no way to recover, only by sending it back to motorola or amazon if you bought from them. i sold about 100 pieces of nexus 6 to customers and my first advice to them is to check " Enable oem unlocking "
anyway email google and blame them for this and i am sure they will help
Hey friends, so yesterday i decided to try and root my Moto X 2nd gen.
I first did a full backup using ADB, then i unlocked my bootloader, after the unlocking of the bootloader it restarted and and went to the 'Warning bootloader unlocked' but boots up normally. I set up a few stuff after reboot since everything was wiped. Then i rooted using Kingoroot's desktop client and when it finished i restarted my phone and there it got stuck at the Warning screen indefinitely.
Please help me, i'll be on a trip to the province and i need a usable phone.
Thanks a bunch in advanced fellow users! :fingers-crossed::fingers-crossed:
BRO I Don't KNOW WHAT TO DO NOW BUT ILL SUGGEST U TO DOWNLOAD STOCK ROM AN FLASH IT
ImRavi006 said:
BRO I Don't KNOW WHAT TO DO NOW BUT ILL SUGGEST U TO DOWNLOAD STOCK ROM AN FLASH IT
Click to expand...
Click to collapse
Are you having the same problem bro?
_pseudoimage said:
Hey friends, so yesterday i decided to try and root my Moto X 2nd gen.
I first did a full backup using ADB, then i unlocked my bootloader, after the unlocking of the bootloader it restarted and and went to the 'Warning bootloader unlocked' but boots up normally. I set up a few stuff after reboot since everything was wiped. Then i rooted using Kingoroot's desktop client and when it finished i restarted my phone and there it got stuck at the Warning screen indefinitely.
Please help me, i'll be on a trip to the province and i need a usable phone.
Thanks a bunch in advanced fellow users! :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
What is your phone model? XT1092/XT1096/XT1097? Who is your carrier?
What version of the OS was running when you tried to root?
If you unlocked your bootloader then Kingroot was not needed to root, there are other methods.
donslade said:
What is your phone model? XT1092/XT1096/XT1097? Who is your carrier?
What version of the OS was running when you tried to root?
If you unlocked your bootloader then Kingroot was not needed to root, there are other methods.
Click to expand...
Click to collapse
Hi, i got the XT1092 version and my carrier is Globe Telecom ( Philippines )
running marshmallow 6.0
Hope you could help me out!
I don't know why you rooted with kingroot if you already unlocked your bootloader...
You can flash twrp and then super su, this is safer.
Anyway, since you unlocked the bootloader, flash twrp and then flash the stock 6.0 xt1095 version, you can find that in the android development section. It will work on your xt1092, don't worry.
I have xt1096 with this os...
Hope you fix it !
OrenGazala said:
I don't know why you rooted with kingroot if you already unlocked your bootloader...
You can flash twrp and then super su, this is safer.
Anyway, since you unlocked the bootloader, flash twrp and then flash the stock 6.0 xt1095 version, you can find that in the android development section. It will work on your xt1092, don't worry.
I have xt1096 with this os...
Hope you fix it !
Click to expand...
Click to collapse
Thanks for the reply! gonna try it out tomorrow!
and by the way Kingo doesn't retain its root after reboot if your device's bootloader is locked so i thought i'd unlock first then use Kingo. but anyway thanks again!
_pseudoimage said:
Thanks for the reply! gonna try it out tomorrow!
and by the way Kingo doesn't retain its root after reboot if your device's bootloader is locked so i thought i'd unlock first then use Kingo. but anyway thanks again!
Click to expand...
Click to collapse
Lol no problem.
Update us how it is going
OrenGazala said:
Lol no problem.
Update us how it is going
Click to expand...
Click to collapse
hey bruh! finally got it working and rooted!
Thanks to your advice.. *high five
Now last question, since my device transitioned from XT1092 to XT1095 are there any drastic changes or is it really just a number change i'm a bit worried bout that.
Thanks again!
_pseudoimage said:
hey bruh! finally got it working and rooted!
Thanks to your advice.. *high five
Now last question, since my device transitioned from XT1092 to XT1095 are there any drastic changes or is it really just a number change i'm a bit worried bout that.
Thanks again!
Click to expand...
Click to collapse
Hey man, happy to hear that!
In my gmail I saw the post befire you edited it and I was like "wow.. what is that problem?!" and then I entered the forum and saw it worked!
You don't need to worry about that change... xt1092 and xt1095 is exactly the same phone, just xt1095 called "pure" and xt1092 is for india or europe carriers.
Well, you don't need to worry at all from that change!
Since you don't need the CDMA verizon offers, you are good.
Well, I'm happy that it's working to you!
My pleasure to help.