I've read reports from users with the Moto z variant (not z play) having successfully applied rootless substratum themes. I've setup substratum and Andromeda plugin to install the Swift black theme and the overlays are installed but I cannot enable them. I have security patch April and aware of Google's decision to disable any custom overlays automatically. The work around was to install an overlay (with Andromeda enabled), reboot, then enable it in the manager tab of substratum. The problem is when I reboot then enabling Andromeda, the overlays don't show for managing but in offline mode they show up.
Mine is working with out any problems
cobolmx said:
Mine is working with out any problems
Click to expand...
Click to collapse
That's good to hear that it works for our phone. How did you go about actually enabling the overlays? I tried enabling Andromeda first then install the overlays then rebooted to then enabling Andromeda again but the option to enable doesn't show nor show any overlays. Maybe it's the theme I'm using?
Make sure you did enable selected theme after rebooting
Mine is working ?
You need to do following:
1. enable andromeda with the script
2. compile and update selected theme (don't apply it)
3. reboot
4. enable andromeda again
5. apply the theme from substratum app
btw @DroneDoom your substratum app looks different then mine, are you using latest (922)?
yaatzek said:
You need to do following:
1. enable andromeda with the script
2. compile and update selected theme (don't apply it)
3. reboot
4. enable andromeda again
5. apply the theme from substratum app
btw @DroneDoom your substratum app looks different then mine, are you using latest (922)?
Click to expand...
Click to collapse
Yes I just tampered with the settings to use night theme. I tried using Swift black substratum theme (Nexus/pixel version) using your method and it doesn't do anything on step 5.
Did you granted storage permissions for substratum?
yaatzek said:
Did you granted storage permissions for substratum?
Click to expand...
Click to collapse
Yes. I even granted substratum access to install from unknown sources.
Maybe it's something with the theme? Did you tried other? Since oreo apeared I use Dejan's themes and everything works ok.
yaatzek said:
Maybe it's something with the theme? Did you tried other? Since oreo apeared I use Dejan's themes and everything works ok.
Click to expand...
Click to collapse
I tried the nineteen theme and nothing... Actived plugin, build & update, reboot, enable plugin again, enable selected. The overlays never turn green just stay pink and notice no change regardless.
Something has came to my mind is it possible that an app called "Island" might be affecting this? What it does is creates a sandboxed partition and creates a copy of the system partition for sandboxing apps. I've noticed my overlays copy over to there when substratum has done it's compilation.
The partition runs in parallel with my personal profile while the other is designated as a "work" profile.
try this theme Swift Black Substratum Theme +Oreo & Samsung theme that's the one i'm using, also be sure if when compiling see any errors that's why is not applying it, I had some at the beginning, the apps that were throwing where the docs apps , for those i exclude them from compile, after that all went smooth
DroneDoom said:
Something has came to my mind is it possible that an app called "Island" might be affecting this? What it does is creates a sandboxed partition and creates a copy of the system partition for sandboxing apps. I've noticed my overlays copy over to there when substratum has done it's compilation.
The partition runs in parallel with my personal profile while the other is designated as a "work" profile.
Click to expand...
Click to collapse
Well you answered yourself
Just an update, still not able to activate overlays. I've uninstalled the partition that an app created that I thought was the problem. Reinstalled substratum and tried the process again, no luck.
I really don't have a clue then. Maybe ask in official g+ community.
does substratum also applies its themes to google apps? like google calendar?
JonasVFC said:
does substratum also applies its themes to google apps? like google calendar?
Click to expand...
Click to collapse
Yes it does
After leaving this alone for a bit, I finally got it to work. The Andromeda plugin works well with magisk Su and performed the same method as mentioned here in this thread.
I cant'use substratum.
I have installed Andromeda and run the script . The andromeda app Grant the acces ( Green) but When i open substratum all show me verification failed.
Have you any ideas
Android 8.0 June. Patch . Stock
Related
Some apps like supersu or xposed app settings dont open on firetv.
Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes.
To fix those apps and make em run, you need the xposed module “Holo Themer“.
Its very important that you take the version 3.0 because with all newer versions you might get bottles bootloops when the module is enabled.
Even with that 3.0. you might get a bootloop, but there is a fix for that:
https://forum.xda-developers.com/fire-tv/general/protip-how-to-fix-bootloop-caused-t3552052
The theme which is working fine for me is the “Material Dark“ one.
Enjoy your Supersu settings and xposed settings etc.
zroice said:
Some apps like supersu or xposed app settings dont open on firetv.
Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes.
To fix those apps and make em run, you need the xposed module “Holo Themer“.
Its very important that you take the version 3.0 because with all newer versions you might get bottles bootloops when the module is enabled.
Even with that 3.0. you might get a bootloop, but there is a fix for that:
https://forum.xda-developers.com/fire-tv/general/protip-how-to-fix-bootloop-caused-t3552052
The theme which is working fine for me is the “Material Dark“ one.
Enjoy your Supersu settings and xposed settings etc.
Click to expand...
Click to collapse
I hope this works & that it might be implementable outside of XPosed some how.
Do you know if this will also fix the ES File Explorer "Sorry, test failed. This feature cannot run on your device" bug too ?
More info on it here: https://forum.xda-developers.com/showpost.php?p=71704440&postcount=15
Wonder if this will let us change settings in SuperSU to be able to get ES File Explorer Root to work correctly ???
well you can change super su settings with that fix.
xposed is necessary
zroice said:
well you can change super su settings with that fix.
xposed is necessary
Click to expand...
Click to collapse
Was finally able to try it & it let me update the included SuperSU. And that fixed all my ES File Explorer Root option failing problems. So thanks. This option did the trick. Which actually makes sense since when we first rooted our FTV1's doing a normal update in SuperSU when that popped up was part of the process. Will include more details over in the ES File Explorer thread. :good:
Thanks again for sharing this.
FYI, I do deactivate the Holo Themer module to lessen the device random rebooting. So it's good to only have it active on as needed basis.
Big thanks for this info. I can finally change su settings from prompt to grant permission for rooted apps.
blue1978 said:
Big thanks for this info. I can finally change su settings from prompt to grant permission for rooted apps.
Click to expand...
Click to collapse
But make sure you keep it deactivated or you will start to see multiple random restarts to your device. Only turn it on when needed. Which shouldn't be often. Also turning it on/off requires a reboot too.
Y314K said:
But make sure you keep it deactivated or you will start to see multiple random restarts to your device. Only turn it on when needed. Which shouldn't be often. Also turning it on/off requires a reboot too.
Click to expand...
Click to collapse
I didn't have any issues leaving it enabled.
Hey all!
As you all know, Wileyfox has started rolling out Nougat for their devices, starting with the codenamed marmite family (Swift 2, 2 Plus and 2X models). With this new update, Wileyfox has also included a bunch of BLOATWARE I personally NEVER expected from them. I mean, I didn't request ads in my launcher, and why do I need to forcefully use Truecaller dialer instead of the cleaner, AOSP-based one? That's why I've created this Wileyfox Debloater tool, to keep the system apps as clean and stockish as possible.
App removals included:
- AndroidPay
- BasicDreams
- BookmarkProvider
- Google Books
- Chrome
- CMFileManager
- Drive
- Duo
- Gmail
- GooglePrintRecommendationService
- GoogleTTS
- Hangouts
- Keep
- Maps
- Google Music
- News and Weather
- PhotoTable
- talkback
- Google Videos
- WFChromeCustomization
- Youtube
- Contacts
- FoxHole
- Mms
- SnapdragonGallery
- TrueCaller
- All bundled-apps from /system/vendor/bundled-app
- Possibly more in the future.
(Note: All the moved Google Apps were removed for the sole reason that they can also be downloaded from the Play Store.)
App additons / other features included:
- Google Contacts, in replacement of the half-dummy, prebundled Contacts app (which was missing link with the Dialer).
- Google Dialer, in replacement of TrueCaller.
- Google Messages, in replacement of Wileyfox Mms app.
- AOSP's Launcher3, in replacement of FoxHole (Wileyfox's Launcher).
- Framework and permission files for Google Dialer to work.
- Small tweaks in the build.prop, including drop of min processors to work from 2 to 1, and rise of maximum processors to work from 4 to 8, as well as increasing the Android compiler default amount of processors from 4 to 6.
- Possibly more in the future, too.
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
(To learn how to properly upgrade your device, kindly check post [URL="https://forum.xda-developers.com/swift-2/development/debloat-wileyfox-debloater-quickly-t3587536/post72258926#post72258926"]#25[/URL])
2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Downloads:
- For the latest Wileyfox Swift 2, Swift 2 Plus and Swift 2X firmware: Wileyfox-TOS118C-Debloater--11-05-17.zip
(For version TOS089 check Wileyfox-TOS089-Debloater--10-04-17.zip)
- For more Wileyfox devices, coming soon
Installation instructions:
1. Update your device to Nougat
2. Unlock your bootloader and flash TWRP
3. Download the latest version zip
4. Boot into TWRP, make a backup if you wish (although is highly recommended), choose Install and locate and flash the ZIP.
5. Reboot and enjoy!
6. Are you missing missed calls notifications? Is the caller ID always showed as a number instead of a contact name during phone calls? Check post #16!
Uninstall instructions:
Check post #6
Enjoy, and don't forget to leave a Thanks if you loved it!
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
rivierakid said:
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
Click to expand...
Click to collapse
That is also a possibility but:
1. Launcher3 conflicts with the already installed launcher, so it's impossible to get that out of the way
2. I got latest version working here using the required libraries (extracted from a Pixel), so yeah, probably both possibilities are just fine
And for the third one, just wanted to say there's no need to reactivate them (if you manage to deactivate them, ofc), and, all of the packages the script moves are stored in a safe place (/system/__bloat), so they can be restored from there
I don't remember if I had a problem with a previous OTA update for Wileyfox, but I was not able to install an update without reactivation a disabled app.
I'm not sure...
You could select a default launcher and the phone has really enough RAM, so I think it is not necessary to remove the FoxHole from the system.
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
The final solution for this is LineageOS, if they provide the source
Excellent! Thanks for providing this...such a stupid shame that Wileyfox decided to do this. I'm just hoping that they now release their sources so that we can start working on a proper release of Lineage!
*Edit: Nice! https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937/commits/all*
JT
rivierakid said:
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
Click to expand...
Click to collapse
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Hello,
thanks for your effort to the community.
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
linuxct said:
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Click to expand...
Click to collapse
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
MCPoppa said:
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
Click to expand...
Click to collapse
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
jdtanner said:
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
Click to expand...
Click to collapse
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
linuxct said:
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
Click to expand...
Click to collapse
Everytime i installed twrp i got stuck in a bootloop :/
MCPoppa said:
Everytime i installed twrp i got stuck in a bootloop :/
Click to expand...
Click to collapse
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
linuxct said:
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
Click to expand...
Click to collapse
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
MCPoppa said:
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
Click to expand...
Click to collapse
I explained it last night here, but I also stated it in the OP:
linuxct said:
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
[B]2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.[/B]
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Click to expand...
Click to collapse
linuxct said:
I explained it last night here, but I also stated it in the OP:
Click to expand...
Click to collapse
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
MCPoppa said:
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
Click to expand...
Click to collapse
Try flashing it to your recovery partition, my guess is that now that DM-verity is disabled everything should work fine
Cheers!
Quick update post after two days of usage, yesterday I noticed I didn't receive any notifications on missed calls, and that the caller ID always showed as a number although I had it added as a contact.
I realised that I didn't have any "Phone" app chosen as default in Android settings, so I was missing those notifications until I opened the Google Dialer app.
In case it happens to you, to sort it out go into Settings > Apps, then hit the gear in the top right corner and make sure you've a config similar to this one (Launcher3, Google's "Phone" and Google's "Messages" chosen as default Home, Phone and Messaging apps).
I hope this is clear for everyone, since it's not something I can fix on my side/requires the user to do the change
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Ianharding said:
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Click to expand...
Click to collapse
Firsts things first: After heavily modding the system like you did on Marshmallow, make sure not to update your device through the regular OTA but using a recovery image like the ones posted in this device's forum.
For magisk: are you sure you flashed it correctly? Magisk disables that dmverity message you are mentioning, so maybe you installed an old version or wasn't properly flashed.
My advice is: download everything: the recovery image, the debloater and Magisk. Boot into TWRP, wipe EVERYTHING if possible, including Data cache dalvik cache and system partitions. Once done, flash the recovery image zip, and right after that, without rebooting, flash the debloater and magisk. Reboot and everything should work perfectly
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
digidude512 said:
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
Click to expand...
Click to collapse
As soon as you root any Marshmallow/Nougat phone Android Pay will not work, according to this article
I have never used Android Pay so it doesn't make any difference to me. My phone is much better now that I have debloated it. I also installed Evie Launcher and Halo Browser, both small minimalist apps and everything is really smooth.
Instead of a Debloater, could the Stock ROM not be debloated and rezipped as a custom 'Lite' version?
I AM NOT A DEVELOPER, I in no way claim to have made any of this myself, I'm just here to say how I manage to get as close to having Pixel software on my Galaxy S7 G930V as possible.
Basically I'll divide this into three main areas. ROM, Add-on Mods, and Apps.
Read All the way through before starting so as to not miss anything.
Also the add-on mods are installed at the same time as the ROM. That way you keep safety net and what not.
Lets start with the ROM, I am using Ufirm_QE2_Hybrid_Nougat_Rom_FlashFire_Install Status Official For VZW S7FLAT by CVertigo1 / jrkruse
jrkruse said:
Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Go to Step 3 Below
Click to expand...
Click to collapse
To Flash Files in Odin simply launch Odin (Downloads later)
click on each button (Labeled BL, AP, etc.) and select their respective files that were extracted from the archive.
Each respective file's label has each corresponding label. (AP at the beginning of the file name, means put it in AP slot)
Then boot phone into download mode, press home, download, and volume down keys all simultaneously.
Connect it to computer and press the begin button in Odin.
jrkruse said:
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. I'm not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
Click to expand...
Click to collapse
Rooting is very simple for this phone once the Eng Kernel has been flashed.
Here is @jrkruse's Guide:
jrkruse said:
This Root Method For S7 Nougat
Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison]
Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix
Nougat_S7_Root_2_79_All.zip For Ufirm Includes Fingerprint Fix
Download Nougat Eng Boot.img Flash in odin
S7_SU_2_79_Root_Unroot_WO_Tweaks_V3.zip Old method
S7_VOLTE_ICON_FIX_ALL_VARIANTS.zip
HotSpot_Fix_VZW_QA2.zip
HotSpot_Fix_VZW_QA4.zip
HotSpot_Fix_VZW_QC5.zip
HotSpot_Fix_VZW_QC9.zip
HotSpot_Fix_VZW_QF2.zip
Directions:
1. Shut off the phone and boot into download mode (volume down, home, and power). Use Odin And Flash Nougat_S7_Edge_EngBoot.tar.md5 In AP Slot
2. When the phone reboots, plug in phone to computer unlock developer options and enable USB debugging and Disable Verify Apps Over USB.
3. Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.zip and run root.bat from your PC. If you Have Windows 10 from inside the Nougat_S7_Root_2_82_All_Carriers_V2 folder you may need press and hold shift and right click and click open command window here from the dialog box then in command prompt type name of the root bat you want to run and hit enter
4. This will install root when done phone will reboot
5. The process wipes dalvik cache so it will take a few minutes to reboot
6. If having problems getting Grant SuperSU dialog to come up you can delete the SuperSU app and root will be granted instantly to all root request
Give phone a few min to settle open developer options set animation scales .05 and others to .05
@JUSMEJOSE for Eng Boot.img
Original Thread
Click to expand...
Click to collapse
jrkruse said:
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma[/B]
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source
Click to expand...
Click to collapse
Options I selected in Aroma:
Verizon Stock
NoName System UI Mods
Open Source Ad Blocking
Pixel Boot Animation
Manual Debloat
Removed Every thing except Samsung TTS and Samsung Gallary / Camera (you can remove if you prefer to use google camera, DO NOT REMOVE if you plan on using zero camera.)
I don't use the google camera because on my S7 the video records the audio out of sync with the video, I haven't figured out how to fix it. but zero camera allows me to use Photos app instead of gallary so.... yea. (Requires a purchase of the root app for alt gallery)
That's about it for the ROM install.
**note these were installed in FlashFire with the ROM so as to pass safty net.
Now here are the add-on mods I used:
Open-GApps - to get pixel icons, and connectivity service
Android 8 Emojis
iYTB Vanced (Modded YouTube)
Google Lens
Zero Camera Mod
Copy those mods onto internal storage with the ROM install and add them into FlashFire during the ROM install. Place them after the ROM zip, but before the Format Cache / Wipe System less Super SU.
Files To Download ROM / Add-on Mods
ODIN:
Odin.zip
ADB Root Files:
ADB_Root_G930U_QE2Files.zip
ODIN Firmware:
UFIRM_G930_Odin_Firmware.zip
FlashFire Flashable AP:
FlashFire_Flashable_G930UFirmware.zip
ROM installer:
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
ADB Setup:
adb-setup-1.4.3.exe
Open GApps:
http://opengapps.org/
iYTB / Android O emojis / Google Lens (Mirrored into one download for simplicity sake alt donwloads listed later):
Flashables.zip
Zero Camera Mod:
Thread Here
Next is apps
Pixel 2 Wallpapers -
Buttons remapper - get material button layout
Nova - get a better pixel launcher
ForceDoze - bettery battery life
SystemUI Tuner
Pixel 2 Wallpapers:
https://forum.xda-developers.com/android/apps-games/port-live-earth-wallpapers-t3481640
All are on google play except for Pixel 2 Wallpapers at the moment of me typing this.
You will need to grant Force Doze and SystemUI Tuner ADB permissions using a command prompt on windows.
Comands:
SystemUI Tuner:
adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS
adb shell pm grant com.zacharee1.systemuituner android.permission.DUMP
ForceDoze:
adb -d shell pm grant com.suyashsrijan.forcedoze android.permission.WRITE_SECURE_SETTINGS
adb -d shell pm grant com.suyashsrijan.forcedoze android.permission.DUMP
And thats it!
Original Authors / Threads
@jrkruse / @CVertigo1 (AWESOME ROM)
Thread
@Master_T / @ZaneZam (iYTB)
Thread
@ZeevoX (Google Lens)
Thread
@Winb33 (Android O Emojis)
Thread
@zeroprobe (Zero Camera Mod)
Thread
@Pranav Pandey (Pixel Wallpapers)
Thread
ANY OTHER Developer who I did not list
THANKS A TON DEVS!!!! :good: :laugh: :good:
Let me know if anybody has anything else they have done to get this close!
I appreciate you putting all the links and mods into the same place. I have never flashed using FlashFire before (on a G930V) and this was an excellent guide for me.
My only trip up was I didn't understand the language about Camera/Google Camera/Zero Camera Mod and I tried installing the zero mod while debloating the camera off. So I will have to go back and do that.
I skipped the "flashables" youtube, emoji, lens but may end up going back for those.
Thanks again.
Update: I found a cool way to have the new Google now page in the launcher.
Launcher App:
First is the actual app. Typicaly I would just say use Nova but on the pixel launcher the Google Now page looks different than on other third party apps. I wanted this look, so here is how I found a way to get that new Google Now pag to appear on other launchers.
Step one, if you installed Google lens mod, you should be able to get the pixel launcher from the play store, if not get it from XDA labs or APK mirror. Set Google. Set it as your default launcher. Next you will need any third party launcher and Tasker. I'm using Lawn chair Launcher. (On Google play). Use button mapper pro to map pressing the home button to launch third party app. Go into Tasker and make a task, so that whenever Google pixel launcher is launched, open third party launcher. As long as the pixel launcher is set as your default, the new Google now page will appear in apps like Nova and action launcher.
I'm *loving* this so far. Thanks to you and the devs that have worked on each stage of this.
I'm doing:
Verizon Stock
No UI Mods
No Ad Blocking
Pixel Animation
"PlayStore" Edition (not BS free, not manual)
Flashing GApps
Flashing Emoji
My only issue is like you described with the camera. It was working initially and then it updated and the update is causing problems. Also, the double home button launch doesn't work without a 3rd party app (and with screen off with no root).
So I can either figure out a way to always ignore camera app update and use a 3rd party app for launch (screen on only)
or
Will the S8 camera option include the gallery app and not be cleared by the "PlayStore" option?
MCrly7 said:
I'm *loving* this so far. Thanks to you and the devs that have worked on each stage of this.
I'm doing:
Verizon Stock
No UI Mods
No Ad Blocking
Pixel Animation
"PlayStore" Edition (not BS free, not manual)
Flashing GApps
Flashing Emoji
My only issue is like you described with the camera. It was working initially and then it updated and the update is causing problems. Also, the double home button launch doesn't work without a 3rd party app (and with screen off with no root).
So I can either figure out a way to always ignore camera app update and use a 3rd party app for launch (screen on only)
or
Will the S8 camera option include the gallery app and not be cleared by the "PlayStore" option?
Click to expand...
Click to collapse
I believe so, however I don't know, this would be a better question to ask in the ROM's Thread. the link is in the OP
It says you flashed open gapps, does it just re write over existing gapps with no problems
Hello.
I'm trying to apply this theme (bought on Play Store of course) and it doesn't work asides for already themed apps from OOS dark theme.
Is there anything special to do in order to make it work ?
Thanks for your help.
Did you choose Oxygen version in the left top corner of the app list? Swift black is working well for me on OB6.
Same thing happened tonme..infact none of substratum themes working. overlay getting installed successfully but nothing is getting themed..not even after a reboot..tried clearing cache nd dalvik but still nothing..
eerrroh said:
Hello.
I'm trying to apply this theme (bought on Play Store of course) and it doesn't work asides for already themed apps from OOS dark theme.
Is there anything special to do in order to make it work ?
Thanks for your help.
Click to expand...
Click to collapse
It was a little tricky for me to but here's what I did
1. Open Swift black selected OOS from the top drop down
2. Make sure your select the option for every app that has a drop down confirming your app version# for each one Instagram, play store etc....
3. Click the FAB SELECT BUILD /UPDATE
4. repeat step 2
5. click FAB SELECT BUILD/INSTALL
make sure you the "THEME INSTALLED WITH NO ERRORS" message in status bar wait 30 sec for system UI to restart you should notice some changes now
REBOOT- PROFIT ENJOY:good: much WoW,??
STEP BY STEP VIDEO: ??
https://youtu.be/i0kaWJWjllU
galaxy s4 nutjob said:
It was a little tricky for me to but here's what I did
1. Open Swift black selected OOS from the top drop down
2. Make sure your select the option for every app that has a drop down confirming your app version# for each one Instagram, play store etc....
3. Click the FAB SELECT BUILD /UPDATE
4. repeat step 2
5. click FAB SELECT BUILD/INSTALL
make sure you the "THEME INSTALLED WITH NO ERRORS" message in status bar wait 30 sec for system UI to restart you should notice some changes now
REBOOT- PROFIT ENJOY:good: much WoW,
STEP BY STEP VIDEO:
https://youtu.be/i0kaWJWjllU
Click to expand...
Click to collapse
Thanks, it works for me.
The steps are different in custom ROM tho (OmniROM case)
1- Build and update
2- Reboot
3- Activate
Yep, it's odd imo ,but that's how it works lol
Or, after installing the themes, reboot. Then go back into substratum to the manager page and select all themes and then enable selected. You will have to reboot again for apps like Google to to theme. Enjoy.
version 2 out now~~~
After researching the framework info, I found out MEA G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download 47.1.A.12.179 stock rom for G8141 or G8142 ROM, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get problems with encryption
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. (G8141) recover my system backup using twrp, if you have dual sim G8142 you have to follow step 4 as well
https://www.androidfilehost.com/?fid=11050483647474827606
(version 2, replaced google apps, more debloat, more stable system)
to recover, simply make a backup of something, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover my system data
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files (2), (3), (4), xposed
3.4 install keyboard
https://androidfilehost.com/?fid=818070582850495399
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
can also just download this, put it in notepad++ and save as build.prop, push to system with 0600 permission
https://pastebin.com/0iyaEJGf
https://youtu.be/Yl4mUPdjMKc
proof it works
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
Where is the build.prop file?
amakuramio said:
currently uploading! done in few hrs
After researching the framework info, I found out ASEAN G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download ANY G8141 or G8142 ROM that is 179 version, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get force close
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. recover my system backup using twrp, for g8142 you have to follow step 4
uploading currently, isdone within 15 mins
to recover, simply make a backup of anything, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files 2, 3, 4, xposed
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
todo: need to optimize settings.apk (is zipaligned, but lags)
Click to expand...
Click to collapse
How about screen on time im using turbo75b(with mods and xposed) , i usually get more than 9 hours screen on time when have a little gaming and alot browsing and streaming videos, so my question is this rom is super debloated? Or no.
And next one is how many hours you get screen on time without enabling stamania mode.
Blackghosthm said:
How about screen on time im using turbo75b(with mods and xposed) , i usually get more than 9 hours screen on time when have a little gaming and alot browsing and streaming videos, so my question is this rom is super debloated? Or no.
And next one is how many hours you get screen on time without enabling stamania mode.
Click to expand...
Click to collapse
on wifi I get 8 hrs to 8.30
on 4g, drains very fast
but newer versions are faster (after march, sony use 8.1 compiler for faster apps)
its 89% upload
its also possible that I combine system from 179 with turbo rom 75, it should be compatible and easy to do.
jianlin3062 said:
Where is the build.prop file?
Click to expand...
Click to collapse
the build.prop file is in ''root/system/build.prop'' I use notepad++ to edit it on pc then push it back to the phone
twrp file manager, copy build.prop to sd card, copy to pc, replace maple with maple_dsds and g8141 with g8142, its easy to do
1. Can't log into Google And because it's constantly trying to connect to Google, it's lagging
2. Lots of ANRs that pop up for a second and close themselves
3. You forgot to leave a keyboard, LOL. I use gBoard anyway
4. Feels better than .75 anyway.
5. Launches with the .205 JanJan's kernel, but the WiFi doesn't work
I'll keep testing. THANK YOU A LOT!!!
upd. In China the whole Google is banned, and I only can log in via VPN-ned WiFi, which I can't use unless I install keyboard, lol.
upd. So, I've disabled the security on my WiFi. I've connected to the network from the very beginning. But still no success. Just black screen.
upd. I've flashed OpenGAPPS, thinking that it would help. And, guess what? Black screen.
I went further:
Chrome STOPS.
Google Earth STOPS.
Maps STOP.
Many cool features DO work, but because I can't log into my Google account, sadly, the FW for me is unusable here. I can't keep figuring out why, because I need a working device by tomorrow...
saved-j said:
1. Can't log into Google And because it's constantly trying to connect to Google, it's lagging
2. Lots of ANRs that pop up for a second and close themselves
3. You forgot to leave a keyboard, LOL. I use gBoard anyway
4. Feels better than .75 anyway.
5. Launches with the .205 JanJan's kernel, but the WiFi doesn't work
I'll keep testing. THANK YOU A LOT!!!
upd. In China the whole Google is banned, and I only can log in via VPN-ned WiFi, which I can't use unless I install keyboard, lol.
upd. So, I've disabled the security on my WiFi. I've connected to the network from the very beginning. But still no success. Just black screen.
upd. I've flashed OpenGAPPS, thinking that it would help. And, guess what? Black screen.
I went further:
Chrome STOPS.
Google Earth STOPS.
Maps STOP.
Many cool features DO work, but because I can't log into my Google account, sadly, the FW for me is unusable here. I can't keep figuring out why, because I need a working device by tomorrow...
Click to expand...
Click to collapse
you did something completely wrong
backup your data (if you want, prefer clean) flash a 179 stock firmware erase all otherwise force close, then restore my system, then flash the 4 zips, reboot after the first one, then flash last 3 zips I posted in the link up there, then xposed, then reboot
I really have 0 problems here. I thought I kept swiftboard in it? hmm. I will make a patch zip with keyboard in it, hopefully it helps. you can also push a keyboard app in system/app/Appname/app.apk 0644 permission
https://www.apkmirror.com/apk/swift...swiftkey-beta-7-0-8-363-android-apk-download/
can you do me a favor? make a screenshot of the system app scroll down, then send me. Maybe I uploaded wrong system?
do you can xposed patch on turbo final v2 rom?
it stucked.
amakuramio said:
you did something completely wrong
Click to expand...
Click to collapse
1. Flashed .179 with FULL WIPE.
2. pushed the TWRP and Kernel via ADB.
3. Entered the TWRP and restored your /system from the backup.
4. Flashed the Kernel again, just in case. (JanJan's 179)
5. Rebooted back into the TWRP and flashed the other three zips (2-Patching, 3-Magisk and 4-Permissive)
6. Flashed the Xposed v90-sdk26-beta3
7. Booted system.
Passed the welcome.
Installed the Xposed Manager and SwiftKey.
All the way get the FC messages that pop up for a second and disappear by themselves.
-Messaging keeps stopping.
Opened the Play Store, it kept loading something for a minute and then ...stopped too.
-Google Play Services keeps stopping.
This is 100% the right /system you've provided, but something just doesn't work.
I'm attaching a screen record from today.
I will update this post as it goes.
Also am gonna try:
-AndroPlusKernel 12 -
-Magisk 16.4 (instead of 16.0) -
-OpenGapps (instead of included) -
-Magisk-Systemless-Xposed (instead of flashing /system included) - works either way
saved-j said:
1. Flashed .179 with FULL WIPE.
2. pushed the TWRP and Kernel via ADB.
3. Entered the TWRP and restored your /system from the backup.
4. Flashed the Kernel again, just in case. (JanJan's 179)
5. Rebooted back into the TWRP and flashed the other three zips (2-Patching, 3-Magisk and 4-Permissive)
6. Flashed the Xposed v90-sdk26-beta3
7. Booted system.
Passed the welcome.
Installed the Xposed Manager and SwiftKey.
All the way get the FC messages that pop up for a second and disappear by themselves.
-Messaging keeps stopping.
Opened the Play Store, it kept loading something for a minute and then ...stopped too.
-Google Play Services keeps stopping.
This is 100% the right /system you've provided, but something just doesn't work.
I'm attaching a screen record from today.
I will update this post as it goes.
Click to expand...
Click to collapse
pushing a keyboard into the system will also help, but that is the way to do it, yes
do you have g8141 or g8142? google play issue is related to not updating proper build prop to your device
amakuramio said:
g8142
Click to expand...
Click to collapse
Oh, i forgot to mention it. I have extracted your build.prop (with added extra lines against the stock .179), changed the lines to the g8142 and saved it. I replace the build.prop to the one containing "g8142" lines right after restoring your /system, setting the rights to 0644, before the first boot.
lGIKDk said:
do you can xposed patch on turbo rom?
Click to expand...
Click to collapse
I can actually do that, but in the opposite way. Debloat exactly in the same way as turbo rom. its possible, but first I want people to try this out and see if ti works, before I make a rom that doesnt work.
saved-j said:
Oh, i forgot to mention it. I have extracted your build.prop (with added extra lines against the stock .179), changed the lines to the g8142 and saved it. I replace the build.prop to the one containing "g8142" lines right after restoring your /system, setting the rights to 0644, before the first boot.
Click to expand...
Click to collapse
can you try to enter system/priv app/gmscore, then inside the folder delete lib and gmscore.apk, then replace it with this
https://www.apkmirror.com/apk/googl...2-8-66-090400-200774163-android-apk-download/
GmsCore.apk with permission 0644
same with phonesky
https://www.apkmirror.com/apk/googl...6-08-all-0-pr-200628961-android-apk-download/
then reboot with dalvik and cache removed (2 things only) there may be LIB compatibility issues.
Hell if google play doesnt work for g8142, I can also do nanomod! which is very light on the battery
nanomod needs xposed, but it works with xposed, so
amakuramio said:
can you try to enter system/priv app/gmscore, then inside the folder delete lib and gmscore.apk, then replace it with this
Click to expand...
Click to collapse
working on it. 15 minutes please. nanomod would be AWESOME btw
p.s. you forgot a file in an inappropriate place: "/system/Settings zipaligned.apk" - wtf is that lol
---------- Post added at 05:41 PM ---------- Previous post was at 05:21 PM ----------
amakuramio said:
Hell if google play doesnt work for g8142
Click to expand...
Click to collapse
I've already tried the whole ROM with the OpenGapps yesterday, and it didn't work, but I gave it a try again with your files. :good: I didn't even replace the Build.prop - let it stay where it is.
So, on a clean flash:
1. I've replaced the GmsCore.apk, Phonesky.apk with the ones you gave me the links for
2. Gave them the proper permissions
3. Cleaned Dalvik
Result? Google Play Services keeps stopping.
Messaging and other apps kept FC too.
I don't think it's 8142's problem. I think there's something wrong with your /system
It is not only the Gapps problem, because Messaging and some other apps randomly FC too. Check the video in my previous post. It's a common problem, not only the Gapps fail.
Note! I don't do dirty flashes for testing purposes: every and each time I flashed everything cleanwise again, from scratch, with the flashtool rom, to make 100% sure.
Now, I don't know what to do. Any suggestions?
*trying one more time while you're thinking*
saved-j said:
working on it. 15 minutes please. nanomod would be AWESOME btw
p.s. you forgot a file in an inappropriate place: "/system/Settings zipaligned.apk" - wtf is that lol
---------- Post added at 05:41 PM ---------- Previous post was at 05:21 PM ----------
I've already tried the whole ROM with the OpenGapps yesterday, and it didn't work, but I gave it a try again with your files. :good: I didn't even replace the Build.prop - let it stay where it is.
So, on a clean flash:
1. I've replaced the GmsCore.apk, Phonesky.apk with the ones you gave me the links for
2. Gave them the proper permissions
3. Cleaned Dalvik
Result? Google Play Services keeps stopping.
Messaging and other apps kept FC too.
I don't think it's 8142's problem. I think there's something wrong with your /system
It is not only the Gapps problem, because Messaging and some other apps randomly FC. Check the video in my previous post. It's a common problem, not only the Gapps fail.
Note! I don't do dirty flashes for testing purposes: every and each time I flashed everything cleanwise again, from scratch, with the flashtool rom, to make 100% sure.
Now, I don't know what to do. Any suggestions?
Click to expand...
Click to collapse
if nothing works, then it means it must be a framework issue. I am on G8141 without any issues.
thanks for testing so far. I don't have g8142 so I cannot know.
1. in xposed install http://repo.xposed.info/module/com.thermatk.android.xf.fakegapps (do this first, just enable it, dont reboot in recovery yet)
2.delete the following
/system/app/GooglePrintRecommendationService/GooglePrintRecommendationService.apk
/system/app/GoogleAnalyticsProxy/GoogleAnalyticsProxy.apk
/system/app/GoogleExtShared/GoogleExtShared.apk
/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
/system/priv-app/GmsCore/GmsCore.apk
/system/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk
/system/priv-app/GoogleExtServices/GoogleExtServices.apk
/system/priv-app/GoogleFeedback/GoogleFeedback.apk
/system/priv-app/GoogleOneTimeInitializer/GoogleOneTimeInitializer.apk
/system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
/system/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
/system/priv-app/Phonesky/Phonesky.apk
3. then flash nanodroid https://downloads.nanolx.org/NanoDroid/Stable/ then reboot. you might want to go options of google play then clear data afterwards.
(4. extra, see if settings folder in app is same permission as other folders, and if apk inside is also same as other apk in the different folders)
cant google login. it just black screen
amakuramio said:
if nothing works, then it means it must be a framework issue. I am on G8141 without any issues.
thanks for testing so far. I don't have g8142 so I cannot know.
Click to expand...
Click to collapse
The difference between them is minimal. Somehow it worked for me with OpenGapps. I'll set the phone up and leave it as it is, as it's 4:00 am already. I'm glad it worked somehow.
I'll test it during the week, though i've already found several issues, like, in Album app it doesn't allow to move from the internal memory to the folders on the SD card already existing (don't know why?? - Google Photos app does it with no problem)
lGIKDk said:
cant google login. it just black screen
Click to expand...
Click to collapse
Did you read the conversation here before posting your message? You're not alone in this problem.
Try flashing .179 again, with all the wipes, etc - following the instruction.
And flash Open Gapps right before you boot up in the system. It has JUST worked for me when I tried it in the last time, though it hadn't worked for me yesterday!
Active Screen, XZ2 Camera and some other XZ2 features, Xposed, WiFi, data, everything works just fine.
Had to spend two nights to achieve it, though.
Attaching a video of working Xposed. My device recognizes as Pixel XL because I have a Daydream Enabling magisk module.
amakuramio said:
I can actually do that, but in the opposite way. Debloat exactly in the same way as turbo rom. its possible, but first I want people to try this out and see if ti works, before I make a rom that doesnt work.
Click to expand...
Click to collapse
ok. i wait.
i hope completly version
amakuramio said:
After researching the framework info, I found out ASEAN G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download 47.1.A.12.179 stock rom for G8141 or G8142 ROM, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get problems with encryption
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. (G8141) recover my system backup using twrp, if you have dual sim G8142 you have to follow step 4 as well
https://www.androidfilehost.com/?fid=674106145207498283
to recover, simply make a backup of something, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover my system data
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files (2), (3), (4), xposed
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
can also just download this, put it in notepad++ and save as build.prop, push to system with 0600 permission
https://pastebin.com/0iyaEJGf
https://youtu.be/Yl4mUPdjMKc
proof it works
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
todo: need to optimize settings.apk (is zipaligned, but lags)
Click to expand...
Click to collapse
Are you sure, this room created by you not @machao44
At least have him the credit,but thanks for debloating and modifying the rom.
Same as others Google play services crash like base rom(m-rom).
Blackghosthm said:
Are you sure, this room created by you not @machao44
At least have him the credit,but thanks for debloating and modifying the rom.
Same as others Google play services crash like base rom(m-rom).
Click to expand...
Click to collapse
though the rom is made by sony I got it from MEA version from XPERIFIRM and modified by me I did include HIS xposed fix (not directly).
What I did copy was the framework intents those are the same as his. If I modified framework myself and installed his xposed then because of mismatch the whole thing would crash so I had to force the same intents to match the signature.