Database Info

TF300T 4.2 TWRP Error

Hi XDA,
I am a complete noob, and this is my first time posting, so bear with me.
Some time ago I rooted and unlocked my TF300 with SuperSu. Recently I wanted to upgrade to 4.4 kitkat. However, my Tablet was stuck at Andriod 4.1 because of the the unlock.
I went to manually update my TF via the Asus website. I installed the 10.6.1.8 using my TWRP 2.5, and Oem 4.1 OS. Installation worked just fine. After install, I booted up and I had 4.2 with everything working correctly.
Next step was to install TWRP 2.7.0.1. I reset my TF and went into RCK to see something went wrong when updating.
My TWRP will not load, and I get the Android on his back with the red triangle when I try to enter RCK.
Thanks in advance!!

I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.

TallMilk said:
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
Click to expand...
Click to collapse
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.

cmendonc2 said:
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
Click to expand...
Click to collapse
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks

TallMilk said:
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
Click to expand...
Click to collapse
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.

You are amazing. I will give it a try tonight and report back!

cmendonc2 said:
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
Click to expand...
Click to collapse
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.

TallMilk said:
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
Click to expand...
Click to collapse
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.

cmendonc2 said:
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
Click to expand...
Click to collapse
Awesome! Worked like a charm. twrp 2.7.0.1 installed perfectly.
Then I tried to flash the cyanogenmod. Said it installed fine, but it just gets stuck on the loading screen...

I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?

SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.

TallMilk said:
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
Click to expand...
Click to collapse
Damn, so I'm screwed. Why does Asus have to such so much...? You can no longer unlock afaik.

SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?

cmendonc2 said:
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
Click to expand...
Click to collapse
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:

SilentSpartan said:
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
Click to expand...
Click to collapse
Did you ever get your tablet fixed? I am having some problems myself after a miserable m9 update.

Unable to root after OTA update

Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?

arunhebbare said:
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
Click to expand...
Click to collapse
Just for the heck of it, have you tried just booting into TWRP instead of permanently installing, to see if TWRP will even load ok?

No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).

arunhebbare said:
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
Click to expand...
Click to collapse
I had no problems flashing TWRP with "flash" command afterwards. My notes... http://forum.xda-developers.com/2015-moto-g/general/manual-ota-update-process-step-step-t3206049

Boot command worked
As an update I tried the fastboot boot recovery.img command and I could reboot and adb reboot onto twrp recovery mode. But when resorting to the volume button mode to recovery I again was presented with stock recovery.
I tried using the fastboot flash recovery command and it seems to have done the job. Now I am able to reboot to twrp recovery using both software and hardware ways.
What still bugs me is that why did not the flash commands work?
Any insight into this will help me understand the nuances of differences between booton and flashing o I have misunderstood them.

fastboot boot recovery.img=boot into recovery once
fastboot flash recovery=flash it permanently
Sent from my Nexus 6 using Tapatalk

Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation

arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
I don't know if it's same in Moto devices too or not but in Samsung there's a file named installrecovery.sh which replaces custom recoveries with stock on boot.
But once the device has been rooted it can be stopped from doing so.
Maybe this same thing happend with you.
Again this is just mere assumption keeping a samsung device in mind and may be completely wrong logic.
Sent from my SM-A800F using XDA Free mobile app

arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
Try using a new usb cable. I have no idea WTF motorola was thinking, including that god-awful charger without a detachable usb. I've seen this problem happen several times, though. When the cable goes bad but still has the actual connection it may not transfer data properly...but since it's connected fastboot doesn't know the file never actually transferred so it reports that it's done.
I bought a 6-pack of Tronsmart USB cables from amazon for $10, and they're absolutely amazing!!! They're made with 20-gauge wires, which are far thicker than those that will come with the phone, no matter what OEM it's from. Fat cable means fast transfer speeds and a longer life, since it will take longer to fray due to its heft.
*** the deal I got is actually back. Last time it only lasted a day, so if you want it, I'd recommend hurrying!!
http://www.amazon.com/Tronsmart-Cha...YYK0/ref=sr_1_7?ie=UTF8&qid=1442849948&sr=8-7

[Guide]How to Root OnePlus 6 Guide! [Video Tutorial][Windows/Mac/Linux]

For those of you who want to root your OnePlus 6, here is the easiest root method even a 10-year old can follow that works on all Windows, Mac, and Linux. Now, before I begin, you will have to unlock the bootloader. If you have not unlocked your bootloader or don’t know what that is, please follow How to Unlock Bootloader on OnePlus 6 first!
Here's a full step-by-step video tutorial:
First, I want to thank those who made root tutorials but I found an easier way to root that does not involve switching any slots, took me a quite awhile to figure this out but well worth the effort. You only have to flash TWRP image to boot, then with TWRP flash boot.img, TWRP installer, and Magisk with this tutorial. You can do it easily on all Windows, Mac, Linux, or even Chromebook(just install Chrome ADB on Chrome Web store)
Special thanks to magnamentis, his method didn't work for me as I lost my Wifi but after few hours of tinkering, found you can just reflash boot.img then the TWRP installer zip file he provided, and voila! Flawless root everytime, I've tested this about 10 times now, thanks again for the post here:
https://forum.xda-developers.com/showpost.php?p=76687704&postcount=212
Step 1. Once you have unlocked your bootloader, make sure to SIGN IN as if you do not sign into your phone, you will end up in a nasty bootloop.
Step 2. Check your Android version in Settings->About Phone just in case you are reading this in the future when Android 9.0 comes out but this tutorial is future-proof and will work on future Android versions so long as you use the correct boot image file.
Step 3. Power off your phone and hold down Volume Up and Power buttons for about 3 seconds until you enter the Fastboot mode. When doing this, make sure your USB cable is disconnected otherwise you may enter another special mode for unbricking. If you mess up and get into that special mode, simply reboot your device by holding down Volume Down and Power buttons for about 20 seconds.
Step 4. Once in fastboot mode, connect a USB cable from your OnePlus 6 to your computer. You can use Windows, Mac, or Linux. For my video tutorial, I will be using Windows 10 but you can go ahead and use the substitute code for Mac or Linux as most of the steps are nearly identical.
Step 5. You will need to download:
NOTE: All the download links are at the BOTTOM OF THE PAGE, wait 5 secs and click on "CLICK HERE TO DOWNLOAD", don't click on the ads!!!
Download fastboot.zip:
https://download.highonandroid.com/file/Tools/fastboot.zip
Android USB Drivers for Windows:
https://download.highonandroid.com/file/Drivers/UniversalAdbDriverSetup.msi
Download Magisk:
https://download.highonandroid.com/file/Tools/Magisk/Magisk-v16.4.zip
Download TWRP image:
https://download.highonandroid.com/file/TWRP/OnePlus6/twrp-3.2.1-oneplus6.img
Download TWRP installer zip:
https://download.highonandroid.com/file/TWRP/OnePlus6/twrp-installer-oneplus6-3.2.1.zip
Download and boot.img for OnePlus 6T Android 8.1:
https://download.highonandroid.com/file/TWRP/OnePlus6/boot/8.1/boot.img
Step 6. If you have followed my bootloader unlock tutorial and installed drivers for Windows, you can skip that step. If not, you can go head and run the Android USB Driver program and install drivers. For Mac or Linux, no drivers are needed!
Step 7. Unzip fastboot.zip and move over the TWRP image file you downloaded earlier to the fastboot folder.
Step 8. Open a command prompt for Windows by typing “cmd” in the search bar. For Mac or Linux, open a terminal, if you don’t know how, please Google it.
Step 9. Type the following.
For Windows:
cd Downloads
cd fastboot
fastboot flash boot twrp twrp-3.2.1-oneplus6.img
For Mac:
cd Downloads
cd fastboot
chmod 755 *
./fastboot-mac flash boot twrp twrp-3.2.1-oneplus6.img
Note: CHMOD command basically changes file permissions so you can run the files.
For Linux:
cd Downloads
cd fastboot
chmod 755 *
sudo ./fastboot-linux flash boot twrp twrp-3.2.1-oneplus6.img
Note: CHMOD command basically changes file permissions so you can run the files.
This will flash the TWRP image to your boot partition. Normally, we can simply boot TWRP image but since we don’t have official TWRP recovery(as of writing this), you will have to flash TWRP image to the boot partition, which allows us to boot TWRP recovery.
Step 10. Choose “Recovery” using the Volume keys and hit Power button to enter TWRP recovery.
Step 11. Recovery will probably be in Chinese, hit the “Read Only” button, top button on left middle.
Step 12. You can change the language back to English by hitting the second box from bottom right then hit the globe icon on top right.
Step 13. Go back to your computer and copy over the TWRP install zip file, Magisk zip file, and boot.img file.
Step 14. You don’t need the USB cable connected anymore. Go ahead and install the boot.img file using the image option in Install menu. This will flash back your regular boot image to the boot partition.
Step 15. Next, install the TWRP install zip and Magisk zip file. This will give you permanent TWRP recovery and full root.
Step 16. Reboot and you should see everything working including WiFi, 4G LTE, yadayadayada. Open Magisk Manager app and find you have full root with SafetyNet pass also so you can hide root.
Verify you have full root by installing Titanium Backup app(free app) on the Play Store, you should see a Superuser request window.
That’s it! Enjoy folks!

OnePlus 6T? How is this supposed to be easier? You have sixteen steps here. The other method from wuxianlin is very simple I did it in five minutes with no issues at all including WiFi still working. And how can you say you don't have to switch slots. It is required to flag TWRP to both a and b for it to work properly. You don't even mention that in this tutorial.

se7ensde said:
OnePlus 6T? How is this supposed to be easier? You have sixteen steps here. The other method from wuxianlin is very simple I did it in five minutes with no issues at all including WiFi still working. And how can you say you don't have to switch slots. It is required to flag TWRP to both a and b for it to work properly. You don't even mention that in this tutorial.
Click to expand...
Click to collapse
I got lost trying to do that root method, I was following this one here:
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
But yeah you don't have to switch slots for my root tutorial, which can cause havoc if you flash to the wrong one. If you don't believe me just watch the video. It doesn't hurt to have multiple root methods so long as they work. But my Wifi kept dying everytime I used the slot switch method until I found this way to do it.
I am only trying to make a tutorial that even a kid follow but I've broken down a few steps into maybe 10+ steps, probably helpful for noobs who are trying to root. If you are advanced XDA user, great job though, took me a few hours myself to get a flawless root method. Believe me, I love shortcuts and any method that works the first time out but sucks if people don't explain every little detail as not everyone is an expert. I've been rooting phones for awhile now and it was not easy task with OP6.

Can i use this method over patched boot image? I now rooted from https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 this guide…i wonder

galza said:
Can i use this method over patched boot image? I now rooted from https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 this guide…i wonder
Click to expand...
Click to collapse
Yes, since this root method flashes a stock boot image after installing TWRP, you can follow it fine. But make a backup of everything just in case.
Basically, this root method, you flash TWRP to boot partition, then flash stock boot image in TWRP, flash TWRP installer for permanent TWRP, then flash Magisk, and reboot. It's actually just 4 steps, I had to make it much longer for noobs because they will mess up.

zedomax said:
Yes, since this root method flashes a stock boot image after installing TWRP, you can follow it fine. But make a backup of everything just in case.
Basically, this root method, you flash TWRP to boot partition, then flash stock boot image in TWRP, flash TWRP installer for permanent TWRP, then flash Magisk, and reboot. It's actually just 4 steps, I had to make it much longer for noobs because they will mess up.
Click to expand...
Click to collapse
I didn't have to switch slots to root at all and I used the very first method to gain root that was posted here on op6 forums.
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440

se7ensde said:
I didn't have to switch slots to root at all and I used the very first method to gain root that was posted here on op6 forums.
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Click to expand...
Click to collapse
Yes, that root method is great but it does not give you TWRP recovery, meaning you can't install custom ROMs with it. But if you need TWRP recovery, you will need to install TWRP recovery thru one of the tutorials here.

zedomax said:
Yes, that root method is great but it does not give you TWRP recovery, meaning you can't install custom ROMs with it. But if you need TWRP recovery, you will need to install TWRP recovery thru one of the tutorials here.
Click to expand...
Click to collapse
The current method of installing TWRP is not noob friendly. Nor is yours in fact after reading yours or seems not complicated than it needs to be. You also need to give credit to the creators of our TWRP and there guides.

galza said:
Can i use this method over patched boot image? I now rooted from https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 this guide…i wonder
Click to expand...
Click to collapse
Did it work for you?

Thanks @zedomax!! Never hurts to have different methods, opinions, or guides! Jeep rockin! #neversettle

@zedomax Thank you for these amazing tutorials. I watched both your videos. In that you mentioned that OnePlus ota updates are twrp compatible but then if I root will I have to unroot the phone or flash the stock rom first then install that ota update and then root again or there's some other method to install OTA on a rooted device?

Aashay said:
@zedomax Thank you for these amazing tutorials. I watched both your videos. In that you mentioned that OnePlus ota updates are twrp compatible but then if I root will I have to unroot the phone or flash the stock rom first then install that ota update and then root again or there's some other method to install OTA on a rooted device?
Click to expand...
Click to collapse
You can accept OTA, but you will have to reflash Magisk.img. Most OTAs do not overwrite boot.img I think unless they are major updates(like to Android P 9.0 when available). So, just flash OTA and if you lose root, reboot into TWRP and flash Magisk.

HI, thanks for the guide but my phone just blocked at recovery launch. Ho can i do?

Same
Edit: It's ok, probably a bug

Thank you zedomax for taking the time to create this guide. I'm gonna try it!
I assume this will work for both A6000 and A6003 right?

Hi Admin,
I lost my Wifi as soon as i rooted my device, please help?

Prabhjeet Bagga said:
Hi Admin,
I lost my Wifi as soon as i rooted my device, please help?
Click to expand...
Click to collapse
Me too. How can this be fixed?

I think I bricked my phone.
This is what I did:
- Bought OnePlus 6 (I think it was A6000)
- Installed OTA, so I was on Android 8.1.0 and OOS 5.1.8
- Followed this tutorial, which broke wifi
- I followed mixtapes02's advice on the video and reflashed OOS 5.1.8
- Now I cannot boot into Android anymore, I can only get to TWRP
EDIT: I managed to install OOS 5.1.5 successfully

aximili said:
I think I bricked my phone.
This is what I did:
- Bought OnePlus 6 (I think it was A6000)
- Installed OTA, so I was on Android 8.1.0 and OOS 5.1.8
- Followed this tutorial, which broke wifi
- I followed mixtapes02's advice on the video and reflashed OOS 5.1.8
- Now I cannot boot into Android anymore, I can only get to TWRP
EDIT: I managed to install OOS 5.1.5 successfully
Click to expand...
Click to collapse
I had the same issues and went through the same process. Took a whole day to get it back to stock.

I am sorry to ask such a noob question, but i am very confused by the command you say to use in Step 9:
>fastboot flash boot twrp twrp-3.2.1-oneplus6.img
what is the meaning of the first "twrp" in that command?
shouldn't it be simply:
fastboot flash boot twrp-3.2.1-oneplus6.img
Thank you in advance for the explanation

Installed TWRP to Boot, want to boot myself in the a**.

Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.

https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892

Thank you, the tool worked like a charm.
BTW: I did search and find other "methods" but none of them worked

noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.

MrSteelX said:
What you should have done was fastboot boot twrp.img. which would start twrp, then you could have used the installer in to install twrp on phone. After that you would have to installed stock or custom kernel.
Click to expand...
Click to collapse
That is exactly what I wanted to do.
I could get into TWRP, but I couldn't see the phone on the PC and couldn't move files (ROM) to the phone (although fastboot was working and I could see the device using adb) but I couldn't figure out how to have TWRP look for or find the ROM on the PC.

There's no recovery partition on A/B phones remember.

RusherDude said:
There's no recovery partition on A/B phones remember.
Click to expand...
Click to collapse
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?

noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.

noncomjd said:
Own the OPP6; Rooted, on OxygenOS 5.18.
Went to install the newest TWRP (was going to install XXX no limits), when asked where to install it to, accidentally, without thinking, hit install to Boot.
Problems.
I can get into fastboot, the PC sees the phone in fastboot.
Have tried to flash a recovery image and similar, got an error saying: FAILED (remote: (recovery_b) No such partition).
Just want to get the phone booting again, wipe the whole thing start over, from fastboot.
Any help appreciated.
Click to expand...
Click to collapse
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/

MrSteelX said:
In twrp, you go to advance/sideload. Twrp then waits for adb sideload to push file to phone then auto flashes file.
In your case, you would sideload rom to flash and have been go to go.
Click to expand...
Click to collapse
Thanks.
I will give this a try. After I learn a little more about the A/B partitions & recovery on this phone, I want to try one on the custom ROMs.

pankspoo said:
If you have working fastboot mode and getting detected via fastboot then
fastboot flashable stock rom via fastboot mode.
U don't have to do anything just downloaded zip file unzip it any folder u want. Connect u r phone to. Computer in fastboot mode
Then go to that folder and just click flash all bat waut for 10to 15 min and then phone boots in working oos.
(all data will be get wipes after this)
Link
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/
Click to expand...
Click to collapse
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).

noncomjd said:
Thanks for the link/guide. I had been trying an iteration of this (and the guide) but after reading your link, it too explains some things. I was trying to restore a Stock ROM from fastboot according to your link:
Things are changing with the advent of project treble. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlcoked. This will erase all your data and will wipe
I download and was trying to use the stock ROMs, I didn't see any bats, and now I know why.
Lots more reading to do. I love doing playing with this stuff, but trying to learn & keep up with things burns time, which most days I don't have.
This is the longest I've ever been on a stock OS (6 weeks? got the phone right after its release) although it's rooted (can never leave things completely alone).
Click to expand...
Click to collapse
I have to unzip the downloaded fastboot ROM at any folder on computer and open that folder u will see named [flash all bat]
Now connect phone in fastboot mode to computer and just click [flash all bat] file

noncomjd said:
Thanks for that. and that explains a few things and explains why when I installed TWRP, I didn't see the recovery option. Doesn't pardon my hitting install to Boot.
Just thought of another Q, if there is no recovery partition, where is the OEM recovery stored? (I figured the lack of a recovery partition is why TWRP gets overwritten if installed without a custom ROM)
I did a quick read on that, it seems really interesting and may be of some use as soon as I learn more.
I've got so much to learn about this. I keep meaning to take time to begin, but stuff comes up and boom more changes.
I've got to do more reading to take advantage of that.
@MrSteelX mentioned that I could have used TWRP to install a ROM from the PC.
Is this what is referred to as "sideloading". I've been looking for some info on this and haven't really come across much that is any good.
Are there any available guides that anyone can point to so I can learn about using TWRP that way?
Click to expand...
Click to collapse
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.

RusherDude said:
"recovery" (what's left of it... wipe and mostly nothing else) is inside the boot partition. TWRP on those devices is installed into the boot partition (NOT overwriting the boot partition, but into the "ramdisk", a part of the kernel where OEM recovery resides and where TWRP, Magisk, Xposed and all the mods do their stuff on the kernel. On a phone with A/B partitions, you have to fastboot BOOT twrp, and then you have to flash the installer zip, you should never ever flash the image to any partition since there isn't any.
Click to expand...
Click to collapse
Thanks for the information.
and this is what I did, originally I thought I had accidentally selected the wrong partition, but it seems since there is no recovery partition, I did it wrong from the start.
Q: I'm guessing this is why when you do load TWRP (the correct way, which I did once, following a guide) without a custom ROM (still using Oxygen OS) that the OEM recovery overwrites TWRP or the OEM recovery is called up at the next reboot into recovery?
Q: I understand, at least in theory the benefit of the A/B partitions, what is the benefit of eliminating the recovery partition other than giving more control of the phone to the OEM and OS? Is this setup limited to the stock kernel or mandated to be copied by any potential replacement kernels (this information is new to me, I haven't yet read up on kernels).

major pixel 2 rooting problems

im serous this is the worst device i ever had to root in my life. ive rooted meany devices and modded meany other stuff without issue, had one brick that i was then able to restore and get right the 2nd time. this time however this is the 2nd! pixel that has went into an unrecoverable bootlap when following root tutorials via magisk.
when i then attempt to unbrick eaither of the devices the fast boot official flash all dosent cut it, and adb ota restore dosen't work as recovery menu is destoyed., and dosent revive when original boot.img is flashed. when i looked at the first phone what i found on net is hawrdware issue can cause corruption in flash and cause them to be unrecoverable...... but a 2nd one now? is this upside down world? "root friendly" my A......

Nightmare-Rex420 said:
im serous this is the worst device i ever had to root in my life. ive rooted meany devices and modded meany other stuff without issue, had one brick that i was then able to restore and get right the 2nd time. this time however this is the 2nd! pixel that has went into an unrecoverable bootlap when following root tutorials via magisk.
when i then attempt to unbrick eaither of the devices the fast boot official flash all dosent cut it, and adb ota restore dosen't work as recovery menu is destoyed., and dosent revive when original boot.img is flashed. when i looked at the first phone what i found on net is hawrdware issue can cause corruption in flash and cause them to be unrecoverable...... but a 2nd one now? is this upside down world? "root friendly" my A......
Click to expand...
Click to collapse
In my opinion, you should use root tutorials from your phones forum, not magisk. You haven't explained what your steps were or even asked a question. If you tried using stable channel/files, try the canary debug channel and files instead. I've never had any problem rooting the pixels though I've read where the magisk version 20.2 has caused bootloops for some phones.

allright so it might just be the magisk. it was magisk 20.1 first phone magisk 20.2 2nd phone. i cannot boot into recovery mode and fastboot mode restoring ota dosen't work and it still bootlaps weather i restore just the boot_A and boot_B or whole thing. also where can i find unbrick and root tutorials made for my phone when looked it was mostly magisk and little TWRP.

Nightmare-Rex420 said:
allright so it might just be the magisk. it was magisk 20.1 first phone magisk 20.2 2nd phone. i cannot boot into recovery mode and fastboot mode restoring ota dosen't work and it still bootlaps weather i restore just the boot_A and boot_B or whole thing. also where can i find unbrick and root tutorials made for my phone when looked it was mostly magisk and little TWRP.
Click to expand...
Click to collapse
Hi, I thing, that you need to download factory image (not OTA) for walleye:
Code:
https://developers.google.com/android/images#walleye
Latest SDK Platform Tools:
Code:
https://developer.android.com/studio/releases/platform-tools.html
than boot to bootloader, open command prompt in folder with extracted SDK platform tools run flash-all.bat script with command:
Code:
flash-all.bat
This should format/flash your phone to "factory" state. Good luck.
Btw, I have no problem with magsik 20.1 neither with 20.2...

Just to rule the magisk thing out, I recently bought a used pixel 2 to replace my broken og pixel and I got round to unlocking it last night and had no issue gaining root using magisk 20.2 following the usual process.
Updated to latest platform tools.
Unlocked the bootloader via adb
Skipped through the set up and re enabled usb debugging
Rebooted to bootloader
fastboot booted twrp 3.3.0-0 via adb
flashed magisk 20.2 from fastbooted twrp
rebooted and all good.
If you are having problems booting to the existing recovery you could try fastboot booting the latest twrp in adb (may not work if you had a pin set up as may not be able to decrypt) and try flashing the original or fresh boot.img from there other than that follow the previous post and do a full re flash to stock.
Good luck