Database Develop

[MOD/THEME][APK]BluQseT - FU green "gingerbread - systemUI.apk

This is for 10.1
Now, I can't stand green in my Android. I simply can't. I can't stand TouchWiz.. All the colors thrown together like a box of crayons. I've modified my systemUI.apk and framework-res.apk to change the quick settings to blue and the V ticks as well. If you want em, use em.
I did this on GigaWatts 2.0 ROM and I'm not responsible if any other stock rom will fck up from this.
Get the systemUI.apk here. - This is for the quick settings and the tickers in the drop-down menu.
Get the framework-res.apk here - This is for the Settings menu's tickers and switches.
Install:
1. Open your root browser of choice.
2. Browse to /system/priv-app/ and locate systemUI.apk, make a backup, always make a backup.
3. Replace it with my systemUI.apk and set the permissions JUST as they were on the old one, otherwise this won't work.
- You can stop here and restart if you don't want to deal with the next section of crashes. It's a one time procedure but it's a bit annoying to deal with none the less. Enjoy the quick settings icons.
4. Go to /system/framework and locate framework-res.apk, make a backup, always make a backup.
5. Replace it with my framework-res.apk.
6. At this point your system will crash with "android.process.acore has stopped". This is normal for a framework-res.apk replacement. Basically you can make one press in between each "Ok" when the system repeatedly crashes.
7. First manage to set all the permissions.
8. Then manage to go into "apps" in Settings and locate "Contacts Storage" under "All", then clear data and boom, crashing stops.
9. Re-add your Google account.
It should look like this :victory:
{
"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"
}

ok first thanks and its stuff like this that i do on my phones that makes me want to root my Tab. if i had one that (i have 10.1 T520) that towelroot worked on this would already be installed.
thanks for your work

fletch33 said:
ok first thanks and its stuff like this that i do on my phones that makes me want to root my Tab. if i had one that (i have 10.1 T520) that towelroot worked on this would already be installed.
thanks for your work
Click to expand...
Click to collapse
You're welcome.
Don't wanna trip Knox? Since Towelroot?

FWIW, towelroot won't trip knox. Are you saying it doesn't work on your Tab? It rooted my 8.4 an did not trip knox.

He means towelroot didn't work on his 10.1.
Verstuurd vanaf mijn SM-T320 met Tapatalk 4

I guess this won't work on the 8.4? Wat do I have to edit in the systemui.apk in order to change the colors?
Sent from my XT897 with Tapatalk 4

wallpaper
can you provide me with your wallpaper

[Q] mtk6582

can you make it work on mtk6582
i can install xpossed but when i reboot he gets stuck in bootloop, i have a alcatel c7 pop

tinocnm said:
can you make it work on mtk6582
i can install xpossed but when i reboot he gets stuck in bootloop, i have a alcatel c7 pop
Click to expand...
Click to collapse
Hey, I have the same device as you. and its working. but not all modules (i.e. GravityBox).
And heres what you do if you get on bootloop. reboot device, as soon as you see the alcatel logo, press any hardware button repeatedly until it vibrates. maybe after about 5 times pressing that button repeatedly and vibrating, it should be able to boot again.

kryptonify said:
Hey, I have the same device as you. and its working. but not all modules (i.e. GravityBox).
And heres what you do if you get on bootloop. reboot device, as soon as you see the alcatel logo, press any hardware button repeatedly until it vibrates. maybe after about 5 times pressing that button repeatedly and vibrating, it should be able to boot again.
Click to expand...
Click to collapse
I was looking, what xpossed do You use, 2.3.1?
Have you tried gravitybox 3.0.2?, seems it works on c5

tinocnm said:
I was looking, what xpossed do You use, 2.3.1?
Have you tried gravitybox 3.0.2?, seems it works on c5
Click to expand...
Click to collapse
Im using the latest Xposed Framework. And no i havent tried gbox 3.0.2 yet. i think the reason why gbox wont work because this device is just messed up. with all the custpack partition and symlinked system apps and all. the SystemUI.apk doesnt even contain .pngs. its just xml codes. the .pngs are separated in another apk.

kryptonify said:
Im using the latest Xposed Framework. And no i havent tried gbox 3.0.2 yet. i think the reason why gbox wont work because this device is just messed up. with all the custpack partition and symlinked system apps and all. the SystemUI.apk doesnt even contain .pngs. its just xml codes. the .pngs are separated in another apk.
Click to expand...
Click to collapse
When you say the latest you mean 2.6.1 or 2.7 beta?
I tried xposed 2.3.1 with gbox 3.0.2 and the latest it says don't find the requested system.
what modules do You use, I just want to make a transperent status bar with smart hide

{
"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"
}
Sent from my ALCATEL ONE TOUCH 7041D

Thanks, a lot very useful

Accidentally forgot to give root permission to Xposed

Hi! Running Xposed v79 + Xposed Installer 3.0 alpha 4 w/ one module (Swype Row) on my OnePlus One (CM12.1 | Android 5.11 | rooted with SuperSU v2.46).
I installed the framework (via TWRP 2.8.6.0) and installer with no issues; the framework shows as installed. Then, I added the "Swype Row" module and rebooted. When I rebooted, Xposed said it didn't get root permissions. But, I didn't see a SuperSU prompt or I might've missed it. SuperSU shows it was "denied", but that must've been one quick prompt.
How can I get Xposed to ask for root access again so I can approve it?
{
"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"
}

ikjadoon said:
Hi! Running Xposed v79 + Xposed Installer 3.0 alpha 4 w/ one module (Swype Row) on my OnePlus One (CM12.1 | Android 5.11 | rooted with SuperSU v2.46).
I installed the framework (via TWRP 2.8.6.0) and installer with no issues; the framework shows as installed. Then, I added the "Swype Row" module and rebooted. When I rebooted, Xposed said it didn't get root permissions. But, I didn't see a SuperSU prompt or I might've missed it. SuperSU shows it was "denied", but that must've been one quick prompt.
How can I get Xposed to ask for root access again so I can approve it?
Click to expand...
Click to collapse
Just open SuperSU tap on Xposed and change to allow
Sent from my SPH-A120

mattzeller said:
Just open SuperSU tap on Xposed and change to allow
Sent from my SPH-A120
Click to expand...
Click to collapse
Where exactly do I tap? The screenshot above shows that blank log when I tap "Xposed Installer - #"

ikjadoon said:
Where exactly do I tap? The screenshot above shows that blank log when I tap "Xposed Installer - #"
Click to expand...
Click to collapse
Make sure re-authenticate it checked, reinstall Xposed app and then run it, see if you get the prompt
Sent from my SPH-A120

mattzeller said:
Make sure re-authenticate it checked, reinstall Xposed app and then run it, see if you get the prompt
Sent from my SPH-A120
Click to expand...
Click to collapse
OK, it worked! But, I actually just unchecked my module and rebooted from the Xposed app. Then, out of nowhere, the prompt came! Thank you, thank you!

Very helpful, thanks.

MikePancake6 said:
Very helpful, thanks.
Click to expand...
Click to collapse
You had the same problem tonight? haha, what luck. Glad it worked for you, too.

Magisk Hide

Magisk Hide doesn't seem to be working when it comes to my automobile's app, Uconnect. I'm rooted and now the Uconnect app states that I'm using an unsupported device. It worked before rooting.View attachment magisk_log_20181022_153305.log
{
"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"
}

tried clearing apps data?

kamilmirza said:
tried clearing apps data?
Click to expand...
Click to collapse
Yes. I even uninstalled, then reinstalled the Uconnect app.

destiple said:
Yes. I even uninstalled, then reinstalled the Uconnect app.
Click to expand...
Click to collapse
THIS great module might help :fingers-crossed:

Destiple, can you confirm whether MagiskHide Props Config, which kamilmirza referred you to, worked?
Alternately, did you find another solution to get Uconnect working?

If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).

Didgeridoohan said:
If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).
Click to expand...
Click to collapse
That's very good to know. I'm nervous about running a Canary build on my normal phone, but I'll see if I can find a spare to test it on.
Will the new MagiskHide be on the next Magisk update, or is it several versions away from being in the stable build?

Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.

Coop9 said:
Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.
Click to expand...
Click to collapse
Good to know! I tried it - hiding the manager by itself wasn't enough. But once I added Uconnect to the apps being hidden, *then* the app finally loaded.
Of course, upon trying to log in, the app immediately crashes. Would that have anything to do with it being added to the MagiskHide list?

Hotel app Marriott detects Magisk and root

Please see discussion already at
https://www.reddit.com/r/Magisk/comments/yf8gyu
Security message when running an app
Hello I installed the Marriott app this morning, and when I go to run it, i get that security message along the bottom third of the screen, and the app shuts down. What is causing that?
forum.xda-developers.com
Calling on the broader community to look at this, as I only start to have this today. I have also tried HuskyDG's Magisk Delta which is said to have brought back MagiskHide, but I failed. Thanks

try this https://forum.xda-developers.com/t/guide-howto-use-banking-apps-on-your-rooted-device.4530801/
supermansaga said:
Please see discussion already at
https://www.reddit.com/r/Magisk/comments/yf8gyu
Security message when running an app
Hello I installed the Marriott app this morning, and when I go to run it, i get that security message along the bottom third of the screen, and the app shuts down. What is causing that?
forum.xda-developers.com
Calling on the broader community to look at this, as I only start to have this today. I have also tried HuskyDG's Magisk Delta which is said to have brought back MagiskHide, but I failed. Thanks
Click to expand...
Click to collapse

Thanks. It does seem to work, except I didn't perform these following steps mentioned. Maybe they are not applicable to the latest 3.1.1 version on GitHub instead of play store? Also don't think I truly understand how to use template. Finally, there is a popup to ask me to uninstall Magisk? Probably not a good idea.
Under the Preference head, tap on Select hide methods -> Check API requests, Intent queries, ID detections -> Tap OK
Under the Template config head, tap on 0 additional apps invisible -> Check Magisk, LSPosed and HMA

{
"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"
}

lelakon666 said:
try this https://forum.xda-developers.com/t/guide-howto-use-banking-apps-on-your-rooted-device.4530801/
Click to expand...
Click to collapse
It worked several times but has since been busted. Maybe I didn't set it up correctly?

I heard Magisk Delta by HuskyDG could hide it from detection. Has anyone been brave enough to try? Well, I tried and it didn't work. I tried the whitelist mode by leaving Marriott out of the SuList and many other banking apps too. But it still detects root. Marriott app version 10.13.1. Older version say 10.12.0 and below should survive.

marriott’s new version 10.15.0 appears to have fixed the over-detection issue. Shamiko is now 0.7.1. not sure if relevant