Related
I'm gonna be getting one as soon as my plan is up. I have a few questions though.
1. (Disregard this one. Didn't realize this was a Verizon exclusive.)
2. When I first get it should I OTA it, so it doesn't disable the possibility of unlocking it?
3. Is this phone supported by many developers?
If I think of any more, I'll post them. Thanks guys!
DubleJayJ said:
I'm gonna be getting one as soon as my plan is up. I have a few questions though.
1. (Disregard this one. Didn't realize this was a Verizon exclusive.)
2. When I first get it should I OTA it, so it doesn't disable the possibility of unlocking it?
3. Is this phone supported by many developers?
If I think of any more, I'll post them. Thanks guys!
Click to expand...
Click to collapse
I think SOL. Used? I do not think you can get the non 98.18.78 anymore.
aviwdoowks said:
I think SOL. Used? I do not think you can get the non 98.18.78 anymore.
Click to expand...
Click to collapse
So when I get it I won't be able to unlock it. Verizon..WHY DO YOU DO THIS...
What version did they patch the BL Unlock method? Cause when I get it I won't be OTA'ing. I will unlock this phone.
DubleJayJ said:
So when I get it I won't be able to unlock it. Verizon..WHY DO YOU DO THIS...
What version did they patch the BL Unlock method? Cause when I get it I won't be OTA'ing. I will unlock this phone.
Click to expand...
Click to collapse
You will most certainly be able to unlock the phone with the latest update using either cellzealots method or mine, but the bootloader will remain locked disabling the ability to use custom roms. If you get one on the 98.17.66 (?) Software your good to use Matt's Droid RAZR M Utility to unlock the bootloader yet so dont take the update, unlock the bl and do what youd like
DubleJayJ said:
I'm gonna be getting one as soon as my plan is up. I have a few questions though.
1. (Disregard this one. Didn't realize this was a Verizon exclusive.)
2. When I first get it should I OTA it, so it doesn't disable the possibility of unlocking it?
3. Is this phone supported by many developers?
If I think of any more, I'll post them. Thanks guys!
Click to expand...
Click to collapse
stock, this phone is great (not sure about the latest release - although, I think it was just to enable a security patch to prevent folks from unlocking the device). so, essentially, if your version is prior to May 2013, then you'll be able to unlock with current methods - otherwise, you'll have to HOPE for someone to create a new method for unlocking or for the devs to make their ROMs flashable via safestrap.
I'm pretty sure you can still root though.
developer support is great (both kernels and ROMs).
jco23 said:
stock, this phone is great (not sure about the latest release - although, I think it was just to enable a security patch to prevent folks from unlocking the device). so, essentially, if your version is prior to May 2013, then you'll be able to unlock with current methods - otherwise, you'll have to HOPE for someone to create a new method for unlocking or for the devs to make their ROMs flashable via safestrap.
I'm pretty sure you can still root though.
developer support is great (both kernels and ROMs).
Click to expand...
Click to collapse
Root works fine still using the RAZR M Utility
jco23 said:
stock, this phone is great (not sure about the latest release - although, I think it was just to enable a security patch to prevent folks from unlocking the device). so, essentially, if your version is prior to May 2013, then you'll be able to unlock with current methods - otherwise, you'll have to HOPE for someone to create a new method for unlocking or for the devs to make their ROMs flashable via safestrap.
I'm pretty sure you can still root though.
developer support is great (both kernels and ROMs).
Click to expand...
Click to collapse
So if I do get this don't OTA it when it first arrives? I'm down to this phone or the HD
DubleJayJ said:
So if I do get this don't OTA it when it first arrives? I'm down to this phone or the HD
Click to expand...
Click to collapse
right - do not accept the OTA if your baseband is prior to May 2013. if it reads May 2013, then you've already got the latest, and you're locked until someone really smart decides to crack it.
if you wanted to, go into the store, have them break out the device, and check the baseband.
jco23 said:
right - do not accept the OTA if your baseband is prior to May 2013. if it reads May 2013, then you've already got the latest, and you're locked until someone really smart decides to crack it.
if you wanted to, go into the store, have them break out the device, and check the baseband.
Click to expand...
Click to collapse
Closest one to me I think is down in Pittsburgh. Only a 30 minute drive, not too bad. I guess I could do that, if I decide to go with this. I'm either going with this, or the Razr HD.
DubleJayJ said:
Closest one to me I think is down in Pittsburgh. Only a 30 minute drive, not too bad. I guess I could do that, if I decide to go with this. I'm either going with this, or the Razr HD.
Click to expand...
Click to collapse
Too bad you aren't closer to Reading, I could really use the business at my shop lol
---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------
DubleJayJ said:
Closest one to me I think is down in Pittsburgh. Only a 30 minute drive, not too bad. I guess I could do that, if I decide to go with this. I'm either going with this, or the Razr HD.
Click to expand...
Click to collapse
I have both to play with and I have to say I like the feel and size of the RAZR M moreso over the bulk of the HD. won over my Galaxy Nexus which hates me now lol
jco23 said:
stock, this phone is great (not sure about the latest release - although, I think it was just to enable a security patch to prevent folks from unlocking the device). so, essentially, if your version is prior to May 2013, then you'll be able to unlock with current methods - otherwise, you'll have to HOPE for someone to create a new method for unlocking or for the devs to make their ROMs flashable via safestrap.
I'm pretty sure you can still root though.
developer support is great (both kernels and ROMs).
Click to expand...
Click to collapse
Ok, as long as I can root. I think I can live without the custom ROMs... maybe. I plan to get one used, hopefully no OTA but whatever.
braveally said:
Ok, as long as I can root. I think I can live without the custom ROMs... maybe. I plan to get one used, hopefully no OTA but whatever.
Click to expand...
Click to collapse
Its a great little thing, I have people playing with them in my office all the time even my boss and hes an iFart lover
I have received a notice of an OTA update for my SM-G900V. I am rooted Via towel root. android version 5.0 oc4 kernel 3.4.0 I did try to accept the update and it failed.
I since have tuned off update notices in T.B. Is this update something I need or even want? Or should I just keep the update
notification turned off? I don't want to lose root. Thanks in advance to all of the members and posters and XDA in general.
I have the same phone configuration as you, android version 5.0 oc4, kernel 3.4.0, but when I attempt to run Towelroot it tells me " This phone is not currently supported". Can you help me figure out how to root mine? Or point me to a step by step instructions for dummies(me)? Thank you.
LDBAKE said:
I have the same phone configuration as you, android version 5.0 oc4, kernel 3.4.0, but when I attempt to run Towelroot it tells me " This phone is not currently supported". Can you help me figure out how to root mine? Or point me to a step by step instructions for dummies(me)? Thank you.
Click to expand...
Click to collapse
You're not trying to use towelroot on lollipop, are you?
If 5.0 is lollipop, and it is, then yes. I seem to have the same config as the OP and he indicated that he was rooted using towell root, so I was asking how he did it. Can you suggest a way to root 5.0? Thanks.
LDBAKE said:
If 5.0 is lollipop, and it is, then yes. I seem to have the same config as the OP and he indicated that he was rooted using towell root, so I was asking how he did it. Can you suggest a way to root 5.0? Thanks.
Click to expand...
Click to collapse
1. You can't
2. Search first on how to downgrade
3. See #2
ldeveraux said:
1. You can't
2. Search first on how to downgrade
3. See #2
Click to expand...
Click to collapse
Thanks. I've only had this phone for a few weeks, and I immediately started looking for a root process to get rid of bloatware. Very confusing situation. Lots of posts about One Click Root, Towelroot, etc....all very misleading, for a noob to Samsung. I had already seen the post you suggested, but (at this point) am not terribly interested in the downgrading route. Maybe later. Keep hopeing one of the brilliant devs here will figure out a way to root without downgrading first.
LDBAKE said:
Thanks. I've only had this phone for a few weeks, and I immediately started looking for a root process to get rid of bloatware. Very confusing situation. Lots of posts about One Click Root, Towelroot, etc....all very misleading, for a noob to Samsung. I had already seen the post you suggested, but (at this point) am not terribly interested in the downgrading route. Maybe later. Keep hopeing one of the brilliant devs here will figure out a way to root without downgrading first.
Click to expand...
Click to collapse
This is what people don't understand: No one is working to root this phone on lollipop. There are assuredly folks working to crack the OS in general, but frankly no one cares about a legacy phone now that the S6 is out. So until L is exploited, there won't be any news for this phone.
So if your phone came with an OS lower than OE1, your only choice right now is to backup, downgrade, TR, profit. There is no one-click-root for the 900V. Honestly, just take half a day and do it. You'll be glad you did for just AdAway!
Read, reread the read again. then set aside a few hours. Good luck
http://forum.xda-developers.com/ver...-to-downgrade-lollipop-5-0-to-kitkat-t3088571
I don't wanna...
ldeveraux said:
This is what people don't understand: No one is working to root this phone on lollipop. There are assuredly folks working to crack the OS in general, but frankly no one cares about a legacy phone now that the S6 is out. So until L is exploited, there won't be any news for this phone.
So if your phone came with an OS lower than OE1, your only choice right now is to backup, downgrade, TR, profit. There is no one-click-root for the 900V. Honestly, just take half a day and do it. You'll be glad you did for just AdAway!
Click to expand...
Click to collapse
...I don't wanna hack it. I am a professional developer that wants to legitimately register with Google as a trusted developer and get granted legal root access. Anywhow if I were to take half a day to do it, the next day Google updated the phone to Marshmallow 6.0 and I have to start all over again...like the proverbial sysyphus....
John Bonifas said:
...I don't wanna hack it. I am a professional developer that wants to legitimately register with Google as a trusted developer and get granted legal root access. Anywhow if I were to take half a day to do it, the next day Google updated the phone to Marshmallow 6.0 and I have to start all over again...like the proverbial sysyphus....
Click to expand...
Click to collapse
If you were a professional, then you could probably figure out how to do it yourself?
I figured it out...
ldeveraux said:
If you were a professional, then you could probably figure out how to do it yourself?
Click to expand...
Click to collapse
nah, nah, I was full of it. Apologies. See - what the carriers don't want you to know is that there are actually TWO versions of a device - the consumer version, which is completely locked down (as it should be), and the developer version of the device. OK, yeah the developer version of a device usually costs twice as much as the consumer version - but the bootloader is unlocked, it's easy to flash away the stock, non-root consumer ROM without fear of bricking, and its APIs probably have many more functions that help with debugging and performance tuning. So as a professional developer what I need to do is trade in my Galaxy S5 consumer edition for the developer edition, and I'll be able to install MultiROM, CyanogenMod, SuperSU, and all the other developer candy.
:good:
John Bonifas said:
nah, nah, I was full of it. Apologies. See - what the carriers don't want you to know is that there are actually TWO versions of a device - the consumer version, which is completely locked down (as it should be), and the developer version of the device. OK, yeah the developer version of a device usually costs twice as much as the consumer version - but the bootloader is unlocked, it's easy to flash away the stock, non-root consumer ROM without fear of bricking, and its APIs probably have many more functions that help with debugging and performance tuning. So as a professional developer what I need to do is trade in my Galaxy S5 consumer edition for the developer edition, and I'll be able to install MultiROM, CyanogenMod, SuperSU, and all the other developer candy.
:good:
Click to expand...
Click to collapse
What you NEED to do is stop drinking before you post. Every user here knows of the dev edition, you're adding nothing new.
ldeveraux said:
This is what people don't understand: No one is working to root this phone on lollipop. There are assuredly folks working to crack the OS in general, but frankly no one cares about a legacy phone now that the S6 is out. So until L is exploited, there won't be any news for this phone.
So if your phone came with an OS lower than OE1, your only choice right now is to backup, downgrade, TR, profit. There is no one-click-root for the 900V. Honestly, just take half a day and do it. You'll be glad you did for just AdAway!
Click to expand...
Click to collapse
...Except if you have a *Verizon* consumer edition phone. Then your out of luck, right? not even downgrading to 4.4 first will work, right? because of the signed bootloader image?
John Bonifas said:
...Except if you have a *Verizon* consumer edition phone. Then your out of luck, right? not even downgrading to 4.4 first will work, right? because of the signed bootloader image?
Click to expand...
Click to collapse
You have to read what he wrote. If your Verizon consumer edition phone has the OE1 or OG5 build you have the locked down signed bootloader. If your Verizon consumer edition has a build prior to OE1, you can still downgrade to KitKat, root, and run a few ROMs through Safestrap or Flashfire.
landshark68 said:
You have to read what he wrote. If your Verizon consumer edition phone has the OE1 or OG5 build you have the locked down signed bootloader. If your Verizon consumer edition has a build prior to OE1, you can still downgrade to KitKat, root, and run a few ROMs through Safestrap or Flashfire.
Click to expand...
Click to collapse
here is my build number: LRX21T.G900VVRU2BOG5
...am I out of luck?
thank you again for your continuing help landshark68, I'm an old PC developer but a complete noob at mobile dev, deciding whether to develop for Android, IOS, or Windows.
John Bonifas said:
here is my build number: LRX21T.G900VVRU2BOG5
...am I out of luck?
thank you again for your continuing help landshark68, I'm an old PC developer but a complete noob at mobile dev, deciding whether to develop for Android, IOS, or Windows.
Click to expand...
Click to collapse
BOG5, you are out of luck. Sorry.
mercermtn said:
I have received a notice of an OTA update for my SM-G900V. I am rooted Via towel root. android version 5.0 oc4 kernel 3.4.0 I did try to accept the update and it failed.
I since have tuned off update notices in T.B. Is this update something I need or even want? Or should I just keep the update
notification turned off? I don't want to lose root. Thanks in advance to all of the members and posters and XDA in general.
Click to expand...
Click to collapse
How do you turn off the OTA notification? I'm not gonna bother with the update but the notification is irritating.
B. J. said:
How do you turn off the OTA notification? I'm not gonna bother with the update but the notification is irritating.
Click to expand...
Click to collapse
You disable it in tb
ldeveraux said:
You disable it in tb
Click to expand...
Click to collapse
Yes. Thank you but my question is how do you disable it in Titanium backup. I'm not sure what it's called or what exactly to disable. Also when I find it do I disable it by freezing? I've tried what I thought was disabling it but I still get them. So I think I must be doing something wrong
B. J. said:
Yes. Thank you but my question is how do you disable it in Titanium backup. I'm not sure what it's called or what exactly to disable. Also when I find it do I disable it by freezing? I've tried what I thought was disabling it but I still get them. So I think I must be doing something wrong
Click to expand...
Click to collapse
Freeze all packages in tb with the words SDM and SPD. Our you could delete them, but I wouldn't...
So i recently updated to the new mhc19l version on my nexus 6p (this is not android N, just the latest android update for the 6p). I did it via the flashfire method following this youtube video: https://www.youtube.com/watch?v=cvs0JQswTWw&feature=youtu.be
I dont have multirom so i didnt do the stuff it mentioned about that. At first I thought I was successful and everything was working great. I reflashed xposed to the latest version, and updated my elemental X kernal too.
But now when I do anything with the camera the phone gets really weird. Post reboot the camera preview will work only once. If I take a photo it crashes. And every time I try to do anything with the camera involved the thing will crash and not even load preview anymore. That includes 3rd party apps like snap chat. Also I can't edit quick setting tiles in system ui as it tells me system ui tuner has crashed, but that i can live with. The camera issues I can not live with.
None of that happens with my rooted 6p on the same build. I think you need to look at xposed, the kernel changes and all the other jiggerypokery you've done. I'd do begin by reflashing the factory image and do this manually either using Heisenberg's extremely clear guide, or by the flash-all.bat command that google supplies in the factory build. Then you can check camera, flash recovery (again, using Heisenberg's guide, it takes but a couple of commands), then root, add xposed, kernels and all that special sauce. Do it step by step, then you'll know when something goes wrong and only have to fix that.
Thank you for your help. I'll check that out. Do you think it may be because I updated from a pretty old build? (808L) I skipped a few updates and went right to the latest one, could that cause any problems?
Not really. I think it's because you've done too much using a tool and without checking things after each step. Stop using tools like flashfire when you don't understand what they do and get yourself up to speed with using the commands. After that, you'll spot where things have gone wrong and be able to fix or troubleshoot it within the community. No one can help you when it's an issue that could caused by one or more of a hundred things you've tinkered with.
It's not hard and worth the little bit of busy work and brain thought. You'll enjoy it!
Yea I like to tinker and stuff. It's just the customizations with dashclock and stuff that I don't want to lose. But I did app backups so hopefully I won't.
Something probably went wrong during the flash process. I highly doubt xposed or kernel modifications are to blame. I keep 12 xposed modules running at all times with kylo kernel which I have heavily modified with EX kernel app. Read Heisenberg's guide and learn to flash images properly and you should be good to go.
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You can't flash anything with a locked bl. Locking the BL is nothing but trouble if you like to tinker.
Sent from my Nexus 6P using Tapatalk
and313 said:
So i gotta ask. Using flashire only is it possible to lock the bootloader and flash small incremental updates without a problem? Its a bit sad to have a unlocked bootloader...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
dirtyuzbek said:
Before I do any reflashing today can anyone do me a favour and upload their camera APK?
Im just hoping it has something to do with that. Last ditch effort.
And thanks for the help guys
Click to expand...
Click to collapse
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Any Advice ?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
naruto.ninjakid said:
Hello you seem very knowledgeable on the subject. I just picked up a 6P and was wondering how does encryption affect things such as TWRP and root. Do you advise to disable encryption on the device for ease-of-use in TWRP and root.
Click to expand...
Click to collapse
Look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Deception isn't necessary anymore, as long as you use the latest TWRP you should have no problems.
did it flash the vendor?
Heisenberg said:
Locking the bootloader is nothing but trouble. You know what's sadder than having an unlocked bootloader? Having a bricked phone because an OTA failed and your bootloader is locked. If that happens there's no way to save it.
What method did you use to update? Did you use an OTA zip? Or factory images? I'd Is there a reason you used Flashfire instead of updating the proper way?
Click to expand...
Click to collapse
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
and313 said:
Wait.. If the bootloader is locked and a ota fails you cant oem unlock it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Heisenberg said:
No, because if the OTA fails you won't have access to the option in Developer Options to enable OEM unlocking. Trust me, you want to have that bootloader unlocked. You don't wanna end up like the other guys who had to send their phone back for repair because they locked it.
Click to expand...
Click to collapse
Right... I did not think that the first step (enable bootloader unlock from dev options) is actually necessary.
Sent from my Nexus 6P using Tapatalk
Its been reported that merely having an unlocked bootloader now trips safetynet. Google has officially turned their backs on developers and enthusiasts.
I never had a problem with xposed or magisk tripping safetynet; but an unlocked bootloader is by no means a security risk. So I'm not happy having to choose between snapchat and an unlocked bootloader.
Sources: https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
https://www.reddit.com/r/Nexus6P/comments/586bq7/android_pay_stopped_working_on_nonrooted_device/
Discuss.
Well RIP AP....
Pixel and now this, I guess Google is becoming Apple 2.0
can confirm, I have unrooted stock 7.0 as my primary on multirom and is tripping safetynet, no more AP for me I guess since I'm NOT locking the bootloader, nice play Google
Sent from my Nexus 6 using Tapatalk
IIRC chainfire DID warn us about this..saying if we keep trying to hide root, they'll keep trying to make it harder for us to do so.
Doing it to the pixel? Fine..but to a nexus phone? Kinda murders the whole selling point of Nexus.
Either way elgoog has been making some really odd decisions this past month or so.
I have an unlocked bootloader with everything stock and no root and I got past safety net for Pokemon Go.
biggiesmalls657 said:
I have an unlocked bootloader with everything stock and no root and I got past safety net for Pokemon Go.
Click to expand...
Click to collapse
Last I heard pokemon go isn't working with safetynet properly right now. Download SafetyNet Helper Sample from the PlayStore, it'll tell you whether you pass or not.
geokhentix said:
Last I heard pokemon go isn't working with safetynet properly right now. Download SafetyNet Helper Sample from the PlayStore, it'll tell you whether you pass or not.
Click to expand...
Click to collapse
Well I guess that a smartphone isn't for me, I'm gonna get a dumb phone again. Google can suck it. This is so ridiculous.
geokhentix said:
IIRC chainfire DID warn us about this..saying if we keep trying to hide root, they'll keep trying to make it harder for us to do so.
Doing it to the pixel? Fine..but to a nexus phone? Kinda murders the whole selling point of Nexus.
Either way elgoog has been making some really odd decisions this past month or so.
Click to expand...
Click to collapse
The only pixel that is locked is the Verizon version
holeindalip said:
The only pixel that is locked is the Verizon version
Click to expand...
Click to collapse
Yeah, that one isn't a part of this as its not unlockable. I'm talking about the Google Pixel.
This f's people who just want to install the latest factory image too; non power users who don't root and just want the latest OS..considering you need an unlocked boot loader to flash the images.
geokhentix said:
Yeah, that one isn't a part of this as its not unlockable. I'm talking about the Google Pixel.
This f's people who just want to install the latest factory image too; non power users who don't root and just want the latest OS..considering you need an unlocked boot loader to flash the images.
Click to expand...
Click to collapse
Not if you side load the latest ota files posted the same day:good:
By the way, does re-locking bootloader wipe data or internal? Factory image page says that "Locking bootloader will wipe the data on some devices. ".
Pretty sure on the n6, we wipe everything on both unlock & relock.
I'm planning on getting a new Nexus 6. Is it not the right time? I'm afraid this issue will make me unable to customize my new phone.
jesuajovan said:
I'm planning on getting a new Nexus 6. Is it not the right time? I'm afraid this issue will make me unable to customize my new phone.
Click to expand...
Click to collapse
You can still customize. You just can't do crap that you probably shouldn't be worrying about anyway. Android pay is a sham, since your credit card has an RF chip in it that works on the same scanner... but ONE FEWER companies get to track all your purchases when you use it since it leaves google out of the loop.
Indeed; also as long as you log into Snapchat once before you install root, it seems to continue to work after root / magisk installation.
I'm on 7.0 stock, rooted and unlocked bootloader and snapchat works fine.
pharpe said:
I'm on 7.0 stock, rooted and unlocked bootloader and snapchat works fine.
Click to expand...
Click to collapse
I just want to say that Snapchat is one of the worst coded apps ever
For Snapchat to work, you have to login before rooting your device, just don't log out lol
holeindalip said:
I just want to say that Snapchat is one of the worst coded apps ever
Click to expand...
Click to collapse
Amen.
I wonder what the hook is that it uses to check if the bootloader is locked...? It *must* go through the kernel, so maybe this is as simple as telling the kernel to LIE about it.
Well, that is simple conceptually, but not necessarily *easy* to implement.
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)