Database Info

adb problem

hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?

When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"

Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?

well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?

ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian

Did you do fastboot flash boot imagename or fastboot flash recovery imagename

runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this

ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)

If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed

redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing

If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.

Stuck in Bootloop when installing Magisk

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

Flash TWRP via fastboot android 10

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.

Unable to flash TWRP. Lost Recovery, OS and only have unlocked bootloader.

Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks

Arnavzz said:
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Click to expand...
Click to collapse
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk

Kaleshwar said:
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks

Arnavzz said:
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Click to expand...
Click to collapse
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk

Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip

chintu1234 said:
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
Click to expand...
Click to collapse
This doesn't work. It flashes successfully but when I select Reboot Recovery and press the power button, it boots back to the bootloader.

Maybe wrong twrp img
Try the older 3.3.1-12 twrp.img and then try
Also try the following as well
Fastboot flash boot_a twrp.img
Fastboot flash boot_b twrp.img
And try just reboot not reboot to recovery

Kaleshwar said:
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?

Arnavzz said:
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Click to expand...
Click to collapse
You can try it . Looks pretty solid.
Sent from my ONEPLUS A6003 using Tapatalk

Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853

I had similar situation last evening.
I made the mistake of having a factory reset on rooted 9.0.8 and then trying to flash the 10.0.1
I got the same error, so I had to connect my mobile to my laptop, fastboot to the newest TWRP, flash the TWRP, flash the 9.0.9, flash the 10.0.1, flash magisk 20.x and then everything was working.

xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules
Update through local update 10.3 or current ROM
Reboot
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img - ( https://androidfilehost.com/?fid=4349826312261678088 )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP ( https://androidfilehost.com/?fid=4349826312261678087 ) or Blu zip (https://github.com/engstk/op6/releases/download/r112/blu_spark_r112-oos_op6-op6t_0dd5f9228.zip)
5. Reboot to recovery
6. Flash Magisk 20.1 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://drive.google.com/file/d/1w44cUg815g-H1h_6gObUVPLDTc_dtiMX/view
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
This worked for me.. Finally. PS - I did in a slightly different order. I installed twrp first, booted into twrp, made sure I was in slot A. If I wasnt, I rebooted to recovery. If I still wasnt I set slot to A manually then rebooted to recovery again. Flashed the stock boot img you linked to boot, then rebooted to recovery slot b (same process I did to get to slot a) then flashed the stock boot img to boot again THEN finally installed magisk. Booted to system, where it hanged a bit, rebooted before getting into android, but booted in just fine after that..
For some reason if you don't flash stock img to slot A (and maybe slot B too, I did this for good measure) before installing magisk everything dies a horrible death and breaks, which can't even be recovered from /boot /system backups..
EDIT: Tried to reboot into recovery, which reverted back to stock for some reason after doing the above steps. So I proceeded to install the bluspark recovery, rebooted into recovery, made sure I was in slot b, made a back up of the boot image, then flashed bluspark kernel. Got stuck at the unlocked bootloader screen. Rebooted into recovery, restored my /boot back. Still stuck when I try to boot into system. Fixed it by booting back into recovery in slot A flashing stock boot img, then into slot b stock boot, then magisk, but also installed bluspark kernel here because I had a feeling I would lose twrp from flashing to stock boot img, and that the issue was caused by twrp (both twrp-3.3.1-16-enchilada-installer-mauronofrio and twrp-3.3.1-x_blu_spark_v9.108_op6 have this issue). Guess what? Turns out I was right. Having twrp breaks everything after you install magisk, so you need to flash the stock boot img before flashing magisk for some reason.. and cant install twrp again unless you dont mind bricking your phone.
EDIT2: F2FS works, just boot into recovery via fastboot (this should be slot b), change /data to f2fs, boot back into fastboot then into recovery again by fastboot (slot b again), flash stock boot img > magisk > bluspark kernel > f2fs_fstab.zip > f2fs_optimize.zip > factory reset/wipe (from twrp before rebooting), done just reboot into system. You of course lose twrp because magisk doesnt like twrp on oos 10.x for some reason, and will need to set everything up again to cause of the wipe. If you dont factory reset/wipe from twrp before booting into system your system will crash and reboot every time you boot into android, then have to do all the steps I listed again.
EDIT3: Never mind, I was wrong, f2fs makes almost all your apps and storage unusable. Not sure if it's cause of the rom (OOS10.3.0) or because we have to flash stock boot.img and get rid of twrp before booting into system. Either way, f2fs has never really been stable or fun to get working so better to stick to ext4.. that few percent performance boost isnt worth it.
EDIT4: This is my last update. After experimenting with different things, bricking my phone, restoring it via fastboot rom, many many times, I've verified the simplest and cleanest way to install magisk.. Do note you wont be able to keep twrp.
Method A - If you already have twrp
Boot recovery into slot a, flash your rom's stock boot.img, then boot into your recovery in slot b (dont boot into slot a recovery because slot a wont have twrp anymore), flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot boot into system. That's it.
Method B - If you don't have twrp
Boot into fastboot, and from your cmd/terminal run fastboot flash boot yourtwrp.img (I suggest Mauronofrio's twrp-3.3.1-16-enchilada-Q-mauronofrio.img or newer). Use your volume buttons to select boot into recovery. Make sure your active slot is B, (if it isnt, install twrp (bluspark and Mauronofrio's twrp both work great) by zip, then follow the steps above in method A). Once you've verified you're in slot B flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot into system. That's it.
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.

not working
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....

gauravkapoor99150 said:
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
Click to expand...
Click to collapse
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk

RASTAVIPER said:
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
sir can you send me a link

lemon07r said:
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
Click to expand...
Click to collapse
@mauronofrio wrote the following in his TWRP thread a while ago:
So little update, after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now.
There are not problems on Android Pie, if you need of the twrp on android Q just flash in boot partition the Q .img (fastboot flash boot twrp.img) and then reboot from fastboot in recovery. Before publishing the twrp I had not tested magisk and twrp together.
On Android 10 use only magisk 19.4
Click to expand...
Click to collapse

xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
Basically worked for me, too, with 2 exceptions:
- this tool to remove magisk modules etc. wouldn't be flashed, always ended in an unnamed error; probably the cause for some other problems?
- flashing boot.img (V 10.3.4 from this thread) didn't work for me, I always ended up in twrp's splash screen
- got it solved by dirty flashing the full V 10.3.4 ROM (again from the above thread)
Many thanks once again!

Fastboot wrong command entered and now phone won't boot into anything but fastboot/stock recovery!

Hi , I just screwed up when I was trying to flash TWRP recovery on my OnePlus 7 Pro. I accidentally wrote "fastboot flash boot twrp.img" instead of "fastboot boot twrp.img" and now my phone wont boot into anything but the bootloader. How can I fix this issue? Thanks heaps!
Edit: Ok, it looks like I need the boot.img from stock firmware. Could someone provide that for me? My download speed is super slow (like less than 100 KB/s) so downloading the stock firmware is gonna take me 7 hours D: (Yay for living in the middle of nowhere!!)

fastboot boot twrp.img shouldn't have messed anything up. That should just have booted the recovery without installing it, and this is the command you should use.
If you want help getting the boot image you should probably post what build and version you are using, since there are quite a few to pick from.

Didgeridoohan said:
fastboot boot twrp.img shouldn't have messed anything up. That should just have booted the recovery without installing it, and this is the command you should use.
If you want help getting the boot image you should probably post what build and version you are using, since there are quite a few to pick from.
Click to expand...
Click to collapse
Well my phone won't boot now, so it did something wrong haha :'( When I go fastboot boot twrp.img, the phone hangs on it's splash screen of the 1+ logo, with powered by android at the bottom.
As for build, I think it was the latest version out 11.0.0.2.GM21AA, thank you!
Also, typing fastboot flash boot twrp.img then trying to reboot to recovery just takes me back to the stock bootloader, so I don't know what's going on there :\
Also, fastboot gives this as it's outupt about why it can't flash twrp to the phone, using fastboot flash recovery twrp.img:
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')

Aqyx said:
Well my phone won't boot now, so it did something wrong haha :'( When I go fastboot boot twrp.img, the phone hangs on it's splash screen of the 1+ logo, with powered by android at the bottom.
As for build, I think it was the latest version out 11.0.0.2.GM21AA, thank you!
Also, typing fastboot flash boot twrp.img then trying to reboot to recovery just takes me back to the stock bootloader, so I don't know what's going on there :\
Also, fastboot gives this as it's outupt about why it can't flash twrp to the phone, using fastboot flash recovery twrp.img:
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
Click to expand...
Click to collapse
I feel your pain on download speed. Took me two tries, finally had to zip it I will try to upload boot.img for op7p 11.0.2.1, OnePlus7ProOxygen_21.P.38_OTA_0380_all_2107172338_49e62 build which I believe is the latest. Use at your own risk. It would be good to know for sure what build you're on.

Phoenix 15 A said:
I feel your pain on download speed. Took me two tries, finally had to zip it I will try to upload boot.img for op7p 11.0.2.1, OnePlus7ProOxygen_21.P.38_OTA_0380_all_2107172338_49e62 build which I believe is the latest. Use at your own risk. It would be good to know for sure what build you're on.
Click to expand...
Click to collapse
Thank you mate!