Develop Bugs

[MOD] Quick & Easy Root Script - HC

This should work for any and all a100 Honeycomb builds, you'll need to install an app from the market called terminal emulator. Also, you'll need a file manager like Astro to unzip the file.
This mod should root your tab in a matter of seconds after the script file is launched. I've tested this on my tab from a clean build and it works like a champ.
Here we go!
- Install the following apps from the market:
Terminal Emulator
https://market.android.com/details?id=jackpal.androidterm&hl=en&rdid=jackpal.androidterm&rdot=1
Astro File Manager
https://market.android.com/details?id=com.metago.astro&hl=en
- Download the attached file from this post.
- Extract and put both the root.sh and su in /mnt/sdcard from the root.zip file.
(Using Astro, find the root.zip file it might be in /mnt/sdcard/Downloads or could be else where if your not using the website to view XDA. Copy it from where ever it's at and paste it in /mnt/sdcard. Press your finger on the zip file and tap Extract when the menu pops up. Tap "Extract to This Directory".)
- Next, open terminal emulator and copy / paste the following:
sh /mnt/sdcard/root.sh
Text will fly by, the script will automatically copy the su binary and install it to the proper location.
Once the script finishes running, be sure to install superuser from the market:
Very Important, if you skip this you won't be "officially rooted yet"!!!
https://market.android.com/details?id=com.noshufou.android.su
Open the superuser app once it's installed, click on the wrench in the upper right corner, scroll to the bottom and find "Su binary v... Tap to check for updates" and tap that link. It should bring you to an update screen, click the button at the bottom to update!
Once you have done the above, then install busybox, Titanium, etc.. if needed.
Thanks goes to abliss for origionally coming up with the root commands!
This mod really just automates his work.

permission denied every step of the way. Used both script manager and terminal

ok terminal manager is out, I didn't realize that doing a hard reset wouldn't wipe the /system/xbin directory completely so technically busybox tools were still installed and sh wouldn't normally be there. I'll see if there's another way..

this method work for any build? and if so, is there any problem during the process that could "kill" my a100 or it's safe?

This method should, yes and it's safe.. It's actually more safe (if that's possible) than the method origionally posted in the dev section since there really isn't any room for user error.
Sent from my MB860 using XDA App

Ill give the new method a go around tomorrow and report back for you.

I wasn't expecting it to anyway, but I figured I'd let you know this doesn't work on the A101.
Hoping someone can find a working root method for this model.

Sorry to hear about the a101, that thing sounds like a tough nut to crack!
Sent from my MB860 using XDA App

This working for me i manage to root my a100

It works and its so simple
Thank you so much for this! It was so easy. Though the only problem I had was with the terminal emulator, no fualt of the Dev, but it might help someone. When I was trying to write in the line of code I kept getting errors because I couldnt get the keyboard to write lower case. So copy and paste if your a noon like me to get it through the terminal.

Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...

mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
You sure you don´t have an a101? what build number are you running?

A100_2.007.04_COM_GEN1
Most definitely an A100...

mvan4310 said:
A100_2.007.04_COM_GEN1
Most definitely an A100...
Click to expand...
Click to collapse
I have no idea then.. the only thing I could say is to try and restore from a "Full" rom, like Acer_A100_1.014.08_COM_GEN1 and try to root it before doing anything else. It wouldn't hurt to try anyway and the worst that could happen is that you'd have to restore all your apps and stuff. If we can ever get this thing to run cwm and a different kernel, you'll definitely be needing root.

Works great!
Thanks so much for the script and instructions. Im enjoying my rooted tab yay!

mvan4310 said:
Well, I dont know what the hell is up with my tab, but Even this didnt work. It showed the file was there, but after I tried installing SU, it didnt get root, so I went back in to verify the file was still there, and nope. It disappeared. I have no idea how, unless somehow mine device is checking the directories, which is the only thing I can think of...
Click to expand...
Click to collapse
Did you check the boxes for USB Debugging and Unknown sources just in case?? (in Settings > development)

I checked them both. Root Checker shows I have root, but other apps cant get root access, and SuperUser cant update because of this issue... I dont know what the hell to do because this has me stuck atm... Im gonna flash back to 1.018 and see if that helps, probably not, but it wont hurt to check.
EDIT:
I reverted back and got root. It seems to be the newest update that stopped it. Im updating back up again to see if I retain root. What a pain...
Edit 2:
Yep, Im rooted now. It unrooted me when updating, ran the script you provided and its working now. Dont know why it didnt take before reverting back, but works wonderfully now. Now that Im rooted, let me know what I can do and peek around at to help out here.

Has anyone tried that on an A500?

A500 has its own rooting methods. You can find info about the A500 here
http://forum.xda-developers.com/forumdisplay.php?f=1136

Thanks alot crossix. Worked like a charm.
Sent from my A100 using Tapatalk

[HOWTO] Easy Root Instructions (Sprint or T-Mobile) [Updated 24 June 2012]

First off, let me say that I did not develop this schtuff and all thanks should go to those that did. Special thanks to noobnl (his thread here), mskip and TeamEpic for all their work.
A note about these instructions:
They're long and may seem a little daunting to those that aren't experienced. Please don't let that deter you as they've been written to be as simple and easy to follow as is reasonably possible assuming you can work a Windows PC and extract a zip file.
==> If you encounter problems with these instructions, please check the FAQ in the post following this one. <==
For video instructions (courtesy of qbking77) scroll to the bottom of this post.
General Disclaimer:
Use these tools and this guide at your own risk. Doing these things wrong/improperly/etc. has the ability to completely ruin your device and YOU assume all risk and responsibility if that happens.
Also note that rooting WILL violate the manufacturers warranty on the device making it ineligible for warranty repair. If you have insurance on the device however, they MAY still replace it for the cost of your deductible.
Click to expand...
Click to collapse
Non-ADB Root instructions (Windows Only):
First, the non-dangerous, standard user stuff:
Download and install the Samsung USB drivers from Samsung's website: http://downloadcenter.samsung.com/c...nt_L710_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Turn on Debugging on your Phone
Open Settings
Select "Developer options" in the System section
Check the box for "USB Debugging"
Press "OK" to confirm.
Plug you phone up to your computer using the USB cable and allow the drivers to install.
Download CMW_SuperUser_v3.07.zip from the bottom of this post
I recommend making yourself a nice little GS3 folder in your downloads folder for all this stuff so it's easy to find
DO NOT UNZIP!!
Copy CMW_SuperUser_v3.07.zip on to the Root of your GS3s INTERNAL storage (if you put it into a folder, you may have a hard time finding it later, but that's on you).
DO NOT UNZIP!!
Unplug your phone
Power off your phone
Now, this is the part that can BRICK your phone so follow ALL instructions CAREFULLY!!
Download Odin3-v3.04 from the bottom of this post
Extract Odin3-v3.04 into it's own folder somewhere where you can easily find it.
Download clockworkmod.tar from the bottom of this post to somewhere you can easily find it.
Reboot your phone into download mode
Hold down Volume Down, Home and then the Power button until the Warning!! message is displayed
Press Volume Up to continue.
Your phone should now be in download mode, displaying a green Android and say Downloading. If it is not, power off your phone by holding down the power button and then try to get into Download mode again. Do NOT progress until you have done so.
Go into the folder you extracted Odin3 into and run Odin3 v3.04.exe (you may have to Right-Clik => Run as Administrator)
Connect your phone to your computer via USB. Drivers may install again; if this happens, allow them to finish before progressing.
In Odin, the COM box all the way to the left should turn blue and it should say Added!! in the Message area.
Click on PDA and in the Open window that pops up navigate to and open the clockworkmod.TAR file you downloaded earlier
Verify that Auto Reboot and F. Reset Time are checked
Click Start. Once the process is completed you device should automatically reboot and there will be a green PASS! box in the upper left of the window. You can then close Odin.
Power off your device and boot into Recovery mode
To boot into Recovery mode: Hold down Volume Up, Home and then the Power button until the device begins to power on then release all 3.
You'll know you're in recover mode when it says "CWM-based Recovery" at the top of the screen
Install CMW_SuperUser_v3.07.zip that you copied onto your internal memory
Navigating ClockWorkMod Recovery: Use the Volume Up and Down rocker to change the highlighted option and the Home button to select an option. The Back softkey works, but will not be lit and will take you back one screen.
Installing a zip:
Select "Install zip from sdcard" (Yes, I know it's on the internal storage.)
Select "Choose zip from sdcard"
Select the zip you want to install; in this case CWM_SuperUser_v3.0.7.zip
Select "Yes" to begin installing
Once the process has completed use the Back arrow to get back to the main recovery screen (Remember: it works, but it's not lit) and select "reboot system now." Once your device boots up you should now be 'Rooted,' but there's still a few more things to be done
Install BusyBox. There are actually several ways to do this, but the BusyBox app in the Google Play Market is quick and easy.
Install BusyBox (this is a link to the online verison of the Google Play store. You can actually follow this link and install it from there and it will get pushed to your phone. Alternatively, just search for BusyBox in the Google Play store and it should be the first app in the search results from author Stephen (Stericson))
Open BusyBox Free from your App Drawer
Allow it Root access when it prompts you
Tap the red "X" to close the dialog window that pops up
Allow BusyBox to scan you phone
Tap "Install" to install BusyBox and make the necessary file changes.
Update your Binaries.
Open the Superuser App from the App Drawer
Get into settings (the wrench icon in the upper right of the screen)
Select Su binary under the General section towards the bottom of the list
Select Update
Your device is now rooted and all set.
How to video (YouTube): http://www.youtube.com/watch?v=7Soapch0c5U
Thanks again to qbking77 for the instructions video!
P.S. If you are a developer or I have used some of your material and/or you feel you should be credited, please let me know and I will update this post.

Frequently Asked Questions
This FAQ is in the works as more questions roll in so I'll do my best to keep it updated.
Q: Odin failed! What do I do!?
A: Try plugging your USB cable into a different USB port on your computer and/or try a different USB cable (Odin's picky about the cable). The drivers may install again; if so, wait for them to finish. After that, verify that the device shows as Added in Odin again and click start again. If that still fails, try unchecking F. Reset Time box and removing any MicroSD card you have in the device, plug the device into (yet another) USB port and try again.
Q: Will these instructions work for other US (LTE) versions of the GS3?
A: I have not personally tested this method on any other versions of the GS3 but uoY_redruM and carrrnuttt (and others) have confirmed that this method works for the T-Mobile version as well. It should in theory also work for the AT&T and Verizon versions, though that's unconfirmed at this point.
Q: Ok, so I've got Root. What now?
A: That's entirely up to you. Root allows a near endless amount of customizatoin, but some of the most commonly sought after benefits of Root are these:
Root Only applications. These allow you to simply do more with your phone or tweak the way it functions. Some that I personally recommend are:
Titanium Backup and its Pro Key => For making backups of your apps, app data and system data and uninstalling or freezing Bloatware.
Quick Boot => For booting drectily to recovery or Download Mode (listed as Bootloader in the App)
Removing Bloatware => I recommend Titanium Backup for this
Loading custom ROMs. There aren't many floating around just yet, but I expect that'll change soon as the ball gets rolling.

Excellent write-up. Thanks. Now can we install custom roms from other forums or do we have to specifically wait for any to come up here.

Great write up! very easy and simple

daniel06gt said:
Excellent write-up. Thanks. Now can we install custom roms from other forums or do we have to specifically wait for any to come up here.
Click to expand...
Click to collapse
You should wait for any specific Sprint Galaxy S3 ROMs that get posted if you want to ROM your phone. I'm sure some will be popping up by the end of the weekend so I wouldn't expect that you'll have to wait too long

Excellent write up, though I don't see the difference in methods; maybe because I speed read it but if you follow noobnl's method, you basically do the same thing, minus the adb to set the permissions, though if you install busybox, its the same goal. Again great because some people are afraid of adb.

Very nice work... I'll get a how to video going very soon!

(repost, sorry)

Great write-up! Thanks for taking the time to do this.

Thanks for writing this up!

teh roxxorz said:
Excellent write up, though I don't see the difference in methods; maybe because I speed read it but if you follow noobnl's method, you basically do the same thing, minus the adb to set the permissions, though if you install busybox, its the same goal. Again great because some people are afraid of adb.
Click to expand...
Click to collapse
Yes, this and noobl's method are pretty much the same, the main reason for this post is to put the method into an easy-to-read step-by-step format that's easy for beginners to follow. Remember, we were all beginners at some point

I come from HTC so Odin is new to me, this guide is little more friendly than noobl's method. Although either would suffice this is just pretty clearly laid out.
Look forward to root.

Very nice and simple
Thank you. Now let the games begin....

cypher_zero said:
[...]Remember, we were all beginners at some point
Click to expand...
Click to collapse
While I expect a fair amount of carry-overs from Sprint Epic's and Epic Touch's, I also expect a large influx of excited users who haven't used a Galaxy S phone before.
:highfive:

How to video is done! Just have to compile and upload it

qbking77 said:
How to video is done! Just have to compile and upload it
Click to expand...
Click to collapse
Always on the ball qbking77 gotta add galaxy s 3 to your signature now =)

teh roxxorz said:
Excellent write up, though I don't see the difference in methods; maybe because I speed read it but if you follow noobnl's method, you basically do the same thing, minus the adb to set the permissions, though if you install busybox, its the same goal. Again great because some people are afraid of adb.
Click to expand...
Click to collapse
I hate adb that shiit is tedious LOL

tj.iscool said:
I hate adb that shiit is tedious LOL
Click to expand...
Click to collapse
You can always script a bat file or two, saves always rewriting commands.

tj.iscool said:
I hate adb that shiit is tedious LOL
Click to expand...
Click to collapse
I actually prefer adb over one click roots.
Something about seeing what your doing and sense of accomplishment lol

cypher_zero said:
Yes, this and noobl's method are pretty much the same, the main reason for this post is to put the method into an easy-to-read step-by-step format that's easy for beginners to follow. Remember, we were all beginners at some point
Click to expand...
Click to collapse
No qualms there, just making sure I didn't miss anything. Though you are right, it may be hard for a beginner to follow noob's more experienced cut throat guide. Kudos.

[HOW TO][GUIDE] VPN Without Security Lockscreen

I dont know how many other people out there use androids built in vpn, but i hate the fact that you are required to use a security screen (pattern, pin, password) to do so. I have found a way to bypass this if you are rooted. This has only been tested on the stock kk rooted ota. However i would think it is the same on almost any stock based rom.
This assumes you already have your vpn and a security screen setup and working.
Go to the market and download a root capable data base (db) editor. I use SQLite Editor which is a paid app, but im sure there are free ones too.
Open the db editor. SQLite Editor sorts it by the app (in this case Android System) the data base is associated with, others may not work this way and may require you to navigate to the db file directly (/data/system/locksettings.db).
Open locksettings.db and select the locksettings directory. Look for the line that says "lockscreen.password_type". Under the value colum it will show some random number. Select the line and edit the value to be 0 (zero). Save if required by your db app, and restart your phone.
When it reboots you should no longer have a security lock screen only the swipe up screen. When you go to settings - more - vpn, it will still say you need to setup a security lock. Hit CANCEL, and it will show you your list of setup vpn's. Select one and connect. Boom working vpn with no pattern, pin, password screen required.
To undo this just go to settings - security - screenlock, and setup a new lock pattern, pin, or password.
You can also disable the swipe up lock screen by editing the "lockscreen.disabled" value in the locksettings.db to be a 1 instead of a 0.

good write up, thank you sir.

Where did you get stock kk rooted?
Sent from my HTC One

I was already unlocked and s-off, so i ruu'd took the kk ota and then rooted it. But i believe santod has his thread in development where you can download the stock rooted kk rom.

an alternative method
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:

Alternative method
found it on another forum
The process does not require rooting its more like a bug
worked on my i9300 with 4.3 firmware
1. Add a VPN
2. Lock the device with a pin
3. Enter the pin wrong 5 times
4. Press OK to the message that pops up
5 Press Forgot Pin
6. Sign into your Google Account
7. Select pin lock
8. Press cancel.
and now u got unlocked screen with working vpns

the method works, but after I reboot, when I enter VPN screen is aks me for "password for credential storage"... how can I solve? thanks in advance

Hirishiolo said:
the method works, but after I reboot, when I enter VPN screen is aks me for "password for credential storage"... how can I solve? thanks in advance
Click to expand...
Click to collapse
Yeah i have the same issue (nexus 10 rooted 4.4.3 stock)

Hit cancel, and it should bypass it.

cmlusco said:
Hit cancel, and it should bypass it.
Click to expand...
Click to collapse
it should.... but it does not for me (Sony Xperia Z1 with CM11 4.4.3)

schickel said:
it should.... but it does not for me (Sony Xperia Z1 with CM11 4.4.3)
Click to expand...
Click to collapse
same for me, it does not work

ebackbone said:
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Click to expand...
Click to collapse
Thank you :good:

ebackbone said:
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Click to expand...
Click to collapse
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
i am on kk 4.4.2

vadimo said:
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
i am on kk 4.4.2
Click to expand...
Click to collapse
My locksettings.db is empty as well. Does anybody know why?

Geilerzucker said:
My locksettings.db is empty as well. Does anybody know why?
Click to expand...
Click to collapse
on mine one its not empty

Hirishiolo said:
same for me, it does not work
Click to expand...
Click to collapse
i also followed the tutorial now and same as you guys, doesnt work

worked for me initially on samsung mega (jellybean), but after reboot i'm getting the 'enter password for creditial storage' issue and pressing cancel doesn't solve it.
is there any other solution?

In 4.4 there is no such file
Code:
/data/system/locksettings.db
.. any ideas?

Clauu said:
In 4.4 there is no such file
Code:
/data/system/locksettings.db
.. any ideas?
Click to expand...
Click to collapse
Try a different file manager.
It failed like that for me with ES File Explorer,
but worked when I used SM File Browser.
---------- Post added at 10:53 AM ---------- Previous post was at 10:42 AM ----------
vadimo said:
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
Click to expand...
Click to collapse
Tap on the "QUERY *" button to see the file contents.
---------- Post added at 11:11 AM ---------- Previous post was at 10:53 AM ----------
pajenn said:
worked for me initially on samsung mega (jellybean), but after reboot i'm getting the 'enter password for creditial storage' issue and pressing cancel doesn't solve it.
Click to expand...
Click to collapse
What I do here: just type something.. anything, doesn't matter. At least one character.
Then on the next screen, where it asks to set up a lockscreen, just Cancel.
This seems to be necessary once per boot -- any password, different time or the same, works.
After that it lands me on the VPN manager screen, all functional.

Well I kind of messed up. I tried to open with SQLite but it would give me an error 14. So i decided to try to open just like that using ES Explorer and edit it like regular note(SQL is totally different I had no idea). Anyways i didnt edit anything but now i cant set a pin or any type of security on my phone. When i try to set up a pin it still shows a swipe and when i try again my Note 3 freezes and get an error message saying settings stopped responding.
Any idea on how to fix this? Im rooted and im running the latest firmware 4.4.2 if that helps.

[TUT]How To Obtain A Little Freedom

[Tut]How To Systemless Root+Root+More!
This was fully tested on SM-G928A;Baseband:UCU2AOJ1 on 5.1.1
Just in case needed //SM-G928A\\ **Full Odin Restore G928AATT2AOJ1**
$<Download Mode & Odin Systemless Root Flash>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.Odin 3.10.7
4.Kernel_Root_Android_5.1.1_AT&T_SamFirm.NET
5.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
____________________
Okay now assuming that everything has been required, we can begin.
Turn off your phone and open Odin with admin rights on the computer & connect your phone to the computer using the usb cable that comes with the phone.
On the phone now hold all of these following buttons down, Volume Down+Home Key+Power Soon after once you see the blue screen release those buttons and press the Volume Up key to enter Downloading Mode.
Now in Odin on the computer, it should have recognized your device now press the "AP" button and open up for example, "G928A_Kernel_Root_5.1.1_SamFirm.NET.tar.MD5" now just press start and sit back and relax and soon you will have Systemless Root!(Note your phone will reboot which is normal after the flash.
--------------------
#<Obtaining Root Access>
Requirements:
1.A Windows Computer
2.Your Phone Device SM-G92-0/5/8A
3.USB Drivers(Most of the time if connect the phone to the computer using the usb cord that comes with the device it will install all of the drivers if your computer is connected to the internet.
4.Flashed The Systemless Root
5.Kingo Root
6.Root Checker Cost $FREE
7.SuperSU Cost $FREE
8.BusyBox Cost $FREE
9.Developer Options (USB Debug)
____________________
Okay now assuming that everything has been required, we can begin.
Go into Settings>System>About Device & Enable Developer Options.(Keep tapping the "Build Number" category until it says Developer options have been enabled.
Connect your device with your usb that which comes with the phone on the computer. Open "Kingo ROOT" on your computer with admin rights, and once the program asks you to turn USB Debug on, go on your phone into Settings>System>Developer options and make sure it is enabled as well as usb debugging. Wait for kingo root to find your device and once found, it will ask you to either "Reroot,Root, or Remove Root, click "Reroot" then wait for it to start.(After it starts you should see on your phone the kingo root usb app pop-up and show the same thing you see on your computer)
After it is done it should confirm you have been rooted and will ask to donate.
Now you may exit out of the program on the computer and the phone and once out of the app and back on your phone, you will want to look in your app drawer for the kingo root "Superuser" and uninstall this. Then head on over to the playstore if haven't all ready and install "SuperSU" & "Busybox" if want to. Once have the SuperSU app open it and install the su binary updates with the "Normal" option not the recovery one since we don't have that.... & once done just press OK DO NOT REBOOT or you will bootloop and will have to use Odin to reflash your system of your phone to get it back working out of the box "state"
UPDATE Have a pc around and can still boot with root:
Yamaha169 said:
You can restart the device while rooted... but you have to have ADB to do so...
When you reboot ... you will get stuck at the ATT logo... at this point... plug your phone in to your pc...
Open up ADB (COMMAND WINDOW)
type in
ADB devices
until your device # appears in adb... (this can take a minute for your pc to find your phone) so don't panic
This means the phone is found...
From this point... type
ADB ROOT
ADB SHELL
YOU will now be inside the shell of the device with root permissions
Now type
setenforce 0
(MAKE SURE LOWERCASE just like seen. "setenforce 0" if do Setenforce 0 it won't be found.....)
This will set selinux to permissive ... allowing the phone to boot...
Someone with enough experience could probably create a selinux permissive stock kernel ... but I've contacted several developers with no response ...
Click to expand...
Click to collapse
Now open up the root checker app & click verify to see if you truly do have root.(You must grant root access so allow once it pops up.) Enjoy your root but never ever reboot.
UPDATE: How to Root If Possibly not allowing you to root!!!
Step one you will need to of downloaded "Android Studio
Step two you will now need to install all of the updates(Well that's what I did) inside the studio program.
Step three now locate 'program tools" which for me was located here: C:\Users\NameofComputer\AppData\Local\Android\android-sdk\platform-tools
Step four make a cmd.exe file to go in the platform-tools simply just clicking on the "start button" on windows and searching "cmd" then dragging the cmd file to the folder.(Rename it to something like ADB Root or something different than just cmd)
Step FIVE download the su binary which can be located HERE and place it in the "platform-tools" folder.
Step SIX now almost there. Open the cmd file(ADB Root.exe) and once opened, plug the phone into the computer with the cable that came with your phone.
Step Seven:^.^ now with the phone plugged in and the program start, type this command to make sure your device is found:
Code:
adb devices
and if found you will see your attached devices and if more than one or can't see your device, you can do
Code:
adb kill-server
command and it will restart adb.
Step Eight: MAGIC time lol now that your phone is connected and you can see it is indeed listed, type these commands as followed:
Code:
adb root
adb remount
adb push su /system/bin/su
adb shell
chown 0:0 /system/bin/su
chmod 6755 /system/bin/su
You don't really have to do the other commands after pushing su it's just for pre-caution.
Step Nine: Now do the following at the top and try to use the Kingo root once more and click root or reroot.
If this doesn't work try to press unroot and restart phone then try this again.
Also like down below I talk about if you did reboot before you unrooted, you can still unroot but sometimes it's tricky and it needs you to do the adb remount before will work so just remember that...
--------------------
$#$<UnRooting & Keeping Systemless Root So You Can Reboot & Reroot>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.Root Checker Cost $FREE
____________________
This is very simple and easy to do, all you must do after every root and before every reboot is to go into "SuperSU" and go into the settings and scroll down until you see "Fully Unroot" and click that and once done verify with the root checker that you are indeed unrooted but still have adb shell and once done that you may freely reboot with no bootloop and then if want root once more just use "Kingo Root" on the computer to reroot once more.(I'm hoping someone will come out with an app that does the same thing and works so we don't need the computer anymore which would make it much easier..)
Edit/Update:
I found that if you maybe forgot to unroot before a reboot that you can still unroot without the need of going into odin and reflashing stock system just by connecting your phone to the computer via the usb that which comes with your phone and opening up Kingo Root and waiting for it to find your phone then click unroot and wait for it after you have unrooted and you will hear a sound which means it's fixed! So just force shutdown the device with pressing both: Volume Down+Home Button+Power then it will boot back up as normal!
-------------------- ____________________ -------------------- ____________________
~My Findings Through Long Research & Errors~:
<How to Fix Wifi Bug That Comes With Flashing Systemless Root>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights)
3.SuperSU Cost $FREE
4.BuildProp Editor Cost $FREE
____________________
On your phone open up the "BuildProp Editor".
click on the search button and search for "ro.securestorage.support=true" now once found change the =true to =false and save. Now you must reboot for it to take place but remember to UNROOT before you reboot.
Now doing this your wifi will stay connected and you no longer have to enter your password millions of times so it will be nicer to keep systemless root.
--------------------
<How to Enable AT&T Hotspot System FULLYApp>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Root Explorer Cost $3.99
4.NEW Modded TetheringProvision .apk Cost $FREE(Also can be found in this thread in attachments.
5.ADB Root cmd knowledge or Download SQLite Editor Cost $2.99
6.BuildProp Editor Cost $FREE
____________________
Okay my fellow members that stayed on 5.1.1 with me, this tut did once work but then at&t blocked me and it stopped working but now rejoice becase there is a bypass once more!!!
NEW WAY:
I'm not sure which worked so I'm gonna just tell you everything that I did...
1.I first rooted obviously
2.I found a new TetheringProvision.apk which I have uploaded down in the attachment and at the top.
3.I used adb root for this but this can also be done with sqlite editior so I'll explain both ways, first way will be the easy way the adb root...>>>
Step 1: Ensure you have the correct OEM drivers installed for your handset on the computer
Step 2: Download and install the necessary ADB drivers (v1.4.2)
Step 3: Enable USB debugging on your Android handset:
Go to Settings > About Device, and tap the build number 7 times or until you see 'You're now a developer' message.
Return to Settings > Developer options and use the toggle button to turn on USB debugging. Then tap OK button to accept the warning and continue.
Step 4:Connect your device to PC with original USB cable.
Step 5: Launch a command window on your Windows PC.
Step 6: Access ADB shell and run the following command:
adb shell now just type " settings put global tether_dun_required 0 " and enter.
________----------Now the sqlite way
Step 1:Go into sqlite editor and allow root rights...
Step 2: Locate "Settings Storage" and click on "Settings.db then click on "global"
Step 3:Locate tether_dun_required 0 and if not there add by clicking on the +
then fill out name as " tether_dun_required " >>And value as " 0 " and then save file and unroot then reboot.
Now then after all of that I downloaded the build.prop which I know you don't have to but it makes it easier for me to do so and probably for you too...
Step 1:Get build.prop editor from the playstore and open it to grant root rights.
Step 2:Click on the pencil icon on the top right where the search icon is.
Step 3: Scroll all the way down to an open line.(If not one make one.)
and put this in the line....>>> " net.tethering.noprovisioning=true " and then click the save button at the top right and then save it and unroot then reboot.
Then replacing the Tetherprovision.apk . >>>
Step 1: Download the NEW modded TetherProvision.apk at top or at bottom.
Step 2: get a root explorer and go to System/App/TetheringProvision
Step 3: Rename the actual TetheringProvision.apk to TetheringProvision.apk.bak
Step 4: in the same location, go into "arm64" and rename the TetheringProvision.odex to TetheringProvision.odex.bak
Step 5: Now locate the modded TetheringProvision.apk you've just downloaded and place it in System/App/TetheringProvision/ now should be two TetheringProvision, the TetheringProvision.apk.bak and the modded one, TetheringProvision.apk.
Step 6: change the property promissions of the tetheringprovision.apk to give it root rights by changing the promissions to look just like the actual one which is " rw-r--r-- "
Step 7: save and unroot then reboot!
Now youre wifi tether and usb should work!!! enjoy!
--------------------
<How to disable OTA & Security Notification>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
____________________
Open up titanium back with pro license and freeze these following apps:
1.SecurityLogAgent(This is that annoying notification that which comes with the systemless flash root that keeps annoying you to reboot and undo what you done.)
AT&T Software Update(This will make it so AT&T won't push any updates to your device anymore so no need to worry about installing an update ota and losing your root or something else like bootlooping.
And again, all of this sticks after you unroot and reboot!
___________________________________________
<How to Get Youtube RED (Sort of) FREE!>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.OGYoutube Cost $Free
Basically all you do here is download the modded sort of youtube app(OGYoutube) and install it then done! You now can download videos/music on the app and have access to run audio in the background plus NO ADS!!! (if there are I haven't seen any yet...)
Best part of this too since can't be used fttb, no need for XPOSED apk!
_____________________________
<How To Install Viper4android>
Requirements:
1.Your Phone Device SM-G92-0/5/8A
2.Root Access(Superuser rights & .SuperSU Cost $FREE)
3.Fast Reboot
4.Soft Reboot
5.Viper4Android V2.3.4.0
6.Audio_Effect.Config
7.Titanium Backup & Titanium Backup Pro License Cost $Free | $5.99
8.IRS Impulse Response Sample files
9.Root Explorer Cost $3.99
~~~~~~~~~~~~~
To Read the tuts yourself than rather follow my tut, you may do so by following This Link & This Link
~~~~~~~~~~~~~~~~~~
Alright, I decided to do my own detail tut to make it much easier so follow me and you'll have viper4android in no time : )
So let's get begin, download if not already, the busybox,SuperSU,TitaniumBackup,Fast reboot,Soft Reboot, & Root explorer. Now having all that done open up Busybox and allow it root rights and you may wait for it to research for a smart intall, or just press install. Once you installed it in the default location System/xbin, click on the will be installed to location and choose System/bin and install it there too.(Not sure why but that's what the tut called for.)
Now let's download the folders for viper4android, go ahead and download Audio_Effect.Config.zip file,IRS Impulse Response Sample files, & the Viper4Android V2.3.4.0 folder.
Now open up the root explorer and unzip all that which is zipped up.(Which is all of the files;Audio_Effect.Config.zip file,IRS Impulse Response Sample files.zip, & the Viper4Android V2.3.4.0 folder.zip
)
Now once all are extracted, we will begin putting what is needed where.
Let's start off with the ViPER4Android_FX_A4.x (The actual name of the folder) you're gonna want to long press it and copy this folder. Once done, you're gonna want to paste this folder in System>Priv-app and make sure to change the permission of the .apk to 0644 rw-r--r-- & the FOLDER to 0755 rwxr-xr-x(The folder should have the same permissions as the other folders in that location.) which is inside the folder to give it root access which is 0644;rw-r--r-- and if not sure what root permission should look like, refer to this link Or Google what it looks like, then save/press ok.
Now go back to where you extracted your folders, and this time copy the "audio_effects.conf and go to System>etc and find and rename the actual audio_effects.conf to audio_effects.conf.bak and then paste the copied modded audio_effects.conf here & DONT FORGET change the permissions to give it root rights.
Now after all is done, open the app "Titanium Backup Pro" and look for and freeze these following applications: 1.Adapt Sound 4.0 & SoundAlive 3.0 now open the app "Soft Reboot (Root) and click yes you want to do a soft reboot. Then once back up(If want you can click the "Fast reboot app" to quickly refresh the system) and running you should see the viper app inside your app drawer. Open it and install the update/software when ask you to and once done it should ask for you to reboot just click on ok and then go out and back to the "Soft Reboot (Root) then do another soft reboot.
Now almost DONE!!! Once back up and running again, go to your root explorer again where you extracted the folders and grab the folder of "ViPER4Android and move it to your device storage ex; Storage/emulated/0 (It's where the download folder is and dcim folder is.. Then finally, go toSettings>Device>Sounds and notifications>Sound quality and effects and toggle on all of the listings[NOTE YOU MUST PUT EARPHONES IN FOR THESE TOGGLES TO SHOW]; UHQ Upscaler|SoundAlive+|Tube Amp Pro now you're done enjoy viper4android via editing the settings in the app.
Edit
You need to download SELinux Mode Changer and give root rights and just click on permissive mode and all done. Also might need to use compatible mode in the Viper4Android settings.
I found that this mod works with Pandora and Youtube app but not with google music or the default music app and not sure how to fix that....
__________________________________0
This is some more quick finds which you don't need a tut for just information I'd like to share so you all know.
I found out that you can use Titanium Backup Pro Cost $5.99 and freeze anything you want such as bloatware and that annoying notification that appears every time you reboot if have systemless root installed "SecurityLogAgent" and as long as you UNROOT before you reboot, it is safe and everything you froze stays frozen.
Now I haven't tried uninstalling any system apps so I wouldn't advise doing that unless you wanted to but I don't see the point except to free space up since you can just freeze anything and does the same thing except for freeing space....
I haven't been able to unlock the bootloader in my research and errors which probably never gonna happen anytime soon....
I also never found an app that could root the device yet without a computer....
And yeah that's it! I just was so happy to find out all of this and just had to share it with xda members which are on the same boat as me that has been wanting some "freedom" which now can have a piece of it. : )
If found these tuts to be helpful, feel free to hit thanks button and if want donate.

AngelRyu said:
Just gonna get right to it and be fast.
Odin Flash Kernel for systemless root.
obtain root
Download SuperSU
After rooted download some sort of buildprop editor and search for " ro.securestorage.support=true" Now change =true to =false. and save!
Now go into the superSU app and fully unroot then reboot and also keep adb shell root!
So you fix the wifi bug plus keep the adb shell so you can obtain root once more! Now we just need some app that can give root access with 1 click without needing a pc and this would work for me until we can actually reboot with root without it bootlooping anyways.... I still can't find a wifi tether app or a method that works for the at&t hotspot app though...
Click to expand...
Click to collapse
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?

fuzmik said:
Question for clarification.
So current method for rooting g928a is this systemless root.
Question 1, will it brick my phone with this root if i reboot, because i read somewhere on here that the phone will just keep on rebooting.
You mention using superSU app to unroot to reboot. So basically I have to unroot with superSU whenever I want to reboot then reflash again to get root?
Click to expand...
Click to collapse
Yes you must unroot to remove the su binary so the system acts like nothing has happen. I use kingo root for windows and it works every time with root all you need to do is hit "root" or it may say "reroot" and works every time. I have been playing with this a lot trying to do things to get it to reboot with root but have failed so far.... I wish someone with more experience would approach this so we could have an app to use at least so we not have to use pc every time to reroot until we get the ability to keep root and reboot.
Kingo root can be found here : https://www.kingoapp.com/android-root.htm
and this works after flashing the kernel from odin. This was the only way I actually found to be able to get root was with this because manually pushing su just didn't work for me....

Thanks for being much clearer on the instructions and idoit proof. I was worried about the bootloop and I thought there was no exit strategy on this expensive phone until you mention reflash. With your extensive tinkering on this, did your knox security trip up?
If this is the only possible way, maybe the community could make some sort of app that if we have to shutdown or reboot the phone specifically for g928a, it will safely unroot it for us.
TASKER?!

Anyone know if this still works after taking the latest OTA a few days ago?

The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.

tonys.94 said:
The problem is this isn't root. I restart my phone several times a day. There is no point especially if I can't get a custom OS. However, thanks for making the instructions clear. And for anyone who doesn't understand systemless root, it's temp root. When you reboot dmverity sees the false file structure and tries to rewrite and reverse the changes, effectively removing root. On the Note 5 AT&T for temp root you didn't have to unroot before reboot as it wouldn't boot loop, it would just remove root and let you continue on. So something in this version must be getting farther in breaking past dmverity if it's causing the OS to bootloop.
Click to expand...
Click to collapse
I was wondering if maybe we could place SU somewhere else so we might could trick it to reboot with root but haven't done it yet and or maybe keep SU on the sdcard/storage and use the terminal on the phone to push su to xbin every reboot but just hoping maybe can get root working without making the stupid thing bootloop.... Like I said I been doing a lot of dumb stuff with my phone because I have been so disappointed in this phone with not having wifi tether at the most really but now that got that I'm much happier but I'm still on the research of keeping root and being able to reboot.
I won't be updating until something maybe for sure comes along with 6.0 I can wait because my galaxy s4 I had stayed on stock version forever because was able to do everything so was no need to update really.... Anyways yeah lol maybe someone greater or maybe my playing around will work. WE can only hope...
Oh yeah, to the other guy NO it did not trip knox doing any of the things I've done. which I wouldn't care if could unlock the bootloader lol...
Edit:
I've done all I can think of and didn't work to keep root on a reboot except it did keep root without bootloop with a soft reboot...
I found out to maybe later will add tut up top but for now I'd like to tell you or whoever, if you do bootloop due to not being able to access the su unroot in time, you can still connect your device with Kingo Root in that bootloop and can unroot to save you from having to reflash every time... Might have to reboot as soon as you hear the found from the unroot though.
Oh and on a factory reset everything sticks excepts what was frozen becomes unfrozen just fyi...
Yeah, that's all I can find so I'm done with it hope someone can help later on but I'm just happy with wifi tether so much : )

So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?

O0Gjulian said:
So what all can we do with this root
Thank you for your hard work. it's very much appreciated!!!
Will pay part of my bounty which is 50 dollars pay day!!
But, please reply. what all can we do with this root!?
Click to expand...
Click to collapse
Hi, I didn't come up with anything but the fix for wifi bug and hotspot app.
I just made a very detail tut to help others, but thanks.
I would wait on the bounty to be paid to someone who can make it possible to keep root on and still be able to reboot.

So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.

Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.

antizombie said:
So in theory with this method I can root, install a modified tetheringprovisions, unroot (as hotspot is the only feature I actually desire), and go about my business without worrying about bootlooping or knox being tripped? Feels too good to be true, but I want to believe.
Click to expand...
Click to collapse
It's true, that's how my phone is rolling with frozen apps and the modded hotspot without root, but still the systemless root remains in the system but doesn't do anything with out a computer or applying the kingo root to true root it.
I haven't tested the adaway yet so idk if will work or not.... and I been wanting xpose to work to disable youtube ads but haven't tried that either. . I might root tonight and try out adway tho.
But yeah to your question you are 100% safe and will not change anything or trip anything; phone can reboot all it wants with no bootloops with the modded tether is what I'm trying to say lol .. .
Edit:
Yeah adaway works after unroot and reboot. . . But I decided not to use it because a lot of people us adfly and it wouldn't let me access the link so yeah.....
On another note I froze a lot of stuff and done a lot of things not sure which part caused it but it doesn't bother me because I don't use samsung pay but in the end I had to freeze samsung framework for samsung pay because it kept saying force closed but which again Idc about that app so no biggy to me : )

Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.

antizombie said:
Was Samsung Pay crashing before you started freezing apps? I have yet to use Pay but I'd prefer to keep my options open if possible.
Click to expand...
Click to collapse
Honestly, I'm not sure but it had to be either the freezing at&t update or securityagent because it seemed to happen after that... Or could be the hotspot mod but I didn't get any crashes until i froze those 2 apps so idk...

Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
navalynt said:
Just a reminder that Android 6.0.1 is right around the corner. If you don't fully go back to stock before the upgrade it will not flash and could possibly wipe the data partition. Both the system and boot images need to be 100% stock.
Click to expand...
Click to collapse
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!

I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):

O0Gjulian said:
I can confirm this works. Sorta a pain to have to reroot but hey, It's progress. We may never have a custom ROM option or recovery, But this is the next big thing. If we can find a app that'll just reroot us. it's perfect. (somewhat) Just rooted a few minutes ago. Going to play around. More than likely I'll re flash stock and make a youtube video for anyone needing questions or wanting to see it be done.
And I lied.. So, My experience was weird. Lagging constantly and weird download issues with a fresh wipe.
I'm sadly gonna have to unroot and hope that a better method would come out.
):
Click to expand...
Click to collapse
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Also @
joe3681 said:
Package Disabler in play store freezes apps so what's the point?
Can you fully remove with TiBu and be safe unrooted?
---------- Post added at 03:55 PM ---------- Previous post was at 03:40 PM ----------
Yeah and from what I've seen of the nightmares people have been having with their Note 5's on Marshmallow, I'm staying FAR away from it!
Click to expand...
Click to collapse
I can confirm freezing anything won't harm the system on a reboot after unrooting but not sure about removing the apps would be safe. I have however remove the youtube app and reinstalled it in play store and it didn't harm anything.

AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse

O0Gjulian said:
AngelRyu said:
I'm not sure why you would experience "lag" because I have no lag what so ever. Maybe try going to settings>system>developer options and change both transition animation scale and window animation scale to 0.5x
I've reflashed stock many of times due to to trying to find everything there is to find and I've had no "lag" but also you could download the soft reboot and fast reboot from market. Fast reboot frees up memory via closing and restarting certain apps, and soft reboot kills zygote and does a "hot reboot" without going through whole start up process .
Please reply I'm gonna try and help you : )
Thanks for helping me! I went ahead and flashed stock and followed your steps!
Working great now!
NOW, My next question... What difference would it make if I used package disabler pro VS TBU?
Wouldn't both of these apps freeze the processes? Or would it make a difference with root and SU access?
Click to expand...
Click to collapse
I'm not sure because I've never heard of that program, but I did buy it just now for about $1.89 and the activation keeps failing so I can't test it to see the difference but with titanium you can do everything not just freeze stuff but back up apps and their data and much more.
Titanium backup has been around for ages which is why I recommend it.
Click to expand...
Click to collapse

I use package Disabler. Works like TiBu without root. Only reason to root would be to fully remove apps but would it boot okay after?

[GUIDE]Enable auto brightness in custom roms

Hello everyone, I want to share how to enable auto brightness also known as adaptive brightness to custom roms for redmi 7.
Steps to enable auto brightness:
1. Download the attached apk
2. Navigate to /system/vendor/overlay using any file explorer which supports root. I will recommend ES File Explorer
3. Now copy the apk file to the navigated path
4. Set the apk permissions to 0777. If you are using ES File Explorer, then skip this step.
5. Reboot your device
6. Go to Settings > Display > Adaptive Brightness and enable it.
Don't forget to hit the thanks button
Note: This solution was found by @BoomBoomsss and was posted on 4PDA. I am just sharing his solution.

I am sorry that I couldn't give you credit on my post. But I am pretty sure that you have misunderstood me.
First, I didn't know that you are on XDA or what's your XDA profile. That's why I can't give you credit. But now I know. I will give you the credit on this post.
Secondly, I didn't say it's my work I just wanted to everyone hit the thanks button. I was looking for auto brightness for so long. But couldn't find a solution. That's why I thought I should share the solution with everyone.
Last thing, Sorry once again.

Tried the step by step guide, but I can't copy or move the apk to the specified folder... Sometimes the app points an error, but sometimes it says it copied/moved successfuly, but when I reboot nothing happens. Tried with ES File Explorer, and other apps as well. Any ideas?

prezoto said:
Tried the step by step guide, but I can't copy or move the apk to the specified folder... Sometimes the app points an error, but sometimes it says it copied/moved successfuly, but when I reboot nothing happens. Tried with ES File Explorer, and other apps as well. Any ideas?
Click to expand...
Click to collapse
Yes. Follow these steps:
Open ES file explorer
Go to menu > Tools> Root Explorer
Select Mount R/W
Select '/' and 'vendor/' to RW
Click Ok button
Restart your phone. Now follow the main steps and reboot again.
Sorry for being late. ?

Not working
I've followed your procedure, everything worked fine except the autobrightness doesn't. Brightness slider doesn't work at all.
My setup:
- redmi note 7
- vendor stock
- rom: lineage os 17 gsi from andyyan
- microg working
- phh-magisk
My question is, should i delete the only other file in /system/vendor/overlay which has almost the same name? Or what else can i do?
Thanks in advance
Edit: found a fix: in this telegram group @Lavendergsi
Search for brightness fix lavender and rename the zip so doesnt have spaces anymore. Flash via orangefox