yashsingh1/xdaforums huggingface dataset:
[Moto X Themes and Apps] DIYiT:
Has anybody seen any problems with the entitlement hack working in the past week or so? I had tethering working on my VZW DE 4.4 for two weeks and now cannot get it to work. Were there any updates lately that would have changed anything.
[Moto X Themes and Apps] crazyxzer0:
Mine still works on vzw de

sent from Moto X Dev Edition
[Moto X Themes and Apps] Kittiesoncrack:
Mine works but I cant get internet access from it
[Moto X Themes and Apps] FSXv13:
I just did this yesterday but couldn't get it to work unless I left the .odex alone.
[Moto X Themes and Apps] EYEramid:
Mine works, just got 39 mbps with it
[Moto X Themes and Apps] evandena:
Posting from my tethered laptop, works like a charm.

Thanks
[Moto X Themes and Apps] buton2:
i tried doing the root browser method and didnt work...going to try the other method

---------- Post added at 06:38 PM ---------- Previous post was at 06:16 PM ----------

i did it with the command prompt method and it worked !!!!!
[Moto X Themes and Apps] Blitzpwnage:
Any way we could get a Sprint version of this
[Moto X Themes and Apps] tscan:
Would there be anyway to make this bypass the check completely? Like the previous 4.2.2 method and other posters were wondering.
[Moto X Themes and Apps] xastey:
FYI my file was in /system/app and not /system/priv-app.. also I no force close when turning on for the first time. Is there a way to get ride of the dialog or is that something we have to deal with.. not really a problem but wanted to know.

Thanks for the tut, just got my phone today and setting everything up.

Edit:

Take that back, ended up getting force closes and had to restore to a previous backup, now I'm in a boot loop LOL
[Moto X Themes and Apps] BackInA88:
Than you got the wrong file, why would your Verizon phone be different than the rest?

Steve
[Moto X Themes and Apps] scootle74:
Make sure you are on a rooted, but fully updated 4.4 system, to do this... the relevant entitlement .apk and .odex files should be in /system/priv-app in 4.4.

I just performed everything described in the OP, but using Root Browser (JRummy) and it worked fine on a non-DE, rooted MotoX.
[Moto X Themes and Apps] xastey:
I forgot to update to 4.4, I previously unlocked my bootloader and couldn't get the damn ota to install so had to go the long route with fastboot, got everything work now.
[Moto X Themes and Apps] thepolishguy:
Just wanted to thank the OP. It worked great after I read the instructions a couple of times. Imagine that.
[Moto X Themes and Apps] Se7enLC:
Worked great, but didn't survive a reboot. Any ideas why?
[Moto X Themes and Apps] tluley51:
Mine doesnt survive a reboot either. assuming it is a write protection thing? maybe?
[Moto X Themes and Apps] Coderedpl:
Are you trying to do it on a developer edition or consumer/retail?
[Moto X Themes and Apps] tluley51:
VZW non dev rooted
[Moto X Themes and Apps] Coderedpl:
Reboot to bootloader

Select recover from the list

Boot

Follow steps.

Reboot.

Should stick.

It's due to the write protection
[Moto X Themes and Apps] tluley51:
still checks for subscription after the reboot and comes up with the error from Verizon.
[Moto X Themes and Apps] Se7enLC:
Can you elaborate on that? do you mean that I need to make the changes from adb in recovery vs while running android? I mount the /system partition r/w, make the changes, and mount it r/o again. Is there some other sorcery going on with this phone where even though it appears to make changes to /system they aren't made? I've been on CM on my galaxy nexus for so long I've forgotten how to deal with these bizarre restrictions.

On a side note, I ended up wiping the phone and restoring to plain vanilla stock. I then:

Applied the Koush Superuser.zip file in recovery to get root access

Booted up, did the initial setup

Installed Xposed

Installed the awesome module linked in the other thread on here that disables the entitlement check

(http://xdaforums.com/showthread.php?t=2601859)

Worked like a charm. I've never had to use Xposed before, but so far I'm a fan.
[Moto X Themes and Apps] Coderedpl:
This worked for me on my non-dev when I had it so I know it works but I've done mistakes that showed messages and issues you're getting.

Reboot into bootloader. It will be a black screen, and You'll have a bunch of options to pick from there. Normal recovery and some others.

Scroll down with volume down to select Recovery.

I believe in order to select it you have to push VOLUME Up not power. If you select power I think you're simply rebooting.

What this does is it boots into Android without write protection enabled.

If you follow the steps from the first post without rebooting and it works. Then it should work since then after reboot.
[Moto X Themes and Apps] Se7enLC:
On a dev model, this boots into your recovery console (clockworkmod for me).

I meant elaboration on what "write protection enabled" means for this device, not on what steps to follow.

Is there a difference between adb from the recovery console vs remounting /system as rw? getprop ro.boot.write_protect returned 0 for me when booted into android, so if I'm understanding it right, that means that the protection is disabled.

I spent an hour tearing my hair out when I got the phone a few days ago trying over and over to flash recovery, not realizing that it was flashing fine, and I was just not booting into it properly. I was hitting volume-down and then power to select it like every other phone I've had. It wasn't until I watched a YouTube video that I picked up on that information about volume-up being the enter key.
[Moto X Themes and Apps] tluley51:
I think I am fully SOL. My phone wont even boot into recovery EVEN when using vol up to select it. It still just boots into android like a normal bootup.

I think since I flashed TWRP back when I had 4.2.2 on this device screwed me. I now have stock 4.4 - rooted but since I previously flashed TWRP, I lost both TWRP and stock recovery with 4.4.
[Moto X Themes and Apps] Coderedpl:
I'm no expert just an avid user but I'm assuming this won't allow changes to stick in system, since if you didn't have root it wouldn't be possible to do any changes in the first place. If it returned 0 then protection is off. Also I was talking about nondev edition.

no worries, I did the same thing initially but I think if you read what it says on the screen it says to push volume up to select

I never said boot into recovery. Just select the option and let it boot. It will boot into android without write protection.

Run getprop ro.boot.write_protect to check

Am i missing something or how did you have twrp on nondev? Safestrap?
[Moto X Themes and Apps] tluley51:
Correct, safestrap. I will try your method now.
[Moto X Themes and Apps] Coderedpl:
It will look like you rebooted but once you run that command you'll see either a 1 or 0. If everything went correctly with rooting process and you boot correctly. It should show 0.

I have a dev edition now but when I had the Consumer I had the same issue and it wasn't until I did this that it worked.
[Moto X Themes and Apps] tluley51:
Holy s*** it looks like it worked...Wow, thanks!!!
[Moto X Themes and Apps] Coderedpl:
Reboot regularly to make sure
[Moto X Themes and Apps] tluley51:
I rebooted twice and it still is working
[Moto X Themes and Apps] Se7enLC:
Remounting /system as rw requires root to do, so it should (and does) work on other devices. And since that getprop call returned 0, the protection shouldn't have been on, if I understand it right. But for some reason it still didn't "stick". The files stuck (at least, the .bak files were still there), but it just stopped working after the reboot. Something else must have happened on the reboot.

I think perhaps there's a difference between dev and non-dev in this regard, and that's all it was. No matter, I'm fine with using the Xposed framework module until the custom roms are mature enough to run.

> no worries, I did the same thing initially but I think if you read what it says on the screen it says to push volume up to select

Oh, it certainly says it, I just didn't read. That's the downside of knowing what you're doing, it's much easier to screw it up when something changes and you just blow right by it with "oh, I know this".
[Moto X Themes and Apps] Coderedpl:
Remember same thing applies if you use things like xposed.

Which device do you have? Dev or nondev? You're confusing me now.

On the non dev. I followed the steps except I booted to Android as I listed earlier and it worked.

On the dev edition. Unlocked and rooted. I followed the steps. And it sticks. Didn't have to do any special steps.

I rebooted a few times and it still works.
[Moto X Themes and Apps] Se7enLC:
I have the Verizon dev, unlocked and rooted, and it didn't stick for me. You mentioned selecting the recovery option and that it would boot into android with write_protect off, and I think that is only applicable to the non-dev version - the dev version just runs your recovery console (CWM or TWRP). The instructions never specified that it needed to be run from ADB in CWM, so if that's the case, now I know. I did check ro.boot.write_protect, and unless I am misunderstanding what it means, it indicated that whatever the magical write-protection is, it was not enabled.

I'm not trying to fix the tether option - the xposed module got that working for me reliably. I'm now just trying to understand what the system write_protect issue is, for my own understanding. My ro.boot.write_protect was showing 0, and I remounted /system as rw and was able to write to it. I'm not sure why the tether change didn't stick, and I didn't investigate whether it was the changes to /system not sticking or whether there was something else preventing it from working.

In the event that I try to do the change again, I think I will compare my results from adb in CWM vs adb in android to see if there's any difference. If you happen to come across more information about what write_protect is, I'd like to read up on it. Maybe it's a bind mount or some kind of overlay filesystem? I really have no idea.
[Moto X Themes and Apps] Yazzinit:
Hey, thanks for this. JUst to confirm, didn't see it asked/answered (or if I missed it, sorry!). It says checking for subscription and then works as usual, allowing me to use the native tethering/wifi. That's what is supposed to happen, right? It will "check for subscription" for a few seconds each time, but that's all, not actually sign me up right? lol
[Moto X Themes and Apps] icrf:
I'm seeing the same thing on my brand new Verizon DE unlocked and rooted. AP is created, I can connect, but can't pull data through it. How do I go about troubleshooting this? Are there log files somewhere I can look at?
[Moto X Themes and Apps] Kittiesoncrack:
hold on, Im working on this. this is a KitKat issue and there might be a way around it
[Moto X Themes and Apps] icrf:
I'm definitely interested in what you come up with. What confuses me is what would be different between the 4.4 on my/our device compared to everyone else that seems to get this working painlessly. You're on Sprint, too, so it's not likely a Verizon locking problem.

Android-wifi-tether, stable or beta, doesn't work for me, either. It's different, though, in that an AP is just never created. The app acts like it works fine, though. I saw in another post that you said that one was working fine for you.

I'm hoping that it's just something random/stupid that both of us did and there isn't any kind of software/hardware variability that would cause these kind of problems.
[Moto X Themes and Apps] Kittiesoncrack:
i talked another dev awhile back and he linked to a Nexus 5 thread where a user was trying to enable native wifi tether and he came up with the solution. for some reason, i had entered the wrong "entry" and it did not work at the time. but today i sat down and tried it again it worked. I also tried it on my brothers Moto x and it also worked. Im gonna try to talk the dev so he can figure out a better, more simpler way, to implement it
[Moto X Themes and Apps] Dburgessme2:
Hi there. I'm looking to be prepared for 4.4.2 update soon (hopefully)

Aside from root & TWRP, I'm thinking this entitlement apk is only system thing I need to make right.

So, in priv-app can I just delete the entitlement apk from this thread and rename the old one & its odex file. (remove "bak" from them) Then, reboot and should be good?

I'll then use the xposed module for tether.

Does that sound about right without any ill effects?

DB's Moto X
[Moto X Themes and Apps] jideay:
Thanks to CJ64 and GeeK, this worked perfectly. Tethered my tablet and got 12.68 Mbps down and 1.04 Mbps up! Awesome!!!

---------- Post added at 07:21 AM ---------- Previous post was at 06:46 AM ----------

Has anyone found a widget that can turn off the hotspot? I've tried several. Most can turn the hotspot on, but I haven't found anything that will turn it off.
[Moto X Themes and Apps] thals1992:
OK, I'm trying to port a tethering hack over to the Samsung Odyssey (a Windows Phone) I had just recently InteropUnlocked it (with registry/near complete access.) On the Trophy (a 3G device), all that needed done was the username changed from [MENTION=809261]dun[/MENTION].vzw3g.com to just [MENTION=536007]vzw3[/MENTION]g.com.... I have no clue how it works on LTE now, but the username is now [MENTION=4451643]vzim[/MENTION]s.com. Reading how you achieved it you simply disabled the Entitlement Check. Is there a different username I'm supposed to use for LTE devices these days? I'm kinda lost, as there have been loads of new Android devices on Verizon since they added LTE, but only 5 windows phones in the last three years, with the Trophy being their 3G only device.
[Moto X Themes and Apps] rebretz000:
Just used this. Thanks. Makes it nice to be lazy
[Moto X Themes and Apps] ozymandias2:
I've had no luck. As far as I can tell, this is a widespread issue -- I found people commenting on play store apps that they have this problem, as well as several threads with people asking -- but no solutions -- yet...
[Moto X Themes and Apps] ozymandias2:
I have found a solution to the Moto X not programatically toggling off a wifi tether -- it appears that ALL apps had this issue on my Verizon Developer Edition with KitKat 4.4 (adding terms for searching).

I installed the Xposed Framework, and on the off-chance, I installed the 'deactivate entitlement check' module -- once that module was added, *all* apps appear to be able to programatically toggle *off* the tether. This implies to me that the entitlement check code has a bug of some sort...
[Moto X Themes and Apps] jideay:
Where did you find the 'deactivate entitlement check' module? I went through all the modules list in the program and didn't see it.
[Moto X Themes and Apps] ozymandias2:
Oh, sorry, I used the "Moto Tether" Module. The description is that it removed the entitlement check.
[Moto X Themes and Apps] jideay:
That works perfectly with the widget I use. Thanks!
[Moto X Themes and Apps] ozymandias2:
I was able to resolve this by installing Xposed, and the MotoTether plugin, which simply removes the entitlement check from the tethering app.

It's pretty conclusive that the entitlement apk is what causes this issue.
[Moto X Themes and Apps] Cozume:
Thanks so much for this!

Do you know if the modified VzwEntitlementServices.apk bypasses the check to Verizon's servers or if it just ignores the result of the check?
[Moto X Themes and Apps] mercurycougar871:
4.4.2

has this mod been done to the vzw 4.4.2 version yet?

found it: http://xdaforums.com/showthread.php?t=2657265
[Moto X Themes and Apps] GrillMouster:
The method described at the beginning of this threat works on 4.4.2. Easy to do using Root Explorer.
[Moto X Themes and Apps] Mickoou:
Thether

Is this still the easiest way?

I don't need to be connected to a computer?

Thanks
[Moto X Themes and Apps] Mickoou:
Foolproof is just what I needed.

Thanks Geek
[Moto X Themes and Apps] t2fingers:
I have been using this method and it has worked great. Will this change stick if I do the OTA Verizon update that was just released? I don't want to screw anything up if I do the update.
[Moto X Themes and Apps] dymmeh:
The OTA checks your system before it updates. It won't allow you to update if it detects any changes to system files.
[Moto X Themes and Apps] t2fingers:
Does this mean that I have to install my twrp backup and unroot before I can get the update?
[Moto X Themes and Apps] dymmeh:
You should just need to change your entitlement apk back to the original.
[Moto X Themes and Apps] JGoldz75:
Is there a way to undo this? I need to undo it so I can update to 4.4.2 OTA. Thanks! (Please keep in mind i'm a noob when it comes to adb)
[Moto X Themes and Apps] JGoldz75:
Got it! Thanks!
[Moto X Themes and Apps] GloryUprising:
Any chance for and update for 4.4.2?

Thanks!
[Moto X Themes and Apps] GloryUprising:
I confirm this method works for the Dev Moto X on VZW on 4.4.2 doing it the manual way.

Thanks, OP!
[Moto X Themes and Apps] Mickoou:
This is what I did.

Do i have to undo this first to get the 4.4.2 update.

Dont know how to reverse the VZW Entitlement hack.

Totally confused.
[Moto X Themes and Apps] czechm8:
Worked for me as well.

Details:

XT1060 Dev edition. Rooted, on stock firmware and using TWRP. VZW Entitlement hack.

I undid the VZW Entitlement hack using Root Explorer and flashed back the stock recovery using the Moto X Toolkit V1.3.4

Rebooted, checked for VZW update. Downloaded and it installed with no issues.

I then flashed TWRP back using the Toolkit.

I did not lose root, SU or any data. Couldn't be happier! Now running 4.4.2 rooted with a custom recovery.
[Moto X Themes and Apps] Mickoou:
Since I used the script for the Verizon Entitlement hack how do I undo it

Thanks
[Moto X Themes and Apps] RadOD1:
I'd to hear this too. I kinda think I can do it by putting back the .bak files, but I'd love it if someone could spell it out for me.
[Moto X Themes and Apps] czechm8:
The instructions are on page 2 of this thread.
[Moto X Themes and Apps] Mickoou:
Quote:

Originally Posted by Mickoou View Post

Since I used the script for the Verizon Entitlement hack how do I undo it

Thanks

I'd to hear this too. I kinda think I can do it by putting back the .bak files, but I'd love it if someone could spell it out for me.

Should i use the instructions in ascending or descending order to revert.

Feel like a dummy here

Thanks
[Moto X Themes and Apps] 640k:
other thread should be closed, or have this file replace the one in the OP of that thread. this worked for me on 4.4.2. thanks!
[Moto X Themes and Apps] Ren118:
New Guy

I am a former progamer from the 90s, so I am about to ask some realy dumb questions.

Can i use this code with the Droid Mini? It doesn't have an SD Card.

Can you walk me through the installation of this code?

Is there a compiler I should be using?
[Moto X Themes and Apps] wmarcin:
The code you're referring to are just command line instructions. You need to get the necessary apk file and run these lines from your PC CMD.exe.

... Moto X VZW DE ...
[Moto X Themes and Apps] Caseyk621:
This will work on the mini, if rooted. Check this thread OP for easy instructions.

http://xdaforums.com/showthread.php?t=2578410

Sent From Droid Ultra
[Moto X Themes and Apps] Pxbacher:
Works, but...

I'm on a Moto G flashed from Verizon to PagePlus. ROM is stock Verizon, which appears to NOT have the usual "Wifi Hotspot" setup menu option.

I can see the default SSID when I turn on tethering via SwitchPro, but I don't know hwo to change the SSID and PW so I can actually connect.

Anybody have an easy solution? I tried an app called TetherSetting, but it has no effect on the SSID/PW :confused:

Thanks!

-Pete
[Moto X Themes and Apps] 640k:
anyone validate this against 4.4.4 yet?
[Moto X Themes and Apps] czechm8:
I'd like to know too if undoing the VZEntitlement hack, and re-doing it after upgrade to 4.4.4 works as it did on the previous version.

I'd sure like to keep my tether option!
[Moto X Themes and Apps] faganm24:
I was getting ready to undo this and found that I no longer have the backup files. Anyone have a spare copy of the two files that you could share? Moto X 4.4.2 VZW DE.

Edit: Fixed with flashing system.img. I had a bad file.
[Moto X Themes and Apps] Ratamacue:
^This. Would love to do 4.4.4 update but not without tether!
[Moto X Themes and Apps] blempka:
Confirmed working on 4.4.4 for me.
[Moto X Themes and Apps] 640k:
i feel like this method was easier/better:

http://xdaforums.com/moto-x/themes-apps/mod-native-android-tether-t2657265
[Moto X Themes and Apps] Ratamacue:
Thank you!
[Moto X Themes and Apps] czechm8:
Awesome!
[Moto X Themes and Apps] a1exus:
Can this be applied to non developer edition phone? I'm still on 4.4 and I wanna switch to 4.4.4 but I really don't want to give up root for tethering purposes, but I know going to 4.4.4 means losing root, but can apply this somehow?
[Moto X Themes and Apps] Topsnake:
Seriously? Reread the very first line of the op again.

If you update to 4.4.4 use [MENTION=4850320]iKrYpToNiTe[/MENTION] method

[MENTION=2509024]samwathegreat[/MENTION] look at this.
[Moto X Themes and Apps] a1exus:
First line of OP refers to 4.4 with write protect off, my question was for 4.4.4, so I guess I'll take a look at iKrYpToNiTe method.

Thanks!
[Moto X Themes and Apps] 640k:
bottom line is you must be rooted and you must have r/w protection off for this to be a successful hack.
[Sony Xperia S, Acro S, Ion] TitaniumZERO:
Just last Sunday when I received a notification to update SuperSU, so as usual I choose to update it. It was installed fine but after that SuperSU stops granting root access permission, when I launch any apps that requires root access example Titanium Backup, XBlast Tool, etc. my phone will restart by itself. When I uninstall and reinstall those apps there were no prompt from SuperSU to grant the access, it like I've lost the root access.

So I want to use flashtool to re-root my phone by using DooMLord method (flash .211 kernel, root using his v18 toolkit, flash .96 kernel) so that I should able to keep all the settings and mods and files on my phone. But another problem, Windows 8.1 cannot recognize my Xperia S in flash mode i.e. when plug in my phone by holding volume down button, Windows 8.1 says the USB device is not recognized therefore I cannot proceed to flash.

So my question:

1) Why do I lost the root access by updating SuperSU? Was I suppose to update it?

2) By using DooMLord method (flash .211 kernel, root using his v18 toolkit, flash .96 kernel), can I keep all my settings, files, data, mods, etc. or should I just do a full wipe?

3) How to setup the drivers properly in Windows 8.1? The Windows 8 trick doesn't work anymore as the drivers are installed but I can't connect in flash mode.
[Sony Xperia S, Acro S, Ion] TitaniumZERO:
Ok, Problem solved.

If anyone is interested, you can visit http://xdaforums.com/showthread.php?t=920746 for solution.
[Micromax A116] babvin:
Is there any work happening on new TWRP versions?
[Micromax A116] suhas.holla:
Im working on it ...the fact is the newer versions of TWRP are larger in size (7mb) so it does not fit in our recovery as mt6589 recovery has 6mb partition ...i tried my best to compress the recovery but was upto 6.2mb was successful ...its no use ..the recovery should be less then 6mb then only it will work
[Micromax A116] babvin:
TY Suhas.
[Micromax A116] userprince:
so in other word new version can never be ported for our device?
[Micromax A116] is0l4ted:
Thank you brother...

Well, About the huge partition space delete some unwanted files in recovery and then compile it hope it may work, as it was a better work in late Sony 2011 Devices. this was the key!!