Develop Bugs

[Non-Gapps-Solution] To broken home, statusbar, QT, etc

EDIT: Skip to the bottom EDIT for the short version..
Preamble: I searched for a fix to this recently and over the past 10 months and haven't seen any real solutions to this. Most people have probably experienced this issue at some time flashing roms, especially those people running gapps-free Android :highfive: such as myself. A band-aid for fixing this is running gapps' SetupWizard and/or CM's CMAccounts, I started adding CMAccounts.apk to /system/app some months ago to fix this. I was never satisfied with this workaround though since it doesn't narrow down the actual problem, and I really like sticking to the AOSP experience, open-source, no Stasi-esque permissions, and without the need to taint my installation just to set it up (setupwizard does a lot more than you might think).
Using some additional skills I didn't have 6 months ago, I finally isolated the issue to the SQL database /data/data/com.android.providers.settings/databases/settings.db, table global, value name device_provisioned. It is set to "0" by default which leads to all these ridiculous problems, and setting it to "1" + a reboot fixes all of these problems for me. Setting it back to "0" + reboot breaks everything again, back to "1" fixes, provision.apk present or removed.. I searched for (sqlite3 dump | grep) lots of other provision and setup value differences... tested this a lot.
!!!BACKUP /data/data/com.android.providers.settings/databases/settings.db before attempting this. Use 'busybox cp -p /data/data/com.android.providers.settings/databases/settings.db Your_Backup_Location' to copy and keep correct permissions on it. I would do a nandroid backup maybe anyway. This should be harmless or very helpful, but it's a su'd command in depths of /data so ya never know.
A couple simple ways to get this set right since you can't reliably grep'n'sed here: Get a nice free sql-frontend app off fdroid or xda -very handy- and go to the settings.db file, 'global' table, and then find or add "device_provisioned" in the name column and "1" in the value column. Root Explorer has this built in I think. The better way though is to pull up the 'adb shell' terminal remotely or use a terminal emulator from the phone with free && adfree Jack Palevich's Terminal Emulator, Spartacus Rex' Terminal IDE (recommended ...for everything!), anything using a jni_exec java execute emulation command. Also Ghisler's Total commander file manager has a built-in command line for convenient executions (or cool shell-script shortcuts you can make --it was actually the first tasker).
# Enter each command line by line (after '>'):
Code:
>su
>$(which sqlite3) /data/data/com.android.providers.settings/databases/settings.db
>update global set value="1" where name="device_provisioned";
>.quit
>exit 0
# One-liner
Code:
su && $(which sqlite3) /data/data/com.android.providers.settings/databases/settings.db 'update global set value="1" where name="device_provisioned";'; exit 0
Then just reboot, enjoy that home softkey that takes you to your launcher home.. your notification bar that displays your notifications. lol such basic s***.
Hope this can help someone else out as much as it did me. You don't have to use gapps/setupwizard to fix it! I also want to make sure there isn't another rogue SQL.db value. (btw if you happen to read this and have a broken back softkey/button, your problem is likely the lib file /system/lib/jni_latinime.so. Thought I'd throw that out there.)
EDIT: Heres an update short version. I added another sqlite value that needs correcting in ROMs without gapps setup bla installed. Run these commands in terminal emulator or via adb. Just copy and paste, they need to be exact.
Check that the values on the right are "1" when you fire off:
Code:
su -c '"$(whence -p sqlite3)" /data/data/com.android.providers.settings/databases/settings.db '\''select * from global where name="device_provisioned"; select * from secure where name="user_setup_complete";'\'
Otherwise or just to be safe, fire off this wicked one liner(Warning: reboots when finished):
Code:
su -c '"$(whence -p sqlite3)" /data/data/com.android.providers.settings/databases/settings.db '\''update global set value="1" where name="device_provisioned"; update secure set value="1" where name="user_setup_complete";'\'' && sync && fsync /data; sleep 3; svc power reboot'
Done, 1-2 steps.

Great write up and worked perfectly. Any more tips tricks advice or links for non-gapps users?

namtombout said:
Great write up and worked perfectly. Any more tips tricks advice or links for non-gapps users?
Click to expand...
Click to collapse
Yeah man, glad it worked. Cheers to your cojones for trying it!
What I usually do for a no gapp solution is:
-grab the libjni_latinime lib from microgapps cause its needed for the aosp keyboard swipe usually
-use "gapps browser" for Google related stuff like gmaps.
-or use rmaps (this and gapps browser need the maps api, so you gotta pull the google maps framework jar or use the "no-gapps project" hack api /system/framework/*google*jar. Make sure to add the corresponding /etc/permissions/*google*xml files too)
-instead of gmail I use the standard email client of k9
-instead of play I use fdroid, aptoide sometimes, nextwap.net, or mobilism forums, or a lucky patcher cracked Google play. (careful with the non-fdroid ones)
Sorry bout this 6 month late reply, Jesus I gotta watch my posts more closely.

Developer needs your feedback (sense lock screen & root needed)

Hi;
I'm currently developing an application (seen in my signature). One of the things users are asking is the action to remove lock when certain conditions are met. This, however, can be echieved with root permissions and here's where you step in.
Since there are some differences in roms developed by Sony, Samsung, HTC and others, I am looking for additional info.
So if your phone is rooted and running Stock HTC ROM with Sense UI, you're the person I need!
Please do this steps and just copy paste results here:
1. Enable any kind of lock screen protection in System Settings.
2. Open Terminal Emulator or connect your phone with PC with usb cable and run adb command:
2.1 if Terminal Emulator, run: "su" (without quotes)
2.2 if adb, run: "adb shell" and then "su" (both, without quotes)
3. run command: sqlite3 /data/system/locksettings.db "SELECT * FROM locksettings"
4. save output info somewhere
5. Disable lock screen protection you've enabled in 1st step.
6. run command: sqlite3 /data/system/locksettings.db "SELECT * FROM locksettings"
7. save output info
8. paste output info from #4 & #8
9. ???
10. profit.
Click to expand...
Click to collapse
Here is the example output:
Code:
[email protected]:/ # sqlite3 /data/system/locksettings.db "SELECT * FROM locksettings"
2|migrated|0|true
3|migrated_user_specific|0|true
4|lockscreen.password_salt|0|3977270701243753649
9|lockscreen.passwordhistory|0|
14|lock_pattern_autolock|0|0
15|lockscreen.password_type|0|0
16|lockscreen.password_type_alternate|0|0
17|lockscreen.disabled|0|0
Thank you for your help!
(if you think you're pasting too much information, you can replace any strings (hashes, salts, etc) with zeros or anything else)

How to unlock our redmi 1s phone if it locked you out ??

I just recently discovered that I am doing unlock any phone through simply removing data/system/gesture.key file in recovery .
You just have to open twre and do delete that file that stores your password based data
Ha Ha Ha .... :laugh:
Simple
Isn't it?
Before continue reading I worn you
Thank you must say other wise experience BOOTLOOP.
Well
I got tested only on redmi 1s and lg p500
These are another methods :
If Just Google Ask you For Password (Credentials) - You Can Turn On WIFI Via ADB In Order To Google Accept Your Device Via this Command:
Code:
adb shell svc wifi enable
Requirements:
The Device Needs To Have Usb Debugging Enabled
In Case Usb Debugging Isn't Enabled And You Have Recovery,you Can Run The Same Instructions From Recovery
For Some methods Will Be Better If Device Is Rooted
If None Of This Methods Works For You - Unfortunally You Probably Must not Wipe Your Device please notify me first.
METHOD I
Solution For Everyone With Recovery (Cwm, Twrp, Xrec,Etc...) Installed:
INSTRUCTIONS:
1. Download this zip Pattern Password Disable (Download from google.com) on to your sdcard (using your PC, as you cant get into your phone, right )
2. Insert the sdcard into your phone
3. Reboot into recovery mode
4. Flash the zip
5. Reboot
6. Done!
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
METHOD 2
Solution For Everyone Without Recovery Installed - ADB :
What You Need:
=>A computer running a Linux distro or Windows+Cygwin
=>USB cable to connect your phone to the PC
=>Adb installed
How to install adb:
1. Open Terminal
2. Type:
Code:
sudo apt-get install android-tools-adb
Hit [Enter]
3. Follow the instructions until everything is installed.
INSTRUCTIONS:
1. Connect you (turned on) Phone to the Computer via USB.
2. Open a terminal window.
3. Type:
Code:
adb devices
adb shell
cd data/system
su
rm *.key
4. Done...Now You Just Have To Reboot.
Note : as above...
METHOD 3
Solution For Everyone Before Lock Accident :
SMS Bypass - Download Link - Install It On Your Device (Download from attachments)
This App Allows You To Remotely Bypass Your Phone's Screen Lock By Sending A SMS.
It Removes Your Gesture Pattern Or Password After Receiving A Preset Keyword Along With A Secret Code Via SMS.
SMS Bypass App Requires Root.
INSTRUCTIONS:
1.First, make sure you give permanent root access to the app.
2.Change the secret code to your preferred choice. The default password is : 1234
3.To reset your screen lock, send the following message from another phone:
Code:
secret_code reset
Example:
Code:
1234 reset
Note 1 : There is a space between your secret code and reset. Also the secret code is case sensitive.
Note 2 : There is an option available to change the preset keyword. Default is : reset - Your phone will restart and your lock screen will be reset.
Note 3 : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
METHOD 4
Solution For Everyone Via Adb - SQL Command :
INSTRUCTIONS:
=>Type This Commands Separated In Your Terminal (CMD Prompt) :
Code:
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
=>Now You Just Have To Reboot.
METHOD 5
Solution For Everyone Via Adb - File Removal :
INSTRUCTIONS:
=>Type This Command In Your Terminal (CMD Prompt) :
Code:
adb shell rm /data/system/gesture.key
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
METHOD 6
Solution For Everyone With USB Debugging Enabled :
INSTRUCTIONS:
Primary Step for all method:
Download & Extract to anywhere - Bypass Security Hack (Download from attachments)
Open SQLite Database Browser 2.0.exe in SQLite Database Browser.
Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone.
Drag settings.db and drop to SQLite Database Browser 2.0.exe program.
Navigate to Browse data tab, At table there, click to list down the selection & selete secure
Instruction To Remove Pattern Lock:
Now, find lock_pattern_autolock, Delete Record
Close & save database
Run push settings.db.cmd and reboot your phone
Instruction To Remove PIN Lock:
Now, Find Or Create lockscreen.password_type, double-click & change it's value to 65536, Apply changes!
Now, find lock_pattern_autolock, Delete Record, If doesn't exist, Ignore
Close & save database
Run push settings.db.cmd and reboot your phone
Instruction To Remove Password Lock:
Now, find lockscreen.password_salt, Delete Record
Now, find lockscreen.password_type, Delete Record
Close & save database
Run push settings.db.cmd and reboot your phone
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
METHOD 7
Solution For Everyone With Recovery Installed :
INSTRUCTIONS:
1.Download and Copy Aroma File manager.zip (Download from attachments or http://forum.xda-developers.com/show....php?t=1646108) to your memory card.
2. Open your recovery (press volume Down + Power button or it can be different according to the phones. Generally the phones who have press able button on the middle they have to press all three buttons. Google for you pattern there are lots)
3. There’ll b an option in recovery called “mount”. Go in that option and then mount all the cache and everything it is there.
4. Then select “update” and select “apply update from SD/external” and select aroma file manger.zip file that you downloaded using above QR code above.
5. After Flashing or updating, the aroma file manger will open. Use volume keys for up/down and power button 2 select like you use to get into recovery.
6. In aroma File manager , Go to menu , which is located in bottom strip and then select Settings.
7. Go to bottom n select “mount all partition in startup ” then exit from aroma file manger.
8. Now after exit , re-update that aroma file again and it will open again.
9. Go to data >> and then System.
Then find ‘gesture.key’ (for pattern lock) and ’password.key’ (for password lock) then long touch on gesture.key or password.key and sum option will be prompted , choose delete and delete that file and restart.
Try out one by one
Tell if works on another phonephone
Pattern Disabler zip
http://forum.xda-developers.com/attachment.php?attachmentid=2532214&d=1390399283
SMS bypass app:
http://forum.xda-developers.com/attachment.php?attachmentid=2532215&d=1390399283
Bypass securities mods:
http://forum.xda-developers.com/attachment.php?attachmentid=2532216&d=1390399283
Aroma file manager :
http://forum.xda-developers.com/attachment.php?attachmentid=2532253&d=1390400421
Thank you must say other wise experience BOOTLOOP.

Thanks mate you give all working method for unlock is there

bro plz hit thanks button
niral.naik said:
I just recently discovered that I am doing unlock any phone through simply removing data/system/gesture.key file in recovery .
You just have to open twre and do delete that file that stores your password based data
Ha Ha Ha .... :laugh:
Simple
Isn't it?
Before continue reading I worn you
Thank you must say other wise experience BOOTLOOP.
Well
I got tested only on redmi 1s and lg p500
These are another methods :
If Just Google Ask you For Password (Credentials) - You Can Turn On WIFI Via ADB In Order To Google Accept Your Device Via this Command:
Code:
adb shell svc wifi enable
Requirements:
The Device Needs To Have Usb Debugging Enabled
In Case Usb Debugging Isn't Enabled And You Have Recovery,you Can Run The Same Instructions From Recovery
For Some methods Will Be Better If Device Is Rooted
If None Of This Methods Works For You - Unfortunally You Probably Must not Wipe Your Device please notify me first.
METHOD I
Solution For Everyone With Recovery (Cwm, Twrp, Xrec,Etc...) Installed:
INSTRUCTIONS:
1. Download this zip Pattern Password Disable (Download from google.com) on to your sdcard (using your PC, as you cant get into your phone, right )
2. Insert the sdcard into your phone
3. Reboot into recovery mode
4. Flash the zip
5. Reboot
6. Done!
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
METHOD 2
Solution For Everyone Without Recovery Installed - ADB :
What You Need:
=>A computer running a Linux distro or Windows+Cygwin
=>USB cable to connect your phone to the PC
=>Adb installed
How to install adb:
1. Open Terminal
2. Type:
Code:
sudo apt-get install android-tools-adb
Hit [Enter]
3. Follow the instructions until everything is installed.
INSTRUCTIONS:
1. Connect you (turned on) Phone to the Computer via USB.
2. Open a terminal window.
3. Type:
Code:
adb devices
adb shell
cd data/system
su
rm *.key
4. Done...Now You Just Have To Reboot.
Note : as above...
METHOD 3
Solution For Everyone Before Lock Accident :
SMS Bypass - Download Link - Install It On Your Device (Download from attachments)
This App Allows You To Remotely Bypass Your Phone's Screen Lock By Sending A SMS.
It Removes Your Gesture Pattern Or Password After Receiving A Preset Keyword Along With A Secret Code Via SMS.
SMS Bypass App Requires Root.
INSTRUCTIONS:
1.First, make sure you give permanent root access to the app.
2.Change the secret code to your preferred choice. The default password is : 1234
3.To reset your screen lock, send the following message from another phone:
Code:
secret_code reset
Example:
Code:
1234 reset
Note 1 : There is a space between your secret code and reset. Also the secret code is case sensitive.
Note 2 : There is an option available to change the preset keyword. Default is : reset - Your phone will restart and your lock screen will be reset.
Note 3 : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
METHOD 4
Solution For Everyone Via Adb - SQL Command :
INSTRUCTIONS:
=>Type This Commands Separated In Your Terminal (CMD Prompt) :
Code:
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
=>Now You Just Have To Reboot.
METHOD 5
Solution For Everyone Via Adb - File Removal :
INSTRUCTIONS:
=>Type This Command In Your Terminal (CMD Prompt) :
Code:
adb shell rm /data/system/gesture.key
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
METHOD 6
Solution For Everyone With USB Debugging Enabled :
INSTRUCTIONS:
Primary Step for all method:
Download & Extract to anywhere - Bypass Security Hack (Download from attachments)
Open SQLite Database Browser 2.0.exe in SQLite Database Browser.
Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone.
Drag settings.db and drop to SQLite Database Browser 2.0.exe program.
Navigate to Browse data tab, At table there, click to list down the selection & selete secure
Instruction To Remove Pattern Lock:
Now, find lock_pattern_autolock, Delete Record
Close & save database
Run push settings.db.cmd and reboot your phone
Instruction To Remove PIN Lock:
Now, Find Or Create lockscreen.password_type, double-click & change it's value to 65536, Apply changes!
Now, find lock_pattern_autolock, Delete Record, If doesn't exist, Ignore
Close & save database
Run push settings.db.cmd and reboot your phone
Instruction To Remove Password Lock:
Now, find lockscreen.password_salt, Delete Record
Now, find lockscreen.password_type, Delete Record
Close & save database
Run push settings.db.cmd and reboot your phone
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
METHOD 7
Solution For Everyone With Recovery Installed :
INSTRUCTIONS:
1.Download and Copy Aroma File manager.zip (Download from attachments or http://forum.xda-developers.com/show....php?t=1646108) to your memory card.
2. Open your recovery (press volume Down + Power button or it can be different according to the phones. Generally the phones who have press able button on the middle they have to press all three buttons. Google for you pattern there are lots)
3. There’ll b an option in recovery called “mount”. Go in that option and then mount all the cache and everything it is there.
4. Then select “update” and select “apply update from SD/external” and select aroma file manger.zip file that you downloaded using above QR code above.
5. After Flashing or updating, the aroma file manger will open. Use volume keys for up/down and power button 2 select like you use to get into recovery.
6. In aroma File manager , Go to menu , which is located in bottom strip and then select Settings.
7. Go to bottom n select “mount all partition in startup ” then exit from aroma file manger.
8. Now after exit , re-update that aroma file again and it will open again.
9. Go to data >> and then System.
Then find ‘gesture.key’ (for pattern lock) and ’password.key’ (for password lock) then long touch on gesture.key or password.key and sum option will be prompted , choose delete and delete that file and restart.
Try out one by one
Tell if works on another phonephone
Pattern Disabler zip
http://forum.xda-developers.com/attachment.php?attachmentid=2532214&d=1390399283
SMS bypass app:
http://forum.xda-developers.com/attachment.php?attachmentid=2532215&d=1390399283
Bypass securities mods:
http://forum.xda-developers.com/attachment.php?attachmentid=2532216&d=1390399283
Aroma file manager :
http://forum.xda-developers.com/attachment.php?attachmentid=2532253&d=1390400421
Thank you must say other wise experience BOOTLOOP.
Click to expand...
Click to collapse
Rahulraj943472 said:
Thanks mate you give all working method for unlock is there
Click to expand...
Click to collapse
bro plz hit thanks button

Disable AT&T apps on your Samsung SM-N920A by the maker of bricked droids

*** New Tool Added: 04-06-2017 ***​Warning: 'extremely powerful and dangerous tool'
This tool is designed to execute commands as root + system_server && install_recovery. While this example shows how to disable packages please be aware that a typo will be executed on the system as a command.
General Notice:
This package disabler is Android 6.01 64 bit and it isn't Samsung specific.
This tool is currently limited to only two contexts and therefore may not currently be able to disable "some??" packages.. Please let me know if that is true and I will attempt to find the correct context to disable the problem package.
Please note
This tool is part of a root kit I'm designing but since it's purpose was never a package disabler it isn't likely to receive updates. If you have an issue and you're waiting for a correction it's gonna be some wait unless you pm me. (i'm trying to learn forums, best thing to do is PM me to make me aware of your post here)
Information Updates:
You can disable every AT&T app on the device for a net gain on battery performance for your device. But if you disable some of the security logging and Android proper packages you will start seeing a net loss on batter performance. I was at < 1% over night before I got crazy.. Now I'm back to 6% battery lost in 6 to 8 hours of screen off time.
(obviously a tool that can disable a package can enable it also so keep careful track of your cmd_list.txt files)
Instructions
Don't brick your phone... just kidding see in depth instructions on my github
sources, no binaries
April 12 2017 sources have been majorly overhauled, binaries are beta beta.. however, package disabling power not increased
--Android 5.11 r2 64-bit binary toolbox and applypatch 'till' now added. ubuntu + ndk needed to make run5
https://github.com/droidvoider/CVE-2016-5195_GreyhatRootProject_Root_Console
BINARIES - NO SOURCES -instructions for disabling packages are in the zips
Linux
https://drive.google.com/open?id=0B-fnF5v-xg6OYmdreVNJOGlLWUE
Windows (i didn't test that batch file.. edit the batch file it's just a "batch" of commands)
https://drive.google.com/open?id=0B-fnF5v-xg6OYmdreVNJOGlLWUE
Scope:
dirtycow 5195 is patched November 2016.. If you are running Android 6.01 you may be able to flash the October 2016 kernel to your phone to bypass the patch
1. First make sure you have the AP file from your firmware.. (specifically boot.img and recovery.img which are included in the AP file)
2. Backup your device.
3. Use Odin to flash PJ1 boot.img / recovery.img to your phone
https://drive.google.com/open?id=0B-fnF5v-xg6OR1VWRTItWFVOTVE
4. Constantly check your phone, if it is getting hot or losing a lot of battery fast you need to stop... restore it and forget this
5. as long as it's all good see the instructions included with the tool
OLD PROCESS BELOW
************************************************************ UPDATE: 02/21/2017 ************************************************************************
This exploit is powerful and from what I can tell you don't need to use adb at all to make it work. Create an archive of the app with your tool, I listed what I used below. Install from archive. "app crashes". There are 3 updaters that I kill: com.sec.fwservice + com.sec.android.soagent + com.ws.dm. Any apps I can disable in App Manger I disable normally instead. For example if you begin disabling Google play it will allow you to fully disable it. This was the biggest thing that made my batter life better. You can use the adb commands, script and etc also if you want to do anything and everything to avoid additional updates. Hopefully I'm right because I am done with updating.
**** Warning **** Disabling the wrong thing this way can cause the phone to crash so hard you need to flash firmware to restore it. Make sure you have backed up and that you have your firmware ready. Also be warned that in my experience devices can suddenly crash & need repair from doing this type of stuff!!
tESted on firmware N920AUCS4CPK1 Android 6.01 w/Nov. Sec. Patch
Overview of the process
Our goal is to completely remove most AT&T from the application manager list and have AT&T software show up as a regular app, not a hidden system app. I am unsure if we need to have a fresh flash and how far you need to go in order to achieve our intended goal. I am fairly confident we need only change system settings to off for AT&T + Knox that and then fire this script. If that is not enough please see page two. I would very much appreciate feedback so I can edit this.
===> REMINDER <===
Backup all your contacts, text messages, downloaded files and also individually back any apps there are important to you. Also have a look at your /sdcard/ to see what's there. Do a full backup on the entire phone just in case you forgot anything.
*** Prepare to have to flash/wipe data to get this to work as I've only truly tested this after a recent flash personally!!! ***
This walk through utilizes the following technologies you will need to Google
You need the platform-tools from Android Studio SDK it comes with adb. (You can probably google platform-tools directory and download it)
(path environment needs to be set in the script or just fully qualify the location of adb which is what I do) <change to match your path>
I assume you understand how to download a file, open command prompt, cd to the directory it's download to and edit the path to your platform-tools inside the batch file
I also assume you can figure out the Samsung USB driver for Windows and test that you can adb shell to your device.
I assume you can get into Download mode and flash your firmware with Odin / Windows using a usb cable.
Steps to brick your perfectly good working AT&T Note 5 phone
Denial of permission and general rearrangement of system apps Version .0008 beta
Fresh after a flash please block the signal on your phone if possible. I always block signal!!!
1.) Turn on developer options then confirm that you have OEM unlock on(like it matters), USB Debugging On and default Verify Apps via USB remains off
2) Kill all AT&T running processes DEVELOPER OPTIONS | RUNNING SERVICES (get Smart Limits, Protect app, ATT yahoo mail, anything ATT)
every opportunity)
2A) Package disabler is awesome leave it running if you have it we don't need anything special for adb, besides adb.
3) Plug your phone into your PC via usb and get it connected.. (adb devices "unauthorized means you didn't say ok on phone in time unplug/replug try again")
3a) adb shell should log you into the phone and exit should get you back out (we don't want to be in the shell just testing the connection)
4.)Turn off "can make system changes" for AT&T apps. Application Manger | More | Change System Settings | More | Show System Apps -- Turn off anything AT&T (I also kill anything I can knox, samsung)
5) Fire this script on your phone (obviously you will have it connected to your pc, allowed the connection on your phone screen)
Basic commands I'm using, I prioritize com.ws.dm and then I run the commands on the rest of AT&T:
<This small snippet is a linux bash shell while the attached script is a Windows example>
#NOTE TO LINUX USERS: take the rest of the script from the windows batch and convert it to bash
#!/bin/bash
/opt/Android/Sdk/platform-tools/adb devices
/opt/Android/Sdk/platform-tools/adb wait-for-device
/opt/Android/Sdk/platform-tools/adb shell am kill-all
/opt/Android/Sdk/platform-tools/adb shell pm clear com.ws.dm
/opt/Android/Sdk/platform-tools/adb shell pm reset-permissions com.ws.dm
/opt/Android/Sdk/platform-tools/adb shell am set-inactive com.ws.dm true
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.CHANGE_CONFIGURATION
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.WRITE_SECURE_SETTINGS
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.BATTERY_STATS
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.INTERACT_ACROSS_USERS
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.SET_PROCESS_LIMIT
/opt/Android/Sdk/platform-tools/adb shell am kill-all
/opt/Android/Sdk/platform-tools/adb shell am kill com.ws.dm
/opt/Android/Sdk/platform-tools/adb shell pm clear com.ws.dm
Note: I always did this right after a flash so I'm hoping that's not necessary
(I know I misused reset-permissions but it accepts it, laugh)
In the attached photo notice that I can "Show" system apps but AT&T Software Update is already shown (i.e. not a system app) For me I have no other att apps even if I show system apps!, they're installed tho)

**** Warning **** Disabling the wrong thing this way can cause the phone to crash so hard you need to flash firmware to restore it. Make sure you have backed up and that you have your firmware ready. Also be warned that in my experience devices can suddenly crash & need repair from doing this type of stuff!!
Stern Warning: You need your current matching firmware before doing this!! You can make a copy of your own firmware following directions on this forum. The info about your firmware is in SYSTEM | ABOUT
tESted on firmware N920AUCS4CPK1 Android 6.01 w/Nov. Sec. Patch
Overview of the process
We are going to do a various pronged assault using App Archiving / Restoring with a Google Play app as well as attacking a select set of permissions as well as clearing app data through adb using a batch or shell script from your computer. In some case I am able to also install the apk using adb shell pm install -rts which tags it as a test package. But I'm unclear how I achieved that so this is a work in progress.
(For the install -rts trick this is only after freshly flashing so it's been a little hard to remember to test it. Let me know if you stuble upon the process order again)
===> REMINDER <===
Backup all your contacts, text messages, downloaded files and also individually back any apps there are important to you. Also have a look at your /sdcard/ to see what's there. Do a full backup on the entire phone just in case you forgot anything.
*** Prepare to have to flash/wipe data to get this to work as I've only truly tested this after a recent flash personally!!! ***
This walk through utilizes the following technologies you will need to Google
You need the platform-tools from Android Studio SDK it comes with adb. (You can probably google platform-tools directory and download it)
(path environment needs to be set in the script or just fully qualify the location of adb which is what I do) <change to match your path>
I assume you understand how to download a file, open command prompt, cd to the directory it's download to and edit the path to your platform-tools inside the batch file
I also assume you can figure out the Samsung USB driver for Windows and test that you can adb shell to your device.
I assume you can get into Download mode and flash your firmware with Odin / Windows using a usb cable.
Steps to brick your perfectly good working AT&T Note 5 phone
Denial of permission and general rearrangement of system apps Version .0008 beta
Fresh after a flash please block the signal on your phone if possible. I always block signal!!!
1.) Turn on developer options then confirm that you have OEM unlock on(like it matters), USB Debugging On and default Verify Apps via USB remains off
2) Kill all AT&T running processes DEVELOPER OPTIONS | RUNNING SERVICES (get Smart Limits, Protect app, ATT yahoo mail, anything ATT)
every opportunity)
2A) Package disabler is awesome leave it running if you have it we don't need anything special for adb, besides adb.
3) Plug your phone into your PC via usb and get it connected.. (adb devices "unauthorized means you didn't say ok on phone in time unplug/replug try again")
3a) adb shell should log you into the phone and exit should get you back out (we don't want to be in the shell just testing the connection)
4.)Turn off "can make system changes" for AT&T apps. Application Manger | More | Change System Settings | More | Show System Apps -- Turn off anything AT&T (I also kill anything I can knox, samsung)
5) Backup/Restore the AT&T apps from a "backup tool", I used System App 2 let us know if others work "or excel".
Use an app archive tool such as System Panel 2 | apps | Archive to archive the AT&T apps then install them from that archive. You can do this to any you see!
(don't uninstall the app but feel free to install it repeatedly. e.g. install = uninstall as system app but uninstall = reinstall as system app
5 a) --- if doing step 8 you need a the com.ws.dm.apk copied to your computer so you can fire the install -rts on it
6) Repeat step 4
7) Fire the script from the first post on your phone (obviously you will have it connected to your pc, allowed the connection on your phone screen)
Basic commands I'm using, I prioritize com.ws.dm and then I run the commands on the rest of AT&T: (While it's running install/uninstall with the archive tool)
<This small snippet is a linux bash shell while the attached script is a Windows example
#NOTE TO LINUX USERS: take the rest of the script from the windows batch i think if you use linux you don't need step by step
#!/bin/bash
/opt/Android/Sdk/platform-tools/adb devices
/opt/Android/Sdk/platform-tools/adb wait-for-device
/opt/Android/Sdk/platform-tools/adb shell am kill-all
/opt/Android/Sdk/platform-tools/adb shell pm clear com.ws.dm
/opt/Android/Sdk/platform-tools/adb shell pm reset-permissions com.ws.dm
/opt/Android/Sdk/platform-tools/adb shell am set-inactive com.ws.dm true
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.CHANGE_CONFIGURATION
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.WRITE_SECURE_SETTINGS
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.BATTERY_STATS
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.INTERACT_ACROSS_USERS
/opt/Android/Sdk/platform-tools/adb shell pm revoke com.ws.dm android.permission.SET_PROCESS_LIMIT
/opt/Android/Sdk/platform-tools/adb shell am kill-all
/opt/Android/Sdk/platform-tools/adb shell am kill com.ws.dm
/opt/Android/Sdk/platform-tools/adb shell pm clear com.ws.dm
Note: I always did this right after a flash so I'm hoping that's not necessary
(I know I misused reset-permissions but it accepts it and I like it that way. Don't end process through your app archive tool it wakes up com.ws.dm)
Steps that may not work quite yet:
Note) I need to add to the how to for this to not say Invalid_URI bla bla but the way I do it is by flashing an invalid modem file, that's not acceptable since I don't think it's necessary yet:
8) issue the command adb shell pm install -rts com.ws.dm.apk.
8 a) refire the above snippet that is just an example for linux it is my knock out punch for after, but this step should fail if you make it work let me know please

**** Warning **** Disabling the wrong thing this way can cause the phone to crash so hard you need to flash firmware to restore it. Make sure you have backed up and that you have your firmware ready. Also be warned that in my experience devices can suddenly crash & need repair from doing this type of stuff!!
************************************************************ UPDATE: 02/21/2017 ************************************************************************
This exploit is powerful and from what I can tell you don't need to use adb at all to make it work. Create an archive of the app with your tool, I listed what I used above. Install from archive. "app crashes". There are 3 updaters that I kill: com.sec.fwservice + com.sec.android.soagent + com.ws.dm. Any apps I can disable in App Manger I disable normally instead. For example if you begin disabling Google play it will allow you to fully disable it. This was the biggest thing that made my batter life better. You can use the adb commands, script and etc also if you want to do anything and everything to avoid additional updates. Hopefully I'm right because I am done with updating.
Notice: 02-15-2017
It's reversible if you didn't realize this (tested in PK1 by me and one other). If you used the subtle approach just go into your backup app then uninstall. Only the extra installation is removed then the app will heal itself. If you used harsh method adb shell pm uninstall com.ws.dm = att updater. (do for all apps you miss dearly)
Package Disabler not working? OOPS, KLMSAgent is necessary use the above method to reverse our actions on com.samsung.klmsagent
Attached photos show that the AT&T Software updater is gone. I achieved that with a harsher script if I am going to release this method I want a more assured way then wrong modem file and 8 windows open at once.

I have to ask, if you see a snippet representing an efuse in the code, why not remove it and all references to it? If possible to do so, you'd be the first to crack an AT&T (and this would likely work for Verizon as well) GN5?
Edit - Also, the January sec. patch is beginning to roll out to users. I just got it today and I am usually behind most.

Update 02/21/2017 regarding efuse. I'v studied the binaries and processes hard and it is my belief the efuse will never trip if you aren't altering files on the system. We aren't doing that here and after weeks of testing my bit is still 0x0
**** Warning **** Disabling the wrong thing this way can cause the phone to crash so hard you need to flash firmware to restore it. Make sure you have backed up and that you have your firmware ready. Also be warned that in my experience devices can suddenly crash & need repair from doing this type of stuff!!
ajaxburger said:
I have to ask, if you see a snippet representing an efuse in the code, why not remove it and all references to it? If possible to do so, you'd be the first to crack an AT&T (and this would likely work for Verizon as well) GN5?
Edit - Also, the January sec. patch is beginning to roll out to users. I just got it today and I am usually behind most.
Click to expand...
Click to collapse
It's in the bootloader and they are friggin smart programmers and I am not that smart, yet. Probably ever.
I know you guys are on later firmware than me by now but I had to get off the marry go round at PK1. I had listed a work around to taking updates in Novemember but it was iffy at best. This is the first almost safe way I found, and now it's too late. That's the problem with the Note 5 we can't get back to a common point so we can all work toward freedom together.
edit: removed idea about flashing cm.bin, it's almost killing download mode.. we need to swim away little fishes

There is a new tool for disabling apps I posted on the first post

[Guide] Getting the Most out of your S20FE

Here's a guide to help you make the most out of your phone
Guides below can be followed by both rooted and unrooted users
Debloat list: https://paste.rs/OLC
Debloating guide:
1) Download Google platform-tools (ADB and fastboot) from here for the operating system you are using on your computer, I will be using Windows for this guide, and extract the zip file to the root directory of your drive in its own folder (For example, C:\platform-tools, inside of the platform-tools folder you should see ADB and fastboot executables as well as other files).
2) On Windows, download and install the Samsung USB Drivers from here, I don't believe other OSes have to do this.
3) On your phone, go to Settings > About phone > Software information and tap Build number 7 or 8 times until you get a pop-up notification saying "Developer options have been enabled."
4) Go back out to the main Settings menu where you will notice a new option called "Developer options". Tap it and scroll down a little bit until you find USB Debugging, turn this option on and keep your phone unlocked (don't turn off the screen).
5) Plug your phone into your computer and open Command Prompt or Terminal and type cd C:\platform-tools and press Enter (Command will differ for the OS you're using).
6) Type ADB devices, give it a few moments, and check your phone for an ADB connection authorization prompt, check the box that says "always allow..." so you don't have to do this every time you want to use ADB.
7) Type ADB shell, the prompt should change from "C:\platform-tools\>" to something like "<phoneserialnumber>:/"
8) Either highlight all of these commands and paste them into the Command Prompt by right-clicking or highlight one command at a time and paste them in one by one
*************************************
Apps:
1)Naptime(Better Battery Life)
2)Galaxy Max HZ(Helps you change the refresh rate of your phone's display)
------------------------------------------------------------------------------------------------------------------------------------------
For rooted/Unlocked Devices only:
Twrp for Exynos
Kernel for Exynos
Remove Bootloader Warning(Exynos only)
Twrp for Snapdragon
Kernel for Snapdragon
*************************************
Magisk Modules:
Nuked Script: This module includes some scripts that will disable some services on all the apps on your device in order to avoid substantial wake-lock battery drain because your apps send some useless usage and information to GOOGLE and this amazing module will stop that.
Download
SAMSUNG GENERAL PATCHER: This Lets you use most Samsung apps on rooted devices
Download
Universal GMS Doze: Optimizes Google Play services.
Download
Safetynet-fix: fixes the SafetyNet.Install riru and enable magisk hide before installing this module
Download
NFS-Injector: This module aims to improve kernel/ram management between efficiency and energy-aware. Using a complex algorithm, determine the most optimal settings between battery and performance for your device.
Download
Telegram Group link if you need help: http://t.me/S20FeModding