Database Users

V3.90 Debloater(Lets remove all that carrier bloat !! Root not required..)

Debloater by Gatesjunior
Disclaimer:
I nor XDA are responsible for anything that you choose to do with this program to your device or others. Modifying my code or redistributing it is not allowed without prior approval from me. Yes, that includes Kanging it, I will be able to tell. Neither is trying to use any of my code to create an apk file with my code logic allowed without prior approval from me.
Donations:
"If this application helps you out, please consider a small monetary donation to further improve development of this application. You can Donate by clicking the "Donate to Me" button on your left, underneath my Profile picture.
Background:
So after many times of going back and forth blocking / disabling apps on my devices through the command line and or shell, I decided to write a program to make this all much easier for myself. Well, after I got it all finally running and doing what I wanted, for each particular device I own, I decided that his was a pretty nice program and I wanted to share it with the community. After all, this community is where I started and learned a lot of the things I know today. So why not share with my family of Android enthusiasts.
Requirements:
The program requires that your manufacturer USB drivers are installed for your specific device as well as the following:
• Windows Operating System
• USB Debugging turned on for your device
• Root or KitKat and above running on your device
Some people have had trouble getting their PC to see their device, even with the device manufacturer drivers installed. Watch your device when you plug it in and authorize your computer to access it, the device should display a popup something for you to grant access to the PC. If it does not, go into Settings, Developer Options and look for an option that says something about Revoke USB debugging authorizations and tap it. Click ok. Now, unplug your device and plug it in while watching your device and click on the option to always allow this computer and then grant when the popup window displays.
What does it do?:
• Block / Disable applications on your device
• UnBlock / Enable applications on your device
• Allow UnBlock / Enable all applications at once on your device
• Allows filtering of the displayed packages for quicker decision making
• Allows exporting your blocked / unblocked listing to a file (Right click on Read Device Packages after list is loaded)
• Allows importing your blocked, or someone else's, listing (Right click on Read Device Packages after list is loaded)
• Allows complete removal of application(s) if you have root (It will backup the original folder structure and apk for you, just in case you need to restore the application(s) back to your device.
So, essentially what it does is this. It will disable / block any system and third party application on your device with ease and allow you to enable / unblock the application just as easy. It also reads everything, real-time, directly from your device, so that there are no messy batch files, scripts and txt files, etc. that you have to maintain and keep track of for every device you own. I mean let’s be honest, most of us own more than one device. Phones, tablets, etc. Who wants to maintain all those scripts and files for every device? The other nice thing that this program does is allow you to, at a granular level, control what is blocked/disabled and what is not. There are quite a few scripts and things like this available in the community that give everyone a start on what to disable/block, but who wants to scour through these scripts and decide what they want or don’t want with something someone else put together. The other nice feature of the program is it will display information for you about your device. Such as Model number, Serial number and battery status. As well as whether or not your device is rooted or not.
What audience of device does it support?:
This program supports many devices. It will support any device running KitKat or above, whether rooted or not. That’s right, if your running KitKat or above, your device does not need to be rooted. If you’re running anything other than KitKat or above, your device does need to be rooted. As long as these requirements are met the program will run. The program will also auto-detect whether or not your device is supported. So if you are not sure, plug it in and let the program tell you. If your device is not supported, it will put up a message saying as much and close the program.
Program Functionality:
The first thing you need to make sure of is that USB debugging is turned on for your device. The video at the end of this OP is a must to watch. It will describe this process as well as allowing adb shell permissions.
So when you first connect your device you will need to wait for the program to detect your device and whether or not it is supported. Once this is established, usually within a couple of seconds, it will display a warning message to you reminding you to be careful with what you disable and block. Yes, it will allow you, if your device is supported, to disable/block even system dependent applications. This message will also include, if your device does not support block mode, a message indicating that block mode is not supported and that it will disable the applications. Here is a sample screenshot of this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once the program has initialized, and the warning message has been presented, it will put you into the main program screen itself which will look like the following.
From here the first thing you need to do is click the Read Device Packages button on the upper left. This will initiate the process to start reading all of the applications on your device and then list them in a list in the window. It will also indicate to you what it detects as applications that are already disabled/blocked on your device by putting a checkmark in the box next to the application. It will look similar to this.
As you can see it will tell you in the upper right how many applications it detects as blocked and not blocked. You will notice that on the bottom left it has an indicator that is labeled Synced. As you make changes to the device application listing this will turn red. In other words, it will indicate whether you have made changes to the device application listing since the last sync. Also, in the upper right there is a counter labeled Changed. This indicates the number of changes you have made to the device application listing since last sync.
Once you have made any changes to the device application listing an Apply button will show up in the upper left replacing the existing Read Device Packages button, it will look like the following.
Once you click the Apply button the existing changes you made to the device application listing will be applied to your device. Keep in mind that you can disable/block and enable/unblock applications all at the same timeand then apply those changes to your device. After you have applied the changes to your device a message will be displayed stating the status of your changes as seen below.
Once the changes are applied to your device you now just click the Read Device Packages button again to reload the information from your device and you will now notice that the application(s) you just made changes to will indicate as much in the refreshed listing. As seen below.
You will notice that the particular application I asked it to disable/block has now a check mark next to it indicating that the device itself has disabled/blocked this application.
So now on to filtering. Lets say you want to limit the listing to specific items you are searching for within the package name. Like packages that contain "vzw" for Verizon. You will see below by clicking the filter checkbox and then typing in what I want to filter on, it will limit the list to your specific filter criteria immediately.
And here is the results of our filter below.
From here I can make changes to the listing, by checking the box next to the packages or I can simply uncheck the filter checkbox and return back to the full listing unfiltered.
O.k., so far so good. Now let’s say that you want to enable/unblock all the applications on your device. Maybe you’re selling it or maybe you have an issue with it and you want your carrier to take a look at it. By clicking the Unblock All Packages button and then click Apply this will enable/unblock all applications on your device. As if it is back to factory with no changes made.
Remove mode turned on. For all you root users, this will completely remove the application(s) in the exact same manner and will keep a backup for you in the install folder under Backup of the original apk files. They will also be kept in the original file structure they came from on the device so that it will make it easy for you if you have to push one back to your device. Here is an example of the remove mode turned on and the warning you will receive when it is active for the device that is rooted.
Also, after you have removed the application(s) you want, if you Reload Device Packages again, you will notice them in the list and checked. This is in fact accurate, it sees them as removed / uninstalled. To not have them show up in the list any longer, just reboot your phone and run the program again and you will see that they no longer show up in the listing.
Sharing your blocked list or re-import it to your device:
So there are times when you get a replacement device and do not want to have to go through all the pain remembering what you had blocked. Well to the rescue comes the export/import functionality of the application. This will allow you to export and import your blocked list. You also might want to share it with someone. So this is how it works:
Once you launched the program and have clicked the Read Device Packages and your list is up, you can right click on the Read Device Packages button and export the blocked packages to a file and share it. Then the person receiving it just does the same process, but when they right click on the Read Device Packages, they just choose import blocked packages and then click the Apply button. Done.. You of course can do this yourself to your device. This can come in very handy if you have to Wipe Data, because you blocked something you should not have and your device is experiencing issues.
Well community people that is it. I hope you enjoy the program as much as I do and look forward to your feedback. Gatesjunior signing out…
Full Install:
Download link: https://1drv.ms/u/s!AjfH26Z4pHaFk1V8rA5Zj_p5vtkx
Upgrade Install: (Just replace debloater.exe in your "Crogram Files (x86)DebloaterDebloater" folder)
Download link: http://rootjunkysdl.com/?device=Gates&folder=DeBloater
OSX Version (dmg file): Thank @eyekyu for the port over with Wineskin..
Download link: http://rootjunkysdl.com/?device=Gates&folder=DeBloater
Mirror: https://onedrive.live.com/redir?resid=8576a478a6dbc737!831
Video by our own RootJunky:
Credits:
RootJunky - For finding the original KitKat weakness
Misterxtc - For all of his hard work already on helping people with a script process for this purpose
Er. Aditya - For testing with me and going back and forth with builds to finally resolve the no packages issue
XDA:DevDB Information
Debloater, Tool/Utility for the Android General
Contributors
gatesjunior
Version Information
Status: Stable
Current Stable Version: 3.85
Stable Release Date: 2015-02-07
Created 2015-02-07
Last Updated 2018-01-12

Change Log:
01/09/2015: Initial Release
01/10/2015: Updated the handling of application filtering determining what is disabled / blocked
01/11/2015: Updated application (v2.1) to hopefully help address the local Administrator issues
01/12/2015: Major update v2.8 (Fixes all the users not being able to see packages - Xposed Framework fix)
1/13/2015: (v2.9) Fixed an issue with an Out of Bounds Exception in certain cases.
1/15/2015: (v2.10) Complete rewrite of the filter engine, all interactive and immediate now. Also some cleanup.
1/16/2015: (v3.0) Root mode added with ability to completely remove application(s), with backup feature.
1/17/2015: (V3.1) Added new intro screen as well as import blocked list functionality.
1/18/2015: (V3.2) Added some hover helper text. If you hover over a major item it will display helper text.
1/19/2015: (V3.3) Fixed some more Xposed framework issues that would impact rooted users and removing packages as well as fixed some import logic to make it more reliable and optimized.
1/23/2015: (V3.4) Major update and bug fixes as follows:
•Interactive search now also supports searching through the package name(s) as well as the apk file(s)
•Bugs related to duplicate entries showing up when you Read Device Packages multiple times with filter on and off are fixed. This could have caused issues with some users saying it will not remove something.
•Blocking mode fully supported on 4.4.x, found a major bug that was preventing this with rooted devices
•APK file backups now include Odex files if they exist with the APK
•Remove option now completely removes both apk and odex, so yes, previous builds would have left the odex files behind. They will not hurt anything, but take up space. I will release a quick fix for the cleanup of those soon, if you cannot do it yourself.
•Buttons appearing where they should not at times with filter is fixed
•If you have disabled something on the phone itself or in a script, and are rooted, the program will not care any longer and will unblock them anyway.
(1/31/2015: (V3.5) Major logic update. I think I finally put a nail in the coffin with the Xposed Framework issues and removing applications. Also added the functionality where once you import a blocked list all the items will turn red for the changes it has made.
(2/6/2015): V3.6 Quite a few additional options. Including the following:
Ability to only show blocked packages, unblocked packages and all packages. (Just right click on either Read Device Packages button or Apply button after initial package listing is displayed.)
Ability to right click now on not only the Read Device Packages button, but also the Apply button.
Ability to import unblocked listing (Yes, changes will be made red to identify what would be unblocked before Applying)
Ability to sort by either APK Filename or Package Name and be able to sort in either Ascending order or Descending order in each area.
Complete removal of all associated data and folders that pertains to a package if the Remove option is selected (Root Mode only)
(2/7/2015): V3.7 Added a checkbox identifier on Display mode to let users know which Display Mode they are in currently.
------ (Fix was placed into this build later that fixes the UnBlock All Packages button bug..)
(3/28/2015): V3.8 Added Lollipop support for rooted / non-rooted users. It will now support hiding the packages, if you are rooted it will disable them instead. Also, you will notice if you right click on the Read Device Packages after it loads there is also a Backup / Restore menu option. Do not use those yet, I am still working on them.
(4/4/2015): V3.85 Fixed issue with base.apk flags being read incorrectly from device. Logic issue.
(4/12/2015): Updated a logic issue in the detection of the device and it's abilities. Same release number, v3.85
(5/24/2015): Fixed an issue during import of a blocked list that would flag all "base.apk" files..
(1/7/2018): Added newer Android Debug Bridge Files..

Hold
For me..

Looking Good video coming soon

I can't wait to give this a run.

Well be getting a note edge soon for testing, and looking forward to giving this a shot.

OP updated now with Video..

Great application but not working on my Droid Razr M (XT907) with latest OTA firmware on it.
Pressing "Read Device Packages" and nothing comes up.

Just tried it on my AT&T Note 4. It seemed to work, great job and thanks for building this app.

0rtli said:
Great application but not working on my Droid Razr M (XT907) with latest OTA firmware on it.
Pressing "Read Device Packages" and nothing comes up.
Click to expand...
Click to collapse
Try this one and let me know:
https://drive.google.com/file/d/0B31X8bH_5Gl-OHpva0dCbHBTb2c/view?usp=sharing

Great idea. Tried it with my ASUS MeMO Pad 8 (ME581CL) but after "Read Device Packages" nothing happens

[email protected] said:
Great idea. Tried it with my ASUS MeMO Pad 8 (ME581CL) but after "Read Device Packages" nothing happens
Click to expand...
Click to collapse
Look back a post and try that one.. Also, send me a screen shot.. Make sure USB debugging is on and in the correct mode as well.

This version works, thanks!
Will be great if this soft give option to disable modem fast dormancy service without root access.
Anyway, thanks.

My AV detects Malware.

Using licensed ESET - no malware detected.
Just disabled FastDormancy.apk (com.motorola.fastdormancy) - how to check if its disabled? In Running programs still see this service is running.

Maximus1a said:
My AV detects Malware.
Click to expand...
Click to collapse
It doesn't like the behavior of the program LOL

I cant get it to download from the webpage. I tried the one in the drive folder and it does not see my phone. Verizon Note 4. Looks awesome, cant wait to get it working!
Got it. I guess the server is overloaded!

Great job on this project addition. I'll be adding your link to my XDA signature this afternoon. Like you and many others, I too believe that until root is achieved on our devices (for those unable to at this time) that having this capability to do with our devices is the next best thing; hands down!
Again, great job to you and to the others like RootJunky and Misterxtc for making this possible for the community here at XDA.

Dear gatesjunior,
I wonder how you'r software disable/enable apk's?
For example: on my device (xt907) I'm not able to complete disable fast dormancy service (see screenshot) only "Force stop" it for a while.
Wonder which method you are using to disable it complete (are you disable it or just force stop it?)

howellcp said:
I cant get it to download from the webpage. I tried the one in the drive folder and it does not see my phone. Verizon Note 4. Looks awesome, cant wait to get it working!
Got it. I guess the server is overloaded!
Click to expand...
Click to collapse
Make sure your USB debugging is on and in the right mode.

[YT3-X90L] Lock state - locked - Recovery image needed

Hello XDA-Community,
I've got a Yoga Tab 3 Pro YT3-X90L from a customer.
He was telling me, that he wanted to unlock his device with the pattern, mismatched for several times and now its locked and requires the owners google account. Or something like that. He never had the owners google account. He told me that his seller has activated his device for him. And he has no clue who it was.
Now here is my part.
I've researched and obviously it's a FRP. The owners google account information are stored in the FRP-Partition. And this partition won't get deleted with a simple factory resett.
What i've tried so far:
1.) https://www.youtube.com/watch?v=nCzrnnh2K1w I was able to follow this tutorial to minute 9:08. But the option "Email and password" is not there anymore. I guess they patched it with 6.0.1.
2.) I tried to flash a stock rom or twrp with LenovoDownloader(QcomDLoader). The stock rom file is: Lenovo_Yoga_Tablet_3_YT3-X90L_ENG_S200028_1609230146. even its a german device this file was the only one i could find. But the LenovoDownloader won't recognize my device. The windows stays white, no entries. I guess i installed the correct driver for this device and Windows recognizes them as removable device if i plug it in via usb.
3.) I've tried to use adb and fastboot boot oem unlock. But this commands aren't working in locked state.
4.) With a trick i could open the Settings and was full of hope to active the developer options to set usb debbuging to active. But this developer options aren't available either with this "user".
5.) There is an apk for showing the "Email and password" interface. I could install it, but it force closes right after starting it.
6.) I've tried several tools to bypass this FRP: WinDroid Toolkit, D-G Unlocker, Realterm, but NOTHING.
What could i do further? I'm out of ideas right now.
I've read about a factory_update.img but i cant find anything, except the stock rom file, for this device.
Or downgrading the device, so i could use the "Email and password" but. But i can't even flash the stock rom.
Specs for the device:
Lenovo Yoga Tab 3 Pro YT3-X90L
Lenovo/YT3_l0_row_lte
6.0.1/MMB29M/LenovoYT3-X90L_S200307_170614
i appreciate any help i can get
greets
redplate

I've wrote it down. Hope this helps.
Situation:
"Confirm account: The device has been reset. To continue, sign in with a Google Account that was previously synced on this device. "
Explanation:
The device has been blocked by repeated input of the wrong password, pattern, etc. and can only be unlocked with the Google account of the owner.
A factory reset or hard reset does not help here, as the account information is saved in its own FRP partition and will not be deleted when the factory state is restored.
Solution:
1. Connect device to a Wi-Fi and Internet access.
2. Before confirming "Next", select another hotspot here
3. Go to "Advanced Settings" and change the proxy settings of any hotspot to Manual.
4. In the text input field of the proxy settings you enter now any word: e.g. Test
5. Now mark this word and select "Assist" in the context menu.
6. Selecting this "Assist" option opens the Google search application.
7. You can now not only browse the Internet through this search, but also search for and open installed programs.
8. We are looking for Chrome, open the internet browser, go to www.google.com and search for DPC test.
Link: https://www.apkmirror.com/apk/sampl...-release/test-dpc-4-0-6-android-apk-download/
9. After downloading this application, go back to the Google search application.
10. Here we enter "Download" to search for the download application.
11. In Downloads we can now find and install the downloaded app.
12. To allow the installation of this .apk, you must allow the installation of "unknown sources" in the settings.
13. Either you go here on the installation itself on "Settings", or you search for "Settings" on the Google search app.
14. After completing the installation of the DPC-Test program, start it with "Open".
15. The app itself is will register as a device owner and now allows us to set up a new Google Account as owner.
16. If this is set up, it will also be included in the FRP partition.
17. In the event of a new factory reset, the device is reset, the DPC-Test program is removed and the device can be freshly set up in the factory settings.
after the takeover of the owner, the reason for blocking the device was not present anymore and the old owner was overwritten. This will be overwritten in the FRP partition aswell with the new account and the old one no longer queried.

You, mister, are my savior! Thank you very much.

Solve works for Lenovo Yoga 3 tablet
Just a big giant thank you! My dad passed away leaving me a Lenovo Yoga 3 tablet, unable to gain access due to information stored in the FRP partition. :highfive:

Hi
I followed your instructions for first 5 points
redplate said:
1. Connect device to a Wi-Fi and Internet access.
2. Before confirming "Next", select another hotspot here
3. Go to "Advanced Settings" and change the proxy settings of any hotspot to Manual.
4. In the text input field of the proxy settings you enter now any word: e.g. Test
5. Now mark this word and select "Assist" in the context menu.
6. Selecting this "Assist" option opens the Google search application.
Click to expand...
Click to collapse
I marked the word and only that is offered on the top right side is : SELLECT ALL - CUT - COPY.
There is no ASSIST option . I don't know, maybe this tablet on my desk has a newer android version with that option removed...
Is there any other solution? Probably will be helpfull for me as well for someone who will have tjis problem in the future
Thx in advance

marOOn1971 said:
Hi
I followed your instructions for first 5 points
I marked the word and only that is offered on the top right side is : SELLECT ALL - CUT - COPY.
There is no ASSIST option . I don't know, maybe this tablet on my desk has a newer android version with that option removed...
Is there any other solution? Probably will be helpfull for me as well for someone who will have tjis problem in the future
Thx in advance
Click to expand...
Click to collapse
Hi. Actually I'm not into this anymore. Could be possible they removed it since it might was reported.
If I have any idea I'll let you know it

I want to root a Galaxy Tab A SM-T350

I delete my files and still can't free up memory. I was reading that bloat could be located under /data/lost+found but I don't know how to access it without root. I've tried to root using SuperSu and TWRP. I downloaded Odin, I downloaded the Samsung USB Drivers, and I installed multiple TWRP files using the `AP` button in Odin.
I get stuck at the Samsung load screen, and can't run recovery mode.
I don't want to load any new Roms, I just want to get sudo access so I can access /data/lost+found
Can someone please help?

androidgeek230 said:
I delete my files and still can't free up memory. I was reading that bloat could be located under /data/lost+found but I don't know how to access it without root. I've tried to root using SuperSu and TWRP. I downloaded Odin, I downloaded the Samsung USB Drivers, and I installed multiple TWRP files using the `AP` button in Odin.
I get stuck at the Samsung load screen, and can't run recovery mode.
I don't want to load any new Roms, I just want to get sudo access so I can access /data/lost+found
Can someone please help?
Click to expand...
Click to collapse
SuperSU, really? That's been dead for years, download Magisk instead

Nimueh said:
SuperSU, really? That's been dead for years, download Magisk instead
Click to expand...
Click to collapse
I thought they stopped implementing `sudo` privileges. What's the easiest way to get the sudo command installed on phone?

Nimueh said:
SuperSU, really? That's been dead for years, download Magisk instead
Click to expand...
Click to collapse
LOL. There are two apks. What do I do with them? Do I still need Odin? Sorry, I'm very new to this. Is there a particular thread you know works?

The basic of rooting:
*unlock bootloader
*Install recovery TWRP for your tab
*Install magisk trough TWRP
*Debloat your lovely TAB...please
*enjoy
If you downloaded magisk.zip ,you can also change the extension to .apk
Regards

Tresans said:
The basic of rooting:
*unlock bootloader
*Install recovery TWRP for your tab
*Install magisk trough TWRP
*Debloat your lovely TAB...please
*enjoy
If you downloaded magisk.zip ,you can also change the extension to .apk
Regards
Click to expand...
Click to collapse
Awesome! This is what I'm looking for! So to unlock the bootloader, I download Odin? When I put the tablet in download mode, Odin can then flash the TWRP recovery image. Then when I restart, I can install magisk?
I think I'm running into an issue where the backlight for my tablet is not displaying (the TWRP UI). I'm verifying.

Hello Androidgeek230,
Unlocking bootloader means,your /Data map will completely wiped.no more guarentee from Samsung (fun part )
* go on your tablet to the about section and tab 10 times to activate developer options, enter it and select OEM unlock + Adb USB debugging
*Install USB driver for samsung tab
*shutdown Tab
*While pressin "Volume UP + volume Down button,connect your Tab with USb cable to PC (maybe in background device driver is being installed.
*Device is in unlock mode,select volume Up again to enter "bootloader"
*Select again volume up to unlock bootloader.
Now your tab is Unlocked and will restart installing Android,couple minutes later your in Android again.
Now you must install recovery TWRP with ADB
regards

about the developer options:
Step 1: Go to Settings > About Phone.
Step 2: Tap Software Info > Build Number.
Step 3: Tap Build Number seven times. After the first few taps, you should see the steps counting down until you unlock the developer options.

Tresans said:
Hello Androidgeek230,
Unlocking bootloader means,your /Data map will completely wiped.no more guarentee from Samsung (fun part )
* go on your tablet to the about section and tab 10 times to activate developer options, enter it and select OEM unlock + Adb USB debugging
*Install USB driver for samsung tab
*shutdown Tab
*While pressin "Volume UP + volume Down button,connect your Tab with USb cable to PC (maybe in background device driver is being installed.
*Device is in unlock mode,select volume Up again to enter "bootloader"
*Select again volume up to unlock bootloader.
Now your tab is Unlocked and will restart installing Android,couple minutes later your in Android again.
Now you must install recovery TWRP with ADB
regards
Click to expand...
Click to collapse
Hi Tresans,
I want to see what's in my /data/lost+found though. Is there a way to do that?

Tresans said:
about the developer options:
Step 1: Go to Settings > About Phone.
Step 2: Tap Software Info > Build Number.
Step 3: Tap Build Number seven times. After the first few taps, you should see the steps counting down until you unlock the developer options.
Click to expand...
Click to collapse
Thanks for the detailed instructions! I was able to do this and I can see developer options.

Tresans said:
Hello Androidgeek230,
Unlocking bootloader means,your /Data map will completely wiped.no more guarentee from Samsung (fun part )
* go on your tablet to the about section and tab 10 times to activate developer options, enter it and select OEM unlock + Adb USB debugging
*Install USB driver for samsung tab
*shutdown Tab
*While pressin "Volume UP + volume Down button,connect your Tab with USb cable to PC (maybe in background device driver is being installed.
*Device is in unlock mode,select volume Up again to enter "bootloader"
*Select again volume up to unlock bootloader.
Now your tab is Unlocked and will restart installing Android,couple minutes later your in Android again.
Now you must install recovery TWRP with ADB
regards
Click to expand...
Click to collapse
I don't see OEM unlock anywhere, though.

androidgeek230 said:
I delete my files and still can't free up memory. I was reading that bloat could be located under /data/lost+found but I don't know how to access it without root. I've tried to root using SuperSu and TWRP. I downloaded Odin, I downloaded the Samsung USB Drivers, and I installed multiple TWRP files using the `AP` button in Odin.
I get stuck at the Samsung load screen, and can't run recovery mode.
I don't want to load any new Roms, I just want to get sudo access so I can access /data/lost+found
Can someone please help?
Click to expand...
Click to collapse
Btw, you can delete bloat without root.

Arealhooman said:
Btw, you can delete bloat without root.
Click to expand...
Click to collapse
Yes,only for current user,but apk is still in system,so no "real" cleanup.

Tresans said:
Yes,only for current user,but apk is still in system,so no "real" cleanup.
Click to expand...
Click to collapse
What do you mean? Adb or app de bloater can fully remove them.

Arealhooman said:
What do you mean? Adb or app de bloater can fully remove them.
Click to expand...
Click to collapse
I used adb shell.
I can't access /data folder.
It says permission denied. This is why I want sudo.

androidgeek230 said:
I don't see OEM unlock anywhere, though.
Click to expand...
Click to collapse
Hello,
OEM unlock feature is in the developer options,together with USB debugging.
Or it is greyed out,cause of already boatloader unlocked.

Arealhooman said:
What do you mean? Adb or app de bloater can fully remove them.
Click to expand...
Click to collapse
I didnt knew this, so without root? including system files cleanup.
May I have a link how to do it I ,have a original Android,no root on it,I can try it
Kindly regards

I have the following in my development options - no OEM Unlock
Submit bug report
Desktop backup password
Stay awake
Bluetooth HCI snoop log
Running services
Picture color mode
WebView implementation
Multiprocess WebView
Auto update system
Demo mode
Debugging
USB debugging (enabled)
Revoke USB debugging authorizations
Include bug reports in power menu (disabled)
Mock location app
View attribute inspection (disabled)
Select app to be debugged
Wait for debugger (grayed out)
Verify apps via USB (disabled)
Buffer size for logging
Networking
Authorize wireless display devices (disabled)
Wi-Fi verbose logging (disabled)
Aggressive WiFi/cell handover (disabled)
Allow Wi-Fi roaming scans (disabled)
Keep Mobile data turned on (disabled)
USB configuration (MTP (Media Transfer Protocol))
Disable absolute volume (disabled)
Input
Show touches (disabled)
Show pointer location (disabled)
Drawing
Show screen updates (diabled)
Show layout boundaries (disabled)
Force RTL layout (disabled)
WIndow animation scale (1x)
Transition animtion scale (1x)
Animator duration scale (1x)
Simulate secondary displays (none)
Minimum width (768dp)
Hardware-accelerated rendering
Force GPU rendering (disabled)
Show GPU view updates (disabled)
Show hardware layers updates (disabled)
Debug GPU overdraw (Off)
Show non-rectangular cips (off)
turn on 4x MSAA (disabled)
turn off hardware overlays (disabled)
simulate color space (off)
Media
prevent usb audio routing (disabled)
Monitoring
Strict mode (disabled)
GPU rendering profile (off)
Applications
Do not keep activities (disabled)
Limit background processes
SHow all ANRs
Inactive apps
Force allow apps on external (disabled)
Force activities to be resizable (disabled)
Reset the ShortcutManager API call limit

Tresans said:
Hello,
OEM unlock feature is in the developer options,together with USB debugging.
Or it is greyed out,cause of already boatloader unlocked.
Click to expand...
Click to collapse
I have the following in my development options - no OEM Unlock
Submit bug report
Desktop backup password
Stay awake
Bluetooth HCI snoop log
Running services
Picture color mode
WebView implementation
Multiprocess WebView
Auto update system
Demo mode
Debugging
USB debugging (enabled)
Revoke USB debugging authorizations
Include bug reports in power menu (disabled)
Mock location app
View attribute inspection (disabled)
Select app to be debugged
Wait for debugger (grayed out)
Verify apps via USB (disabled)
Buffer size for logging
Networking
Authorize wireless display devices (disabled)
Wi-Fi verbose logging (disabled)
Aggressive WiFi/cell handover (disabled)
Allow Wi-Fi roaming scans (disabled)
Keep Mobile data turned on (disabled)
USB configuration (MTP (Media Transfer Protocol))
Disable absolute volume (disabled)
Input
Show touches (disabled)
Show pointer location (disabled)
Drawing
Show screen updates (diabled)
Show layout boundaries (disabled)
Force RTL layout (disabled)
WIndow animation scale (1x)
Transition animtion scale (1x)
Animator duration scale (1x)
Simulate secondary displays (none)
Minimum width (768dp)
Hardware-accelerated rendering
Force GPU rendering (disabled)
Show GPU view updates (disabled)
Show hardware layers updates (disabled)
Debug GPU overdraw (Off)
Show non-rectangular cips (off)
turn on 4x MSAA (disabled)
turn off hardware overlays (disabled)
simulate color space (off)
Media
prevent usb audio routing (disabled)
Monitoring
Strict mode (disabled)
GPU rendering profile (off)
Applications
Do not keep activities (disabled)
Limit background processes
SHow all ANRs
Inactive apps
Force allow apps on external (disabled)
Force activities to be resizable (disabled)
Reset the ShortcutManager API call limit

Nimueh said:
SuperSU, really? That's been dead for years, download Magisk instead
Click to expand...
Click to collapse
Sorry Nimueh,
I downloaded Magisk. Okay I went to the Github and was reading the instructions. It says I should do this:
`If your device has boot ramdisk, get a copy of the boot.img.`
How do I get a copy of the boot.img?

Samsung Galaxy J5 locked with Google account

Hi all,
I hope somebody can help me.
For a client we recieved an old J5 and wanted to reset it to factory settings.
We have done this through the power + volume up + home menubut we have a issue.
It asks for a previous Google account which we dont have.
Is there a way to bypass this or remove the lock?
Thanks in advance

This is called FRP (Factory Reset Protection), and there is no proven working way to remove it, all you will find is shady paid app that may or may not work. Even reflashing will not fix it.

You can try some of the shady apps, but I can not vouch.

Try to install Sam Fw, its a software who can unlocked FRP on a gran numbers of Samsung phones

Lmao yes I as just about to say that. I looked around and found this gem. SamFW is a trusted site for firmware, so chances are this is legit.

If doest work, try to open Chrome via the talkback configs.
1-open talkback via the buttons
2-open talkback config
3-close talkback
4-in the configs open "Help & Feedback"
5- if show a error screen, click on the three buttons on the top
6- click "send feedback"
7- write any thing and hold
8- select the option "assitant"
9- search 'internt" or "chrome"
10- go to this website https://www.bloggerraposoinforceljh.com.br/2019/10/sem-papapa-sem-pepepe.html or search "So recebe infocell"
11-download "Android 6 Apk" and "Bypass FRP Apk"
12-open dowloads
13-install frp 6
14- install and open Bypass frp"
15- click on the three butons on the top and click in "ok"
16-enter a email and a password
17-restart device
18-after conclues the configs of the phone, reset the phone again to erase the downloaded contents

[GUIDE] Flash CrDroid 9.5, A13 build.20.05, Magisk Delta, Pass SafetyNet, Hide Root

W.I.P. - UPDATED on 21.05.2023​​Assumptions of reader,​PRIOR to following this guide:​​
You understand that you follow anything seen here of your own volition.
Your Bootloader is unlocked.
Able to troubleshoot your device, setups, installs, unlocking, rooting, etc.
Capable of searching on XDA/Github/Telegram/Google for missing information and files.
This guide outlines the process I used to clean install the following:​TWRP-3.7.0_12-v7.8_A13_FBEv2-lmi-skkk.img
CrDroid v9.5/ A13/build-02.06.2023
NikGapps-T FULL package, 09.06.2023
ROOT/Magisk DELTA - fdac22ba-delta(25210)
Pass SafetyNet Basic Attestation - Universal SafetyNet Fix 2.4.0 by kdrag0n
LSPosed v1.8.6 (6712) ZYGISK and Hide My Apps List
Test root detection, Pass SafetyNet Basic Attestation
​PIXEL LAUNCHER ISSUE;
On CrDroid ROMs :
Due to CrDroid Home/Stock Launcher having its own QuickStep built-in, it cannot be installed alongside Pixel Launcher, nor vice versa.
This concerns the Pixel Launcher included in some NikGApps package AND the Pixel Launcher addon.
Therefore, you/we can ONLY use CrDroid Home/Stock Launcher OR Pixel Launcher,
The Pixel Launcher section of your nikgapps.config should look like this to avoid any issues with CrDroid Home Launcher ;
PixelLauncher=1
# Pixel Launcher set to 0 to skip its installation over CrDroid Home Launcher
PixelLauncher=0
DevicePersonalizationServices=1
QuickAccessWallet=1
GoogleWallpaper=1
SettingsServices=1
PrivateComputeServices=1
#Pixel Themes set to 0 to avoid issues with CrDroid Home Launcher
PixelThemes=0
#For Live Captions to work, the follwing must be enabled, i.e. set to 1.
DevicePersonalizationServices=1
SettingsServices=1
PrivateComputeServices=1
More details on using the NikGApps config file can be found here.
​A Clean Flashing/Install Environment:​
We first need to establish a clean environment.
Opinions may vary, but I will be clean flashing a stock MIUI ROM via fastboot.
For this, I will be using two software programs and one file;​
Mi Flash Tool v20220507, or later, from here https://xiaomitools.com/mi-flash-tool-ru/
7-zip file archiver, from here, 7-zip
You will also need the stock MIUI Rom from here; https://xiaomifirmwareupdater.com/miui/lmi/stable
- make sure the details are as below ;​
Device: POCO F2 Pro Global​
Codename: lmi​
Version: V14.0.1.0.SJKMIXM​
Branch: Stable​
Type: Fastboot​
Size: 5.1 GB​
Release Date: 2023-03-17​
Package Name: lmi_global_images_V14.0.1.0.SJKMIXM_20230317.0000.00_12.0_global_15e376c371.tgz
This is a ".tgz" file and will need to be extracted to obtain the ".tar" file.
Which will then have to be extracted to obtain the images' folder.
The images' folder should be placed on the Desktop, as that is the default working folder now for the Mi Flash Tool.​
Note: It is entirely up to you to use the RECOVERY version instead of the FASTBOOT version, but please remember if you did, in the event that you encounter issues, it may help you to troubleshoot accordingly.
Now we can proceed.
The Flashing Process:
​An excellent guide on using the tool made by @NOSS8 can be found here; https://forum.xda-developers.com/t/miflash-guide-use-xiaomi-flash-tool.4262425/​​01. Extract the Mi Flash Tool archive.
02. Open the Mi Flash Tool folder and create a folder called 'log'.
03. This is to avoid an error when we have to authenticate our Mi account.
04. Open the Mi Flash Tool app and select 'Authentication'.
05. Log in with the same credentials you used for your Xiaomi/Mi account and/or to unlock your Bootloader.
06. Select English.
07. Enter your details and wait for the "Login successful[CN]" message, like below, then MINIMISE that window.
Spoiler: Login successful [CN]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
08. Select "Driver" to install drivers to communicate with your device.
09. Select "Configuration", in the "Configuration" window, nothing should be selected/written/filled/checked.
10. In the 'Check Point' section, if you see, "\$fastboot -s .* lock" be sure to delete it and don't leave any blank spaces.
Spoiler: Check Point
11. Click "OK".
12. Select "select" and select your images' folder.
Spoiler: images' folder
13. On your device, Developer Settings/Options must be enabled.
14. Place your device into fastboot mode.
15. Now connect your device to your computer with your data cable.
16. Verify the device is connected by using "fastboot devices" in a terminal window.
Upon confirmation, we can proceed.
17. Verify that at the bottom of the Mi Flash Tool Window that you have selected the "clean all" radio button and that to its right you can see "flash_all.bat" in the drop-down box.
Spoiler: clean all radio button
18. Now you can click, "flash" and the process will begin.
Spoiler: flash result; success
19. Eventually you will see 'success' highlighted in green under "result", shortly after which your device should reboot to system for the first time, in this order; POCO boot logo > MIUI boot animation > Activation screen..
20. It should ask you to connect to a Wi-Fi network, so you can activate the device.
21. Tap "Open Wi-Fi Settings", select the network of your choosing, enter the password, under Advanced Options when entering the password, I usually select Device/Stable MAC because I have had issues with Randomised MAC in the past.
22. Confirm your connection then back out to the main screen to "Activate this device", enter your login details.
23. The MIUI setup process will begin, agree/yes to everything EXCEPT restoring your Google account.
Skip/Ignore the account restoration process as it is a waste of time, we're here for Custom ROMs mate.
DO NOT PUT A PIN/SCHEMA/PASSWORD.
24. Eventually you'll get to the Home Screen, where you'll see the Settings icon in the middle, open it.
25. Now go, Settings > About Phone > All specs > Tap MIUI version until it says Developer Settings unlock, normally 7 taps I think.
26. Now go, Settings > Additional Settings > (scroll to bottom) Developer options > enable USB Debugging, I'm aware etc., 10 sec countdown, tap OK.
Done, now we can get to flashing a Custom Recovery and then our Custom ROM.
27. Reboot your device to fastboot, "adb reboot bootloader" or any other method.
28. Locate your recovery image (TWRP-3.7.0_12-v7.8_A13_FBEv2-lmi-skkk.img) and, using a terminal window, 'cd' to the directory. Then use "fastboot flash recovery twrp.img" to flash your recovery. After which, use "fastboot reboot recovery" to boot your recovery.
29. Assuming TWRP, under the "Wipe" category, perform a Factory Reset" then Wipe Data, after which, REBOOT TO RECOVERY.
30. Copy the ROM and NikGApps to the device, flash the ROM, reboot to recovery, flash NikGApps, reboot to recovery, factory rest and format data, reboot to system.
(Some will say this is excessive but from my perspective, it has eliminated many issues I was having when flashing ROMS)
31. Complete your device first boot setup.
So at this point, I will assume you have done as I have and waited to have restored your Google backup, WhatsApp etc.
EDIT; DUE TO A NEWLY RELEASED TWRP, THE MAGISK DELTA APK CAN BE RENAMED TO .ZIP AND FLASHED FROM RECOVERY WITH THE TWRP LINKED AT THE TOP OF THIS THREAD
Spoiler: Deprecated steps
32. Reboot to recovery. Here you will notice that you cannot mount the Data partition. As of the 9th January, 2023 there is no recovery for our device that can decrypt A13 ROMs, so when rooting the device we will be using "adb sideload" to send and flash Magisk.
33. In your recovery (assuming TWRP), go to Advanced > ADB Sideload, don't wipe Dalvik/Cache > Swipe to start ADB Sideload.
34. In a Command Prompt or Terminal window, opened as Administrator, use ADB sideload by entering the command similarly as seen here;
35. Reboot to System > install the Magisk Delta 25.2 delta 6 apk > open the app > ensure that the installed version is "a0b2003b-delta (25206)"
36. Install Magisk Delta by flashing the apk you have renamed to .zip as mentioned above.
36a. Go to Magisk Delta App > Settings and change the following :
Enable DNS over HTTPS
HIDE the Magisk App
Tap on Systemless Hosts once if you want to use an adblocker like AdAway later on.
Enable Zygisk
Enable Bootloop Protection
Enable MagiskHide
REBOOT
37. Now go to > Configure MagiskHide > search for these apps and use these settings;
For Google Play Store, enable it for com.android.vending
For Google Play Services, enable it for com.google.android.gms AND com.google.android.gms.unstable
You can go ahead and add detection apps like AppList Detector, MOMO, TB Checker etc.
38. In Magisk, flash Universal SafetyNet Fix 2.4.0 and Zygisk LSPosed 1.8.5-6649
REBOOT
39. Allow the shortcut of LSPosed to be added to your Home Screen, open LSPosed, tap the Respository button on the bottom-left side and search for and then install Hide My AppsList 3.1.1, tap on the notifcation and enable the app/module in LSPosed, then REBOOT.
40. Open Hide My Applist > Template Manage > Create a blacklist template with whatever name you want, I just use 'Blacklist' > Edit list > Add the Magisk app and Hide My Applist > back out and the changes will be saved.
41. Open Hide My Applist > App Manage > Search and select your detection apps, and Google Play Store and Services. Ensure that you can see the word "Enabled" next to the selected apps' names, open each and Enabled hide, then under Template config, tap "Using 0 templates" and select the Blacklist you just made.
42. Reboot and check your detection apps, they should look like this;
Spoiler: Detection Apps

Great guide, thanks for your hard work.

Can you share a link to delta 6 zip?

Old_grinch said:
Can you share a link to delta 6 zip?
Click to expand...
Click to collapse
Just rename the .apk to .zip and you can flash it.

I don't even own this phone but this guide it's very good.
typo edit:
30. Copy the ROM and GApps to the device, flash the ROM, reboot to recovery, flash GApps, reboot to recovery, factory rest and format data, reboot to system.
(Some will say this is excessive but from my perspective, it has eliminated many issues I was having when flashing ROMS)
Click to expand...
Click to collapse
"factory rest and format data" - "factory *reset and format data"

"Enable MagiskHide
REBOOT
37. Now go to > Configure MagiskHide > search for these apps and use these settings; "
Is this prefered ? I use SuList mode . Am I wrong and shold use "configure MagiskHide" instead ?
"Pass Basic SafetyNet Attestation - Universal SafetyNet Fix 2.4.0 by kdrag0n"
It works correct on Poco F3 but not on Poco F2 Pro (Crdroid). I suggest to use working :
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com

Tomek0000 said:
"Enable MagiskHide
REBOOT
37. Now go to > Configure MagiskHide > search for these apps and use these settings; "
Is this prefered ? I use SuList mode . Am I wrong and shold use "configure MagiskHide" instead ?
"Pass Basic SafetyNet Attestation - Universal SafetyNet Fix 2.4.0 by kdrag0n"
It works correct on Poco F3 but not on Poco F2 Pro (Crdroid). I suggest to use working :
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Click to expand...
Click to collapse
KernelSU and/or SUList will not be implemented in the guide until I start using it.
This SafetyNet fix is no longer needed on CrDroid 9.5 20.05 build, but thank you for this, though, I hope it helps someone if they encounter issues.

OP Updated.

Deleted member 10679719 said:
I don't even own this phone but this guide it's very good.
typo edit:
"factory rest and format data" - "factory *reset and format data"
Click to expand...
Click to collapse
Good looking out, I think I got all the typos, if not most this time around when I updated the guide a little.

Old_grinch said:
Can you share a link to delta 6 zip?
Click to expand...
Click to collapse
Spoiler: Check here

Glad to see the guide updated

Lughsen said:
Glad to see the guide updated
Click to expand...
Click to collapse
You're welcome!
The process outlined can work for many ROMs, but I focus on CrDroid because I use it as my daily driver.
I'll try my best to update it as often as I can (once/twice every two weeks) but for the moment I have exams.

Gonna made a rom installation round.
I'll tell you if the guide works on other roms

With lastest TWRP FBEv2, all roms installed with no issues.
I´m having problems (i hope i will solve it) with the fastboot full rom installation. I think new version on twrp has an option to prevent from installing new recovery checked by default, so brand new miui installation always fails.
On your next update of the guide, maybe you need to point about this

Lughsen said:
With lastest TWRP FBEv2, all roms installed with no issues.
I´m having problems (i hope i will solve it) with the fastboot full rom installation. I think new version on twrp has an option to prevent from installing new recovery checked by default, so brand new miui installation always fails.
On your next update of the guide, maybe you need to point about this
Click to expand...
Click to collapse
Thanks for reminding me about FBEv2, needed to add that in for some time.
I just updated the guide after following the steps, changing/adding only the recent builds of TWRP FBEv2, CrDroid 9.5, NikGapps.
I had no issue at the fastboot clean flash section, using the TWRP linked in the guide.
I require more specificity on the issues related to the fastboot clean flash, so I can reproduce them on my side and write a detailed solution/circumvention into the guide.
Thanks for looking out @Lughsen

lots of unneeded step, i succesfully do it 5x faster than this.
coming from miui13:
ubl, flash latest twrp, reboot reovery
format data, reboot recovery
flash latest fw>rom>nik core>magisk official>reboot system
after boot, open magisk>direct install>reboot
open magisk, install unisafetynetfix>magiskhidepropconf, enable zygisk, reboot
open magisk, deny playstore stuff
all works fine, safetynet passed.
i wonder why you need to torture yourself by going full miui flash and lsposed.