Hey Guys,
The OTA zip uploaded here recently (for 820n) is for build 484493.5 only. It WILL NOT work for other build.
Please check your build.prop (/system/build.prop) before starting the OTA update for Lollipop. OTA update surely will fail if it doesn't match. Check the line in your build.prop:
Code:
ro.build.fingerprint=htc/a51ul_htc_europe/htc_a51ul:4.4.4/KTU84P/484493.5:user/release-keys
Anyone having the same build pls make a TWRP backup for system partition and upload (mega is preferred) here. It will help us to work for a custom build.
so you are saying official update wont install because phone system and htc did not checked which build I have before sending the update package?
because i had a failed update. so please explain, why this happens and what can be done to correct the issue. (noob alert)
Lollipop OTA update mostly patches the existing (KK) files in your system so that build signature and file hash has to be matched. Take a look of the below OTA script, it checks the Bluetooth.apk and apply the patch Bluetooth.apk.p if the hash matched.
sha1_check(read_file("system/app/Bluetooth/Bluetooth.apk"), e405b2ad3ec910b8644f566356d2a00f3fdde1f3) || assert(apply_patch("/system/app/Bluetooth.apk", "-", e405b2ad3ec910b8644f566356d2a00f3fdde1f3, 3512926, 855bb7bbd530a22da407e617374e7008039230c1, package_extract_file("patch/system/app/Bluetooth.apk.p")));
Ok so do you think is a solution to change finger print in build.prop with
ro.build.fingerprint=htc/a51ul_htc_europe/htc_a51ul:4.4.4/KTU84P/484493.5:user/release-keys and then to try to flash lollipop?
Partition structure has changed in Lollipop! Play with caution.
Kitkat:
Code:
lrwxrwxrwx root root 2015-05-08 11:19 recovery -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 2015-05-08 11:19 boot -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 2015-05-08 11:19 system -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 2015-05-08 11:19 userdata -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 2015-05-08 11:19 cache -> /dev/block/mmcblk0p41
. . .
Lollipop:
Code:
lrwxrwxrwx 1 root root 21 Oct 20 19:11 recovery -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Oct 20 19:11 boot -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Oct 20 19:11 userdata -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Oct 20 19:11 system -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Oct 20 19:11 cache -> /dev/block/mmcblk0p42
. . .
My Fingerprint matches but i cant install !!!!!
i checked the build.prop file , i searched for the line "ro.biuld.fingerprint" and it completely matches with the one you shows .
but when i try to boot into the bootloader for installing the update (after renaming the file and moving it to the sd card) i see a blue bar on the top-right side and under "Hboot" is see loading.
then the the plue bar go and a yellow one shows up and the loading word is gone and i see "Checking" instead. Then when the yellow bar finishes i see a red typing over the "checking" word that says "Press <POWER> to reboot". then i reboot and nothing changes , the same android , the same every thing . Sorry for taking to long but please tell me what to do !! I didn't do anything to the phone (no root , no bootloader unlock , no s-of) .... oh oh i forgot some thing when the update started i was downloading it from the "software updates" . it downloaded about 2 or 3 times , each time it says "download unsuccessful" but now when i try to go to "software updates" and try to check is says that there is no update for me ...... please help me !! Thanks in advance
5
medo2214 said:
i checked the build.prop file , i searched for the line "ro.biuld.fingerprint" and it completely matches with the one you shows .
but when i try to boot into the bootloader for installing the update (after renaming the file and moving it to the sd card) i see a blue bar on the top-right side and under "Hboot" is see loading.
then the the plue bar go and a yellow one shows up and the loading word is gone and i see "Checking" instead. Then when the yellow bar finishes i see a red typing over the "checking" word that says "Press <POWER> to reboot". then i reboot and nothing changes , the same android , the same every thing . Sorry for taking to long but please tell me what to do !! I didn't do anything to the phone (no root , no bootloader unlock , no s-of) .... oh oh i forgot some thing when the update started i was downloading it from the "software updates" . it downloaded about 2 or 3 times , each time it says "download unsuccessful" but now when i try to go to "software updates" and try to check is says that there is no update for me ...... please help me !! Thanks in advance
Click to expand...
Click to collapse
Settings application, all applications, Download Manager, clearing your cache and clear dannye.Posle, try to download updated.
vuk1963 said:
Settings application, all applications, Download Manager, clearing your cache and clear dannye.Posle, try to download updated.
Click to expand...
Click to collapse
i did this while ago and i did it again now but the same problem !! Thanks for your care
Related
I am currently stuck at the acer screen after using dd to update /dev/block/mmcblk0p3 and /dev/block/mmcblk0p6 to the image for 1.139.04
Logcat shows
I/Netd <Increasing number...> Netd 1.0 starting
You are most definitely not bricked.
Flash the Chinese update (update.acer.zip), do a search for the file. Rename as update.zip and copy it to the root of your microSD. Turn off tablet, then turn on holding the menu button closest to the power button. Don't let go of the volume button until you see some text in the same corner of the screen. After that it will update and restore the system to a working state. You will need to reroot, reflash system.img, reboot, and flexrom.img. You might need new kernel modules for wifi (search, they are available). You will also need Gingerbreak to, so copy it to the microSD. Also get an apk for a terminal if you need to do modifications directly on the tablet.
Good luck.
Hi There,
i've installed the update to Android 4.3. During the Update Process the Phone hung at the step "Apps werden gestartet" (Sorry, don't know what the correct english translation is). After 1 hour i've turned the power off und rebooted the phone, but the only thing i see is the Google Nexus "X".
My device had Stock Android and was not unlocked.
After that i want to get my files off the device.
I did the following:
Unlocked Bootloader with Nexus4 Toolkit
Booted into CWM through Toolkit to gain adb access (Option 10 in Toolkit) (adb access works but the N4 display shows a black screen)
adb.exe shell
ls /sdcard
ls /data/media
The problem is, that /data/media is empty:
Code:
~ # ls -lart /data/media
ls -lart /data/media
drwxr-xr-x 3 root root 0 Jan 1 00:00 ..
drwxr-xr-x 2 root root 0 Jan 1 00:00 .
~ #
How can i get my files off the phone?
Best regards!
If it rebooted after unlocking the Bootloader I'm afraid your data is gone and can't be retrieved as far as I know. Simply because unlocking the Bootloader wipes your device, fully, but only if it reboots after that.
Thanks for your reply... Not that what i wanted to heat..
I cant remember if the device has rebooted, but i have rebooted it.
Just to be sure: when i flash a stock image through the nexus toolkit, is there something to think about or is it just flashing and afterwards the device will Boot again?
s4ndst0rm2 said:
Thanks for your reply... Not that what i wanted to heat..
I cant remember if the device has rebooted, but i have rebooted it.
Just to be sure: when i flash a stock image through the nexus toolkit, is there something to think about or is it just flashing and afterwards the device will Boot again?
Click to expand...
Click to collapse
No, it's not that you rebooted it, the thing is your data will be gone *if* the phone is rebooted *right after* unlocking the Bootloader.
Anyways, at this point I would assume it is gone after all because you can't simply see it.
Also, I have never used any of the available toolkits and I don't recommend them either. Why? Well, for the very same exact reason you're posting here: you're not 100% sure about the process behind each action and if things go wrong you won't know how to solve them.
@MikeChannon removed OP. please close
what? lol
I'm away from PC for few days but if someone has luck with 1050l please update.
Sent from my YOGA Tablet 2-1050L using Tapatalk
This is awesome, to unlock the full potential of the tablet!
Works on my 1380F
Oh! I gave up on the unlock
Now, thank you for opening the possibilities!
Thank you! XD!
Worked on my already unlocked 1050F..... Bring on the fun people....
and the first tester prize goes to @workdowg ... as usual i might add
just when i was ready to write: come'on all of you dwarf 1050 owners
so we already have confirmation from 1050 (workdowg), i would say 99% it's the same on 830
again after you flash it you can leave it there (it's a good feeling to know that you have an unlocked bootloader)
and now the really important questions will follow:
- is this a permanent root?
- it already installs linux/windows or do i have to put my sdcard in?
- where's the link to the marshmallow cm rom ?
I succeeded. np (flashing, 1050F)
But how can I know that I had unlocked? (how to check?)
neverapple88 said:
I succeeded. np (flashing, 1050F)
But how can I know that I had unlocked? (how to check?)
Click to expand...
Click to collapse
if it boots up to Android AFTER you flashed the patched esp image then you are
it allows whatever boot image (in boot or fastboot or recovery partition) to be loaded without being checked for valid signature (ie you can modify your boot images from now on and flash them and you will no longer get the "verification failed" error message that a locked bootloader would give)
ionioni said:
if it boots up to Android AFTER you flashed the patched esp image then you are
it allows whatever boot image (in boot or fastboot or recovery partition) to be loaded without being checked for valid signature (ie you can modify your boot images from now on and flash them and you will no longer get the "verification failed" error message that a locked bootloader would give)
Click to expand...
Click to collapse
Thank you! :victory:
neverapple88 said:
Thank you! :victory:
Click to expand...
Click to collapse
if you really want to test with some more tangible result (the already tested) extract then flash the attached file, boot to fastboot and flash with
fastboot flash boot boot-selinux-permissive.img
it will make your selinux permissive ie log & ALLOW operations that are violating the selinux policy. the original stock has selinux in enforcing mode ie log & BLOCK
before you flash the modded boot image open an adb shell and check the selinux mode, input
getenforce (it should output enforcing)
now go to fastboot and flash the modded image as per above instructed, reboot and enter in the same command
getenforce (should output permissive now)
there you go... on a locked bootloader it would have hang on boot start after you flashed the modded image with some verification failed error message (and it's true, the modded image is by no way digitally signed )
ps. this is made from a stock 1050f boot image so it works/testing on 1050f only (the other 830 and 1380 models will most likely hang on boot or at least blank the screen due to different configurations in the original images, but it's the same concept, this is made at the special request of our korean guy)
ionioni said:
if you really want to test with some more tangible result (the already tested) extract then flash the attached file, boot to fastboot and flash with
fastboot flash boot boot-selinux-permissive.img
it will make your selinux permissive ie log & ALLOW operations that are violating the selinux policy. the original stock has selinux in enforcing mode ie log & BLOCK
before you flash the modded boot image open an adb shell and check the selinux mode, input
getenforce (it should output enforcing)
now go to fastboot and flash the modded image as per above instructed, reboot and enter in the same command
getenforce (should output permissive now)
there you go... on a locked bootloader it would have hang on boot start after you flashed the modded image with some verification failed error message (and it's true, the modded image is by no way digitally signed )
ps. this is made from a stock 1050f boot image so it works/testing on 1050f only (the other 830 and 1380 models will most likely hang on boot or at least blank the screen due to different configurations in the original images, but it's the same concept, this is made at the special request of our korean guy)
Click to expand...
Click to collapse
Thank you for your time.
Test and english search(?) success!
ps. (After the test, find) I've used this app for security : SELinuxModeChanger
Any chance this could be modified for yt3?
Worked on my 1050f. Thanks!
Patched image booting fine on my 1050f.
Thanks
What's droidboot.img?
The original disk contains no droidboot:
Number Start End Size File system Name Flags
1 20.5kB 8409kB 8389kB reserved msftdata
2 8409kB 43.0MB 34.6MB fat32 ESP boot, esp
3 43.0MB 59.8MB 16.8MB boot msftdata
4 59.8MB 80.8MB 21.0MB recovery msftdata
5 80.8MB 97.5MB 16.8MB fastboot msftdata
6 97.5MB 106MB 8389kB reserved_1 msftdata
7 106MB 139MB 33.6MB panic msftdata
8 139MB 676MB 537MB ext4 factory msftdata
9 676MB 685MB 8389kB misc msftdata
10 685MB 819MB 134MB ext4 config msftdata
11 819MB 953MB 134MB ext4 cache msftdata
12 953MB 1222MB 268MB ext4 logs msftdata
13 1222MB 3369MB 2147MB ext4 system msftdata
14 3369MB 31.3GB 27.9GB ext4 data msftdata
Click to expand...
Click to collapse
cocacola2015 said:
What's droidboot.img?
The original disk contains no droidboot:
Click to expand...
Click to collapse
Fastboot
From my LG-G4, Rooted running Stock 5.1
---------- Post added at 01:57 AM ---------- Previous post was at 01:54 AM ----------
workdowg said:
Fastboot
From my LG-G4, Rooted running Stock 5.1
Click to expand...
Click to collapse
And it changed significantly from kit Kat to lollipop.
From my LG-G4, Rooted running Stock 5.1
ionioni said:
if you really want to test with some more tangible result (the already tested) extract then flash the attached file, boot to fastboot and flash with
fastboot flash boot boot-selinux-permissive.img
it will make your selinux permissive ie log & ALLOW operations that are violating the selinux policy. the original stock has selinux in enforcing mode ie log & BLOCK
before you flash the modded boot image open an adb shell and check the selinux mode, input
getenforce (it should output enforcing)
now go to fastboot and flash the modded image as per above instructed, reboot and enter in the same command
getenforce (should output permissive now)
there you go... on a locked bootloader it would have hang on boot start after you flashed the modded image with some verification failed error message (and it's true, the modded image is by no way digitally signed )
ps. this is made from a stock 1050f boot image so it works/testing on 1050f only (the other 830 and 1380 models will most likely hang on boot or at least blank the screen due to different configurations in the original images, but it's the same concept, this is made at the special request of our korean guy)
Click to expand...
Click to collapse
Awesome! I flashed it on my 1050f and it is now finally unlocked and the SELINUX stuff has been successfully tested as well!
I really hope that finally some great custom rom's might get released sooner than later.
Your work was hidden for a while - but finally you decided to make it public.
I was so frustrated about the bootloader policy and the missing possibilities an Android device usually offers. But I see light at the end of the tunnel. Looking forward to see also your work on AoL and other great stuff.
You guys are really the Yoga 2 heroes!
So does this mean we can now get a permanent recovery?
Can you post video guide? Thank's.
pateken said:
Can you post video guide? Thank's.
Click to expand...
Click to collapse
Please don't take this wrong... His instructions are pretty straight forward (1,2,3)... If you don't understand them you may not want to start messing with your tablet like this. Rooting is more than enough for the average user (See HERE for Windows based rooting and HERE for Linux based rooting)...
Hi guys, i've flashed LineageOS ROM, TWRP and MAGISK successfully but when i saw a website offering SystemUI mod, i downloaded the zip , mounted and gotten an error for wrong version. Frustrated, i choose to wipe data, cache and dalvik to resolve but got myself into deeper trouble. Now it's stuck on Bootloop of Death. I am, however, able to load into TWRP custom recovery and the Bootloader is unlocked, when i connect phone to PC by USB, there's sound alert that it's connected but ADB and Fastboot couldn't detect the devices.
Hence i can't push any installation file into the Internal storage because ADB doesn't detect devices and ADB sideload doesn't work.
When i atttempt to initiate ADB sideload, it states " Failed to mount '/system' ( Invalid argument). My suspicion is that somehow System partition is wiped. When i try to reboot, it says " NO OS, are you sure you want to reboot? "
Please advice! Help much needed
Try this. Go to Wipe -> Advanced Wipe -> Select System -> go to Repair or Change File System -> then go to Change File System -> transform to FAT -> slide to confirm -> transform to EXT4 -> slide to confirm.
Hi Folkz,
the rollout for 11.0.3.4. begins.
I've already downloaded 11.0.3.4 KB05BA (EU) via Oxygen Updater.
Here is a Link to a Post someone in official OPForums who provided a GDrive Link -> https://forums.oneplus.com/threads/...-the-oneplus-8t.1338403/page-34#post-22346201
I will install it now and then I give feedback (rooting etc.).
greetings rage
P.S. Please feel free to add OOS Update News for OP8T (all Variants) here in this Thread.
Okay... installed it already with no problems and root persists... looks great so far.
This is how I did the update:
1. Download FULL Update (e.g. via OxygenUpdater)
2. Install the update via "Settings->System->Systemupdates->Local Upgrade"
3. DO NOT REBOOT!!
4. Open Magisk Manager
5. Tap "Install" (Magisk) and select -> "Install to Inactive Slot (After OTA)" and install magisk to inactive slot
6. Reboot
7. Enjoy updated OOS with active root
greetings rage
Further Information:
* I used latest magisk canary version dc5e78e1 (21006) from here -> https://github.com/topjohnwu/magisk_files/tree/canary
* SafetyNet checks are sucessfull
I've already patched the boot.img with latest magisk canary, if you need it. -> https://forum.xda-developers.com/on...-to-root-oneplus8t-kb2001-t4178675/page15#146
is it just me, or fastboot dont work anymore - i get no connection in fastboot mode after this update ('fastboot devices' never show the device).
edit: but adb in recovery works (without proper adb rights of course, but adb devices shows the device)
ChillDuder said:
is it just me, or fastboot dont work anymore - i get no connection in fastboot mode after this update ('fastboot devices' never show the device).
edit: but adb in recovery works (without proper adb rights of course, but adb devices shows the device)
Click to expand...
Click to collapse
...I think it's just for you. I tried it and "fastboot devices" and "fastboot reboot" works.
Hint: If you use Windows PowerShell, the command looks like this (if you start PowerShell in the same directory where fastboot.exe is located) ->
Code:
.\fastboot.exe devices
greetings rage
rage302 said:
Okay... installed it already with no problems and root persits... looks great so far.
This is how I did the update:
1. Download FULL Update (e.g. via OxygenUpdater)
2. Install the update via "Settings->System->Systemupdates->Local Upgrade"
3. DO NOT REBOOT!!
4. Open Magisk Manager
5. Tap "Install" (Magisk) and select -> "Install to Inactive Slot (After OTA)" and install magisk to inactive slot
6. Reboot
7. Enjoy updated OOS with active root
greetings rage
Click to expand...
Click to collapse
Like an idiot i rebooted before reinstalling Magisk. Patching boot images does not work anymore (fastboot locks on "fastboot mode" logo).
Any hint?
Scrambler77 said:
Like an idiot i rebooted before reinstalling Magisk. Patching boot images does not work anymore (fastboot locks on "fastboot mode" logo).
Any hint?
Click to expand...
Click to collapse
You can try to boot the other/untouched slot with this command in fastboot mode (if applicable):
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
...depending on which bootslot you are at the moment.
If this doesn't work you can try to boot my magisk_patched_boot.img form here -> https://forum.xda-developers.com/on...-to-root-oneplus8t-kb2001-t4178675/page15#146
with this command:
Code:
fastboot boot magisk_patched.img
Or you can dump your own boot.img and patch it via magisk by your own (but I think you tried this already?)
If nothing helps you can use the Unbrick Tool from here -> https://forum.xda-developers.com/oneplus-8t/how-to/op8t-unbrick-tool-to-restore-device-to-t4180837
greetings rage
rage302 said:
You can try to boot the other/untouched slot with this command in fastboot mode (if applicable):
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
...depending on which bootslot you are at the moment.
If this doesn't work you can try to boot my magisk_patched_boot.img form here -> https://forum.xda-developers.com/on...-to-root-oneplus8t-kb2001-t4178675/page15#146
with this command:
Code:
fastboot boot magisk_patched.img
Or you can dump your own boot.img and patch it via magisk by your own (but I think you tried this already?)
If nothing helps you can use the Unbrick Tool from here -> https://forum.xda-developers.com/oneplus-8t/how-to/op8t-unbrick-tool-to-restore-device-to-t4180837
greetings rage
Click to expand...
Click to collapse
Done it! Many thanks!
I couldn't get the OTA file for my variant. So, this is what I had to do to get it installed.
1. Open Magisk Manager -> Uninstall Magisk -> Restore Images
2. Don't reboot.
3. Take the OTA from Settings -> System -> System Updates
4. Don't reboot.
5. Open Magisk Manager -> Install Magisk -> Install To Inactive Slot
6. Reboot.
7. Your phone should be updated with Magisk still installed.
Next Update 11.0.4.5 is on it's way >
https://forums.oneplus.com/threads/oxygenos-11-0-4-5-for-the-oneplus-8t.1342473/
https://m.gsmarena.com/oxygenos_110...ls_out_with_11_different_fixes-news-46278.php
https://www.xda-developers.com/oneplus-8t-oxygenos-11-0-4-5-update/
Changelog
System
* Optimized the call stability
* Improved system power consumption performance to reduce heating
* Improved mis-touch prevention to offer better gaming experience
* Optimized fluidity with some mainstream games to reduce lagging risks
* Optimized user experience with Alert Slider by adding toast messages when switching among the 3 modes
* Fixed the issue that the status bar kept hovering on the screen in landscape mode
* Fixed the issue that NFC cannot be turned on in a small probability
Camera
* Optimized the imaging effect to bring you with better shooting experience
* Improved camera stability
Network
* Optimized mobile network connection to improve the network intensity with signal
* Fixed the small probability issue with network interruption while playing games
Click to expand...
Click to collapse
It is just a hot-fix update, so the changelog is nearly the same than 11.0.3.4.
Rollout for OOS 11.0.4.5 KB05BA (EU Version) begins.
Available via Oxygen Updater and here is the direct FULL OTA Link:
https://otafsg1.h2os.com/patch/amaz...gen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip (Source)
greetings rage
---UPDATE---
I've sucessfully upgraded to 11.0.4.5 KB05BA with keeping root and SafetyNet pass,
with my standard method -> https://forum.xda-developers.com/oneplus-8t/how-to/update-thread-t4188149#2
greetings rage
rage302 said:
Rollout for OOS 11.0.4.5 KB05BA (EU Version) begins.
Available via Oxygen Updater and here is the direct FULL OTA Link:
https://otafsg1.h2os.com/patch/amaz...gen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip (Source)
greetings rage
Click to expand...
Click to collapse
Lol, updated shortly before your post. First update post root and went flawlessly.
Sent from my OnePlus8T using XDA Labs
Is there a link for the AA version? I'm getting the "Installation problem" inherent with unlocked bootloaders
ChillDuder said:
is it just me, or fastboot dont work anymore - i get no connection in fastboot mode after this update ('fastboot devices' never show the device).
edit: but adb in recovery works (without proper adb rights of course, but adb devices shows the device)
Click to expand...
Click to collapse
This happened to me on first try.
Installed the Oneplus usb drivers
rebooted
All is well thereafter
blackknightavalon said:
Is there a link for the AA version? I'm getting the "Installation problem" inherent with unlocked bootloaders
Click to expand...
Click to collapse
It's on Oxygen Updater
Sent from my unknown using Tapatalk
Would be nice if OnePlus would release a Full OTA for us Global Model users, this Incremental mess is making things a pain.
@blackknightavalon and @Keinta15 I too am getting install failed. I'm betting I will need to MSMDownloadTool the phone, upgrade to 11.0.4.5 then Unlock Bootloader and root it.
card13 said:
Would be nice if OnePlus would release a Full OTA for us Global Model users, this Incremental mess is making things a pain.
@blackknightavalon and @Keinta15 I too am getting install failed. I'm betting I will need to MSMDownloadTool the phone, upgrade to 11.0.4.5 then Unlock Bootloader and root it.
Click to expand...
Click to collapse
If you're rooted you need to unroot before updating
Sent from my unknown using Tapatalk
@Keinta15 Right...? Which I have already done, then I get a Crashdump (dm-verity device corrupted force dump kernel_restart) and both slots no longer boot. All of which could be solved if there was full flash file and not a 300MB Incremental OTA.
card13 said:
@Keinta15 Right...? Which I have already done, then I get a Crashdump (dm-verity device corrupted force dump kernel_restart) and both slots no longer boot. All of which could be solved if there was full flash file and not a 300MB Incremental OTA.
Click to expand...
Click to collapse
Did you flash the 11.0.2.3 incremental in the past?
@g96818 I was able to flash 11.0.1.2 Incremental, 11.0.3.4 and 11.0.4.5 have both failed, with the exact same process I used to get 11.0.1.2 installed (unroot -> reboot -> install update -> boot patched boot img -> dd boot.img backup -> patch img -> boot to newly patched img -> direct install root).
****EDIT #1****
Looks like switching boot slots was a really bad idea and I irritated my phone. It's in a bootloop. "Boot reason: init_user0-failed unable to parse kernel log. For more debug information, adb pull /mnt/vendor/op2/rbr_log or pull op2.img".
***Edit #2****
Well that didn't go as planned. Tried to Factory Reset, still got install failed. Then locked the bootloader to see if it would installed and got stuck on DM-Verity Device Corrupted screen. Ended up using MSM to restore then update to 11.0.4.5. Good thing I was doing every couple days backups with SwiftBackup.