Question Magisk on android 13 beta - Nothing Phone 1

does anyone use magisk on android beta 13?

MyRaVEi said:
does anyone use magisk on android beta 13?
Click to expand...
Click to collapse
I can't get magisk to work on android 13. after flashing the boot, I get a bootlap

I was able to fix it.
1) flash the stock boot and install the Magisk application (if removed)
2) press and hold the reset button, press "reboot to safe mode"
3) immediately press the power + volume down to get into fastut and prevent the phone from turning on
4) we get into fastubt
5) flash the patched magisk image, after that the phone should boot in safe mode
6) reboot the phone in normal mode
7) go to magisk and remove the "nothing mod" module
it was a surprise to me that even after deleting the Magisk application, the modules of the old modules cause a bootlap

Related

No TWRP, Bootloop after installing EdXposed Module

I am running the latest OOS 10.0.1 Stable on my OP6T
I installed the Riru-Core module from magisk manager, rebooted perfectly fine. Afterwards installed the EdXposed module. Now I am stuck in a bootloop. Is there a way to uninstall the module without having TWRP? or factory resetting.
edit: I am unable to boot into fastboot or recovery
Please help me out
Thank you
Press volume up + power button to force reboot then press volume down + power to get into stock recovery. Then you can boot to fastboot through stock recovery...
2 Options ,
1. Try flashing stock boot.img on fastboot to remove Root so EdExposed won't work. (Recommended)
Then you'll have the option to remove EdExposed modules.
2. msmdownloadtool , But it will REMOVE all your data and will put your phone on Android 9.

Root, flash recovery and custom ROMs. Only for LG G6 H872 (20g original firmware)

This is a much easier way to flash a new recovery and custom roms. Besides using a PC / USB cable for unlocking the bootloader, all the process can be done straight from your device.
IMPORTANT: This procedure is only valid for LG G6 H872. Other G6 variants will end up bricked. All partitions will be wiped, this means that all the files needed must be saved to your external SD. It’s been tested with 20g firmware.
Prerequisites:
LG G6 device with original Oreo 20g firmware and fully charged
External SD card
Download and install su98.apk, Root Checker and Flashify
Download this specific TWRP version and save it to your external SD
Download Magisk and save it to your external SD
(Optional) Download latest TWRP to flash A10+ custom roms and save it to your external SD
0. Backup everything
1. Unlock your bootloader, otherwise you will brick your device. You can follow this guide.
2. Disable Google Play Protect (from PlayStore) or you won't be able to go on with the next step
3. Install su98.apk, open it and tap INSTALL NOW (leave the checkbox blank)
4. Install Root Checker and open it to verify that your device is rooted
5. Install Flashify and open it to flash TWRP (recovery_h872_20180813-1.img)
6. Turn off the phone (at this point, if the phone boots to Android you will have to start over from step 3).
7. Reboot into recovery (press and hold Volume Down and Power buttons together for a few seconds. When the LG logo appears, release the Power button while keep pressing the Volume Down and then press the Power button once more. Once you see a white screen, use Volume keys to choose "Yes" and Power button to select the option, you will have to press “Yes” twice).
8. Once in TWRP (be patient, takes some time to load) a “decrypt data” legend will appear. Press cancel. Then swype to allow system modifications. After that, go to Wipe / Format data and confirm by typing yes.
You are now able to flash any Stock ZIP (not KDZ). If this is your choice, remember to flash Magisk after flashing the ROM. If you want to flash any other custom ROM, jump to the next step.
9. Still in TWRP, flash Magisk to keep your device rooted
10. Flash the latest TWRP. Go to reboot options and tap Recovery
11. Once in the new TWRP, wipe system, data, dalvik, cache
12. Flash Rom + Gapps + Magisk and reboot to system
VIDEOS
Unlock bootloader LG G6 - H872
Root LG G6 - H872 without PC
Special thanks to Man Stevo for sharing this!!
LG G6 H872 back to stock Oreo 20g
IMPORTANT: All partitions will be wiped, this means that you must backup everything otherwise you’ll lose everything stored in the phone.
Prerequisites:
LG G6 device fully charged
USB cable
LG Mobile driver installed
Patched LG UP installed in the right folder (otherwise your device will not be recognized)
LG G6 H872 latest Oreo firmware (20g)
0. Backup everything.
1. We are going to flash this using the patched LG UP. Place the files in C:\Program Files (x86)\LG Electronics\LGUP. You can't just unzip it anywhere and run it, it will not find the model file.
2. Boot to download mode (power off your Phone. Plug one end of the USB cable to PC and while holding the Volume Up button connect the other end of the cable to your device. Release the Volume button once the device boots into Download Mode. To exit the Download Mode, press and hold the Power button until the device reboots)
3. Open LG UP and wait until the device model is recognized. Then choose partition DL
4. Pick the H872 20g KDZ and click start / ok
5. You’ll now get a list of partitions to flash, check them all and click start / ok
6. You may get a warning about additional modified partitions. Ignore it, and click ok
7. When the process is finished, the device will reboot
If the progress bar reached 100% and the device got stuck in the pink bootanimation, follow these steps:
Unplug the device and turn it off by holding Volume Down + Power (keep holding them down until it turns off)
Once the device is off, press and hold Volume Down and Power buttons together for a few seconds. When the LG logo appears, release the Power button while keep pressing the Volume Down and then press the Power button once more. Once you see a white screen, use Volume keys to choose "Yes" and Power button to select the option, you will have to press “Yes” twice.
The phone will now restore factory defaults and reboot to system
IMPORTANT
In case camera crashes when opening or you get an IMS error, you'll have to flash H87211h_00_0406.kdz (same procedure as above from step 0 to 7, just changing step 4 where you need to pick H872 11h KDZ), reboot to system (until you finish the initial wizard) and then flash H87220g_00_1228.kdz (again, same procedure from step 0 to 7).
Reserved
Works like a charm. Thanks
FYI, Going back to full working stock need to return to Android 7 firmware 1st (H87211h_00_0406.kdz); otherwise, you will get camera and IMS error.
Questions:
Does SkyHawk Recovery support stock firmware as TWRP can't backup and restore stock properly.
e20140 said:
Works like a charm. Thanks
FYI, Going back to full working stock need to return to Android 7 firmware 1st (H87211h_00_0406.kdz); otherwise, you will get camera and IMS error.
Questions:
Does SkyHawk Recovery support stock firmware as TWRP can't backup and restore stock properly.
Click to expand...
Click to collapse
Worked here when getting back straight to stock 20g, but good to know for those with issues.
I didn't test any custom recovery to backup stock, so I don't know about that.
Thanks for reporting!
Has anyone else used this recently? I cannot get the phone to boot to recovery at step 7. I've tried:
1) press vol- and pwr until the LG logo appears, release power, and press it once more
2) same as 1) above, but pressing power button multiple times to get through the "your phone can't be checked for security stuff" warning
Both times, it just boots straight to Android.
EDIT: Using adb reboot recovery worked!
Yeah, it works @zolotiyeruki
Check the vídeo in the first post for more details with the whole procedure.
Anyone else get an antivirus warning for the su98.apk?
My AV indicates it has a trojan in it - Trojan:Script/Ulthar.A!ml
AmbientMix said:
Anyone else get an antivirus warning for the su98.apk?
My AV indicates it has a trojan in it - Trojan:Script/Ulthar.A!ml
Click to expand...
Click to collapse
To follow up on this, I believe it's flagged because it is the exploit to get root that is seeing.
So it seems it's getting recognized by the anti-virus correctly and it's the desired functionality of the .apk.
(Anyone feel free to chime in to correct this if it's inaccurate.)
AmbientMix said:
To follow up on this, I believe it's flagged because it is the exploit to get root that is seeing.
So it seems it's getting recognized by the anti-virus correctly and it's the desired functionality of the .apk.
(Anyone feel free to chime in to correct this if it's inaccurate.)
Click to expand...
Click to collapse
Exactly.
hello Magisk no longer provides a downloadable zip to flash with twrp. that and for some reason i cant seem to get twrp to stick after flashing ive followed the instructions as exactly except for not installing magisk via twrp. i tried to install magisk via the manager after flashing twrp the first time and wiping data after that i am givin the option to reboot to system which i tried first and was not able to boot back into twrp. after doing everything from step 1 to finish all over i tried staying to flash the latest twrp before returning to system but seeing as how i dont have any gapps or roms or a flashable zip for magisk i just rebooted to system after flashing and still could not return to twrp..... i need help how do i get twrp to stick around after reboot, and how am i supposed to install magisk properly without the flashable zip? i seem to need a copy of my current boot.img so i can patch it with magisk and flash it with fastboot, how do i do this?
jsjames7715 said:
hello Magisk no longer provides a downloadable zip to flash with twrp. that and for some reason i cant seem to get twrp to stick after flashing ive followed the instructions as exactly except for not installing magisk via twrp. i tried to install magisk via the manager after flashing twrp the first time and wiping data after that i am givin the option to reboot to system which i tried first and was not able to boot back into twrp. after doing everything from step 1 to finish all over i tried staying to flash the latest twrp before returning to system but seeing as how i dont have any gapps or roms or a flashable zip for magisk i just rebooted to system after flashing and still could not return to twrp..... i need help how do i get twrp to stick around after reboot, and how am i supposed to install magisk properly without the flashable zip? i seem to need a copy of my current boot.img so i can patch it with magisk and flash it with fastboot, how do i do this?
Click to expand...
Click to collapse
Download latest Magisk APK, rename it to ZIP and flash it through TWRP.

Bootloop after Viper4Android

So I just rooted and got everything to work just fine (.33). Thought i'd smash in Viper4Android aswell.
The phone is now stuck on the logo with the red and two white dots.
I can get it to reboot with Vol+ and power, but the power-button does not let me go into recovery mode at all. It's like its disconnected.
Is there anything you can do to get into recovery/fastboot from here?
Also tried every single vol+powercombination with 0 results..
Thanks in advance.
What viper4android version did you install? And what Android version are you on?
If using Magisk 21> you should be able to hold down power button to boot into safe mode.
Hold power button and volume down and up at the same time, this should boot you into bootloader.
If you're on Android 10:
Boot into TWRP and remove module folder from data/adb/modules
Android 11 (or 10)
[Recovery][Stock OOS]Oxygen OS Stock recovery with ADB enabled
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled...
forum.xda-developers.com
Lossyx said:
What viper4android version did you install? And what Android version are you on?
If using Magisk 21> you should be able to hold down power button to boot into safe mode.
Hold power button and volume down and up at the same time, this should boot you into bootloader.
Click to expand...
Click to collapse
Thanks for the reply.
I seem to have solved it (for now..).
I could not get any key to answer to my commands when i rebooted the phone (hence why i couldnt get into recovery etc.), it only went back to the loop after displaying the usual message about the bootloader being unlocked.
Holding down both volume-buttons and using the msm-tool i managed to get it back to OEM (with everything locked. Again. Lmao) so now i just gotta watch out when I install Viper again (if i do..).
Running Oxygen 11.0.3.3.IN11BA with the latest Magisk (I just patched it today)
Edit: I just used the Viper4Android that i found inside Magisk if that makes any sense.
I'll try your links and see if i have to re-flash again..
Cheers

Magisk 21.4 causing bootloop on LG G5(H850)

Hi all,
So I was triying to update my Magisk through the recommended direct update method. I got a bootloop. Never had any issues with this update method, Magisk always did a splendid job.
Now my only options are:
1. Flash a custom rom (I don't have any stock Telekom roms)
2. Update Android OS to 8.0 with LG Bridge (my goal is to have a stock rooted android os, that's why I'm doing this)
3. adb reboot, flash the latest twrp recovery (at least that's working)
4. flash the latest Magisks without reboot option, just power off and then turn on. And this is stage where I get a bootloop.
I only have v19.3 saved on my HDD. Flashing that is working just fine, not causing any bootloop. However Fake GPS and Pokémon Go are not working with this version anymore. :/ So I'm kinda chess-mated here because of this Magisk bootloop.
Anyone can help me how can we fix this?
I have bootloops with all Magisk 21.x versions, so I'm stuck with 20.4. Can't you download Magisk 20.4 and install it from TWRP? I don't need SafetyNet, so I have no idea if Magisk 20.4 can still pass the check, but at least it would be newer than Magisk 19.3.
I downloaded the previous 21.0 versions from here https://droidfeats.com/download-magisk-zip/ flashed it and it's working. I also tested the previous versions. Seems like only 21.4 version is affected only, which is the latest stable.
I had the same problem: I had Magisk 21.4 and withing Magisk Manager I tried to update to v. 22.0 because I got an update prompt that asked me to do so. Trusting everything was fine I updated but I got a bootloop. I managed to recover from bootloop and get the latest version of Magisk working in my Huawei Y5 MYA-L13 (Android 6.0). For these steps, it is assumed Magisk v21.4 and Magisk v22.0 ZIP files are stored in your storage. This is the way I did it:
Manage to get into stock recovery mode.
This step was more time-consuming than it should have been... This Huawei model with the bootloader unlocked states at boot: "Press volume key up to 3 seconds to enter recovery to restore your device". It didn't... With Vol+ just restarted the device (no TWRP or stock recovery or download mode...) and pressing Vol- it loaded into the bootloop. It took me some time to guess the right way:
Plug the turned-off device into a USB cable plugged into the computer.
Wait for the device to start into "charging mode" (I made up this... I mean wait until the charging percentage appears).
Turn on the device using the Power Button.
Immediately, press and hold Vol+.
The device will reboot. Press and hold Vol -.
The device will get into the stock recovery mode (EMUI Huawei eRecovery).
Try again if this fails... After a few attempts, you'll get it.
Now the device will be visible to ADB. Verify this in a command prompt with adb devices. Mine was listed as 0123456789ABCDEF recovery.
Use the command adb reboot recovery to get into the real recovery mode. I mean TWRP. (It's still there even if it seemed to be it wasn't).
Flash the version that caused the problem. In my case, I had Magisk v21.4 initially, so I installed this same version ZIP I got from the official Magisk GitHub releases section.
Once finished the installation, if it was successful Reboot. The device should boot normally this time, having installed this version of Magisk and not the new one, of course.
Now proceed to uninstall Magisk 21.4 completely using the ZIP file provided in the above URL (step 4) with TWRP.
Follow the official installation guide in the Custom Recovery section to install Magisk 22.0 (that is: having renamed Magisk-v22.0.apk to Magisk-v22.0.zip previously, use TWRP to install it). Reboot.
Your device should boot normally. You'll find a Magisk app where you'll be able to verify latest Magisk 22.0 was successfully installed!!! DONE.
I hope my guide is useful to someone. If so, please like my post to be aware it was useful. Greetings!
TL;DR
adb reboot recovery
Install Magisk-v21-4.zip. This solves bootloop problem!
Uninstall Magisk using Magisk-uninstaller-20210117.zip
Rename Magisk-v22.0.apk to Magisk-v22.0.zip. Install it using TWRP.
Reboot. You have the latest Magisk version v22.0 installed with no bootloop!!!
I've upgraded from v20.4 to v22 yesterday using the new Magisk app, it all went smoothly.

Howto update a rooted Stock Rom

As far as I know OTA updates will not work if devices is rooted (Magisk/TWRP installed).
Very likely it checks unlock state of bootloader.
How to update? I wan't lose my data.
Firmware updates and keeping your data, for phones Magisk rooted without TWRP.
[Magisk] Root for the Galaxy S10 Series
Here comes official Magisk support for the Galaxy S10! Let's get Magisk to kick start the development of these Samsung devices! Link to Instructions Carefully read through everything in the page linked above! Follow the instructions closely so...
forum.xda-developers.com
Just download new firmware, copy the AP file of the new firmware to your phone.
Open Magisk Manager, ensure Magisk is up to date, if not, update it.
When Magisk is up to date, if you have any Magisk Modules running, go into Modules and disable them (no need to uninstall them). Then reboot and go back into Magisk Manager.
Hit the _top_ INSTALL, select INSTALL again then select 'Select and Patch a File'
Locate the new AP file from your new firmware and patch it. Then copy the *magisk_patched.tar* (find it in /sdcard/Download - do not forget to delete it here after everything is done; otherwise Magisk will choke on the next patch) back to your computer, preferably with adb pull to minimize corruption during transfer.
Power off phone and reboot to *Download mode* (switch off, Vol-Down + Bixby and plug USB cable).
Open Odin 3.13.1 or later on your computer, and deselect Reboot under Options tab.
Now use the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do it's stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power, when screen goes off, quickly change to Vol-up, Bixby button and Power.
As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Just re-enable your previously disabled Magisk modules.
Last edited by robbo1947; 2019-08-30 at 04:28.
Alle Bootvorgänge im Überblick, nach der Installation von Magisk:
(Normales Einschalten) → (System ohne Magisk)
(Power + Bixby + Volume Up) → (Bootloader-Warnung) → (Alle Tasten loslassen) → (System mit Magisk)
(Power + Bixby + Volume Up) → (Bootloader-Warnung) → (Haltet nur noch Volume Up) → (Aktuelles Recovery)
Hard Power Off
Volume down and Power/Lock keys on the device for about 10-20 seconds
then it reboots again into recovery menu
last edited by ew 2020-07-07
Be warned though: I had a severe soft brick when upgrading Android 10 to 11 on my S10e!
Half+ day (hard reset did not work, battery had to run out) to get out of the boot loop another two hours to get everything back up running with the help af my backup via restore function of TitaniumBackup.
Yesterday and the day before I had smooth sailing upgrading my S10e and Tablet S7+ using that method as I am used to it since two years.
EDIT: it just worked as expected in UPGRADING my T725 from Android 10 to 11!
Thanks for this. Will give it a go.
I went back to stock firmware from Lineage 18.1 cause I missed the Atmos DSP - couldn't quite get the same effect using JamesDSP - and the finger scanner didn't function.
Stock is mostly ok, but I do miss some root stuff like host file ad blocking and a few other things.
Currently on Stock 11 Rom
shaitan667 said:
I went back to stock firmware from Lineage 18.1 ..... and the finger scanner didn't function
Click to expand...
Click to collapse
The fingerprint sensor works in LOS?
OhioYJ said:
The fingerprint sensor works in LOS?
Click to expand...
Click to collapse
Wasn't for me
shaitan667 said:
Wasn't for me
Click to expand...
Click to collapse
It should, that's something else going on. I use it to unlock / wake my tablet all the time never an issue.
It may have just been an old rom.
I can't go back to LIneage though - the Atmos DSP is just too good.
DHGE said:
Firmware updates and keeping your data, for phones Magisk rooted without TWRP.
[Magisk] Root for the Galaxy S10 Series
Here comes official Magisk support for the Galaxy S10! Let's get Magisk to kick start the development of these Samsung devices! Link to Instructions Carefully read through everything in the page linked above! Follow the instructions closely so...
forum.xda-developers.com
Just download new firmware, copy the AP file of the new firmware to your phone.
Open Magisk Manager, ensure Magisk is up to date, if not, update it.
When Magisk is up to date, if you have any Magisk Modules running, go into Modules and disable them (no need to uninstall them). Then reboot and go back into Magisk Manager.
Hit the _top_ INSTALL, select INSTALL again then select 'Select and Patch a File'
Locate the new AP file from your new firmware and patch it. Then copy the *magisk_patched.tar* (find it in /sdcard/Download - do not forget to delete it here after everything is done; otherwise Magisk will choke on the next patch) back to your computer, preferably with adb pull to minimize corruption during transfer.
Power off phone and reboot to *Download mode* (switch off, Vol-Down + Bixby and plug USB cable).
Open Odin 3.13.1 or later on your computer, and deselect Reboot under Options tab.
Now use the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do it's stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power, when screen goes off, quickly change to Vol-up, Bixby button and Power.
As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.
Just re-enable your previously disabled Magisk modules.
Last edited by robbo1947; 2019-08-30 at 04:28.
Alle Bootvorgänge im Überblick, nach der Installation von Magisk:
(Normales Einschalten) → (System ohne Magisk)
(Power + Bixby + Volume Up) → (Bootloader-Warnung) → (Alle Tasten loslassen) → (System mit Magisk)
(Power + Bixby + Volume Up) → (Bootloader-Warnung) → (Haltet nur noch Volume Up) → (Aktuelles Recovery)
Hard Power Off
Volume down and Power/Lock keys on the device for about 10-20 seconds
then it reboots again into recovery menu
last edited by ew 2020-07-07
Be warned though: I had a severe soft brick when upgrading Android 10 to 11 on my S10e!
Half+ day (hard reset did not work, battery had to run out) to get out of the boot loop another two hours to get everything back up running with the help af my backup via restore function of TitaniumBackup.
Yesterday and the day before I had smooth sailing upgrading my S10e and Tablet S7+ using that method as I am used to it since two years.
EDIT: it just worked as expected in UPGRADING my T725 from Android 10 to 11!
Click to expand...
Click to collapse
I think I followed the instruction but there is no Bixby at S5e, right? After flashing the pathed AP I try to go to Recovery, but it doesn't seem to work. It just boots. If I keep Power+Vol+ pressed it loops ...
So something I do wrong.
Even if I do an adb reboot recovery it boots into Android ?!?
Edit:
I could get it managed by "adb restart recovery". Again I didn't see somewhat like recovery, but after that Magisk is shown to be installed. So it seems not of importance to reboot to recovery DIRECTLY after flashing patched AP, but before you actually want to get Magisk enabled.
Does someone know Vk_Wakelock ? That eats up my battery...
After that update I have problems. It seems that wifi can't find any nets. Looking to Wifi-Mac ... it is empty. Anyone has a tip for me?

Categories

Resources