Smaller LTE Data Icon Android P - Google Pixel XL Themes, Apps, and Mods

Flash these in TWRP if you want a smaller LTE Data Icon. I also have one for removing it completely. These will also be in my next updated Aroma installers.
Oct Pie
https://www.androidfilehost.com/?fid=1322778262904023071
Oct Magisk
https://www.androidfilehost.com/?fid=1322778262904023073
DP3 uploaded
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thought you might want to see how it looks.
Big improvement over the large LTE stock P version.

Thanks for your hard work and releasing it us!

I uploaded new Magisk versions just now. Updater-script problems.

So for the magisk version we can stick it in the magisk modules folder , reboot and it should see it ?

Phalanx7621 said:
So for the magisk version we can stick it in the magisk modules folder , reboot and it should see it ?
Click to expand...
Click to collapse
Flash TWRP

Phalanx7621 said:
So for the magisk version we can stick it in the magisk modules folder , reboot and it should see it ?
Click to expand...
Click to collapse
Flash in TWRP only.
Edit. It is not a module. Just a Magisk vrthemer zip that installs systemlessly.

liam_davenport said:
If it's a Magisk Module go into Magisk > Modules and the + icon go to where the zip is located and install it
Click to expand...
Click to collapse
Flash in TWRP only.
Edit. It is not a module. Just a Magisk vrthemer zip that installs systemlessly.

Tulsadiver said:
Flash in TWRP only.
Edit. It is not a module. Just a Magisk vrthemer zip that installs systemlessly.
Click to expand...
Click to collapse
Thanks for clarification

Cause bootloop on DP3.

Queentus said:
Cause bootloop on DP3.
Click to expand...
Click to collapse
Which one did you flash?

Tulsadiver said:
Which one did you flash?
Click to expand...
Click to collapse
Sorry for not making it clear back then. I flashed the older mod which I believe was made for DP2, and it caused system ui crashing.
No problems with the DP3 updated one and thanks for the awesome work!:good:

Magisk installation failed on DP3, Magisk 16.4.
Log below.

Related

Magisk problem with xiaomi.eu MIUI 8.5.2.0 Stable

Hi all.
I make clean install of stable 8.5.2.0 from xiaomi.eu and now I have problems with Magisk.
On weekly builds I installed Magisk v12 containing hide fix + xiaomi safetynet fix and everything works file. Root and SafetyNet. But right now, when I Install, Root don't work but safetyNet does.
When I flash Magisk v12 downloaded via Magisk Manager, root works, but safetynet don't.
Any solution?
So right now it looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Used files you can find here:
Magisk-v12.0.zip
Magisk12.0_Hide_fixed.zip
MagiskManager-v4.3.3.apk
xiaomi-safetynet-fix-v1.9.1.zip
https://mega.nz/#F!PRAQDJwD!39Zd4yxHanX1lb_gD2YIew
dariusz666 said:
Hi all.
I make clean install of stable 8.5.2.0 from xiaomi.eu and now I have problems with Magisk.
On weekly builds I installed Magisk v12 containing hide fix + xiaomi safetynet fix and everything works file. Root and SafetyNet. But right now, when I Install, Root don't work but safetyNet does.
When I flash Magisk v12 downloaded via Magisk Manager, root works, but safetynet don't.
Any solution?
So right now it looks like:
Used files you can find here:
Magisk-v12.0.zip
Magisk12.0_Hide_fixed.zip
MagiskManager-v4.3.3.apk
xiaomi-safetynet-fix-v1.9.1.zip
https://mega.nz/#F!PRAQDJwD!39Zd4yxHanX1lb_gD2YIew
Click to expand...
Click to collapse
Are you using Xposed? If yes, try removing it.
alediniz said:
Are you using Xposed? If yes, try removing it.
Click to expand...
Click to collapse
No, ofc no. I use magisk on dev/beta releases before and I know I can't have Xposed or SuperSU.
I tried it for a week and safetynet test was always working.
The problem is that, even if locked and with no restriction on battery use, it was randomly loosing root.
I installed Magisk12.0_Hide_fixed and then xiaomi-safetynet-fix from TWRP.
Then I updated the manager from Play Store and reboot.
Any idea?
In the meanwhile I switched back to SuperSu.
BTW I also tried installing systemless SuperSu and then Magisk but root wasn't working at all.
I should try that again after the recent SuperSu updates.

Lockscreen wallpaper Tint Remover

Removes Lockscreen wallpaper dimming tint and the notification pulldown tint as well. Flash in TWRP. For stock roms.
DP4
https://www.androidfilehost.com/?fid=5862345805528052629
DP4 Magisk version
https://www.androidfilehost.com/?fid=5862345805528053144
8.1 July update
https://www.androidfilehost.com/?fid=5862345805528052627
8.1 July update Magisk version
https://www.androidfilehost.com/?fid=5862345805528053136
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Magisk version fails
prot- said:
Magisk version fails
Click to expand...
Click to collapse
Could you elaborate some? Which one, fails how?
Tulsadiver said:
Could you elaborate some? Which one, fails how?
Click to expand...
Click to collapse
Yeah sorry dude
Log attached.
Also would like to know why it's trying to do all those things?
I mean that is a huge log of changes.. wow..
This is the magisk one on Android p
prot- said:
Yeah sorry dude
Log attached.
Also would like to know why it's trying to do all those things?
I mean that is a huge log of changes.. wow..
This is the magisk one on Android p
Click to expand...
Click to collapse
It is flashing the systemuigoogle.apk. Are you completely stock?
Edit:. Also, are you on magisk 16.3 or higher? I just flashed this on my Pixel and it works fine.
Appreciate the effort though dude I hate that tint
Will this work on dp5?
Tulsadiver said:
It is flashing the systemuigoogle.apk. Are you completely stock?
Edit:. Also, are you on magisk 16.3 or higher? I just flashed this on my Pixel and it works fine.
Click to expand...
Click to collapse
Stock latest 16.7 magisk.
Same issue on dp5
prot- said:
Stock latest 16.7 magisk.
Same issue on dp5
Click to expand...
Click to collapse
I don't know why some people have problems and some don't on Magisk. My suggestion is to remove Magisk, reroot, use regular one to get where you want to be, then install Magisk manager.

OnePlus 7T HD65BA OxygenOS 11.0.0.2 Patched Magisk/Boot.img

Does anyone have a link to this, please?
Magisk patched:
HD65BA_OxygenOS_11.0.0.2_magisk_patched.img
drive.google.com
Stock:
HD65BA_OxygenOS_11.0.0.2_stock.img
drive.google.com
THank you mate, much appreciated
jatson said:
Magisk patched:
HD65BA_OxygenOS_11.0.0.2_magisk_patched.img
drive.google.com
Stock:
HD65BA_OxygenOS_11.0.0.2_stock.img
drive.google.com
Click to expand...
Click to collapse
Hi,
Would you please be so kind and help us out with the recent version 11.0.1.1 HD65BA? May thanks for your support!
Otherwise I cannot update as I need root from my usage...
By the way: Is there a ways to patch the boot-image myself? How to extract it to let Magisk Manager do the job?
Hi,
Sorry for the delay. Here you go.
Magisk patched:
HD65BA_OxygenOS_11.0.1.1_magisk_patched.img
drive.google.com
Stock:
HD65BA_OxygenOS_11.0.1.1_stock.img
drive.google.com
joegreat said:
Otherwise I cannot update as I need root from my usage...
Click to expand...
Click to collapse
If you already updated to Android 11 and rooted your device, you can easily update to the newer revs and keeping your root access. Check here how to do that.
A usefull tool for the updates (if you did not know it yet): https://oxygenupdater.com/
joegreat said:
By the way: Is there a ways to patch the boot-image myself? How to extract it to let Magisk Manager do the job?
Click to expand...
Click to collapse
Actually yes. I'm doing the same way like you mentioned. I'm using Payload Dumper to get the boot file from the image. You can find the details here.
When you got the needed boot.img file you can simply "ask" magisk to do the job for you:
- Select Magisk install in the app
- Choose "Select and Patch a file"
- select the boot.img you want to patch
- click "let's go"
Hope I could help.
Does anyone have the patched 11.0.2.1 image please?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can someone make a magisk patched image of this version? (Indian)
thanks in advance
jatson said:
Magisk patched:
HD65BA_OxygenOS_11.0.0.2_magisk_patched.img
drive.google.com
Stock:
HD65BA_OxygenOS_11.0.0.2_stock.img
drive.google.com
Click to expand...
Click to collapse
I Have flashed the patched one. But it doesn`t work. the phone stop after reboot an stand still display black.
After flash the stock rom, the phone boot normal but bootloop.
atnoword said:
I Have flashed the patched one. But it doesn`t work. the phone stop after reboot an stand still display black.
After flash the stock rom, the phone boot normal but bootloop.
Click to expand...
Click to collapse
Do you have a screenshot about your actual version running on your phone?

Question Rooted and debloated with C.47 update (some apps, mainly google, would open and crash)

I don't know if it's just me, but I updated to C.47 by:
Magisk uninstall, restoring stock images.
installing the update
Magisk install to inactive after OTA completes
Reboot.
I have 4 modules. USNF, osm0sis busybox binary, debloater and systemless hosts.
The only way I was able to get them to work was by disabling all modules, rebooting, finding the google play store APK download from APKMirror and installing it.
Now, I have randomly cloned APKs, but they were only ones I debloated. I debloated again and they vanished.
I admit this thread might be a huge waste of your time to read, but if someone is having this trouble, it might bail them out
I am in same situation like u with Google play store and Google services play crash .I try everything but no luck .finally idowngrade to os 11. But I'm very intested to know why Google applications crash .The only magisk module installed is : Octavia dialer A12.
Wow, good to know this is happening and that you found a workaround. I guess I'll probably wait a few days to install this and see if other people are having issues.
In c47 version, the 5G option returned in network settings?
DavidKalil10 said:
In c47 version, the 5G option returned in network settings?
Click to expand...
Click to collapse
Not for me
Skenderbeggar said:
Not for me
Click to expand...
Click to collapse
I've just discovered a workaround isign the app force LTE/5G. With this app is possible to open the Network settings and force the 5G as it was possible in Android 11 using *#*#4636#*#*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It fails when reaching the middle
Moka UA said:
It fails when reaching the middle
View attachment 5566125
Click to expand...
Click to collapse
are you rooted?
Yes
Moka UA said:
Yes
Click to expand...
Click to collapse
go to magisk, uninstall magisk. pick restore images. DO NOT REBOOT. install the update. go back to magisk. install magisk to inactive slot. reboot
i'd disable whatever modules you have enabled.
aNGERY said:
go to magisk, uninstall magisk. pick restore images. DO NOT REBOOT. install the update. go back to magisk. install magisk to inactive slot. reboot
i'd disable whatever modules you have enabled.
Click to expand...
Click to collapse
Ok..i have root zygisk ..Is there a problem with that?
Moka UA said:
Ok..i have root zygisk ..Is there a problem with that?
Click to expand...
Click to collapse
Zygisk is fine, only installed modules should be disabled when you update to avoid possible issues. Most modules won't have any issues, though.

Question how do i know which version of magisk patched boot img to flash?

how do i know which version of magisk patched boot img to flash? i recently updated to the newest version via OTA on stock, but i forgot to run the install again before rebooting, would it be the 12.C47 version that i flash?
The one which fits the OOS version number. So, if it's C47 then you need a boot.img made for C47 (patched with magisk).
ekin_strops said:
The one which fits the OOS version number. So, if it's C47 then you need a boot.img made for C47 (patched with magisk).
Click to expand...
Click to collapse
ah i see, thanks!
Veid71 said:
how do i know which version of magisk patched boot img to flash? i recently updated to the newest version via OTA on stock, but i forgot to run the install again before rebooting, would it be the 12.C47 version that i flash?
Click to expand...
Click to collapse
Settings > About Device > Version > Build Number
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure you've done all the OEM Unlock, etc first
djsubterrain said:
Settings > About Device > Version > Build Number
View attachment 5587231
Make sure you've done all the OEM Unlock, etc first
Click to expand...
Click to collapse
Thanks man, I was able to flash it and install, I enabled zygisk and put a bunch of apps on the deny list but for some reason I'm still failing YASNC for both basic and CTS I know it's off topic but any advice on how to fix that?
Veid71 said:
Thanks man, I was able to flash it and install, I enabled zygisk and put a bunch of apps on the deny list but for some reason I'm still failing YASNC for both basic and CTS I know it's off topic but any advice on how to fix that?
Click to expand...
Click to collapse
Jump in here :
Magisk
Magisk - The Universal Systemless Interface, to create an altered mask of the system without changing the system itself.
forum.xda-developers.com
Just Incase anyone else runs into this issue on that magisk forum there's a universal safetynet fix (UNSF) that you can download and it'll fix it

Categories

Resources