Related
Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part
You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2
Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs
The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!
Next time don't be a twrp and use twrp
dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update
Hey guys,
So I saw that the OnePlus team rolled an update (9.0.3) and I wanted to get it installed on my phone (from 9.0.2). I had Magisk 18 installed and working correctly so I installed the OTA update and then went to Magisk and selected "Install to second slot after OTA" (or something like that), thinking it would be enough. I then rebooted my phone and now when I boot it, it goes after the boot animation, then show a dialog saying "Shutting down..." then automatically reboot to recovery (no TWRP).
Since I clearly ****ed up my install, how can I fix this? Do I just have to install twrp and flash magisk to make everything work again? If yes, can you point me to an up-to-date tutorial? I am totally clueless and could use some advices...
Thank you in advance
Just in case, I successfully got on the fastboot and then used "fastboot" command to boot on TWRP. I am now making a backup of "/sdcard".
But I would really like to not have to make a factory reset... Is there a solution to avoid this?
Flash ROM and flash Twrp
Reboot
Shutdown
Boot on twrp
Flash magisk
Do this after every update, magisk install on parallel slot not good idea if you don't know how to repair your mistake [emoji6]
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
I succeeded in fixing it by installing twrp and doing... I don't really remember what lol, but I was able to uninstall Magisk and reinstall it with twrp, now everything works again!
"Do this after every update, magisk install on parallel slot not good idea if you don't know how to repair your mistake"
Yeah, I thought it was the most safe way to update but it seems that I was clearly mistaken.
Thank you anyway!
I've updated like that a couple of times now and it always work. Most likely you had modules that made you not being able to boot.
hey, the error is that you need START the update using the standard OTA interface (don't reboot), and then go to magisk, and install to second slot. Afterwards it will reboot. What you did is configure your phone to boot from the second slot but the update wasn't ready or something like that. I don't know the technical details but I did the exact same thing on the last update, and I've learned from my mistake
In that case, you can change the slot using fastboot, I think that's what I ended up doing. It took me like a whole afternoon to figure out the mistake. I'm hoping this warning is useful for future updates.
It will be useful yes, thank you for the clear explanation!
noom4_5 said:
Hey guys,
So I saw that the OnePlus team rolled an update (9.0.3) and I wanted to get it installed on my phone (from 9.0.2). I had Magisk 18 installed and working correctly so I installed the OTA update and then went to Magisk and selected "Install to second slot after OTA" (or something like that), thinking it would be enough. I then rebooted my phone and now when I boot it, it goes after the boot animation, then show a dialog saying "Shutting down..." then automatically reboot to recovery (no TWRP).
Since I clearly ****ed up my install, how can I fix this? Do I just have to install twrp and flash magisk to make everything work again? If yes, can you point me to an up-to-date tutorial? I am totally clueless and could use some advices...
Thank you in advance
Click to expand...
Click to collapse
Flashing magisk uninstaller fixes this.
*system error* said:
Flashing magisk uninstaller fixes this.
Click to expand...
Click to collapse
I had same problem and I fixed it flashing magisk uninstaller, but how could I install magisk without having this issue?
tamamma said:
I had same problem and I fixed it flashing magisk uninstaller, but how could I install magisk without having this issue?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213/page5
If you are on Android 10 beta 1
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).
wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk
lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1
I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...
wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed
I installed the update like i normally did. Went into magisk and installed Magisk on the "After OTA" setting. Now it's boot looping. I'm NOT using TWRP. This is the first time this has happened. Normally I update the OTA, DONT RESET, install Magisk on OTA setting and reboot and it works fine. Anyway to fix this? It boots 90%, but once it gets to main screen RIGHT before it asks for my PIN, it goes to 'rebooting'. Do I need to wipe my phone and start over?
I'm not rooted but From my experience you have to delete modules folder in twrp
RISHI RAJ said:
I'm not rooted but From my experience you have to delete modules folder in twrp
Click to expand...
Click to collapse
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
whitak3r said:
I just wiped my phone and I'm going to start fresh. I should have done some reading before installing the new OTA. I just figured it was like the old ones. I was bootlooping so I was unable to disabled those AFTER the fact.
My fault at this point. I'll just start fresh and reinstall Magisk when I have time.
Click to expand...
Click to collapse
Only disabling modules won't help,You have to delete the folder,Next time when you update
RISHI RAJ said:
Only disabling modules won't help,You have to delete the folder,Next time when you update
Click to expand...
Click to collapse
Thank you. I'll do that next time, would of saved me a bunch headache if I would of just read a little bit lol
I ended up cleaning my system and everything went back to stock root. So I updated magsik and magisk man. And it fixed everything. I'm in the processes of reinstalling all my stuff now though
For me, there is only one module causing problems - the OOS call recorder enabler.
I simply remove that module and reboot before starting the OTA and all was fine.
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Is this a bug of Magisk?
sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
Hi, can you use this command on adb shell? OnePlus 7T Pro doesn't have TWRP yet. Thanks.
sulliwane said:
I have same problem here (bootloop). Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!
Click to expand...
Click to collapse
This. But the module clearly says REMOVE before attempting upgrade!
And like I suppose most people here - I also did not follow that instruction and ended up with a bootloop. lmao. :good:
If you have TWRP you can remove modules if you have a bootloop.
Don't know if you guys saw, but TopJohnWu released a new Canary Magisk for the developer preview.
spotmark said:
Don't know if you guys saw, but TopJohnWu released a new Canary Magisk for the developer preview.
Click to expand...
Click to collapse
Tried it but got a bootloop. Not sure what I did wrong. Used canary magisk manager to patch the factory boot.img and flashed the patched.img with fastboot. Then the bootloop.
Daisymae said:
Tried it but got a bootloop. Not sure what I did wrong. Used canary magisk manager to patch the factory boot.img and flashed the patched.img with fastboot. Then the bootloop.
Click to expand...
Click to collapse
Did you flash to both slots? Maybe that could be the problem?
Sent from my Pixel 3 XL
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Eudeferrer said:
Did you flash to both slots? Maybe that could be the problem?
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I'll give it a try...
Addendum--Tried both slots=bootloop
Daisymae said:
I'll give it a try...
Addendum--Tried both slots=bootloop
Click to expand...
Click to collapse
Works! Downloaded latest MM then patched file. Root!
kngbn79 said:
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Click to expand...
Click to collapse
Try the very latest Canary MM. It works!
Daisymae said:
Try the very latest Canary MM. It works!
Click to expand...
Click to collapse
I tried last night with the newest MM and still ended up with the same result. Not sure if missing something or not but did notice the patched image was half the size of the unpatched one
kngbn79 said:
I tried last night with the newest MM and still ended up with the same result. Not sure if missing something or not but did notice the patched image was half the size of the unpatched one
Click to expand...
Click to collapse
Try again today. He just pushed a new magisk update. (Today)
Anyone tried this on dp3?
I just clean flashed dp3 and downloaded the latest magisk to test. Nothing but bootloops here.
Anyone care to upload their patched boot?
Update: works fine after all. Redownloaded .apk and made sure to select the canary channel in the app settings.
lafester said:
I just clean flashed dp3 and downloaded the latest magisk to test. Nothing but bootloops here.
Anyone care to upload their patched boot?
Update: works fine after all. Redownloaded .apk and made sure to select the canary channel in the app settings.
Click to expand...
Click to collapse
Update: SDK Platform-Tools: r30.0.0
It roots dp4 but after flashing module it unroots but the module is still active and reflashin boot.img wont reroot at that point
edit: Clean flashing DP4 5 times. lollolol. Each time i would have to copy the stock boot over to the phone an let magisk patch it then copy it back over to pc to flash. I could not use the previous patchedboot.img for whatever reason. And if i factory reset it wouldnt work period. The only module im flashing was busybox. but either way this time after clean flash i went to magisk settings changed the name of magisk package an turned on magisk hide. When restarting after busybox install I still had root. SO step in right direction for now
kngbn79 said:
I had the same problem as Daisymae, I patched the boot image with Canary Debug MM, flashed it to both slots and ended up stuck on the screen with the Google logo bootlooping for around 10 mins each time
Click to expand...
Click to collapse
Cant you use direct method? boot the phone with patched boot and flash direct. This method eliminates most issues.
Update: SDK Platform-Tools: r30.0.1
billyt1 said:
It roots dp4 but after flashing module it unroots but the module is still active and reflashin boot.img wont reroot at that point
edit: Clean flashing DP4 5 times. lollolol. Each time i would have to copy the stock boot over to the phone an let magisk patch it then copy it back over to pc to flash. I could not use the previous patchedboot.img for whatever reason. And if i factory reset it wouldnt work period. The only module im flashing was busybox. but either way this time after clean flash i went to magisk settings changed the name of magisk package an turned on magisk hide. When restarting after busybox install I still had root. SO step in right direction for now
Click to expand...
Click to collapse
Weird I flash the dp4 patched boot without issues
On July 5th update, works great! (Though not all modules work due to the removal of /sbin, etc)
?