I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help
mnaceem said:
I am trying to install the latest Pie Update, but unable to do so, tried local upgrade/install from internal storage, recovery mode, and ADB Sideload, every time same error "Installation failed", I wiped data, erase everything, reset and wipe cache as well, no success. My device is not rooted, it is reset to Oreo Oxygen OS 5.02. Please help
Click to expand...
Click to collapse
maybe a bad/corrupted download
Same issue here, I am unable to update my phone
Sent from my [device_name] using XDA-Developers Legacy app
I just got the same error too.
I also got a warning while i boot back to the old version.
System update failed
Update failed, tap to enter repair mode to try again.
guys, i had the same issue too.
Download the full rom via xda link, installation failed. Same goes for the OTA.
However, I managed to update to stock PIE.
My bootloader was unlocked when using stock OREO.
So what I did was, I RE-LOCKED the bootloader, and reboot the OP3T. (BE WARNED,IT RESET THE WHOLE PHONE)
After fresh installation, i was able to update to PIE via OTA. (Should work with local upgrade too)
So for my case, that helps.
vinoxflame said:
maybe a bad/corrupted download
Click to expand...
Click to collapse
NOPE no bad/corrupted download...
---------- Post added at 09:01 AM ---------- Previous post was at 08:52 AM ----------
Well I was upgraded to the pie with locked bootloader and after that, I had flashed official twrp and magisk but I flashed oreo rom to check if this problem is there when the bootloader is unlocked well yes the one plus detects that your bootloader is unlocked and doesn't deliver the ota so what you can do is click on download upgrade read carefully bro DOWNLOAD not INSTALL just DOWNLOAD it and then you will find it in .ota directory in File Manager now what you have to do is backup your all data via your prefered backup method from which you can restore things after the update I am going to give you a spoiler all data will be corrupted when you will flash the update file via twrp that's why the one plus package updater doesn't update and says installation failed... The pie update will be successfully installed but you have to factory reset your phone to use it that's why I told You to take a backup and after this restore your data...
***I have experienced all this by downgrading and then again upgrading with an unlocked bootloader so I would be honored if you thank me***
I was on stock Pie. I was facing some battery drain issue so I decided to install Oreo official stock which was already downloaded last month. I installed it through local upgrade and rom is still in internal memory. Now I am stuck in Recovery. It tries to boot but every time after few minutes it comes back to recovery. Please help me. It installs Oreo through recovery but unable to boot.
I think Pie can be installed through sideload but I could not find exact links for installation through sideload. Or if there is any option to copy Pie Rom in my internal memory to try installing back latest rom.
If anyone could help me It will be highly appreciated. My bootloader is still locked.
Related
Hi All,
I have a Spice MI 498 handset. I have unlocked boot loader, installed Philz recovery. For OTA update to 5.1, I had to go back to stock recovery as there was an error message when Philz was running. Once the update completes, my IMEI numbers disappeared and I was unable to recover it through any of the methods. As per another users experience, I did a factory reset and upon rebooting touch stops working. Has anybody faced this issue and what should be the approach that I need to take to resolve this issue?
Regards,
Ram
ramlivs said:
Hi All,
I have a Spice MI 498 handset. I have unlocked boot loader, installed Philz recovery. For OTA update to 5.1, I had to go back to stock recovery as there was an error message when Philz was running. Once the update completes, my IMEI numbers disappeared and I was unable to recover it through any of the methods. As per another users experience, I did a factory reset and upon rebooting touch stops working. Has anybody faced this issue and what should be the approach that I need to take to resolve this issue?
Regards,
Ram
Click to expand...
Click to collapse
Factory reset usually doesn't work with problems like that. Flash the stock kitkat for your phone with SP Flash Tool (search the forum for a tutorial). That'll fix it. BTW. what OTA did you flash? (LMY47O. LMY47I etc.) I've flashed LMY47O OTA with TWRP recovery and it flashed without a problem. Did you wiped anything on your phone before or after flashing the OTA?
Dhamithl said:
Factory reset usually doesn't work with problems like that. Flash the stock kitkat for your phone with SP Flash Tool (search the forum for a tutorial). That'll fix it. BTW. what OTA did you flash? (LMY47O. LMY47I etc.) I've flashed LMY47O OTA with TWRP recovery and it flashed without a problem. Did you wiped anything on your phone before or after flashing the OTA?
Click to expand...
Click to collapse
Hi,
I have LMYF7O installed via OTA method. I had not wiped anything on my phone before flashing the OTA. I managed to get back my phone working after I found out the reason for this missing touch. I just called my mobile number from another number and found that touch was actually working. So once that was done, I came out of the installer/registration mode and everything worked fine. Now getting all the data restored including sms, applications etc.
Thanks for the help.
Ram
I have a rooted Verizon Moto X 2013 Developer Edition (XT1060) with Android 4.4.4, TWRP and SuperSU installed. I rooted the phone so I could install a wi-fi tethering app that I frequently use. Last night I noticed that the Lollipop OTA was available, and being a dumas, I proceeded to download it without coming to xda-developers first to educate myself on the correct process and potential issues with the upgrade (one such issue being whether I will be able to run my tethering app after the upgrade). Consequently, after I downloaded the upgrade, my phone restarted and booted to the TWRP screen, and I don't know where to go from there to complete the upgrade, if it's even possible to do so.
This is my only phone, so it's more important that I get my phone up and running in the next 1-2 hours than it is to complete the upgrade. With that in mind, what should I do next? Is there a way to quickly abort the upgrade process, perhaps by simply deleting the update file "Blur_Version.212.166.3.ghost_verizion.Verizon.en.US.zip" in my cache folder using TWRP's File Manager and rebooting my phone? Or is it possible to complete the upgrade process in the next 1-2 hours? If so, how should I proceed?
By the way, TWRP is displaying the following error messages:
Error executing updater binary in zip '/cache/Blur_Version.212.166.3.ghost_verizion.Verizon.en.US.zip'
Error installing zip file '/cache/Blur_Version.212.166.3.ghost_verizion.Verizon.en.US.zip'
Thanks in advance for helping me recover from my dumas behavior.
The OTA update file does not work with TWRP, IMHO. It only works with the stock recovery.
If you just boot back out of TWRP (boot back to regular system) your phone should still be functional.
kschang said:
The OTA update file does not work with TWRP, IMHO. It only works with the stock recovery.
If you just boot back out of TWRP (boot back to regular system) your phone should still be functional.
Click to expand...
Click to collapse
Thanks, kschang. Your suggestion worked, but not right away, so there appears to be a twist involved that other users should be aware of if they get stuck in the same situation I was in.
As I indicated in my original post, after downloading the update, my phone would power off and boot to TWRP. From TWRP's main menu I would click on "Reboot," then "System." I tried this a number of times, and each time my phone would reboot to what it appeared to be before I downloaded the upgrade, but only for about 10 seconds, then it would power off and reboot to TWRP again--except for just now, when the phone displayed a message that the upgrade had failed and no changes were made to my phone! Apparently the upgrade process has to fail a certain number of times before it finally aborts. I don't know what the number is, but I must have tried rebooting my phone at least 10-15 times before the upgrade process aborted.
So thanks again for your suggestion. It encouraged me to keep trying to reboot until it ultimately worked:good:
I had the same issue with my phone rebooting so I forced the system update app to freeze via Titanium Backup and that seemed to work.
My phone now is kinda messed up though. To get it to boot I have to hold the volume key while powering it up and choose "boot normally". Any time I just restart my phone or power it up while it's off I get a black screen because like the OP I tried to update to Lollipop without reading XDA first. Doh!!
Any first impressions on the update for this phone by the way? Battery life improve or get worse? Can I still use Xposed on Lollipop? Rooting still possible? Wifi tethering for us on unlimited data?
Same situation. Want to upgrade but not sure how now... waiting for an angel to answer my prayers!
daddylonglegs said:
I had the same issue with my phone rebooting so I forced the system update app to freeze via Titanium Backup and that seemed to work.
My phone now is kinda messed up though. To get it to boot I have to hold the volume key while powering it up and choose "boot normally". Any time I just restart my phone or power it up while it's off I get a black screen because like the OP I tried to update to Lollipop without reading XDA first. Doh!!
Any first impressions on the update for this phone by the way? Battery life improve or get worse? Can I still use Xposed on Lollipop? Rooting still possible? Wifi tethering for us on unlimited data?
Click to expand...
Click to collapse
Root is still possible. The only issue i had was after flashing Twrp, if i rebooted the phone and then tried to boot the recovery Twrp was gone. So i reflashed Twrp while i was still in fastboot i selected "recovery" it booted into Twrp and i flashed a SuperSU zip.
After that i could reboot into Teamwin without issue. I haven't tried Xposed yet. Battery life is great on my end.
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
rice923 said:
Same situation. Want to upgrade but not sure how now... waiting for an angel to answer my prayers!
Click to expand...
Click to collapse
The way i did it was to fastboot flash the dev edition 4.4.4 files to unroot. Then i used Verizon upgrade assistant to take the small update that came out awhile ago. After that i factory reset the phone, checked for updates and the first of two updates installed then it updated to 5.1
I reinstalled Twrp and regained root access.
James L said:
The way i did it was to fastboot flash the dev edition 4.4.4 files to unroot. Then i used Verizon upgrade assistant to take the small update that came out awhile ago. After that i factory reset the phone, checked for updates and the first of two updates installed then it updated to 5.1
I reinstalled Twrp and regained root access.
Click to expand...
Click to collapse
Would flashing dev 4.4.4 unroot as well as remove twrp? Twrp seems to be the main obstacle to get past in order to get the update going. If so, I might just do this tomorrow
The immediate way to get out of the failed flash and reboot-cycle is to (quickly) use a file explorer such as ES File Explorer and migrate to your internal cache folder and delete the Verizon flash file. That stops the reboot cycle in its tracks. You'll get the "failed" message before too long, too.
I found I had more like a minute before a reboot occurred after a failed flash. In other words, I'd be stuck on TWRP, clicked to reboot system, it would reboot. Then, I had about a minute to do stuff before it would shutdown/reboot again. During that time, I would just go to ES File Explorer and delete the Verizon update file from the cache folder, and problem solved.
Of course, it will download again shortly thereafter, but won't do anything until you agree to go ahead and install it.
Guess I'm going to have to flash all the 4.4.4 files like stated above to get back to stock (lame!) and then do the OTA updates. I seem to recall someone had figured out how to flash OTA on a previous update without having to go back to stock, though.
rice923 said:
Would flashing dev 4.4.4 unroot as well as remove twrp? Twrp seems to be the main obstacle to get past in order to get the update going. If so, I might just do this tomorrow
Click to expand...
Click to collapse
Yes it would remove Twrp if you flash the stock files.
---------- Post added at 10:34 AM ---------- Previous post was at 10:25 AM ----------
You could take the little update prior to the 5.1 update by reflashing the stock recovery that will stop the bootloop from the smaller update.
I didn't lose root and just reflashed Twrp. Then after a bit the 5.1 update was released so i just took the jump and flashed stock files to unroot, and took the update. Is it possible to update to 5.1 with root and a stock recovery?..... Not sure i was going to try it but didn't
Root is still possible. The only issue i had was after flashing Twrp, if i rebooted the phone and then tried to boot the recovery Twrp was gone. So i reflashed Twrp while i was still in fastboot i selected "recovery" it booted into Twrp and i flashed a SuperSU zip.
Click to expand...
Click to collapse
Verizon MotoX Developer Edition (2013) - I am having the same issue installing TWRP after reverting to stock and receiving/installing the 5.1 OTA. If I try to flash TWRP via fastboot, it doesn't seem to take. The flash shows as a success, but when I reboot to recovery I'm still in stock. I've tried flashing TWRP then using the volume rocker to immediately boot into TWRP, with no success. I've also tried holding down the bootloader key combo immediately after "fastboot reboot", with no success. When I boot up, though, my apps will optimize every time. Am I missing something?
EDIT: Resolved the problem, turns out I was not using the volume up button to enter recovery immediately after flashing...smh
For VIE-AL10 the new firmware update B390 is out. However, currently I am on B356, rooted and TWRP installed. However, when I do the OTA update it restarts into TWRP (because stock recovery is gone). I can't find a download to stock recovery for B356. How else can I installed this OTA update? I've tried dload folder way but with no avail. Any help would be appreciated.
you wont be able to install stock ota whilst you are rooted with twrp. You are going to have to go back to stock and with no root to do the ota, use this tool its worked for me in the past.
https://forum.xda-developers.com/p9-plus/development/tool-srk-tool-huawei-bootloader-root-t3405999
PLEASE READ ALL THE THREAD BEFORE USE
if you do have questions ask in that thread
So I decided to wipe and reinstalled my firmware B356. Locked bootloader, no root, no twrp, brand new install. I look into hicare and it doesn't have the option to upgrade to B356. Anyone know why?
go into twrp
advance -> files manager -> /dev/block/platform/hi_mci.0/by-name/
copy recovery2 to SDcard (or other place)
rename copied recovery2 to recovery
recopy the file to /dev/block/platform/hi_mci.0/by-name/
reboot
Deviatorz said:
So I decided to wipe and reinstalled my firmware B356. Locked bootloader, no root, no twrp, brand new install. I look into hicare and it doesn't have the option to upgrade to B356. Anyone know why?
Click to expand...
Click to collapse
It should show updates, set your region to china in hicare after a reboot check it. If still nothing then post in the thread that I left a link for
Sorry for late reply. It started to show the update after a week. Not sure if the other methods worked but it showed up. I have a feeling it's because huawei decided to pull the firmware temporarily.
UPDATE: I was able to install stock recovery through BOOTLOADER (it started working again) and I tried sideload 4.1.7.zip that way. It seemed to work for a while, but unfortunately, sideloading crashed. Same for 4.1.6, update fails around 45%. Phone says INSTALLATION FAILED. Any thoughts?!
Hi guys,
I'm a longtime flasher of phones, but my wife today jacked up her 3T beyond the point that I know what to do. In short:
Her phone was rooted, had an unlocked bootloader and TWRP installed. She updated (despite my endless begging never to do that) the OTA, which crashed her phone. Duh. Not smart. The problem: the phone would not restart the OS anymore. Upon restarting, the phone immediately jumped to TWRP and hung at the splash screen (which takes a while to load, but she doesn't know that). She panicked, rebooted the phone a bunch of times before giving it to me.
I was able to get into TWRP eventually, and figured I'd manually install the newest 3T firmware. This is what I did:
First, I updated TWRP through TWRP, to the most recent version. This was successful. Then, this happened:
Downloaded 4.1.7 from the OnePlus website
Placed it on the phone's internal storage
Went into TWRP, wiped Dalvik, Cache, System etc. (leaving Internal Storage in tact)
Flashed the firmware
I've done this thousands of times, never fails. Except now.
After flashing (which was supposedly successful, as I did not receive error messages), I hit 'reboot' and TWRP told me 'NO OS INSTALLED - WANT TO REBOOT ANYWAY?'
That is bad, right? So, I did not reboot, stayed in TWRP and ended up trying to wipe internal storage, thinking I could then add the .zip with the firmware again later and try flashing again. Just a clean phone, you know? I was wrong. I cannot copy anything to the phone right now, so I can't flash anything (because I can't put anything on the phone).
I'm trying to sideload things now through TWRP (adb sideload) and regular fastboot (either the firmware 4.1.7 or 4.1.6 - I've even tried flashing the stock recovery through fastboot to try and get the stock back, so I can sideload the firmware through there), but nothing works.
If anyone knows what to do, or can give me an outline on what to try, I'd be very helpful. The situation right now:
3T, without OS or ANYTHING on the phone
With functioning TWRP
Only recognized in the command prompt when in TWRP, not when in BOOTLOADER
Phone does not allow things to be copied to the phone via my laptop.
On behalf of my extremely upset wife, I thank you!
@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.
Siddk007 said:
@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.
Donaghy said:
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.
Click to expand...
Click to collapse
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Click to expand...
Click to collapse
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.
Donaghy said:
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.
Click to expand...
Click to collapse
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Click to expand...
Click to collapse
I don't own an OTG cable. The only USB option there is, is within the ADB menu in the recovery.
EDIT: locking the bootloader seemed to have made things worse, as I now cannot get the .zip files with the firmware on it to be accepted by ADB/the phone... God, this is a gigantic mess..
I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.
C3C076 said:
I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.
Click to expand...
Click to collapse
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.
Donaghy said:
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.
Click to expand...
Click to collapse
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Whichever is the most recent one that is on the OnePlus website. I downloaded the .img off of their website.
I've had a similar issue, and I tried a billion times on trying to reflash Stock OOS 4.1.0, and sadly nothing happened. I then tried LineageOS by SultanXDA, nada.
So then, I said "Scr*w my data, I'm going to start anew", and I tried the Unbrick Tool, and Voila, new phone with OOS 3.5.X. Not the latest, but it's working.
I suggest you try that mate, you can find it over here.
Cheers!
P.S. - Love your profile pic.
If you sucessfully flashed 4.1.7 then I'd just reboot into system. TWRP sometimes says "No OS installed" if /system was wiped prior to flashing.
Regardless, I recommend you do these things now (if you havent already) and report back:
-Unlock bootloader (fastboot oem unlock)
-Flash TWRP* recovery, not stock. (fastboot flash recovery twrp.img)
-Boot recovery (fastboot boot twrp.img)
-Wipe data + system + cache + dalvik from TWRP
-ADB sideload in advanced section of TWRP
-from your PC: "adb sideload oos417.zip"
-from TWRP: reboot into system (ignore "No OS installed")
If you follow this and its succesful, everything will be fixed
* flash the twrp by xda member eng.stk, not the official one: the only place I can find his TWRP is in the 3/3t toolkit zip. So extract the v5 zip and use the "TWRP_recovery.img": https://drive.google.com/drive/u/0/folders/0B1cephDrsyt_ZzJ1cXpUUlVhSzg
Edit: Instead of doing all this manually, you may want to use the toolkit. See if your device is recognised
Thanks for the help, everybody!
I used the unbrick tool, which worked! I got the phone 'alive' again.
New problem: Right after successfully booting the phone again, I set up the phone (so: clean install, no root, stock recovery, straight out of the box, you know what I mean) and then proceeded to download the OTA that OnePlus pushed to the phone (4.1.7). It downloaded quickly, but the installation has been stuck for almost an hour.
The phone says 'Updating, please wait - do not turn off your phone', and the blue bar is filling. Well, not filling, as it has been stuck at about 10% for an hour.
Is this normal? If not, what can I do? Thanks again!
I turned the phone off and was able to successfully sideload 4.1.7 via ADB. Upon updating, the phone gave me a notification (blue and white letters) that the "DECRYPTION IS UNSUCCESSFUL. The password you entered is correct, but you have to perform a factory reset to use your phone".
So I did another factory reset in recovery, rebooted, and it's up and running, with 4.1.7 on it! I can't believe we got it back from the dead. Thanks everyone, for your help! Really appreciate it!
1900-1 variant (Android One) with unlocked bootloader. Followed these instructions and it worked fine.
I then flashed TWRP and rebooted (did not install Magisk) and that's when the bootloops started. I was still able to get into TWRP, so I did a factory data reset since I didn't care about my data. Still looping.
Then I followed the first part of those instructions (flash to stock Oreo via fastboot)...still looping, and TWRP is gone. I can't seem to get into stock recovery using the vol+/pwr so I can do an adb sideload of Pie.
Thoughts?
I have a 1900-2 & there is no stock recovery. Go to bootloader & use commands "fastboot boot ((name of recovery img(twrp.img))".
There is several threads on booting out flashing recovery. I never installed the recovery to my phone because I've already seen this problem in other threads. I just use my PC to boot twrp when I need it.
rczrider said:
1900-1 variant (Android One) with unlocked bootloader. Followed these instructions and it worked fine.
I then flashed TWRP and rebooted (did not install Magisk) and that's when the bootloops started. I was still able to get into TWRP, so I did a factory data reset since I didn't care about my data. Still looping.
Then I followed the first part of those instructions (flash to stock Oreo via fastboot)...still looping, and TWRP is gone. I can't seem to get into stock recovery using the vol+/pwr so I can do an adb sideload of Pie.
Thoughts?
Click to expand...
Click to collapse
Download Pie full fastboot package. Check my previous post somewhere here.Then won't install TWRP, only boot to TWRP.
Comby_sk said:
Download Pie full fastboot package. Check my previous post somewhere here.Then won't install TWRP, only boot to TWRP.
Click to expand...
Click to collapse
Thanks! This link to Mega that you posted?
https://forum.xda-developers.com/showpost.php?p=78370069&postcount=5
Is that for the Android One (1900-1) variant? Although I don't suppose it really matters, since I'm not using it with Fi.
EDIT 1: well, it "worked" in that Pie would boot, but it's definitely not for the A1 and upon setup it can't find any wireless networks, so I'm assuming I need the A1 files. I did try to flash back to Oreo, but I'm bootlooping again.
EDIT 2: I flashed stock Oreo 8.1 again. I don't know if I was doing the key combination incorrectly to get into recovery (hold PWR and just once press VOL+) or I needed to flash Oreo again, but I could get into recovery. I tried flashing Pie again, but it failed since I (probably) needed to get the two Oreo OTAs (28.3.4 and 28.3.5) that have been released since the full image (28.3.3). I was, however, able to do a full factory data reset (including userdata and personalization) and that let me boot into Oreo! So I'll try the Pie thing again
EDIT 3: I booted back into Oreo and did the two OTAs. Since I wasn't rooted (only an unlocked bootloader), I did the Pie update via OTA and it worked fine.
No:
https://forum.xda-developers.com/showpost.php?p=78466061&postcount=102