Database Info

Android Rooting (Simplified)

Hello everyone!
I know some of you are still roaming around here and there trying to root your phone; others wanting to root the phone without knowing what rooting is...
Wandering if it's illegal or not; and why should they be Rooting their Devices.
Well that's why i've done this tutorial with a lot of help from different sources.
It has been almost 2 days reading; reading; reading; and writing this tutorial to simplify and compact information scattered around this forum and the web.
Knowing the Basics
In order to explain everyone (specially noobs / starters); please follow this link.
(I advise you to open it in a "new Tab" or "Window"; so you don't loose yourself)
One thing before starting:
I found out that it is important to reboot the device and the PC after installing and Updating the following apps: "Super one Click" and SDK with your firmware version API's.
Some errors that occur during the Rooting with the "Super One Click" happen due to some kind of need to reboot of the machine and device.
As mentioned in Step #9
[...]
Now that you understand what rooting is; let's ROOT your Android.
P.S - As you already know; you are responsible for doing this process; or for anything that goes wrong.
“Rooting Your Android Phone”
Requirements:
Download: "android-sdk_r15" or Later Version.
After Downloading and Installing SDK; download the API's according to your Firmware Version.
(Check Step #1 and #12 of the Easy Rooting Method)
Download: "Super One Click Program"
(Link Goes to XDA Developers "Super one Click Program" Thread)
Download: "Java SE Development Kit 7" (or later)
I. (Easy Method - Using “One Click Rooting Program”)
Note: This method works for almost every Android phone.
1) Take a note of you brand model and android Firmware/ROM installed on you device.
(You need to know the version of your O.S to download your SDK API's later)
i.e:
“Model: Acer C4 Liquid Mini (E310)”
“O.S: Android Froyo v2.2”
2) Download/Install your Android Drivers. (PC)
3) Download/Install your Android SDK/ADB. (PC)
4) Open SDK (as Administrator) and mark the following things to download:
- “Tools” (Select the entire Folder)
- “Your Firmware/ROM Version Installed” (i.e: “Android 2.2 API”) (Select the entire Folder)
5) Now press “Install Packages” (The download will start; follow the next step after it’s completed)
6) Download / Install the Latest version of the rooting program (Super One Click Rooting Program); unzip it and install it on your computer.
7) Make sure that your phone has the "USB Debugging Mode" ON.
NOTE: To turn it on go to your device and press: “Menu” > “Settings” (Icon) > “Applications” > “Debug / Development” > “USB Debug”
8) Make sure you turn Off your Device and Remove the SD Card. It must be done without the SD Card.
9) Safely disconnect your Phone from the PC; and restart. (PC and Device)
10) When your Phone and Windows are ready; connect your phone to the PC.
Note: Just plug the cable. Do NOT select any option in the Phone.
Also you will notice that a small Android Icon will appear at the top left of the screen.
That means that you phone is prepared for debugging Mode.
11) Once again make sure that your phone has the "USB Debugging Mode" ON.
12) Run SDK/ADB as Administrator.
(Windows XP Users just double click to open)
13) Right Click the “Super One Click Rooting Program” and open it as Administrator.
(Or just double click; if you are using Windows XP)
14) Press "Update Check"; just to make sure you have the latest files. (Don't worry with the app version error; if it happens means you just downloaded it/you have the latest version)
14) Click the "Root" button and wait it to finish. (There should be no errors)
15) Once done; you should see “Superuser” permission in your phone’s apps.
Note: If so; your Device is Rooted. Congratulations!
II. (Advanced Method - Manually Rooting)
Pre-requisites
There are a few things that you need to have before you start rooting.
Obviously, you will need an Android device with Android 1.5 or higher and a USB cable to connect it to your computer.
You will also need to have some files for this:
SuperOneClick.zip and the Android SDK/ADB up and running on your computer.
(Run as Administrator if not using Windows XP)
If you are unfamiliar with ADB, GoodAndEvo site has an awesome ADB tutorial that should get you up to speed.
(Note that the tutorial in the Good and Evo Page is for HTC Devices)
First, we need to move some files around to make running commands a bit easier.
Unzip the SuperOneClick.zip and copy the following files: su-v3, busybox, Superuser.apk, psneuter, and GingerBreak; to the Android “ADB Platform-Tools folder”; which is contained in the Android SDK folder on your computer.
i.e: C:\Program Files\Android\Android-SDK\Platform-Tools\
These files can be found in the following SuperOneClickv2.1.1-ShortFuse folders:
- “Busybox” -> “Dependencies” folder
- “psneuter” -> “Exploit” folder
- “GingerBreak” -> “Exploits” folder
- “SuperUser.apk” -> “Root” folder
- “SU-V3” -> “Root” folder
Once copied rename “su-v3” to “su”.
If you are on Windows, you will also need to have proper drivers for your phone installed.
These can usually be found by going either to the manufacturer website or searching for the name of your phone and the word "Drivers."
Once you find drivers, download and install them like any other application.
Rooting your device
Now that you have ADB setup and the proper exploit files, you are finally ready to Root.
Before you start running commands, you need to put your phone in "USB Debugging" mode.
(Menu > Settings > Applications > Development > Enable USB Debugging) and connect the device to your computer.
Note: Just plug the cable and do not select any option in you device.
Now, open command prompt to run some commands.
Windows Vista/7 Users:
(Press "Windows Key" > Type: "CMD" > Right Click on "CMD" and Run it as Administrator)
In Linux, open whichever terminal emulator suits you. Once you have a command prompt, you need to enter your platform-tools folder, also called a directory.
You can use the "CD" or Change Directory command to accomplish this.
If your SDK folder is called "android-sdk" the command should look like this: cd android-sdk_r11-windows/platform-tools.
This command will leave you with a shell prompt in the platform-tools directory.
From here, you can run the commands that will actually root your phone.
Be sure to run these commands exactly as they are written.
The commands with an "$" or "#" will only run after the "adb shell" command.
First, here are the commands that run the” psneuter” exploit and gain a root shell.
Type them in the following order.
…Yes after the ADB and the “$” there is a “Space”.
• adb devices
• adb push psneuter /data/local/tmp
• adb shell
• $ cd /data/local/tmp
• $ chmod 777 psneuter
• $ ./psneuter
At this point, the exploit will run and close the shell.
You will need to run these commands to restart the ADB server.
• adb kill-server
• adb devices
Now comes the moment of truth.
Type:
• adb shell
...command to open a shell.
If you see a "#" sign, you have root access, so go ahead and continue to the next part of this tutorial.
If not, you can go back and try the previous steps again, or ask for help in the comments.
We now need to make this root permanent.
From the root shell you just opened, type the following commands.
• # mount -o remount,rw -t rfs /dev/block/st19 /system
• # exit
• adb push busybox /system/bin
• adb push su /system/bin
• adb install Superuser.apk
• adb shell
• # chmod 4755 /system/bin/busybox
• # chmod 4755 /system/bin/su
• # mount -o remount,ro -t rfs /dev/block/st19 /system
• # exit
• adb reboot
At this point, your device should reboot.
You can check for the Superuser icon in the app drawer, and then try a root only app like Titanium Backup.
If that app works, congratulations!
You have successfully rooted your Android device.
Prepare to enjoy all the benefits of root.
If you are having trouble with this tutorial or want to offer others a tip, please leave a comment.
Me or every XDA developer/user shall gladly help you out clarifying any error message or issue. (at least if i know how i will help)
Just make sure you did exactly as described; and only then post your question / expose your issue(s).
P.S
- Use “Code” Tags to report Logs.
- Remember to "Thank" if this tutorial helped you or if you find it usefull.
Special thanks to:
XDA Developers (Users & Staff)
Pocketables.net (Aaron Orquia)
CLShortFuse (For bringing such Great App)

I can´t do this with method #1 (freeze on step #6)
In method #2 ....
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ ./psneuter
./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
$
Some help?
Regards

niki40 said:
I can´t do this with method #1 (freeze on step #6)
In method #2 ....
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ ./psneuter
./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
$
Some help?
Regards
Click to expand...
Click to collapse
Greetings;
What's your device Make and Model?
Try/Check the following:
- Download the "Super One Click Program" Again. Since there is a new Fix for it.
Follow this Link to download and get more detailled info:
http://forum.xda-developers.com/showthread.php?t=803682
- Check that you have the USB Debug Turned ON (in your device)
---> List > Settings > Applicatons > Development > USB Debugging
- Check what version do you have in your device; and verify that SDK Manager has downloaded your Version API's; and Tools folder. (Look at status tab; it should say installed)
- Did you Restart the machine after the install of Super One Click and SDK Manager? (Only then Root the Device)
- In a Last case there's a small percentage that your phone isn't compatible with "Super One Click".

Thanx a lot bro

You Can Add This To The OP If You Want .
Press Thank If I Help .
For Sony Ericsson Xperia Only .
I Use A Sony Ericsson Xperia X10 And It Work Well .
The File Name Is Call Flash Tool .
The Fuction It Has Is ( Latest 4.2 )
Root
Flash Kernel
Flash Rom
One Click Unlocked Bootloader .
Click to expand...
Click to collapse
Thing You Need To Do Is :
Download The Two File .
Install In The Same Place .
Open The File .
Open Driver Folder .
Install The Driver .
And Open Flash Tool exe .
See If The Computer Detect Your Phone .
USB Debugging Must On .
Click to expand...
Click to collapse
Thing Your Need ( For Rooting Only ) :
https://github.com/Androxyde/Flashtool/downloads
==================================================
Unlocked Bootloader Try At Your Own Risk . Sony Ericsson Xperia X10 Success ) :
Only For Sony Ericsson Xperia Phone .
Download Generic version 2.3.3 build 3.0.1.G.0.75 ( http://www.multiupload.com/564T6TLUD8 )
Download DoomLoard Boot Manager . ( http://doomlord.sylvester20007.com/...tmanager/X10_2.3.3_Stock-BootManager-v1.3.ftf )
Put This Two File In Flash Tool Frimware Folder .
Open Flash Tool .
Press Flash .
Select All The File Inside .
Reboot Your Phone .
Root Your Phone .
And Install DoomLoard Boot Manager .
You Can Now Install Unlocked Bootloader Rom .
Click to expand...
Click to collapse
If Anyone Know Anything And Notice I Say Wrong Here Please Private Message Me Or Comment Here To Tell Me
Special Thank To :
Every One That Teach Me Last Time .
Androxyde For Flash Tool . http://forum.xda-developers.com/showthread.php?t=920746
DooMLoRD For DoomLoard Kernel And Boot Manager . http://forum.xda-developers.com/showthread.php?t=1278318
Every Body Who Click Thank .
Every Body Who Read .
Click to expand...
Click to collapse
==================================================
Do It At Your Own Risk . Press Thank If I Help
And Yes It Work For New Xperia ( 2011 Lines )

nice share...but i already rooted my xperia

[How to][GUIDE] Bypass and Disable Password on lockscreen

Hello, as the title states I have found a way to bypass the password with the pin, pattern, and password option on the lockscreen without doing a factory data reset. I have not tried face unlock, I will try it soon. I would first like to thank Kosborn for his p2p-adb which bothe helped and gave me the idea. His p2p-adb can be located here.​
I will also be adding this feature to Kosborn's p2p-adb soon as well.
Now to get down to it.
What you will need:
Phone with eithier 'USB Debugging" enabled or a Custom Recovery
ADB
A file editor (I use Notepad++)
Basic adb skills
*If you already have "USB Debugging enabled please skip to Step 5*​
Step 1)
If the phone does not have USB Debugging enabled you need to flash a custom recovery to the phone. I will not post a step to step guide to on how to flash a custom recovery, just google it.
Step 2)
When you have the custom recovery flashed to the phone boot into recovery mode and mount /system. In CWM it can be found under "Mounts and Storage"
Step 3)
When /system is mounted pull build.prop and open it with the file editor I mentioned above.
Code:
adb pull /system/build.prop
You will have to add one line into the build.prop file for adb to be enabled when you reboot the phone
Add the line below to the build.prop file.
Code:
persist.service.adb.enable=1
Save build.prop file.
Now we have to push the file back to the phone so
Code:
adb push build.prop /system/build.prop
adb shell chmod 0644 /system/build.prop
Step 4)
Reboot phone
Run command below and you should see you device attached, If not make sure you have the correct drivers installed.
Code:
adb devices
Step 5)
Using adb type the following commands
Code:
adb shell mv /data/system/gesture.key /data/system/gesture.key.bak
adb shell mv /data/system/password.key /data/system/password.key.bak
Step 6)
Reboot phone
You should now be able to unlock your phone without having any password. And more importantly with having all of your data on the phone still.
If you found this helpful please hit the thanks button.

RESERVED

So this will work on any device correct?
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
With either pin lock or pattern?

prairiedogn said:
So this will work on any device correct?
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
With either pin lock or pattern?
Click to expand...
Click to collapse
In theory yes. I can't be for sure. It won't hurt it

When I had to use I typed "adb shell rm /data/system/gesture.key", not "adb shell mv /data/system/gesture.key" and that worked well.

eduds said:
When I had to use I typed "adb shell rm /data/system/gesture.key", not "adb shell mv /data/system/gesture.key" and that worked well.
Click to expand...
Click to collapse
That will work as well the reason why I used adb shell mv /data/system/gesture.key is to keep the file there when i was testing just incase but it could be removed as well.

not trying to be too much of a smart-butt, but heres the full version to do it, what u did is the basic commands, but leaves an empty pin/pattern for ANY input will be correct, heres each command (new line=new command):
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update secure set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
update secure set value=0 where name='lockscreen.lockedoutpermanently';
.quit
busybox rm /data/system/gesture.key
busybox rm /data/system/cm-gesture.key
busybox rm /data/system/password.key
busybox rm /data/system/cm-password.key
busybox rm /data/system/locksettings.db
busybox rm /data/system/locksettings.db-wal
busybox rm /data/system/locksettings.db-shm
reboot
some kernels+file-systems(or user actions) convert databases to "wal", or "shm" so they will have different names, as for some newer CM-based rom builds, the pattern, gesture unlock (if implemented), and sometimes pin get put into a different file "cm-***.key" but pin+password goes into "cm-password.key";
u need to only do first two commands(adb shell, and the cd), then skip to after the .quit if u ARE NOT locked out, if u are u need to do ALL these commands, and if it says "file/directory not found" or simmalier errors when doing the "gesture.key","cm-gesture.key","cm-password.key", the "locksettings.db-wal" +"locksettings.db-wal"; just ignore those errors as u dont have the configurations stored in there like some other custom roms do =)
i found and compiled this list from my app i made, if u heard about it "SMS Tasks", and this is acually the exact code (in adb shell form, not in java command line with added characters, voids, etc...) to unlock the phone remotely =), idk why people tell me not to share this code, as its good for users to have so they dont lose their data incase of forgotten passwords on devices stored in their dressers/storages for ages and got out for whatever reason (maybee a new rom-tree was born for it and u want to see it in action, idk =S) but use this if u want, if not u can ignore this post, just wanted to share this with u incase u want to add some to the OP as the commands u do some roms might not fully unlock (it will erase pass/pin, but some roms keep the config that its still set, but any pass (even one characters+a single_space, or one-three dot patterns), so if anyone got those errors, or want more understanding on what files are used, this is my most resent list of things to delete by what i see used on rom developer's github's anyways =S
but hope this helps any of u in any ways =)

much simpler way
download aroma file manager from
http://forum.xda-developers.com/showthread.php?t=1646108
flash aroma file manager in cwm with system mounted
browse to data/system
delete gestures.key
delete password.key
restart
of course you will need aroma file manager on the root of your sd card so download it and put it there now for safe keeping
you can always put it there via a card reader or pop your sd card into another phone if your phone is already locked

Using Aroma File Manager would be the easiest way!
Thanks for the share Marcussmith2626!

There is a way to do this without USB Debugging enabled nor Custom Recovery installed, as long as stock Android system recovery <3e> "backup user data" option is working:
- create a backup
- modify the backup file
- root the phone
- restore backup
root is not required for backup, but for restore. i prefer restore from custom recovery. but i have done this without flashing, too.
please see this link
Android system recovery <3e> alternative restoring program

i know this is an old thread, but im trying to bypass the screen where it says that youve tried your pattern too many times on a zte z932l (also known as the rapido) for a friends sister. She really just wants the pictures that are stored on the internal memory is all because they are of her kids. Any ideas on how to get this done? I would up on this thread because i was hoping that usb debugging had been enabled, but it hasnt

no "backup user data" option in Android system recovery <3e> i guess? if you can't create a backup then my friend, this is the hardest case for unlocking... if playstore is working and wifi enabled, you can unlock using Android Device Manager first. if this not help, check if fastboot is working. you can boot custom recovery with "fastboot boot recovery.img" if no fastboot mode available, find any way to make a backup of usrdata partition (maybe in download mode?) once you have a backup, its easy to modify and restore (as long as FRP lock is disabled)

with usb debugging enabler you can modify a rom and flash it via odin (without losing data???), and with Android Multi Tools you can unlock the screen. if this is possible for samsung devices, then there should be a way for other phones, too. another way is to enable adb via sideload, if someone will create such app.
and of course, if fastboot mode is available, the easiest way is booting a custom recovery without flashing it. then just delete /data/system/locksettings.db* files from adb or with aroma file manager (try calung version 1.80)

Remove all themes via ADB? Installed 8.1 Dev Preview without disabling themes first!

I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!

s1dest3pnate said:
I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!
Click to expand...
Click to collapse
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk

Acid0057 said:
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!

s1dest3pnate said:
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!
Click to expand...
Click to collapse
Awesome!
Sent from my Pixel XL using Tapatalk

I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery

GBpfan95 said:
I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery
Click to expand...
Click to collapse
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.

s1dest3pnate said:
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.
Click to expand...
Click to collapse
Does that work even if I am locked and not rooted?

GBpfan95 said:
Does that work even if I am locked and not rooted?
Click to expand...
Click to collapse
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.

I just ended up factory resetting. Most of everything is backed up anyway. Definitely learned my lesson

Could you please post the SubstratumRescue.zip? I cannot get to the directory on my phone via ADB and want to try running the script commands manually.
EDIT: Nevermind, I tracked it down on the dev's AFH page.

I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,

AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks

pR0wl3r said:
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks
Click to expand...
Click to collapse
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...

jeremywh7 said:
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...
Click to expand...
Click to collapse
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?

bobby janow said:
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?
Click to expand...
Click to collapse
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.

jeremywh7 said:
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.
Click to expand...
Click to collapse
Yeah still shows an x.
Sent from my Pixel using XDA-Developers Legacy app

Thanks!
AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Thanks so much mate this worked for me perfectly!

This can be done in a less manual fashion. It looks like many of you are on Windows, but I'm sure theres a way to accomplish something similar. I'm on Linux and this is how I did it.
Code:
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 echo cmd overlay disable
cmd overlay disable com.samsung.android.app.aodservice.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.smartmirroring.StatusBarIconsforSamsungextras
cmd overlay disable android.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.app.smartcapture.StatusBarIconsforSamsungextras
cmd overlay disable com.android.settings.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.lool.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.navbars.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.tiles.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.statusbars.StatusBarIconsforSamsungextras
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 adb shell cmd overlay disable
For reference, ag is very similar to grep. So the explanation is adb shell allows you to pass a command to it so it can run that command immediately. So adb shell cmd overlay list is the same as typing adb shell followed by cmd overlay list except it prints the output and immediately exits. So I take that output, grep (using ag in this case) for the enabled overlays and then programmatically disable them. xargs -n 1 says take at most one of the arguments passed to this command and append it to the rest of the line. So this calls adb shell cmd overlay disable __insert-overlay-here__ repeatedly.

I messed up good....
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first one was apparently not removing my overlays. So anyway...
My device rebooted after Chainfire, and was on the G/progress bar for like 5 mins so I knew something was up.
I decided to flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread, so I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
EDIT: Resolved. I was able to delete all overlaid apk's from /data/app.

Hi there,
Question, I got a non-rooted S8, Stock in like everything, and it runs everything fine, including Substratum!
I am wondering about one thing though after reading this thread, imagine something went wrong, what would be my options? I found the Rescue ZIP on my phone, can I apply this if needed with the original recovery from the S8? Or do I need TWRP for that?
---------- Post added at 08:44 PM ---------- Previous post was at 08:39 PM ----------
s1dest3pnate said:
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.
Click to expand...
Click to collapse
Hi mate, do I read correctly, that its possible to only boot TWRP temporaly without flashing it?
I have to put the folder/files in the same folder as platform tools?

Debloat/Disable System Apps

So you got your new shiny realme device but you hate bloatware or want to disable system apps so you can use 3rd party apps instead?
Follow the steps below:
THIS DOES NOT REQUIRE ROOT HOWEVER MAKE SURE NOT TO DISABLE IMPORTANT SYSTEM APPS. WIPE DATA/FORMATTING RE-ENABLES ALL SYSTEM APPS. THIS DOES NOT MESS WITH OTAs.
WHAT YOU NEED:-
ADB/Fastboot Drivers
Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip,
Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
DEBLOAT:-
1. Enable developer options by tapping on the build number 7 times and enable USB Debugging.
2. Plug in your phone.
3. Goto the folder where ADB is installed, hold shift and right click, and click on open command window here(windows).
4. Type
in CMD
Code:
adb devices
in Powershell
Code:
./adb devices
.
5. This should return the ID of your device and show if its authorised. Enable debugging Promt on your Phone if it shows unauthorised (allow this computer).
6. Type
in cmd
Code:
adb shell
in Powershell
Code:
./adb shell
.
7. This should display a prompt, something like RMXxxxx:/ $
8. To uninstall type
Code:
pm uninstall -k --user 0 <name of the package>
To disable type
Code:
pm disable-user --user 0 <name of the package>
eg: pm uninstall -k --user 0 com.heytap.browser / pm disable-user --user 0 com.heytap.browser
9. Done!
To reinstall uninstalled apps type
Code:
pm install-existing <name of the package>
To enable disabled apps type
Code:
pm enable <name of the package>
Some apps do not uninstall such as market and gamecenter, disabling is the only option.

Hi, I made a small shell script to remove bloat in my device. Anyone who are interested can check it.
Place it in root of Internal Storage, then
Code:
adb shell
sh /sdcard/bloat.sh.txt
Ref
⋆ [2022-09-28] Remove system apps on Realme UI 2.0 using ADB ⋆
Remove system apps on Realme UI 2.0 using ADB Updated : 2022-09-28 Tested On: Model: RMX2001 Hardware Version: RMX_2001_11 RealmeUI Version: V2.0 ColorOS Version: V11 Android Version: 11 Android Security Update: 2022-03-05 Build Number...
forum.xda-developers.com
Debloat Colour os For smooth Performance
Color OS preloaded with certain apps. Such apps can't simply uninstall. Its hard coded, , for e.g. App Market. Use these command to disable those apps.. No root required... Os updates will still work.. No problems there... Users need to apply...
forum.xda-developers.com
[GUIDE][EU/IN ROM] REALME UI Debloat List
I got this phone a few days ago, am positively surprised with it. As soon as I got it I installed the REALME UI update from the official website and spent the next hour trying to find out what apps should be removed for maximum privacy and...
forum.xda-developers.com
[GUIDE] Debloat your Realme X2 to get more free RAM
Install ADB Drivers properly .This is really important Video Tutorial : Debloat any Realme/Oppo phone Then open command windows in adb directory and type adb devices,then authorize it from your phone . After you have done it ,type adb shell...
forum.xda-developers.com
Debloat COS / RUI
For those who want to debloat the stock system without root, here my list with apps uninstalled for me. How-To: activate ADB in developer settings download ADB tools from Google...
forum.xda-developers.com
[GUIDE] [SCRIPT] Debloater for Bootloader locked & Unlocked devices
For Bootloader Locked: Download debloat_bootloaderLocked.zip extract & execute debloat-main.bat file For Bootloader Unlocked: Assuming you already have custom recovery, just download & flash debloat_flashable.zip Unhide to show up the list of...
forum.xda-developers.com

Nice thank you for sharing this wonderful trick thanks

Hi guys. Thanks for the nice debloat tutorial and script! These are always welcome.
debdeep98 said:
Some apps do not uninstall such as market and gamecenter, disabling is the only option.
Click to expand...
Click to collapse
Are you sure about that? Have you tried it yet with my brand new
universal make system read write flashable script

DeGoogling

Hi
I used to use Cyanogenmod on my phones years ago and want to DeGoogle my Samsung A12. CF-ROOT is what I always used and Odin but It's not supported and seems to be depreciating. What Is the way forward now as I don't think Lineage does anything like a rom for this phone. I've gone for this phone because It's easy to get the back off and disconnect the battery easily.
Can you help?
Kind Regards
Graeme

You may manually - or programmatically by a script that makes use of ADB-commands - remove / uninstall all of Google's services and apps ( read: GMS ) what are put inside the running Android system. You can't do that unless you have the permissions level of the system itself - means ROOT, and you can't remove / uninstall files that are in use.
Example of a Degooglefy script
Code:
adb devices
adb root & adb shell "stop"
for /F "tokens=2 delims=:" %%a in ('adb shell "pm list packages | grep 'google'"') do (
set "pkg=%%a"
if NOT [%pkg%]==[] (
adb uninstall %pkg%
)
)
adb shell "start"
adb reboot

jwoegerbauer said:
You may manually - or programmatically by a script that makes use of ADB-commands - remove / uninstall all of Google's services and apps ( read: GMS ) what are put inside the running Android system. You can't do that unless you have the permissions level of the system itself - means ROOT, and you can't remove / uninstall files that are in use.
Example of a Degooglefy script
Code:
adb devices
adb root & adb shell "stop"
for /F "tokens=2 delims=:" %%a in ('adb shell "pm list packages | grep 'google'"') do (
set "pkg=%%a"
if NOT [%pkg%]==[] (
adb uninstall %pkg%
)
)
adb shell "start"
adb reboot
Click to expand...
Click to collapse
Thanks
Problem is I don't know how to achieve root to this device since I always previously used CF-ROOT sadly depreciated. I've unlocked the bootloader and have odin but no further forward.
Graeme3514

If anyone can help me root and get another software on this phone I'll donate/ pay , whatever. I'm sick of having Google running in the background and CF-ROOT is now depreciated, sadly.

jwoegerbauer said:
You may manually - or programmatically by a script that makes use of ADB-commands - remove / uninstall all of Google's services and apps ( read: GMS ) what are put inside the running Android system. You can't do that unless you have the permissions level of the system itself - means ROOT, and you can't remove / uninstall files that are in use.
Example of a Degooglefy script
Code:
adb devices
adb root & adb shell "stop"
for /F "tokens=2 delims=:" %%a in ('adb shell "pm list packages | grep 'google'"') do (
set "pkg=%%a"
if NOT [%pkg%]==[] (
adb uninstall %pkg%
)
)
adb shell "start"
adb reboot
Click to expand...
Click to collapse
If anyone can help me root and get another software on this phone I'll donate/ pay , whatever. I'm sick of having Google running in the background and CF-ROOT is now depreciated, sadly.
Graeme