Database Develop

[GUIDE] Root and Install TiBu for Lollipop Nexus 7 (2012 Wifi)

So you want the latest Lollipop image for the 2012 Wifi Nexus 7, but no root and no TiBu is holding you back?
You can root the 2012 WiFi Nexus using WUGS Root Tool kit. Get it here -> http://www.wugfresh.com/nrt/
It's real easy to use and it walks you through what you need to do once it's installed. It will download the correct root kernel, boot image, recovery and root.
Once rooted, you can go to Play Store and download the latest TiBu. As of 11/14/2014, it has been updated to work with Lollipop. No need for the Beta version anymore.
It works. I just restored all my users apps from KK with this. Works like a charm. No issues so far.
Here's your Lollipop!
{
"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"
}
https://api.soundcloud.com/tracks/78714022/download?client_id=b45b1aa10f1ac2941910a7f0d10f8e28

4.4.4 ?
Does this work with 4.4.4 ?
Thanks
---------- Post added at 03:01 AM ---------- Previous post was at 02:43 AM ----------
Oops, never mind.

Stuck on 'Searching application data .... ' forever.. :/

I flashed factory images yesterday, so my device is unlocked and I'm attempting to root it.
I've downloaded the cf-auto-root-grouper-nakasi-nexus7.zip, rebooted into bootloader, did fastboot boot the .img, it does its thing and reboots. superSU is there but no binariers :/
I've tried it several times. At one point it kept rebooting to TWRP recovery, so re-flashed boot and system.img, boots up fine, all my stuff is still there along with SuperSU but still no binaries....
Hold on, let me try again with stock recovery.
update: Having TWRP recovery flashed was causing the issue. Reflashed stock recovery in bootloader, rebooted bootloader, booted the auto root image and rebooted. SuperSU is not complaining about missing binary.
Now I'm having difficulties with Busybox. At first it said devices wasn't properly rooted. So I downloaded root checker and it said device is rooted. reopened Busybox, granted it root permissions, hit install and gave me an error about improper root installation.
Tried again and now it's saying "can't verify the integrity of the binary selected to be installed" and requesting i exit and try again.

Great! Root work on Nexus 7 wifi 2012 and android 5.0. Thanks!

Used this method last night and it installed without a hitch but I am very disappointed on how slow, Laggy and darn right unusable 5.0 is. I will wipe and go again to see if it improves but if not I will be happy to stay on KK

Eddster3000 said:
Used this method last night and it installed without a hitch but I am very disappointed on how slow, Laggy and darn right unusable 5.0 is. I will wipe and go again to see if it improves but if not I will be happy to stay on KK
Click to expand...
Click to collapse
I went and did a full wipe and that seems to have helped. Also, after the setup, are you allowing it to reinstall apps from the cloud? That can cause it to be laggy until it's done.
Remember, we are also under ART now. Under Dalvik, applications, after initially installed, would have to be "recompiled" to cache them to the Dalvik cache. This occurred when the app was launched for the first time since being installed.
Under ART, it recompiles the apps once they are installed rather than waiting for them to be launched. So, if you are having a lot of apps being reinstalled, you'll notice it might take longer to install them, and hence, since it recompiles them after install, it could slow down your device, causing it to be laggy.

thanks for the guide, it did install supersu and busybox on my nexus 7 2012 with lollipop, however, titanium backup and others apps that require root aren't working, supersu is prompting to give permission on those but they cannot execute xbin/su command

gnrsenpai said:
thanks for the guide, it did install supersu and busybox on my nexus 7 2012 with lollipop, however, titanium backup and others apps that require root aren't working, supersu is prompting to give permission on those but they cannot execute xbin/su command
Click to expand...
Click to collapse
Did you launch SuperSU after rooting? Also, you to launch Busybox and actually tell it to install.
Did you enable USB debugging in developer options? TiBu won't work without that being enabled.
If you don't see developer options in your settings, then you need to go to the About Tablet section in system settings, and then tap on Build Number seven times.
After that, then the Dev Options will show up and you can enable USB Debugging there.
After that, you'll need to go back into TiBu and then restart it (or reboot).

iBolski said:
Did you launch SuperSU after rooting? Also, you to launch Busybox and actually tell it to install.
Did you enable USB debugging in developer options? TiBu won't work without that being enabled.
If you don't see developer options in your settings, then you need to go to the About Tablet section in system settings, and then tap on Build Number seven times.
After that, then the Dev Options will show up and you can enable USB Debugging there.
After that, you'll need to go back into TiBu and then restart it (or reboot).
Click to expand...
Click to collapse
hello, the first thing i did after flashing lollipop was enabling usb debugging and then rooted with the op's recommended tool, i left it that way untill now, i really don't know what could be the cause.
Sent from my GT-I9300 using Tapatalk

gnrsenpai said:
hello, the first thing i did after flashing lollipop was enabling usb debugging and then rooted with the op's recommended tool, i left it that way untill now, i really don't know what could be the cause.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
After using WUGs toolkit to root, it tells you to first launch SuperSU and then install Busybox and ensure it's installed in /system/xbin. What they mean by that is actually launching the Busybox app and then installing all the links for the commands and such via the app itself. WUGs is just installing the apk itself but that doesn't set up Busybox. You have to actually launch the Busybox app and then tell it to install everything. That's probably why it can't find su.
Supersu just provides a way to prevent rogue apps from gaining root access without your permission. The actual "su" command is installed by Busybox.
Launch the Busybox app, tell it to install and then try again.

iBolski said:
After using WUGs toolkit to root, it tells you to first launch SuperSU and then install Busybox and ensure it's installed in /system/xbin. What they mean by that is actually launching the Busybox app and then installing all the links for the commands and such via the app itself. WUGs is just installing the apk itself but that doesn't set up Busybox. You have to actually launch the Busybox app and then tell it to install everything. That's probably why it can't find su.
Supersu just provides a way to prevent rogue apps from gaining root access without your permission. The actual "su" command is installed by Busybox.
Launch the Busybox app, tell it to install and then try again.
Click to expand...
Click to collapse
yes, i've also did install all the scripts provided by busybox, it's not the first time i've done it, that's why is really strange, maybe busybox is not correctly installing the su script (i marked the xbin folder instead of bin in busybox).
Sent from my GT-I9300 using Tapatalk

gnrsenpai said:
yes, i've also did install all the scripts provided by busybox, it's not the first time i've done it, that's why is really strange, maybe busybox is not correctly installing the su script (i marked the xbin folder instead of bin in busybox).
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Then I'm at a loss. It worked the first the time I did it and then again when I decided to do a full wipe of my device. Not sure what is going on.
You did this via WUGs correct? And, when it asked what device you had, you chose Nexus 7 2012 with the Lollipop image, correct?
Just trying to make sure you didn't miss something.

iBolski said:
Then I'm at a loss. It worked the first the time I did it and then again when I decided to do a full wipe of my device. Not sure what is going on.
You did this via WUGs correct? And, when it asked what device you had, you chose Nexus 7 2012 with the Lollipop image, correct?
Just trying to make sure you didn't miss something.
Click to expand...
Click to collapse
yeah, furthermore i reflashed lollipop twice and redo the process all over again with no luck, nevertheless, thanks for your input ?
Sent from my GT-I9300 using Tapatalk

gnrsenpai said:
yeah, furthermore i reflashed lollipop twice and redo the process all over again with no luck, nevertheless, thanks for your input ?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Ok. Sorry I couldn't help. Hopefully, you can get it figured out.
You DO have the bootloader unlocked, correct?

iBolski said:
Ok. Sorry I couldn't help. Hopefully, you can get it figured out.
You DO have the bootloader unlocked, correct?
Click to expand...
Click to collapse
indeed, i can see the unlocked padlock when the device boots, before flashing lollipop i had a kitkat custom rom (forgot the name), so i did have to unlock the bootloader. the only thing i'm missing is the su command and i don't see it in the busybox checklist of scripts to install.
Sent from my GT-I9300 using Tapatalk

iBolski said:
After using WUGs toolkit to root, it tells you to first launch SuperSU and then install Busybox and ensure it's installed in /system/xbin. What they mean by that is actually launching the Busybox app and then installing all the links for the commands and such via the app itself. WUGs is just installing the apk itself but that doesn't set up Busybox. You have to actually launch the Busybox app and then tell it to install everything. That's probably why it can't find su.
Supersu just provides a way to prevent rogue apps from gaining root access without your permission. The actual "su" command is installed by Busybox.
Launch the Busybox app, tell it to install and then try again.
Click to expand...
Click to collapse
Wut? No, su is on the system by default. It is REPLACED by the supersu zip, with the supersu.apk to control it in Android.
Busybox has nothing to do with su.

khaytsus said:
Wut? No, su is on the system by default. It is REPLACED by the supersu zip, with the supersu.apk to control it in Android.
Busybox has nothing to do with su.
Click to expand...
Click to collapse
DOH! Don't know what I was saying there. My bad. :silly: Chalk it up to a long night last night with little sleep.

I followed the directions and everything worked. only thing now is that windows doesn't see the nexus7 so i can't copy the tibu backups over...do i need to install any additional drivers?

Storage space
Haven't seen this mentioned anywhere or maybe I'm not searching properly. I have the 16GB model and my storage is now down to 6GB, is there anything I can do to fix that? I used Wugs toolkit to install twrp but I can't find the folder in my internal storage.

(Q) Manually install xposed.

I dont have a custom recovery to be able to flash the installation .zip file.
I do have root access, I have tried to manually by push the files to the correct location with correct permissions.
but it results in a bootloop.
I currently trying it on my Meizu mx4 with lollipop 5.0.1.
It used how to work without issues on K.K
Im trying it with the xposed-sdk21-arm-20150430.zip
with Xpossed 3.0 alpha2
Things I have tried.
http://bbs.flyme.cn/thread-245435-1-1.html
http://bbs.flyme.cn/thread-240899-1-1.html
Anyone have any ideas on how to get this working please
Thank you.

Did a quick search and found this:
http://forum.xda-developers.com/meizu-mx/general/mx4-flashing-recovery-t3102402
Hope that helps!

Djlatino said:
Did a quick search and found this:
http://forum.xda-developers.com/meizu-mx/general/mx4-flashing-recovery-t3102402
Hope that helps!
Click to expand...
Click to collapse
I'm not asking for a custom recovery, I know about the situation of meizu and not being open source that way.
I'm asking for a way to install Xposed successfully without a custom recovery by manually pushing the files etc.
But thank you.

If you read that thread, you'll note that in order to flash anything to begin with, you're going to need the recovery emulator "FlashGordon".
http://forum.xda-developers.com/showthread.php?t=2250555
^Spoonfeedin'

Djlatino said:
If you read that thread, you'll note that in order to flash anything to begin with, you're going to need the recovery emulator "FlashGordon".
http://forum.xda-developers.com/showthread.php?t=2250555
^Spoonfeedin'
Click to expand...
Click to collapse
I appreciate the help, I knew a app was about that could flash .zips without recovery, I will try it out.
Unfortunately it didnt work, didnt change any files in /system

punkmonkey1984 said:
I appreciate the help, I knew a app was about that could flash .zips without recovery, I will try it out.
Unfortunately it didnt work, didnt change any files in /system
Click to expand...
Click to collapse
The alternative approach is manually copying and pasting the zip files to the appropriate folders but I don't know what permissions you have to set for each of them besides the standard 664, so I apologize for not finding a solution, but I have a tablet that is pretty much in ter same ballpark as the MX4 so I'll monitor this thread!

Djlatino said:
The alternative approach is manually copying and pasting the zip files to the appropriate folders but I don't know what permissions you have to set for each of them besides the standard 664, so I apologize for not finding a solution, but I have a tablet that is pretty much in ter same ballpark as the MX4 so I'll monitor this thread!
Click to expand...
Click to collapse
I have tried to do that also, its working on the mx4 pro, but that has a different cpu chip.
Watch the video on this thread :http://bbs.flyme.cn/thread-240899-1-1.html
It explains how to copy/paste to the correct places.
Hopefully it works for you.

punkmonkey1984 said:
I have tried to do that also, its working on the mx4 pro, but that has a different cpu chip.
Watch the video on this thread :http://bbs.flyme.cn/thread-240899-1-1.html
It explains how to copy/paste to the correct places.
Hopefully it works for you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Check out flashfire, it seems to be more active than flashgordon.
Thanks for the link btw.

Djlatino said:
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Check out flashfire, it seems to be more active than flashgordon.
Thanks for the link btw.
Click to expand...
Click to collapse
Seems to have better support, coming from Chainfire etc, but it just results in black screen without progress.
Will keep searching for a solution tomorrow.

Ok, can get it to show installed, but after I reboot it is just resulting in bootloops.
Anyone have a solution!
{
"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"
}

punkmonkey1984 said:
Ok, can get it to show installed, but after I reboot it is just resulting in bootloops.
Anyone have a solution!
Click to expand...
Click to collapse
Same, got it installed, but boot loops for days.
Thank you based rovo for the Safe Mode

Djlatino said:
Same, got it installed, but boot loops for days.
Thank you based rovo for the Safe Mode
Click to expand...
Click to collapse
I did manage to get it installed and working without issues.
Follow the guide here: http://bbs.flyme.cn/forum.php?mod=viewthread&tid=254959&page=1&extra=#pid3301122
Files link: http://pan.baidu.com/s/1hq1pPUs
Basic chinese-> English:
1: Extracting installation charm Andrews 5.0 toolkit installation kingroot4.0 Mobile, the phone root, generally a few minutes to resolve.
2: the tmp folder, RE Manager copied to the system root directory, modify ub.sh tick all permissions.
3: Install a terminal emulator, open a terminal emulator to enter expert mode, choose Terminal Emulation, SU checkbox ticked above,
After entering sh /tmp/ub.sh carriage return (later sh space), etc. output stop after a while you can exit the terminal emulator.
4: Install xposed installer.apk, installation charm toolbox, open frame - module check Charm toolbox restart into effect.
I got it installed by wiping my data and trying on a fresh install before doing anything else, hopefully you wont have to do that.
Try removing all xposed related apps/modules before trying and rebooting/ clear catches before.
I used superSU not King user. Ignore charm-toolbox, thats a meizu flyme related module like gravity-box.
Follow the guide, then install xposed installer, mine didnt install, so i pushed in manually to /data/app with correct permissions then rebooted. I think it rebooted first time.
But a couple of times i have had to reboot by holding the power button for 10s because its gone into bootloop when activating new modules, but after it comes back on.

I got it to work another way, but my device is completely different.
What I did was install the installer, but right after I followed these instructions:
n root browser:
go to the /data/data/de.robv.android.xposed.installer/ and create folder "conf" (permissions rwxrwxrwx)
in folder "conf" create the file "jit_reset_offset" (permissions rw-r--r--)
Download Terminal Emulator, install and open it. Then:
type "su"
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset"
Reboot the tablet.
Open Xposed Installer, install framework, reboot.
Click to expand...
Click to collapse
I gave that offset a shot and it luckily worked on mine. Unfortunately, the only way of getting the "offset" code is by analyzing some lib file, which I have yet to find out how to do. That being said, you can always try 0x98 a try as it seems to work on many. The default AOSP is 0x78, and some even have it as 184.
This does, however, fix most of the issues with "unsupported" devices out there, that seems to be the solution from rovo all the time.

punkmonkey1984 said:
I did manage to get it installed and working without issues.
Follow the guide here: http://bbs.flyme.cn/forum.php?mod=viewthread&tid=254959&page=1&extra=#pid3301122
Files link: http://pan.baidu.com/s/1hq1pPUs
Basic chinese-> English:
1: Extracting installation charm Andrews 5.0 toolkit installation kingroot4.0 Mobile, the phone root, generally a few minutes to resolve.
2: the tmp folder, RE Manager copied to the system root directory, modify ub.sh tick all permissions.
3: Install a terminal emulator, open a terminal emulator to enter expert mode, choose Terminal Emulation, SU checkbox ticked above,
After entering sh /tmp/ub.sh carriage return (later sh space), etc. output stop after a while you can exit the terminal emulator.
4: Install xposed installer.apk, installation charm toolbox, open frame - module check Charm toolbox restart into effect.
I got it installed by wiping my data and trying on a fresh install before doing anything else, hopefully you wont have to do that.
Try removing all xposed related apps/modules before trying and rebooting/ clear catches before.
I used superSU not King user. Ignore charm-toolbox, thats a meizu flyme related module like gravity-box.
Follow the guide, then install xposed installer, mine didnt install, so i pushed in manually to /data/app with correct permissions then rebooted. I think it rebooted first time.
But a couple of times i have had to reboot by holding the power button for 10s because its gone into bootloop when activating new modules, but after it comes back on.
Click to expand...
Click to collapse
I have installed xposed today by a very similar way that I have made but I am not sure if xposed totally installed.
Do you think that it is really installed?
I also have tried with the method of the chinese forum and the result is the same (basicaly is the same as my procedure).
There is any module to check it is really working? As you see I dont use much xposed

iicc said:
I have installed xposed today by a very similar way that I have made but I am not sure if xposed totally installed.
View attachment 3324770
Do you think that it is really installed?
I also have tried with the method of the chinese forum and the result is the same (basicaly is the same as my procedure).
There is any module to check it is really working? As you see I dont use much xposed
Click to expand...
Click to collapse
Flyme tools still works.
Did you encounter any bootloops?
You could try this one if your having trouble (not tested myself)
http://bbs.flyme.cn/thread-258466-1-1.html

punkmonkey1984 said:
Flyme tools still works.
Did you encounter any bootloops?
You could try this one if your having trouble (not tested myself)
http://bbs.flyme.cn/thread-258466-1-1.html
Click to expand...
Click to collapse
No bootloops so far.
[emoji33] [emoji33] thats the cofface cwm, I thought it didnt worked and the project was abandoned

iicc said:
No bootloops so far.
[emoji33] [emoji33] thats the cofface cwm, I thought it didnt worked and the project was abandoned
Click to expand...
Click to collapse
I'm not sure, I think it's only temporary cwm, I think it reverts back to the stock one after a reboot.

[MODULE] Nexus Assistant

This is a Magisk module to enable the assistant on existing Nexus devices
Github Repo:
https://github.com/kudiaborm/Nexus-Assistant

How soon? I'd like to try the assistant and I was thinking of doing the build.prop modification, but now that I saw this thread maybe I'll rather wait for this module.
Edit: Sweet module. Love it, worked as expected.

Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.

flindaman said:
This is a Magisk module to enable the assistant on existing Nexus devices
Github Repo:
https://github.com/kudiaborm/Nexus-Assistant
Click to expand...
Click to collapse
Just so you're aware replacing the entire build.prop causes issues. It's best to replace the two individual lines. You can use my module as a guide.

loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
Will this be a magisk module still? Can it be undone easily?

loserskater said:
Just so you're aware replacing the entire build.prop causes issues. It's best to replace the two individual lines. You can use my module as a guide.
Click to expand...
Click to collapse
Oddly enough no matter what I tried it didn't work/run properly from the post-fs script. I'll check your module. Maybe it has something to do with file encoding

flindaman said:
Oddly enough no matter what I tried it didn't work/run properly from the post-fs script. I'll check your module. Maybe it has something to do with file encoding
Click to expand...
Click to collapse
I couldn't get his to work. I probably am doing it wrong. But now on tap still shows up.

loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
Flashed in TWRP on Nexus 6, no /cache/magisk was created and neither the properties have changed:
Code:
$ adb shell
shamu:/ $ getprop ro.product.model
Nexus 6
shamu:/ $ getprop ro.opa.eligible_device
shamu:/ $
Did it work on Nexus 6p?

loserskater said:
Make sure you're on a Google app version higher than 6.5.35.21. http://www.apkmirror.com/apk/google-inc/google-search/google-search-6-6-14-release/
Magisk Manager doesn't like cache mods so you have to flash in recovery. Make sure you wipe data for Google App after flashing.
This only sets the two build. prop variables. I didn't include any Google app apks or wipe data for Google app. You'll have to do that yourself.
Click to expand...
Click to collapse
This worked for me, thanks so much. Was wating for a way to do this in magisk
Flashed the file in twrp, rebooted, wiped all google app data, long pressed home and there it was. "ok google" command working great
My setup:
Nexus 6P
Stock NBD90X
Magisk v7
Magisk phh
Magisk V4A

Papote3 said:
This worked for me, thanks so much. Was wating for a way to do this in magisk
Flashed the file in twrp, rebooted, wiped all google app data, long pressed home and there it was. "ok google" command working great
My setup:
Nexus 6P
Stock NBD90X
Magisk v7
Magisk phh
Magisk V4A
Click to expand...
Click to collapse
Are you able to Download+Install modules through the Magisk Manager Downloads section? I'm on NBD90x with Magisk v7, Nexus 6P, Magisk phh, Magisk Manager 2, and I get an error for every module I try to install through the manager. If I could get at the zips and just flash them that would be awesome, but I can't.

shinobi26 said:
Are you able to Download+Install modules through the Magisk Manager Downloads section? I'm on NBD90x with Magisk v7, Nexus 6P, Magisk phh, Magisk Manager 2, and I get an error for every module I try to install through the manager. If I could get at the zips and just flash them that would be awesome, but I can't.
Click to expand...
Click to collapse
Yes I can download, install and reboot from the manager. But this mod needs to be flashed in recovery FYI.
Try and flash them from recovery. There's a folder where magisk manager downloads the zip files. It's in the root of the SD and I think its named magiskmanager

Papote3 said:
Yes I can download, install and reboot from the manager. But this mod needs to be flashed in recovery FYI.
Try and flash them from recovery. There's a folder where magisk manager downloads the zip files. It's in the root of the SD and I think its named magiskmanager
Click to expand...
Click to collapse
Yes, there is. Unfortunately immediately after the zips are downloaded, when the install fails, it removes the zip and I can't get at it. I've gone completely back to full stock NBD90X and installed everything, gone into Magisk Manager and am still unable to install any of the modules from there. It's so frustrating, haha.

shinobi26 said:
Yes, there is. Unfortunately immediately after the zips are downloaded, when the install fails, it removes the zip and I can't get at it. I've gone completely back to full stock NBD90X and installed everything, gone into Magisk Manager and am still unable to install any of the modules from there. It's so frustrating, haha.
Click to expand...
Click to collapse
Does magisk manager have storage permission?

loserskater said:
Does magisk manager have storage permission?
Click to expand...
Click to collapse
It does. It's the only permission in fact.

If there's any Nexus 6 (so far the only arm and not arm64 phone to get Nougat, right?) owner who have this module or any other cache-module working, please post here. I suspect something cache-module related is broken on the arm phone(s).

stangri said:
If there's any Nexus 6 (so far the only arm and not arm64 phone to get Nougat, right?) owner who have this module or any other cache-module working, please post here. I suspect something cache-module related is broken on the arm phone(s).
Click to expand...
Click to collapse
You could try my mod. Instead of replacing the whole buld.prop file it just adds the two properties
Code:
ro.product.model=Pixel
ro.opa.eligible_device=true
to it.
Edit:
Forgot to mention it's still a cache mod so let me know how it works out.
And remember you need to flash it via recovery. Magisk Manager won't install it correctly.
Edit2:
As you can see below, loserskater already posted the same thing in post 3.
So yeah ...

TAM1m said:
You could try my mod. Instead of replacing the whole buld.prop file it just adds the two properties
Code:
ro.product.model=Pixel
ro.opa.eligible_device=true
to it.
Edit:
Forgot to mention it's still a cache mod so let me know how it works out.
And remember you need to flash it via recovery. Magisk Manager won't install it correctly.
Click to expand...
Click to collapse
This is exactly like my module in post 3 of this thread.

loserskater said:
This is exactly like my module in post 3 of this thread.
Click to expand...
Click to collapse
Oh man I didn't see that.. Sorry! Didn't want to take anything from you

TAM1m said:
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
Click to expand...
Click to collapse
No worries, just merely pointing it out.

TAM1m said:
Oh man I didn't see that.. Sorry! Didn't want to take anything from you
Click to expand...
Click to collapse
Thanks for trying to help, but you probably missed this: http://forum.xda-developers.com/showpost.php?p=69088754&postcount=8 too.
Again, if anyone with Nexus 6 (or arm platform in general) got any cache modules working, please let me know.

Magisk HIDE defeated by NemID code app

Magisk v16.4 (also tried v16.0)
I've hidden the app in the HIDE list, I repackaged Magisk, force stopped NemID, cleared cache and data, and the app still spots root. I've successfully hidden apps from root before using this method, so it's just this app here that somehow goes beyond the usual. Are there any further steps I can take to hide root from the app more thoroughly?
Thanks
{
"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"
}

Launchy21 said:
Magisk v16.4 (also tried v16.0)
I've hidden the app in the HIDE list, I repackaged Magisk, force stopped NemID, cleared cache and data, and the app still spots root. I've successfully hidden apps from root before using this method, so it's just this app here that somehow goes beyond the usual. Are there any further steps I can take to hide root from the app more thoroughly?
Thanks
Click to expand...
Click to collapse
I believe that the app detects root by any of the following things :-
1. Bootloader unlocked detection
2. Custom ROM detection
3. Presence of apps that require root
4. Reading log of root being used (which is very rare, but possible)
5. Some very private code that renders Magisk useless

Tested it, and the app looks for both Magisk and the Manager. With the app on the Hide list and the Manager repackaged I can open the app without issue. It doesn't seem to "remember" root. This is on stock OxygenOS and also NitrogenOS (both on Oreo).
The app might be detecting other properties of the ROM your using (if not stock) or other known root apps on your device. Try running a logcat when the app detects "root" to maybe see what it's detecting, or simply uninstall some root apps and try again.

It works for me aswell, im using custom rom 8.1, hide the app, repackage, reboot, open app
So if that doesnt work, you might wanna try another rom as mentioned above me

It seems the app changed its way of detecting root after their upgrade on 25/6. It also worked for me before by using Magisk Hide and repack Magisk manager, but not anymore.
It is a losing battle anyway, just a matter of time. So I do not expect this method will work for good.

yeah my nemid app also stopped working a few days ago. This is not good if its not possible to hide root from an app anymore

Since there are users reporting that they can open up the app with MagiskHide active for NemID and the Manager repackaged, it's very likely that the app is detecting some other thing on your device. It could be a property of a custom ROM you're using, it could be a root app, etc... Possible solutions: try a different ROM (as stock as possible), uninstall root apps, etc.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Ok I'm running Samsung s7 stock oreo w. Root. Knox is tripped
Removed all apps needing root, installed magiskhide props config module, disabled systemless hosts.
Still no go. It worked until before latest update

mbeltoft said:
Ok I'm running Samsung s7 stock oreo w. Root. Knox is tripped
Removed all apps needing root, installed magiskhide props config module, disabled systemless hosts.
Still no go. It worked until before latest update
Click to expand...
Click to collapse
What Magisk version do you have? If not on beta v16.4, the issue might be that the app has a sub-process that previous Magisk versions can't hide automatically. Scratch that... Just went back and saw that the OP has tested it on v16.4.
Or, if you're unlucky it's checking Knox...
Does it only check for root at the start, or is it other points as well? As stated before, I can open the app just fine on both my Oneplus 3T and Nexus 6.

AFAIK it's only checking at start-up. It shows it's load screen for a few seconds ( but longer than before when it was working) and then give the error screen OP posted.
If you leave the app and reenter it it will show the main screen but jump back to the error screen whenever a button is pressed

I tested this on a pixel 2 with stock rom in this order :
All root apps installed, no magisk or root : working fine
All root apps installed, no magisk or root, custom kernel: working fine
All root apps installed, root and magisk, magisk hidden+magisk hide: not working
No root apps installed, root and magisk, magisk hidden+magisk hide: not working
No root apps installed, root and magisk, magisk manager not installed+magisk hide: working
I then tried cloning the apk without changing the name: not working
I tried cloning the app but changing the name of Magisk Manager from "Magisk Manager" to just "Manager" and then Nemid worked again.
Could it be the Nemid app is just looking to see if there's an app called Magisk Manager installed and if there is, the app failes
Unfortunately the cloned app doesn't work. Maybe we could have the "Hide magisk" function rename the app name too?
//Peter

Just tried cloning an entirely different app and renaming it "Magisk Manager" - after this the nemid app failed, so I guess that confirms that nemid just checks the name.
//Peter

Nice detective work.
By uninstall the app (not unroot) NemID works. If you use magisk 16.6 you can just reboot phone to get the manager again or just install the apk.
But if being able to change magisk managers name to something generic (like manager) or a custom name could be a great solution (I would change name to NemID). Because if nemid can defeat magiskhide, others will follow

I posted the findings in the beta thread but I think it got removed during thread cleanup. Any other way to let the developers know?

peter_dk01 said:
I posted the findings in the beta thread but I think it got removed during thread cleanup. Any other way to let the developers know?
Click to expand...
Click to collapse
It's already on the to-do list.

Didgeridoohan said:
It's already on the to-do list.
Click to expand...
Click to collapse
Perfect! Thank you ?

Didgeridoohan said:
It's already on the to-do list.
Click to expand...
Click to collapse
Unfortunately, the change is not included in the latest 5.8.1 release.

kqueenc said:
Unfortunately, the change is not included in the latest 5.8.1 release.
Click to expand...
Click to collapse
Manager v5.8.1 was simply a bug fix. Stability is prioritised over new features. You'll have to wait, and that feature will be available when it's available. Not before that...

Didgeridoohan said:
Manager v5.8.1 was simply a bug fix. Stability is prioritised over new features. You'll have to wait, and that feature will be available when it's available. Not before that...
Click to expand...
Click to collapse
Is there any other workaround to change the name of Magisk Manager App in order to bypass the check? And will there be any other consequence (like root cannot be detected by other app)?

kqueenc said:
Is there any other workaround to change the name of Magisk Manager App in order to bypass the check? And will there be any other consequence (like root cannot be detected by other app)?
Click to expand...
Click to collapse
Until there is a feature like that, you can uninstall or freeze the Manager whenever you need to use whatever app detects it.

Magisk Manager: Manager was denied Superuser rights (and buttons missing)

Please see the posted screenshot image for the problem. I just got a brand new OnePlus 8 Pro today, updated the firmware (it's current and running Android 11), unlocked the bootloader, installed my data, and rooted it. Since there is no TWRP for Android 11 for this device, I had to manually extract the current boot.img and patch it myself with Magisk Manager to root this device.
On the first boot after root, I launched Magisk Manager. The countdown timer was so fast, I did not have a chance to grant Magisk Manager root permissions. Now Magisk Manager is being denied Superuser permissions, and there are no buttons at the bottom of Magisk Manager to set Magisk Hide settings or set what apps are allowed Superuser/root.
I have googled as well as searched this forum for relevant help, and have found nothing helpful (really, I may have missed something, but I did try). How can I reset the apps allowed root permissions so that I can grant Magisk Manager the Superuser permissions it needs to function?
{
"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"
}
Any help is greatly appreciated!
I already tried force stopping Magisk Manager and clearing the storage for Magisk Manager (which did nothing to solve the problem).

https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access

Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access
Click to expand...
Click to collapse
Thank you for the reply. I found this article earlier (or a variant of it), and it does not appear to solve the issue. I don't have two different Magisk Managers installed. I just accidently denied the one Superuser access by not granting it Superuser access quickly enough.

The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.

Didgeridoohan said:
The Magisk app does not need to ask for superuser access. It is the one that grants it... In other words, one way or the other Magisk is looking for a hidden Magisk app with a package name that doesn't match the one you're using.
Try deleting /data/adb/magisk.db. It'll reset everything (including granted superuser requests, etc) and you can reinstall the app and start over.
Click to expand...
Click to collapse
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).

chriv said:
Thank you. This is no longer an issue (I have a new issue that is unrelated to this thread, so I'll search for the solution to it).
Click to expand...
Click to collapse
Just out of curiosity, did you solve it be deleting the database file?

Didgeridoohan said:
Just out of curiosity, did you solve it be deleting the database file?
Click to expand...
Click to collapse
I wish I could say, yes, but no. Long story short, I started over from a clean phone install. Unfortunately, (this part is off topic), I accidently upgraded to 11.0.4.4.IN11AA with an OTA after starting over (the version almost nobody has yet), didn't realize it, and patched a stock 11.0.2.2.IN11AA boot.img and flashed it to the boot partition. Magisk and root worked great, but WiFi and phone calls were broken. Now I'm stuck waiting to get the 11.0.4.4.IN11AA full package (Global/NA/US version of 11.0.4.4) to fix everything (by extracting the boot.img from a payload dumper).

So you mean that deleting the database file didn't work, or that you never tried it?

Sorry if I was unclear. I didn't try it. My phone was already in a state where I could not try it (and this no longer applied) before I saw this message. I am very grateful for the assistance/information.

I have the same problem. can you help me?

kas001 said:
I have the same problem. can you help me?
Click to expand...
Click to collapse
Have you already checked to see if this is the cause? https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access. It's definitely the best starting point.

Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.

SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.

aleep123 said:
Yeah, I did forgot that I have changed magisk name to "settings" and magisk is working fine right now.
Click to expand...
Click to collapse
Can you please explain?

ivanov_16 said:
Can you please explain?
Click to expand...
Click to collapse
There's a setting in the Magisk app where you can rename it with a random package name, to hide it and make the app harder to detect. This will give it a generic Android icon and give it the same "Settings" (previously it would name the repackaged app "Manager").

OK I missed the prompt to grant access to the ADB shell. Where's the settings for all the applications permission grants? So that I can untick the "deny" for ADB shell. I've changed the setting from prompt to grant, and tried again. But the toast just says Shell denied superuser access.
Thanks.
--Chris
EDIT:
OK I just installed a terminal app and nuked
/data/adb/magisk/magisk.db
which allowed me to start the permission process over.
This sure seems like a brutal approach to grant/permission management. It also requires starting the whole process from scratch.

SparJar said:
Just for anyone else finding this thread having this issue and forgetting they told Magisk to change it's APK name to stay hidden like I did. Look for a second "Settings" app on your phone. That's what Magisk changes itself to.
Click to expand...
Click to collapse
You are a superstar!! I have been tearing my hair out for acouple of days now trying to work out why i could not reinstall magisk, this was exactly the solution to the problem i was facing, therefore i give you my gratitude.

I have the same issues after updating to v24.1 how can I Access to delete the duplicate apps of Magisk. It was naming to Settings.

After the 25206
Didgeridoohan said:
So you mean that deleting the database file didn't work, or that you never tried it?
Click to expand...
Click to collapse
I on the other hand tried it. Not sure if it works or not. After the 25206 to 25207 disaster, 25208 is finally normal except it can't hide itself anymore. Any solutions there? Many thanks. F Droid file explorer/Network Signal Guru also lost super user rights. Rootchecker now says it's not properly rooted

I tried deleting /data/adb/magisk/magisk.db with Termux but can't even access it as I get "permission denied" and am still seeing SuperUser and Modules greyed out. Tried sudo, was prompted to install 'tsu' package and it failed as it appears the host no longer exists