Hello, i'm panicating since I made a HUGE MISTAKE.
Some timee ago I unlocked my boot loader, installed twrp and susseffuly root with and old magisk version.
Now With my OOS 11.1.2.2 I tried to restore Magisk root.
I successfully installed TWRP, I still can enter in its recovery mode.
I followed this guide to install magisk again, but I'm so fool I used twrp .img as boot image as magisk_patched_img.
I used fastboot flash boot with that files and now my phone is locked in bootloader
I downloaded oos 11.1.1.1 image from here and used again fastboot flash boot... but still my phone is locked...
Now I can't enter TWRP anymore
There is a way to restore its boot?
Seems I found a way to use again my phone. In the oos 11.1.1.1 thread at post #23 there is a patched 11.1.2.2 image.
Since I was able to go in fastboot I flashed again the boot with 11.1.2.2 patched image.
Now I can power up my phone again, but the startup process is really SLOW than before. Is this an issue since I used OP6T patched image instead of OP6?
Related
it freezes the phone then it boots back into the OS.
I noticed that it takes a bit of a long time (0.6 minutes) to patch the boot image but it ends up successful.
Before this, I unlocked the bootloader on my phone which was on Android 8.0.0 October 2017, then I OTA updated it to Android 8.0.0 November 2017 using the recovery mode.
Also, right after I unlocked the bootloader, I tried to flash the November full system image but it didn't work and returned the error "could not create userdata" or similar, and it threw a lot of missing .sig errors.
The OS all works fine and it still boots into it, just I have no recovery mode now.
I used https://www.youtube.com/watch?v=FcgCrmL8xfE to flash the latest TWRP.
I verified the hashes of all the files too, no luck.
What can I do to fix the issue?
UPDATE: I was trying TWRP 3.2.3-1, I also tried 3.2.3-0 which failed then I tried 3.1.1-1 which didn't change the recovery mode at all, it just returned errors when I was in the temporary TWRP boot.
I'm curious why you want a one year old version of the ROM, and not the most recent version. In any case, you should be able to download the full factory image, then extract the boot.img file. Use fastboot to flash the boot.img to your phone using
Code:
fastboot flash boot boot.img
After that, you should be able to boot to system fine, and you should also be able to boot from the TWRP.img file fine. Always use the latest version of TWRP. Specifically for the Pixel phones, version 3.2.3-1 of TWRP is the first version which successfully unlocks phones with a pattern unlock.
So I used msm tool to go back to 9.5.3 to unbrick my OP7 Pro and then updated the firmware to 9.5.4 because apparently TWRP fails on adb unless you go to firmware 9.5.4 or above I believe. So I did adb commands and did the TWRP I'm file and booted into TWRP just fine. Then adb sideloaded and flashed TWRP zip file and TWRP sticks fine until I go back into recovery and flashed the magisk beta 20 version and 19 does the same thing. After I flashed magisk zip hell breaks loose. Literally TWRP won't stick unless I go back to adb and do fast boot then twrp.img file and force it to show up even then if I were to adb sideloaded it again and flash the TWRP zip again and see if it sticks without flashing magisk it still will not hold. I don't understand what is happening. I just want to get my OnePlus 7 pro with magisk and working g TWRP without any troubles at all. Should I update it to a different firmware or is the magisk or TWRP files I downloaded wrong what is the deal???? TWRP is the 3.3.4 or whatever and so is the img file and magisk is 20 version please let me know the solution it makes no sense to me. I have to keep msm unbricking back to 9.5.3 and it's pissing me off.
You got two ways:
- flash TWRP
- Boot to TWRP
- flash Magisk (DO NOT REBOOT)
- flash TWRP again (use the TWRP installer zip always)
Or...
- Flash TWRP
- Flash Magisk
- Boot device
- Flash TWRP installer as a module in Magisk
Didn't work
I tried all methods stated above and none of them are confirmed working on 9.5.4 Could you confirm it working on that firmware please? I just flashed twrp zip 3.3.4 file through magisk no luck and magisk is no longer rooted now with twrp... I'd have to run adb command and fastboot boot twrp.img to get twrp to come back and reflash magisk now... However that means twrp will still not stick at all. Which doesn't make sense. If you get it working on this firmware please let me know because I've been trying to get both to stick for awhile now. I did get it to work on another firmware but I couldn't remember which one... But technically it should work on firmware 9.5.4 because that is the firmware that supports adb commands where as 9.5.3 does not. This is gm-1917 model global/US 9.5.3 is the first firmware it comes with.
Want to chime in here and add I have the GM1915 and I have the same issue even after following the above steps. I've updated and used the MSM tool multiple times but TWRP never stays on the recovery, in fact, I usually find the OEM recovery to be gone completely after flashing so if I attempt to boot to recovery it just sends me to my bootloader.
Bump
Hello guys, i installed 10.0.2-GLOBAL-OnePlus7ProOxygen_21.O.22_OTA_022_all_1911070323_2b888-FASTBOOT using flashall.bat. Then i patched its boot img using magisk manager.
Then i fastbooted that patched boot image and rebooted my device. After that i had root, however when i restarted my device it got stuck in fastboot mode. I tried fastbooting that patched image again but its still stuck in fastboot mode
Any help appreciated
What version were you on before installing the fastboot 10.0.2? Because I am pretty sure the fastboot options aren't meant for upgrading, just meant for fixing any issues you have while already on that version. If you can get it to boot up, I would use oxygen updater to upgrade with a full download to 10.0.3.
Do you have any magisk modules enabled right now? Do you have TWRP working on your device?
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.
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.