Related
As we have all seen with this latest STOCK G935U [BQD2] Firmware for T-Mobile indeed it runs smooth and personally I have experienced better performance without all those carrier-bloat applications by default. Dating a week ago, I tried to root this build version and for some reason I experienced infinite bootloops after my device boots up. So I did some research as to what system apps could be causing this I still I can't believe that a network-related system application was causing this issue.
I am talking about com.samsung.sprint.chameleon as mentioned by @qwewqa here -> https://forum.xda-developers.com/tmobile-s7-edge/how-to/4-28-t-mobile-935-firmware-t3597866/page10
I will not go in-depth about what this is but this relates to a network configuration. I will post a reference on this if you guys feel like checking out...
https://community.sprint.com/t5/Archives/Chameleon/td-p/654097
FAST & STABLE ROOT METHOD FOR THE G935U under T-Mobile // S7 EDGE
1 - Download & Flash Via Odin the latest Firmware provided on this post. Thanks to @justda
https://forum.xda-developers.com/tmobile-s7-edge/how-to/4-28-t-mobile-935-firmware-t3597866
------------ HERE COMES THE MOST IMPORTANT STEP ON THIS GUIDE ----------
2 - Install Package Disabler Pro from OSPolice. Play Store link ...
https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro&hl=es
3 - Open the application, activate Device Administrator, just hit next or ok or just follow through the setup and once the apps list loads up look for the system app with the name of: com.samsung.sprint.chameleon. Go ahead clear data and DISABLE it. After you are done disabling this system app, you are now safe and good to follow through the root method below.
4 - I suggest that you use the root.bat file provided by @Quickvic30 on this thread to root your device
https://forum.xda-developers.com/tmobile-s7-edge/how-to/heres-how-rooted-nougat-s7-edge-g935t-t3567502
IF YOU HAVE SUCCESSFULLY BOOTED UP YOUR DEVICE PAST THE SAMSUNG SCREEN WITHOUT ENDING UP IN BOOTLOOPS (Bootloops may occur within 30 seconds after booting up from the Samsung Screen) THATS IT, YOU ARE DONE!
### Post-Root Suggestions ###
Applications to Install:
Titanium Backup
Kernel Adiutor
L-Speed
SD Maid
THE FOLLOWING XML DEBLOAT PACKAGE IS FOR THOSE WHO ARE LOOKING INTO DISABLING THE MOST PACKAGES INCLUDING SOME STOCK APKS. PLEASE CAREFULLY GO OVER THE LIST ATTACHED AND JUST CONTINUE ON TO MAKE ANY MODIFICATIONS TO FIT YOUR NEEDS
### DEBLOATER FOR PACKAGE DISABLER PRO - SAFE TO DISABLE APPS & SYSTEM APPS [~1950 MB RAM FREE - SOMETIMES 2000 MB's] ###
Attached is the xml file for Package Disabler Pro that will free ~ 2 GB RAM on your device.
Since I don't see any mention of using the engineering kernel should I assume this method does not work for US models?
So basically you take qwewqa's discovery, make no mention of him, then pass it off as your own. Then copy and paste some steps from other people, and submit it as your work?
markmain2. 0 said:
Since I don't see any mention of using the engineering kernel should I assume this method does not work for US models?
Click to expand...
Click to collapse
As referred in the procedure section. The main and original root method goes to the forum thread linked above. As I briefly specified in the background info section, this is just a quick fix in performance and stability when applying root to this build.
tofu- said:
So basically you take qwewqa's discovery, make no mention of him, then pass it off as your own. Then copy and paste some steps from other people, and submit it as your work?
Click to expand...
Click to collapse
I didn't copy nor plagiarize any information from their respective owners. Credits are given, very briefly detailed information on the steps as to the main reason of this thread is just giving the list and proceed with the order of steps to successfully achieve root. The link that I attached in regards to the conflicting system app that where I noticed the issue with other models.
I didn't look into @qwewqa thread comment regarding this, and I apologize and edited to credit him on this finding.
The debloat list provided is extremely aggresive. It removes the stock gallery, stock calender, lock screen wallpaper, stock contacts, Bluetooth, and all google back up services.
Your list is great for the hardcore folks BUT you have to go back through the lost and re-enable the apps and clear the data then re disable them.
Sent from my SM-G935U using XDA Premium HD app
Brian,
Thanks for bringing it all together. I am currently rooted on T-Mobile QC1. I wanted to go to the U firmware wanted a tested way to root first.
Pat
Thank you kindly. Going to try this out right now
gonna give this a try, Any kernel tweak recommendations? how smooth/fast is it or does it lag like a bunch
any fix for the finger print sensor?
Im think the eng is conflicting with a app killing the fingerprint sensor
patcal said:
Brian,
Thanks for bringing it all together. I am currently rooted on T-Mobile QC1. I wanted to go to the U firmware wanted a tested way to root first.
Pat
Click to expand...
Click to collapse
Hey Pat,
In fact there is a way to root the U Firmware and achieve functionality and administration. All thanks to their devs for their work
black96ss said:
gonna give this a try, Any kernel tweak recommendations? how smooth/fast is it or does it lag like a bunch
Click to expand...
Click to collapse
As a matter of fact, the root.bat from @Quickvic30 does all the jobs needed. I strongly suggest running his method. No L Speed, no Kernel Adiutor. Just Titanium Backup to freeze/uninstall bloatware.
black96ss said:
gonna give this a try, Any kernel tweak recommendations? how smooth/fast is it or does it lag like a bunch
Click to expand...
Click to collapse
black96ss said:
any fix for the finger print sensor?
Click to expand...
Click to collapse
Hmmm...to be honest I didn't have any issues regarding the fingerprint sensor. Have you solved your issue by now?
Broken Fingerprint Sensor
purotijuana said:
Hmmm...to be honest I didn't have any issues regarding the fingerprint sensor. Have you solved your issue by now?
Click to expand...
Click to collapse
Yes, I also have the same problem. The fingerprint sensor has stopped working after flashing the Eng Bootloader.
Found the fix: Credits to qwewqa
Link
Dexolit said:
Yes, I also have the same problem. The fingerprint sensor has stopped working after flashing the Eng Bootloader.
Found the fix: Credits to qwewqa
Link
Click to expand...
Click to collapse
I tried to use this method but my phone won't let me change permissions. It pops up with a message that says "changing permissions was not successful. Please note that some file systems do not allow permission changes." Is there something special I need to do to enable permission changes?
Also I am using root browser to do this.
nickp22127 said:
I tried to use this method but my phone won't let me change permissions. It pops up with a message that says "changing permissions was not successful. Please note that some file systems do not allow permission changes." Is there something special I need to do to enable permission changes?
Also I am using root browser to do this.
Click to expand...
Click to collapse
Try another file browser. Root Explorer is what I have always used.
patcal said:
Try another file browser. Root Explorer is what I have always used.
Click to expand...
Click to collapse
Awesome man it worked! Thanks a lot. Root explorer seems pretty legit by the way. I've only ever used root browser.
nickp22127 said:
Awesome man it worked! Thanks a lot. Root explorer seems pretty legit by the way. I've only ever used root browser.
Click to expand...
Click to collapse
Glad it worked. I have been using Root Explorer for as long as I have been using & rooting android phones.
nickp22127 said:
I tried to use this method but my phone won't let me change permissions. It pops up with a message that says "changing permissions was not successful. Please note that some file systems do not allow permission changes." Is there something special I need to do to enable permission changes?
Also I am using root browser to do this.
Click to expand...
Click to collapse
I also had that problem too. Just extract the libs and overwrite them in /system/lib and /lib64, then change the permissions to rw-r--r--. Apparently, it only worked after overwriting the files.
Disclamer: use at your own risk. I take no responsibility for bricked devices, bootloops, etc..)
Updated for Pixel 4 XL from my Pixel 3 XL Thread
Like my 3 XL, I unlocked and rooted out of the box but have a grandfathered At&t Unlimited Data Plan. At&t has somehow figured out how to block tethering on a Google purchased and unlocked device. Did a little research, and tethering can be achieved using methods already available for other devices. This can be done entirely on the device. Confirmed to work with At&t grandfathered unlimited, haven't tested others.
Prerequisites:
Unlocked Bootloader and Root with Magisk(See the How-Tos here: https://forum.xda-developers.com/pixel-4-xl/how-to/root-pixel-4-xl-unlocked-google-store-t3989033)
Magisk Module MagiskHide Props Config (available directly through Magisk)
BusyBox Module Installed
Terminal editor of your choice installed on your device
Step one: Make sure you're up to date on the Prerequisites above.
Step two: Open terminal editor and grant SU access by typing
Code:
su
Step three: Open up the props config by typing
Code:
props
Step four: Select add/edit custom props by typing
Code:
4
, Select new custom prop by typing
Code:
n
Step five: type
Code:
net.tethering.noprovisioning
it will ask what you want to set it to, type
Code:
true
make sure this is all lower case it will then ask you to confirm with y and ask if you want to reboot, select y again
Step six: Open the terminal again and grant SU access
Step seven: type
Code:
settings put global tether_dun_required 0
and exit the terminal
Step eight: reboot
Step nine: test the hotspot and crack a beverage of your choice to celebrate
On my Pixel 3 XL, If I sideloaded an OTA and was just re-enabling this mod, Steps 6-8 should were not required. Quick update(note from my Pixel 3XL thread 4/17/19), just sideloaded the April OTA via ADB. That retained my bypass settings, and tethering works even after re-rooting with no other changes (not even build.prop). it would seem that unless you flash the factory image, you should retain these modifications (but not root, go figure)
That works! Thank you.
Quick update to this. Re-rooting after sideloading the OTA still retains the tethering settings as it did in the April update to the 3XL
An easier way to do this is to add
net.tethering.noprovisioning=true
To the very end of the build prop using any note editor with root access.
You of course still have to follow The process to root your phone first.
Will this obscure Tmo from knowing how much I tether vs use as regular data?
bbender716 said:
Will this obscure Tmo from knowing how much I tether vs use as regular data?
Click to expand...
Click to collapse
Not sure, do you use native tethering with T-Mo, or is it their app?
emulater tells me inaccessible or not found after SU step when entering props
miahdog said:
emulater tells me inaccessible or not found after SU step when entering props
Click to expand...
Click to collapse
Are you rooted?
There is a magisk module that works as well (same commands in magisk module format essentially).
https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427
loonix said:
There is a magisk module that works as well (same commands in magisk module format essentially).
https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427
Click to expand...
Click to collapse
This one won't unlock the throttles that the carrier does, about 60kBps which you can't even see a YouTube video without buffering.
On t-mobile, you can see the hotspot usage., in other hand .. Pdanet+ USB hides it and you can use the phone download speed. Which goes about 7MBps... Hopefully this trick fixes it.. It did with the 2xl.. Eager to try it now.
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
fredgar75 said:
An easier way to do this is to add
net.tethering.noprovisioning=true
To the very end of the build prop using any note editor with root access.
You of course still have to follow The process to root your phone first.
Click to expand...
Click to collapse
Pixel 4 xl partitions A/B won't allow you to do so.... Build.prop can't be written for some reason.
@Gloff thanks! It worked on my 4xl on at&t 0120 security update.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
miahdog said:
emulater tells me inaccessible or not found after SU step when entering props
Click to expand...
Click to collapse
I was getting the same message untill I flashed the magisk hide prop module. After that I was able to follow the guide.
Who-Lep said:
@Gloff thanks! It worked on my 4xl on at&t 0120 security update.
---------- Post added at 05:50 AM ---------- Previous post was at 05:46 AM ----------
I was getting the same message untill I flashed the magisk hide prop module. After that I was able to follow the guide.
Click to expand...
Click to collapse
Glad I could help!
Ah yes, magisk hide prop is in the prerequisites, that's the tool that works through the emulator to edit the build.prop and global settings
eloko said:
This one won't unlock the throttles that the carrier does, about 60kBps which you can't even see a YouTube video without buffering.
On t-mobile, you can see the hotspot usage., in other hand .. Pdanet+ USB hides it and you can use the phone download speed. Which goes about 7MBps... Hopefully this trick fixes it.. It did with the 2xl.. Eager to try it now.
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
Pixel 4 xl partitions A/B won't allow you to do so.... Build.prop can't be written for some reason.
Click to expand...
Click to collapse
That's not true.. Look at the scripts inside the magisk module
In post-fs-data.sh
Code:
# This script will be executed in post-fs-data mode
settings put global tether_dun_required 0
and in system.prop
Code:
# This file will be read by resetprop
# Example: Change dpi
# ro.sf.lcd_density=320
net.tethering.noprovisioning=true
Exact same commands as what you have in your OP.
loonix said:
There is a magisk module that works as well (same commands in magisk module format essentially).
https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427
Click to expand...
Click to collapse
Thanks
this thing wont unlocked the throttle, hotspot is enable but cant get more thatn 1mbps download. using vpn hotspot gets me 12mbps. FYI
The service/throttling etc are carrier dependent. I just wanted to mention that a magisk module that achieves the same commands is available for those who prefer to enable/disable it within the magisk manager. What you posted is all good, just the command line equivalent.
Hey all,
Its been a few years since I've messed around with the tethering on Nexus/Pixel devices.
I have a question...
Is this supposed to hide tethering usage from carrier? I'm on TMo native tethering and the usage is showing up when I check in the TMo app.
Sorry if this is something simple, I just need to make sure I'm not missing something.
Side Note:
I'm getting 100Mb+ through native tethering and only about 10Mb with PDANet.
Thanks.
Just an FYI - working perfectly on my Verizon 4xl
TriniMike215 said:
Hey all,
Its been a few years since I've messed around with the tethering on Nexus/Pixel devices.
I have a question...
Is this supposed to hide tethering usage from carrier? I'm on TMo native tethering and the usage is showing up when I check in the TMo app.
Sorry if this is something simple, I just need to make sure I'm not missing something.
Side Note:
I'm getting 100Mb+ through native tethering and only about 10Mb with PDANet.
Thanks.
Click to expand...
Click to collapse
I do not know if this will block that. I used about 20gb last month solely through tethering and didn't hear a peep from att, even though the plan i'm on is not native tether friendly. If they know, they don't care.
dtroup64 said:
Just an FYI - working perfectly on my Verizon 4xl
Click to expand...
Click to collapse
What sort of speeds are you getting? Did you do the opening post method or the magisk one?
Hey guys... I've seen various methods to get Google Pay working and simply put, none of them worked for me. All that I could find left was advanced stuff involving SQLite editors and that's just not for everyone. So I started trying other known working methods from different devices, and this is what I did to get it going without issue.
1. Open Magisk, Magisk Hide, and tick the check box next to Google Pay. Proceed normally through the following steps after doing so.
2. Force stop Google Pay, clear app data/storage.
3. Open a root file manager
4. Using root file manager, find /data/data/com.google.android.gms/databases directory
5. Select a file called db.dg and chmod the permissions to 440, save and make sure it in fact saves
6. Reboot and set up Google Pay.
This should get you set up in no time without a need for modules or advanced user techniques. Hope it helps!
Edit: People seem to really dislike this method for some reason, so just throwing out there it seems everyone else recommends the SQL editing. This method worked for me, but YMMV and everyone else hates it
wrongway213 said:
Hey guys... I've seen various methods to get Google Pay working and simply put, none of them worked for me. All that I could find left was advanced stuff involving SQLite editors and that's just not for everyone. So I started trying other known working methods from different devices, and this is what I did to get it going without issue.
Unlocked users start at Step 1 below. Rooted users - First open Magisk, Magisk Hide, and tick the check box next to Google Pay. Proceed normally through the following steps after doing so.
1. Force stop Google Pay, clear app data/storage.
2. Open a root file manager OR reboot to TWRP if you don't have one
3. Using root file manager OR TWRP file manager, find /data/data/com.google.android.gms/databases directory
4. Select a file called db.dg and chmod the permissions to 440, confirm if in TWRP, save and make sure it in fact saves if using a file manager.
5. Whether in TWRP or using a root file manager. reboot and set up Google Pay.
This should get you set up in no time without a need for modules or advanced user techniques. Hope it helps!
Click to expand...
Click to collapse
That will only work if the attestation values in the dg.db file haven't been changed to flag root/unlocked bootloader already.
If your values have already been changed, you will need to manually edit the dg.db file or use the Magisk modules from this post: https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950/post79643248
ilal2ielli said:
That will only work if the attestation values in the dg.db file haven't been changed to flag root/unlocked bootloader already.
If your values have already been changed, you will need to manually edit the dg.db file or use the Magisk modules from this post: https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950/post79643248
Click to expand...
Click to collapse
Yeah... I'm not sold on making those kinds of edits or loading modules that do so without a working TWRP for this device anywhere in sight. That's precisely why I posted this thread - a working solution that doesn't involve editing things at that level - even if it doesn't work for everyone, I think it'll be more comfortale for those apprehensive to make certain changes without recovery :good:
wrongway213 said:
Yeah... I'm not sold on making those kinds of edits or loading modules that do so without a working TWRP for this device anywhere in sight. That's precisely why I posted this thread - a working solution that doesn't involve editing things at that level - even if it doesn't work for everyone, I think it'll be more comfortale for those apprehensive to make certain changes without recovery :good:
Click to expand...
Click to collapse
Having TWRP or not changes nothing for anyone that makes a mistake with those edits or Magisk. Editing the dg.db and messing that up doesn't require TWRP to fix it and there's already a boot image with Magisk core only mode posted by Tulsdiver that will save you in case a Magisk module screws things up (the Google Pay fix module is working perfectly, BTW).
People probably shouldn't be messing with any of this until they understand everything that entails getting Google Pay working on a modified device. I'd argue that changing permissions of the dg.db file is just as difficult for anyone who doesn't understand what they're doing as it is going all the way and modifying the actual values in the dg.db file. It's all a slippery slope for the overzealous people anyway.
wrongway213 said:
Yeah... I'm not sold on making those kinds of edits or loading modules that do so without a working TWRP for this device anywhere in sight. That's precisely why I posted this thread - a working solution that doesn't involve editing things at that level - even if it doesn't work for everyone, I think it'll be more comfortale for those apprehensive to make certain changes without recovery :good:
Click to expand...
Click to collapse
Grab the modified kernel in the themes area that forces modules to be deactivated. That way you can just temp boot it to fix your issues if it goes south on you. I've used it several times so far when needing around with different combos of mods, etc...
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
While I appreciate your efforts this is a halfbaked hack and like the previous poster said it's will do nothing if those values have been tripped. I have always been a believer of figuring out things and going the long route that way you know why and how it was done it's very convenient for somebody else to do it and you just flash it but if you do it yourself you'll find out the intricacies of how Android and how rooting and modding works....
CyberpodS2 said:
Grab the modified kernel in the themes area that forces modules to be deactivated. That way you can just temp boot it to fix your issues if it goes south on you. I've used it several times so far when needing around with different combos of mods, etc...
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Click to expand...
Click to collapse
That's kind of my reason for not wanting to use mods on this device yet - being tied to Fastboot at any given time isn't practical for me. Being unable to buy gas because my phone isn't set up isn't practical for me. My goal is to use my device just like I did when I had working TWRP on other devices without losing functionality OR having to rush to a PC for fastboot. Neither are practical solutions for me - making simple modifications that are easily overwritten gives me much less anxiety than messing with things at a deeper level.
wrongway213 said:
Yeah... I'm not sold on making those kinds of edits or loading modules that do so without a working TWRP for this device anywhere in sight. That's precisely why I posted this thread - a working solution that doesn't involve editing things at that level - even if it doesn't work for everyone, I think it'll be more comfortale for those apprehensive to make certain changes without recovery :good:
Click to expand...
Click to collapse
No disrespect, it looks like you're active here and helpful, but I don't think editing some values some values in a SQL editor that is tested and proven in a thread that has 55+ pages is going to hurt anything.
vanydotk said:
No disrespect, it looks like you're active here and helpful, but I don't think editing some values some values in a SQL editor that is tested and proven in a thread that has 55+ pages is going to hurt anything.
Click to expand...
Click to collapse
I'm apprehensive because of what SQL changes under the hood typically mean. I know most people haven't built ROMs, built kernels, maintained for a ROM Team, done platform development, etc. etc . - I have done all those things. One thing I learned is that there are TWO scenarios that will ALWAYS necessitate a clean flash no matter what - SQL changes and Android version changes. Given we don't know as much as we typically do about the state of Coral without TWRP due to Android 10 changes makes me unwilling to assume things proven to work on other devices will work when we get an OTA on this one. Chmod perms will be overwritten but SQLite changes can cause things to go south in my experience - none of which relating to this module. It's about SQL vs chmod for me. I'm doing what I trust and understand until recovery exists to fix things without needing a PC. If no one else finds use for it, I'm OK with that. For my use case - it makes perfect sense. :good:
Fair enough, I figured you knew what you were talking about, everyone needs to make their own decisions. Nonetheless, thanks for contributing!
Here's a simple way to get gpay to work on stock with root after you hide gms and gpay with magisk.
1. Install Termux app and open the app
2. Type pkg install sqlite hit enter and let it install.
3. Type su hit enter
4. Copy and paste this then hit enter
am force-stop /data/data/com.google.android.apps.walletnfcrel && chmod 777 /data/data/com.google.android.gms/databases/dg.db && /data/data/com.termux/files/usr/bin/sqlite3 /data/data/com.google.android.gms/databases/dg.db "update main set c='0' where a like '%attest%';" && chmod 444 /data/data/com.google.android.gms/databases/dg.db
5. Reboot
The Magisk modules are honestly easier.
Busybox module, SQLite module, reboot, the fix module, and reboot once more.
LLStarks said:
The Magisk modules are honestly easier.
Busybox module, SQLite module, reboot, the fix module, and reboot once more.
Click to expand...
Click to collapse
How hard is it to enter a few lines in terminal? Lol
People should learn how to fix things without always relying on a module or a zip they can flash.
The manual fix isn't persistent.
LLStarks said:
The manual fix isn't persistent.
Click to expand...
Click to collapse
What I posted is.
It's weird that google pay to registry my credit cards is so unstable after flashing Gpay Sqlite fixer 1.7. When flashing Gpay sqlite fixer 1.7 at first time, I could registry my 1st credit card but it failed in next credit card. It showed up an error message and said that my phone has been rooted and .... ", So I returned commend mode to key-in few words to make me registry rest 3-credit-card successfully.
You could just delete the GMS folder while rooted and it also works
This is something myself and another user found on the p3 when Google started tripping the values on unlock
Rolling back to a previous version also works but we found that deleting that folder from /data/data along with gsf folder fixed it
Of course after clearing gpay cache.
This is working on my p4xl too
wrongway213 said:
I'm apprehensive because of what SQL changes under the hood typically mean. I know most people haven't built ROMs, built kernels, maintained for a ROM Team, done platform development, etc. etc . - I have done all those things. One thing I learned is that there are TWO scenarios that will ALWAYS necessitate a clean flash no matter what - SQL changes and Android version changes. Given we don't know as much as we typically do about the state of Coral without TWRP due to Android 10 changes makes me unwilling to assume things proven to work on other devices will work when we get an OTA on this one. Chmod perms will be overwritten but SQLite changes can cause things to go south in my experience - none of which relating to this module. It's about SQL vs chmod for me. I'm doing what I trust and understand until recovery exists to fix things without needing a PC. If no one else finds use for it, I'm OK with that. For my use case - it makes perfect sense. :good:
Click to expand...
Click to collapse
It might work for you but like it's been said multiple times, if the values are already tripped then your method is useless. Then it would REQUIRE SQL editing.
Posting an incomplete or half baked method can cause issues with newer people on these forums no matter how "simple" it may be.
spaceman860 said:
How hard is it to enter a few lines in terminal? Lol
People should learn how to fix things without always relying on a module or a zip they can flash.
Click to expand...
Click to collapse
This 100%
Sent from my Pixel 4 XL using Tapatalk
Hi there. Just a question. With this mod google pay works flawlessly all the time? No need to redo the procedure all few days when there are updates to play service? Because i need a real stable google pay when i am out only with my mobile to pay.
Just delete the folder...GMS will recreate the folder withthe right values because magisk is already setup to hide GMS
I've looked into the forums and haven't seen anyone ask about this, but ever since a update in January (I think) I've been unable to use my hotspot. I'm on an unlocked rooted phone with verizon as my serivce provider.
Normally I would just edit the build.prop, but lately I've been having issues since MagiskHide Props is a dead module. Does it still work for anyone else?
Am I missing a new feature?
I'm not that verse with how MagiskHide works, so I'll ask is there a way of changing / editing build.prop like the days of old?
rknee said:
I've looked into the forums and haven't seen anyone ask about this, but ever since a update in January (I think) I've been unable to use my hotspot. I'm on an unlocked rooted phone with verizon as my serivce provider.
Normally I would just edit the build.prop, but lately I've been having issues since MagiskHide Props is a dead module. Does it still work for anyone else?
Am I missing a new feature?
I'm not that verse with how MagiskHide works, so I'll ask is there a way of changing / editing build.prop like the days of old?
Click to expand...
Click to collapse
I had a similar issue on the Pixel 5. You should be able to turn the hotspot on while connected to WiFi. Turn Wifi off while leaving the hotspot on and see if it stays on. You shouldn't need to edit anything in the build.prop to get hotspot to work, but there does seem to be an elusive authentication issue.
V0latyle said:
I had a similar issue on the Pixel 5. You should be able to turn the hotspot on while connected to WiFi. Turn Wifi off while leaving the hotspot on and see if it stays on. You shouldn't need to edit anything in the build.prop to get hotspot to work, but there does seem to be an elusive authentication issue.
Click to expand...
Click to collapse
Gave it a try, but my hotspot immediately turns off as soon as I turn off wifi.
If I can figure out why the props command doesn't take. I've read some posts about people talking about "Settings version mismatch" when using props. I'll have to take a look at that thread and see if there are any new answers.
Thanks for the reply
rknee said:
is there a way of changing / editing build.prop like the days of old?
Click to expand...
Click to collapse
I haven't used this so can't comment on how well it works, but maybe it's something that will help your situation.
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is also possible without Magisk) - GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
github.com
Lughnasadh said:
I haven't used this so can't comment on how well it works, but maybe it's something that will help your situation.
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is also possible without Magisk) - GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
github.com
Click to expand...
Click to collapse
thanks for the resource, I'll take a look, as I'd like to learn more in depth of the inner workings.
I've found the issue, MagiskHide still works but for whatever reason the directory that I get started on when opening a terminal app is incorrect, so all that was needed was changing the directory ( /system/bin/ )
Thanks to anyone who took the time to look at this post, but my problem is now resolved
Great a file (no extension) in /data/adb/post-fs-data and put
resetprop prop value
So, "resetprop net.tethering.noprovisioning insert-value"
And reboot. Be sure to give 744 permission
how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Win_7 said:
how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Click to expand...
Click to collapse
There Isn't a screen recorder or secure folder on the SM-A226B you can use calculator+ and flash a android 13 GSI to use the screen recorder.
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
fede2782 said:
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
Click to expand...
Click to collapse
thanks!!!! will this work on any other phone other than a226b?
and do you know of any file manager app that can actually edit system files (i have a good one called filemanager+ but it can only read even if i do mount -o remount,rw /
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (https://www.apkmirror.com/apk/samsu.../samsung-capture-5-4-22-android-apk-download/) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
eh thats ok i used adb and accepted root on device
my phone didnt have the file is that ok if i just create it?
also you made a mistake on the url can you send a working one?
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
um how can i fix "system partition doesnt have enough free space" when trying to convert newer samsung capture to system app
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
fede2782 said:
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
Click to expand...
Click to collapse
oh bruh i deleted system app and reinstalled
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
fede2782 said:
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
Click to expand...
Click to collapse
i still didnt have the file i made it and updated capture but didnt get screen recorder even after reboot :/ am on android 11 and im not updating especially as theres bootloader update
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
fede2782 said:
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
Click to expand...
Click to collapse
i have a70 with screenrecorder its on android 10
my a22 is on oneui 3.1
I don't know.
fede2782 said:
I don't know.
Click to expand...
Click to collapse
alright then sorry for bothgering you
Win_7 said:
alright then sorry for bothgering you
Click to expand...
Click to collapse
Don't worry
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
fede2782 said:
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
Click to expand...
Click to collapse
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Win_7 said:
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Click to expand...
Click to collapse
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
fede2782 said:
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
Click to expand...
Click to collapse
i have AVA6 not 1