Related
In this method you will be able to activate your tethering hotspot only for a temporary period of time. First hotspot activate will work fine but once you turn it off you will be prompted with the entitlement check when you try to reactivate the hotspot. You will need to repeat the process again in order to bypass the entitlement check. So with that in mind lets begin.
(I AM NOT RESPONSIBLE FOR VERIZONS GETTING UPSET FOR YOU USING THIS FREE HOTSPOT!!!!)
In other words try to keep this method under VERIZONS knowledge and you should be fine.
Requirements:
You will need to have done CrashXXL`s root method to have a rooted Droid.
Then once you have a rooted device download SQlite editor which can be purchased on the Gioogle Playstore.
(NOTE: i will not post any download links for SQlite Editor due to XDA rules.)
Step1: Open Rsqlite editor then go to apps then Settings storage with the two tools icon. Now from there go to settings.db . Now go to secure and you`ll see a list of words and ids as well as value columns.
Step2: Change these exact values to the values listed below.
-dun_nat_enabled= enabled
-tether_reverse_nat_enabled= enabled
-entitlement_check= 0
-USB_entitlement_check= 0
-Network_settings_on_boot= 1
-APN_CHECK_STATE= 1
APN check state is the most important.
Step3: Once the values are changed reboot your device and you will be able to use the hotspot once then once you deactivate the hotspot itll check for entitlement check. So for now this is a temperary Hotspot method! Enjoy
My YouTube video tutorial: https://m.youtube.com/watch?v=A0Xc_z6vYXA
Easier method
This is only my first post, and I know that I might be missing something important, but there is an easier method to activate tethering for this device and firmware. While the xt1080 is not supported officially by kingroot, the app will grant temporary and limited root permissions (no /system access). This is enough to get the entitlement bypass app working on the device. I have attached the apks for the entitlement bypass and kingroot apps below. You can download the latest version of Kingroot from the official website. The entitlement bypass app will only run successfully once the device has been temporarily rooted by kingroot. While the root will not last, the bypass of the entitlement check for the tethering hotspot should remain in effect, until the next reboot. You should be able to use the hotspot without any problems until that point, at which time you will have to rerun the Kingroot app. This method has worked for me for months. I am on an xt1080 Droid Maxx running 4.4.4 SU6-7.2. Nothing else is required for this method. Although, the initial root may require a restart/retry or two. I hope this helps.
jamesbrogan85 said:
This is only my first post, and I know that I might be missing something important, but there is an easier method to activate tethering for this device and firmware. While the xt1080 is not supported officially by kingroot, the app will grant temporary and limited root permissions (no /system access). This is enough to get the entitlement bypass app working on the device. I have attached the apks for the entitlement bypass and kingroot apps below. You can download the latest version of Kingroot from the official website. The entitlement bypass app will only run successfully once the device has been temporarily rooted by kingroot. While the root will not last, the bypass of the entitlement check for the tethering hotspot should remain in effect, until the next reboot. You should be able to use the hotspot without any problems until that point, at which time you will have to rerun the Kingroot app. This method has worked for me for months. I am on an xt1080 Droid Maxx running 4.4.4 SU6-7.2. Nothing else is required for this method. Although, the initial root may require a restart/retry or two. I hope this helps.
Click to expand...
Click to collapse
I've spent a lengthy period of time trying to get tethering to work on a broken screen MAXX, because I refuse to finance a new phone to Verizon. This entitlement app worked perfectly. So I am not able to tether the connection to a prepaid phone and forward my calls to the prepaid device and use my TWC Phone2go.
Thank you
Hello everyone. Many users have problems with slowing phone after installing xposed. The same applies to me. No one has yet found a solution that would suit everyone. But I found something that might help someone. This is in a forum where solves slowdown S-Health application for Samsung. While I do not have Samsung (I have Jiayu G4S), so I tried it. I'm simply install certain module "XSecureStorage" in Xposed and really my phone runs without lags
Link here:
http://forum.freelatestmovies.org/note-4-tmobile/general/fix-how-to-fix-xposed-framework-lag-t2935423
Copied text from this URL:
Found and confirming a method on how to get the latest version of Xposed Framework working on Note 4 (T-Mobile SM-N910T). Also Wanam Xposed is working fine too inside Xposed Framework.
Step 1:
Insure that Xposed Framework is fully uninstalled from the device temporarily.
Step 2:
Go into Root Browser, or any browser of choice that has root privileges and go to /System/Build.Prop and open it as a text document.
Step 3:
Inside the Build.Prop file look for a line that says "ro.securestorage.support=true" [NOTE: IT IS THERE I PROMISE YOU, a bit hard to find] ...*I do not have this line*
Step 4:
Build.Prop finnished file
Change "ro.securestorage.support=true" to "ro.securestorage.support=false"
Step 5:
Go back into Xposed Framework, install and reboot and you MAY be fine. Most users will need to continue here. If you still have issues there are 2 methods to fully fix Xposed and S-Health
[Option 1: Download a fix module after Xposed re installed after the Build.Prop fix]
[Option 2: Disable S-Health completely]
Thanks to Compusmurf for mentioning about this module
Option1:
Step 1:
Go into Xposed Framework, download a module called "XSecureStorage"
Click Framework and hit Install/Update and you are good to go! If this module doesn't do the
trick, try Option 2. Option 2 is guaranteed to work since you will be disabling S-Health all together.
Option2:
Step 1:
In Settings App>>Application Manager find "SHealth" and select "Turn Off"
That will guarantee for Xposed to work fully fine with no lag. Leave a Thanks if this worked for you and post back if any questions or issues!
Last edited by chaunold; 2014-11-11 at 3:45AM.
Quick Reply Reply
12 users say Thank You to chaunold for this useful post
I only have ro.secure=0
Using Last pixel experience with Last alize Sanders kernel
Root SM-T707A on Lollipop with SuperSu - Xposed & Debloated - Part III
Where are we right now?
* Part I: Flash Stock Lollipop 5.0.2.
* Part II: Gain Root access for Lollipop with SuperSU.
* Part III: Flash Xposed Framework thru Flashfire. <---- YOU ARE HERE!
* Part IV: Debloat the tablet from both AT&T and most of Samsung stuff.
* Part V: Improve usability and aspect with Xposed Modules.
Part III: Flash Xposed Framework thru Flashfire
Disclaimer: I'm NOT, I repeat: I'm NOT responsible for any use you give this guide.
Prerequisites:
* In order to install Xposed framework, you MUST have your tablet Rooted with SuperSU as your superuser-giving app. If you followed the first 2 parts of this guide, you are ready! If not, go back to our first guide.
For starters, download these two files:
* Xposed Framework by dkcldark
* Xposed Installer APK
Copy both to the root of your external microsd.
Installing Flashfire
Now, head over to the Play Store, search and install "[root] FlashFire".
Open the app, the superuser request shows up so grant it root access.
After accepting the Disclaimer, you are ready to use the app.
Flashfire works almost like a custom recovery, giving most of the options you could get on TWRP or CWM and even more. Since the bootloader for the T707A is locked, Flashfire is our ticket to flash zip files to our System.
Press the "+" located on the lower right corner.
Choose Flash ZIP or OTA.
Tap "Internal Storage" and select "External SD card"
Now look for the "Xposed v85.0 LP by dkcldar.zip" and select it.
Don't modify any of the options and just tap the check mark.
Tap the big "FLASH" button to start the process and hit OK.
Wait for Flashfire to perform its magic, it should not take more than a minute. Your tablet will reboot in the process.
This boot is going to take A WHILE. The ATT logo will stay there more than than usual and after that, at least 206 apps are going to be optimized. So go and grab a drink or a coffee and relax.
Installing the Xposed Installer
We are back to our desktop, but the now Xposed Framework is ready.
What's left is to set up the Xposed Installer.
To do that, tap the folder icon on your bottom left corner of your desktop. Once inside sammy's file manager, select "SD Card" and look for the Xposed Installer.apk you copied before. Tap it and install the app.
Open it. Choose the first option "Framework".
If everything went well, you'll read:
"Xposed framework version 85.0 (by dkcldark)...is active".
If you have never used Xposed before, go back to the main menu and go to "Download". There you'll find all the apps and system modifications to enhance our tablet.
Important information while using Xposed
Using Xposed doesn't come risk free. You have to know that playing around with modules and apps puts you on the risk of soft-bricking the tablet. Since we can't use a custom recovery, coming back from a soft-brick is time consuming because you'll be forced to flash KitKat and the ota updates for Lollipop again, root with kingroot and switching it to SuperSu, flashing Xposed again.
But fear not my friend. I have tried over 20 modules, even conflicting ones. And so far, there wasn' t a single softbrick. While it's not exactly a guarantee, I have to say I'm pretty impressed with stability so far. Remember that modules thought for brands other than Samsung probably won't work (unless there's some common backgrounds). And even some modules for Samsung might not work as advertised.
Now I invite you to go to part 4 (in construction) of this guide if you're interested in debloating the tablet.
Or you can go to part 5 (in construction) where I discuss some interesting Xposed Modules and Apps that do work for the T707A tablet.
Special Thanks
* @Chainfire - For the fantastic FlashFire app as well as SuperSU.
* @rovo89 - For creating Xposed. A game changer.
* @dlckclark - For the modified version of Xposed for Samsung 5.0.X on Lollipop.
* @ashyx - For helping over PM and explaining in other threads how to get Xposed to work in Samsung tablets.
Where are Parts 4 and 5? And thanks for your work. I just bought the 707A without the knowledge that its a piece of junk compared to the 705.... In attempt to upgrade my 700 and gain LTE.
nFiniti said:
Where are Parts 4 and 5? And thanks for your work. I just bought the 707A without the knowledge that its a piece of junk compared to the 705.... In attempt to upgrade my 700 and gain LTE.
Click to expand...
Click to collapse
can you do a speed test for your 707A LTE speeds?
Just want to see if it is throttled like t705w
Gratitude!!
kainanmaki, I need to thank you for the time you've put in to create this guide. I will most likely gift you something for your efforts as I would've lost money on this so I may as well thank you in a way that matters. I'm not very familiar with software manipulations as such, but I do have an electronics/programming background and like others, have also made a mistake in purchasing the SM-T707A thinking it would an unbloated top of the line tablet.
The intention was to use it as an interface for the Mavic Pro drone, but it's sooooo laboured by (I'm guessing) all the AT&T and Samsung apps running in the background, it hasn't got enough processing power to communicate smoothly with the unit. Either that, or it's something to do with the USB interface (MIDI option not available)
Anyway, I digress.....there aren't too many discussions about rooting this model with the aim of upgrading the software or de-bloating. It's been hinted that the Tab S should have USB MIDI option which mine doesn't for some reason. More research required.
Thanks again kainanmaki - I look forward to the next instalment.
Cheers, JerichoJC
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
nFiniti said:
Where are Parts 4 and 5? And thanks for your work. I just bought the 707A without the knowledge that its a piece of junk compared to the 705.... In attempt to upgrade my 700 and gain LTE.
Click to expand...
Click to collapse
Looks like we've made a similar mistake. Looks great, but doesn't allow me to connect to what I want. Does yours allow USB MIDI option when a USB device is connected?
Hi, just curious, are the part 4 and 5 not happening at this moment?
kcmocam said:
Hi, just curious, are the part 4 and 5 not happening at this moment?
Click to expand...
Click to collapse
There's many reasons I haven't done this before:
1) My Tab-S display is not working and repairing it is as expensive as buying a new one.
So there's little I can do without the display
2) I do have a very extensive list (an excel sheet in fact), of every lollipop service included on this tablet. Which ones you could disable or remove with some explanations. Since I'm about to get my degree I won't have time for at least two more weeks to work on a guide.
After that I'll probably update Part IV with that information. It's amazing how much is debloatable (mostly samsung stuff, not just ATT).
Part V is just a matter of using the right xposed modules and/or apps to improve battery and usability. Modules like Amplify, alternate launchers an so on. Probably won't update that though.
Even without a guide, I know I personally would love a look at that excel sheet! Been trying to test randomly for a while now, but I know for sure there's a lot I'm missing. =\
Once I root my tablet, will I be able to install TWRP and a custom rom?
Samsung Xposed Safe Mode script v1.0
What does it do?
This is an init.d script which emulates the xposed safe mode where you can press any button during boot, get a vibrate (to know it detected you), and it will disable all your xposed modules. To be used in case of bootloops because of incompatible modules.
This only disables all modules so that you can boot. It does NOT actually uninstall or disable xposed itself.
Why would I need this?
I talked with the developer of xposed for Samsung, wanam, and apparently, xposed safe mode was disabled for Samsung devices due to a Knox issue (if you disabled xposed, Knox will hate you and refuse to boot the phone). This is good, but if you have a bootloop, AND you're on a bootloader locked device, you have NO CHOICE but to wipe your data. Ouch!! That's a heavy penalty for accidentally installing one malfunctioning module!
Or maybe your phone still is bootloader unlocked, but you're running Samsung xposed and safemode is still disabled for you. Then you'd rather have xposed safemode back just for the ease of not having to go through recovery to fix things.
How does it work?
1. Press any of three buttons during boot (volume keys, or home button). You have 10 seconds from bootup to choose to do this.
2. System will give you 2 short vibrates to tell you it detected it.
3. Press any button 4 more times, each time will give you another short vibration.
4. One long vibration will signal to you that xposed has been disabled.
5. The script will automatically reboot your device in 6 seconds. This is because we can't disable xposed, so xposed will STILL load modules on this bootup, which means you'll still see the bootloop momentarily until you reboot.
Great! How do I install it?
This is an init.d script, so you need init.d support in your phone. Obviously, if you have a bootlocked device, you probably don't have init.d support. This is not a guide on how to get init.d support, but I'll offer you a few tips you can use to search yourself.
- install-recovery.sh, since it's called by init.rc during boot, can be hijacked in order to create an init.d system.
- If install-recovery didn't work, SuperSU also includes an su.d directory which is executed at a similar time. Just throw a script in there, or throw a script in there which enables use of the init.d folder (run-parts /system/etc/init.d).
Anyways, here's how you install it:
- Place the script you downloaded into
Code:
/system/etc/init.d
OR
Code:
/system/su.d
Give the script proper permissions for the folder it's in
- For su.d folder, it is root:root 0700 (rwx------)
- For init.d folder, it could be a variety of permissions. My init.d folder runs as a result of su.d, so I gave it same permissions as su.d. If yours doesn't, then you might want to try root:root 0755 (rwxr-xr-x)
- The important point here is to make sure it's at least root user and group, readable and executable, rwxr-xr-x
Will it work on my device?
It should work on any device really, if you follow the simple instructions. But I've only tested it on the ATT S4 (Lollipop 5.0.1), so I can't guarantee it will work on your device. Test it out and see if it works for you! It probably will!
You saved me!
I'm glad to hear that! I love to hear and see a thanks, so make sure to click the thanks button and maybe write a post too!
Bugs and problems
You know how to report bugs and issues. State all relevant information related to the problem; device, problem in clear detail, with reproducible steps, and anything else you might need.
Related custom xposed builds
Here are a list of Samsung custom xposed builds I know this "safe mode problem" to be present in. (Don't forget, this problem is likely to be in any and all Samsung xposed custom builds due to the nature of the Knox problem).
[UNOFFICIAL] Xposed for Samsung Lollipop by arter97
[UNOFFICIAL][5.0][v87.1][03 Dec] Xposed for Samsung Lollipop 5.0.x
[UNOFFICIAL][5.1/6][v87.1][28 Nov]Xposed for Samsung Lollipop/Marshmallow
Disclaimer: As usual, while I've made every attempt to make it perfect, there are no guarantee it will work for you. By using this, you agree not to hold me accountable in case something bad happens to you (or it didn't save your device)! Do your own testing to make sure it works before you actually need to use it in an emergency!
FAQ
It didn't vibrate
You probably have a different device which places the vibrator in a different location. I don't have your device, so maybe you'll need to help me debug and find where the vibrator is located at.
It didn't work!
What happened? Give me some detailed information about exactly what you did, what happened, and the device you're on!
Some possible problems to investigate are:
Does the script have correct user: owner and permissions?
Is your init.d or su.d system even working? Make sure it is first
Nice work!
It should help with incompatible modules leading to a bootloop, but it won't prevent Xposed from loading, the flag "/data/data/de.robv.android.xposed.installer/conf/disabled" is ignored on my Xposed version, done here for a reason, i got many bootloop reports in the past by people accidentally triggering safe mode by physical buttons, leading to Knox refusing to deal with modified binaries.
Fortunately it does not seem to be the same with TouchWiz 7.0, so i will bring it back later for Nougat.
wanam said:
Nice work!
It should help with incompatible modules leading to a bootloop, but it won't prevent Xposed from loading, the flag "/data/data/de.robv.android.xposed.installer/conf/disabled" is ignored on my Xposed version, done here for a reason, i got many bootloop reports in the past by people accidentally triggering safe mode by physical buttons, leading to Knox refusing to deal with modified binaries.
Fortunately it does not seem to be the same with TouchWiz 7.0, so i will bring it back later for Nougat.
Click to expand...
Click to collapse
Thank you!
It certainly will help a lot for disabling incompatible modules. Yes, although it doesn't technically disable xposed itself. It's really great that future versions aren't that way!
I actually thought of creating another script which utilizes back and menu key buttons to actually uninstall xposed from backups (an actual disable xposed script of sorts), but I thought it was too much.
Hi, all. I am trying to enable multiple users on my S6 Active. I'm aware there's no root exploit for this device, but enabling multiple users normally doesn't require rooting a Samsung device, just installing a custom recovery so that I can boot without read-only applied to the system partition.
Can TWRP (or any recovery that allows adb write access to the system partition) be installed onto an S6 Active, running Android 7.0.1? I read something about how it could trip Knox, but I'm a bit unclear on how bad that is -- I don't understand if tripping Knox totally disables the device or just deactivates Samsung-specific features like Samsung Pay. Personally, so long as Google Play and calling/texting work normally, I couldn't care less about Samsung-specific apps being disabled, and I don't care about the warranty.
Alternatively, any other method to enable multiple users would be warmly welcomed. (If I need to install an app or something to simulate multiple users, that's probably fine, if it works.)
Thanks in advance for any help. I know this is an older device and people have probably moved on from it.