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.
Related
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.
I know you guys have waited FOREVER for somebody to pick this project up.... I have, and today I preset to you...ROOT
WARNNG: THIS DOES USE A CUSTOM KERNEL
Steps:
Unlock bootloader using this TUTORIAL:
http://forum.xda-developers.com/desire-510/help/qa-bootloader-unlock-htc-desire-510-t2911491
DO NOT FLASH RECOVERY FROM THAT THREAD
Grab boot.img from here:
http://goo.gl/AlaZpI
Old Versions:
http://goo.gl/dzQ3Wi
Load boot.img into fastboot folder
run this command:
"fastboot flash boot HTC-Desire-510-64bit-Root.img"
Install SuperSU from Play Store. Select cancel everytime it asks to update. It WON'T work
VigiDroid said:
Okay first things first let's get a couple things straight. SuperSU is the APPLICATION that allows for other applications to gain root access. When you first run SuperSU it will complain that the SU BINARIES are out of date. This is not important. It claims that you need a custom recovery (typically TWRP or CWM) to install the BINARIES, or you can try install it without it. This does not work, but it doesn't matter, since the out dated BINARIES still function correctly.
It is important to identify the difference between those two to avoid confusion though. SuperSU is the APPLICATION that allows root, and SU is the BINARIES which allow SuperSU to have root access.
I had trouble at first, but after a couple of initial reboots, SuperSU functioned correctly and granted root applications access. Once you have rebooted a few times, try download "root access checker" and run it to see if it works.
Click to expand...
Click to collapse
Good job rbheromax
thanks!
Thank you soo much
---------- Post added at 05:59 PM ---------- Previous post was at 05:32 PM ----------
I have started my phone succesfully with this kernel,but no root access (i have installed supersu alredy)
(I dont have recovery on my phone)
Sorry for my english.
I'm not a programmer or expert android but by unpacking the file boot.img, there are necessary files to root
{
"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"
}
I only checked to make sure that root could be accessed by shell. I'll upload another version with it having universal access
Sent from my XT1028 using XDA Free mobile app
rbheromax said:
I only checked to make sure that root could be accessed by shell. I'll upload another version with it having universal access
Sent from my XT1028 using XDA Free mobile app
Click to expand...
Click to collapse
Alright,thanks.
this will install su to /system as well as remove write protection
http://tempsend.com/33CE45F61D
rbheromax said:
this will install su to /system as well as remove write protection
http://tempsend.com/33CE45F61D
Click to expand...
Click to collapse
You gave me this file in private message,i have tried it and not worked,i had same problem
Edit: Its say there is no SU Binaries installed and SuperSu not installable......(i use SuperSU Free from google play)
Can anyone post a video which shows the process (and success!) of root the HTC Desire 510 64bit (EU)
Thanks
GianniDarkos said:
Can anyone post a video which shows the process (and success!) of root the HTC Desire 510 64bit (EU)
Thanks
Click to expand...
Click to collapse
Fix for root is coming soon,please be patient.
Ops ok, sorry
(I did not understand, I can not read english well)
http://goo.gl/AlaZpI
link updated in OP
it IS rooted, but you cannot update in-app using SuperSU. for some unknown reason, it wont work
use any other root managing app and you should be ok. try using koush's superuser app
Change Screen Size
Guys,
If you wanna be normaly screen size (not original sh.. screen sizes) than download this apk to your phone:
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer&hl=hu
NOMone Resolution Changer (its free)
Open the app and you see
"Width" "Height" "DPI"
Change Width to 720
Change Height to 1280
Change DPI to 312
and click on apply
Or second way:
Open the app
Click on "Select device template"
and choose Motorola Moto X or Htc One X
Click on apply and you done
If you dont like this sizes,dont worry,apk will restore stock sizes after 10 sec and after 1 minutes too.
Good Luck to all.
rbheromax said:
http://goo.gl/AlaZpI
link updated in OP
it IS rooted, but you cannot update in-app using SuperSU. for some unknown reason, it wont work
use any other root managing app and you should be ok. try using koush's superuser app
Click to expand...
Click to collapse
Have you got a link please. I can't seem to find that one in particular
Burtrum57 said:
Have you got a link please. I can't seem to find that one in particular
Click to expand...
Click to collapse
Check the link in the OP? Hit the big blue download button on it and follow the instructions from the OP. In case you missed it, you have to use FASTBOOT to FLASH the KERNEL. So in other words, use this command: fastboot flash boot HTC-Desire-510-64-Bit-Root.img
VigiDroid said:
Check the link in the OP? Hit the big blue download button on it and follow the instructions from the OP. In case you missed it, you have to use FASTBOOT to FLASH the KERNEL. So in other words, use this command: fastboot flash boot HTC-Desire-510-64-Bit-Root.img
Click to expand...
Click to collapse
I've downloaded the kernal, fastboot flashed it and rebooted the phone and all is going well. Your correct supersu won't install without twrp or cwm. I have busybox installed and it is ok but a couple other apps complain that things aren't right.
Burtrum57 said:
I've downloaded the kernal, fastboot flashed it and rebooted the phone and all is going well. Your correct supersu won't install without twrp or cwm. I have busybox installed and it is ok but a couple other apps complain that things aren't right.
Click to expand...
Click to collapse
Okay first things first let's get a couple things straight. SuperSU is the APPLICATION that allows for other applications to gain root access. When you first run SuperSU it will complain that the SU BINARIES are out of date. This is not important. It claims that you need a custom recovery (typically TWRP or CWM) to install the BINARIES, or you can try install it without it. This does not work, but it doesn't matter, since the out dated BINARIES still function correctly.
It is important to identify the difference between those two to avoid confusion though. SuperSU is the APPLICATION that allows root, and SU is the BINARIES which allow SuperSU to have root access.
I had trouble at first, but after a couple of initial reboots, SuperSU functioned correctly and granted root applications access. Once you have rebooted a few times, try download "root access checker" and run it to see if it works.
You are right. All seems to be correct, I have root access, can copy, delete and move files with no problems. A couple apps do complain but if ignore them all still works well. Thank you so much. It may be a small step but it is a huge leap for what can now be done with this phone
/system/build.prop for Europe
Could someone on a European 510 please post their /system/build.prop file?
adb shell
su
cat /system/build.prop
...and since you're at it, could you post a stock (or not) TWRP backup? I know I am asking a lot, but after all I did help (in a very small way) @rbheromax in achieving root for you guys.
Thanks very much!
Instead of including the third party APK files in the magisk modules/repo, this module, developed by @loserskater and me, systemizes user-installed apps systemlessly thru magisk. Another benefit of systemizing the user-installed apps is that if you uninstall magisk, your settings for the apps will be retained. If you originally install any of the apps above thru an app-specific magisk module (like Pixel Launcher magisk module for example), then when magisk is uninstalled or disabled, app settings will be gone.
If you're on Oreo ROM, you will need this add-on developed by @yochananmarqos: https://forum.xda-developers.com/apps/magisk/module-privileged-permission-whitelist-t3670646
This module requires installation from Magisk Manager, not recovery.
This module might lead to your device stuck on logo or booting to recovery, I gather it might be a kernel issue -- the closer you're to stock firmware/kernel the more likely it is to work. If it fails, try the "Terminal App Systemizer" instead.
Important links:
README
AppSystemizer commits
Companion app commits
NOW IN OFFICIAL MAGISK REPO!
11.0.6: This is the last "classic/simple" version I could get from github, (11.0.6) which might fail on the larger APKs but doesn't include magisk partition resizing code which might cause problems. It also does NOT include a companion app.
12.0.5: This is the latest "stable" version with the companion app. Based on pre-"magisk 13" template (version 3), but seems to work with magisk 13.
14.0.0: This is the 12.0.5 version migrated to 1400 template (released with magisk 14). Not tested by me, so use at your own risk (but please post back wherever it does/does not work).
The source code (with history) is available here if anyone wants to continue development: https://github.com/stangri/AppSystemizer
So since the new apk for Pixel Launcher is available and it has a different signature than previously leaked apk files, here's the list of steps you need to take to replace your Pixel Launcher if used with this module:
1. Go to Magisk Manager and delete (or disable) the App Systemizer module.
2. Reboot.
3. After step 2 your Pixel Launcher should no longer be a system app and you should be able to uninstall old Pixel Launcher -- do so (with your favourite root uninstall app or thru System Settings -> Apps -> Pixel Launcher -> Uninstall).
4. Install the new Pixel Launcher.
5. Add again (or reactivate) the App Systemizer module.
6. Reboot TWICE.
7. The new Pixel Launcher should be active and working as a system app now.
ForceDoze
Playe said:
ForceDoze
Click to expand...
Click to collapse
Please try the attached ZIP after you have installed the app from the play store and remember to reboot twice. Post back if it works and why do you need it to be a system app.
Does this essentially make it a system app without it actually being in the system, or am I not understanding this correctly?
Sent from my Nexus 6 using XDA-Developers mobile app
pnwsr6 said:
Does this essentially make it a system app without it actually being in the system?
Click to expand...
Click to collapse
Precisely, it makes the user-installed app a system app without actually modifying the /system partition.
Can it support Cerberus anti-theft?
Sent from my Nexus 6 using XDA-Developers mobile app
pnwsr6 said:
Can it support Cerberus anti-theft?
Click to expand...
Click to collapse
It sure can, I'm not sure if the "magiskized" Cerberus would survive data reset tho. Can you try it out please? Just make sure to reboot TWICE after installing the attached module before the big reset.
OK. It will be this weekend before I can get to it. Doing all the research and downloading ahead of time. Figured I would try some of this systemless stuff out before upgrading to far. Not upgrading to N yet but is this systemmless stuff seem to be working OK with N?
Sent from my Nexus 6 using XDA-Developers mobile app
pnwsr6 said:
OK. It will be this weekend before I can get to it. Doing all the research and downloading ahead of time. Figured I would try some of this systemless stuff out before upgrading to far. Not upgrading to N yet but is this systemmless stuff seem to be working OK with N?
Click to expand...
Click to collapse
Smart move. Yeah, no major issues on Nexus 6 and released Nougat. DP5 was draining my battery, but that seems to have been fixed in the release build. There seems to be a problem with magisk CACHE modules (they don't install on Nexus 6) but these are far and few between.
BTW, OTAs which affect the boot partition will kill magiskized Cerberus until you reflash magisk.
stangri said:
Smart move. Yeah, no major issues on Nexus 6 and released Nougat. DP5 was draining my battery, but that seems to have been fixed in the release build. There seems to be a problem with magisk CACHE modules (they don't install on Nexus 6) but these are far and few between.
BTW, OTAs which affect the boot partition will kill magiskized Cerberus until you reflash magisk.
Click to expand...
Click to collapse
Should this make Cerberus show up as a system app in something like Titanium backup? I can't get Cerberus to turn on gps like it would if it was installed as a system app. Shouldn't this allow it to behave like a system app or am I wishing for to much?
FYI
I had Cerberus installed first
Ran the zip file in Magisk
rebooted after install
rebooted again
logged into my Cerberus Dashboard and tried to track my phone and it will not turn on my gps like it will if installed into the system
If this is a limitation that can't be avoided I understand. If I did something wrong or can try something else let me know. Also I did this on my nexus 6 running N. Supersu seems to work and Adaway is installed and seems to be working so far. Latest twrp is also installed, everything is systemless so far. Thanks for your time
pnwsr6 said:
Should this make Cerberus show up as a system app in something like Titanium backup? I can't get Cerberus to turn on gps like it would if it was installed as a system app. Shouldn't this allow it to behave like a system app or am I wishing for to much?
FYI
I had Cerberus installed first
Ran the zip file in Magisk
rebooted after install
rebooted again
logged into my Cerberus Dashboard and tried to track my phone and it will not turn on my gps like it will if installed into the system
If this is a limitation that can't be avoided I understand. If I did something wrong or can try something else let me know. Also I did this on my nexus 6 running N. Supersu seems to work and Adaway is installed and seems to be working so far. Latest twrp is also installed, everything is systemless so far. Thanks for your time
Click to expand...
Click to collapse
If you have a file manager which can browse system partition, can you verify that there's a folder /system/priv-app/CerberusAntiTheft and its permissions are the same as the other folders in /system/priv-app? If it's there and still Cerberus doesn't behave like a proper system app then I don't know what's wrong.
PS. I believe installing twrp prevents OTAs from being installed so kinda contradicts the whole systemless concept. I only boot twrp thru fastboot when needed (usually just once to install magisk/phh root).
stangri said:
If you have a file manager which can browse system partition, can you verify that there's a folder /system/priv-app/CerberusAntiTheft and its permissions are the same as the other folders in /system/priv-app? If it's there and still Cerberus doesn't behave like a proper system app then I don't know what's wrong.
PS. I believe installing twrp prevents OTAs from being installed so kinda contradicts the whole systemless concept. I only boot twrp thru fastboot when needed (usually just once to install magisk/phh root).
Click to expand...
Click to collapse
Do not see it.
Sent from my Nexus 6 using XDA-Developers mobile app
pnwsr6 said:
Do not see it.
Click to expand...
Click to collapse
That's weird, but now we found the reason Cerberus is not working as expected.
Can you please check if the following exist:
/magisk/AppSystemizer/system/priv-app/CerberusAntiTheft
/data/app/com.lsdroid.cerberus* (could be -1, -2, etc).
If there's no /data/app/com.lsdroid.cerberus* -- my module couldn't find the installed Cerberus. Can you find out what canonical package ID did they use then?
stangri said:
That's weird, but now we found the reason Cerberus is not working as expected.
Can you please check if the following exist:
/magisk/AppSystemizer/system/priv-app/CerberusAntiTheft
/data/app/com.lsdroid.cerberus* (could be -1, -2, etc).
If there's no /data/app/com.lsdroid.cerberus* -- my module couldn't find the installed Cerberus. Can you find out what canonical package ID did they use then?
Click to expand...
Click to collapse
So I found /magisk/AppSystemizer but no more folders after that. So /system/priv-app/CerberusAntiTheft is missing.
/data/app/com.Isdroid.cerberus-1 directory exists and has the lib and oat directories plus the base.a pk in it. Forgive my lack of knowledge on this but how do I find the canonical package ID?
Sent from my Nexus 6 using XDA-Developers mobile app
Ok, I sincerely hope you just grabbed the attachment from the first post (which I posted before I added Cerberus support) and not from my reply to you down in the thread. Was the ZIP file you installed named AppSystemizer.zip or AppSystemizer-Cerberus.zip?
I still don't want to update the original attachment, so could you please add the ZIP attached to this reply to magisk and then reboot twice.
PS. If you're reading this on mobile, I don't know how the attachments show up for you, but you need the most recent AppSystemizer-Cerberus.zip file from this thread.
OK, so I deleted the old zip, it was AppSystemizer-Cerberus.zip, and removed the module. Rebooted and verified that it was removed from the magisk directory, rebooted one more time, then installed the zip you just posted for me. Rebooted twice. Went through and looked for the directories you had me looking for earlier, and they are still not there. Let me know what else I can do.
Sent from my Nexus 6 using XDA-Developers mobile app
pnwsr6 said:
OK, so I deleted the old zip, it was AppSystemizer-Cerberus.zip, and removed the module. Rebooted and verified that it was removed from the magisk directory, rebooted one more time, then installed the zip you just posted for me. Rebooted twice. Went through and looked for the directories you had me looking for earlier, and they are still not there. Let me know what else I can do.
Click to expand...
Click to collapse
Just installed Cerberus app and got it converted to systemless with the module.
Can you PM me (or post here) the magisk log?
PS. Does magisk have root access?
stangri said:
Just installed Cerberus app and got it converted to systemless with the module.
Can you PM me (or post here) the magisk log?
PS. Does magisk have root access?
Click to expand...
Click to collapse
{
"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 has root access. Or at least I get the toast notification saying it was granted and it shows up in the SuperSU logs. I'm sure I have done something wrong, or something didn't install correctly. Just not sure what.
Sent from my Nexus 6 using XDA-Developers mobile app
pnwsr6 said:
I'm sure I have done something wrong, or something didn't install correctly. Just not sure what.
Click to expand...
Click to collapse
I'm sure it's just MM vs N difference and nothing you didn't do. Thanks for sticking by. Can you please try replacing the module with the attached AppSystemizer-debug.zip, rebooting and posting/PMing the log. This version should print stuff to the magisk log file helping me figure out what's going on.
PS. No need to uninstall existing module, just add this ZIP over the old one.
Hello Fellows,
here is a little script, rootAVD, I wrote to root Android Studio Virtual Devices with Magisk.
I hope this might come in handy.
Cheers
NewBit
Please check out the README.md for "up to date" information.
Requesting for Help!
Please provide the following information If you are asking for support:
Host System
Android Studio Version
AVD Version
Magisk Version
Terminal input & output
Example Templates:
Host System:
sw_vers
ProductName: Mac OS X
ProductVersion: 10.15.7
Android Studio Version: 4.1.3
AVD Version: Google APIs Intel x86 Atom_64 System Image (revision: 2)
Magisk Version: Stable 22.1
Before you ask, please answer your self the following questions:
Did I read AND understood the README.md ?
Is my question as detailed and simple as possible couched ?
Also, please include my Username in your Salutation to make sure I will get notice of it.
I love to help, but asking all the time, where to pick you up, just increases the time period to get
your issues fixed.
Download the latest Version:
Direct: https://github.com/newbit1/rootAVD/archive/refs/heads/master.zip
Git: git clone https://github.com/newbit1/rootAVD.git
Use Case Examples
on MacOS
{
"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"
}
on Windows
on Linux
Fake Boot.img on MacOS
hi,i am new to android studio.
I just try to use your script, it's works .thank you for share it!
wangofjian said:
hi,i am new to android studio.
I just try to use your script, it's works .thank you for share it!
Click to expand...
Click to collapse
hi, I'am glade it works for you and grateful for your feedback.
Do you mind telling me on which system and AVD you let the script run?
newbit said:
hi, I'am glade it works for you and grateful for your feedback.
Do you mind telling me on which system and AVD you let the script run?
Click to expand...
Click to collapse
My work System:
OS: MacOS Catalina 10.15.6
Android Studio 4.0.1
AVD： Pixel 2 API 30 Android 10.0+ x86_64
I restart AVD into safemode, then exec
./rootAVD.sh ~/Library/Android/sdk/system-images/android-30/google_apis_playstore/x86_64/ramdisk.img
restart and follow the magisk to fix problem.
My work System:
OS: Windows 10
Android Studio 4.0.1
AVD： Pixel 2 API 29 Android 10.0+ x86_64
BUT
basicintegrity: False
ctsProfile: False
And i cant install lot of Apps.
But root look like the Picture above me
Hylianer said:
My work System:
OS: Windows 10
Android Studio 4.0.1
AVD： Pixel 2 API 29 Android 10.0+ x86_64
BUT
basicintegrity: False
ctsProfile: False
Click to expand...
Click to collapse
Nice, thanks for your feedback.
I've never tried to get pass through the SafetyNet Check.
But If you want to go further, you can try to change your devices fingerprint with MagiskHidePropsConf from @Didgeridoohan.
So you could pass basicintegrety, and for ctsprofile you can try Universal SafetyNet Fix from @kdrag0n
Both modules are just awesome and I have them both on my real phone for the same purpose.
Hylianer said:
And i cant install lot of Apps.
Click to expand...
Click to collapse
What do you mean by that? If you can't drag and drop the apk to Emulators Display to install it, there is something wrong
with your ADB connection. I had this quite a lot, but booting the AVD up over the SDK fixed it mostly for me.
newbit said:
Nice, thanks for your feedback.
I've never tried to get pass through the SafetyNet Check.
But If you want to go further, you can try to change your devices fingerprint with MagiskHidePropsConf from @Didgeridoohan.
So you could pass basicintegrety, and for ctsprofile you can try Universal SafetyNet Fix from @kdrag0n
Both modules are just awesome and I have them both on my real phone for the same purpose.
What do you mean by that? If you can't drag and drop the apk to Emulators Display to install it, there is something wrong
with your ADB connection. I had this quite a lot, but booting the AVD up over the SDK fixed it mostly for me.
Click to expand...
Click to collapse
THX , i will test it.
I test to install Magisk and spoof with Pokemon Go
Magisk install - Check
Smalipatcher install - Check
Pokemon Go install - not check (cant install)
Joystick install - not check (cant install)
But i will test more first
Both Zips cant installed by Emulator
it come a Error = Unsupport CPU.
I think it dont work to make it ready for Fake GPS^^
Hylianer said:
Both Zips cant installed by Emulator
it come a Error = Unsupport CPU.
I think it dont work to make it ready for Fake GPS^^
Click to expand...
Click to collapse
I could install the MagiskHidePropsConf over the Magisk Manager and changed the fingerprint, but it didn't change anything on the
safetynet checks. The other zip didn't install yes.
Maybe SafetyNet Check v1.0.3: The Best SafetyNet Checker For VMOS is worth a shot?
newbit said:
I could install the MagiskHidePropsConf over the Magisk Manager and changed the fingerprint, but it didn't change anything on the
safetynet checks. The other zip didn't install yes.
Maybe SafetyNet Check v1.0.3: The Best SafetyNet Checker For VMOS is worth a shot?
Click to expand...
Click to collapse
Umm OK but how does a safetynet Checker help in this situation??
newbit said:
now it works with Android 11 (R), Android 10 (Q)
and Android 7 (Nougat) with all the Google Play Store API Versions
Click to expand...
Click to collapse
Hi @newbit Is it going to work on API-28? I tried on google_api and google_play images - no errors, evrything is fine during the process but after reboot root is not installed in magisk manager.
baribalbear said:
Hi @newbit Is it going to work on API-28? I tried on google_api and google_play images - no errors, evrything is fine during the process but after reboot root is not installed in magisk manager.
Click to expand...
Click to collapse
API 28 is PIE, Google changed the ramdisk location to SAR Partition.
The Qemu Engine does have a ramdisk.img, but it is not used by it!!
Therefor the rootAVD script succeeded, but Qemu is ignoring the ramdisk.img anyway. -> No Root
You could try to force qemu using it by passing it as boot parameter, I never tried this.
rushi12565 said:
Umm OK but how does a safetynet Checker help in this situation??
Click to expand...
Click to collapse
I thought this app is running the apps in question independent of the safety state, that is what I figured. Perhaps I am wrong, then ignore it.
newbit said:
You could try to force qemu using it by passing it as boot parameter, I never tried this.
Click to expand...
Click to collapse
I tried to boot emulator with -ramdisk parameter and pointed to patched file - no luck, it boots but magisc manager don't see root.
What is changed in Android 10 comparing to Android 9 that it started to work with the patching script?
baribalbear said:
I tried to boot emulator with -ramdisk parameter and pointed to patched file - no luck, it boots but magisc manager don't see root.
What is changed in Android 10 comparing to Android 9 that it started to work with the patching script?
Click to expand...
Click to collapse
It seems that since Android 10, qemu is using the ramdisk.img file again.
hello i am new to this, after downloading the zip file what do i have to do? i was trying to open the .bat but it closes immediately and does not do the rooting process
edit: I ran the script but it doesn't work does anyone know what I'm doing wrong, I tried it on both android 11 and 12
QuilLeeR said:
hello i am new to this, after downloading the zip file what do i have to do? i was trying to open the .bat but it closes immediately and does not do the rooting process
edit: I ran the script but it doesn't work does anyone know what I'm doing wrong, I tried it on both android 11 and 12
Click to expand...
Click to collapse
Hey @QuilLeeR,
it is possible that you didn't meet all the preconditions for rootAVD. So, first things first:
Have the AVD running
Have a command prompt open
make sure if you run adb shell it will connect to the running AVD
If you have all above checked, run rootAVD.bat with appropriate argument.
For Android 11 (R):
Code:
rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-30\google_apis_playstore\x86_64\ramdisk.img
For Android 12 (S) rev 1 and rev 2:
Code:
rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-S\google_apis_playstore\x86_64\ramdisk.img
On Android 12 (S), you have to run the script a second time, after the shutdown and restart!
The Magisk App doesn't find its Deamon running, and shows no root. - But you can grant root if you request it!
adb shell
su
Hence, it doesn't trigger the additional setup. Hence, you need to run the script twice.
Since Android 12 (S) rev 2, the Magisk Daemon is not running when the AVD is booted.
To solve this, you need to install a Canary Version. Which you can now choose during the installation process.
Cheers
NewBit
newbit said:
Hey @QuilLeeR,
it is possible that you didn't meet all the preconditions for rootAVD. So, first things first:
Have the AVD running
Have a command prompt open
make sure if you run adb shell it will connect to the running AVD
If you have all above checked, run rootAVD.bat with appropriate argument.
For Android 11 (R):
Code:
rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-30\google_apis_playstore\x86_64\ramdisk.img
For Android 12 (S) rev 1 and rev 2:
Code:
rootAVD.bat %LOCALAPPDATA%\Android\Sdk\system-images\android-S\google_apis_playstore\x86_64\ramdisk.img
On Android 12 (S), you have to run the script a second time, after the shutdown and restart!
The Magisk App doesn't find its Deamon running, and shows no root. - But you can grant root if you request it!
adb shell
su
Hence, it doesn't trigger the additional setup. Hence, you need to run the script twice.
Since Android 12 (S) rev 2, the Magisk Daemon is not running when the AVD is booted.
To solve this, you need to install a Canary Version. Which you can now choose during the installation process.
Cheers
NewBit
Click to expand...
Click to collapse
hello, now it works perfect in android 12, I think I was restarting it wrong, if I understand correctly I had to shut down, restart "android studio" and enter again to start rootAVD.bat for the second time. thank you very much for your help
QuilLeeR said:
hello, now it works perfect in android 12, I think I was restarting it wrong, if I understand correctly I had to shut down, restart "android studio" and enter again to start rootAVD.bat for the second time. thank you very much for your help
Click to expand...
Click to collapse
Well, you don't have to restart the entire Studio, just the AVD. And yes, shutdown and start is mandatory, only rebooting
doesn't pick up the patched ramdisk.img
I am glade it worked eventually.
Just for improvement purposes.
Did I hint it not well enough? What was missing?
Or was it just a misreading/misunderstanding on your side?
I would like to keep the Notes for the script as clear as possible.
Also, there is always some space to the top left.
Cheers
NewBit
newbit said:
Well, you don't have to restart the entire Studio, just the AVD. And yes, shutdown and start is mandatory, only rebooting
doesn't pick up the patched ramdisk.img
I am glade it worked eventually.
Just for improvement purposes.
Did I hint it not well enough? What was missing?
Or was it just a misreading/misunderstanding on your side?
I would like to keep the Notes for the script as clear as possible.
Also, there is always some space to the top left.
Cheers
NewBit
Click to expand...
Click to collapse
you explained it correctly when I consulted you because the steps you gave me were not included from the beginning and maybe for someone who does not understand a lot, they are lost like me but I hope that with the answer to my question someone else can understand the process and I think it was my mistake, maybe I was writing something wrong, maybe I misspelled the ramdisk path
QuilLeeR said:
you explained it correctly when I consulted you because the steps you gave me were not included from the beginning and maybe for someone who does not understand a lot, they are lost like me but I hope that with the answer to my question someone else can understand the process and I think it was my mistake, maybe I was writing something wrong, maybe I misspelled the ramdisk path
Click to expand...
Click to collapse
Ok, thanks for your feedback. I've updated the README.md accordingly.
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