I am trying to install magisk on stock nougat with elementalx installed but after reboot it wont boot and stuck on "your device is unlocked" mensage, I tried to find some tutorial but no success
Which magisk version are you using? Try magisk 18 or 17 and also try wiping your cache after flashing magisk and before you reboot.
Ensure also if you're switching root managers (e.g. if you're coming from supersu), that you've fully uninstalled the previous manager and reverted back to the stock kernel, for a clean start. Then, flash ElementalX 2.0.1 (for Nougat) then flash magisk. Wipe cache and reboot
echo92 said:
Which magisk version are you using? Try magisk 18 or 17 and also try wiping your cache after flashing magisk and before you reboot.
Ensure also if you're switching root managers (e.g. if you're coming from supersu), that you've fully uninstalled the previous manager and reverted back to the stock kernel, for a clean start. Then, flash ElementalX 2.0.1 (for Nougat) then flash magisk. Wipe cache and reboot
Click to expand...
Click to collapse
ty bro, i tried 18.3 but still stuck and only 17 works for me
None worked for me. I cant root the phone again after I reinstalled android.
lexie90 said:
None worked for me. I cant root the phone again after I reinstalled android.
Click to expand...
Click to collapse
What device do you have, and which stock ROM are you using? Root steps can be specific to a device and the ROM you're using.
stuck after flashing magisk zip
echo92 said:
Which magisk version are you using? Try magisk 18 or 17 and also try wiping your cache after flashing magisk and before you reboot.
Ensure also if you're switching root managers (e.g. if you're coming from supersu), that you've fully uninstalled the previous manager and reverted back to the stock kernel, for a clean start. Then, flash ElementalX 2.0.1 (for Nougat) then flash magisk. Wipe cache and reboot
Click to expand...
Click to collapse
I flashed the magisk zip file from twrp and rebooted but its stuck not booting after that i tried wiped all data and formatted also but still the same pls he
Suraj Rawat 271201 said:
I flashed the magisk zip file from twrp and rebooted but its stuck not booting after that i tried wiped all data and formatted also but still the same pls he
Click to expand...
Click to collapse
What device are you using, which ROM are you running and which magisk version have you been using?
Related
I just reloaded oxygen 3.1.0 on my device, unlocked and flashed recovery. Everything works fine to this point but as soon as I flash superSu my phone stops booting. I have tried clearing the cache and checked for the recommended version of the superSU zip with the same result. Anyone have any suggestions?
rompup said:
I just reloaded oxygen 3.1.0 on my device, unlocked and flashed recovery. Everything works fine to this point but as soon as I flash superSu my phone stops booting. I have tried clearing the cache and checked for the recommended version of the superSU zip with the same result. Anyone have any suggestions?
Click to expand...
Click to collapse
Which recovery ? Which superSu version ?
SuperSU 2.79
TWRP 3.0.2-2
rompup said:
SuperSU 2.79
TWRP 3.0.2-2
Click to expand...
Click to collapse
There shouldn't be a problem as I've used these versions without any problems.
Try a clean flash (wipe data + cache + dalvik cache) with latest superSu beta(2.79 SR1).
Search for supersu in oneplus forums for oxygen 3.1.0 since normal supersu will break boot.
rompup said:
I just reloaded oxygen 3.1.0 on my device, unlocked and flashed recovery. Everything works fine to this point but as soon as I flash superSu my phone stops booting. I have tried clearing the cache and checked for the recommended version of the superSU zip with the same result. Anyone have any suggestions?
Click to expand...
Click to collapse
Scherzengel said:
To succesfully install the newest Versions of SuperSU you have to install it in systemless mode. If you flash the ZIP it will install it in /system mode, so you have to force the systemless install.
Before you flash the newest Beta SuperSU.zip go to the TWRP terminal and write:
echo SYSTEMLESS=true>>/data/.supersu
Then flash the ZIP.
SuperSU will be installed in systemless mode and your Phone will boot up fine.
Click to expand...
Click to collapse
I found this in another thread and it worked for me. all credit goes to Scherzengel
Hey all!
Those of you monitoring the unofficial LineageOS thread may have seen me talking about this already. I've been having issues with Magisk. I'm running their beta versions for 13.0.
So here's the story...
I have wanted to pass SafetyNet since May, when I got this phone and rooted it. I obviously went to Magisk, and when I realized that 11.6 was not passing SafetyNet, I decided to try the 13 betas. These didn't pass either, but since they were more recent than 11.6, I stuck with them. But when I heard of the Universal SafetyNet Fix Module, I immediately tried it.
Bottom line, these are my issues:
1. Magisk will not install the module. I go to Magisk Manager -> Modules -> + and select the ZIP for the module. Magisk gives me a toast saying "Installation error!" (See screenshot).
2. Okay, so now I want to start fresh and see if it works then. I boot into TWRP, flash the lastest Magisk uninstaller (08 June), and boot. Nope! Stuck on the "device unlocked" screen with ID: bad key.
3. Uhh.. maybe the stock boot image will work? I go to TWRP and flash the stock boot.img taken from the stock firmware. Still ID: bad key and I'm stuck again.
And I can boot successfully if I flash a Magisk 13.0 beta.
So, does anybody have any solutions? I think I may just have to reflash stock firmware.. not my top choice. Thank you for any help and reading through my long post :good: :highfive:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
eskamhl said:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
Click to expand...
Click to collapse
Will give it a shot and update when I see results.
Edit: Nope. I've a feeling that I'll have to start from scratch by flashing stock firmware.
Try flashing the safetynet fix in trwp.
triggerlord said:
Try flashing the safetynet fix in trwp.
Click to expand...
Click to collapse
Tried already. Still no.
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
smitharro said:
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
Click to expand...
Click to collapse
Lol, was doing this all on the stock ROM. See my original response to triggerlord's post.
Edit: issues fixed with a clean install of the pure Nexus ROM. I'm assuming this would be the case with a clean install of the stock ROM, but I am definitely not switching anytime soon (this ROM is amazing!)
Spoiler: Culprit was App Systemizer.
I've had Magisk on my OP5 (128) for some time, and had the most common modules installed (can't get the list currently), but when I rebooted the phone this morning to install AllStream (dlna streaming app), the phone got stuck on the 1+ logo screen, that shows before the boot animation. I let it run for around 15 minutes but it was still stuck.
I rebooted into fastboot (recovery didn't work) and did
Code:
fastboot boot twrp-cheeseburger.img
to get into TWRP, and I reflashed the zip of the latest OOS (4.5.8) (of course, wiped caches beforehand). I rebooted and it worked (no root, of course).
So I rebooted into TWRP and flashed a freshly downloaded Magisk 13.3 zip, rebooted, and then it got stuck on the 1+ logo again. Flashed OOS zip, and it worked again (writing from the phone right now).
TL;DR: OP5 128 with Magisk & TWRP works perfectly. And then one day, book, stuck on logo at boot
Flashed latest OOS zip, works. Flash Magisk zip, stuck at boot again. Flashed OOS again, works.
In case of a Magisk module is responsible for that, how can I remove modules without actually installing Magisk?
I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5
Try just installing the magisk manager apk but without installing magisk root. Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.
Wechy77 said:
I'm on latest OOS with magisk and twrp with no issues. I don't use any magisk module. My upgrade procedure was in twrp:
Flash full zip of 4.5.8
Flash twrp IMG from twrp
Flash magisk 13.3
Wipe cache and dalvik cache
Reboot
Sent from my OnePlus 5
Click to expand...
Click to collapse
You don't need to flash the twrp image on every update.
As I said, Magisk has been working perfectly for weeks, it's just that when I random rebooted my phone it didn't boot correctly.
Then on magisk manager uninstall the offending module, reboot to recovery, wipe caches and then flash root.
Click to expand...
Click to collapse
If Magisk is not installed, Magisk Manager doesn't have the Modules tab.
You don't need to flash the twrp image on every update.
Click to expand...
Click to collapse
I do. Stock recovery is restored every time I flash an update.
I am quite sure the problem comes from a module and not from Magisk itself, since it was working before. But I can only remove modules if Magisk is installed.
Quote from my reply on the other thread
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse
I'm having the same problem, look here: https://forum.xda-developers.com/oneplus-5/help/magisk-modules-t3651558
I suppose the magisk's modules stay installed in the background and when we flash it again, the phone bootloops.
I had to use SuperSU for now until I understand what's happening.
I updated to 9.0.12 today and went to magisk app to reinstall and wasnt able to. So i rebooted and when it was all booted back up i didn't have magisk or root. I decided it was time for a permanent twrp so i loaded twrp. Img and installed the twrp installer. Booted back into twrp and flashed magisk 18.1.zip and rebooted. When it was back up i still didn't have magisk or root so i tried to install magisk apk and it fails to install.
I dont know what else to do to be rooted again. Any help would be great.
That's strange. I'm having a similar problem. I upped to OOS 9.0.12 on my rooted 6t by flashing the full rom, flashing TWRP, then rebooting to recovery and flashing Magisk 18.1 stable.
After rebooting it boots into the system, but after just a quick moment it says powering down and then reboots to TWRP. I tried a nandroid backup and the same issue keeps happing.
Flashing OSS 9.0.12 and TWRP again fixes the rebooting issue, but now I don't have root
did you "fastboot boot twrp img name" then install the Twrp installer to both slots ?
AndyBury said:
did you "fastboot boot twrp img name" then install the Twrp installer to both slots ?
Click to expand...
Click to collapse
That's what I did and have no issues.
BittahWarlock said:
That's strange. I'm having a similar problem. I upped to OOS 9.0.12 on my rooted 6t by flashing the full rom, flashing TWRP, then rebooting to recovery and flashing Magisk 18.1 stable.
After rebooting it boots into the system, but after just a quick moment it says powering down and then reboots to TWRP. I tried a nandroid backup and the same issue keeps happing.
Flashing OSS 9.0.12 and TWRP again fixes the rebooting issue, but now I don't have root
Click to expand...
Click to collapse
I had this issue yesterday too, where I loaded 9.0.12 and TWRP, rebooted to recovery, loaded Magisk and then the phone would automagically shutdown after boot.
TL;DR; an issue with a magisk module misbehaving.
After some research, this is what worked for me:
Download the latest version of Magisk and the Magisk uninstaller from the Magisk thread. Reboot to recovery, and then zip install Magisk, but don't reboot. Immediately after, run the Magisk uninstaller. This should clear any offending modules. After that, you can reboot back into recovery and install Magisk normally. You'll need to reload your modules, though.
psychen6 said:
I had this issue yesterday too, where I loaded 9.0.12 and TWRP, rebooted to recovery, loaded Magisk and then the phone would automagically shutdown after boot.
TL;DR; an issue with a magisk module misbehaving.
After some research, this is what worked for me:
Download the latest version of Magisk and the Magisk uninstaller from the Magisk thread. Reboot to recovery, and then zip install Magisk, but don't reboot. Immediately after, run the Magisk uninstaller. This should clear any offending modules. After that, you can reboot back into recovery and install Magisk normally. You'll need to reload your modules, though.
Click to expand...
Click to collapse
thanks, that worked
BittahWarlock said:
That's strange. I'm having a similar problem. I upped to OOS 9.0.12 on my rooted 6t by flashing the full rom, flashing TWRP, then rebooting to recovery and flashing Magisk 18.1 stable.
After rebooting it boots into the system, but after just a quick moment it says powering down and then reboots to TWRP. I tried a nandroid backup and the same issue keeps happing.
Flashing OSS 9.0.12 and TWRP again fixes the rebooting issue, but now I don't have root
Click to expand...
Click to collapse
The best way to take the update is download the full ROM and let the factory installer do the update via local install.
You lose root and TWRP, but that happens anyway.
I typically install, reboot, install.
This forces the OS to be the same in both a and b.
Then I go through the process of TWRP, etc.
after what i mostly do:
in fastboot boot to twrp,
install full rom,
install twrp,
reboot to twrp,
install magisk,
reboot to system
aaand it shut down on me ;(
in twrp i had to:
uninstall magisk (with the magisk uninstaller)
install magisk
almost done (reboot to system)
reinstall your magisk modules (they will be gone thanks to the unistaller, so know what you have magisked)
luckily it was that simple
So to avoid it al together:
take note of your magisk modules
fastboot to twrp,
install full rom,
install twrp,
reboot to twrp,
uninstall magisk,
install magisk,
reboot,
done!
Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Factory reset from TWRP?
yes
null0seven said:
yes
Click to expand...
Click to collapse
So, do you mean the classic Wipe data, cache and dalvik?
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
TWRP Users
1. Boot into TWRP and Flash the Latest Magisk Uninstaller
2. Flash the latest Full Oxygen OS Zip
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash the Latest Magisk to maintain root
6. Reboot System and Enjoy the latest firmware without any data loss
Click to expand...
Click to collapse
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Galeanatur said:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Click to expand...
Click to collapse
I don't have the OTA but the full rom, isn't simplier to update with the full ROM?
I think I'm going to try the null0seven's solution
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Ok, I've done this and actually is even worse, the device started to boot in recovery again and TWRP doesn't recognize that the internal storage is crypted, so i can't even access the internal storage (it shows only strange folders), so, now I can't flash the nandroid backup anymore.
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
null0seven said:
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
Click to expand...
Click to collapse
So I've to Full wipe and then adb sideload the ROM? Because at the current state I can't even boot the device, it always starts in TWRP
Edit: I've also tried the blue_spark's version but nothing changed, TWRP can't recognize the encrypted storage
you can try this first.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
fuji97 said:
Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Click to expand...
Click to collapse
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
ebproject said:
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
Click to expand...
Click to collapse
No, I flashed the full ROM downloaded from the OnePlus server
Have you tried formatting data?
Cablespider said:
Format data.
Click to expand...
Click to collapse
So, full format data and flash rom + TWRP + Magisk?
fuji97 said:
No, I flashed the full ROM downloaded from the OnePlus server
Click to expand...
Click to collapse
You're best bet is to use the MSM tool
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
fuji97 said:
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
Click to expand...
Click to collapse
Maybe it was a Magisk module that caused it. I removed pixel module from Magisk and it done the same to me.