Database Users

Why one should never unlock the Motorola Razr HD bootloader (xt925) !

The pro & cons of unlocking the bootloader:
Pro: Install customs ROMS with custom kernels (basically that's it)
Cons: - Loosing warranty from Motorola & your carrier
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
If someone can add some Pro's to an unlock bootloader please do it..

Are you sure about the firmware upgrades? I read somewhere that's not the case.

I wish I had known all this before I unlocked my phone.

Are you sure about the firmware upgrades? I read somewhere that's not the case.
Click to expand...
Click to collapse
I spoke to Motorola & my carrier services, also read the warning details before the unlock process begins.
I wish I had known all this before I unlocked my phone
Click to expand...
Click to collapse
Same here..(I learned all that after the fact)

I'd add this to Pro:
If you're stuck on Rogers 49003 ICS because you flashed the ROM trying to get root, your best option to get anything above 4.0.4 is to unlock bootloader?

Perhaps a CWM install will be possible for those with unlocked bootloaders when updates come.
It seems that in one form or another an unlocked bootloader means being able to push all the new files in doesn't it? Is there any limitation on this phone, for example flashing a new modem or kernel?

Cons one by one:
itzik_man said:
- Loosing warranty from Motorola & your carrier
Click to expand...
Click to collapse
True, but obvious.
itzik_man said:
- No more firmware upgrades (your IMEI is dropped out of Motorola databank)
Click to expand...
Click to collapse
Nope. Even if you were not to receive OTA, which by the way is not true as I've observed on my Photon Q, you can still freely flash the new firmwares yourself ^^
itzik_man said:
- Little verity of quality custom ROMs or development (close to none) exist for the Razr HD
Click to expand...
Click to collapse
Depends on ones point of view. Usually a CM port means you get newer Android sooner.
itzik_man said:
- Future upgrade to JB & KLP will never happened (this phone is listed as a potential candidate for KLP update)
Click to expand...
Click to collapse
Why it wouldn't? Unlocking BLs has no impact on upgrade schedule.
itzik_man said:
- Keeping your xt925 beyond your 1 year warranty will still guaranty, a steady upgrades of firmware
Click to expand...
Click to collapse
No. That's solely on Moto / Google decision. They don't have to update it at all. (See Droid 3, Milestone 3, Motorola XT720 etc.)
itzik_man said:
- Can root a phone with bootloader locked (without loosing warranty - root is reversible)
Click to expand...
Click to collapse
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
itzik_man said:
- Legally (Motorola binding Bootloader unlock contract), you can't sell a BL unlock Motorola Razr HD phone !
Click to expand...
Click to collapse
You can sue Moto for breaking laws. They can't forbid you doing that (don't know honestly how is that in US / Canada, but I doubt that seeing how it works with computer games).
So please, while for normal user not willing to flash custom ROMs it's true that they should not unlock the bootloader, don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.

don't spill nonsenses around that. It's just that when you unlock your bootloader, you're on your own when playing with the firmware. But when you have stock firmware back on it, nothing prevents you from getting the OTA.
Click to expand...
Click to collapse
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...

At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.

itzik_man said:
Possible 90% of your response represent just false theories..
OTA is goneforever once you unlock your bootloader ! If & when you be able manually to install JB, still your IMEI (not registered with Motorola) wont OTA.
You can sue nobody ! it's a contractual agreement you "sign" when you agree to unlock BL !
And if you can't OTA, No future auto upgrades.
So, before you use a statement "don't spill nonsense" make sure you are talking sense...
Click to expand...
Click to collapse
Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.

I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.

We should be promoting "unlock the world"
This is not to imply everything should be free, however if I own something it should be mine in every regard, that includes breaking it.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
@skrilax thanks for you work on the a500.
Sent from my Galaxy Nexus using Tapatalk 2

I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.

Once again.
A) The reason why the page says "no updates" is beacuse OTA updates only work when you're on stock firmware, which is unlikely when you have the bootloader unlocked. That's all.
B) There are things that such "agreement" cannot contain. Being unable to sell the phone is one of them in most countries.
Click to expand...
Click to collapse
To end my part in this discussion: The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !

Darbness said:
I have xt925, first thing I did was unlock boot loader. Then I updated ota to Telstra JB. OP is misleading people.
Click to expand...
Click to collapse
Have you tried out lte tethering? It doesn't work on Rogers.

To epinter -
I disagree from the op.
Every change to device firmware compromises the warranty, not just bootloader, read the agreements ... If you exploit a bug to have root access, you will have to fool everyone who will have contact with your phone so they don't see what you have done. Even if you try to "reverse" the root, you(or the program you use) will always leave a trace.http://www.linuxmobile
Click to expand...
Click to collapse
I did not notice your response at first, now to the point -
Without any disrespect to the work, time & effort invested, the main point is being ignored by the developers: All comments I got on this OP didn't touched the number one reason of my suggestion to not unlock the bootloader: There in not really enough of a variety of development options today to justification the bootloader unlocked of the xt925.

Skrilax_CZ said:
Cons one by one:
Yes, although you have to be careful, because there are scirpts checking if you're rooted.
Click to expand...
Click to collapse
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Tombs1234 said:
At least on my O2 Germany xt925 I got the update OTA from ICS to JB after unlocking. Had to return to the stock bootloader because the OTA relies on it after rebooting though.
Click to expand...
Click to collapse
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?

itzik_man said:
The limitations, restrictions & disadvantages of unlocking the bootloader are much greater then any benefit or gain under the current availability of development !
Click to expand...
Click to collapse
It's your decision whether to unlock the bootloader or not. I'm just saying (for other users) that many of the cons you wrote were absolutely incorrect.
PantsDownJedi said:
Can someone elaborate on this point; I read in another thread that when you remove all rooted apps and data, clear out the files left in /system, that there is still info stored stated if the device has ever been rooted, and that this can be cleared using an app on a PC (don't remember which) however when I looked at the app it was specific to the XT926 and thus I wouldn't be able to use it.
After a thorough clean of every rooted app and everything left behind by rooted apps, is there a known way (or assumed to be working way) on XT925 to erase the record of the root.
Also, assuming I was to get my phone back to that state and remove proof of root, what specifically do I need to do in order to be careful as stated... or is epinter correct in saying that there is always a trace left behind, and if so, is this a blatant trace or something that hasn't been of much concern for Motorola in the past when servicing phones?
Click to expand...
Click to collapse
I believe there is something stored in the pds partition. Or at least it is that way on Droid RAZR XT912 and you had to fix it to remove the remaining traces. Flashing FXZ is also a way how to get a clean stock firmware, but pds partition is not affected that way.
PantsDownJedi said:
How would I return to a stock bootloader if I were to unlock mine and an OTA didn't work? How did you do it?
Click to expand...
Click to collapse
I think he meant "stock firmware" instead of "stock bootloader"

So if that were the case on this phone, I wonder if doing a dd backup of the pds partition before rooting at ICS, for restoring after downgrade, would be the way to go. Assuming it restores properly, it would be a good thing to add to the sticky thread about rooting. I did a dd of all my partitions except for /data last night, but I'm already rooted.
hmm... I'm wondering if there's something inaccessable in /system or even the sdcard since they get mounted with fuse. My only other Android phone was the Galaxy S II which was pretty straightforward and dead simple to root and unroot. I was surprised to see the fuse module being used to mount anything when I got this one.

The original topic is here: http://forum.xda-developers.com/showthread.php?t=1857558
I don't know if there was a proper fix developed (haven't checked) on the RAZR.

[LOLLIPOP WARNING]Those Who Unlocked Via Sunshine or Purchasing a Code from China

There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.

JulesJam said:
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
Click to expand...
Click to collapse
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
I can't imagine the OTA would lock the bootloader, but who knows...

fury683 said:
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
Click to expand...
Click to collapse
But others relocked after unlocking and didn't check the box then flashed something, ended up in a bootloop and were unable to unlock again to repair their phones.
Regardless, you cannot rely on what happens with a Nexus device. These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
fury683 said:
I can't imagine the OTA would lock the bootloader, but who knows...
Click to expand...
Click to collapse
I don't think it will relock the bootloader either. I am more concerned about those who relock then take the update not realizing that they will not be able to unlock again.

JulesJam said:
These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
Click to expand...
Click to collapse
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Didn't intend to say you were wrong in my first post, just that people had the same thoughts when the N6 came out and it wasn't a problem. People freaked out when My Verizon updated a while back and it requested root permissions, too. It's an abundance of caution, I get it.

fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Click to expand...
Click to collapse
The GSM Dev Ed is not identical to the AT&T MX13. But still, so what? None of us know how this is going to be implemented in 5.1. We can speculate all we want but we will know for sure once it is released.
fury683 said:
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Click to expand...
Click to collapse
Rather than take the OTA, I would use Motorola Device Manager to upgrade - it leaves a copy of the fxz on your computer.

fury683 said:
, just that people had the same thoughts when the N6 came out
Click to expand...
Click to collapse
No, they could not have had the same thoughts as the N6 was always an unlockable device. You don't have to use Sunshine or purchase an unlock code to unlock the N6. So whatever thoughts anyone has had about the Enable OEM Unlock feature wrt how it would work with the N6 have nothing at all to do with this thread. The situations are totally different.
fury683 said:
and it wasn't a problem
Click to expand...
Click to collapse
On the contrary - it has been quite a problem for a lot of people with N6's who relocked their bootloaders. That is well documented on the N6 forum.

Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?

Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..

Saythis said:
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Click to expand...
Click to collapse
The option only appears when you update to 5.1 with your bootloader locked.

fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable...
Click to expand...
Click to collapse
Most would expect that for those Moto freely gives away the bootloader unlock code for (on their web site), should be ok and not impacted. At least that is what we hope, otherwise Moto could have a bunch (maybe a small bunch) of angry users on their hand
But the thought about a warning or caution was directed toward those with ATT, Republic Wireless, or Verizon (non-dev) units who either purchased their bootloader unlock code from the China seller (or middle man) when it was available, or used Sunshine in order to bootloader unlock... since those devices were not ever intended to be bootloader unlocked.... There is uncertainty over this new "check box" in the rom. Moto could leave it out for those models (especially since ATT and RW use their own roms, VZW could be a little trickier since all XT1060's, dev and non-dev use the same rom), and if so, how does that impact any user who had a code and didn't use it yet, or unlocked, and might later want to relock for some reason.
For Sunshine, the concern would be due to changes in the phone's bootloader, TZ, or other parts that might be included in the update which might close that exploited vulnerability down. Think back to how some of the early Root/WPDisable processes were said to be "permanent" only to find they were NOT when the next OTA came out and "un-did" the hack.
So yeah, as you said...
fury683 said:
It's an abundance of caution, I get it.
Click to expand...
Click to collapse

superkeest said:
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Click to expand...
Click to collapse
Some people relock b/c they think it is more secure if they lose their phone or it gets stolen.

it leaves a copy of the fxz on your computer.

sseuorosal said:
it leaves a copy of the fxz on your computer.
Click to expand...
Click to collapse
Motorola Device Manager does, yes if you upgrade using MDM, you will have a copy of the fxz on your computer.

Any Updates on this situation?
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.

dont know about 5.1 but when i flashed 4.4.4 removing cm 12.1 on my att moto x it didnt relock my bootloader hope this stays same with 5.1 i used sunshine to unlock.

Icon000 said:
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
Click to expand...
Click to collapse
The 5.1 OTA for ATT, Republic Wireless and Verizon hasn't been available yet, so I doubt anyone has tried it.
The only ones upgrading to 5.1 right now are those with a bootloader that is unlockable via code from Moto's web site.
I haven't seen Jcase, Beaups, or anyone related to Sunshine make any comments.

Further... I asked in the Sunshine thread...
See JCASE's response -> http://forum.xda-developers.com/showpost.php?p=61503326&postcount=3529

I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.

breakthestatic said:
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
Click to expand...
Click to collapse
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.

Maverick-DBZ- said:
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Click to expand...
Click to collapse
How did you convert it, I'm considering converting my att moto x to retail version. Btw its bootloader is unlocked

BL unlock for Verizon Pixel just released

The guys who brought us sunshine for HTC devices just released their bootloader unlock tool for those of us with Verizon Pixels. YAY!
Check it out here http://theroot.ninja/depixel8.html

Sweet, will do it in the morning for sure.

Works perfectly first try. Wonderful news.

Few questions.
Does this do a wipe on the phone?
Will this allow you to flash stock images from google with no issues and remain unlocked?

If you unlock it and then relock it(without flashing the stock image from google), does it stay unlockable without exploit?

qwer777 said:
If you unlock it and then relock it(without flashing the stock image from google), does it stay unlockable without exploit?
Click to expand...
Click to collapse
No. If you unlock the bootloader, you need to leave it unlocked. Otherwise you will need to re "dePixel8". No matter if you flash one of the google factory images or stay with your current build. The toggle will be greyed out the moment that you connect to the internet.
Also, word is the exploit will be patched in the November security patch. So there is a time frame on this (November 7th). You can also disable automatic updates if you aren't sure whether you want to do this in order to give yourself a little more time to decide.

Is there a way to do this without wiping user data?

SophieTurner said:
Is there a way to do this without wiping user data?
Click to expand...
Click to collapse
Unfortunately no. Unlocking or locking the bootloader wipes user data. Its a security feature. This is how all Pixel / Nexus phones have been for a while now.

DELETED

dbrohrer said:
No. If you unlock the bootloader, you need to leave it unlocked. Otherwise you will need to re "dePixel8". No matter if you flash one of the google factory images or stay with your current build. The toggle will be greyed out the moment that you connect to the internet.
Also, word is the exploit will be patched in the November security patch. So there is a time frame on this (November 7th). You can also disable automatic updates if you aren't sure whether you want to do this in order to give yourself a little more time to decide.
Click to expand...
Click to collapse
Alright. Thanks so much for the info! I'm guessing they're tying the lock to the IMEI then.

Could one unlock the bootloader on the Verizon variant, flash the stock Google firmware and receive OTA updates from Google? In other words, converting the phone to the unlocked version software wise.

darabo said:
Could one unlock the bootloader on the Verizon variant, flash the stock Google firmware and receive OTA updates from Google? In other words, converting the phone to the unlocked version software wise.
Click to expand...
Click to collapse
I want to know about this as well!
Also could Verizon become aware if their uses did this and retaliate by shutting off service due to violating terms or something?

deesugar said:
I want to know about this as well!
Also could Verizon become aware if their uses did this and retaliate by shutting off service due to violating terms or something?
Click to expand...
Click to collapse
They have never done this for other devices that have had their bootloaders unlocked, so I doubt it.

deesugar said:
I want to know about this as well!
Also could Verizon become aware if their uses did this and retaliate by shutting off service due to violating terms or something?
Click to expand...
Click to collapse
I highly doubt they'd go as far as shutting down one's service. Jailbreaking and modifying one's device has been deemed legal by the US Supreme Court IIRC, it's your own property to do what you wish after all.
Now if you were to hack Verizon's servers directly for some reason then that'd be a completely different story...

darabo said:
I highly doubt they'd go as far as shutting down one's service. Jailbreaking and modifying one's device has been deemed legal by the US Supreme Court IIRC, it's your own property to do what you wish after all.
Now if you were to hack Verizon's servers directly for some reason then that'd be a completely different story...
Click to expand...
Click to collapse
Alright so I guess the remaining question is can you flash the stock Google firmware and receive OTA updates from Google? Thereby turning your Verizon phone into a Google Store version with no issues?

dbrohrer said:
No. If you unlock the bootloader, you need to leave it unlocked. Otherwise you will need to re "dePixel8". No matter if you flash one of the google factory images or stay with your current build. The toggle will be greyed out the moment that you connect to the internet.
Also, word is the exploit will be patched in the November security patch. So there is a time frame on this (November 7th). You can also disable automatic updates if you aren't sure whether you want to do this in order to give yourself a little more time to decide.
Click to expand...
Click to collapse
They are backorder for me until the 12/9 wonder what version they will ship with.

JustusIV said:
They are backorder for me until the 12/9 wonder what version they will ship with.
Click to expand...
Click to collapse
It will almost certainly ship with the October security patch. The kicker is the phone will check for updates as soon as you sign in and connect to the internet. I don't know if it will force the update or if it will just notify you that there is one.... And I don't think you can boot the phone up without a sim on the first boot to get around this. I think it requires and internet connection to get through the setup.
---------- Post added at 02:57 PM ---------- Previous post was at 02:48 PM ----------
deesugar said:
Alright so I guess the remaining question is can you flash the stock Google firmware and receive OTA updates from Google? Thereby turning your Verizon phone into a Google Store version with no issues?
Click to expand...
Click to collapse
Negative. You cannot turn a Verizon phone into a Google phone.
They are the same phone. The difference is a server side switch that is being made. Maybe there is an IMEI database with all of the Verizon phones or something similar. As soon as your phone connects to the internet, it will check and confirm that its in that database and the "OEM unlocking" toggle will be grayed out, no matter what Google factory image you are on.
The beginning and the end is the OEM unlock toggle. dePixel8 is just forcing the switch so that you can unlock the bootloader. If you flash a new image or just reboot you will see that the toggle will be flipped, but it was still be grayed out.
If you want an unlocked bootloader, unlock it and leave it unlocked. If you don't care or want to stay stock, leave it alone.

DELETED

dbrohrer said:
It will almost certainly ship with the October security patch. The kicker is the phone will check for updates as soon as you sign in and connect to the internet. I don't know if it will force the update or if it will just notify you that there is one.... And I don't think you can boot the phone up without a sim on the first boot to get around this. I think it requires and internet connection to get through the setup.
---------- Post added at 02:57 PM ---------- Previous post was at 02:48 PM ----------
Negative. You cannot turn a Verizon phone into a Google phone.
They are the same phone. The difference is a server side switch that is being made. Maybe there is an IMEI database with all of the Verizon phones or something similar. As soon as your phone connects to the internet, it will check and confirm that its in that database and the "OEM unlocking" toggle will be grayed out, no matter what Google factory image you are on.
The beginning and the end is the OEM unlock toggle. dePixel8 is just forcing the switch so that you can unlock the bootloader. If you flash a new image or just reboot you will see that the toggle will be flipped, but it was still be grayed out.
If you want an unlocked bootloader, unlock it and leave it unlocked. If you don't care or want to stay stock, leave it alone.
Click to expand...
Click to collapse
Where are you getting this information?

cambunch said:
Where are you getting this information?
Click to expand...
Click to collapse
Jcase comments on the Pixel XL forum, other Pixel XL forum comments, my own device / experience. I have a Pixel 128gb from Verizon.

VZW: Tethering available? Require Hotspot subscription?

Hi All,
I'm very interested in the Moto G5 Plus, and I see that it already has Unlock Bootloader and Rooting threads, but I am looking to see whether or not tethering is a thing on Verizon G5 Plus. I would like to use my data plan but not have to pay extra for the hotspot.... they already gouge us on the price of the data plans...

It tied to your sim. So they will know you are using tethering.

903tex said:
It tied to your sim. So they will know you are using tethering.
Click to expand...
Click to collapse
This is true, but in the past and even with the Moto Z Play Edition they had tethering enabled out of the box without the need for a separate hotspot data plan... That's more towards what I'm looking for in this phone.

its a combo of what services are tied to your sim, and what the phone supports.
you can root and enable it if you don't get it out of the box.

Karlinski said:
its a combo of what services are tied to your sim, and what the phone supports.
you can root and enable it if you don't get it out of the box.
Click to expand...
Click to collapse
That's basically what I'm looking for... and since this phone already has root and bootloader unlock threads, I think I might be in the right area. lol
Thanks for the input.

Karlinski said:
its a combo of what services are tied to your sim, and what the phone supports.
you can root and enable it if you don't get it out of the box.
Click to expand...
Click to collapse
I have not seen any root method on here for the US version. I believe the current root is for an Indian variant, I believe the XT1686. If I am wrong on this can you point me to a root method tutorial for the US XT1687. We just got this phone for my sister but I was holding off on rooting until a solid method was available with a non beta TWRP recovery built. Again if I am mistaken on this please point me in the right direction. Thanks.
---------- Post added at 02:20 PM ---------- Previous post was at 02:07 PM ----------
mchype said:
That's basically what I'm looking for... and since this phone already has root and bootloader unlock threads, I think I might be in the right area. lol
Thanks for the input.
Click to expand...
Click to collapse
I'm quite positive this phone will support tethering without the provision you mention since this is not running Verizon branded firmware. Much the same as some of the older Verizon branded phones that could run a aftermarket ROM, which totally bypassed the provisioning flag that Verizon put in place. Furthermore if you are already on one of Verizon's newer rate plans, then tethering is supported by pretty much every phone they have without provisioning. I'll have my sister give tethering a shot and report back the results.

robn30 said:
I have not seen any root method on here for the US version. I believe the current root is for an Indian variant, I believe the XT1686. If I am wrong on this can you point me to a root method tutorial for the US XT1687. We just got this phone for my sister but I was holding off on rooting until a solid method was available with a non beta TWRP recovery built. Again if I am mistaken on this please point me in the right direction. Thanks.
Click to expand...
Click to collapse
Out of curiosity, the current root thread here actually doesn't say any specific version... I've posted there looking for input, but I've read through the entire thread and can't find anything specific....
Please correct me if I'm totally missing where it indicates version (other than the screenshots clearly not being english... lol )
robn30 said:
---------- Post added at 02:20 PM ---------- Previous post was at 02:07 PM ----------
I'm quite positive this phone will support tethering without the provision you mention since this is not running Verizon branded firmware. Much the same as some of the older Verizon branded phones that could run a aftermarket ROM, which totally bypassed the provisioning flag that Verizon put in place. Furthermore if you are already on one of Verizon's newer rate plans, then tethering is supported by pretty much every phone they have without provisioning. I'll have my sister give tethering a shot and report back the results.
Click to expand...
Click to collapse
OK, sounds good. I received confirmation from someone on T-Mobile that it's not required for a mobile hotspot data plan.
I'm excited about Verizon though.

mchype said:
Out of curiosity, the current root thread here actually doesn't say any specific version... I've posted there looking for input, but I've read through the entire thread and can't find anything specific....
Please correct me if I'm totally missing where it indicates version (other than the screenshots clearly not being english... lol )
OK, sounds good. I received confirmation from someone on T-Mobile that it's not required for a mobile hotspot data plan.
I'm excited about Verizon though.
Click to expand...
Click to collapse
As far as root goes, that post is made by a guy in Brazil and the links he provides are for videos by a guy in India. The US variant is different than the international versions. I wouldn't feel comfortable using that root method and messing something up since there has not been a recovery image released yet. Once you unlock and attempt to root, if it fails and you have no recovery image, you are hosed. I prefer not to soft brick my phone and make it unusable until someone provides a valid root method with recovery images. I personally own a Moto X Pure that is unlocked and rooted, but it is well documented unlike this brand new device.

Well, give it time guys, the device just came out. once everything is rooted and all, there will all sorts of mods

Karlinski said:
Well, give it time guys, the device just came out. once everything is rooted and all, there will all sorts of mods
Click to expand...
Click to collapse
I agree, I'm in no rush at all, as I appreciate all the effort the Developers put into these devices. Most of it on their own time. I was just giving solid advice for rooting a device if you are a non developer like me. I can't afford to force the issue and mess up my phone with no way to restore it. I am glad to wait for a US version root method with a restore option. Hopefully that will be soon , if we are lucky.

robn30 said:
I agree, I'm in no rush at all, as I appreciate all the effort the Developers put into these devices. Most of it on their own time. I was just giving solid advice for rooting a device if you are a non developer like me. I can't afford to force the issue and mess up my phone with no way to restore it. I am glad to wait for a US version root method with a restore option. Hopefully that will be soon , if we are lucky.
Click to expand...
Click to collapse
Lol, that is definitely true.
I'm just impatient and was hoping it was good... not "too good to be true" lol

robn30 said:
As far as root goes, that post is made by a guy in Brazil and the links he provides are for videos by a guy in India. The US variant is different than the international versions. I wouldn't feel comfortable using that root method and messing something up since there has not been a recovery image released yet. Once you unlock and attempt to root, if it fails and you have no recovery image, you are hosed. I prefer not to soft brick my phone and make it unusable until someone provides a valid root method with recovery images. I personally own a Moto X Pure that is unlocked and rooted, but it is well documented unlike this brand new device.
Click to expand...
Click to collapse
I followed that root method on my US g5 plus and it worked fine. It's a solid method you just have to follow the instructions to a "T".

That's good to here but there still isn't any recovery files if something goes wrong. You rolled the dice and came out a winner, might not be the same for someone else. I'll wait until recovery images are available, especially since the phone isn't my own.
Sent from my XT1575 using Tapatalk

If you can obtain root using the methods mentioned here (rooting requires an unlockable bootloader, and a voided warranty) you can add this to your build.prop:
net.tethering.noprovisioning=true

bob2600 said:
If you can obtain root using the methods mentioned here (rooting requires an unlockable bootloader, and a voided warranty) you can add this to your build.prop:
net.tethering.noprovisioning=true
Click to expand...
Click to collapse
I have the EU/Intl version fully unlocked. I can tether with the hotspot using my tether allowance.
If I root my device and edit my build.prop as you've stated what exactly does this do?
Does it mean I can use the inbuilt hotspot/tethering function but instead of using my tether allowance it uses my mobile data?

Changing the build.prop allows you to tether if your verizon plan doesn't include tethering without a separate charge. Newer verizon plans have tethering included as part of your data (ie use it how you like)

Frendly reminder to unlock your bootloader

If you intend to do basically anything with this phone I highly recommend unlocking the bootloader and leaving it in that state always. Especially do this before accepting any kind of beta ota because you might not be able to roll back without bootloader unlock. Do not for any reason try locking your bootloader again unless a rom you are using specifically says to do so like Copperhead or you may end up semi or hardbricking your device. Having and leaving your bootloader unlocked also makes it possible to recover from almost every single possible problem that can arise with the device on a firmware/os level.

Yes,
Recent Non Beta OTA Update also Ruined the Phone. Since the Device was Locked it turned into a Useless Brick Now.
So its Strongly advisable to keep the Developer Mode on with USB Debugging ON and Allow Boot-loader Unlock Option ON at-least.

senthil19 said:
Yes,
Recent Non Beta OTA Update also Ruined the Phone. Since the Device was Locked it turned into a Useless Brick Now.
So its Strongly advisable to keep the Developer Mode on with USB Debugging ON and Allow Boot-loader Unlock Option ON at-least.
Click to expand...
Click to collapse
This is mostly the problem I'm referring to as I've now seen like 5 people who are stuck with a broken ota or are stuck on beta with no way off

I bought a second hand Pixel phone(small version) this summer and it came with locked bootloader. But i live in Russia now, so i dont use verizon. Is there any way to unlock bootloader on verizon phone? Android 8.1 last release

Karolei said:
I bought a second hand Pixel phone(small version) this summer and it came with locked bootloader. But i live in Russia now, so i dont use verizon. Is there any way to unlock bootloader on verizon phone? Android 8.1 last release
Click to expand...
Click to collapse
Doesn't matter where you are, but there is a post or two on here talking about a guy who can unlock it using remote access and installing flexihub on your machine. If you wanna try it make a windows VM real quick and wipe ur phone after you back everything up that you need

Edit: double post

KittyRgnarok said:
Doesn't matter where you are, but there is a post or two on here talking about a guy who can unlock it using remote access and installing flexihub on your machine. If you wanna try it make a windows VM real quick and wipe ur phone after you back everything up that you need
Click to expand...
Click to collapse
Can you give me a link to this thread or to this guy?

Karolei said:
Can you give me a link to this thread or to this guy?
Click to expand...
Click to collapse
Literally first non-stickied thread in q&a

KittyRgnarok said:
Literally first non-stickied thread in q&a
Click to expand...
Click to collapse
Oh, you are right, sorry. Thank you!

Karolei said:
Oh, you are right, sorry. Thank you!
Click to expand...
Click to collapse
No problem my dude. Make sure to do this in a sandbox environment please. Have fun

Karolei said:
I bought a second hand Pixel phone(small version) this summer and it came with locked bootloader. But i live in Russia now, so i dont use verizon. Is there any way to unlock bootloader on verizon phone? Android 8.1 last release
Click to expand...
Click to collapse
today，i spand 150￥ on chinese Taobao.he let my 8.1 verzon pixel unlock,its amazing,i found all bbs ,only fine one way to unlock，our phone need S-OFF S-OFF S-OFF（importance say third）s-off need our chinese is king-card，i dont know what speak in english（Key words：S-ON S-OFF htc） through it to return android 7.1 （sorry my english is pool，but i think you can understand，wish you an early unlock）

pingzi- said:
today，i spand 150￥ on chinese Taobao.he let my 8.1 verzon pixel unlock,its amazing,i found all bbs ,only fine one way to unlock，our phone need S-OFF S-OFF S-OFF（importance say third）s-off need our chinese is king-card，i dont know what speak in english（Key words：S-ON S-OFF htc） through it to return android 7.1 （sorry my english is pool，but i think you can understand，wish you an early unlock）
Click to expand...
Click to collapse
Do You have bootloader unlocked now?
And how you did it? remote over internet?
can you post link no this service?

KittyRgnarok said:
This is mostly the problem I'm referring to as I've now seen like 5 people who are stuck with a broken ota or are stuck on beta with no way off
Click to expand...
Click to collapse
Can you explain this further please, are you saying regular update can brick the phone?

invisibles said:
Can you explain this further please, are you saying regular update can brick the phone?
Click to expand...
Click to collapse
A misparsed or improperly fetched OTA can semi-brick a phone yes. It can also happen when the manufacturer or carrier push a broken update. Both scenarios have happened many times with lg and Samsung phones for example