Related
I was running stock OOS with Android 8.1 with the normal TWRP and Magisk working. When the OOS 9 got out, I installed the full OTA through TWRP (dirty flash) and everything went perfectly, with no problems whatsoever, but I lost TWRP and Magisk, of course.
Now in Android 9 I can't seem to reinstall TWRP (I'm trying with the latest bluespark): I can boot TWRP from fastboot and install Magisk, everything is fine, Magisk works great. However, when I try to install the TWRP zip (through the fastboot loaded TWRP), the phone freezes at the bootloader warning and doesn't boot (and I have to reinstall the full OTA zip to get the phone working again). Or, some other times, it reboots always to the recovery and never to the OS. Any ideas on how to solve this? Thanks in advance.
What version of bluespark are you using ?? v2
Glsoto said:
What version of bluespark are you using ?? v2
Click to expand...
Click to collapse
9.85v2
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
I also tried to fastboot boot blu_spark twrp V2 IMG.... This ended in a black screen. I used the latest official twrp without a problem on pie.
Glsoto said:
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
Click to expand...
Click to collapse
Thanks! Did it in that exact order and now everything works. I was forgetting to reboot the recovery before installing Magisk.
don't flash magisk on the temporary TWRP
Hexyl said:
I also tried to fastboot boot blu_spark twrp V2 IMG.... This ended in a black screen. I used the latest official twrp without a problem on pie.
Click to expand...
Click to collapse
Cuz of kernel panic. When you boot into twrp after fastboot command - unplag your cable from pc when the command is done, then disable mtp, connect to pc and re-enable mtp.
Dont forget to click thanks
And yeah, use blu spark's TWRP, not official one
Came here from google.
Glsoto said:
first fastboot boot twrp.img, the install twrp.zip , reboot recovery and then magisk..
Click to expand...
Click to collapse
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Alekcander said:
Came here from google.
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Click to expand...
Click to collapse
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
jasiorr said:
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
Click to expand...
Click to collapse
You need to Fastboot boot twrp. Img
jasiorr said:
Hi
I have same problem ... after installing twrp i have black scream. twrp doesnt boot
I trying to use this method but cmd give me ]
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I have restored phone with msn download
OnePlus is again unlocked
I have this problem sins i tried to install magisk and after reboot my op doesn't boot to OS with crash error
any ideas ?
Click to expand...
Click to collapse
yldlj said:
You need to Fastboot boot twrp. Img
Click to expand...
Click to collapse
Alekcander said:
Came here from google.
This procedure didn't work for me, for some reason "fastboot boot twrp.img" was leading to black screen.
What worked for me was
1) Boot to fastboot
2) fastboot flash twrpXXX.img
3) Without rebooting, select recovery from fastboot's bootloader menu
4) If you are able to boot in twrp this time, then flash blu spark twrp.
5) Reboot
6) Try to reboot in recovery as usual
If all worked well, you should see twrp recovery.
Cheers.
Click to expand...
Click to collapse
I have the same problem as Alekcander
When I try to use command ,, fastboot boot twrp-xxx.img nothing happens. I mean mobile restart as always but there is only black screen and notification diode shine white ...
Also Alekcander method doesn't work:
C:\Android>fastboot flash twrp-3.3.1-x_blu_spark_v9.101_op6.img
unknown partition 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
error: cannot determine image filename for 'twrp-3.3.1-x_blu_spark_v9.101_op6.img'
I tried official twrp and is the same , I tried to disconnect from usb when mobile is restarting also nothing ...
so again ... I have restored phone with msn download -> unlock bootloader...
i have this issue sins i tried to install magisk and after reboot my OP6 doesn't boot to OS and give crash error
any other ideas ?
Solved I have to update system to more recently version. Why twrp doesn't work with oxygen is 5.1.5 ?
Helloguys and gals,
I just got a Pixel 3 and wanted to root it. I followed this guide: https://www.youtube.com/watch?v=BgV1xxkcBk8
I installed the latest TWRP recovery (didn't keep it read only, maybe this was a mistake?). After that I installed Magisk which was followed by a bootloop.
To fix the bootloop I used TWRPs fix bootloop fix which worked. But that makes Magisk undone.
So my Questions is how to install Magisk? Do I need to flash the stock image on both slots and start again? Is the guide outdated? If so, which guide should I follow?
Edit: My phone is still on the update from November 2018.
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot
bafforosso said:
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot
Click to expand...
Click to collapse
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance
I run twrp as the devices recovery and have magisk. I would follow the twrp and magisk guides for this device. First boot twrp then use the installer, second reboot, third get to recovery and flash magisk. The boot partition needs to be rebooted before root. It is an initialization thing. Get twrp, reboot, magisk.
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?
levibuko said:
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance
Click to expand...
Click to collapse
I tinker a lot with my phone so I usually want to have both slots clean flashed when I start back from scratch, not sure that is really necessary, but here are the steps I use for flashing both slots :
Code:
fastboot getvar current-slot
./flash-all.sh
fastboot --set-active=x (x being a or b, the other slot than the one you get with the fastboot getvar command)
./flash-all.sh
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------
tenthousandfeet said:
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?
Click to expand...
Click to collapse
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
wangdaning said:
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
Click to expand...
Click to collapse
Tried that. No success.
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.
wangdaning said:
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.
Click to expand...
Click to collapse
I had a similar thought, but no dice. Tried installing Magisk 19.2, which boot looped just like the latest 19.3.
I even went back to 16.7, and though that one didn't boot loop it also didn't show up in the system. Magisk Manager didn't recognize it, anyway.
Though I'm loathe to do a full wipe/reset and then reconfigure all my junk, I may be headed in that direction as I'm running out of other ideas. Perhaps I'll save a backup just before that I can return to if the reset is fruitless.
---------- Post added at 07:53 AM ---------- Previous post was at 07:36 AM ----------
Magisk 18.0 does the same as 16.7 - no bootloop, but no root.
Interestingly, I noticed that the 18.0 and 16.7 zip installers say something about the partition being boot_a, whereas the bootlooping 19.2 and 19.3 zip installers say it's boot_b.
Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.
sliding_billy said:
Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.
Click to expand...
Click to collapse
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.
sliding_billy said:
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.
Click to expand...
Click to collapse
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.
tenthousandfeet said:
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.
Click to expand...
Click to collapse
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.
tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
Please update when/if you find a solution. We are both in the same boat.
I'll let you know if I get anything working.
sliding_billy said:
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.
Click to expand...
Click to collapse
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.
tenthousandfeet said:
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.
Click to expand...
Click to collapse
It still looks like your boot slot ended up the one you had tried already (b), since you changes to a and ran flash-all, changed back to b and ran flash-all and rebooted. As for the old platform tools, that could definnitly have an impact on running the fastboot of the patched boot. Other than that, I think a flash-all with the -w is the only approach left.
I'm also in the same boat. I've tried all the various install methods, and done the double "flash-all" on both slots, and no matter what, it ends in a bootloop.
Haven't tried the -w yet so I'll be interested if anyone gives that a go. Until then I'm dying with no root
Hello guys, as we known that it is unable to use command in fastboot to boot into TWRP if we are on Android 10 (both OOS and Custom rom) at the moment, so here is the simple command allow us to do that if you want to roll back android 9 or any rom by TWRP
fastboot flash boot_a <twrp name.img>
fastboot flash boot_b <twrp name.img>
fastboot reboot
Your phone will automatically boot into TWRP, so you can flash another rom
Can anyone confirm this works?
I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it.
I would try again, but I'm on a critical work trip until the end of the month, so my phone's uptime is expected to be 100% until then.
worked for me while anything else didnt
LazerH said:
worked for me while anything else didnt
Click to expand...
Click to collapse
Does it wipe your data?
Didn't work for me. My boot image was patched already this is probably why.
ok, I tried this, but as reported above, now also stuck on this same: "I tried something similar when I first installed OOS 10, and I successfully booted TWRP, but I ended up getting a bootloop (stuck at the g.co/ABH warning thing) when I rebooted to system. I don't know if I did something wrong, or flashing twrp to both boot partitions caused it."
How do I resrore operation for my phone? (help?)
Well, I met this issue before, and ended up with using this method to successfully boot into twrp.
This issue seems to appear on OOS, when I using `fastboot boot xxx.img` on other ROM like omni, I'm able to boot into twrp, thanks!
can someone help me please. my phone is stuck in a fastboot bootloop. everything I try doesn't work.
fastboot boot TWRP.img NOTHING
tried your solution above and still nothing
Still stuck in fastboot this is what I get:
PS C:\Users\Les Brown\Desktop\OnePlus 6> fastboot boot twrp-3.3.1-17-enchilada-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 0.617s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.655s
@killathenoob Download DECRYPTED OOS 10.3.0 with this help if you don't really know what to do with this.
For others people (and you if you want to root or just install TWRP after fresh OOS10 Decrypted install) don't forget to OEM unlock before doing anything.
Download this
Copy "twrp-3.3.1-17-enchilada-installer-mauronofrio.zip" into internal storage of your OP6
Power it OFF
Power it ON in fastboot mode
Launch "Boot TWRP.bat"
Connect your OP6 to your PC and wait for TWRP to boot
Install twrp-3.3.1-17-enchilada-installer-mauronofrio.zip
Reboot to recovery and install magisk if you need to.
Source
Hope I helped a bit.
Hi everybody,
I tried to update my OOS to Android Q while keeping magisk, there was probably a module not compatible that I forgot to remove before and I could not access the interface after rebooting.
Trying to restore the stock boot.img with fastboot, now I am stuck on the "Boot Loader is unlocked" warning page and the phone refuses to boot.
I tried to wipe everything using fastboot -w but still can't boot normally, if anyone can help me solve this please, I would be grateful.
Regards.
Try flashing the unofficial TWRP for Q from here
You can follow that guide but don't install Magisk, then after successful boot, try flashing Magisk uninstaller in TWRP.
Can try flashing android 10 boot.img from #2 link.
this happened to me. It was because I had the usb pluged. If you take the usb out it will boot. Or at least mine worked that way.
What I did was completely restoring the device by flashing a fastboot ROM then updating to Q again. SO I've lost all my data.
Do you know any way I can root android Q actually ?
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
danecr7 said:
Hi everybody,
I tried to update my OOS to Android Q while keeping magisk, there was probably a module not compatible that I forgot to remove before and I could not access the interface after rebooting.
Trying to restore the stock boot.img with fastboot, now I am stuck on the "Boot Loader is unlocked" warning page and the phone refuses to boot.
I tried to wipe everything using fastboot -w but still can't boot normally, if anyone can help me solve this please, I would be grateful.
Regards.
Click to expand...
Click to collapse
If you have access to fastboot then you can flash twrp and do below steps exactly else you will stuck at bootloader warning message
Reboot to fastboot mode. Flash TWRP img using the following command--> Oneplus blocked fastboot boot command
Code:
fastboot flash boot twrp-******.img
From fastboot mode, reboot directly to recovery mode. Now you have a working TWRP. (If you already have Magisk earlier, flash Magisk uninstaller now before proceeding to the next steps)
In TWRP, flash the stock boot image in boot partition. Don't reboot .
Flash TWRP installer zip then reboot to recovery. You now have a fully working TWRP in OOS 10. . Don't reboot .
Flash Magisk v20.1. Reboot to system.
Merry Christmas guys,
I have a really unusual situation.
First time that I have tried all tricks I know and I can't get myself out of this difficult situation.
I was trying to update Magisk with a patched boot file and after a reboot I was not being able anymore to access the system but only this black screen with the Crashdump Mode is appearing.
I can access the Fastboot screen, but no way to reboot to the TWRP recovery or to flash another boot.img, even through some pc flashing utilities.
Is there anything to try through another slot or something else?
I also tried:
fastboot flash boot_a boot.img
and I get this error:
FAILED (remote: Flashing is not allowed for Critical Partitions)
But my bootloader is unlocked and other commands like fastboot reboot works normally.
After I flashed through fastboot the images of boot, abl, dtbo, fw I can only access the TWRP recovery where everything is decrypted.
Any other ideas?
Try booting temporary into TWRP by using this command
fastboot boot twrp.img
If you can't use MSMDownloadTool