Magisk 22101 (22.+) not detected by Manager, but SU still working on Android 6.0 Marshmallow with Samsung Note 4 SM-N910F TouchWiz, - Galaxy Note 4 Q&A, Help & Troubleshooting

- Target image: /dev/block/
- Device platform: armeabi-v7a
- Installing: 22.0 (22000)
! Unable to check signature
! Installation failed
this is the message inside of magisk manager when i try to install with recommended way. but i have root after flashing zip not showing anything else in the app not magisk hide not modules etc
ant solution?

I do not quite understand what you want, but I think I understand some of it. You want to install a new version of magic and can not do it from the magic app, it was properly understood. If it was I can help. Try using another file explorer if you need to patch for it, or download the zip file and install it from recovery.

i have tried all when flashing the latest magisk the manager doesnt recognize the version but i have root rights nor appears su hide modules etc in the manager

Im running a 6.0 Custom ROM and noticed Magisk isnt working well but does give me SU access. I you need to run an earler version of Magisk (16?) in order to run it smoothly.

Related

[Q] Lenovo K1 UMTS Base Firmware

Does anyone have the Stock Rom from the germarn UMTS model?
I have been rooting my device with the none UMTS version (US) and now can't go back. Unfortunately it is not posted in Lenovos OTA section and the versions with letter M in the name for other countrys fail to boot. Maybe some files are missing there (blob)!
The version I had before I updated and rooted it was:
K1 A301 01 01 111026 M GE.zip
I hope someone can upload it for me or get me a link.
Thank you.
You don't need the original firmware. Just flash US-02 (with nvflash). Next, take "K1_A301_02_02_111004_GE.zip" and then "K1_A301_11_11_111213_M_GE.zip". After that, you can get the latest OTA via the settings menu. This should work for the original US-02 as well as the rooted US-02.
Thanks. Working fine. Rooting again with nflash was a little complicated. But now I have the issue, that the external sd card could not be mounted, so i cant do app2sd.
Sent from my K1 using Tapatalk
Can you explain what you did exactly? It worked for me this way: flash rooted US-02-image with nvflash->turn on backdoor to keep root during OTA updates->install "K1_A301_02_02_111004_GE.zip" (move zip file to /sdcard/Download/update.zip and rebooot into recovery)->install "K1_A301_11_11_111213_M_GE.zip" (move zip file to /sdcard/Download/update.zip and rebooot into recovery)->perform OTA update via settings menu->install superuser and busybox and check if it works->reboot->turn off backdoor->reboot.
If you don't have the backdoor tools yet or a rooted US-02 image, look at this thread and download the file "K1 - PermanentRoot.7z".
I did all that.
But my root is gone after I flash K1_A301_11_11_111213_M_GE
I still got no sound after OTA to K1_A301_12_12_120109_M_GE
How to re-root?
You have no sound because the backdoor is still enabled. You have to install Superuser and Busybox (you can try to install "BusyBox Installer" and "Superuser" in Google Play). If both are working, reboot and disable the backdoor.
Superuser App installs fine but under Settings/General it shows:
SU binary vnull
If I try to update it tells me it does not find any old superuser and quits.
When I Try to install busybox it tells me it cant find superuser.
Yes I got no sound but how do I use the backdoor to install superuser?
...
Check out this post. This Rom (download K1_CWM_120109_M_GE_Rooted.zip)
should work , includes Root an CWM based on K1_A301_12_12_120109_M_GE.zip.
http://forum.xda-developers.com/showthread.php?t=1564002
Did anyone know, or could add init.d support because of ability to move app2sd?

[Z3 All variant][Locked Bootloader][Noob Friendly] How to root

MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
XPERIA ANDROID 5 LOLLIPOP EASY ROOT :​
ALL LOCKED&UNLOCKED BOOTLOADERS.
1-) Copy ALP folder in phone memory.
2-) Settings >Security > Unknown sources make it open. And Settings > Developer Options > USB debugging make it on. (If developer options exist go Settings > About phone and click Build number (7 times))
3-) Install Root.apk Allow all messages.
4-) Install Recovery.apk
5-) Install Busybox.apk
6-) Open KingRoot and click Root button.
MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
6-) Wait to complete. İf you see a chinese blue button click it. All of messages you will allow.
7-) When you see blue tick symbol or %100 its ok.
Look to the menu KingUser its in here ok. No problem don't open it.
9-) Open busybox and install it. When you see It looks like busybox installed succesfully congratulations message its ok.
10-) Open XZRecovery and click Install Recovery .
11-) Phone will be reboot and recovery will open.
12-) Install > find ALP folder and select SuperSU.zip then swipe and install it.
13-) Complete the install Wipe Cache/Dalvik and reboot the phone.
14-) You can see SuperSU in menu and check with rootchecker your root access.
15-) Everything OK. You can enjoy with your rooted Android 5 lollipop device.
16-) You can uninstall KingRoot, busybox, Xzrecovery app. (won't delete supersu or ndrutils)
PREPARED BY ALPEREN ÇUBUK.
DOWNLOAD LİNK : https://yadi.sk/d/qMsejobDgedBw
MIRROR :
https://app.box.com/s/86e7vlwfmu5z62lo95vu2kfej38uj01q
NOTE: Extract downloaded zip and copy ALP folder your phone memory.
Thanks for the comprehensive guide. For some reason step 11) Getting my D6653 into recovery is not working (Also tried ADB reboot recovery)
Any ideas?
EDIT: After updating BusyBox, and then re-installing the Recovery, it re-started and is now stuck in a bootloop..
EDIT2: The bootloop is very likely related to this (from this post: http://forum.xda-developers.com/showthread.php?t=2261606):
"@vaisakh7 found a busybox updater which seems to be compatible with XZDualRecovery: Busybox On Rails, which installs a version of busybox created by stericson, which leads me to believe his Busybox installer should also install a version which works together with XZDualRecovery.
Either case, be careful with updating busybox as there still is a possibility it will break your ability to enter recovery or even break full root, which means you might not be able to recover from the broken situation. Your best bet is the installer version, using that to break the lock on the system partition and reinstall the correct busybox."
Recommended to NOT update BusyBox
Busybox can never be installed through this process always failed and there is no other option left once busybox installation failed except to reinstall the whole firmware please add the steps to guide for busybox installation too
Does this method null the waranty?
Sent from my Xperia Z3

[Honor 8 Nougat General Info/Guides]

So I've been getting lots of different questions about how to get this and that on android 7.0 nougat so to make it easier for everyone to find ill create this thread.
1. TWRP
Is twrp available for N? If so where can I find it?
http://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947
2. ROOT
Oh cool now I have twrp. So how can I root?
Download phh r275 version and flash
Download and install Material phh apk: Release post
Now you should be good to go. If any issues feel free to ask here or in phh official thread.
3. BUSYBOX
User friendly zip flash this and the below steps isn't needed!
Flashable zip (1.25.1) : https://mega.nz/#!zlRm3S4B!9rAtfi0wI8oFu6xjJITgF0dRwV21UPsxvZQZzMo6VXk
This one is a bit tricky. If you run root. But
Download jrummy's busybox on Gplay.
Select installation folder to /system/xbin or if u don't want to touch system folder use /sbin if available. U can replace jrummy''s busybox with stericsson version if you like it better. But you must have installed jrummys version first if you're booted into android. Else stericsson busybox might have issues installing. Or u can use zips which contains busybox Google busybox flashable.
4. VIPER
More user friendly if using this zip the below steps should only need se Linux mode changer!
Flashable zip: https://mega.nz/#!f8wlzIrB!vVCAv-xqWB8lOrcQTgIyFL0WS7MFsE9iFb08E1YKV2Y
Is quite a mess to get working. You need se Linux mode set to permissive. Flash guitarheroes version of v4a (2.5.0.5) once flashed you need to replace the audio effects in /vendor/etc/audio_effects else you'll get I/O driver installation failed. Copy the .so files to /system/lib and /system/lib64 and set correct permission. If you have wrong busybox message. Try different versions of busybox but I use latest from stericsson and it works great. Hope u get it working.
Oh and don't forget to allow sd storage access or you'll get driver I/O error as well. And se Linux changed to permissive use se Linux mode changer for it. It works great with phh!
5. MAGISK
As it seems to be now. Magisk won't work due to loop issues on boot. And mount seems to have losetup fail 1 on mounting a .img while booted.
6. Xposed
Not yet available. Be patient rovo needs time we can wait for him
7. comes soon.
More stuff.
Sent from my FRD-L09 using Tapatalk
Updated busybox and v4a zip is found here https://mega.nz/#F!HlpzlaZL!wGNoJinVPZL0YiBcdbLlKA
V4a should be more easy installed shouldn't give you driver I/O error anymore.
Sent from my FRD-L09 using Tapatalk
Updated op with links.
V4a zip more user friendly.
Same goes for busybox. No more struggle
Sent from my FRD-L09 using Tapatalk
Any updates on xposed?

Need help with J5 Pro [2017] Permissions

So i installed twrp with odin (i have some problems with twrp too but idk how i installed the magisk to be honest) , as i said i installed magisk manager. Now here comes the problems :
1. Can't install Magisk Modules (think is because of system rw permissions)
2. Can't use Freedom app , it shows an error Please allow system write permissions or something like that.
Please help me guys..
I remember that on my old phone on the TWRP menu i had a fix permissions button , but here i don't have it.
The errors in the TWRP when i try to install a zip file (ex: magisk , supersu) are something like that:
E: ERROR GRAB (or RELEASE or RETRY) : (and 2 numbers ex: ) 500 ,1000
Can anyone help me?
Thanks.

Magisk 25.1 for Fire TV

As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Sus_i said:
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Click to expand...
Click to collapse
It works on Android 9, but on Mantis (4K with 7.1.2) dialog worked with Magisk 20.4 (old manager) and broken (don't have any focus so user can't press any button in it) with any Magisk 21+ and new Manager GUI
mamcho said:
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Click to expand...
Click to collapse
hm, it's apk from studio, tesed it on TWRP from Fire TV 4K and it installs fine. Try to disable digest check in TWRP options.
Im on sloane and disabling digets check doesnt change anything. I ve read that 24.3 is problematic for sloane. 23.0 works tho
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
BTW: guys on magisk github page asnwer really bad to your suggestion, no reason to do that
The manager UI is not tv-friendly so it's really easy to press update by mistake. It was the 1st thing I though when I saw it after installation...
Noisemaker00 said:
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
Click to expand...
Click to collapse
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
tsynik said:
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
Click to expand...
Click to collapse
So the steps are:
uninstall current magisk-manager version
download and rename your .apk to .zip
reboot to twrp and flash the zip
reboot the system
is it correct?
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
mamcho said:
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
Click to expand...
Click to collapse
Yes, probably it's some kind of bug in Magisk. When hiding, Magisk replaced with stub app, which download full apk from https://github.com/tsynik/Magisk/releases, but failing to load it's classes and initialize app context.
Fixed with v25.1.FTV release
tsynik said:
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Click to expand...
Click to collapse
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
What I did was to rename .apk to .zip, flash with twrp. manager was not to be found on apps. then I manually installed the .apk and it appeared on apps.
yakovperelman69 said:
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
Click to expand...
Click to collapse
I am having the same issue
BTW to uninstall rename the apk to uninstall.zip then flash it in twrp
I have a tank (2nd gen stick) with latest firmware (5.2.9.5 at time of writing)
Now that Magisk v26 has dropped support for android 5, it would be wise to release a final version for old fire sticks.
Anyway the UI does not start at all, both on your fork and on the original v25.2 . (and, both of them do not remember superuser permissions - they get asked every time)
I just tried to flash Magisk v26.1 via TWRP. FireOS6 (mantis - FTV4K)
First fresh Kernel followed by Magisk v26.1.zip.
All seams to work but I noticed that the repacking step went unusual fast!
After rebooting and updating Magisk app to v26.1 it seams to work.
But now I get after a fresh start/reboot a warning message in Magisk app that an reflash is necessary!
I now went back to 25.2 (again Kernel + Magisk.zip) and all is good again.
I do not know what happens here or if something went wrong or if 26.1 is not fully compatibe to FireOS6 (Android 7)...
Anyway - Just wanted to let you all know.

Categories

Resources