Database Info

Downgrading from Android O DP2 to 7.1.2 no TWRP

I was enrolled in the Android O Beta Program and followed these steps but can't get TWRP to boot:
• Un-enroll from O beta
• Take OTA to downgrade to 7.1.2 N2G470
• Set up system (dev. options, enable USB debugging, etc.)
• fastboot boot twrp-3.0.2-0-RC1.img
• Boots in to TWRP but doesn't go passed splash screen (after waiting more than 30 minutes)
Not sure if I have to re-flash nougat bootloader, radio and img. Any help is appreciated, thanks!

It's a known issue with TWRP with way O repartitions your phone even after downgrade. You'll have to wait for an update to be released to accommodate the changes in partition structure.

You'll have to flash the factory images from April or May to both slot before it will work again properly

S8ntsHaz3 said:
You'll have to flash the factory images from April or May to both slot before it will work again properly
Click to expand...
Click to collapse
Gotcha, I'll give it a shot tonight.

No problem

S8ntsHaz3 said:
You'll have to flash the factory images from April or May to both slot before it will work again properly
Click to expand...
Click to collapse
This is correct.. all you need to do is flash the factory images to BOTH slots and you'll be good to go.. I went through this issue myself and once I did this, everything is back to normal

pahlerc1 said:
This is correct.. all you need to do is flash the factory images to BOTH slots and you'll be good to go.. I went through this issue myself and once I did this, everything is back to normal
Click to expand...
Click to collapse
Perfect. Thanks for looking out dudes.

That's what this place is for!!!

S8ntsHaz3 said:
You'll have to flash the factory images from April or May to both slot before it will work again properly
Click to expand...
Click to collapse
I've tried multiple times to get this booted to both slots and can't seem to get it right. Can you provide steps how to flash to both slots?

I use the unified android toolkit. I'm just learning all of this myself but I know there's a guide on here somewhere that can explain it better than my self. I believe it involved getting the factory image and removing the -w from the flashall file. I'm sorry I cant be of more help!!

S8ntsHaz3 said:
I use the unified android toolkit. I'm just learning all of this myself but I know there's a guide on here somewhere that can explain it better than my self. I believe it involved getting the factory image and removing the -w from the flashall file. I'm sorry I cant be of more help!!
Click to expand...
Click to collapse
Thanks, I'll look around, but if anyone has a link I'd appreciate it

In my experience if you flash the factory images twice it's flashes to both slots

Finally got the image flashed to both slots. Now for some reason I always get a bootloop after flashing the twrp installer. fml

chesstopher said:
Finally got the image flashed to both slots. Now for some reason I always get a bootloop after flashing the twrp installer. fml
Click to expand...
Click to collapse
On the May update?
You need to install the zip from inside twrp that is in the first post of the thread below. Need to do that when you root, twrp or change kernels.
So fastboot boot to twrp again and adb push the zip to the phone and install it.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

TonikJDK said:
On the May update?
You need to install the zip from inside twrp that is in the first post of the thread below. Need to do that when you root, twrp or change kernels.
So fastboot boot to twrp again and adb push the zip to the phone and install it.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yup, I was on the may update, had no idea they changed anything up in May. What I did was reboot the system, download the twrp zip, fast boot back to twrp and flash the zip, resulted in boot loop. I'll try flashing the verified bootsigner later and if that doesn't work, I'll try rolling back to April.

Flashing the bootsigner did the trick. Thanks for all the help!

enrolled android beta program for almost a day, battery consumes very much.
Now flashing the full May image, but after finishing flash, the phone can't boot into system.
It persisted in four turning dots for almost half an hour.
Tried to re-flash the may image, it did no help.
What should I do, mate?
chesstopher said:
Flashing the bootsigner did the trick. Thanks for all the help!
Click to expand...
Click to collapse

bush911 said:
enrolled android beta program for almost a day, battery consumes very much.
Now flashing the full May image, but after finishing flash, the phone can't boot into system.
It persisted in four turning dots for almost half an hour.
Tried to re-flash the may image, it did no help.
What should I do, mate?
Click to expand...
Click to collapse
Sorry man, I've been away from my computer for a couple days. Glad to see you got it figured out. What worked for me was booting into twrp from fastboot, flashing the twrp zip, flashing the latest bootsigner zip from CF, reboot recovery then following the steps to flash PA + gapps that I had downloaded previously.:good:

[solved] June updates are out, but which one?

Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.

CatThief said:
[solved] Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
Click to expand...
Click to collapse
There's actually 4 different builds.
See here for what's what

Yep, I did that. There is no description there for "N" but I found out "B" is the one I want.

I always get Failed to udate, try again when installing the ota via settings.

Juli112 said:
I always get Failed to udate, try again when installing the ota via settings.
Click to expand...
Click to collapse
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.

alluringreality said:
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
Click to expand...
Click to collapse
Did you update already. I read somewhere since the may update that if you have bootloader unlocked, rooted, and another kernel you get bootloops?
Is that true? I'm still on April security update and been using stock rom, just unlocked bootloader, rooted, and using elementalx kernel

I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435

I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.

alluringreality said:
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
Click to expand...
Click to collapse
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!

Nope. twrp.img must be firstly boot into the phone, then via this temporary twrp,you can install twrp.zip from your phone.
kazemitsui said:
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse

CatThief said:
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
Click to expand...
Click to collapse
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?

TENN3R said:
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I used twrp-3.0.2-0-RC1-fastboot-sailfish.img because it was the only version that was stable for me from the start. When the January update came out I tried the current TWRP at that time (it was an RC3, can't remember the version) and while others had no problems I had an experience of my own that I'm not keen on repeating.
As for SuperSU, I installed SR5-SuperSU-v2.78-SR5-20161130091551.zip then updated to the latest 2.82 from Google Play.
I know​, newer releases may work now, but I was only going to try something newer if my "old" method failed. Like I said, I only boot to TWRP, I don't​ flash it. I just want root.

kazemitsui said:
i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
TENN3R said:
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.

alluringreality said:
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
Click to expand...
Click to collapse
I just flashed TWRP through my computer I couldn't bother trying to figure out if FlashFire will flash TWRP or not haha

8.1 developer system image

Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?

Horgar said:
Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?
Click to expand...
Click to collapse
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.

mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?

Horgar said:
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?
Click to expand...
Click to collapse
I'm not bothered with twrp recovery so did not flash the zip, but like I said I booted into twrp.img, flashed supersu and suhide and that's it. All working for me including SafetyNet. I used USB OTG for this process.

I did the same as the poster above.

just curious;
but how is Android 8.1? ?
I've found 8.0 to not be as good on battery life as 7.x.x, although I think I have mostly worked that out on my custom kernel...
any other notable goodies?
(ps: I don't care for the pixel launcher or the ambient services stuff..)

mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
I flashed factory image and I have error.

Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
Move the entire folder to a drive other than C drive. I think that might fix it.

NoobInToto said:
Move the entire folder to a drive other than C drive. I think that might fix it.
Click to expand...
Click to collapse
I did. But the error exit

Myo Thu Htet said:
I did. But the error exit
Click to expand...
Click to collapse
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.

NoobInToto said:
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.
Click to expand...
Click to collapse
I did all u did ?
Yes I checked G+
Only few can install.

Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5

mannunikhil said:
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5
Click to expand...
Click to collapse
Nope. It looks like Google's fault this time.

NoobInToto said:
Nope. It looks like Google's fault this time.
Click to expand...
Click to collapse
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.

mannunikhil said:
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.
Click to expand...
Click to collapse
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...

NoobInToto said:
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...
Click to expand...
Click to collapse
Mine was the fair test just to check if OTA zips are corrupt or not. I provided suggestions for factory image not for OTA, no point in extracting the OTA anyway. And if you had gone through all the threads you would see I mentioned I had similar issue sideload'ing OTA over 8.0.0, so that means we are sailing in same boat. OTAs had compatibility issue with 8.0.0, glad google listened and taken them off.
I still have little lag in app drawer hoping that would be fixed too in republished OTA.

Just signed up for Android beta program and got the 8.1 update for my project fi carrier unlocked Google pixel XL. The update seems to be running smoothly and everything is working so far on my device... I didn't have any issues with installation it installed just fine... Can't wait for Nov security patch supposed to be a good network feature in there in Dev settings.

I am not sure if this may help anyone trying to look at why the issues are present when trying to install:
Android 8.1 beta OTA upgrade on OG Pixel
I, just like many of you, have been experiencing OTA "installation problem" when trying to upgrade to the 8.1 beta. After reviewing comments and what worked for who, I decided to give this a shot and it worked. I am not sure if this will work for other devices (nexus or XLs) and keep in mind that you WILL lose all your data stored on the device, so back up prior to this method.
1. Be sure you are enrolled in the beta program.
2. Wait for the OTA to notify you that it's available.
3. Select "Download and Install".
4. After it has done its duty, DO NOT select "Restart and Install"
5. Go to "Factory Reset" and pull the trigger.
6. Your phone will factory reset, stating it's wiping everything, then it will install the update successfully.
NOTE: this is what worked for me. I'm unsure if it will solve all the "Installation problem" reports which have been made.
It's weird cause when I tried to factory reset, then download and install, it didn't work. Yet, downloading but NOT installing, then factory resetting worked.
After doing this I posted it here: https://plus.google.com/+ChristopherLeeMurray/posts/KDCZXbfAxLJ

You don’t need to sign up to the beta program. Just go to the Google website and download the latest 8.1 factory image. That's what I did and had no problem with flashing it. You can also delete the - w and keep your data. It's getting past the TWRP password to decrypt that I cant do. So can't flash root or recovery. Anyone managed this?

I'd prefer to be in the beta program since I'm a Android apps beta tester. I beta test everything and when it was installing it said on the screen that it's a beta version of the original software version of 8.1 which is what I believe is on Googles page and mine may have errors and defects.. the beta program gets different software than what Google usually posts. Different features and such which isn't in the official version which makes it a beta version.

June update is out! (Android 9.0.0 Build PQ1A.190105.077)

When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?

liquor said:
When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?
Click to expand...
Click to collapse
When will it end? Probably August 2020 as Essential has promised 2 years of OS updates and 3 of security updates like the Pixel. Android Q would be the last OS update, followed by a year of security updates. And August because the phone launched late August. It might get support through September. All assuming nothing happens to Essential before then.

Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip

Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?

goofball2k said:
Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip
Click to expand...
Click to collapse
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.

jxcorex28 said:
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.
Click to expand...
Click to collapse
I have TWRP installed. This is my way of doing the update.
Ensure the OTA zip and TWRP zip (optional, you can choose to install TWRP your own way) and Magisk zip (optional, only if you want to be rooted) are on the phone storage
Reboot to TWRP recovery
Select Install, then install the OTA zip file and then the TWRP recovery zip.
Reboot to system, or if you wish to have Magisk installed, flash the Magisk zip file.

knochnkopf said:
Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?
Click to expand...
Click to collapse
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install

cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
I had no issues installing the June OTA through TWRP after going back to stock May ROM from the Q Beta.
I would recommend you to back up again and start with the stock fastboot June ROM.
Good luck.
Sent from my PH-1 using XDA Labs

cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Update: Flashed OTA zip from stock recovery without loss of data. They should really make that clearer on their website because it says flashing OTA "may" result in loss of data.

knochnkopf said:
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Click to expand...
Click to collapse
I flashed the OTA via TWRP and retained all app's and the data without any problems.
Sent from my PH-1 using XDA Labs

The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.

Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy

marcdw said:
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
Click to expand...
Click to collapse
Actually I did try that, but I can't flash it due to fastboot not working unfortunately. It seems like one of my slots is corrupted.

Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
I don't use TWRP, but I was able to successfully flash Magisk-patched boot image after the latest update, so fastboot seems to be working just fine for me...

Unable to boot recovery after Android 10 Open Beta 1 OTA

Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!

seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.

HighOnLinux said:
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
Click to expand...
Click to collapse
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.

verbatim7 said:
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
Click to expand...
Click to collapse
Had read somewhere that flashing stock boot.img will help restore stock recovery.. Have you tried doing that

brashmadcap said:
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
Click to expand...
Click to collapse
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me.
Edit: this part down was meant for OP, sorry for confusion
so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal

HighOnLinux said:
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me. so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
Click to expand...
Click to collapse
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:

Use an older version of magisk and you won't lose twrp

verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
how did u get back the recovery?

LazerH said:
how did u get back the recovery?
Click to expand...
Click to collapse
As stated above - just downloaded the OTA Android 10 update file for the right device, installed it and didn't install magisk to inactive slot and I had it back. If I tried to install magisk to keep root I didn't have the recovery mode. My guest guess is that magisk still isn't fully compatible with the new Android 10 boot changes.

verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
To me having a stable phone is much more important than a heavily modified device that's unstable at any given time. I'd say use the msm tool, flash back to a fresh build of pie, download the full open beta 30 zip, after its done flashing, reboot twice to iron out any present issues, then unlock the bootloader, and then you should be good to go. If you want root, just fastboot boot into twrp and flash the latest magisk zip and you're good to go. At the end you should have root, an unlocked bootloader, all while on the open beta android 10 build, with access to the stock recovery

Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (

terrorblade23 said:
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
Click to expand...
Click to collapse
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot

Schnullifax said:
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Click to expand...
Click to collapse
thanks..this is what i was looking for ...the problem is that now i'm in a boot loop , the dots keep spinning 4ever...and i did factory reset it from recovery
up1: i managed to install on slot a (i guess) Twrp.. but the whole memory is empty and i cant place anything (firmware) with pc on phone
formated data from twrp (to some format ntfc4 or smth like that ) and installed back android q and is working .