Related
First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!
This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.
What is write enabler?
Keeps aborting for me
THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.
@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.
To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.
What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?
ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2
ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.
I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.
I reinstalled the stock odex ROM and flashed this again and it worked.
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app
fails in recovery for me.
says error executing updater binary in zip
in stock rooted...
To make Xposed's AppSettings' DPI function work, I reverted this change: https://github.com/LiquidSmooth/and...92#diff-82378faf2a467d2f28e834dddd59207eR1363
Updated 01/04/2015 Build with overclock http://web.mit.edu/ispatel/www/builds/lsoc/LS-KK-v3.2-2015-01-04-vs980_yes_properoc.zip
First... Awesome. How did I beat Lawlrus.
Mightycaptain said:
First... Awesome. How did I beat Lawlrus.
Click to expand...
Click to collapse
I blame work on that one.
Glad to see a build of liquid again op, thank you. I'll DL at work and see about flashing.
Sent from my Vs980 running Aicp 5.0 4.4.4_r2
Edit nevermind, brain fart.
Its 4.4.4, can't read, sorry
@ishyesh
Maybe I'm missing it, but is there a toggle for knock on? Doesn't seem to be working and I don't see the option.
Sent from my LG-VS980
Lawlrus said:
@ishyesh
Maybe I'm missing it, but is there a toggle for knock on? Doesn't seem to be working and I don't see the option.
Sent from my LG-VS980
Click to expand...
Click to collapse
The knock code value is probably set to "0" instead of "1" in the kernel. ishyesh will most likely have to change the value in the kernel before compiling.
You can use a script to activate it in the mean time (assuming there is no option anywhere in the settings to turn it on or off).
EDIT: Try this (see if it fixes it): http://www.mediafire.com/download/icnb1bu56nq4jb9/Turn_Knockon-On_G2.zip
@bouchigo
Thanks, but it didn't work. I for the life of me cannot find the option to enable knock on if there is one. I'll just wait for op to respond I guess.
Edit: so it did work. But you need to make sure use proximity sensor to have it turn on.
I did mess with this option before flashing your zip, and it didn't work. So your zip definitely fixed it.
Thanks again bro.
Sent from my LG-VS980
Lawlrus said:
@bouchigo
Thanks, but it didn't work. I for the life of me cannot find the option to enable knock on if there is one. I'll just wait for op to respond I guess.
Edit: so it did work. But you need to make sure use proximity sensor to have it turn on.
I did mess with this option before flashing your zip, and it didn't work. So your zip definitely fixed it.
Thanks again bro.
Sent from my LG-VS980
Click to expand...
Click to collapse
To enable knock-on,
use Tasker or some sort of automation software to execute this whenever the system boots:
"echo 1 > /sys/devices/virtual/input/lge_touch/touch_gesture"
Also, I uploaded a camcorder fix in the OP. Flash like any other.
To change DPI for the overall system, use an application like "texdroider dpi". I haven't tested the built in DPI changer.
ishyesh said:
To enable knock-on,
use Tasker or some sort of automation software to execute this whenever the system boots:
"echo 1 > /sys/devices/virtual/input/lge_touch/touch_gesture"
Also, I uploaded a camcorder fix in the OP. Flash like any other.
To change DPI for the overall system, use an application like "texdroider dpi". I haven't tested the built in DPI changer.
Click to expand...
Click to collapse
I just changed the build prop using root browser. Thanks.
Also flashing that zip persists through reboots. No need to set a tasker if you flash that.
Sent from my LG-VS980
Btw, I'm not sure how Linux literate you guys are, but if you're curious and want to learn, try and unzip the KnockOnZip that bouchigo posted. Inside, you'll find a file within the path system/etc/init.d . Upon flashing, the script within that path is copied to your phone's /system/etc/init.d. On your phone, you can place whatever you want inside this directory so that it gets called whenever Android starts (read up on the naming of the script, that's critical). So in the zip, the 98knock-on-On script executes the same command I said you could tell Tasker to do.
Go crazy with that if you wish. And remember, make sure you check every zip that you flash.
ishyesh said:
Btw, I'm not sure how Linux literate you guys are, but if you're curious and want to learn, try and unzip the KnockOnZip that bouchigo posted. Inside, you'll find a file within the path system/etc/init.d . Upon flashing, the script within that path is copied to your phone's /system/etc/init.d. On your phone, you can place whatever you want inside this directory so that it gets called whenever Android starts (read up on the naming of the script, that's critical). So in the zip, the 98knock-on-On script executes the same command I said you could tell Tasker to do.
Go crazy with that if you wish. And remember, make sure you check every zip that you flash.
Click to expand...
Click to collapse
You probably already know this, but if you go into devices folder, and into the vs980 folder (I can't remember the folder structure, I haven't looked at source in a while), anyway, look for init.g2.rc and change the following before compiling:
From: chown system system /sys/devices/virtual/input/lge_touch/touch_gesture
To: write /sys/devices/virtual/input/lge_touch/touch_gesture 1
That should fix it so no scripts or tasker actions are required.
bouchigo said:
The knock code value is probably set to "0" instead of "1" in the kernel. ishyesh will most likely have to change the value in the kernel before compiling.
You can use a script to activate it in the mean time (assuming there is no option anywhere in the settings to turn it on or off).
EDIT: Try this (see if it fixes it): http://www.mediafire.com/download/icnb1bu56nq4jb9/Turn_Knockon-On_G2.zip
Click to expand...
Click to collapse
This zip worked great for me: VS98025A. Thanks
bouchigo said:
You probably already know this, but if you go into devices folder, and into the vs980 folder (I can' remember the folder structure, I haven't looked at source in a while), anyway, look for init.g2.rc and change the following before compiling:
From: chown system system /sys/devices/virtual/input/lge_touch/touch_gesture
To: write /sys/devices/virtual/input/lge_touch/touch_gesture 1
That should fix it so no scripts or tasker actions are required.
Click to expand...
Click to collapse
I did not know that! I'll be sure to incorporate that in my next iteration. Thank you!
http://forum.xda-developers.com/showthread.php?p=54906959#post54906959
Lawlrus said:
@ishyesh
Maybe I'm missing it, but is there a toggle for knock on? Doesn't seem to be working and I don't see the option.
Sent from my LG-VS980
Click to expand...
Click to collapse
could this also work? Worked for me on other ROMs. Liquid was one of my favorite GNEX roms.
mrdunn said:
http://forum.xda-developers.com/showthread.php?p=54906959#post54906959
could this also work? Worked for me on other ROMs. Liquid was one of my favorite GNEX roms.
Click to expand...
Click to collapse
No. I've never updated to knock code. So it didn't have anything to do with my touch firmware. Knock on needs manually turned on.
Sent from my Vs980 running CloudyFlex 2.6
Great work
Sent from my VS980 4G using Tapatalk
The best ROM!!!
The smoothness and fluidity of the UI is amazing.
Use one plus bionic optimized binaries and flash seeder using interactive governor and deadline as scheduler. Then, you have the best user experience on an Android device.
@luv2increase
Check yo pms
Sent from my Vs980
Anybody having issues with youtube playback on this Rom? I went back to stock for now as this Rom wasn't playing a lot of the youtube videos I was trying to watch.
What's the exact youtube error message?
Any fix to the install bar in .207????
A zip or a file????
lucasgta95 said:
Any fix to the install bar in .207????
A zip or a file????
Click to expand...
Click to collapse
You can use an Xposed module to fix it.
Else, you will need to decompile a system apk and fix it yourself
TechnoSparks said:
You can use an Xposed module to fix it.
Else, you will need to decompile a system apk and fix it yourself
Click to expand...
Click to collapse
Okay, but what module and what parameter??
I fix it myself
Later uploaded for you
It has already been fixed before...
Check this out, it is a bug fix package-just extract it and take the packageinstaller.apk, push to system/app, set permissions and reboot. Alternatively try the one attached, the attached one has a white background (unlike the other one which is black), the white fits in more with Sony's 4.3 firmware.
If your getting an 'android is upgrading' message upon every boot (happened to me ) then move (or cut not copy) the packageinstaller.odex to your sd card/internal memory, reboot, then move it back into system/app, set permissions and reboot again-now it should boot like normal.
Btw you need root and a file explorer that supports root access to follow my method.
It seems to work.
Android updated once and then no problem.
Background is white. Why not.
Thanks a lot.
Killawave said:
Okay, but what module and what parameter??
Click to expand...
Click to collapse
Even if you have solved the problem, I will give you the module anyway:
http://repo.xposed.info/module/com.mohammadag.fixsony43bugs
Have fun! and sorry for the late response
TechnoSparks said:
Even if you have solved the problem, I will give you the module anyway:
http://repo.xposed.info/module/com.mohammadag.fixsony43bugs
Have fun! and sorry for the late response
Click to expand...
Click to collapse
It is solved by replacing the APK but I had forgotten this module.
So if fixes this bug?
Is there a list of solved bugs?
I will download and apply to test. Thanks...
Killawave said:
It is solved by replacing the APK but I had forgotten this module.
So if fixes this bug?
Is there a list of solved bugs?
I will download and apply to test. Thanks...
Click to expand...
Click to collapse
It only fixes the uninstall text going offset. Other than that the module seemed to be dead.
This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.
guyd said:
This tweak worked on the stock T-Mobile OCG ROM, and will likely work for other stock based ROM's.
I used the "SQLite Editor" app to do this tweak. Other SQLite editors should work as well.
1.Launch SQLite Editor and select "Files" and drill down into /data/data/com.android.providers.settings/databases/settings.db
2. Select "system"
3. Press the "+" option
4. Leave _id set to auto
5. Add in the name field "notification_panel_brightness_adjustment" (without the quotes)
6. Add in the value field "0" (number zero without the quotes)
7. Press save
8. Exit and reboot
If you decide at a later time you want it back, just change the value of that field to a 1 then save and reboot.
Click to expand...
Click to collapse
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.
Yoshi910 said:
Nice find! However since I actually use the brightness slider daily, I won't be getting rid of it. Now we just need to find a way to get rid of the S Finder/Quick Connect from the notification panel.
Click to expand...
Click to collapse
I can mod systemui.apk to remove them, if you want it.
mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol
guaneet said:
Yes please
And if you could possibly look into having 6 toggles that would be greatly appreciated. Using your rom got it before the pull lol
Click to expand...
Click to collapse
haha, yea im not a fan of having a ton of threads all with mostly the same thing. ill see what i can do about the toggles, i can for sure get rid of the other stuff.
You can also simply install Lux and turn off its persistent notification
Could this be used to do other tweaks like remove icons/clock from the status bar?
mikeyinid said:
I can mod systemui.apk to remove them, if you want it.
Click to expand...
Click to collapse
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.
teiglin said:
That'd be awesome. I was looking through the xml but was having trouble finding an obvious section to cut for this bar--res/layout/status_bar_expanded doesn't even appear to contain a reference to the sfinder_qconnect stuff.
Click to expand...
Click to collapse
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.
mikeyinid said:
its in res/values/dimens.xml. if you google it theres a few tuts how to do it.
Click to expand...
Click to collapse
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Edit for basic instructions:
Use a root-enabled file manager or console to replace /system/priv-app/SystemUI/SystemUI.apk with the attached file, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz. Make sure the permissions of the new SystemUI.apk are rw-r--r-- (chmod 644 /system/priv-app/SystemUI/SystemUI.apk at the console). Reboot and enjoy.
Caveat: you may not be able to swipe away notifications from within the region previously taken up by the sfinder/qconnect bar.
Great! Can also be done via adb:
Code:
adb shell settings put system notification_panel_brightness_adjustment 0
teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Thanks! Works great.
teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
How would you get it to work, I tried to install it but it won't install.
teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Worked fine, thanks !
EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons
EvoYas said:
How would you get it to work, I tried to install it but it won't install.
Click to expand...
Click to collapse
v2.2v said:
Also wondering the same. And I don't see the system ui file in arm64. Can't wait to find out though lol I despise those two buttons
Click to expand...
Click to collapse
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
That worked flawlessly, thank you.
teiglin said:
You either need a root-enabled file manager or su at a console, and replace /system/priv-app/SystemUI/SystemUI.apk with the file I provided, and delete /system/priv-app/SystemUI/arm64/SystemUI.odex.art.xz, then reboot. As always, I strongly recommend making backups and of course, I can provide no guarantees, yadda yadda.
Click to expand...
Click to collapse
perfect! thank you so much
teiglin said:
Thanks, I had been looking at another tutorial involving cutting a few lines from status_bar_extended, but it hadn't occurred to me simply to change its size to zero in dimens. >.<
This doesn't seem worth a whole new thread, so I've attached a systemui whose only change is the removal of the sfinder/qconnect bar. I believe you also have to delete the arm64/SystemUI.odex.art.xz file for things to work properly.
Click to expand...
Click to collapse
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...
Painless001 said:
Awesome! Works perfectly! Thanks so much. Just a reminder to relative noobs like myself to change the appropriate permissions in the new SystemUI file to -rw-r--r--. I forgot to do so first try, and lost both the status bar and the lockscreen. Fixed now, but had a moment or two of panic...
Click to expand...
Click to collapse
BINGO. Yea i forgot to mention that in my response, as well. Always fix permissions
This is an extension of my Android Oreo Pixel Mod thread, found here https://forum.xda-developers.com/nexus-6p/themes-apps/zip-android-oreo-pixel-mod-t3661388
This thread is for the users who want the Pixel Mod but also the ability to use Substratum. Why does my original mod break substratum? It modifies the framework-res.apk. The pixel no longer gets it's features from a modified framework-res.apk. It gets it from a theme. Making a pixel mod work with Substratum now requires making the 6P do the same thing as the Pixel. However, to simplify the mod I mimiced the features by modifying the framework-res.apk. This breaks Substratum. Following this walkthrough will enable the Pixel Theme on your 6P without modifying your framework-res.apk. Exactly how Google does it with the Pixel. (Exciting right?) This will allow the use of Substratum. This is what I am using and I can verify that substratum works.
Here'es the first thing: The files that you will need.
1)My original Pixel mod (flashable) -- https://www.androidfilehost.com/?fid=961840155545590555
2)Stock framework (flashable) -- https://www.androidfilehost.com/?fid=673368273298981491
3)Pixel Theme files (NOT flashable) -- https://www.androidfilehost.com/?fid=889764386195925591
4)You need to be ROOTED
5)You need a file manager that has root functions and can edit file permissions. (I.E.: Amaze File Manager, EX File Explorer, MT Manager)
Here are the steps. This is as simple as I can make it at the moment. It's not too complicated, but if you are a beginner with this stuff make sure to make a back up. Even if you're not. Make a backup. You are responsible for anything that happens to your device and making a backup will save everybody.
Step 1) Download all files onto your internal storage
Step 2) Extract the contents of "NO FLASH Pixel Mod + Substratum.zip". You should have a build.prop file and a folder called "overlay"
Step 3) Move that folder in your Vendor folder. Leave behind the "build.prop" If you go to your root directory you should see the folder "Vendor". Along with folders like "sys" and "system". But you don't want those. You want "Vendor".
Step 4) Make sure the permissions are accurate. The 2 apk files that you will find inside the "overlay" folder (the framework file and the pixel.apk file you'll find in the "pixel" folder inside the "overlay" folder) are set to 644. The folders "overlay" and "pixel" ("pixel" is found within the "overlay" folder) needs to be set to 755.
Step 5) Edit the build.prop file found within your vendor to include the lines that are found in the included build.prop (See footer)
Step 6) Reboot into TWRP
Step 7) In this order flash "Android OPR6 Pixel Mod 6P.zip" and then "Stock Framework.zip"
Step 8) Reboot
Step 9) If you don't see Round Icons you may need to clear Pixel Launcher Data
If SystemUI is crashing after reboot, reboot into TWRP and mount the vendor partition. Then delete the overlay folder and that'll solve the issue
If you followed those correctly you should have now have a Pixel Theme (Accent color, Night Mode, and Round icons) with compatibility with Substratum.
*footer*
ro.opa.eligible_device=true
ro.com.google.ima.theme=5
ro.boot.vendor.overlay.theme=com.google.android.theme.pixel
Followed each step as explained. Changed permissions from 644 to 755. Blue accent gone and stock teal is back. Default round icons gone and the ever so stupid square ones back. And Substratum's still broken. Wonder where I went wrong!!!
Edit : Additional to that, there are 'n' number of folders namely ".." with today's date as modified date. Each ".." folder contains multiple ".." folders and it just keeps going on and on....
Never faced this earlier. Have I screwed up something???
Suhas_JS said:
Followed each step as explained. Changed permissions from 644 to 755. Blue accent gone and stock teal is back. Default round icons gone and the ever so stupid square ones back. And Substratum's still broken. Wonder where I went wrong!!!
Edit : Additional to that, there are 'n' number of folders namely ".." with today's date as modified date. Each ".." folder contains multiple ".." folders and it just keeps going on and on....
Never faced this earlier. Have I screwed up something???
Click to expand...
Click to collapse
That is interesting. The folder thing is weird. Did you set the files "build.prop", "framework_generated.......apk", and "Pixel.apk" to 644? The files needed to be 644 and the folders needed to be 755
krisyarno said:
That is interesting. The folder thing is weird. Did you set the files "build.prop", "framework_generated.......apk", and "Pixel.apk" to 644? The files needed to be 644 and the folders needed to be 755
Click to expand...
Click to collapse
Should I be reflashing Vendor image to set the folders right???
May be I can retry the whole stuff again?
I am ready to be the specimen for experiments :laugh:
Is there any change Pixel Theme alone can be enabled on Nexus using ADB overlay service commands that were explained recently on main XDA page?
Suhas_JS said:
Should I be reflashing Vendor image to set the folders right???
May be I can retry the whole stuff again?
I am ready to be the specimen for experiments :laugh:
Click to expand...
Click to collapse
Definitely. I'm redoing the steps myself and I'm running into a weird bump. I'm going to revise it a little maybe. Definitely a good idea to reflash the vendor and take another shot though!
Suhas_JS said:
Should I be reflashing Vendor image to set the folders right???
May be I can retry the whole stuff again?
I am ready to be the specimen for experiments :laugh:
Click to expand...
Click to collapse
Try setting build.prop to 600 instead of 644
revanmj said:
Is there any change Pixel Theme alone can be enabled on Nexus using ADB overlay service commands that were explained recently on main XDA page?
Click to expand...
Click to collapse
I believe so. Placing the overlay folder found from Pixel's vendor to the same place on the 6P should give the 6p the ability to use all the overlay service commands
krisyarno said:
Try setting build.prop to 600 instead of 644
Click to expand...
Click to collapse
Downloading the latest vendor image. Will keep you updated....
Suhas_JS said:
Downloading the latest vendor image. Will keep you updated....
Click to expand...
Click to collapse
Thanks!
Suhas_JS said:
Downloading the latest vendor image. Will keep you updated....
Click to expand...
Click to collapse
I appreciate your help throughout all of these releases
krisyarno said:
I appreciate your help throughout all of these releases
Click to expand...
Click to collapse
Pleasure's all mine. When we can not do something on our own, the least we could do is to assist someone who is more capable.
Coming back to the point, I am using Amaze & EX Explorer to replace the said files.
Strangely, I am getting various error messages, like "Insufficient space".
Also, everytime I try and copy a folder, it wont show up until I restart the device.
I know this is little too much for you to imagine. I'll may be post a short GIF in some time for you to get a gist of the issue.
Thanks and apologies for the story.
Worked out fine with your instructions, only had to clear data and cache of pixel launcher to get round icons. Thanks!
Tested, substratum works but no night light
syfo said:
Worked out fine with your instructions, only had to clear data and cache of pixel launcher to get round icons. Thanks!
Click to expand...
Click to collapse
Wich permission did you use for the build prop? 600 or 644?
Sent from my Nexus 6P using XDA-Developers Legacy app
Congratulations to me... I think I screwed up my phone. All of a sudden Substratum started working (may be I had done everything alright???). Applied a couple of overlays and voila!!! The phone does a factory reset by itself and get stuck at the Google animation. Interestingly, it's the new animation that came with the OPR6 mod. Don't know where I went wrong. I have currently switched my cell off. Maybe I need to reflash everything again???
bigcelo75 said:
Wich permission did you use for the build prop? 600 or 644?
Click to expand...
Click to collapse
600
Suhas_JS said:
Congratulations to me... I think I screwed up my phone. All of a sudden Substratum started working (may be I had done everything alright???). Applied a couple of overlays and voila!!! The phone does a factory reset by itself and get stuck at the Google animation. Interestingly, it's the new animation that came with the OPR6 mod. Don't know where I went wrong. I have currently switched my cell off. Maybe I need to reflash everything again???
Click to expand...
Click to collapse
I don't believe there is a need to wipe if your phone factory reset itself. There may be a chance that it didn't successfully factory reset. I would reflash stock system.img and stock vendor.img. That should undo everything and let you boot up
noooooo said:
Tested, substratum works but no night light
Click to expand...
Click to collapse
Same here. Is there a fix for that yet @krisyarno?
Sent from my Nexus 6P using XDA-Developers Legacy app[/QUOTE]
Sent from my Nexus 6P using XDA-Developers Legacy app
Not to contradict OP but I used 644 for files (.prop and apk's) and 755 for folders. Also I don't know if it helps but at first I didn't have night light and installed the "pixel" apk (inside the overlay folder), rebooted the device and voila! After that just cleared pixel launcher cache and that took care of the round icons.