Database Info

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.

bump

xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.

robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?

Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now

xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.

Root OOS 10.0.1

Hello, i was on android 10 open beta 2 with root
But while upgrading i ran into some complications and now i am on OOS 10.0.1 but dont have root
I tried to install twrp but after pushing through adb the screen says "fastboot mode" and stays there. And after typing fastboot reboot the phone reboots into home screen
I also tried to patch boot image of oos 10.0.1 but it enters into fastboot loop
Any way i can get root?

What happens when you're in fastboot and boot the twrp file?

Phantom Thief said:
What happens when you're in fastboot and boot the twrp file?
Click to expand...
Click to collapse
The whole screen turns black with the words "fastboot mode" in the center

ViperCDX said:
I tried to install twrp but after pushing through adb the screen says "fastboot mode" and stays there. And after typing fastboot reboot the phone reboots into home screen
Click to expand...
Click to collapse
Your description sounds a bit suspicious, like you aren't doing the right method. Or maybe you are not just using the right (precise) terminology. There is a lot of confusion by folks on how to boot/install TWRP properly on this device, so that is why I am pointing this out, and hope you can clarify more specifically so we can then help you.
You don't need to adb push the TWRP.img file to boot TWRP, and you don't "install" TWRP.img using fastboot either. You should be trying to fastboot boot twrp.img, with that img file on your computer.
You do need the Magisk zip on the phone (and adb push is one way); as well as the TWRP installer zip if you intend to install (not just boot) TWRP to the phone. The TWRP installer zip not completely necessary, if you want to just flash Magisk and achieve root (not have TWRP installed on the phone).
Also, are any error messages showing up on your command prompt on the computer, and if so what does it day exactly?
Might be best if you cut/paste your fastboot commands, or post a screenshot of your PC, so we can see exactly what commands you used, error messages, etc.

redpoint73 said:
Your description sounds a bit suspicious, like you aren't doing the right method. Or maybe you are not just using the right (precise) terminology. There is a lot of confusion by folks on how to boot/install TWRP properly on this device, so that is why I am pointing this out, and hope you can clarify more specifically so we can then help you.
You don't need to adb push the TWRP.img file to boot TWRP, and you don't "install" TWRP.img using fastboot either. You should be trying to fastboot boot twrp.img, with that img file on your computer.
You do need the Magisk zip on the phone (and adb push is one way); as well as the TWRP installer zip if you intend to install (not just boot) TWRP to the phone. The TWRP installer zip not completely necessary, if you want to just flash Magisk and achieve root (not have TWRP installed on the phone).
Also, are any error messages showing up on your command prompt on the computer, and if so what does it day exactly?
Might be best if you cut/paste your fastboot commands, or post a screenshot of your PC, so we can see exactly what commands you used, error messages, etc.
Click to expand...
Click to collapse
ok let me try to be as specific as possible.
First i put the "twrp-3.3.1-4-guacamole.img" file in the adb folder and "twrp-3.3.1-4-guacamole.zip" in the internal storage of my phone
Then i switched off my phone, pressed vol up and vol down and power button to enter fastboot mode
i connected my phone to my pc
opened cmd window in the adb folder
typed "fastboot devices" to check if connected
then "fastboot boot twrp-3.3.1-4-guacamole.img"
on pressing enter , i get the 2 ok messages on cmd window and at that point my phones screen goes completely black with "Fastboot mode" written in the center
And stays there that way
now if i type "fastboot reboot" the phone reboots to the home screen
Hope i made it a bit clear
Sorry cant post screenshots at this moment, i am on vacation and dont have my laptop with me

You're using the wrong twrp image. You have to use the one for android q. Unofficial build of twrp for android q is available on the development section. Get that image, fastboot boot twrp.img and then install magisk 20. You don't need to install the twrp zip. You can just boot the image from fastboot whenever you need a custom recovery.
If you absolutely want the recovery, then you can flash it (remember to get the zip for android q) from magisk and then do direct install of magisk then reboot.

kgs1992 said:
You're using the wrong twrp image. You have to use the one for android q. Unofficial build of twrp for android q is available on the development section. Get that image, fastboot boot twrp.img and then install magisk 20. You don't need to install the twrp zip. You can just boot the image from fastboot whenever you need a custom recovery.
If you absolutely want the recovery, then you can flash it (remember to get the zip for android q) from magisk and then do direct install of magisk then reboot.
Click to expand...
Click to collapse
Oh damn, didnt realise that, so silly of me
Will try the android q version and report back

ViperCDX said:
Oh damn, didnt realise that, so silly of me
Will try the android q version and report back
Click to expand...
Click to collapse
Good catch by the previous user, that you need to use an updated TWRP version.
Unofficial version -70 from the following thread is what you want (if you haven't found it already): https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322

redpoint73 said:
Good catch by the previous user, that you need to use an updated TWRP version.
Unofficial version -70 from the following thread is what you want (if you haven't found it already): https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Yeah i pushed the .70 version through fastboot then flashed the installer
And now i have twrp
However when i try to flash magisk zip through twrp, the phone enters into fastboot mode and does not enter home screen
I have to fastboot boot image to get out of it
I have tried magisk 20.1,20 and 19.4
Kindly help

Hello guys please help me if you know what is this? What can I do? it's bug in Android 10.0.1 or something wrong that show me every minute this error?Show me in every minute this Don't want communicate with E4:5F:8D:9C:06:1A.Wait your answer,thanks.

Failed root, stuck on unlocked bootloader warning message.

Hi everyone,
I have tried to get root priviledges following a guide from Droidwin.com to flash Magisk throught TWRP. At the very last step, after flashing Magisk 19.3 throught TWRP when I tried to reboot my phone, it gets stuck on the "unlocked bootloader warning message", which is supposed to disappear after a few seconds and move on to the boot animation.
It seems like I can go to the stock recovery, which shows fastboot and wipe actions. At this point, I can acces the fastboot screen, but the device is not listed using the ADB command "adb devices", nothing is find.
I'm wondering, what can I try to restore the phone ? I thank you in advance for any suggestions.
Here are some additionnal informations:
---Device---
Oneplus nord running OxygenOS 10.5.5, european version.
---What I've done to get in this situation---
Unlock bootloader using ADB
Launch an TWRP image file using ADB
"Try" to root using Magisk 19.3 zip throught TWRP
Power off from recovery (using TWRP touch interface), but the guide tells to click reboot at this step ...
Get stuck on the warning message, not having any boot animation.

Try to boot in Fastboot.
Turn the Nord Off and start it with plus minus and Power.
Boot TWRP with "Fastboot boot "TWRP File name.img" and flash magisk 20.4

Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?

Search forum....
Msm tool oneplus nord wipes phone but fixes any issues

thibdur said:
Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?
Click to expand...
Click to collapse
Plug your phone to your PC while in TWRP, then you can use adb to push files to your phone, for example with adb push magisk.zip /sdcard. Then, flash Magisk in TWRP.

How about flashing stock boot to see if your OPN boots to system again and then simply load Magisk zip to your internal storage and then flash via TWRP?

Thank you a lot for your suggestions !
Here is the solution in my case :
Because fastboot was working, I was able to flash stock oxygen rom, and get every working, but it needs to erase all your data.
You can find a guide on the XDA topic "[ROM][STOCK][FASTBOOT][OPN] Stock Fastboot ROMs for OnePlus Nord". The rom list have the lastest roms version (09/2020), and the process is super automated.
Have a good week-end XDA !

Bootloop on Magisk with Android 11

I made a mistake when upgrading to Android 11 - not giving a single thought to how Magisk would play out.
I had modules like YouTube Vanced and EdXposed installed before upgrading, and now when I try getting a stock boot.img, throwing it in Magisk Canary, and flashing with fastboot, I'm stuck on the G logo with the infinite loading bar.
I'm guessing EdXposed or some other Magisk module is messing me up. If it helps, I screwed with UART and got a log of my phone booting up. Guess I'm doxxing my serial number by giving this out, but here: https://pastebin.com/syEG69T1
Heck, I even tried getting a console from UART, hoping I can just delete /data/adb/modules or something.
I don't want to lose userdata in order to get Magisk. I'd rather wait for the next TWRP release, if it ever comes back. My phone's fine right now with factory images manually flashed without wiping userdata, so this isn't too urgent

While on a stock boot image can't you go into Magisk Manager and remove the modules? Then reroot and put them back in on at a time?

TonikJDK said:
While on a stock boot image can't you go into Magisk Manager and remove the modules? Then reroot and put them back in on at a time?
Click to expand...
Click to collapse
Unfortunately, Magisk Manager is basically useless when Magisk isn't installed, especially since modules are, or at least I'm pretty sure, stored in /data/adb/modules, so I can't get at them without root

Noorquacker said:
Unfortunately, Magisk Manager is basically useless when Magisk isn't installed, especially since modules are, or at least I'm pretty sure, stored in /data/adb/modules, so I can't get at them without root
Click to expand...
Click to collapse
Ok, take a shot with the below. It's all about luck and timing.
connect your phone to your computer (while bootlooping or stuck on loading)
open a command window where you have the platform tools
run the command: adb wait-for-device shell magisk --remove-modules
hold your power button until the phone restarts,
run the command again while the phone powers up
it will restart itself and if you're lucky it will boot properly this time

Hi! After quite a search, i figured out how to fix this. in short:
1. Flash the boot.img from the official image zip to your device and boot up.
2. Hold the power button until the menu comes up
3. Hold the power off button until you get the safe mode message
4. when rebooting into safe mode, hold down the volume down button to get into fastboot.
5. flash your magisk_patched.img
6. the phone will now boot into safe mode with magisk
7. magisk will automatically disable all modules
8. reboot the phone again to disable safe mode
9. after booting, confirm that magisk works
10. remove all disabled magisk modules with the following adb command:
Code:
adb wait-for-device shell magisk --remove-modules
11. the phone will reboot again. Magisk should still work and all modules are deleted.

TonikJDK said:
Ok, take a shot with the below. It's all about luck and timing.
connect your phone to your computer (while bootlooping or stuck on loading)
open a command window where you have the platform tools
run the command: adb wait-for-device shell magisk --remove-modules
hold your power button until the phone restarts,
run the command again while the phone powers up
it will restart itself and if you're lucky it will boot properly this time
Click to expand...
Click to collapse
This didn't quite work. However, it did make my phone forcefully reboot when it was bootlooping, so the command did kinda run
Incanity said:
Hi! After quite a search, i figured out how to fix this. in short:
1. Flash the boot.img from the official image zip to your device and boot up.
2. Hold the power button until the menu comes up
3. Hold the power off button until you get the safe mode message
4. when rebooting into safe mode, hold down the volume down button to get into fastboot.
5. flash your magisk_patched.img
6. the phone will now boot into safe mode with magisk
7. magisk will automatically disable all modules
8. reboot the phone again to disable safe mode
9. after booting, confirm that magisk works
10. remove all disabled magisk modules with the following adb command:
Code:
adb wait-for-device shell magisk --remove-modules
11. the phone will reboot again. Magisk should still work and all modules are deleted.
Click to expand...
Click to collapse
This worked! I'm back in business, thank you for this solution.

Great! You're welcome!

Incanity said:
Hi! After quite a search, i figured out how to fix this. in short:
1. Flash the boot.img from the official image zip to your device and boot up.
2. Hold the power button until the menu comes up
3. Hold the power off button until you get the safe mode message
4. when rebooting into safe mode, hold down the volume down button to get into fastboot.
5. flash your magisk_patched.img
6. the phone will now boot into safe mode with magisk
7. magisk will automatically disable all modules
8. reboot the phone again to disable safe mode
9. after booting, confirm that magisk works
10. remove all disabled magisk modules with the following adb command:
Code:
adb wait-for-device shell magisk --remove-modules
11. the phone will reboot again. Magisk should still work and all modules are deleted.
Click to expand...
Click to collapse
Dude, cheers, thanks!

Sorry, wrong thread...

Incanity said:
Hi! After quite a search, i figured out how to fix this. in short:
1. Flash the boot.img from the official image zip to your device and boot up.
2. Hold the power button until the menu comes up
3. Hold the power off button until you get the safe mode message
4. when rebooting into safe mode, hold down the volume down button to get into fastboot.
5. flash your magisk_patched.img
6. the phone will now boot into safe mode with magisk
7. magisk will automatically disable all modules
8. reboot the phone again to disable safe mode
9. after booting, confirm that magisk works
10. remove all disabled magisk modules with the following adb command:
Code:
adb wait-for-device shell magisk --remove-modules
11. the phone will reboot again. Magisk should still work and all modules are deleted.
Click to expand...
Click to collapse
Hi Incanity,
just want to ask after step9, is that possible to remove magisk modules from Magisk itself?

Question Stuck in boot loop while trying to root using Magdisk help please?

Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.

Hold the power button till it turns off, volume down + power button to get to bootloader. Reflash stock boot.
ALWAYS fastboot boot first before actually flashing in case this happens

Make sure you're using the correct boot image to patch for your build number too

AphoticAffinity said:
Hi all,
I was following the steps to root my pixel 6a using Magdisk I had put the patch boot image on my macbook and then went into fastboot, and then used the command "fastboot flash boot [image]"
I got the okays and then I went to reboot and it's stuck in a boot loop.
I've tried to get into recovery but I just keep getting a splash screen about the device bootloader being unlocked.
Any suggestions? I've tried rescue mode too but it also goes to the bootloader unlocked screen.
Click to expand...
Click to collapse
What version of Magisk did you use? You must use 24.0 or newer.
As @ctfrommn recommended, you can "live boot" the patched image instead of flashing it:
fastboot boot <patched boot image>
If this fails for whatever reason, it'll reboot with the stock boot image.