Related
I'm an AT&T unlimited plan user trying to figure out the least painful way to enable tethering, preferably without wiping the device, and then unroot it. The story is I can't root permanently because my employer uses a nasty MDM (MaaS360) that checks for root. You can use Xposed to mask it, but don't think that's an option yet on Lollipop. Is there any way to root, edit build.props, and unroot all without wiping? I know you can temporarily flash something like TWCR, but that requires unlocking the bootloader, which wipes the device. Thoughts?
Thanks a ton!
PS: Keeping OTA updates working would be amazing ☺
Settings -> More - > Tethering & portable hotspot.
No root required.
knitler said:
Settings -> More - > Tethering & portable hotspot.
No root required.
Click to expand...
Click to collapse
Won't work for those of us with AT&T unlimited plans. Should have mentioned that... Will update.
1. Use the Nexus Multitool to root your phone
2. Download Root Browser
3. Go to /System/ and open your build.prop file - it will give you the option to open in a text editor
4. At the end of the file, add "net.tethering.noprovisioning=true" (without quotations)
5. Reboot and test the hotspot by going to your settings app, more, then tethering & mobile hotspot
6. Use the Multitool to unroot your phone
Nevermind, I'm an idiot. You'll lose the build.prop edit when you un-root.
Won't unrooting require flashing to stock and loss of user data?
mtpease said:
1. Use the Nexus Multitool to root your phone
2. Download Root Browser
3. Go to /System/ and open your build.prop file - it will give you the option to open in a text editor
4. At the end of the file, add "net.tethering.noprovisioning=true" (without quotations)
5. Reboot and test the hotspot by going to your settings app, more, then tethering & mobile hotspot
6. Use the Multitool to unroot your phone
I don't have an AT&T Sim to test it, but it should work for you
Click to expand...
Click to collapse
gsmm0n said:
Won't unrooting require flashing to stock and loss of user data?
Click to expand...
Click to collapse
You're right. I don't know what I was thinking. I can't think of any way to un-root without losing the build.prop edit.
Sorry.
Why not just do the edits needed and stay rooted? Its not like being rooted causes anything bad to your device. You'll still get OTAs, and even if you did get a OTA. The OTA script would fail because you performed a modification on /system/build.prop which would need you to undo the added line.
You can always just go into SuperSU and uncheck "Enable SuperSU" if you don't want root.
Only reason I'm avoiding it is because my employer uses a MDM that will stop my corporate access from working if rooted... I suppose that might work though, but thinking it may still detect SuperSU...
zephiK said:
Why not just do the edits needed and stay rooted? Its not like being rooted causes anything bad to your device. You'll still get OTAs, and even if you did get a OTA. The OTA script would fail because you performed a modification on /system/build.prop which would need you to undo the added line.
You can always just go into SuperSU and uncheck "Enable SuperSU" if you don't want root.
Click to expand...
Click to collapse
gsmm0n said:
Only reason I'm avoiding it is because my employer uses a MDM that will stop my corporate access from working if rooted... I suppose that might work though, but thinking it may still detect SuperSU...
Click to expand...
Click to collapse
Could always give it a try, you'd have to wait for Xposed to work with ART and then you can use RootCloak
http://repo.xposed.info/module/com.devadvance.rootcloak
gsmm0n said:
Won't unrooting require flashing to stock and loss of user data?
Click to expand...
Click to collapse
You don't need root to make changes to your phone. All you need is an unlocked bootloader. Copy the file on to storage where it can be edited and make the changes. Then boot into bootloader and boot twrp by executing "fastboot boot twrp.IMG" or whatever image name it came with. This will just boot and not actually install twrp. Once in recovery, use the explorer to copy the newly edited file back to original location.
Check permissions on the old file before you do it and if needed make them the same as the new version. Also, make sure you do a backup while you're there in case you mess up something.
By the way if you have sprint or tethering doesnt work you have to edit more then just that line in build.prop
Check here for more details http://forum.xda-developers.com/showthread.php?t=2949024
in the subsequent posts below, you will find all the info you need for not only the device but the ROMs I have had my hands in.
each person who I pulled the files from will get a thanks in the posts as necessary
NonSense 1.04
Disclamer: these files are meant specifically for the HTC Desire 510. Use these files at your peril, you assume any responsibility for loss or damage that may result from use of these files or procedures. what has been included in this tutorial is for the HTC Desire 510
You have been warned.
note: from now on CRI signifies cricket, and B-S signifies sprint/boost if those signifiers aren't used, it applies to both type of this phone
now to the goodies.....
List of supplies:
1. Phone (HTC Desire 510)
2. USB cord that syncs with the PC
3. USB drivers installed for the phone
4. the zip files from this location. click here
4.1 there are 2 different versions of the same ROM, but the *1.04-lean.zip is US only (refer to changes to see why).
4.2 CRI for cricket/att, B-S for boost/sprint
5. read these instructions completely before attempting
before we get started make sure you have supersu (which can be downloaded from here), and NonSense1.04.zip copied to the root of your external SD card
NETWORK UNLOCK (I.E. switching services)
as this phone is LTE compatible, it takes a SIM card no matter the service to receive calls and data. so it stands to presume all you need to do is network unlock the device (Sprint calls it UICC unlock, others it's the Network Unlock Code)
the phone needs to be network (SIM) unlocked in order to switch it from cricket to sprint, or from sprint to virgin mobile, etc.
to network unlock the phone:
1. make sure you are on stock ROM (the one that came with the phone, not the one listed in this post nor CM)
2. call the respective original service provider of the phone (i.e. cricket, sprint, etc.) and tell them that you are leaving the country (like to Australia) and you want to unlock the SIM so you can use your device for service down there.
2.1 if you bought the phone second-hand or don't have service on it, you will have to find a reputable unlock service online
2.2 for sprint customers, your account HAS to be at least 6 months old before they will give you the UICC(SIM unlock) code
2.3 for boost customers, your account HAS to be at least a year before they will give you the UICC(SIM unlock) code
3. once you have the SIM unlock code, pull battery from phone, remove the original SIM, put your services respective SIM in (i.e. originally a cricket phone now running a T-Mobile SIM), put in battery, boot phone, and enter the unlock code where it asks.
4. once your back into device, you'll notice you will have no data.
4.1 what needs to be done is to program the APN (google will be your best friend here - for example sprint lte apn settings, or T-Mobile lte apn settings).
5. now that you have the APN settings, you can program them into the phone.
5.1 APNs can be found in the device by going to settings, then mobile data, clicking on access point names. in there in the upper right hand corner should be 3 dots that are verticle. click on that and then on new APN.
5.2 add the respective settings, click save and then make sure it has a green dot next to it.
6. sit back and enjoy the fruits of your labor
APNs for this device can only be written once the phone has been UNLOCKED and the original (cricket) service providers SIM is NOT inserted, and your using another service Provider ( sprint, T-Mobile, etc.) SIM.
UNLOCKING BOOTLOADER
1. for the drivers, use the ones contained here in the HTCDrivers.zip and extract them to the desktop
1. extract and use the file contained in adb.zip to flash unlock token
2. follow this tutorial and choose all other supported devicess when it asks about device.
INSTALLING TWRP AND KERNEL
in the adb file you should notice a file called recovery.img. that is TWRP recovery for the device
there is also a file called boot.img. this will allow read/write permissions at the System level once root is obtained
if you have either the sprint, boost or another service provider's variety of this phone, try flashing their respective kernel after you install the ROM or before you root (no guarantees that flashing the respective kernel will work. as I have the cricket variety of this phone, I am only developing for that one)
1. from home screen, go to settings and scroll down to power and then scroll all the to the bottom of that and uncheck "fast boot"
2. shut down phone completely
3. go back into fastboot (vol down + power)
4. Select fastboot from the menu list and press the power button.
5. open command prompt and use the CD command to get it to the root of the adb folder (CD C:/users/sky/desktop/adb).
6. plug in device and wait for it to say fastboot USB
7. type in command prompt "fastboot flash recovery recovery.img' (should complete within 4 seconds)
8. in the same command window type "fastboot flash boot boot.img" (should complete within 4 seconds)
8.1 step 8 can be skipped if your just flashing *NonSense1.04*.zip
9. pull battery once that is completed and put it back in.
10. power device on (skip this step if rooting)
OBTAINING ROOT (can be skipped if installing NonSense1.04 as it's already rooted)
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the supersu update package.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load
INSTALLING NonSense 1.04
1. re-enter fastboot mode and choose recovery. press power to select it
2. once in recovery select install and go to external SD and select the NonSense1.04.zip.
3. once selected, you should see a slider on the bottom of the screen that says swipe to confirm. do so
3.1 beware, it may take a bit to install. just be patient, it's working.
4. once package is installed you should see a button that says reboot device. do so
5. wait for it to fully load. be forewarned, it may take about 15 minutes to load
CHANGES
CRI versions
1. DEODEXed the ROM
2. added external SD support into the ROM
3. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
4. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
5. added more stable kernel to flash file.
6. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, and Viper4android (DSP/equalizer)
6.1 all apps that have been listed in 6 can be uninstalled without the need for root
7. root and SU have been added and are up to date in this rom as of 11:45PM MST on 3/1/215
8. added apns-conf.xml from CyanogenMod
9. got native APP2sd support thanks to pattyboi's kernel
B-S versions
1. mostly DEODEXed the ROM
2. fixed FC on clock app (switched clock/alarm from stock worldclock.apk to AOSP clock)
3. changed bootanimation.zip, boot sound, and stock ringtones and sounds.
4. added more stable kernel to flash file.
5. added Pandora (no-ads vers. 5.5), SpiritUL (FM radio support), Facebook, RootBrowser, Adobe reader, Adobe flash player, Wifi Tether, and Viper4android (DSP/equalizer)
5.1 all apps that have been listed in 5 can be uninstalled without the need for root
6. root and SU has been added
*1.04-lean
list of removed apps
1. Dropbox (can be found in playstore)
2. Google plus (can be found in playstore)
3. Hangouts (can be found in playstore)
4. HTC Dot View(can be found in playstore)
5. keyboard language packs for Arabic, Chinese, English UK, French, German, Greek, Italian, Portuguese, Russian, and Spanish (not in play store) if needed, flash language.zip found here
6. VPN dialogs (not in play store) if needed, flash missing.zip found here
7. HTC Zoe (can be found in playstore)
BUGS
CRI versions
1.USB internet pass-through not working
2.WiFi direct (miracast) not working
3. want to get rid of annoying volume too loud warning
B-S versions
1. native hotspot says internet when connected to win 7 machine, but will not allow it to go through. Have included wifi tether as a workaround until the issue can be resolved
THANKS
CRI versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing a more stable kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, CraviingCritic for providing the original ROM in which this wouldn't be possible
B-S versions
I thank wolfaas12345 for his awesome tutorial on bootloader unlocking, pattyboi for providing the current kernel, and chainfire for providing a great solution to provide the SU binary and app for rooted devices. and of course, LarryBoyG for providing the original ROM in which this wouldn't be possible
please feel free to let me know if there's any issues with this release and i will fix them as they are found for now as this device is the one i primarily use as of right now.
I will also be keeping the links updated for as long as I own the device (being that my HTC Desire 510(Cricket) is network unlocked, that may be a long time - or until I get a better device).
UPDATES
for those of you who have downloaded the ROM since first release, I will include an CRI_NSupdate.zip or B-S_NSupdate.zip file found here. it will include the changes I have made to the rom since it's initial upload.
the file by the name of NSupdate.szip will include update that pertain to both the CRI and B-S ROMS
to install the updates, just put the update file onto the root of the SD card, reboot into recovery, choose install, pick the update file, swipe the blue button on the bottom, reboot and enjoy.
EDITING THE BOOTUP
location of files mentioned is in /system/customize/resource
to change boot animation
1. find your favorite boot animation
2. rename it to AIO_bootup.zip
3. copy/move and overwrite the original with a root explorer to /system/customize/resource
to change the boot sound
1. find a sound file you like and want to hear every time the phone boots (can be changed at any time)
2. convert it to wav (the file has to be wav in order for the phone to recognize it)
3. rename it to CRICKET_LOGO_24bit28k_STEREO.wav
4. copy/move and overwrite the original with a root explorer to /system/customize/resource
reboot and enjoy...
THINGS NOTICED WHILE CREATING ROMs
1. both (cricket and boost/sprint) phones are exactly the same except for the boost/sprint ones contain a CDMA chipset.
1.1 the only things I had to change from the cricket rom to the boost rom was apns.xml in framework-res, apns-conf.xml, and the preferred network type in build.prop.
2. all kernels work for both (US) versions
3. the same recovery is used on both (US based) devices
so essentially, if we develop for the boost/sprint version of the device, change a few things, it will be ready to roll for the cricket version as well
TO FIX NATIVE TETHER ON B-S VERSIONS
1. Install Script Manager – SManager app from the Play Store.
2. Open the app and grant it root access when prompted.
3. Now, navigate to /system/etc/init.d and tap “tether” script.
4. Click on SU and Boot (Android skull and gear icons, respectively)
5. Click on Run and Save options.
The issue should be fixed now. Reboot and enjoy!
thanks goes to qwerty6532 and LarryBoyG for the fix. now to add that permanently to the ROMs and then they'll be absolutely stable enough for me to be happy and start working on CM11
CM11
I will be building CM11 for the device for both the cricket and boost models. look for the info here as I update it a I need
****edit**** ok so I figured out some of the issue with CM11 not wanting to install apps. I got the internal memory pulling the 1.1 gbs but now I need to symlink the external memory where it goes.
****edit**** so I have figured out what needs to be done...... the kernel for CM11 needs to be built from the ground, up (or one needs to be built that is compatible with it). i'll upload the current one that fixes the memory error (look in downloads).
reserved
so as i have not been actively developing on the phone i will no longer supply updates. all flash files are up to date as of 8 months ago and should be working with out an issue.
again, reserved
same to you...
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Burtrum57 said:
This would have to be one of the most comprehensive tutorials I have read. 10 out of 10 and kudos. Pity I have a 64 bit device and can't use most of it lol.
Click to expand...
Click to collapse
if I had a 64-bit version for this device, I would have it out as soon as I could. and thanks
Great job. Off and running now
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
CSP III said:
Question to you Schizoidd......If I install the new 1.04lean over the previous build, do I still need to flash that update or is is already included in 1.04lean. I already falshed that some time ago when you first put it out, so I'm just not sure if its needed again or not. Thanks bro.
Click to expand...
Click to collapse
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
qwerty6532 said:
I'm not sure how to add the tether fix to the ROM. Not really a developer more of a tester.. Wish I could get into developing don't really know where to start lol.
If you need any help testing or working on CM11 for Boost shoot me a PM I'd be glad to help
Sent from my 0PCV1 using XDA Free mobile app
Click to expand...
Click to collapse
Well it's added to it. It just needs to be activated for now until I can figure out how to add it to automatically start from the first run of the Sprint/boost ROM
schizoidd said:
When you flash the new one, wipe the system partition and then use an explorer to remove v4a from the user apps. Which is located in /data/apps and reboot
Click to expand...
Click to collapse
Sorry, not following "wipe the system partition" ???
CSP III said:
Sorry, not following "wipe the system partition" ???
Click to expand...
Click to collapse
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
schizoidd said:
if you in recovery, go to wipe and then advance wipe and check system. wipe it like u would as if ur doing a factory reset
Click to expand...
Click to collapse
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
CSP III said:
Yeah, I figured as much. Should have been clearer with my ? Is that before or after I flash the new lean. I though if I did it after, that it would set me back to square one. As in having to start fresh setting everything up again, which I really dont want to have to do. Apologies for my unclearness.
Click to expand...
Click to collapse
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
schizoidd said:
it'll leave ur data alone, just delete the OS. do not touch internal memory, davlik, data, or cache and ur stuff will be safe. I have done it and my stuff is fine
Click to expand...
Click to collapse
Right on buddy. I'll take you at your word on it. I've never had to do that before so it naturally made me a little nervous. Not that I couldnt have just restored a backup, but still . Many thanks.
Problems
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
schizoidd said:
I
for those of you that build the kernels, do you think u can build one that is AOSP and compatible with the device for android 4.4.4?
Click to expand...
Click to collapse
we cant really do a "aosp" kernel because of htc's modifications to the board and pins,and they have their own dtb issues...im 99% sure mine works with android 4.4.x because of larry using it in gpe,just repack the ramdisk the zimage and it should be okay
Bobby060 said:
System UI force closes and power button doesn't turn the screen back on when I flash the latest cricket version.
Click to expand...
Click to collapse
If you're going from bone stock to this, you need to do a factory data reset. Just make ssure you back up your data and use nandroid manager to pull it data back into the new ROM
Hi. When I changed in settings network mode to 2G only, signal icon started to flicker. After reboot I have no signal at all (it is impossible to call, send/receive SMS, use data connection etc.). In info (*#*#4636#*#*) preferred mode is set to "WCDMA preferred" and I cannot change it - I can chose another value from list but changes are not saved.
In settings phone says that none of SIM cards are inserted - but I can now access SIM 1 settings. However, everything is blocked and beneath the network type there is a description: "Invalid Network Mode (-1). Ignore.".
It happend when I was on latest official CM 13.0 nightly but this is probably not ROM's fault. Problem didn't disappear after clean flash, after restore or even after flashing whole set of images with official MiFlash tool.
After some research I found that setting ro.telephony.default_network from 22,22 to 10,10 should work, as 10 is for "LTE/GSM auto" when 22 is incorrect value. Separated by comma for two SIM slots. Ok, so I tried to edit build.prop with some apps without luck - access denied (rooted). I tried to mount system rw from Root explorer - nothing happens, still ro. From ADB - no, "dev/block/bootdevice/by-name/system is read-only". I even tried to change SELinux to permissive but still nothing
Every idea is welcome, I just need to get my phone to work as a phone again
TWRP 3.0.2 and systemless supersu 2.79
You must unlock bootloader first
From bootloader menu
*- To permanently install
fastboot flash recovery (TWRP files name)
*- Running TWRP without installing
Fastboot boot (twrp files name)
download
TWRP 3.0.2 android M
TWRP 3.0.2 Android N (Android wear 2.0)
systemless Wear SU 2.79 from
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
To CHANGE (ADDING or EDITING) APN
edit or add apn on two files (APN-Name and value MUST MATCH between these two files)
The watch select and display APN selection based on MCC and MNC value that stored under the SIM card
(you can see the sim card value under telephony.db under siminfo data)
*- apns-conf.xml
/system/etc/apns-conf.xml
*- telephony.db
/data/data/com.android.providers.telephony/databases/telephony.db
You can push and pull these files from recovery menu main screen
1- Boot into TWRP
2- Mount System as RW (from mount menu)
3- connect the watch into computer and install ADB drivers.
4- Than run adb pull to get the files
Edit the files (by adding APN or edit existing carriers APN)
apns-conf.xml with any text or xml editor
telephony.db (under data and carriers) with Db browser for sqllite or any sql editor
APN name and data value on both files MUST BE THE SAME/MATCH otherwise the watch wont load the selection
5- ADB push to push the files back to the watch
6. Run shell command to change permission, ownership and group
apns-conf.xml - chmod 644 (rw r r), chown and chgrp root
telephony.db - chmod 660, chown and chgrp radio
Wanting to try this, but it isn't letting me mount /system. TWRP log says "Failed to mount '/system' (No such device)". The "Mount system RO" checkbox checks, but doesn't actually mount RO either.
I also looked for the telephony.db and it didn't exist at /data/data/com.android.providers.telephony/databases/telephony.db. The "databases" folder doesn't exist. Couldn't check for the one in /system
Running wear 2.0, so I DL'd the correct TWRP. I did boot-only, not flash.
Any ideas?
Concur.
Rayfen Windspear said:
Wanting to try this, but it isn't letting me mount /system. TWRP log says "Failed to mount '/system' (No such device)". The "Mount system RO" checkbox checks, but doesn't actually mount RO either.
I also looked for the telephony.db and it didn't exist at /data/data/com.android.providers.telephony/databases/telephony.db. The "databases" folder doesn't exist. Couldn't check for the one in /system
Running wear 2.0, so I DL'd the correct TWRP. I did boot-only, not flash.
Any ideas?
Click to expand...
Click to collapse
I have the same problem with TWRP and System RO. I did it in the same manner for booting from bootloader, because the flashing of recovery does not work correctly. I flash the TWRP using fastboot flash recovery, but every time I attempt to boot into recovery I get the same android icon with a red triangle over the top and an exclamation inside. I did not check the apn, because if I cannot go into recovery or flash SU I know that would be useless to even try. Same here device name nemo from bootloader screen using wear 2.0 (Android 7.1.1). Unlocked using fastboot oem unlock.
My Nexus 5 is rooted with custom Nougat ROM and it does NOT have the .db in the data directory. Given that they use a lot of the same AOSP code, it's probably safe to say that Wear 2.0 (nougat 7.1.1) doesn't need this here either. My conclusion then, is that they have consolidated these settings to the XML in the /system directory, which we cannot mount.
In the thread linked for the systemless su, it mentions that system is read only as it is squashfs. I can only assume that this applies to /system/etc/apns-conf.xml, so I'm not sure how OP was able to push the modified file back to /system in the first place without taking this into account.
Got it working with my FreedomPop SIM. Should work to add any APN. So I combined this with another guy's guide. There are two main differences.
First off, use twrp-3.1.1.0.img from this guy's thread. https://forum.xda-developers.com/lg-urbane-2/how-to/root-twrp-squashfs-3-1-1-lg-urbane-2nd-t3661569
Then it works to mount /system as READ ONLY, which allows you to use the systemless-su from this thread. WARNING: This may not modify the system, but it does modify and reflash another partition (I didn't catch which). I do not know if this will prevent your device from receiving OTAs afterward (It updates, see edit below). ALSO, because there isn't a SuperSU app, there is no management of what can use su privileges. Any app could discover root and do whatever without your knowledge. I plan to remove su from my watch when I get around to it now that my APN has been added. I will post how when I do.
EDIT: I just received an update through the Play Store that updated my AW version, build number, the works. Security patch August 1st. The APN I added persists after the update, though it showed the "no sim" icon until I went and manually enabled cell and selected the APN again.
After getting that done, follow these instructions for adding the APN starting from the header "Add the APN via the ADB shell". https://michaeltroger.github.io/blog/2017/08/12/add-apn-in-android-wear-2
Adding FreedomPop's data APN went as follows:
adb shell
su
content insert --uri content://telephony/carriers --bind name:s:"FreedomPop" --bind numeric:s:"310170" --bind type:s:"default,supl" --bind mcc:i:310 --bind mnc:i:170 --bind apn:s:"fp.com.attz"
If you happen to mess up, or have to add it with trial and error as I did, you can use the following two commands to fix things.
content query
content delete
Using the where clause as exampled in the above link.
NOTE: I just found out that as these changes are systemless, they DO NOT survive an unpair/reset.
Use this TWRP instead for Android wear 2
I modified from Android wear 2 stock recovery
TWRP 3.1.1
https://drive.google.com/open?id=0B4W0KuzRjVvGNkF1UnFkQkFBcU0
Systemless root
https://drive.google.com/open?id=0B4W0KuzRjVvGMzJka1dGRFM2dGc
Dont flash TWRP instead run fastboot boot (TWRP image name)
You wont be able to flash any OTA update with TWRP.
Your watch will keep rebooting to TWRP if you try to download and install any OTA.
Rayfen Windspear said:
Got it working with my FreedomPop SIM. Should work to add any APN. So I combined this with another guy's guide. There are two main differences.
First off, use twrp-3.1.1.0.img from this guy's thread. https://forum.xda-developers.com/lg-urbane-2/how-to/root-twrp-squashfs-3-1-1-lg-urbane-2nd-t3661569
Then it works to mount /system as READ ONLY, which allows you to use the systemless-su from this thread. WARNING: This may not modify the system, but it does modify and reflash another partition (I didn't catch which). I do not know if this will prevent your device from receiving OTAs afterward (It updates, see edit below). ALSO, because there isn't a SuperSU app, there is no management of what can use su privileges. Any app could discover root and do whatever without your knowledge. I plan to remove su from my watch when I get around to it now that my APN has been added. I will post how when I do.
EDIT: I just received an update through the Play Store that updated my AW version, build number, the works. Security patch August 1st. The APN I added persists after the update, though it showed the "no sim" icon until I went and manually enabled cell and selected the APN again.
After getting that done, follow these instructions for adding the APN starting from the header "Add the APN via the ADB shell". https://michaeltroger.github.io/blog/2017/08/12/add-apn-in-android-wear-2
Adding FreedomPop's data APN went as follows:
adb shell
su
content insert --uri content://telephony/carriers --bind name:s:"FreedomPop" --bind numeric:s:"310170" --bind type:s:"default,supl" --bind mcc:i:310 --bind mnc:i:170 --bind apn:s:"fp.com.attz"
If you happen to mess up, or have to add it with trial and error as I did, you can use the following two commands to fix things.
content query
content delete
Using the where clause as exampled in the above link.
NOTE: I just found out that as these changes are systemless, they DO NOT survive an unpair/reset.
Click to expand...
Click to collapse
Is Safetynet working after removing root? I presume you can still sideload updates or that there is a method to return to stock if SafetyNet is tripped?
sjavvaji said:
Is Safetynet working after removing root?
Click to expand...
Click to collapse
I never got around to forcefully disabling/removing it. Nor have I gotten around to redoing it after unpaid/reset wiped it all. How would I test that? I'll get it back on and working then remove root this time sometime this week and give it a go. I don't use Android pay, so I'm not sure how I would test it. Perhaps I could adb push one of the checker apps for phone and hope it works?
Rayfen Windspear said:
I never got around to forcefully disabling/removing it. Nor have I gotten around to redoing it after unpaid/reset wiped it all. How would I test that? I'll get it back on and working then remove root this time sometime this week and give it a go. I don't use Android pay, so I'm not sure how I would test it. Perhaps I could adb push one of the checker apps for phone and hope it works?
Click to expand...
Click to collapse
That would be one way to do it. I have my watch coming in tomorrow and a Freedompop sim on the way. I would prefer Android Pay working over data but having both working is optimal.
sjavvaji said:
That would be one way to do it. I have my watch coming in tomorrow and a Freedompop sim on the way. I would prefer Android Pay working over data but having both working is optimal.
Click to expand...
Click to collapse
Just getting around to tinkering today. Did a bit of research and found that installing the systemless SU modifies the kernel. I'm going to dig a little deeper and hopefully come up with a zip to flash that will completely undo everything that is done by the SU zip (if there isn't one already) to make sure that safetynet not only passes, but that the kernel is stock and secure too. The recent update they pushed for Aug security patch possibly updated the kernel too, yet the APN survived, so once set, APNs definitely live in the userdata and should be fine.
Rayfen Windspear said:
Just getting around to tinkering today. Did a bit of research and found that installing the systemless SU modifies the kernel. I'm going to dig a little deeper and hopefully come up with a zip to flash that will completely undo everything that is done by the SU zip (if there isn't one already) to make sure that safetynet not only passes, but that the kernel is stock and secure too. The recent update they pushed for Aug security patch possibly updated the kernel too, yet the APN survived, so once set, APNs definitely live in the userdata and should be fine.
Click to expand...
Click to collapse
Let me know how it goes! I would honestly just like to get the APN working and return to stock. So assuming it works, the process would go, unlock bootloader, run TWRP w/o install, install systemless SU, edit APN, run TWRP w/o install, uninstall systemless SU, and bootloader relock. Am I missing anything?
sjavvaji said:
Let me know how it goes! I would honestly just like to get the APN working and return to stock. So assuming it works, the process would go, unlock bootloader, run TWRP w/o install, install systemless SU, edit APN, run TWRP w/o install, uninstall systemless SU, and bootloader relock. Am I missing anything?
Click to expand...
Click to collapse
Ooooh... does SafetyNet check for an unlocked bootloader? Does relocking it force a data wipe? I can't remember, because once I unlock, I've never gone back
Rayfen Windspear said:
Ooooh... does SafetyNet check for an unlocked bootloader? Does relocking it force a data wipe? I can't remember, because once I unlock, I've never gone back
Click to expand...
Click to collapse
Yeah. I forgot it required a data wipe. That might be an issue lol.
So is there a way to install Magisk? Or any way to bypass the SafetyNet check and a way to reverse the systemless SU check?
Edit:
I did some more research and it seems like we might be able to install Magisk in place if the systemless root uses SuperSU. Other LG watches in the past and android wear devices in general have been rooted using Magisk in place of SuperSU and it seems to pass safetynet.
hoodred said:
TWRP 3.0.2 and systemless supersu 2.79
You must unlock bootloader first
From bootloader menu
*- To permanently install
fastboot flash recovery (TWRP files name)
*- Running TWRP without installing
Fastboot boot (twrp files name)
download
TWRP 3.0.2 android M
TWRP 3.0.2 Android N (Android wear 2.0)
systemless Wear SU 2.79 from
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
To CHANGE (ADDING or EDITING) APN
edit or add apn on two files (APN-Name and value MUST MATCH between these two files)
The watch select and display APN selection based on MCC and MNC value that stored under the SIM card
(you can see the sim card value under telephony.db under siminfo data)
*- apns-conf.xml
/system/etc/apns-conf.xml
*- telephony.db
/data/data/com.android.providers.telephony/databases/telephony.db
You can push and pull these files from recovery menu main screen
1- Boot into TWRP
2- Mount System as RW (from mount menu)
3- connect the watch into computer and install ADB drivers.
4- Than run adb pull to get the files
Edit the files (by adding APN or edit existing carriers APN)
apns-conf.xml with any text or xml editor
telephony.db (under data and carriers) with Db browser for sqllite or any sql editor
APN name and data value on both files MUST BE THE SAME/MATCH otherwise the watch wont load the selection
5- ADB push to push the files back to the watch
6. Run shell command to change permission, ownership and group
apns-conf.xml - chmod 644 (rw r r), chown and chgrp root
telephony.db - chmod 660, chown and chgrp radio
Click to expand...
Click to collapse
Is there a way to flash back to stock AW 1.5?
Sent from my SM-G965U using Tapatalk
Tether used to work fine on Nougat, then in Oreo and Pie, google baked-in the inability to add "dun" to an apn whether existing or new, resulting in an error message of "carrier does not allow apns of type dun." This resulted in a really slow, erratic tether function in the ROMs I tried.
Anyone found a ROM, or kernel, or know of a dev that is actively adding the same functionality as was present on Nougat--that is, tethering worked properly out of the box, or adding dun to the apn makes it work properly? I know for a fact that SOME Oreo and Pie ROMs now allow one to add the dun parameter to the apn, but it still didn't make tethering fast and stable like before.
lineageos
I'm a little surprised no one else has weighed in on this--it is as if @namanjr and I the only ones who have an interest in tethering.
namanjr said:
lineageos
Click to expand...
Click to collapse
Incorrect.
Neither LOS 15 (Oreo) nor LOS 16 (Pie) tether as well as Nougat, and neither allow the dun parameter to be written into the APN. Their tether speed is less than 1/10 of the speed with Nougat.
Furthermore, using either one of them will probably result in the downgrade "Encryption Unsuccessful" error in attempting to re-flash Nougat, meaning that the only way to downgrade is to format interior storage.
pbergonzi said:
Incorrect.
Neither LOS 15 (Oreo) nor LOS 16 (Pie) tether as well as Nougat, and neither allow the dun parameter to be written into the APN. Their tether speed is less than 1/10 of the speed with Nougat.
Furthermore, using either one of them will probably result in the downgrade "Encryption Unsuccessful" error in attempting to re-flash Nougat, meaning that the only way to downgrade is to format interior storage.
Click to expand...
Click to collapse
You have to use the CLI tools or edit the xml with all the APN.
Try "settings put global tether_dun_required 0" in adb shell or terminal emulator.
Something like "settings put global tether_dun_apn APNHERE" would manually add a APN+DUN if you know the input format of the command. Just turn data off and on after and test hotspot.
namanjr said:
You have to use the CLI tools or edit the xml with all the APN.
Try "settings put global tether_dun_required 0" in adb shell or terminal emulator.
Something like "settings put global tether_dun_apn APNHERE" would manually add a APN+DUN if you know the input format of the command. Just turn data off and on after and test hotspot.
Click to expand...
Click to collapse
I've tried "put global..." in one or two other roms, with no success.
One of the other roms would also allow editing the APN, but even with the dun parameter, it didn't perform properly.
Did you do this to your own rom and see an effective before and after?
pbergonzi said:
I've tried "put global..." in one or two other roms, with no success.
One of the other roms would also allow editing the APN, but even with the dun parameter, it didn't perform properly.
Did you do this to your own rom and see an effective before and after?
Click to expand...
Click to collapse
I edited /system/etc/apns-conf.xml manually. Copy and paste your existing APN and change the name, then edit it to allow tethering. You will loose changes when updating unless you make a backup script for it, a magisk module, or get you or a dev to add it to a rom.
namanjr said:
I edited /system/etc/apns-conf.xml manually. Copy and paste your existing APN and change the name, then edit it to allow tethering. You will loose changes when updating unless you make a backup script for it, a magisk module, or get you or a dev to add it to a rom.
Click to expand...
Click to collapse
Thanks. If I decide to upgrade to pie again, I will do this.
Dirty Unicorns V13 (Pie)
ZVNexus said:
Dirty Unicorns V13 (Pie)
Click to expand...
Click to collapse
Thank you. Can you tell me or show a screenshot of your tether download speed with (and/or without) the DU rom or with the dun parameter in/absent from the apn, illustrating the difference in quality?
I am lax to immediately install another P rom knowing that if I need to come back to N, there is extra work/risk involved.
Hey, I've also been struggling in this boat for a few months now. Went from a nexus 6p with Los 14.1 to the oneplus 3t. Only rom available at the time was 15.1 , which I remember kind of sucked when it first came out the gate on the nexus 6p, so I was hesitant to use it. Quickly ran into this issue where the tethering speed was dramatically terrible. For months I've just assumed it was the oneplus 3t's fault. Maybe the radio is weaker, or my carrier doesn't approve of this Chinese import versus the other...
I bounced between Stock, Ice Cold, and Los trying to find the best settings for the best result. With my carrier (tmo) the trick was to make a new apn and set it up to use a different address, meant for devices without lte support. "epc.tmobile.com" . This immediately made everything fast again, however it sort of pipelines any tethering activity. So like it would have the good expected transfer rate with one thing, but if you tried to load anything else, that thing would hang until the first thing finished transferring.
I'm glad I finally caught wind of this question/thread. It's relieving to know that it's just because google f***ed with something in oreo and pie, and not that Los suddenly updated into inconvenience. I'm going to try Dirty Unicorns 13 as ZVNexus suggested, and will report back to you with results. Also if any of you can help better articulate this 'global dun 0 apns-conf.xml trick' for me that'd be great and I'll gladly try that out and give results. I flashed magisk and navigated to the apns-conf.xml file just to be suddenly reminded I have no idea what on earth I'm looking at.
** Dirty Unicorns 13 Result
A big maybe? Tmobile out of the box shoots down tethering speed to ~70 kb/s . I usually use the TTL trick to work around this, but that requires I set/use any APN protocol to IPv4. For whatever purposes, the version I tried (du_oneplus3-v13.0-20190109-0432-RC) doesn't allow you to edit the initial APN settings, however I can see that it has "dun" listed in the types. Inconvenient, but I figured whatever I'll just make my own BUT NO. It won't let you save a new APN with dun anywhere in the types. So in the end I can't give any solid result, sorry. If it means anything the upload speed was good, so this could be an issue exclusive to my carrier.