I get a lot of requests to remove the NavBar. I'm posting this mod at each phone's forum themes section. TWRP flashable zip. Restore zip will be created in a folder named ozop on your sdcard.
Pixel 8.0 November update
https://www.androidfilehost.com/?fid=673791459329061051
Pixel 8.1
https://www.androidfilehost.com/?fid=673791459329061778
Installation instructions for those of you that have root, but do not have TWRP. Busybox must be installed first.
1. Download the enclosed vrthemeADBversion zip and readme.txt for copying and pasting purposes.
2. Unzip the vrthemeADBversion zip to your sdcard. Rename folder to vrtheme
3. Put the readme.txt on your PC where you use adb.
4. Download appropriate NavBar Gone zip. Unzip and copy the system folder that is inside the vrtheme folder to the root of your sdcard.
5. On the root folder of your phone, find the data folder and create a folder inside it named tmp
6. Copy the vrtheme folder you earlier extracted to your sdcard to newly created data/tmp folder (/data/tmp/vrtheme)
7. On PC, with your phone connected and in file transfer mode, open CMD prompt and type "adb devices" without quotes. If your serial number comes up you can proceed.
8. Copy and paste the command lines from the readme.txt (include quotes)
adb shell su -c "mount -o rw,remount /system"
Hit enter
First time you will be promoted by SuperSU to give adb permission.
Copy and paste the second line in readme.txt
adb shell su -c sh /data/tmp/vrtheme/installtheme.sh
Wait until everything runs, after a pause of a few seconds your phone will reboot and your NavBar should be gone.
THANK YOU. works great (flashed zip in TWRP).
Are we going to need a monthly zip after every OTA update? Any tips on how to make this ourselves. Looks like this would make a great Magisk module.
poolemit said:
THANK YOU. works great (flashed zip in TWRP).
Are we going to need a monthly zip after every OTA update? Any tips on how to make this ourselves. Looks like this would make a great Magisk module.
Click to expand...
Click to collapse
Depends on the update. Most don't evolve the framework-res.apk and SystemUIGoogle.apk and that is what is modded. Once flashed, you have what you need to make a magisk module. Pull those two apks and there you go. This is device specific though.
How would I undo this?
shagbag913 said:
How would I undo this?
Click to expand...
Click to collapse
It should have created a restore zip called ozop in a folder called the same on your sdcard
Tulsadiver said:
It should have created a restore zip called ozop in a folder called the same on your sdcard
Click to expand...
Click to collapse
Oh ok. Thanks!
---------- Post added at 04:50 PM ---------- Previous post was at 04:28 PM ----------
Would it be possible to remove the navbar systemessly? I'm trying to still be able to accept ota's.
shagbag913 said:
Oh ok. Thanks!
---------- Post added at 04:50 PM ---------- Previous post was at 04:28 PM ----------
Would it be possible to remove the navbar systemessly? I'm trying to still be able to accept ota's.
Click to expand...
Click to collapse
My mod passes safety net so maybe you can still accept ota's.
Just thought I would let you know, I flashed this mod in twrp on Android 8.1 and it's working beautifully.
Does this work for Marlin?
krazekid7 said:
Does this work for Marlin?
Click to expand...
Click to collapse
I have a navbar gone thread on the Marlin forum.
I flashed this on the final 8.1 build and it bootlooped, but the ozop restore zip fixed it. Did they change something with the apk's?
If someone will upload SystemUIGoogle.apk and framework-res.apk from 8.1 Dec Final I'll make a NavBar Gone and some other mods as well.
Tulsadiver said:
If someone will upload SystemUIGoogle.apk and framework-res.apk from 8.1 Dec Final I'll make a NavBar Gone and some other mods as well.
Click to expand...
Click to collapse
Here are the files from 8.1 December. I've been unable to get apktool to work well with them, and making any mods to them lead to boot issues. They both had some undefined terms, and some 9.png issues.
I hope you are able to make it work. I specifically am hoping for the 30 dpi NavBar and more qs tiles.
https://www.dropbox.com/s/fj3j8tzndraw05k/framework-res.apk?dl=0
https://www.dropbox.com/s/4jax22gr00h6xq2/SystemUIGoogle.apk?dl=0
stranula said:
Here are the files from 8.1 December. I've been unable to get apktool to work well with them, and making any mods to them lead to boot issues. They both had some undefined terms, and some 9.png issues.
I hope you are able to make it work. I specifically am hoping for the 30 dpi NavBar and more qs tiles.
https://www.dropbox.com/s/fj3j8tzndraw05k/framework-res.apk?dl=0
https://www.dropbox.com/s/4jax22gr00h6xq2/SystemUIGoogle.apk?dl=0
Click to expand...
Click to collapse
More qs columns or tiles? I can do columns.....
Tulsadiver said:
More qs columns or tiles? I can do columns.....
Click to expand...
Click to collapse
Columns, my mistake
stranula said:
Columns, my mistake
Click to expand...
Click to collapse
Thank you for the files. I normally go down to 32 dip but I'll include a 30 dip as well. Please remind me if I forget. My aroma will include, 4 as stock, but 5, 6,and 7 column options.
Tulsadiver said:
Thank you for the files. I normally go down to 32 dip but I'll include a 30 dip as well. Please remind me if I forget. My aroma will include, 4 as stock, but 5, 6,and 7 column options.
Click to expand...
Click to collapse
Even 32 would be good. That sounds awesome. Thanks for putting it together, much appreciated.
stranula said:
Here are the files from 8.1 December. I've been unable to get apktool to work well with them, and making any mods to them lead to boot issues. They both had some undefined terms, and some 9.png issues.
I hope you are able to make it work. I specifically am hoping for the 30 dpi NavBar and more qs tiles.
https://www.dropbox.com/s/fj3j8tzndraw05k/framework-res.apk?dl=0
https://www.dropbox.com/s/4jax22gr00h6xq2/SystemUIGoogle.apk?dl=0
Click to expand...
Click to collapse
I have an Aroma for you to try. Install the base at the bottom first. There are NavBar height and column mods you can flash after that. I'm not on 8.1 so this has not been tested.
Aroma
https://www.androidfilehost.com/?fid=889964283620771508
Tulsadiver said:
I have an Aroma for you to try. Install the base at the bottom first. There are NavBar height and column mods you can flash after that. I'm not on 8.1 so this has not been tested.
Aroma
https://www.androidfilehost.com/?fid=889964283620771508
Click to expand...
Click to collapse
I installed the base, followed by 6qs columns, followed by 32 NavBar. No problems at all, everything flashed properly and is working properly. Thanks so much for putting it together, I really appreciate it.
Tulsadiver said:
I have an Aroma for you to try. Install the base at the bottom first. There are NavBar height and column mods you can flash after that. I'm not on 8.1 so this has not been tested.
Aroma
https://www.androidfilehost.com/?fid=889964283620771508
Click to expand...
Click to collapse
Some features of your normal aroma package are missing, of course. Most of the options seem to work, but the navbar icons are a bit messed up. I used the Lite Blue Navbar icons option. Picture attached.
Related
Guide – Change Navbar D.P.I. in Android Jelly Bean (4.1.1)
•Thanks to Vomer for helping me learn this and answering my questions when I had them… Also for persuading me to write this guide for others users to hopefully use to learn a small bit of Android modding, which will hopefully create more publically used mods for the benefit and growth of the community. Let’s get it…
First thing is first… This guide is created with the Galaxy Nexus in mind. Even though other phone brands (Samsung, H.T.C., LG, Sony, etc.) are now upgrading their handsets to Android Jelly Bean, this guide is created with my experience with the pure Google experience in mind and pure Google O.S. *If you are using a rom with Samsung Touch Wiz, H.T.C. Sense or anything else produced/provided by another company, this isn’t for you, although it may answer some questions and get you started in the right direction…
THE TOOLS:
I’m using an ApkTool package, which were obtained from a thread created by monstaX < Credit to him!
First off, go to this webpage http://www.mediafire.com/?acrgcd0w850q0gj and download the file. File name should be “apktoolsJB.zip”. Once you have the tools downloaded, unzip them to your desktop.
Inside the unzipped file, you will locate the following files; aapt.exe; apktool.bat; apktool149.jar; apktool142.jar; apktool144.jar and baksmali.jar.
After confirming that the above listed files are present, rename “apktool149.jar” to “apktool.jar”.
That’s it for the tools, leave the file on your desktop, as this will ultimately be your workspace along with a command prompt.
I would also download 7-Zip and Notepad++ from the internet. You can Google those two programs and download them if you don’t already have them….
GETTING WINDOWS READY:
The next thing we need to do is remove the “Environmental Values”. If you have attempted to edit/mod any apks in the past, you probably set up “Environmental Values” in “Path” under “System Variables”. If you have done this, simply navigate back to “System Variables>Path” and delete the added non-sense that you added before. An example would be something like “Android\SDK\platform-tools\;” Make sure that after you’re done deleting, you leave a “;” at the end of the “Path Variable” line of text.
Now for the fun part:
DECOMPILE/COMPILE
Once you have done the above steps, you’re now ready to have some fun.
First off, you need to download a copy of the .zip file of the ROM you’re using onto your computer OR transfer a copy of the framework-res.apk and SystemUI.apk to your computer from your G-Nex. Once you have located these files, you need to place both files into the JBapktool folder that we unzipped onto the desktop earlier.
Once you have placed both files into the JBapktool folder, open the folder and shift+right-click somewhere inside the folder (NOT ON A FILE). Once you have done that and a menu has popped up, select “Open Command Window Here”.
Once the command window has opened; you need to install the framework-res.apk… Now there is a bunch of technical jargon for this but simply and easily type the following command;
java –jar apktool.jar if framework-res.apk
You will see a line that reads “ Framework installed to: C:\Users\yournamehere\apktool\framework\1.apk”
After the above line appears, you will now decompile the framework-res.apk file. To do this, type the following command;
java –jar apktool.jar d framework-res.apk
You will now see something like:
I: Loading resource table…
I: Loaded
I: Decoding file-resources…
I: Decoding values*/* XMLs…
I: Done
I: Copying assets and libs…
*DON’T CLOSE THE COMMAND PROMPT*
After you see that, you should notice that a new file has been added to the JBapktool folder, which should be named “framework-res”. Inside that folder, you will observe the following folders/files; assets; build; dist; res; AndroidManifest.xml; apktool.yml. The file that we are worried about is the “res” file. Open the “res” folder and then navigate to the “values” folder and look for a file named “dimens.xml”. The “dimens.xml” is where the magic happens. Right click on this file and open as “Edit with Notepad++”.
Once Notepad++ is open with the “dimens.xml” file open, you want to focus on three strings in the file. The strings are: 36.0dip
36.0dip
32.0dip
*For a 32 DPI nav bar, I personally use 32 for the height and 28 for the width.*
Now here, the parts of the string that we want to change are highlighted in yellow and represent the “DPI” of the nav bar. The above lines are from a “dimens.xml” file that I changed to make a “36 DPI” nav bar. Once you have made the changes to the above dimensions, just click file and save in Notepad++ and close the program.
Now to compile the “framework-res” folder back into an .apk.
Simply go back to the command prompt that we opened earlier (you shouldn’t have closed it, but if you did follow steps above to open a new one, reinstall the framework-res.apk (STEPS ABOVE) and then continue).
Type the following command;
Java –jar apktool.jar b framework-res
You will see the following (hopefully);
W:Could not find sources
I:Checking wheter resources has changed…
I:Building resources…
I:Building apk file…
After this, you should revert back to the “JBapktool” folder and navigate to “framework-res” folder>”build”>”apk”… Look for the “resources.arsc” file. THAT’S THE MONEY SHOT…
Using 7-zip, you want to open the “framework-res.apk” file that we originally began with (I would make a copy of it and put it on my desktop). Right-click on the “framework-res.apk” file, click 7-Zip and then open archive. A new window will open, showing the visible files inside the framework-res.apk. Look for the file “resources.arsc”. Delete it, locate the “resources.arsc” from the framework-res folder (framework-res>build>apk) in the JBapktool folder. Click and drag it to the unzipped original framework-res.apk file and drop it. WE’RE DONE WITH THE FRAMEWORK-RES.APK FILE.
Now simply place that file in a CWM flashable .zip file and hold tight.
Now we need to decompile the SystemUI.apk that we placed in the JBapktool folder earlier. Follow the above listed instructions to complete this, same as we did with the framework-res.apk.
Once you have the SystemUI.apk file decompiled, look for a folder in JBapktools named “SystemUI”. Inside the “SystemUI” folder, navigate to res>layout>navigation_bar.xml. We now want to open the navigation_bar.xml file with Notepadd++, so that we can delete two lines in it that would cause a larger back button on the nav bar if left intact.
Inside the navigation_bar.xml file look for the following two lines:
"@drawable/ic_sysbar_back" android:scaleType="center"
"@drawable/ic_sysbar_back_land" android:scaleType="center"
Now, we want to delete the following from both lines:
android:scaleType="center"
After deleting that line from both lines, save the file by clicking file>save and close Notepad++. Now back go back to JBapktools and to the already opened command prompt window (it should still be open).
We are now going to compile the SystemUI. To do this type the following command;
java –jar apktool.jar b SystemUI
You will see some text in the command prompt and will ultimately see I:Building APK file…
Once this is complete, navigate back to the JBapktool folder and to the SystemUI file. Once you have the SystemUI folder open, we need to navigate to build>apk and look for the following file; AndroidManifest.xml. Now this is important, we need to replace this file with the AndroidManifest.xml file from the original unzipped SystemUI.apk. So open the original SystemUI.apk with 7-zip, and copy “META-INF” and “AndroidManifest.xml”. Once you have those copied from the original unzipped SystemUI.apk, relocate back to the JBapktool folder>SystemUI>build>apk and paste both of them. If asked to replace, CLICK YES OR REPLACE ON ALL WARNINGS THAT POP UP!!!!
Now we need to back out to the SystemUI folder in JBapktool and click on the folder that is named “dist” (the “dist” folder is where the freshly compiled SystemUI.apk is located once we type in the compile command in the command prompt). Once inside the “dist” folder, you will see a SystemUI.apk file. DELETE IT… We never use the first SystemUI.apk that we compile, because we needed to added the META-INF and AndroidManifest.xml files for signing purposes. Once you have the 1st compiled SystemUI.apk deleted, return to the command prompt and enter the compile command again and compile a 2nd SystemUI.apk.
The 2nd SystemUI.apk will appear in the “dist” folder and is the usable SystemUI.apk.
Now that you have your new SystemUI.apk compiled, place it in the same CWM flashable .zip file, boot into recovery, wipe cache and dalvik cache and VOILA, you have just pimped your nav bar’s DPI.
•Remember when placing the SystemUI.apk file into your CWM .zip file to place it under /system/App. And when placing your framework-res.apk into your CWM .zip file it goes under /system/framework…
The mods and this guide take time for us to put together for your enjoyment/the improvement of the community. If I or anyone else has helped you, please hit the “Thank You” button. Thanks.
Great tutorial
Sent from my Galaxy Nexus using Tapatalk 2
Thank's man.....................
APatte111: could you upload your 32 height 28 landscape framework-res for v4 rom ?
Great guide.
If you dont want to waste time uploading....its all good anyway mate :good:
bs android said:
APatte111: could you upload your 32 height 28 landscape framework-res for v4 rom ?
Great guide.
If you dont want to waste time uploading....its all good anyway mate :good:
Click to expand...
Click to collapse
This is not the mods thread
Great job bud!
Also, remember guys - if you make a MiNCO Mod - share with other's in the MiNCO Plus+ Thread. Chances are someone else would want it too
bs android said:
APatte111: could you upload your 32 height 28 landscape framework-res for v4 rom ?
Great guide.
If you dont want to waste time uploading....its all good anyway mate :good:
Click to expand...
Click to collapse
This framework-res.apk is in place in several of the mods in the MiNCO Plus+ mods and enhancements thread that vomer began... Just download one of the mods and extract the framework-res.apk from one of the .zip files... Probably the easiest way to get it...
Sent from my Galaxy Nexus using xda premium
vomer said:
This is not the mods thread
Great job bud!
Click to expand...
Click to collapse
OK sorry for asking OP if that annoys you
APatte111 said:
This framework-res.apk is in place in several of the mods in the MiNCO Plus+ mods and enhancements thread that vomer began... Just download one of the mods and extract the framework-res.apk from on of the .zip files... Probably the easiest way to get it...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Nice APatte, I saw it now, downloaded and tried your framework with vomers standard white for minco rom. Got the failure in back button so guess I have to wait till I get home to a computer to fix it. Thanks for the guide anyway, love different and smaller navbars.
bs android said:
Got the failure in back button so guess I have to wait till I get home to a computer to fix it. Thanks for the guide anyway, love different and smaller navbars.
Click to expand...
Click to collapse
Yeah, if by "failure" you mean the larger back key then that is being caused by the un-edited navigation_bar.xml file which is located in SystemUI.apk>res>layout... You need to delete the two lines mentioned above, re-compile the SystemUI.apk and everything should be golden. Let me know if it doesn't work and I will help ya... Good Luck
Good guide!
Great job man!! Great tutorial!
:good::good::good::good::good:
MAN CHANGE THIS IS WRONG!! Java –jar apktool.jar b frame-work
IT IS java -jar apktool.jar b framework-res
masterchif92 said:
MAN CHANGE THIS IS WRONG!! Java –jar apktool.jar b frame-work
IT IS java -jar apktool.jar b framework-res
Click to expand...
Click to collapse
Thanks, you found a typo and the one mistake in the whole guide... Appreciate that...
Sent from my Galaxy Nexus using xda premium
After looking at 5 or 6 other guides. This one is BY FAR the easiest to understand & includes everything you need to get the job done.
Thanks a ton OP!
i cant seem to find the "@drawable/ic_sysbar_back" & "@drawable/ic_sysbar_back_land" in the navigation_bar.xml file. Any help please? I must mention that i am on AndroidME CM10 1.7.0 and took both files from the cwm zip.
Only repeating line i can find is "@drawable/ic_sysbar_lights_out_dot_large" . Dont know if it is the same.
I ve done some android developing in the past. every linear_layout represents a button, right?
angelossssss said:
i cant seem to find the "@drawable/ic_sysbar_back" & "@drawable/ic_sysbar_back_land" in the navigation_bar.xml file. Any help please? I must mention that i am on AndroidME CM10 1.7.0 and took both files from the cwm zip.
Only repeating line i can find is "@drawable/ic_sysbar_lights_out_dot_large" . Dont know if it is the same.
I ve done some android developing in the past. every linear_layout represents a button, right?
Click to expand...
Click to collapse
Can you upload the navigation_bar.xml file for me so I could have a look...
*** Nice signature by the way *** LOL
Sent from my Galaxy Nexus using xda premium
APatte111 said:
Can you upload the navigation_bar.xml file for me so I could have a look...
*** Nice signature by the way *** LOL
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
here. i uploaded in my dropbox.
https://www.dropbox.com/s/7331l8fqs7a99yg/navigation_bar.xml
Thanks for the signature
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
angelossssss said:
here. i uploaded in my dropbox.
https://www.dropbox.com/s/7331l8fqs7a99yg/navigation_bar.xml
Thanks for the signature
Click to expand...
Click to collapse
actually nevermind that... i just flashed the cwm without the systemui.apk and it seems to be working fine. lol
angelossssss said:
here. i uploaded in my dropbox.
https://www.dropbox.com/s/7331l8fqs7a99yg/navigation_bar.xml
Thanks for the signature
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
actually nevermind that... i just flashed the cwm without the systemui.apk and it seems to be working fine. lol
Click to expand...
Click to collapse
I was going to say, it looks like they have already removed that from the navigation_bar.xml file... The description of the ROM shows that Nav Bar Options are included... You could change the DPI size, compile and see if the back button is larger (which is what deleting those two lines fix)... If it's not (which you stated it's working) then skip that step....
APatte111 said:
I was going to say, it looks like they have already removed that from the navigation_bar.xml file... The description of the ROM shows that Nav Bar Options are included... You could change the DPI size, compile and see if the back button is larger (which is what deleting those two lines fix)... If it's not (which you stated it's working) then skip that step....
Click to expand...
Click to collapse
y i only compiled the framework-res.apk but i thing now my phone became a little laggy. especially when swipping between screens and opening apps.
i'll check it out if i did anything wrong.
angelossssss said:
y i only compiled the framework-res.apk but i thing now my phone became a little laggy. especially when swipping between screens and opening apps.
i'll check it out if i did anything wrong.
Click to expand...
Click to collapse
Check in the ROM and see if there is already a built in option to change the nav bar DPI size... if not, make the changes to the dimens.XML file and then recompile/replace the .apk and re-flash... that should work and everything should be normal...
Sent from my Galaxy Nexus using xda premium
APatte111 said:
Check in the ROM and see if there is already a built in option to change the nav bar DPI size... if not, make the changes to the dimens.XML file and then recompile/replace the .apk and re-flash... that should work and everything should be normal...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
unfortunately there is not. it only has options to change the buttons order.
Like many of you new flashers, I have flashed the SkyDragon ROM and have noticed that there is no connectivity to the computer whatsoever, so I did a little digging. I went back and forth between 2 Nandroid backups and kept flashing parts of them until I could narrow down where this problem was coming from. I found out that it comes from the specific folder - data/property
There is a missing file called persist.sys.usb.config ,13B in size, and I have no idea what it does (maybe some of you could enlighten me) but throwing the old file into that folder, changing the permissions to rw-------- and rebooting worked like a charm.
I apologize for not sticking this into the development thread, however I'm a lurker with no input! :victory:
Without further ado,
I TAKE NO RESPONSIBILITY FOR ANY BORKEN DEVICES. IF YOU DON'T KNOW WHAT YOU'RE DOING, DON'T DO IT!
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
----------------------------------------------------------------------------------------------------------------------------------------
Steal this information, spread it around, someone post it to the development thread and make this ROM better!
If you're having any problems, don't hesitate to ask
i could just drop this in the proper location before flashing the rom yes ??
CheesyNutz said:
i could just drop this in the proper location before flashing the rom yes ??
Click to expand...
Click to collapse
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.
88keys6strings said:
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.
Click to expand...
Click to collapse
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
As long as it's after the wipe then yes. If you opened up the zip that contains the ROM, you could head into /data then create a new folder called property and throw the file in there then zip it back up and flash it. But you MUST put the file in /data/property AFTER you flash the ROM. You could drop the file into a downloads or media folder because those don't get touched then flash the rom then move it and change permissions then reboot as well.
So no, you cannot drop the file in it's PROPER location before you wipe, otherwise it'll get deleted. However, you can copy/paste it into say, mnt/sdcard/Download, via your root browser, beforehand then follow my instructions
I'll try when I get home in about six hours.
partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
For sure! Will await results
I hope the developers get to see this for the next update
I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.
Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat.
Just a preliminary finding. I'm not well versed enough to explain it further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
I may have overlooked something. I deleted some usb portion of the build.prop. Didn't change anything so i didnt think about it. If you make a backup then edit it deleting the usb part, then reboot that might get it to work.If you need specifics, I'll be next to a computer in about an hour and a half
Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851
Skizzy034 said:
Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851
Click to expand...
Click to collapse
Awesome! Glad it worked for you
This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.
Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
Jephre said:
I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).
Click to expand...
Click to collapse
partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
UPDATED
Much easier now. Just tested it with a Nand that didn't work at all and followed the instructions and it worked flawlessly. Let me know if you have any more issues
aclegg2011 said:
This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.
Click to expand...
Click to collapse
It should work just fine as long as you didn't actually compress it lol. Thank you for the upload!
ALSO
THIS IS MY 10TH POST!!! DEV SECTION HERE I COME!! :victory:
88keys6strings said:
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
Click to expand...
Click to collapse
I can now confirm that this does work. I now have working MTP again.
You guys could try adding "persist.sys.usb.config=mtp,adb" to the build.prop and see if that works.
This is a Magisk Module Maker that converts various Mods of mine into TWRP flashable Magisk Modules.
Flash the Aroma installer in TWRP. Select and flash all the enclosed mods you want (after each selection is flashed and you want more, hit next, tick the check box at the top of the page, hit Finish and it takes you back to select more). When done, hit Finish. You will back in TWRP, hit the back button and go to Install. Find a folder on your sdcard called "Magisk". Inside there is a Magisk module called "Magisk.zip". Flash and reboot. These are the same mods from my other post but are for people using Magisk.
Now an Add-On selection in case you flash several mods but forgot or want to change some. It is the second selection. Flash it after you have flashed any additional mods. Afterwards, find and flash the Magisk.zip
Options
Internet speed - Up over Down- select position far left or to left of Icons on the right side, or center of statusbar. Indicators can be colored individually 6 different colors
Optional internet speed, single line. Strongest signal is shown. Left side, center, and by WiFi placements are available. Same color options.
Clock position - Center Clock not showing on Lockscreen
Dynamic Navbar, 8 sizes
Regular Navbar, 8 sizes
Battery text, with or without Battery Icon
Invisible screen-off Power Menu Button on far right hand side of status bar with option to remove.
Option of Invisible screen-off Power menu button on right side of Navbar in portrait mod and/or on the top side in Landscape mode.
Dpad left and right on the Navbar, poitrait and landscape options.
3Minit Battery
Settings Theme Colors
QS background Theme Colors
Colored Statusbar Icons - 6 to Choose From
Colored Navbar Icons - 6 to Choose From (Matches Statusbar)
Colored notification backgrounds
Colored notification text
Custom one percent battery mod enabler and 7 custom batteries to choose from.
Colored Halo Ring. You can match the other colors if you choose to.
Rainbow Battery
If you are going to install 3Minit Battery, you must install the 3Minit Resources apk, Prior to flashing that module.
I have flashed most of these myself but as always, have a backup. Signature disabling and Black Google bootanimation, loud effect ticks aren't working at this time. Flash at your own risk.
Credits:
topjohnwu for Magisk
https://forum.xda-developers.com/apps/magisk
aureljared for his enhanced VRthemer called Eviltheme
https://forum.xda-developers.com/showthread.php?t=2774436
djb77 for pairing the two together and making an "On the Fly" Module Maker
https://forum.xda-developers.com/apps/magisk/mod-magisk-module-template-eviltheme-t3590766
3 Minit Resources apk
https://www.androidfilehost.com/?fid=529152257862670024
Magisk Module Maker
https://www.androidfilehost.com/?fid=961840155545584994
Mega
https://mega.nz/#!NQJlXZxA!ZoOCKke5wPxPqi432ivDOiNWpYnb0f2ZnBGQAODRWiE
Hi!
Thanks for all your help in the other thread.
I am trying to figure out exactly what steps I need to take as this whole thing is pretty confusing. Lets just say all I want to do is have a day of the week show up in the status bar. What steps am I missing here?
1. decompile the framework framework-res.apk and install it
2. decompile the SystemUIGoogle.apk
3. go into the SystemUIGoogle.apk FOLDER and look for status_bar.xml
4. Change out the code
5. Save the status_bar.xml
6. Place the newly edited status_bar.xml in my eviltheme folder in /system/priv-app/SystemUIGoogle
Now obviously I am way wrong but I thought that was the whole point; that this thing just pulls the XML instead of messing with my APKs? Can you please help me with the steps that I am doing wrong? Or am I not understanding this program correctly?
daddylonglegs said:
Hi!
Thanks for all your help in the other thread.
I am trying to figure out exactly what steps I need to take as this whole thing is pretty confusing. Lets just say all I want to do is have a day of the week show up in the status bar. What steps am I missing here?
1. decompile the framework framework-res.apk and install it
2. decompile the SystemUIGoogle.apk
3. go into the SystemUIGoogle.apk FOLDER and look for status_bar.xml
4. Change out the code
5. Save the status_bar.xml
6. Place the newly edited status_bar.xml in my eviltheme folder in /system/priv-app/SystemUIGoogle
Now obviously I am way wrong but I thought that was the whole point; that this thing just pulls the XML instead of messing with my APKs? Can you please help me with the steps that I am doing wrong? Or am I not understanding this program correctly?
Click to expand...
Click to collapse
1. You do not have to decompile the framework-res.apk unless you want to mod it. Just install it.
2. Yes
3. When I was talking about folders I meant how things were put into the eviltheme folder. Same premise, though once it is decompiled, so yes.
4. Yes using notepad++ or something similar.
5. Yes
6. No, you must recompile your SystemUIGoogle.apk first. Then unzip it with 7zip, take out your status_bar.xml and put it in evilthheme folder like this: system/priv-app/SystemUIGoogle.apk/res/layout
Those are folder names, not your actual SystemUIGoogle.apk. you must tell it the exact pathway to where your modded file goes. Look at your SystemUIGoogle.apk after you decompile it. It is no longer a apk, now it is folders and files.
Flash my Aroma, however many mods you want. Then flash the very first one, the Magisk Module maker. You don't have to install it. Reboot system, in file explorer, go to the new folder on your sdcard called magisk, find the magisk.zip, unzip it and look at the folder structure.
Tulsadiver said:
6. No, you must recompile your SystemUIGoogle.apk first. Then unzip it with 7zip, take out your status_bar.xml and put it in evilthheme folder like this: system/priv-app/SystemUIGoogle.apk/res/layout
Click to expand...
Click to collapse
OK so I did this (my confusion came from the fact that I did not realize that the status_bar.xml was different when the APK is recompiled!)
However, I do not have an eviltheme folder anywhere on my Pixel. Was I supposed to install EvilTheme along with the zip you made for me? Or just your zip?
daddylonglegs said:
Hi!
Thanks for all your help in the other thread.
I am trying to figure out exactly what steps I need to take as this whole thing is pretty confusing. Lets just say all I want to do is have a day of the week show up in the status bar. What steps am I missing here?
1. decompile the framework framework-res.apk and install it
2. decompile the SystemUIGoogle.apk
3. go into the SystemUIGoogle.apk FOLDER and look for status_bar.xml
4. Change out the code
5. Save the status_bar.xml
6. Place the newly edited status_bar.xml in my eviltheme folder in /system/priv-app/SystemUIGoogle
Now obviously I am way wrong but I thought that was the whole point; that this thing just pulls the XML instead of messing with my APKs? Can you please help me with the steps that I am doing wrong? Or am I not understanding this program correctly?
Click to expand...
Click to collapse
Ok. Correct me if I'm wrong Tulsadiver...
But I believe what you want to do is:
1. Pull the required APKs from your phone.
2. Decompile them.
3. Mod them accordingly to what you wish.
4. Recompile them. (Do not push them to the phone)
5. Extract as .zip, find the files you modded, and now put folders accordingly in the eviltheme folder as is to the needs of your device. (For instance, /system/priv-app/SystemUIGoogle.apk/res/anim/your file here.xml(don't quote me on it, I'm guessing that's where things are)).
Don't ask me why it's nessessary to recompile them. Something to do with signature checking if I remember and understand right.
Correct me if I'm wrong Tulsadiver, just trying to help this lost soul with my own understanding.
daddylonglegs said:
OK so I did this (my confusion came from the fact that I did not realize that the status_bar.xml was different when the APK is recompiled!)
However, I do not have an eviltheme folder anywhere on my Pixel. Was I supposed to install EvilTheme along with the zip you made for me? Or just your zip?
Click to expand...
Click to collapse
The eviltheme folder is inside the magisk.zip I gave you. That is a magisk module template.
Truant_Luce said:
Ok. Correct me if I'm wrong Tulsadiver...
But I believe what you want to do is:
1. Pull the required APKs from your phone.
2. Decompile them.
3. Mod them accordingly to what you wish.
4. Recompile them. (Do not push them to the phone)
5. Extract as .zip, find the files you modded, and now put folders accordingly in the eviltheme folder as is to the needs of your device. (For instance, /system/priv-app/SystemUIGoogle.apk/res/anim/your file here.xml(don't quote me on it, I'm guessing that's where things are)).
Don't ask me why it's nessessary to recompile them. Something to do with signature checking if I remember and understand right.
Correct me if I'm wrong Tulsadiver, just trying to help this lost soul with my own understanding.
Click to expand...
Click to collapse
You have to recompile them because that is the way they are on your phone. What Apktool does is decodes the files so you can read them, kind of like decrypts them. They have to be back in their original form or your phone can't read them. The entire apk would need original signature but we are only talking about edited xml's here.
@Truant_Luce Thank you! Yes that is exactly what was confusing me. I thought he was telling me to recompile in order to push the apk back to the device! No wonder I was so confused My fault! I really appreciate your reply.
Tulsadiver said:
The eviltheme folder is inside the magisk.zip I gave you. That is a magisk module template.
Click to expand...
Click to collapse
OK so open the zip you gave me, put the xml file in the magisk folder, zip it up again, and then install the zip?
daddylonglegs said:
@Truant_Luce Thank you! Yes that is exactly what was confusing me. I thought he was telling me to recompile in order to push the apk back to the device! No wonder I was so confused My fault! I really appreciate your reply.
OK so open the zip you gave me, put the xml file in the magisk folder, zip it up again, and then install the zip?
Click to expand...
Click to collapse
Yes, put the xml in the folder order that was discussed. Zip up the contents of the magisk folder, not the folder itself. In other words, select common folder through config.sh, not magisk itself.
{
"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"
}
Tulsadiver said:
Yes, put the xml in the folder order that was discussed. Zip up the contents of the magisk folder, not the folder itself. In other words, select common folder through config.sh, not magisk itself.
View attachment 4215877
Click to expand...
Click to collapse
OK I did this. Unfortunately when I get to the home screen trying to load it has the default background (mine is removed) and says "Android is starting...." and never loads.
I tried to install the .zip you had uploaded that supposedly fixes the SystemUI if this happens but unfortunately it did not work.
Any advice to get this or my phone booting again would be appreciated. I am not sure how such a tiny modification to the clock could render my phone unusable.
daddylonglegs said:
OK I did this. Unfortunately when I get to the home screen trying to load it has the default background (mine is removed) and says "Android is starting...." and never loads.
I tried to install the .zip you had uploaded that supposedly fixes the SystemUI if this happens but unfortunately it did not work.
Any advice to get this or my phone booting again would be appreciated. I am not sure how such a tiny modification to the clock could render my phone unusable.
Click to expand...
Click to collapse
Upload your zip.
You might have to do a factory reset in twrp. You have to setup your phone like new but I have done it and have not lost data.
Tulsadiver said:
Yes, put the xml in the folder order that was discussed. Zip up the contents of the magisk folder, not the folder itself. In other words, select common folder through config.sh, not magisk itself.
View attachment 4215877
Click to expand...
Click to collapse
Tulsadiver said:
Upload your zip.
You might have to do a factory reset in twrp. You have to setup your phone like new but I have done it and have not lost data.
Click to expand...
Click to collapse
Here you go. I really hope I can manage to get this running without a factory reset. Thank you for helping me.
daddylonglegs said:
Here you go. I really hope I can manage to get this running without a factory reset. Thank you for helping me.
Click to expand...
Click to collapse
You can also fastboot flash your firmware again. First try uploading my Aroma. Select the nexus navbar rainbow battery (selection 64) a navbar height mod (say #28) so you get systemui and frameworks involved. Flash the magisk module. Exit the Aroma and while still in twrp, go back to install, find the magisk.zip in the magisk folder on your sdcard and flash it.
Tulsadiver said:
You can also fastboot flash your firmware again. First try uploading my Aroma. Select the nexus navbar rainbow battery (selection 64) a navbar height mod (say #28) so you get systemui and frameworks involved. Flash the magisk module. Exit the Aroma and while still in twrp, go back to install, find the magisk.zip in the magisk folder on your sdcard and flash it.
Click to expand...
Click to collapse
OK, flash which magisk.zip? xdahelpermagiskFINAL.zip?
daddylonglegs said:
OK, flash which magisk.zip? xdahelpermagiskFINAL.zip?
Click to expand...
Click to collapse
There will only be one called magisk.zip
I noticed in your xml that you took the stock clock completely off and replaced it with a text clock. What I do is leave the stock clock but put in 0.0dip for both the layout width and height so it doesn't show up. I believe you have to have it there though.
I fixed it if you want to try and flash it first.
Tulsadiver said:
You can also fastboot flash your firmware again. First try uploading my Aroma. Select the nexus navbar rainbow battery (selection 64) a navbar height mod (say #28) so you get systemui and frameworks involved. Flash the magisk module. Exit the Aroma and while still in twrp, go back to install, find the magisk.zip in the magisk folder on your sdcard and flash it.
Click to expand...
Click to collapse
I am in a thing that says "Mod options" and I see a bunch listed. None say "navbar rainbow battery". I even counted down 64 lines and 28 lines and they don't match up with what you are saying
---------- Post added at 09:43 PM ---------- Previous post was at 09:20 PM ----------
Never mind. I found the ones you probably meant. I get a "System UI has stopped" and can't do anything when i boot my phone.
daddylonglegs said:
I am in a thing that says "Mod options" and I see a bunch listed. None say "navbar rainbow battery". I even counted down 64 lines and 28 lines and they don't match up with what you are saying
---------- Post added at 09:43 PM ---------- Previous post was at 09:20 PM ----------
Never mind. I found the ones you probably meant. I get a "System UI has stopped" and can't do anything when i boot my phone.
Click to expand...
Click to collapse
Sorry, my Nexus 5X just died about an hour ago and I've been talking with Google about a replacement.
You will probably have to fastboot flash your system firmware again if you don't want to factory reset.
Tulsadiver said:
Sorry, my Nexus 5X just died about an hour ago and I've been talking with Google about a replacement.
You will probably have to fastboot flash your system firmware again if you don't want to factory reset.
Click to expand...
Click to collapse
OK.
So what exactly was the reason this would not work on my Pixel but it worked on yours? :CONFUSED:
daddylonglegs said:
So what exactly was the reason this would not work on my Pixel but it worked on yours? :CONFUSED:
Click to expand...
Click to collapse
It didn't. Just flashed it. I took another look at your status_bar.xml. You left off the original clock and your layout gravity was wrong. Should have been android:gravity not android:layout_gravity
I get a lot of requests to remove the NavBar. I'm posting this mod at each phone's forum themes section. TWRP flashable zip. Restore zip will be created in a folder named ozop on your sdcard.
8.1 March Update
https://www.androidfilehost.com/?fid=673956719939829462
8.0 November update
https://www.androidfilehost.com/?fid=817906626617946403
8.1 preview DP1
https://www.androidfilehost.com/?fid=817906626617947258
8.1 DP2
https://www.androidfilehost.com/?fid=745849072291691723
8.1 Dec Final
https://www.androidfilehost.com/?fid=745849072291694014
Installation instructions for those of you that have root, but do not have TWRP. Busybox must be installed first.
1. Download the enclosed vrthemeADBversion zip and readme.txt for copying and pasting purposes.
2. Unzip the vrthemeADBversion zip to your sdcard. Rename folder to vrtheme
3. Put the readme.txt on your PC where you use adb.
4. Download appropriate NavBar Gone zip. Unzip and copy the system folder that is inside the vrtheme folder to the root of your sdcard.
5. On the root folder of your phone, find the data folder and create a folder inside it named tmp
6. Copy the vrtheme folder you earlier extracted to your sdcard to newly created data/tmp folder (/data/tmp/vrtheme)
7. On PC, with your phone connected and in file transfer mode, open CMD prompt and type "adb devices" without quotes. If your serial number comes up you can proceed.
8. Copy and paste the command lines from the readme.txt (include quotes)
adb shell su -c "mount -o rw,remount /system"
Hit enter
First time you will be promoted by SuperSU to give adb permission.
Copy and paste the second line in readme.txt
adb shell su -c sh /data/tmp/vrtheme/installtheme.sh
(If you would rather run a bat file and are on Windows, extract the ModInstaller zip where you adb is and run it instead of typing or copying and pasting the commands from the readme.txt)
Wait until everything runs, after a pause of a few seconds your phone will reboot and your NavBar should be gone.
bumping this thread for relevancy.
Also.... what is everyone using for navigation replacements? I love LMT, but it crashes and often leaves me without a way to return home.
noidea24 said:
bumping this thread for relevancy.
Also.... what is everyone using for navigation replacements? I love LMT, but it crashes and often leaves me without a way to return home.
Click to expand...
Click to collapse
I'm using LMT. Never thought I'd like it but in order to get this mod right, I had to try it. Now I like it. Took some getting used to.
I could put a invisible home button on the left side of your statusbar.
I use Swipe Navigation and love it. After a recent update caused it to stop working, I downloaded an older apk from the XDA thread and keep that on my device for emergencies.
Edit.. Should mention that the developer, @Splder released another update the same day that fixed the problem I had.
I also use swipe navigation and it works great. I got scared a bit because I updated it and it didn't work but i just needed to turn it back on and grant permissions again but other than that it's the best app to use if you want to get rid of the nav bar. Simple swipe up gestures from the bottom left, middle and right make it a breeze to use.
Holy crap, thanks OP, was looking for something like this since Oreo release.
Is there any bug like Assistant force closing upon opening it or something like that?
ithehappy said:
Holy crap, thanks OP, was looking for something like this since Oreo release.
Is there any bug like Assistant force closing upon opening it or something like that?
Click to expand...
Click to collapse
Not that I am aware of. I'm not really a power user and just went navbarless a couple of days ago. This zip will make a restore zip in a folder called ozop.
Thank you for the great mod. It was a shame that the option to remove the navbar from stock rom was no longer possible. It was the only thing that drove me to custom roms. Immersive mode is not that practical. I've been using either lmt or the pie controls from gravity box since KitKat and going back to using the navbar was impossible.
Thank you for this! Out of curiosity this will break SafetyNet, correct?
AbuShabanov said:
Thank you for this! Out of curiosity this will break SafetyNet, correct?
Click to expand...
Click to collapse
Probably. It is a system flash though it leaves the original meta-inf and android-manifest intact.
I'm not sure if this zip is the same one you made for me last week in the Aroma Mod thread, but that one passes.
911jason said:
I'm not sure if this zip is the same one you made for me last week in the Aroma Mod thread, but that one passes.
Click to expand...
Click to collapse
I appreciate the input. It is almost the same. There were complaints that the LMT navbar didn't come up smooth enough so I added and changed a few things. Nothing that would trigger something that one didn't.
Tulsadiver said:
I'm using LMT. Never thought I'd like it but in order to get this mod right, I had to try it. Now I like it. Took some getting used to.
I could put a invisible home button on the left side of your statusbar.
Click to expand...
Click to collapse
I like the idea of the invisible home button in the status bar with the navbar removal...you think it could be flashed over that previous mod you made for me? Will this introduce lag like I experienced when I tried immersive mode? Im guessing not since it just removes it...
Oh and fwiw I still pass safetynet with the previous zip you made me
AP2FTW said:
I like the idea of the invisible home button in the status bar with the navbar removal...you think it could be flashed over that previous mod you made for me? Will this introduce lag like I experienced when I tried immersive mode? Im guessing not since it just removes it...
Oh and fwiw I still pass safetynet with the previous zip you made me
Click to expand...
Click to collapse
I've slept since then, what mod did I make for you?
Tulsadiver said:
I've slept since then, what mod did I make for you?
Click to expand...
Click to collapse
Lol my fault...here's a link to the post https://forum.xda-developers.com/showpost.php?p=74048596&postcount=118
It also does center clock (in smallest text) and carrier text removal
AP2FTW said:
Lol my fault...here's a link to the post https://forum.xda-developers.com/showpost.php?p=74048596&postcount=118
It also does center clock (in smallest text) and carrier text removal
Click to expand...
Click to collapse
You can try this. I had forgotten how convoluted my statusbar was so I'm not sure if the home button will work. Let me know.
https://www.androidfilehost.com/?fid=817906626617947200
Tulsadiver said:
You can try this. I had forgotten how convoluted my statusbar was so I'm not sure if the home button will work. Let me know.
https://www.androidfilehost.com/?fid=817906626617947200
Click to expand...
Click to collapse
I will try it soon as I can thanks very much :good:
AbuShabanov said:
Thank you for this! Out of curiosity this will break SafetyNet, correct?
Click to expand...
Click to collapse
I finally got around to flashing this and it does indeed pass SafetyNet. Thank you for this!
Tulsadiver said:
You can try this. I had forgotten how convoluted my statusbar was so I'm not sure if the home button will work. Let me know.
https://www.androidfilehost.com/?fid=817906626617947200
Click to expand...
Click to collapse
Worked perfectly and still passing safetynet. Thanks a million
Dear Sir
I uploaded the apk, If you are so kind to make the NaviBar Gone Mod for Pixel XL 8.1
Your mod is the best solution I found so far. Many many thanks to you!
Does anyone know if they already have a solution to fix the fingerprint on any GSI on the moto g7 play?
I don't think there will be a fix for it. GSIs are basically developed for testing purposes and are not functionally ROMs.
---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------
https://source.android.com/setup/build/gsi
Guhl0rd64 said:
Does anyone know if they already have a solution to fix the fingerprint on any GSI on the moto g7 play?
Click to expand...
Click to collapse
I'm working on this right now. It requires a jar from /system/framework, and some libs from the stock OS. And maybe an overlay, but that part I'm unsure about. If I get anything working I'll post a flashable zip.
Spaceminer said:
I'm working on this right now. It requires a jar from /system/framework, and some libs from the stock OS. And maybe an overlay, but that part I'm unsure about. If I get anything working I'll post a flashable zip.
Click to expand...
Click to collapse
man, you are the g7 play hero ngl, can you post an explanation of what needed to be done when youve done it, you know like the technical side, so people like me can learn?
00p513 said:
man, you are the g7 play hero ngl, can you post an explanation of what needed to be done when youve done it, you know like the technical side, so people like me can learn?
Click to expand...
Click to collapse
I use a few methods in general to figure stuff out.
1. Google, Arch linux Wiki, stack exchange.
2. Sleuthing. Go digging though system files or app manifests.
3. Poke it with a stick. Running strings or grep on a file for keywords. Poke the box with the right input, and it'll often give you prizes in return. This is especially true for things you can't just decompile like a bootloader image. You can even do things like tease partition mounts from a vendor image this way.
4. Load files into a hex editor. I personally use HxD. This works similar to the poke the box method. If strings and grep are like a radio, then using a hex editor is like watching TV.
5. Don't reinvent the wheel if you don't have to. Look for things that you know accomplish the same, or a similar task, then adapt them to your situation. This isn't always easy but 90% of the time it'll get you there or damn close.
This project is a combo of 2 and 5.
I first went digging through system and vendor files. I know from prior experience that apps and hardware features often require library files (/system/lib/*.so), bin files (/system/bin & /vendor/bin), jar files (/system/framework/*.jar), and permissions (/system/etc/permissons & (/vendor/etc/permissions). Occasionally hardware features also have an init script to start them. (/system/etc/init & /vendor/etc/init)
So I searched with a root explorer for any files in those locations that have "finger" in the name. That gave me gold. I made a note and created a file structure to match them, then copied the files over and created a zip.
This is where #5 comes in. In order to flash it, we need a script to tell twrp how to mount the partitions we're going to modify, where the files go, and what file permissions to set. (rw-r--r--, 0755 etc.) I knew how to do this from modifying phh's su to work on Lineage OS 17. And I learned how to do that by looking at the flashable zips for, viper for android, and the universal disabler. Since I had adapted those for Phh su, when I needed to do it again, I pulled the scripts from Phh su and edited them to use the new files and permissions.
That's the jist of it. If you want to see how the scripts are written, extract the zip and look at META-INF/com/google/android/updater-script with a text editor. I recommend either Quick Edit pro for android, or notepad++ if using Windows.
Finger Print Test #1
If anyone running a GSI wants to test this, just flash it in twrp and let me know if the finger print sensor works. It should NOT break anything. If you get any flashing errors please tell me. It means there's a typo somewhere in the scripts and I need to fix it.
Spaceminer said:
I use a few methods in general to figure stuff out.
1. Google, Arch linux Wiki, stack exchange.
2. Sleuthing. Go digging though system files or app manifests.
3. Poke it with a stick. Running strings or grep on a file for keywords. Poke the box with the right input, and it'll often give you prizes in return. This is especially true for things you can't just decompile like a bootloader image. You can even do things like tease partition mounts from a vendor image this way.
4. Load files into a hex editor. I personally use HxD. This works similar to the poke the box method. If strings and grep are like a radio, then using a hex editor is like watching TV.
5. Don't reinvent the wheel if you don't have to. Look for things that you know accomplish the same, or a similar task, then adapt them to your situation. This isn't always easy but 90% of the time it'll get you there or damn close.
This project is a combo of 2 and 5.
I first went digging through system and vendor files. I know from prior experience that apps and hardware features often require library files (/system/lib/*.so), bin files (/system/bin & /vendor/bin), jar files (/system/framework/*.jar), and permissions (/system/etc/permissons & (/vendor/etc/permissions). Occasionally hardware features also have an init script to start them. (/system/etc/init & /vendor/etc/init)
So I searched with a root explorer for any files in those locations that have "finger" in the name. That gave me gold. I made a note and created a file structure to match them, then copied the files over and created a zip.
This is where #5 comes in. In order to flash it, we need a script to tell twrp how to mount the partitions we're going to modify, where the files go, and what file permissions to set. (rw-r--r--, 0755 etc.) I knew how to do this from modifying phh's su to work on Lineage OS 17. And I learned how to do that by looking at the flashable zips for, viper for android, and the universal disabler. Since I had adapted those for Phh su, when I needed to do it again, I pulled the scripts from Phh su and edited them to use the new files and permissions.
That's the jist of it. If you want to see how the scripts are written, extract the zip and look at META-INF/com/google/android/updater-script with a text editor. I recommend either Quick Edit pro for android, or notepad++ if using Windows.
Finger Print Test #1
If anyone running a GSI wants to test this, just flash it in twrp and let me know if the finger print sensor works. It should NOT break anything. If you get any flashing errors please tell me. It means there's a typo somewhere in the scripts and I need to fix it.
Click to expand...
Click to collapse
Wow, thank you very much my friend, I will test now
Spaceminer said:
I'm working on this right now. It requires a jar from /system/framework, and some libs from the stock OS. And maybe an overlay, but that part I'm unsure about. If I get anything working I'll post a flashable zip.
Click to expand...
Click to collapse
Thank you.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Guhl0rd64 said:
Wow, thank you very much my friend, I will test now
Click to expand...
Click to collapse
So...?
Marcondes BR said:
Thank you.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
So...?
Click to expand...
Click to collapse
I installed by TWRP, I have Lineage OS 17.1, still with the same problem
Descendent Modified GSI, doesnt work. It sees the reader, but doesnt recognise me touching it
Spaceminer said:
I use a few methods in general to figure stuff out.
1. Google, Arch linux Wiki, stack exchange.
2. Sleuthing. Go digging though system files or app manifests.
3. Poke it with a stick. Running strings or grep on a file for keywords. Poke the box with the right input, and it'll often give you prizes in return. This is especially true for things you can't just decompile like a bootloader image. You can even do things like tease partition mounts from a vendor image this way.
4. Load files into a hex editor. I personally use HxD. This works similar to the poke the box method. If strings and grep are like a radio, then using a hex editor is like watching TV.
5. Don't reinvent the wheel if you don't have to. Look for things that you know accomplish the same, or a similar task, then adapt them to your situation. This isn't always easy but 90% of the time it'll get you there or damn close.
This project is a combo of 2 and 5.
I first went digging through system and vendor files. I know from prior experience that apps and hardware features often require library files (/system/lib/*.so), bin files (/system/bin & /vendor/bin), jar files (/system/framework/*.jar), and permissions (/system/etc/permissons & (/vendor/etc/permissions). Occasionally hardware features also have an init script to start them. (/system/etc/init & /vendor/etc/init)
So I searched with a root explorer for any files in those locations that have "finger" in the name. That gave me gold. I made a note and created a file structure to match them, then copied the files over and created a zip.
This is where #5 comes in. In order to flash it, we need a script to tell twrp how to mount the partitions we're going to modify, where the files go, and what file permissions to set. (rw-r--r--, 0755 etc.) I knew how to do this from modifying phh's su to work on Lineage OS 17. And I learned how to do that by looking at the flashable zips for, viper for android, and the universal disabler. Since I had adapted those for Phh su, when I needed to do it again, I pulled the scripts from Phh su and edited them to use the new files and permissions.
That's the jist of it. If you want to see how the scripts are written, extract the zip and look at META-INF/com/google/android/updater-script with a text editor. I recommend either Quick Edit pro for android, or notepad++ if using Windows.
Finger Print Test #1
If anyone running a GSI wants to test this, just flash it in twrp and let me know if the finger print sensor works. It should NOT break anything. If you get any flashing errors please tell me. It means there's a typo somewhere in the scripts and I need to fix it.
Click to expand...
Click to collapse
I have tested on several GSI, and I have had no success
Guhl0rd64 said:
I have tested on several GSI, and I have had no success
Click to expand...
Click to collapse
You might need to add ro.fpsensor.position=1 & persist.qfp=false to the build prop.
Spaceminer said:
You might need to add ro.fpsensor.position=1 & persist.qfp=false to the build prop.
Click to expand...
Click to collapse
it still didn't work
Guhl0rd64 said:
it still didn't work
Click to expand...
Click to collapse
I'm unfortunately out ideas at this point.
Spaceminer said:
I'm unfortunately out ideas at this point.
Click to expand...
Click to collapse
I guess this means no fingerprint on Ubuntu Touch when i get it to work