For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
For the powersaver mode, try this from a computer with working ADB
Code:
Code:
adb shell "settings list secure | grep power"
If it returns something that looks like this
Code:
Code:
hide_ui_user_powersaver=1
Then try
Code:
Code:
adb shell "settings put secure hide_ui_user_powersaver 0"
This does not require root if done from a computer. It will require root if done from a terminal on the device. This is what works on an M9 running Marshmallow. It may or may not work on the 10. You can also try
Code:
Code:
adb shell "settings list secure"
To get a list of all the settings.
Click to expand...
Click to collapse
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Must have missed that one. I went through that post a couple days ago. Guess this will work for those that can't or don't know how to setup and use adb
Sent from my HTC6545LVW using Tapatalk
Evocm7 said:
For those that don't know, here's how to enable Power saver mode on the vzw model.
You need:
Root
Root browser/ root explorer/ etc.
Navigate to system/ customize/ CID/ Default.xml. scroll about 1/3 of the way down until you find "def_hide_ui_powersaver" >1</item<item> and change value to "0".
Reboot device, then go to home screen, long press to add widget, select shortcuts, then down to power saver. This will put a shortcut to the power saver menu that is hidden from us.
Note that you must mount R/W or the edit will not work. This will not enable the quick setting or for it to show up in the regular power options menu but this will work for now.
Good luck
Thanks to aer0zer0 for pointing me in the right direction.
Click to expand...
Click to collapse
If it is like the M9 on marshmallow, after making that edit, if you factory reset it, the menu option should appear in the standard menu. its alot easier to either put it in as a shortcut, or use xtended settings, and add it to the power menu, or gravity box, and add custom quicksetting tiles (1 of which being battery, it will also show battery temp and mAh remaining).
Once we get a deodexed based, or even a stock odex flash, we can make those edits prior to flash and it will be in the menu as normal
edit, i also believe if you edit the next line (120) def_hide_ui_user_powersaver and set it to 0, this is what will enable the menu on factory reset
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
hgoldner said:
Note that this survives reboot and/or power recycle. Using the adb approach for unrooted handsets, got it working on both my own and a test device.
UPDATE: So far as I can tell, the latest OTA to 1.19.605.22 breaks this ability.
Click to expand...
Click to collapse
Can confirm that the latest update definitely does break this ability (no root). =(
im_high_tech said:
Can confirm that the latest update definitely does break this ability (no root). =(
Click to expand...
Click to collapse
I think the only way to do this is to write to \system; so for those who don't want to flash a custom ROM or write to \system, it's out of reach for now.
And especially galling because the 10's on all the other carriers have the feature. Verizon kills it.
@andybones has it in the stock deodex base, but if you are working off of the odex base, the easiest way is probably gravitybox, and using the QS tile to toggle it (still requires root). Just make sure you are using systemless xposed to not touch the system partition as @hgoldner pointed out, if you need it.
by stock base, i mean OTA to 1.19.605.22
Battery Saver Mode Settings
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
klarthur said:
I can verify that this can also be enabled on unrooted devices as well. Credit goes to user l7777 in this post: http://forum.xda-developers.com/verizon-htc-10/help/verizon-version-missing-options-t3376634.
I had to restart my phone after making the change in ADB. The only thing that doesn't seem to work correctly is when I click on the Battery Saver Mode to edit the settings, I will receive an error message. The Battery Saver Mode will turn on and off with no issue.
Click to expand...
Click to collapse
This modification can be done using Magisk, without editing /system. You need to cache-mount the edited default.xml using Magisk, and Magisk mount the patched SystemUI.apk and HtcPowerManager.apk from @andybones' deodexed stock ROM. HUUUGE thanks to @Captain_Throwback for helping me figure this out and tolerating all-too-frequent stupid mistakes getting to this point, and, of course, none of this would be possible without the amazing efforts of @topjohnwu in creating Magisk in the first place.
I will post detailed instructions if someone is interested.
jackebuehner said:
You can change the power saver mode settings if you install the apk from apk mirror http://www.apkmirror.com/apk/htc-corporation/power/
Click to expand...
Click to collapse
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Chewieez said:
I just tried installing this on my stock, non-rooted Verizon HTC 10 and it didn't give me any new options for power saver mode. I installed the most recent version from apk mirror and then rebooted. Everything looks the same. I'm on version 3.057.92923
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
jackebuehner said:
You have to follow the steps in post #2 before installing the APK does anything. The APK just makes it so that power saver mode settings doesn't crash.
Click to expand...
Click to collapse
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
mrbacks said:
I believe he is referencing the fact that not all of the available settings are shown. From screenshots of the book on the HTC one there should be settings for what power saver does.
CPU
Display
Vibration
Data connection
Useful settings. I would like to be able to turn down the processor without turning off data.
Click to expand...
Click to collapse
You'll likely need a custom kernel for that, which means root access and either unlocked bootloader or S-OFF. Once you're in that boat, you'll need Magisk to clear Safety.net. It's not otherwise doable on pure unrooted stock. FWIW, if you are rooted, you can use @flar2's ElementalX kernel which is quite good, especially when used with the helper app allowing you to tweak all settings.
Related
avlock[10] is a (the first?) real, *system-level* lock screen replacement for Android (CM 5.0.6).
it replaces the standard "connect the dots" behavior with pin-like mechanism. patterns can be arbitrarily large, and nodes can be repeated. also, there are no numbers -- just circles. definitely not for everyone, but i think some people may like it.
here's how it works:
http://files.clangen.org/avlock/avlock.m4v
if you want to try it you must have CM 5.0.6 installed, then:
1. reboot to bootloader
2. nandroid backup <-- do it. seriously. just in case.
3. flash avlock[x].zip
4. reboot
5. if you don't have a lock pattern already, set one: Home > Menu > Settings > Location and Security > Set Unlock Pattern
faq:
q: what happens if something goes really wrong and i can't log in?
a: i've been tweaking this mod for a long time and you shouldn't have any problems. BUT IF YOU DO:
* restore from nandroid backup made in step 2 above
OR
* if you know how to use adb, just delete the file pattern file and reboot:
adb remount
adb shell rm /data/system/gesture.key
adb shell reboot
q: what files are replaced by the patch?
a: framework.jar, framework-res.apk, android.policy.jar, Settings.apk
q: why not just distribute this as a simple .apk file?
a: this is a system-level mod because it replaces system-level components. it cannot be distributed as an .apk.
changelog:
avlock[8]:
* initial release
avlock[9]:
* added tactile feedback
* reduced login delay
avlock[10]:
* disabling "Use visible pattern" works now
* better integration with system and Settings.
* re-added drag lock option.
avlock[11]:
* added the ability to specify a pattern timeout
use at your own risk. i am not responsible for any damages caused by this software. MAKE A NANDROID BACKUP FIRST!
caution: if you update your rom, install a theme, or flash another mod that replaces framework.jar, framework-res.apk, or android.framework.jar, you may not be able to log in upon reboot (or even spin into a boot loop). either (1) make sure you disable your lock screen before flashing or (2) rm gesture.key as described in the faq!
download:
avlock[11]: http://droidbasement.com/db-blog/?p=202 (thanks, pershoot)
sources:
http://github.com/avatar5d
wow, nifty and works well enough
It'd be really nice if it was faster, there is close to a 2 second lag between entering and unlocking
Cool Thanks
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Good work.
Thanks
imfloflo said:
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Good work.
Thanks
Click to expand...
Click to collapse
You could always unzip the zip and push the files manually
adb shell stop
adb push these files to their respective places framework.jar, android.policy.jar, Settings.apk
adb shell start
If you forget the pattern, you can get it emailed to you right?
Looks awesome in the video, nice idea, better executed!
NICE MOD!
Nice work!!!
prettyboy85712 said:
Nice work!!!
Click to expand...
Click to collapse
+1 Nice ...
Good Job !
This looks awesome! Nice work
@ _avatar
Any chance to make this work with Enom's ROM ?
Nice work!
imfloflo said:
Nice , i agree with the faster unlock and if it's possible to install it via apk or another methode than flashing in recovery mode.
Click to expand...
Click to collapse
Unfortunately, because this is a system-level mod it cannot be installed as a simple .apk.
bobtentpeg said:
It'd be really nice if it was faster, there is close to a 2 second lag between entering and unlocking
Click to expand...
Click to collapse
The delay is there on purpose. Once you stop touching the circles for 2 seconds, the combination is verified. Without this delay, there would need to be some sort of "OK" button, which I think is undesirable. However, I'll look into making the delay shorter (1 second?) for future builds. The value needs to be long enough so people can still enter their combination relatively slowly, but fast enough so it's not annoying.
pvillasuso said:
Any chance to make this work with Enom's ROM ?
Click to expand...
Click to collapse
Possibly. Is Enom's source available, and easily buildable like Cyanogen's? I'm not super familiar with his project.
This is hot, installing now. My main complaint with the stock lock pattern was the inability to re-use points. just gotta set a good lock pattern and see how this works.
Thanks.
Wow.. this is pretty damned cool! Good job.
One thing, tactile feedback is not working with this, any way to restore that?
daveid said:
One thing, tactile feedback is not working with this, any way to restore that?
Click to expand...
Click to collapse
It's on my TODO list
EDIT: added to avlk[9] build. see original post!
Can you make a them of some sort and replace the dots with numbers?
Can it run on 1.8.1 rom
Re: [MOD] avlk[9], a real, system-level lock screen replacement
anyway to incorporate trackball wake-up in this for us desire port guys ;-)
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
_avatar said:
Possibly. Is Enom's source available, and easily buildable like Cyanogen's? I'm not super familiar with his project.
Click to expand...
Click to collapse
http://android.git.kernel.org/
You'll want to ask him which actual tag he's building for current versions. Also, since I'm not up on framework patching, it might be more complicated if you don't want to break the trackball-wake and/or notification features. Best to contact him @enomther or for someone to raise the suggestion in his thread.
Is there a mod that allows me disable the Installer from automatically coming up when connecting to a pc through USB?
Tyetiger said:
Is there a mod that allows me disable the Installer from automatically coming up when connecting to a pc through USB?
Click to expand...
Click to collapse
I was able to by deleting autostart.iso file from \system\etc
I use Mac and it no longer mounts the mobile Verizon app. I assume its the same for windows.
Itsmyphoneyo said:
I was able to by deleting autostart.iso file from \system\etc
I use Mac and it no longer mounts the mobile Verizon app. I assume its the same for windows.
Click to expand...
Click to collapse
Ive been trying for days! Haven't been able to find that folder or file. Unfortunately I have a PC
Tyetiger said:
Ive been trying for days! Haven't been able to find that folder or file. Unfortunately I have a PC
Click to expand...
Click to collapse
You need root to do this... I probly should have mentioned that. Sorry. Getting root is easy now, there are a could threads on how to root with very easy step by step instructions. After you gain root, purchase root explorer from PlayStore (yes, you have to spend a couple $ but its worth it) and use that app to navigate and delete the file. You will likely use the app again, unless you switch to an iPhone. So it's worth the little bit of money.
I see autorun.iso, I assume that's what you're referring?
Sent from my SCH-I545 using xda app-developers app
Itsmyphoneyo said:
You need root to do this... I probly should have mentioned that. Sorry. Getting root is easy now, there are a could threads on how to root with very easy step by step instructions. After you gain root, purchase root explorer from PlayStore (yes, you have to spend a couple $ but its worth it) and use that app to navigate and delete the file. You will likely use the app again, unless you switch to an iPhone. So it's worth the little bit of money.
Click to expand...
Click to collapse
Ok. I was able to download a root explorer and remove the autorun.iso. But I notice the phone still says "Installer is connected" and I still can't view the sdcard or drive on the phone unless I'm in Camara(PTP) mode.
Tyetiger said:
Ok. I was able to download a root explorer and remove the autorun.iso. But I notice the phone still says "Installer is connected" and I still can't view the sdcard or drive on the phone unless I'm in Camara(PTP) mode.
Click to expand...
Click to collapse
Check your usb debugging settings. you might need to either check that box or unchecked it. I can't help much more than that if you're using Windows, I'm a mac user. But that sounds like all you would need to do. Hope it helps.
Verizon installer
Okay here is a weird one (or maybe not). Started getting this when I first connected the S4 to PC via USB. Now when I connect my S3 I am getting the same popup. S3 is rooted never had this message.
I am thinking this is somehow embedded into the new Samsung USB drivers. When the phone is plugged in, some form of check reveals a VZW phone which triggers the installer????
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Gam3r 4 Life said:
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Click to expand...
Click to collapse
Bump, I'd like to know the same thing.
ecen92 said:
Bump, I'd like to know the same thing.
Click to expand...
Click to collapse
I'm getting connect/disconnect every 3 seconds.
Gam3r 4 Life said:
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Click to expand...
Click to collapse
Still trying to figure this one out........any ideas......anyone????
Zelmo88 said:
Still trying to figure this one out........any ideas......anyone????
Click to expand...
Click to collapse
Bump! Anyone find a cure for this yet?
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Chris000001 said:
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Click to expand...
Click to collapse
Tried this on Sophisticated 2.5 . It's a 4.3 rom I get this: error: device offlineerror: device offline even though Link Status is Device Connected. My autorun.iso file was in /system/etc I renamed it. Changing the dialer code *#0808# to MTP works until I reboot. Same thing with dialer code *#7284#. I edited a file in /efs/carrier/HiddenMenu "OFF" changed to "ON" all in capital letters This survives a reboot.
But MTP doesn't
desertopal said:
Tried this on Sophisticated 2.5 . It's a 4.3 rom I get this: error: device offlineerror: device offline even though Link Status is Device Connected. My autorun.iso file was in /system/etc I renamed it. Changing the dialer code *#0808# to MTP works until I reboot. Same thing with dialer code *#7284#. I edited a file in /efs/carrier/HiddenMenu "OFF" changed to "ON" all in capital letters This survives a reboot.
But MTP doesn't
Click to expand...
Click to collapse
I'm on MK2 rooted and I have the same problem with the setting not surviving a reboot. Anyone have any other ideas?
Removing the file should work, if it's giving you a delay then my guess is either your computer or the device is trying to find the file. Back on my s3 and dna rom I had only removed the file and vzw installer didn't show up
Sent from my SCH-I545 using XDA Premium 4 mobile app
CovXX said:
Removing the file should work, if it's giving you a delay then my guess is either your computer or the device is trying to find the file. Back on my s3 and dna rom I had only removed the file and vzw installer didn't show up
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Removing the file does not solve the problem, it still connects as installer for a while before connecting as media device. It's not a huge problem, just annoying! I'm curious if everyone has this problem, or if it's just a few of us??
Zelmo88 said:
Removing the file does not solve the problem, it still connects as installer for a while before connecting as media device. It's not a huge problem, just annoying! I'm curious if everyone has this problem, or if it's just a few of us??
Click to expand...
Click to collapse
I have the same issue. I've tried looking through/changing settings in build.prop, default.prop and init.usb.rc with no luck. I need to do a little more searching to better understand init.usb.rc as a lot of the settings are jibberish to me.
Chris000001 said:
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Click to expand...
Click to collapse
Running the Casual-gnote2 I get this: file/ Open Casual Script (go to location, click on the downloaded Casual-gnote2.jar) it opens and gives me this
Description for /home/wade/Downloads/CASUAL-GNOTE2-Hidden Menus.jar
File Not Found Error: /home/wade/Downloads/CASUAL-GNOTE2-Hidden Menus.jar.txt
Delete this debug line in MenuItemOpenScriptActionPerformed()
If I just open Casual-gnote2 and click DO IT I get this: error: device offlineerror: device offline
In both cases the Link Status = Device Connected
I am making this tutorial as I have had multiple versions of the LG LTE Leon and have used many firmware versions. I have created a stable method that has the least issues as I have had trouble with the latest firmware (MS34510f) disabling my root privileges. I have created a MEGA account specifically for all of the files necessary to complete this operation and have your device run smoothly. So, please follow my instructions exactly as stated and you should not have any issues. THIS PROCESS WILL REMOVE ALL DATA NOT SYNCED, DO READ BELOW NOTES IT IS VERY BENEFICIAL
Important Notes:
+This process will wipe all data that is not synced, it is important to ensure that no newer LG process are still on the device. Some might argue to leave data, to that I say good luck keeping your root and tethering without the device becoming suspiciously unstable.
+ I am not GUARANTEEING this will work on every model, but I have had an extremely high success rate with all Leon versions.
+ In this tutorial the process in which I remove Kingroot and replace it with SuperSu is for system stability. I find that most root functions I use seem to not work properly. (Wifi Tether Router and many others). So, I do recommend doing so.
+After the new OS is installed a MetroPCS splash screen will appear even if you do have T-Mobile. DO NOT BE ALARMED this firmware will not limit any functionality you had before, it will even help with tethering functionality.
Tutorial:
Let's Begin.
1. Download the link posted to obtain required files for this tutorial
Link: https://mega.nz/#F!PM4CQRqb!92kgIOnD0ZBY-8HVbtTwGQ
2. Open up LGFlashTool2014.exe
Begin by copying settings posted below, then click "normal flash"
3. Next click the "START" button
4. At this time, I recommend you verify all sync settings are to your liking and that all personal info needed is backed up
a. You have the option to throw all of your personal documents/pictures onto your SD card and removing it appropriately
(Go to: Settings - Storage - [scroll down to] Unmount SD card)
b. Next, navigate to Settings -Backup & reset [leave options default; both checked off] - Factory data reset - reset phone
c. Once reset it will most likely reboot, wipe, and then back to a OS. Now, you will Power Off entirely (make sure it is not plugged in so it will not go to charging mode)
d. Here is where we will hold down the Volume Up button with the phone unplugged from your PC. Then you must plug the USB into your phone.
e. A black screen with white text should post onto your screen, here we will continue to step 6
note: If this screen does not appear please power off and retry step d.
6. Next, follow the posted settings. Make sure to click the "Clear phone Software update Registry" button Then click "OK"
7. A new screen will arrive, and should begin the firmware download process. At this time it will take a few minute to load and should reboot to a fresh OS.
8. With the new OS in place, you can either follow the setup tutorial now or skip through for a later setup.
note: you can now insert your SD card
9. In the tools folder of the folder you downloaded copy the "mrw" folder to the Main Storage folder of your phone
10. Now copy the Kingroot apk to your downloads folder located on the main storage.
11. Go to Settings - About Phone - Software Info
At this time click the build number box a few times until it says you are a developer
12. Hit back until you are at the Setting menu, click on Developer options and check off "Stay Awake" and "Enable OEM Unlock" as well as "USB Debugging"
13. You may now run Kingroot, if it does not install root the first time it should flawlessly install the next.
14. After root is obtained, please go to your home screen and click the "Google Search" widget. Press Update Google Services and let it run. After that has been updated search for terminal emulator and install.
note: If the Play Store is acting fishy and force closing while typing in the search bar do not fret it will be fixed after reboot in further instruction
as an allternative use the jackpal.androidterm-1.0.70-71-minAPI4.apk provided in the "tools" folder
15. Open terminal and in a new window type: Su
16. Allow root usage and at this time type: sh /storage/emulated/0/mrw/root.sh
17. It will run with a few failed messages do not worry it should open SuperSu momentarily
18. Once SuperSu opens up allow it to update binaries using the "NORMAL" option but DO NOT REBOOT YET
19. At this time either download TWRP Manager from the play store or alternatively use the com.jmz.soft.twrpmanager-7.5.1.3-82-minAPI11.apk provided in the tools folder
20. Install and open TWRP Manager. Once opened click on device name and scroll until you see "LG Leon LTE (c50)"
a. Click on Recovery Version to Install and select "twrp-2.8.7.0-c50.img"
b. next click "Install Recovery" and if prompted for verification of install path and for install version select "YES" & "NORMAL"
21. After the TWRP setup is complete it may prompt you to reboot, if not click the arrow in the top left of the TWRP Manager screen and scroll down to "Reboot" and select "Reboot device"
22. After Reboot click TWRP Manager and verify a SuperSu prompt comes up if it hasn't already before the boot
At this point the device should be running smoothly. From here I prefer to do the following steps.
My Personal Setup after new install:
+Personally I like to install use a Root Uninstaller (I use 3C Toolbox Pro) and Uninstall and Backup all MetroPCS BloatWare including the Metro Browser.
+I also access the Hidden Menu by using the Dialer and Dial "2776348*#*"
- I scroll down to ApnUnlock and click to "Unlock APN"
- Then I navigate to Settings -Tethering & networks - Mobile Networks (I check off roaming data) - Access point names
--I then select the top APN and edit APN Type to: default,supl,mms,dun
---I click save from the top right selection, then turn on and off airplane mode
+If you are and Xposed user download "xposed-v79-sdk22-arm.zip","xposed-uninstaller-20150831-arm.zip", and "XposedInstaller_3.0_alpha4.apk" from: http://forum.xda-developers.com/showthread.php?t=3034811
-install the Xposed Installer, then Go to TWRP Manager, use reboot to recovery and from there click install and navigate to the "xposed-v79-sdk22-arm.zip" and install and reboot, it will reboot with a installing screen before your home screen, takes 5 minutes.
+I also use this AMAZING app "Wifi Tether Router", it is the only tethering app I use that works consistently (if you have an unlimited data plan). I get 30mbps up and down, playing many multiplayer games off my PC and PS4 averaging ping as low as 30 ! Setting I use for our device are in a post I created here: http://forum.xda-developers.com/leon/help/unlimited-metropcs-t-mobile-tether-t3290180
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Special Thanks to:
MrW0lf from www.W0lfdroid.com for the Kingroot to SuperSU scrip
Numerous users on the XDA forums I pieced all of this information with
Fabio Grasso for making the amazing Wifi Tether Router
Team Win for being creating an awesome utility that has saved me from numerous bricks creating a stable method
Xposed and the creators of awesome additions such as Lolistat, Lucky Patcher, Max Lock, and SNAPPREFS
Any feedback? Did I do Okay? Questions? Let me know!
Worked for me on T-mobile H345
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
kodacy said:
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
Click to expand...
Click to collapse
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
brad2192 said:
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
Click to expand...
Click to collapse
No problem thank you for your help!
will i still have metro service?
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
kap10nuka said:
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
Click to expand...
Click to collapse
Same here (firmware update) usb not detected when using the S/W update tool
After going all the way through this guide with a T-Mobile Leon, I do indeed have a Metro PCS ROM and root, which is great! Unfortunately, it also refuses to acknowledge my T-Mobile SIM. In fairness, I did not even insert a SIM for the first time (just got the phone) until the end of the process, but it shows as carrier locked which is significantly less than useful. I'll flash back to a TMO rom and put the SIM in to double check, but it's quite a bummer. Great job on the guide otherwise, though! It definitely did what it says on the tin; I have root and apart from the SIM lock which may be my fault somehow it works great.
Hey bud those links are no longer valid know where i can get them?
**Root access required**
Download:
- G900T_PE1_Batch_Debloater
Instructions:
1. Extract the G900T_PE1_Batch_DeBloater folder onto your desktop.
2. Turn on USB Debugging from Developer Options and connect your device to your *PC.
3. Double-click debloater.bat to launch the program.
4. Grant Root Access if prompted by your device.
5. Select "Light," "Medium," or "Extreme" **debloating and press "Enter."
6. Once complete press "Enter" to return to the Main Menu and select ***Reboot Device.
7. Last, select "Exit" from the main menu to end your session. Done!
* Make certain that you have Samsung Drivers installed.
** Use Notepad++ or other text editor to view/edit the lists of removed apps in debloater.bat file.
*** It is normal for apps to begin force closing prior to rebooting your device.
muniz_ri said:
**Root access required**
Download:
- G900T_PE1_Batch_Debloater
Instructions:
1. Extract the G900T_PE1_Batch_DeBloater folder onto your desktop.
2. Turn on USB Debugging from Developer Options and connect your device to your *PC.
3. Double-click debloater.bat to launch the program.
4. Grant Root Access if prompted by your device.
5. Select "Light," "Medium," or "Extreme" **debloating and press "Enter."
6. Once complete press "Enter" to return to the Main Menu and select ***Reboot Device.
7. Last, select "Exit" from the main menu to end your session. Done!
* Make certain that you have Samsung Drivers installed.
** Use Notepad++ or other text editor to view/edit the lists of removed apps in debloater.bat file.
*** It is normal for apps to begin force closing prior to rebooting your device.
Click to expand...
Click to collapse
Thx for this tool, not just for the sake of it, but for the sake of us newbies being able to learn some basics from reading a batch file as well.
Waltsmith
I have the Samsung drivers installed and USB debugging on, however, the bat file stays on "Waiting for device". Normally I would get a notification granting my comp privileges for the debugging but no dice.
Cdub1976 said:
I have the Samsung drivers installed and USB debugging on, however, the bat file stays on "Waiting for device". Normally I would get a notification granting my comp privileges for the debugging but no dice.
Click to expand...
Click to collapse
I get the same unless i right click and run as admin but when i hit 2 (medium) then go i get the following?
UPDATE: Nevermind the reason adb commands were not running was due to the custom kernel i was using. switched kernels and the debloater worked fine.
destructionj said:
I get the same unless i right click and run as admin but when i hit 2 (medium) then go i get the following?
View attachment 3808327
UPDATE: Nevermind the reason adb commands were not running was due to the custom kernel i was using. switched kernels and the debloater worked fine.
Click to expand...
Click to collapse
Interesting. Thanks. I think I flashed the rom and Shinysides kernel. I'll have to try it without next time.
Sent from my SM-G900T using XDA-Developers mobile app
Cdub1976 said:
Interesting. Thanks. I think I flashed the rom and Shinysides kernel. I'll have to try it without next time.
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
yep thats the one. i flashed over to PhoeniX Kernel cuz i couldnt find the stock PE1. The phone booted and debloater worked fine.
http://forum.xda-developers.com/gal...kernel-phoenix-kernel-v7-marshmallow-t3340407
If you plan on using this with the latest update GPG2, edit the .bat file and remove the last line for TmoWfcPrefs, this is needed to change wifi calling preferences.
T-mobile latest marshmallow unrootable
Chuki82 said:
If you plan on using this with the latest update GPG2, edit the .bat file and remove the last line for TmoWfcPrefs, this is needed to change wifi calling preferences.
Click to expand...
Click to collapse
Hi im using the latest marshmallow of t-mobile
Any tips on how can i root my device?
ElKapitan_10 said:
Hi im using the latest marshmallow of t-mobile
Any tips on how can i root my device?
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmo...l/root-how-to-root-sm-g900t-firmware-t3358190
As far as I know my phone has 6.0..1 Marshmallow and all is stock. Will the debloater program work on it?
ElKapitan_10 said:
Hi im using the latest marshmallow of t-mobile
Any tips on how can i root my device?
Click to expand...
Click to collapse
Have you tried CF-Auto-Root?
Chuki82 said:
If you plan on using this with the latest update GPG2, edit the .bat file and remove the last line for TmoWfcPrefs, this is needed to change wifi calling preferences.
Click to expand...
Click to collapse
OK, so I am dependent upon WiFI calling at work, and I did this, but maybe it's because I have an 11 month old or I don't know what but I must not have saved the BAT file correctly. anyway, I broke my WiFi calling.
- EDIT: it works if I turn it on with the quick icon - but if I go to settings, and click more networks, then click wifi calling it just crashes settings every time. any ideas?
Thanks in advance.
See post number 8 in this thread.
Sent from my SM-G900T
I have a Razer Phone 2 rooted with magisk. I use GPS Joystick. I decided to select the "disable system GPS" setting in its options. I rebooted as the app requested and now my phone loads to the point where it wants me to enter my pin and I see my wallpaper for a split second then the screen goes black and it loads up the status bar about ever 10 seconds for a split second then it repeats. Like it is stuck in a loop. After a couple minutes phone reboots and I get this message...
Android Recovery
razer/chery12/aura
9/P-MR1-RC003-RZR-190305/3110
user/release-keys
Use volume up/down and power
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
Click to expand...
Click to collapse
So I reached out to the dev of GPS Joystick and he explains that the option disables the location services called "fused location provider" and I have to re-enable it to fix the problem. He sent me a post here explaining that I need to pull an .xml file from the phone, change the code, and push it back. Simple right? Well maybe if I have TWRP, but I don't. I can however boot into the phones recovery options and there is an option there to "apply update from adb" but I cannot seem to pull anything using that interface. My Windows computer recognizes the device using Minimal ADB and Fastboot but it shows it as a whole bunch of numbers then the word "sideload" which I guess is a limited form of adb just for side loading? Maybe someone could make me a script that I can sideload that changes the file back to normal? Here is the code from the dev of GPS Jostick that is used to disable and enable the fused lcoation provider.
It calls this code to disable:
ComponentName component = new ComponentName("com.android.location.fused", "com.android.location.fused.FusedLocationService");
getActivity().getPackageManager().setComponentEnabledSetting(component, PackageManager.COMPONENT_ENABLED_STATE_DISABLED, 0);
And similar code to re-enable it:
ComponentName component = new ComponentName("com.android.location.fused", "com.android.location.fused.FusedLocationService");
getActivity().getPackageManager().setComponentEnabledSetting(component, PackageManager.COMPONENT_ENABLED_STATE_ENABLED, 0);
Click to expand...
Click to collapse
So my question is, can I pull this /data/system/users/0/package-restrictions.xml file from my phone and push it back without using TWRP? But instead using the phones recovery option and its various selections? I'd prefer to exhaust the resources to recover the phone since I have spent weeks personalizing it. I am not fluent in adb but I am hoping someone can throw some ideas or even a solution at me that I am missing. All I got to do is pull a file, change a word, push it back and reboot. I can't imagine there isn't a way to do this by just using what the phone has to offer. Any help would be greatly appreciated.
Another idea that came to mind is in its current condition could I install TWRP? Is fastboot an option at this point? Maybe if I can flash TWRP in its current state I can then make the appropriate modifications.
I ended up fixing the problem. I installed arter97's kernel that had TWRP baked into it. I then used TWRP to copy over the .xml file, change the code as mentioned above, and then copied it back to the phone. Problem solved. It is amazing how one simple word in a .xml file can prevent a phone from functioning properly. It simply amazes me.