Related
I have rooted my Hero and have root acces on 2.73.405.5. (no custom rom)
How do i get busybox installed on it without installing custom rom?
Would this work or is there a newer build ?
http://benno.id.au/blog/2007/11/14/android-busybox
Ok, I installed busybox according tutorial mentioned before but everytime after a restart i need to re-enter "export PATH=/data/busybox:$PATH" to have busybox cmd set again.
Isn't there a method to have it permanent?
find out where the path is set for android system and alter it?
kendong2 said:
find out where the path is set for android system and alter it?
Click to expand...
Click to collapse
Isn't there some tutorial?
I doubt i'm the only one with this problem
probably not the only one, but one of a few. most people who want to have root access and gadgets like busybox & co install modacos custom rom, where it works. maybe google can help (lol in two ways: either as a search engine or as maintainer of the official android documentation...)
Hello, im about to get this thing tomorrow and just wanted to know the best way to root it and all that. (Used to Samsung Galaxy S3 and Note 3 to root via Odin.)
So first of all i am going to tell you abit of what i'm getting here, it's the Xperia Z2 tablet with LTE/4G Android 4.4.2 pre-installed (i guess it's the international device if there is one) and what i can understand of what the model it's going to be "Castor" right?
So my question now is, what tools do i need to root it and install the recovery? and what recovery do you recommend? is it a damn hassle?
and what specific roms will actually work for this device? im looking for a CM based rom such as AOSP/AOSPA or as close to vanilla 4.4.x
Im also having some questions about the build.prop and DPI
Whats stock DPI?
What's the lowest DPI possible to use (still readable)
What DPI are you using/recommending?
Thanks in advance.
Great regards mattish.91
mattish.91 said:
what tools do i need to root?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2784900
mattish.91 said:
Im also having some questions about the build.prop and DPI
Whats stock DPI?
What's the lowest DPI possible to use (still readable)
What DPI are you using/recommending?
Click to expand...
Click to collapse
Stock DPI is 240, and I have actually not changed it so I can't give any advice on that.
Sent from my Xperia Z2 Tablet using Tapatalk
UgloBuglo said:
http://forum.xda-developers.com/showthread.php?t=2784900
Stock DPI is 240, and I have actually not changed it so I can't give any advice on that.
Sent from my Xperia Z2 Tablet using Tapatalk
Click to expand...
Click to collapse
I would be careful which version of the tablet you have. Despite claims to the contrary, it does NOT work with the latest firmware and model information. I highly suggest checking the model numbers of people who got it to work and avoiding model numbers that don't yet work if you need it rooted right now.
EDIT: Actually, maybe it does work on all models. I have SGP561 with Firmware 17.1.D.0.417 and after running it the errors made it look like it failed, but after a reboot and waiting a little while I was able to edit files in Root Explorer (although some editors couldn't edit the files, which was weird) and of course I can't edit bootanimation.zip, but it's mostly rooted by the looks of things.
Elliander said:
I can't edit bootanimation.zip, but it's mostly rooted by the looks of things.
Click to expand...
Click to collapse
I just wanted to let you know that 4.4.x you cant change anything with the bootanimation.zip i have tried on multiple devices and found out that you actually cant unless you use a rom with cm11s features. Im able to change the boot animation trough settings on my note 3 which got some features from cm11s. I would love to see a rom for xperia tablet z2 that is based on temasek71's source. [email protected] @xda and temasek.hopto.org for devices and such. The best rom i have ever used in my life, it's unofficial cm11 and is 90% Of the time stable and fully working.
Thanks for the heads up
mattish.91 said:
I just wanted to let you know that 4.4.x you cant change anything with the bootanimation.zip i have tried on multiple devices and found out that you actually cant unless you use a rom with cm11s features. Im able to change the boot animation trough settings on my note 3 which got some features from cm11s. I would love to see a rom for xperia tablet z2 that is based on temasek71's source. [email protected] @xda and temasek.hopto.org for devices and such. The best rom i have ever used in my life, it's unofficial cm11 and is 90% Of the time stable and fully working.
Thanks for the heads up
Click to expand...
Click to collapse
If I backup the DRM keys, change to a custom ROM, change the boot loader, then restore to an official ROM with DRM keys restored, would the boot loader remain changed?
Is there a simple way to convert a video file to a boot loader?
EDIT: it also appears that I can't copy any files to the root folder. I want to install Ubuntu as a workaround to the fact that flash doesn't work anymore, even the modified version. I was thinking I could install Ubuntu and then install flash on that and get all my flash programs to work again, but for some strange reason I can't mount as read write anything in the root directory even though I can edit files in system. I'm not sure if I could call it being rooted if I don't have access to the root folder.
Elliander said:
If I backup the DRM keys, change to a custom ROM, change the boot loader, then restore to an official ROM with DRM keys restored, would the boot loader remain changed?
Is there a simple way to convert a video file to a boot loader?
EDIT: it also appears that I can't copy any files to the root folder. I want to install Ubuntu as a workaround to the fact that flash doesn't work anymore, even the modified version. I was thinking I could install Ubuntu and then install flash on that and get all my flash programs to work again, but for some strange reason I can't mount as read write anything in the root directory even though I can edit files in system. I'm not sure if I could call it being rooted if I don't have access to the root folder.
Click to expand...
Click to collapse
I guess what you'r trying to say is that you have a video that you want to use as boot animation? There is multiple tools to create pictures from a video and compile the pictures to a bootanimation.zip, even IF you got a boot animation zip, you wouldn't be able to replace the original zip if you are running android 4.4.x i don't know why but you can't. I can't really say why you only can edit some files are u Sure you have su binaries updated? If you wan't to change the bootanimation, i would recommend you to find a rom based on cyanogenmod 11s (the oneplus one version of cm) as far as i know there is none for xperia z2 yet, but when i come to the level of developing for android i will definitly try to compile one ^^. Yesterday i wrote to temasek71 and asked if he were intrested in developing for tablet, but i havn't got an answere yet, it's his birthday today ^^
mattish.91 said:
I guess what you'r trying to say is that you have a video that you want to use as boot animation? There is multiple tools to create pictures from a video and compile the pictures to a bootanimation.zip, even IF you got a boot animation zip, you wouldn't be able to replace the original zip if you are running android 4.4.x i don't know why but you can't. I can't really say why you only can edit some files are u Sure you have su binaries updated? If you wan't to change the bootanimation, i would recommend you to find a rom based on cyanogenmod 11s (the oneplus one version of cm) as far as i know there is none for xperia z2 yet, but when i come to the level of developing for android i will definitly try to compile one ^^. Yesterday i wrote to temasek71 and asked if he were intrested in developing for tablet, but i havn't got an answere yet, it's his birthday today ^^
Click to expand...
Click to collapse
So even an unlocked boot loader can't edit bootanimation.zip ?
Ya, I'm pretty sure it's rooted with su binaries. I was able to edit files in system anyway. It's just that I have no access to the root folder and a few other places. Also, as I posted elsewhere, shortly after getting it rooted a new problem developed where random apps on the Play Store would not allow me to install them because it says there is insufficient storage available, even though I have more than 20 gigabytes free space internal and more than 100 gigabytes free space external. Sideloading those apps don't help, but other apps install without a problem. None of the normal solutions work, and there are no traces of the files I can't install that I can find anyway. It seems as though I triggered some kind of security program at Verizon put on the device when I rooted it. It's so bad I am considering either a factory reset or flashing an updated official ROM without the branding, but I don't know if a factory reset would also wipe the carrier unlock ( from what I read it might or might not) and the only images I can find are for a different model number and I don't know if they work and I also don't know if the DRM keys will remain intact. Its so bad that I would advise anyone with a verizon branded z2 who wants to keep stock firmware to avoid rooting at all. I should have just bought an international version instead.
A custom ROM would be great, but aren't there specific apps that you can only install if you have the DRM keys working? I mean, if I could independently buy them I would probably not miss the DRM keys, but aren't these important features like infrared and video quality?
Correction! It all works!
EDIT: I backed up everything with Titanium Backup (and moved the backup to SD and removed the SD to be safe) and then performed a factory reset. (The APN settings will be wiped, so to anyone reading this: Don't freak out if your mobile data plan doesn't seem to work.) and then performed an Easy Root and this one is looking MUCH cleaner:
Code:
==============================================
= =
= Easy Root Tool v11 =
= Supports various Xperia devices =
= created by zxz0O0 =
= =
= http://forum.xda-developers.com/ =
= showthread.php?p=53448680 =
= =
= Many thanks to: =
= - [NUT] =
= - geohot =
= - MohammadAG =
= - cubeundcube =
= - nhnt11 =
= - xsacha =
= =
==============================================
=============================================
Waiting for Device, connect USB cable now...
Make sure you have only one Android device connected
BlueStacks emulator can also cause problems
=============================================
Device found
=============================================
Getting device variables
=============================================
Device model is SGP561
Firmware is 17.1.D.0.417
=============================================
Sending files
=============================================
35 KB/s (1585 bytes in 0.044s)
3608 KB/s (657704 bytes in 0.178s)
158 KB/s (1133 bytes in 0.007s)
99 KB/s (9496 bytes in 0.093s)
580 KB/s (13672 bytes in 0.023s)
Copying kernel module...
647 KB/s (34473 bytes in 0.052s)
46 KB/s (767 bytes in 0.016s)
948 KB/s (13592 bytes in 0.014s)
Kernel version is 3.4.0-perf-g31245c3
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
19 bytes transferred in 0.001 secs (19000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xCFADE050
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Loading towelzxperia
=============================================
698 KB/s (13592 bytes in 0.019s)
2639 KB/s (197320 bytes in 0.073s)
=============================================
Waiting for towelzxperia to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
mount: Operation not permitted
cleaning up
done
Checking if device is rooted...
Device rooted.
=============================================
Checking for Sony RIC
=============================================
Sony RIC Service found.
Installing RIC kill script installmount.sh...
Stock mount does not exist. Creating dir and link
Installing of mount.sh finished
Done. You can now unplug your device.
Enjoy root
=============================================
What to do next?
- Donate to the people involved
- Install SuperSU by Chainfire
- Install dualrecovery by [NUT]
- Backup TA partition
Press any key to continue . . .
I then had absolutely NO problems with TA-backup and was able to run adbd-insecure (which I couldn't before) and was able to successfully create the TA.img file for my DRM keys (which I also couldn't before).
I then had no problems editing Platform.XML to restore SD card access, and I have no problems creating folders in the root and moving files into it (although moving very large files to a folder in the root seems to cause the tablet to freeze up and reboot a few minutes later, which bites because I am trying to get Ubuntu. I'm going to have to go with a smaller image.)
Finally, I was able to restore all of my settings and app data without difficulty with Titanium Backup *AND* I was able to freeze or delete the system apps I so hated! (Unfortunately, even after enabling SD write access, Titanium Backup is oddly unable to write to SD. I had to manually copy the backup folder from SD back to internal and then reboot before I could even restore the backups as well. I thought that was very strange. Especially since I have a Pro version.)
Conclusion: The problems I went through were largely related to all of the failed rooting attempts. Don't try anything EXCEPT "Easy Root". It's all you need, and if you start with it you shouldn't have any problems. If you have the problems I had, you will have to do a factory reset before you can fully root the device.
As a side note, it needs to be mentioned that the Xperia Z2 tablet has a "Rooting Status" flag which is a permanent trigger. Even after a factory reset without root the flag remains triggered. If you are concerned about warranty you should be aware of it. Also, after I performed the factory reset I was unable to get rid of the Verizon "Tablet Activation" message permanently. I didn't have it before, but now I have it.
A Rooting Status Flag??
First time I hear about this with Z2. One of the reasons I've chosen this device and not the Galaxy Tab S.
Could you give more information or a link about this?
Vaetheran2107 said:
A Rooting Status Flag??
First time I hear about this with Z2. One of the reasons I've chosen this device and not the Galaxy Tab S.
Could you give more information or a link about this?
Click to expand...
Click to collapse
Well, mine is a Verizon branded factory unlocked SGP561. In:
System > About Tablet >
There is a setting on the bottom that says "Rooting Status" and beneath that, even before I managed to fully unroot it, the status said "Rooted". If you need it I can send a screenshot of the actual status.
After a factory reset it still said it and I assumed the root would have been lost after that (especially since I used the unroot option in SuperSU after), but a few of my bugs related to the bad rooting attempt resurfaced (not as bad though, and it goes away after a reset and restore of data) and after a subsequent factory reset I noticed I still had root access even without using easy root again. I also found that I could not find a way to unroot. I tried Universal Unroot today and it asked for super user privileges, granted it, and restarted itself, but even it couldn't unroot the device. So at this point I don't know if that flag would go away if the device is unrooted because I don't really know how to unroot at this point.
The important thing is that I was able to backup the DRM keys though, so now I have the option of trying other firmwares and later going back to what I had. My next step is going to be flashing an unbranded firmware over the branded firmware and see how that works for me.
well xD
I got my device today and also had some troubles rooting, adb and fastboot but once I got the thing of it, it was pretty easy, I got some good and some bad answers to my questions but now its all good xD running the latest carbon ROM as I type and it works just great, there is no wayim going back to sonys stock pre installed crap xD, just wanted to let you know that I did a backup but not the img file and hopefully won't need it anytime soon xD. Next step is backup and DPI change in my build.prop file to get everything just a bit smaller than it is right now.
Good luck rooting your devices and remember ALWAYS make an backup of your current system, including if you'd just doing an update. :victory:
mattish.91 said:
I got my device today and also had some troubles rooting, adb and fastboot but once I got the thing of it, it was pretty easy, I got some good and some bad answers to my questions but now its all good xD running the latest carbon ROM as I type and it works just great, there is no wayim going back to sonys stock pre installed crap xD, just wanted to let you know that I did a backup but not the img file and hopefully won't need it anytime soon xD. Next step is backup and DPI change in my build.prop file to get everything just a bit smaller than it is right now.
Good luck rooting your devices and remember ALWAYS make an backup of your current system, including if you'd just doing an update. :victory:
Click to expand...
Click to collapse
When you say backup, do you mean anything more than the user + system apps that Titanium backup makes?
Elliander said:
When you say backup, do you mean anything more than the user + system apps that Titanium backup makes?
Click to expand...
Click to collapse
Yes, like a recovery backup. IF you fu** anything up you can always restore that backup from recovery
wow!
I just changed to 180 dpi instead of 240 and it looks awesome so far all apps tested is working flawlessly, defenitly to recommend definitly looks like a tablet now
Look at it here: https://plus.google.com/+MattiasMagnusson
Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.
Does anyone know if the 10E update still lets you use ADB commands? That is how I am changing my DPI and if it does not work in the new update I will not update it.
Just a question, isn't the Settings/Display/Display size change the DPI also ? Why do you need to use fastboot commands?
adit9989 said:
Just a question, isn't the Settings/Display/Display size change the DPI also ? Why do you need to use fastboot commands?
Click to expand...
Click to collapse
Because I like it a crap ton smaller than what the settings allow me to take it down to. On stock android you can change the smallest width in dev options but that setting is not visible. So the fastboot command basically lets you modify that setting because it exists but is not available to be edited.
jaedenhudson14 said:
Because I like it a crap ton smaller than what the settings allow me to take it down to. On stock android you can change the smallest width in dev options but that setting is not visible. So the fastboot command basically lets you modify that setting because it exists but is not available to be edited.
Click to expand...
Click to collapse
I Thought the dpi change was done with adb instead of fastboot. Correct me if im wrong.
R800x_user said:
I Thought the dpi change was done with adb instead of fastboot. Correct me if im wrong.
Click to expand...
Click to collapse
Yes. ADB. NOT fastboot. My error. You can change the smallest width setting in adb commands. Another thread in here explains how to do that.
ADB commands aren't neutered. It's the fastboot commands that are.
I'm still sitting on 10c, waiting for something from T-Mobile hoping to fix the SMS glitches that keep deleting my messages.
Based on the info provided by @ACalcutt here ...
Which is further based on the LG G4 Hotspot app offered by @geoff5093 here ...
I present View attachment VS995_VerizonHotspotUnlocker.zip
This is a flashable ZIP file that performs the exact same operations listed in @ACalcutt's post above. No messing around with copying files or setting permissions, simply flash and boot and go!
Modifications from @ACalcutt instructions:
- Name of APK is simply HotspotProvision.apk as the original is named, not HotspotProvisionVZWG4.apk.
- README file is placed in the /system/app/HotspotProvision directory to notify that modifications have been made.
Enjoy!
NOTES
- This should probably be used only on Verizon VS995 *stock* ROMs
- This was only tested on VS995 13A firmware
- Works with other carriers (MVNOs, etc., not just Verizon).
- ROOT *is required* (...at least AFIAK...feel free to test without, but I don't think it will work).
Can you make a similar zip for AT&T V20 (H910)?
dksoni411 said:
Can you make a similar zip for AT&T V20 (H910)?
Click to expand...
Click to collapse
I can try...but as I don't have an H910 I'm not sure how well it will work without extensive testing from someone else.
I found this post here which describes a method to do it:
https://forum.xda-developers.com/v20/how-to/att-v20-enable-hotspot-unlimited-data-t3524784
Have you tried this method? Does it work?
Are you just looking for a way to flash these settings without having to resort to the manual editing shown there?
Assuming that method works, and assuming that sed is installed on these devices (or I can somehow include it in the installer) I should be able to do it.
If you are just looking for a one time fix I'd recommend following the link above, but if you really need a repeatable way let me know and I'll see what I can do.
I have tried that method and it works.
I wanted to have it through an automatic process. There are many people who tries to root V20 everyday and need that easy way.
I also need it for repeated times because I do test different roms on V20 (it is a test device for me). So if you can make an zip to do that process all automatically that be really awesome and will save a lot of time of others people. Also I will be able to include in my root guide to directly flash while rooting an H910
dksoni411 said:
I have tried that method and it works.
I wanted to have it through an automatic process. There are many people who tries to root V20 everyday and need that easy way.
I also need it for repeated times because I do test different roms on V20 (it is a test device for me). So if you can make an zip to do that process all automatically that be really awesome and will save a lot of time of others people. Also I will be able to include in my root guide to directly flash while rooting an H910
Click to expand...
Click to collapse
Ok, let's start with this little shell script:
Code:
#!/sbin/sh
#
su
settings put global tether_dun_required 0
/system/bin/sed -i 's/name="tether_entitlement_check_state" value="5"/name="tether_entitlement_check_state" value="0"/' /data/system/users/0/settings_system.xml
Basically all this does is issues that "settings" command that the link says needs to be set.
Then, it searches for the tether_entitlement_check_state within the settings_system.xml file and changes it from 5 to 0.
Go ahead and run these commands from a terminal emulator on your device and see if they work.
Make sure your device is clean...as in you haven't made these mods already. You can revert to a non-working config by putting the 0 back to a 5 and issuing the following:
Code:
settings put global tether_dun_required 1
I'm also attaching a shell script you can copy over. You will have to set +x perms on the script to run it.
If this script does what we want it will them be trivial for me to pack it into a flashable zip for you.
TraderJack said:
Ok, let's start with this little shell script:
Code:
#!/sbin/sh
#
su
settings put global tether_dun_required 0
/system/bin/sed -i 's/name="tether_entitlement_check_state" value="5"/name="tether_entitlement_check_state" value="0"/' /data/system/users/0/settings_system.xml
Basically all this does is issues that "settings" command that the link says needs to be set.
Then, it searches for the tether_entitlement_check_state within the settings_system.xml file and changes it from 5 to 0.
Go ahead and run these commands from a terminal emulator on your device and see if they work.
Make sure your device is clean...as in you haven't made these mods already. You can revert to a non-working config by putting the 0 back to a 5 and issuing the following:
Code:
settings put global tether_dun_required 1
I'm also attaching a shell script you can copy over. You will have to set +x perms on the script to run it.
If this script does what we want it will them be trivial for me to pack it into a flashable zip for you.
Click to expand...
Click to collapse
The script didn't worked as expected. As I was using SuperV20 rom, the tether entitlement check line wasn't in expected file.
After writing command in adb shell (then su) my internal storage was locked (un-writeable). I had to reflash whole superv20 rom from beginning and then manually adding the missing lines in mentioned file. Then it worked like charm.
Can you add a condition in zip about if the line is missing it should be added.
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
Also can you help me about this notification that appear when mobile data is turned off.
dksoni411 said:
The script didn't worked as expected. As I was using SuperV20 rom, the tether entitlement check line wasn't in expected file.
After writing command in adb shell (then su) my internal storage was locked (un-writeable). I had to reflash whole superv20 rom from beginning and then manually adding the missing lines in mentioned file. Then it worked like charm.
Can you add a condition in zip about if the line is missing it should be added.
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
Also can you help me about this notification that appear when mobile data is turned off.
Click to expand...
Click to collapse
I'll need you to send me some full copies of the settings_system.xml file - preferably from more than one ROM so I can see the full structure.
Also, I'm concerned by your description re: "internal storage was locked." I don't see how anything I provided you would cause your external storage to be locked. I certainly don't want to distribute anything that is going to cause someone to have to reflash their entire ROM.
Will this work for LG V20 with the Verizon VS99520c Oreo?
Will this work for LG V20 with the Verizon VS99520c Oreo patch 10/1/18 as shown in the attached picture?
Also, what's the easiest way to root?
Please help is appreciated.
Thanks for your time and response.
Eugene
TraderJack said:
Based on the info provided by @ACalcutt here ...
Which is further based on the LG G4 Hotspot app offered by @geoff5093 here ...
I present View attachment 4508476
This is a flashable ZIP file that performs the exact same operations listed in @ACalcutt's post above. No messing around with copying files or setting permissions, simply flash and boot and go!
Modifications from @ACalcutt instructions:
- Name of APK is simply HotspotProvision.apk as the original is named, not HotspotProvisionVZWG4.apk.
- README file is placed in the /system/app/HotspotProvision directory to notify that modifications have been made.
Enjoy!
NOTES
- This should probably be used only on Verizon VS995 *stock* ROMs
- This was only tested on VS995 13A firmware
- Works with other carriers (MVNOs, etc., not just Verizon).
- ROOT *is required* (...at least AFIAK...feel free to test without, but I don't think it will work).
Click to expand...
Click to collapse
Hotspot fix doesn't work with Alpha Omega Oreo
Hotspot fix doesn't work with Alpha Omega Oreo.
Vs995
Guys, this was simply a flashable zip that performed the steps outline from the links in the OP.
If the steps don't work anymore on Oreo, etc, then the zip won't work.
If someone wants to find out what the steps required on Oreo are, I can attempt another zip.
Otherwise, this has only been validated on the build listed in the OP.
Just wanted to say this still works on stock Oreo 20c. Thanks for the zip.
xaxxelous said:
Just wanted to say this still works on stock Oreo 20c. Thanks for the zip.
Click to expand...
Click to collapse
Thanks for the update.
xaxxelous said:
Just wanted to say this still works on stock Oreo 20c. Thanks for the zip.
Click to expand...
Click to collapse
Did you do any additional steps, and are you using a Verizon sim card? I happen to be using a straight talk sim card which still using the same verizon apn values but my hotspot just suddenly stopped working one day giving me the notification "Connected - no internet" on the devices I wanted to use it with. I've tried stock, lineage, resurrection, alpha omega, and always the same dissapointment.
adriascw said:
Did you do any additional steps, and are you using a Verizon sim card? I happen to be using a straight talk sim card which still using the same verizon apn values but my hotspot just suddenly stopped working one day giving me the notification "Connected - no internet" on the devices I wanted to use it with. I've tried stock, lineage, resurrection, alpha omega, and always the same dissapointment.
Click to expand...
Click to collapse
I flashed /system and /boot from a VS995 kdz onto my US996 to see if I could get video calling and and visual voicemail working. Yes, I am on Verizon... So maybe it only worked because most of my firmware is really mostly US996. I'll have to look when I have time, but I think we can do all sorts of crossflashing now with our V20s. Maybe you can flash an entire US996 kdz, then flash /system and /boot from a VS995 kdz.
xaxxelous said:
Just wanted to say this still works on stock Oreo 20c. Thanks for the zip.
Click to expand...
Click to collapse
Did you get this to work on a rooted stock Oreo 20c vs995? If so, could you describe how you got root on 20c?
I've been trying for the past weekend on my vs995 with a verizon sim card and haven't been able to get the hotspot function to work even with root on 20b. hotspot.apk is in the right place with the proper permission, but nothing happens when I push the slider to turn on the hotspot.
I was able to get the netshare+ app to work on the rooted 20b, but it uses an android generated random password which changes every time it is run. And it does not work without root on 20b or 20c.
Thanks!
Zac96122 said:
Did you get this to work on a rooted stock Oreo 20c vs995? If so, could you describe how you got root on 20c?
I've been trying for the past weekend on my vs995 with a verizon sim card and haven't been able to get the hotspot function to work even with root on 20b. hotspot.apk is in the right place with the proper permission, but nothing happens when I push the slider to turn on the hotspot.
I was able to get the netshare+ app to work on the rooted 20b, but it uses an android generated random password which changes every time it is run. And it does not work without root on 20b or 20c.
Thanks!
Click to expand...
Click to collapse
Sorry for the delay, I've been away for work. It sounds like you may be misunderstanding some things or I am misunderstanding you...
First, I don't have a true VS995, I have a US996 that had I crossflashed to VS995 to test some things. I rooted with Magisk.
Second, why are you putting an .apk anywhere and checking permissions? This is meant to be flashed via TWRP. Did you do that? I didn't do anything special. I just did what the OP said: flashed in TWRP, rebooted and hotspot worked.
It's partially working for me in every 20c, either real stock or based on stock on a true vs995. Bluetooth and USB tether are working. Mobile hotspot is not. However there is no error, or directing me to pay Verizon--the slider does nothing. It seems like there is something small here I need to find, but I don't know where to look. Might anyone be able to direct me to the proper log file to investigate?
computererds said:
It's partially working for me in every 20c, either real stock or based on stock on a true vs995. Bluetooth and USB tether are working. Mobile hotspot is not. However there is no error, or directing me to pay Verizon--the slider does nothing. It seems like there is something small here I need to find, but I don't know where to look. Might anyone be able to direct me to the proper log file to investigate?
Click to expand...
Click to collapse
Try using the mobile hotspot icon in the top level swipedown menu. I was able to enable my hotspot that way though the slider does not work. This is on the 20b firmware with root.
I have the modified 20c firmware if anyone wants it. A friend found it on baidu and sent it to me. I haven't tried it yet though as the 20b version is working well for me so far. If there is a place to post it, let me now and I'll upload it. It's about 3 GB.