Database Develop

[MOD] GS3 SecEmail.apk & Exchange.apk with Exchange Security Disabled

This was cross-posted in the US GS3 forum, but I figured you international guys might want this as well.
Below are the Mail and Exchange apks for the S3 with exchange security disabled. This is for those who use exchange support at work, but who hate entering a pin or password every time they want to unlock their phone. Many of us use low-level security corporate exchanges that don't require a pin, so the apk files below remove that security.
DISCLAIMER: If your place of employment's exchange policy requires the use of a pin, please be advised that use of these apks may be punishable up to termination of employment, as well as other possible legal action. Some companies take their exchange security VERY seriously and this mod is only for those whose policy does not require a pin but are unnecessarily prompted to enter one anyway. Please speak with your IT department before using these files as I will not be held responsible for any mis-use of this app or any collateral damage that may ensue. YOU HAVE BEEN WARNED. In the event you need to get back to stock, I have also posted stock apks below which will get you back to stock. Download the 'Return to Stock' link, unzip the downloaded file, and then just push them to /system/app/
1) Delete any exchange email accounts from your phone and remove any shortcuts to the mail app from your device
2) If applicable, remove any exchange administrators from Settings -> Security -> Device administrators
3) Download the 'Hacked Mail apks' file linked below. THIS IS NOT A FLASHBLE ZIP. The apk files were just too big for XDA's upload limit and so I had to zip them up and host them online. Once downloaded, unzip and grab out the 2 apk files inside (SecEmail.apk and Exchange.apk)
4) Mount your phone's system as R/W (either using Root Explorer or 'adb remount')
5) Copy the newly downloaded SecEmail.apk and Exchange.apk files to system/app/ via root explorer and overwrite the older file if/when it asks, or you can just push the files to system/app via adb
6) Set permissions on both apks as rw-r--r--
7) Reboot
8) After reboot, create a shortcut if you want and then open up the Email app and set up your corporate account.
7) You will be prompted to enable security policy midway through... this is normal so hit 'OK' and it will not ask you to enable security any further.
As previously mentioned in the disclaimer, you can use the Stock apks to get back to stock if you run into any issues. Just download the 'Return to Stock' link below, extract the 2 apks out, and follow the same process as above.
Donations always appreciated. Enjoy
LINKS:
Hacked Mail apks: http://d-h.st/8xa
Return to Stock apks: http://d-h.st/aAk
I'd prefer you to use the links directly above, but in the event they aren't working or are blocked in your country, try using these instead:
http://forum.xda-developers.com/showpost.php?p=29011281&postcount=9

Thanks friend
excellent work!

You are the man! I've been waiting for this.
Thank you!
Sent from my GT-I9300 using xda premium

Is there an hacked version of the stock google email floating around?

gkaipale said:
You are the man! I've been waiting for this.
Thank you!
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
You didn't ask for it, it's included on my custom since my first release .

jhericurls said:
Is there an hacked version of the stock google email floating around?
Click to expand...
Click to collapse
Edit: found it
http://forum.xda-developers.com/showthread.php?t=1117452

just what I was looking for only problem is the link dont work :crying:

Same here any chance of posting a link that works :fingers-crossed:

Just tested the links and they are working fine for me. Perhaps they are blocked in your county.
That being said, here are some links secondary links via dropbox. I'd prefer everyone to use the links in the OP as flooding the links below can end up blocking my db account, but they're here for others experiencing download issues
Hacked mail apks: http://db.tt/SXwjYCeK
Return to stock: http://db.tt/cGMIbkVJ

Not working for me
I followed the steps but when I open Email app to add account it gives me a FC error...
I m on stock ROM XXBLFB..pls help

wanam said:
You didn't ask for it, it's included on my custom since my first release .
Click to expand...
Click to collapse
Exactly dear Wanam...
I downloaded your ROM, extracted those 2 apks, all working fine, really very appreciate!

Thanks a lot, this seems to actually work. The strange thing is, i've replaced those 2 apk files on a stock ODEXED rom (!!!), yet it works anyway. I guess none of the other apk/odexes depend on those 2.
Thanks again

InfX said:
Thanks a lot, this seems to actually work. The strange thing is, i've replaced those 2 apk files on a stock ODEXED rom (!!!), yet it works anyway. I guess none of the other apk/odexes depend on those 2.
Thanks again
Click to expand...
Click to collapse
do I need to delete the odex files also after copying these apks? it's not working for me
Sent from my GT-I9300

doesn't quite work like the ones from the HTC forums.
where in you can still choose to do patter lock. after adding an exchange account.
the mod for SIII disables all types of lock aside from Pin and Password after adding an account. although you can add a pattern lock before adding an exchange account and it still works.

kuberchib said:
do I need to delete the odex files also after copying these apks? it's not working for me
Sent from my GT-I9300
Click to expand...
Click to collapse
You do. Ive renamed the 2 original apk files along with the corresponding odex files, placing the new ones in there instead. Works perfectly ok for me. I am on 4.0.4 XXALF5, stock, odexed. Ill probably switch to deodexed soon, though, but it does work for me right now anyway.

baste07 said:
doesn't quite work like the ones from the HTC forums.
where in you can still choose to do patter lock. after adding an exchange account.
the mod for SIII disables all types of lock aside from Pin and Password after adding an account. although you can add a pattern lock before adding an exchange account and it still works.
Click to expand...
Click to collapse
This mod disables thr EXCHANGE administrating those locks for you, it doed NOT affect your ability to setup a lock on a device on your own, in any possible way. In fact, replacing just the apks mentioned, it technically cannot do anything to affect it.

Thanks a lot for that man. What about jellybean I be seen the exchange.apk became exchange2.apk
Is there a difference?

Working great, just needed to delet odex files

I am running the ATT version, with a CM10 preview.. will these work on my version?

there's a bug or my company admin is just good detecting this. it is able to block it
Sent from my GT-P7510 using Tapatalk 2

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

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...

Can anyone provide framework-res.apk from 7.4.8 with wallpaper enabled?

Anyone have a working framework-res.apk from the 7.4.8 stock ROM that has wallpapers enabled? (I did try myself in the past but it resulted in a bootloop)
If so would you be able to upload it :good:
Thanks

Odd, the latest version has a lot of safeties to prevent a bootloop. When was the version of my wallpaper fix that you used? Also you will need to know how to use adb if you plan on copying a already modified framework-res because if you copy and paste over it it could go wrong because of permissions sometimes not carrying over or the fact you would be replacing a system file that's in use.
Sent from my LG-P769 using Tapatalk

It was quite a while ago now, guess I could try again but just wanted to see if anyone had one that they had confirmed working to save any issues.

[TUTORIAL] Manually port T-Mobile Alliance ROM 5.0.1 to Verizon Dev Edition (12/8/15)

** Got Verizon Note 4 Dev Edition to work with Alliance T-Mobile ROM!! Data, calling, sms, mms work ! I smell a daily driver! I am not a developer, but this manual port taught me a lot. This was a personal project of trial and error, and research that turned into a stable ROM. Thought I'd share how I did it. I do not take credit for this ROM or kernel**
DISCLAIMER: Your warranty is now void. Please be careful make a nandroid of your current Verizon ROM. I am not responsible if you break your phone or lose data on your device! Read this whole OP!
**This is using the BETA version of Alliance ROM for T-Mobile Note 4. Download the Alliance BETA and read the thread: http://forum.xda-developers.com/not...-0-1-allianceromn910t-18-themes-huge-t3085560 to get an idea of the features of this ROM. Give lacoursiere18 and hsbadr a thanks and donate to them for making this great ROM and kernel.
Follow these steps one after the other and don't stop**
1. Make sure you are on a OAF Lollipop ROM without xposed installed. I think I used Rick's OAF Lollipop ROM originally. Download the most recent multisystem kernel. I am on BOG modem so I'm pretty sure any Lollipop modem will work with this.
2. On your Verizon Lollipop ROM make copies on your SD card of:
- system/buildprop.xml & cscversion.txt
- system/etc/apns-config.xml
- system/etc/permissions/verizon_net_sip_library.xml & vzwapnlib.xml
- system/lib/libril.so & libsec-ril.so
- system/apps/VzwActivationAgent, vzwapnpermission & **SecSetupWizard2013**
- system/framework/VZWAPNLib.apk
- system/privapp/VZWAPNService & secmms_candy folders
- system/csc folder
4. Reboot into recovery and make a TWRP backup of everything except SD card.
5. While in recovery dirty flash Alliance ROM BETA on top of your lollipop ROM OAF (Wipe everything EXCEPT data, internal storage, and SD). Then flash the most recent multisystem kernel.
6. Once booted up and apps are optimized wait until the screen turns off by itself. Download root browser and delete system/privapp/diagmonagent.apk and system/lib/libdiagmonagent.so because at startup it was sending some kind of diagnostics and thought it was messing with the data drop. Ever since these changes and a reboot data has been stable!
Reboot
7. Using root browser, swap those copied files in the appropriate file location. Change them to the correct permissions (the folders get 0755 and the files 0644, compare with other files and folders that are in place already. Make sure you change the permissions on all folders copied over and their contents. If a permission is incorrect or you leave a file out there can be issues and a restore might be needed.). Let apps optimize. **Longest Step**
Reboot
8. Edit feature.xml in the system/csc folder and add:
<CscFeature_RIL_ForceConnectMMS>true
</CscFeature_RIL_ForceConnectMMS>
Above the two bottom tags:
</FeatureSet>
</SamsungMobileFeature>
This enables auto download mms when data is toggled off !
Reboot
9. Perform a factory reset within the settings. Let phone relax for like 10 mins after it boots. Go through the setup wizard and then reboot.
Reboot into recovery
10. Make an backup in TWRP and you have your own custom ROM
I'm pretty sure this ROM is not compatible with xposed but it is very customizable, smooth, and it comes with a lot of features built in.
**READ ME**
Bugs:
- Silent mode is only available using the toggle. Volume down only goes to vibrate.
**
- Battery section in settings is missing
- No way to remove battery percentage in status bar
(Workaround: Download "Battery Usage Shortcut" from the Playstore to access the battery section and to remove battery percentage)
**
- No way to uninstall 3mint battery mod without messing the systemui up **(see update at the bottom)**
- Now that the mobile network settings are correct the advanced calling option is avaliable but it force closes and messes up your data connection. A reflash of everything will be needed so don't click on it! (I have a feeling a Verizon app is missing)
- My volume titles are not correct (Ringtone, media, notifications, and system.) when I press the volume buttons. (**Workaround download Noyze Volume Panel for free from the developer
http://forum.xda-developers.com/android/apps-games/app-noyze-volume-panel-replacement-t2875501
Give Tombarr a thanks for developing such a slick and customizable app**)
11/18/15:
- Just started using voicemail for the first time in 6 years. Good thing because today I experienced a glitch that it would not let me hang up the phone after listening to voicemails for some reason, but it didn't do that when I was clearing voicemails. (Hangs up automatically after a certain amount of time) Maybe it happens to new voicemails. Also I'm assuming since the verizon voice mail app isn't installed I get a weird unreadable verizon text when I get a new voicemail.
- One hand mode is not in the settings. Not sure why
Any suggestions or thoughts about these current bugs would be helpful.
I cannot guarantee all Alliance settings will work (stay away from performance), but most does work and it's awesome!
This manual port is now stable and buttery smooth! All basic phone functions work. Let me know if you come across any bugs or issues not related to Alliance settings. I will try to help fix it.
Thanks Stedrocklp for taking the time to try and get this working. Jal3223 thanks for sharing that key porting info!!! Wouldn't be possible without your help! Thanks hsbadr for developing Multisystem kernel ! Thanks lacoursiere18 for creating this ROM !
UPDATE:
To update Alliance settings to the most recent version and remove 3mintbattery mod download the newest T-Mobile Alliance ROM v1.1
1. Use ES File Explorer and click on the Alliance ROM you just downloaded to open the archive.
2.
- Extract system/privapp/SystemUI/SYSTEMUI.apk
- In the system/app folder extract AllianceControl folder (towards the top) and all the loose apps without folders at the bottom to a folder on your sd card.
3. Make a system and data backup in TWRP just in case things go wrong. Reboot system
4. Swap all those files and folders in their appropriate file locations and change the folder permissions to 755 and files to 644. Take this step slow and make sure the old files are renamed to .old or overwritten. If a permission is incorrect or you leave a file out there can be issues and a restore might be needed.
5. In system/app folder delete the old loose Alliancecontrol.apk, and delete 3mintbattery.apk
6. Reboot and enjoy!
This is the final release of this ROM so we are all up to date ! :good:

Wondering if this will work for sprint or any rom

dyra502 said:
Wondering if this will work for sprint or any rom
Click to expand...
Click to collapse
I'm pretty sure it would but you need to figure out the sprint specific apps to make the system happy. And flash your sprint kernel after you dirty flash. The dirty flash skips the setup which makes it possible to boot correctly.

Would you mind sharing the Rick's ROM that you used? I looked at his thread, but the download links are no longer available. Thank you in advance for your help!

Romans8vs1 said:
Would you mind sharing the Rick's ROM that you used? I looked at his thread, but the download links are no longer available. Thank you in advance for your help!
Click to expand...
Click to collapse
Damn thats not good. I do not think I am allowed to share the ROM, as it's not mine. But I do not know how to share it anyways. I would just odin back to 4.4.4. and go through the upgrade process to OAF. Or you can try to de-xpose MoRom after a clean flash. I think there are two things you need to remove one being the xposed installer and the other I don't know the exact name but use root browser, search for xposed in the system folder, delete it, and reboot. No sure if it will messed anything up but I don't think it will. Then dirty flash the alliance beta and continue from there. Let me know how it goes!

jcip17 said:
Damn thats not good. I do not think I am allowed to share the ROM, as it's not mine. But I do not know how to share it anyways. I would just odin back to 4.4.4. and go through the upgrade process to OAF. Or you can try to de-xpose MoRom after a clean flash. I think there are two things you need to remove one being the xposed installer and the other I don't know the exact name but use root browser, search for xposed in the system folder, delete it, and reboot. No sure if it will messed anything up but I don't think it will. Then dirty flash the alliance beta and continue from there. Let me know how it goes!
Click to expand...
Click to collapse
Thank you for your response. I ODIN'd back to OAF and went through the steps in your tutorial. My phone booted up and I then proceeded to replace the files/folders and set permissions. I thought I was careful, but once I tried to reboot, the phone would not come back up.
Is there a way to make the changes (file permissions and replacing them in the ROM) on a PC?
Is there a way to share your edited files so that we could simply paste them into the ROM?
Just thought I would ask. Thank you in advance for your assistance!

Romans8vs1 said:
Thank you for your response. I ODIN'd back to OAF and went through the steps in your tutorial. My phone booted up and I then proceeded to replace the files/folders and set permissions. I thought I was careful, but once I tried to reboot, the phone would not come back up.
Is there a way to make the changes (file permissions and replacing them in the ROM) on a PC?
Is there a way to share your edited files so that we could simply paste them into the ROM?
Just thought I would ask. Thank you in advance for your assistance!
Click to expand...
Click to collapse
Damn thats a bummer. Even if I shared the files you would still need to change the permissions. I think it is possible unzip a verizon ROM and unzip Alliance rom and replace the files and then zip it back up on the computer and then dirty flash that but everytime I zip it back up it never flashes. It seems that when I zip it back up it adds an extra folder that makes it unflashable but haven't taken the time to figure out how to make it work. Try starting over and getting the ROM to boot then make a nandroid of that so you have something to restore. This is what I did when I was trying to get everything working. Next time try not adding the camera files and .jar file and add them after a reboot. Let me know how it goes.

Added the setup as one of the files to copy over so a factory reset can be performed to make sure you're starting with a fresh system. This is the first day I did this and I had to pull the battery twice due to freezes after I factory reset. I didn't let the phone sit and let it settle. I would recommend you let it sit and relax for like 10 mins. I have not had any lock ups since this morning. Lemmi know how it goes!

After the factory reset the ROM is flying. As for the battery I cannot say yet but I know I did not have the best battery life on this ROM before. It did get me through the day so I was happy about that. I calibrated the battery but that is about it. If any devs knows any battery optimizations that can be made to the system without xposed please share!

I heard from a user that Xposed works on this ROM. I personally do not use it though. As for battery life I've noticed better results after I disabled automatic check for updates in the settings. Settings > About device > Software Updates and uncheck auto check for updates. This ROM for some reason does not have the audio issues that I experienced on MoROMs ROM. I am happy about that. Now that we finally have the 5.1.1. update I am going to try and port a ROM that looks good. If anybody wants to give this a stab with me that would be great to test multiple ROMs from different carriers and see which one gives us the best results. Thanks

Got something amazing in the works!

Nandroid backup
Can someone send me a nandroid backup of this I'm worried about messing up my phone up

Is there a way to install this rom in the same manner as the kyobi note 5 port? I'm running that now, but would like to try this one out. I've tried a few times but just can't seem to get this one up and running.
Thanks in advance and have a blessed day!
Sent from my SM-N920F using Tapatalk

TheRock40359 said:
Can someone send me a nandroid backup of this I'm worried about messing up my phone up
Click to expand...
Click to collapse
That's a big file idk how I would be able to distribute that lol

Romans8vs1 said:
Is there a way to install this rom in the same manner as the kyobi note 5 port? I'm running that now, but would like to try this one out. I've tried a few times but just can't seem to get this one up and running.
Thanks in advance and have a blessed day!
Sent from my SM-N920F using Tapatalk
Click to expand...
Click to collapse
It's not that simple. A data fix would need to be made and that is out of the scope of my knowledge. But when I have some free time, possibly this weekend, I can attempt to come up with something for you to try.

jcip17 said:
That's a big file idk how I would be able to distribute that lol
Click to expand...
Click to collapse
Could upload it to dropbox

Anyone with a Developer addition phone willing to help us none developers get root/unlocked bootloader? New exploit found but we need an .aboot from a developer phone: http://forum.xda-developers.com/note...ition-t3346422

Since I am currently on BPA1 5.1.1 running the Kyubi ported ROM and this is a 5.0.1 ROM, will I have to do downgrade my device or anything or will I be good to go to dirty flash? Thanks in advance.

stajam said:
Since I am currently on BPA1 5.1.1 running the Kyubi ported ROM and this is a 5.0.1 ROM, will I have to do downgrade my device or anything or will I be good to go to dirty flash? Thanks in advance.
Click to expand...
Click to collapse
I don't recommend dirty flashing from Kyubi. You should try clean flashing MoRom then copying those files from the system. Then dirty flash Alliance, then multisystem kernel:
http://forum.xda-developers.com/not...opment/kernel-multiystem-kernel-v1-0-t3105603
And just follow the OP instructions.

jcip17 said:
I don't recommend dirty flashing from Kyubi. You should try clean flashing MoRom then copying those files from the system. Then dirty flash Alliance, then multisystem kernel:
http://forum.xda-developers.com/not...opment/kernel-multiystem-kernel-v1-0-t3105603
And just follow the OP instructions.
Click to expand...
Click to collapse
Yeah ,I am trying to pull the files I need from my stock ROM backup that I just freshly installed on my device. I stumbled upon a forum here today called Guides There seems to be ALOT of usefull stuff in here about Porting and Building ROM's. I don't know if you have ever come across it or not.

[TUTORIAL][WIP][OPR6] Android Oreo Pixel Mod With Working Substratum

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.