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.

Can't fastboot boot TWRP

So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,

Ph0enix_216 said:
So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,
Click to expand...
Click to collapse
With MSM tool your oneplus 6 is locked again...Maybe you should look if bootloader is locked!

Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp

whizeguy said:
Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp
Click to expand...
Click to collapse
My bootloader is unlocked. Still can't get into TWRP.

Ph0enix_216 said:
My bootloader is unlocked. Still can't get into TWRP.
Click to expand...
Click to collapse
Did you enable debug?

Sounds like you may have the active slot set to an unbootable OS. Check the active slot with fastboot getvar all, then use this to change to the other slot.
fastboot --set_active=[a or b depending on which is inactive]

Was this the end of this? I'm in the same boat. I was recovering from a google account remove device wipe and so I went to restore my TWRP back-up and it succeeds so I reboot. Device is bricked into fastboot mode only. So I msm restore and boot system, enable debugging, unlock bootloader, still can't get into TWRP or versions that worked before, just that taunting blue light.. I found this and changed my active slot but the issue is the same and I'm kind of at a dead end, any help would be appreciated. I can boot into 5.1.5 OOS and stock recovery fine.

Nevermind I had to incrementally update the ROM

angelsenvy said:
Nevermind I had to incrementally update the ROM
Click to expand...
Click to collapse
You can download both twrp zip & img from here: https://drive.google.com/drive/folders/1bnGBrkL5XE3yt7DmIRSDD2v4J6MzFOsH?usp=sharing
fastboot flash boot twrp-3.4.0-1-enchilada-Q-mauronofrio.img instead of fastboot boot .
That will work

TWRP error: Unable to open /system_root/system/apex

In last working condition, my phone is the TMO branded device, converted to global 10.5.11 with Magisk and TWRP.
I decided to update to 10.5.12 via Local Upgrade, as I've done previously to update. The OOS update went fine but I encountered an issue when updating Magisk to 21.4. After attempting to install to inactive slot and reboot, my phone went into QualComm CrashDump mode. Attempting to boot into TWRP or the system resulted in being thrown back into CrashDump mode. I could still get to fastboot, so I booted TWRP from fastboot and was able to at least recover my device into a working state; albeit not how it should be working. I am currently on TMO ROM fresh from msm restore, 10.5.7.IN55CB, bootloader unlocked. Phone works, signal good, IMEI good, can receive texts, etc.
From that point on, no matter if I msm back to T-Mobile firmware, flash the Global fastboot ROM, factory reset, etc I'm getting an error I can't seem to find any hits on while searching.
"Unable to mount storage
E: Unable to open /system_root/system/apex
E: Unable to load apex images from system/apex"
I'm assuming I messed up my slot_b because prior to using the msm tool, if I tried to boot from slot_b it would send me to CrashDump mode while attempting to boot from slot_a directly after attempting slot_b would send me into stock recovery mode where I could do a factory reset and successfully boot into the system. After attempting a factory reset (and format data) via TWRP I then was being sent to CrashDump mode by trying to boot from either slot or trying to enter recovery mode. When first attempting to msm, holding vol+ and plugging device in would send phone to EDL mode where it would stay for a few seconds, then reboot into CrashDump Mode. I didn't think I was getting into EDL mode, but once it showed connected in the msm tool I quickly hit start and the restore process started.
While typing this, I tried to update magisk by installing to the inactive slot (which would be slot_b) and upon reboot I went straight to fastboot. I got the message included in the 2nd image attached.

Hi there. MSM back to stick. Funny ways your time logging in to Google it anything. Murray let the phone after up. Take the OTA to current firmware 10.5.23 I think. Then bootloader unlock and flash global. Happy modding!

Nathan.7118391 said:
Hi there. MSM back to stick. Funny ways your time logging in to Google it anything. Murray let the phone after up. Take the OTA to current firmware 10.5.23 I think. Then bootloader unlock and flash global. Happy modding!
Click to expand...
Click to collapse
So taking the OTA on T-Mobile firmware is the part I'm missing? Because I've went back to stock with MSM, and I've took the OTA on global firmware (just not to 11.x) and problem persists

lordcheeto03 said:
So taking the OTA on T-Mobile firmware is the part I'm missing? Because I've went back to stock with MSM, and I've took the OTA on global firmware (just not to 11.x) and problem persists
Click to expand...
Click to collapse
Yup, I always take the TMO OTA then bootloader unlock and global flash. If not then try another global file. Happy modding!

Nathan.7118391 said:
Yup, I always take the TMO OTA then bootloader unlock and global flash. If not then try another global file. Happy modding!
Click to expand...
Click to collapse
So I reverted back to TMO stock with msm tool, updated TMO firmware, unlocked BL, booted to fastbootd and ran the flashall.bat in 10.5.7 Global firmware... it all was going fine until it needed to reboot... it went to Qualcomm CrashDump mode... Slot B is buggered. I hold both vol buttons + power until it turns off, then do it again to enter bootloader mode. fastboot boot twrp.img and it takes me to twrp where I can toggle the boot slot back to a (I can't do fastboot set_active b from fastboot, it just throws up the fastboot help) and I can boot back into recovery.
The msm tool and global fastboot ROM I flashed is the same one I initially performed the conversion with when I first got the device. Even when on slot_a I am still getting the errors in the first picture I attached in OP; slot_b still gives me the errors posted in the 2nd picture.
edit:
I reverted with msm one more time, followed through the process to convert to global (minus taking the OTA first) and now it's flashing the global firmware. It successfully rebooted as it's supposed to do and it continued the install. On system.img, vendor.img, and product.img so far it has said "invalid sparse file format at header magic" then "resizing system_a" etc for all the partitions mentioned... but no, slot_b is still dead.
I see that the script flashes, say vendor.img but it says vendor_a... Can I manually do it through fastboot (or edit the flash all.bat) to flash to slot_b instead of a?

lordcheeto03 said:
So I reverted back to TMO stock with msm tool, updated TMO firmware, unlocked BL, booted to fastbootd and ran the flashall.bat in 10.5.7 Global firmware... it all was going fine until it needed to reboot... it went to Qualcomm CrashDump mode... Slot B is buggered. I hold both vol buttons + power until it turns off, then do it again to enter bootloader mode. fastboot boot twrp.img and it takes me to twrp where I can toggle the boot slot back to a (I can't do fastboot set_active b from fastboot, it just throws up the fastboot help) and I can boot back into recovery.
The msm tool and global fastboot ROM I flashed is the same one I initially performed the conversion with when I first got the device. Even when on slot_a I am still getting the errors in the first picture I attached in OP; slot_b still gives me the errors posted in the 2nd picture.
edit:
I reverted with msm one more time, followed through the process to convert to global (minus taking the OTA first) and now it's flashing the global firmware. It successfully rebooted as it's supposed to do and it continued the install. On system.img, vendor.img, and product.img so far it has said "invalid sparse file format at header magic" then "resizing system_a" etc for all the partitions mentioned... but no, slot_b is still dead.
I see that the script flashes, say vendor.img but it says vendor_a... Can I manually do it through fastboot (or edit the flash all.bat) to flash to slot_b instead of a?
Click to expand...
Click to collapse
OP said sparse magic invalid is fine and won't hurt anything. If you are having trouble booting the phone then I suggest you wipe data. That's what's I had to do in order for it to work. Though the first few times I did it I didn't wipe any data and it worked just fine. I think OP said you can modify the script if you know what you're doing. Happy modding!

Nathan.7118391 said:
If you are having trouble booting the phone then I suggest you wipe data.
Click to expand...
Click to collapse
When you say wipe data, do you mean how, like, when you use msm tool data gets wiped? Or maybe you mean how data gets wiped when you unlock bootloader? Perhaps you mean like the flashall.bat wipes data as well...
I'm almost certain it's slot_b, I just need to know how to repair slot_b

Did you ever figure this out? I have a list of problems that all started with the exact problem your having now here

i'm getting same error again and again, can you help me to troubleshoot this. ASAP

Oneplus 6 and magisk (stuck in fastboot )

hi guys,
my op6 is running stock oos with magisk as root. My phone worked fine for several months. Today I tried switching magisk from the stable version to canary by first upgrading the manager app and then hitting the direct install option. This failed several times and I got an error saying:
! Unable to unpack boot image
I thought this could be fixed by a reboot, but well... it wasn't. Now the phone only boots into the bootloader. I booted into twrp and tried to uninstall magisk via the uninstall.zip. This fails with error
-Unpacking boot image
! Unsupported/Unknown image format
- Unmounting partitions
cd /tmp/repackorig/ && /sbin/magiskboot unpack -h '/tmp/repackorig/boot.img' process ended with ERROR: 1
Error unpacking image
I don't really know what this means. I'm guessing my boot.img is corrupted?
Is there any way I can solve this problem without a factory reset? Can I just flash the stock boot.img via fastboot?
Do you have any idea what went wrong here, so that I can avoid the error next time?

Yesterday I broke op5 during the magisk update. The repair was simple, flash stock boot.img as boot partition.
I flashed it from TWRP.

Try dirty flashing your ROM without flashing magisk.

I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?

MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?
Click to expand...
Click to collapse
Maybe it's worth trying change the slot and see if it will start? Of course from the fastboot level.

MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Click to expand...
Click to collapse
I managed to fix it as well by flashing the stock boot.img for my software version to both slot_a and slot_b using fastboot. I left the active slot setting alone otherwise.
Afterwards I booted into twrp through fastboot and installed blu spark twrp and magisk 21.4 from there as a user suggested on the Magisk github: https://github.com/topjohnwu/Magisk/issues/3924
Note that github link also has a solution to flawlessly upgrade to latest Magisk without data loss but I haven't had the time to look at it.

[Help] OP7Pro only boots to Bootloader, not detected by Fastboot

As the title says, my OnePlus 7 Pro now only boots to the Bootloader and it isn't detected by Fastboot on my PC. I recently extracted a boot.img from the latest (10.3.8) OOS firmware, patched it with magisk, then flashed in TWRP and booted to system. I realized I forgot to reinstall TWRP so I flashed its installer in Magisk Manager then directly installed Magisk. This may be the reason why I can't boot anymore... I most likely can use EDL and MSM to restore (hadn't tried it yet), but I rather save that as a last resort since I really don't want to wipe my device. I've already tried installing a bunch of adb and oem drivers to no avail. Is there a way to use EDL to boot a twrp.img, perhaps?

Well turns out it was a driver issue. Installed proper drivers and got fastboot to work again. Booted TWRP and dirty flashed stock firmware, TWRP and Magisk.