I've rooted my fire HD 10 (2017). I've installed TWRP and a stock amazon rom (with Magick install, OTA) from here. I installed gapps etc. Its been working great, but I've not been able to get netflix to work becuase of SafetyNet. So I installed a Safetynet bypass module using the MagickManager.
It seemed to install fine. Asked for a reboot and now is stuck on the silver Amazon logo. I booted into TWRP and rebooted, because that seemed to solve a boot problem I had before when I was installing everything. But no joy.
I'm not sure what I can do with TWRP to diagnose the problem. Any pointers on what I can do to diagnose the issue? Is it a partition issue? I'm fairly handy with linux and familiar with computer boot processes, but this is my fire android tablet so I'm not sure what to check. Seem like a bootloader issue?
I use netflix on mine without passing safetyNet. I have used SafetyNet patch and didn't have an issue. I am however on a custom rom. But regardless you can uninstall magisk, reboot then install it again. I suspect your issues are with the stock rom.... (i also download the netflix app from netflix - see link below)
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
There is also MM for recovery mode that you can disable modules but i couldnt find anything for mm 20.0+...
[2019.4.4] Magisk Manager for Recovery Mode (mm)
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
Netflix - https://help.netflix.com/en/node/57688
Worked a treat. The thread you linked to on the recovery for Magick had some info on deleting installed modules using TWRP.
It started fine after that.
I messed around with the Netflix problem and I found turning off F.lux actually solved the video issue I was having. Weird.
Related
Magisk worked fine on the Android P PP2 beta. Just upgraded to the new PP3 and Magisk 16.4 doesn't seem to work. It flashes fine in TWRP, but Magisk Manager says it's not installed. Just want to check if others are experiencing the same before I assume it's just me and start troubleshooting.
I'm running a Pixel XL.
Same in my pixel 2 XL
I tried patching the boot.img and I got an error
I flashed 16.4 on my Pixel with PP3 and it installed fine. Root seems to work as expected, but modules dont install.
Having the s ame issue. Can't unpack and patch boot.img.
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
SirLoinOfBeef said:
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
Click to expand...
Click to collapse
I flashed 16.4 and for some reason worked... but only couple of minutes then suddenly root dissapeared :/
For me works with no problems.
I disabled all modules (just to avoid problems), dirty flashed dp3 over dp2, removed lockscreen password (again, just to avoid possible problems with twrp).
Booted twrp img, then in recovery:
- flashed latest twrp.zip
- rebooted recovery
- I flashed Flash Kernel just because I like it
- Straight after magisk 16.4
- rebooted.
Then I re-enabled all modules and set the password back. Super smooth and zero problems, root survives every reboot, no crashes or freezes of any kind. Also if I download modules they all works.
Still can't get it installed. I am trying to patch the boot.img file via Magisk Manager.
I get:
Code:
- Device platform: arm64-v8a
- Extracting files Failed!
! Installation failed
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
djuniah said:
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
Click to expand...
Click to collapse
I assume you installed through TWRP?
joderme said:
I assume you installed through TWRP?
Click to expand...
Click to collapse
Yes, i flashed through TWRP. I basically have done the same thing TENN3R mentioned above minus a kernel install. I've tried it a few times now with no luck. Pixel XL btw.
Hi,
I need some help
Today I successfully installed the newest stable Xiaomi.eu-ROM on my finally unlocked Mi8, using TWRP from here: https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-1110-t3869729
TWRP is working flawlessly, but I didn't succeed in making root with Magisk to work.
What I did:
- I booted into TWRP
- formatted data
- rebooted back into TWRP
- flashed DM-verity disabler from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
- flashed Magisk v18.0 right after from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- wiped dalvik cache
- rebooted the phone
But everytime I did it, I didn't had root access (checked with Root Checker app) when the phone finally booted up to MIUI 10.1.2.0 (PEACNFI).
I even didn't have Magisk Manager showed up.
Can you tell me what I did wrong? I don't have a clue
Thanks a lot and best regards
Mischa
what does magisk manager tell you about your magisk installation status?
Strange thing...
After I rebooted the phone, there was no Magisk Manager nor the phone was rooted, what I checked with Root Checker app.
Then I used it a couple minutes before it became really laggy. My chosen theme disappeared back to stock theme, scrolling was nearly impossible and the screen went black.
I was not able to wake up the display again, so I held down the power button a couple seconds until the phone rebooted.
Now I saw that the Magisk Manager was installed, without me doing anything else than rebooting after the phone got unusable.
Weird, right? I read that there might be lags after installing Magisk, but that it's going to be like that was surprising.
Anyway, I have root now, TWRP works, Magisk v18 is installed. Now I only have to find some must-have-modules, e.g. like stereo-mod.
BTW, could it be that Netflix isn't working on rooted phones? I always get error 14 saying that the Netflix-service is not reachable even though I have internet connection.
hey dude i know this isnt a guide
but i followed your kind of direction after spending the whole afternoon and few hours in the evening to figure how to root this phone and finally it worked (so far)
thanks a lot my man
and i didnt even format after flashing twrp i hope it didnt **** up my phone
Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!
Organics said:
Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!
Click to expand...
Click to collapse
Please help me to root Moto X4, bootloader unlocked
hrushikesh.inc said:
Please help me to root Moto X4, bootloader unlocked
Click to expand...
Click to collapse
Wrong thread.
https://forum.xda-developers.com/moto-x4/help/moto-x4-f-q-s-thread-t3814393
I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
I haven't need to use edxposed as I was refusing to upgrade from my old oneplus 3, so I'm a complete noob here at this point,
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Thanks!
everlasting207 said:
I forgot to add on the title -- my phone is the EU variant with Snapdragon 5G. (G781B)
Hello, did anyone get Edxposed for the phone?
I've succesfully rooted but edxposed seems to be always causing some kind of bootloop.
However, it does seem like there seems to be issue on this area anyway.
If anyone succeeded, please share what you did.
Click to expand...
Click to collapse
Morning
I have just purchased the same phone, but I didn't get as far as you, so in the hope we can help each other here is a summary of what I did and how far I got -
I upgraded stock ROM all the way upto Android 11
Then enabled dev. options, and clicked on OEM unlock and then rebooted following the new unlock bootloader option on the download screen.
Then rebooted into download mode and flashed vbmeta_disabled.tar via ODIN (this then factor reset the phone).
Then had to re-flash stock android (via ODIN), as OEM unlock disappeared from dev. options.
Then back into download model to flash twrp 3.5.1 via ODIN.
Then after to trial and error and help from @afaneh92 I figured how to get into twrp recovery (and how to stop the phone from restoring stock recovery).
I then extracted & patched boot.img in Magisk (see instructions)
Then I booted back into download mode and 'tried to flash to new magisk patched boot.img via ODIN, but it failed with Can't open the specified file (line: 2006)
I then installed magisk manager 8.05, then tried flashing Magisk 21.2 via twrp and it failed with (Android Rescue party trigger).
So I then re-flashed multi-disabler.zip via TWRP and without rebooting formated data, then power off and boot back into recovery. I then flashed magisk 21.2 no problem.
Back into Android I loaded up magisk to confirm I was rooted and to get Riru & EdXxposed installed.
I installed EdXposed manager via its APK.
I then went back into Magisk manager and found and installed Riru 23.3 (this as i understand it replaced Riru - core).
I then found the latest stable version of EdXposed YAHFA 0.4.6.4 (4563) and this refused to install via magisk manager, with error ( ' Riru - core ' is not installed, Unsupported v22+ is installed, user 21.3 instead ) . So Clearly the above ver. of EdXposed isnt compatible with the latest version of Riru.
I then installed the alpha version of EdXposed 0.5.1.4 (4655) and this installed, but when I went into EdXposed manager it said it was installed but not active
So I have my shiny new SM-G781B, w/custom recovery & rooted, but no Xposed framework. I need Xposed for Xprivacy_lua so not having this running isnt an option. So I am going to try Riru - core 21.3/EdXposed_ 0.4.6.4 and if that fails then going all the way back to Android 10 and starting from the top.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
What versions of Android, Twrp, Magisk, EdXposed, Riru - have you got installed? Also regarding your EdXposed bootloop - if you read the supports docs, its does say that YAHFA can cause soft loop, and to try Sandhook. But on my old S7, Sandhook caused a boot-loops so I went to and am using YAHFA with no issues - so as always your mileage will always vary.
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just restarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the download mode problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
n00btuber said:
Phone Model no : Samsung Galaxy S6 / SM-G920F
Security patch date: 01.10.2017
Android version: 7.0
Root status: Yes
Hey guys,
I rooted my phone several weeks ago for the first time via odin and everything went fine. I installed TWRP and Magisk and everything worked out.
Today I was trying to update Magisk from v20.x to v21.x with the inapp option, but now im stuck in a bootloop to download mode, screen says "Downloading... do not turn off target".
Even if I turn the phone off with Power + Home + Vol Down its just resarting right away and getting stuck in the same screen again.
Im still able to enter TWRP Recovery, but I dont know what to do to end the downloading problem when trying to start the phone.
I actually dont know/understand much about that stuff, so I dont know which other info I need to provide.
Is there something I could do without going through the whole flash/root process again?
should i try to delete magisk and install it again? if yes, how do i do it?
Help would be appreciated.
Click to expand...
Click to collapse
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Lord Sithek said:
I don't know much about your device but if you can enter TWRP, it's not that bad. First what you can try is to download Magisk uninstaller and flash it in TWRP from USB. However, I don't know what can you do to update Magisk safely. Would be best if you can check your device forum or ask the question there
Click to expand...
Click to collapse
Looked like my device forum is pretty dead, which is why I asked the question here again. Thanks for the fast respone
Its probably not possible to just install a Magisk version again and overwrite the current one, probably need to uninstall first and then install it again?
There is a Magisk Module Uninstaller and a Magisk Uninstaller. Are those different things or just the same?
How to Uninstall Magisk Module Using TWRP Recovery | MagiskRoot
Uninstall Magisk Module using TWRP Recovery or Offline whenever you stuck into bootloop. Magisk Module Uninstaller and Magisk Manager for Recovery methods.
magiskroot.net
How to Uninstall Magisk From Android [2 Easiest Method]
Are you facing issues with Magisk? You can uninstall magisk from your phone with these simple and easy steps.
magiskmanager.com
Because the 2nd guide says in the end
Keep in Mind – Whenever you use TWRP as a method to uninstall Magisk, it is imperative to flash the Magisk Module Uninstaller Zip onto your device.
Does this mean I need to do the magisk module one first?
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
If you need to uninstall Magisk use the uninstall zips from the above linked Github repo, and if you need to uninstall modules (but those will also be removed by the Magisk uninstaller) you can do that directly from TWRP:
https://www.didgeridoohan.com/magisk/Magisk#hn_Uninstalldeletedisable_modules_from_recovery
A lot of times you can just flash another Magisk version over your installed one, but there are times where you do need to uninstall first. Since you have TWRP it can't really hurt to just try flashing whatever Magisk zip you want and it it doesn't work you can just use the uninstaller first.
One other thing to try would be the Canary release, mainly to see if you're affected by any bugs that is present in the current stable release but has been fixed upstream. You'll find the Canary app in the same Github link above.
Didgeridoohan said:
@n00btuber Do not trust those websites. They're in no way official and are just trying to get adc revenue from Magisk's popularity. If you're really unlucky they'll also provide you with malicious zips...
Only download stuff from John's GitHub:
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Ok.
Was trying to use the uninstaller from his GitHub.
Trying to flash it leads to
"Updater process ended with ERROR:1
Error installing Zip file .....
Updating partition details"
So what to do now?
Trying to just flash any Magisk version to overwrite the current one leads to the same result.
I think it says Unsupported/Unknown image format
Your TWRP might be bugged/incompatible. I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Didgeridoohan said:
Your TWRP might be bugged/incompatible.
Click to expand...
Click to collapse
But TWRP worked fine when installing magisk the first time, I even tried the same zip folder I used to install it back then, but it wont work anymore.
Didgeridoohan said:
I'd reflash your stock boot image and then patch the file manually (you'll find the instructions for that on GitHub as well).
Click to expand...
Click to collapse
However, whats my stock boot image and how to reflash it? Cant find a guide for that on GitHub.
Would a Factory Reset wipe all Magisk stuff and my TWRP Partition as well?
Does anyone know what is going on between Magisk and Google? It seems Google has removed Magisk Manager from the Play Store AGAIN! What's more, I downloaded and installed the apk but when I try to use it to install the latest Magisk the install fails. Tried installing the Magisk zip via TWRP, and while it doesn't show any errors, I still don't have root.
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
n00btuber said:
Ok I really need some more help @Didgeridoohan
Meanwhile I tried to reinstall TWRP from within TWRP. There was no error so I think it should have worked, but didnt solve the problem.
As soon as I try to boot the system it directly boots download mode and gets stuck in it. The volume buttons wont work or do anything as they are supposed in download mode.
Im still able to get into TWRP, but I still dont know what to do to stop this crashed download mode that starts over and over again.
When trying to flash the magisk uninstall it states "cannot access /data", when trying to flash a magisk installer it states "unsupported/unknown image format"
I dont care about Magisk right now though, I can root and install magisk again as soon as im able to clear the download mode problem. I was just trying this because trying to update magisk from within magisk manager has caused this download mode problem to appear.
Just tell me please how to fix that or how to factory reset my phone so it is able to boot regular again.
Thank you
Click to expand...
Click to collapse
Sounds to me like you need to reflash your ROM, not TWRP. According to your OP, you're running Android 7, but it doesn't say if it is stock or a custom ROM.. If it is stock, then use Frija.exe to download the ROM and then flash th AP, BL and HOME_CSC md5 files with Odin. If it is a custom ROM, use TWRP to flash the ROM and gapps. DO NOT try to flash Magisk. Right now there seems to be a problem with Google disabling Magisk. Wait till it is resolved before attempting to get root.
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Didgeridoohan said:
@n00btuber Dirty flashing your ROM is most likely the way to go, just like described above.
But @lewmur, what do you mean by "Google disabling Magisk"? If you're talking about SafetyNet there are ways around that (and it doesn't affect root)...
Click to expand...
Click to collapse
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
lewmur said:
I not talking about safety net. Look in Play Store for Magisk Manager. It is no longer there. And even if you download and install the apk, it won't install Magisk. Flashing Magisk from TWRP doesn't give root privileges. This just happened yesterday.
Click to expand...
Click to collapse
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Didgeridoohan said:
The Magisk Manager hasn't been on the Play Store for years... Edit: reference - https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/post-72508849
Nothing of what you describe has anything to do with Google "disabling Magisk".
Click to expand...
Click to collapse
That 's my mistake. Play Store would put up a lot of "Magisk Manager" stuff, but I never really tried any of it because flashing Magisk would give me the Manager. But even that "stuff" no longer shows up.
Butt Magisk Manager still won't install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
lewmur said:
Then why won't Magisk Manager install Magisk. It will download the zip file, but when it attemps to install it, it get an error saying Unsupported/Unknown image format. If I flash it from TWRP, and then open Magisk Manager, it still says N/A under Installed for Magisk.
Click to expand...
Click to collapse
That will be an incompatibility between Magisk and your device and has nothing to do with Google (blame your OEM for doing weird stuff instead).
Thanks for the help guys, had to flash the ROM, now its working again.