Database Info

I'm stuck trying to flash a GSI, I can't figure what I'm doing wrong

Hi!
I'd like to get rid of the HTC original firmware on my U12+.
I just tried to flash GSIs of LineageOS 17 by AndyYan then AOSP 10.0 by phhusson, without luck.
I have a factory unlocked HTC U12+ (fastboot mode showing Secure Boot : Development, Secure State : S-Off, Device State : Unlocked(U)) so I went straight to the "flash GSI without TWRP" part of the official XDA tutorial: I factory reset the phone, rebooted in bootloader, then erased system and successfully flashed lineage-17.0-20191117-UNOFFICIAL-treble_arm64_avN.img.
But after reboot, I got a bootloop.
I've wanted to try the TWRP method, but upon launch it asked my password for decryption. While I'm sure of the code I've used and typed, decryption doesn't work, so TWRP didn't help.
Then I've flashed the AOSP GSI via fastboot, but then I got a "This device is corrupt. It can't be trusted and will not boot" error message.
So as suggested on another thread I've used the SD card method to flash a RUU, specifically 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_HTC_Europe_1.30.401.2_Radio_sdm845-000201b-1807311356_release_528103_signed_2_4.zip. It flashed successfully, but then it booted to the static white HTC logo on black background and stayed there for 20 min.
I can still boot to fastboot mode/download mode, but I don't know what to do.
I can't figure what I'm doing wrong, can you help me, please?

After another attempt I've managed to go back full stock using the microSD card method.
Then I've been able to boot TWRP, which first showed a "Mount" "Decrypt data" screen, asking for a password. The 6 digits code I've used previously doesn't work. So TWRP "failed to decrypt data", also was "unable to mount storage" and "failed to unmount /system_root (device or resource busy)". As suggested, I formatted/wiped data to remove encryption.
Then I performed a factory reset, adb pushed system-quack-arm64-ab-vanilla.img to /data, then flashed it successfully to the system partition, as requested in the afore mentioned official tutorial. On reboot I get another bootloop. Bootscreens shows the HTC and Powered by Android wordmarks and also "** ORANGE **" on the top left corner of the screen.
What am I missing?! :-/

After first boot of flashed RUU at the HTC logo reboot the device. Got there myself, rebooted(using power button) and the OS booted up perfectly.
TWRP doesn't decrypt latest Pie with July Patch. So you will not decrypt it. (Wiping does not decrypt).
I used temporary TWRP, flashed permanent (with touchscreen patch), installed Magisk, Rooted, installed LeeDroid from Magisk for example.
Make sure you have a correct RUU for your CID version.
I am not sure how a project treble ROM will work on this device. You still need signed HTC drivers. I don't think we are ready now for 10 on this device for daily use. HTC did quite awful with the Pie update and many bugs are still not fixed after 6 months.

GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
I was unable to determine CID and MID yesterday from fastboot mode or TWRP, so I've downloaded the latest RUU for dual SIM and EMEA model, as my U12+ is dual SIM and I live in Europe.
Now that the phone is back to full stock, I just installed a terminal app right on the phone and executed the following:
getprop ro.cid : 11111111
getprop ro.boot.mid : empty
I understand that the phone is "SuperCID", but I don't really understand what that implies.
Regarding Treble, Treble Info by Hackintosh Five reports (translated from French by me): "Your device supports the old Project Treble version, using VNDK version 26.0."
But the U12+ is listed as supported on phhusson's wiki. A few issues are listed, but I'm fine with them.
I've read a tutorial that asks to "extract the GSI and vendor+boot zips", but then doesn't what to do with the vendor+boot zips. Do you know?
Lastly, do you know what the **GREEN** or **ORANGE** overlay means on the boot screen?
Thank you for your help!

Romano2K said:
GSI tutorials advise against rooting before flashing. They advise to keep the phone full stock. What do you think about this?
Thank you for your help!
Click to expand...
Click to collapse
SuperCID implies you can install any RUU (not specific CID). So you can "transform" your US version into european or asian... for a specific reason. No need to do that. Usually there was a specific base that was needed to install a custom ROM or Custom Recovery or people just wanted a different version because they lived in a different part of the world from where the phone was purposed.
I am guessing the **GREEN*** overlay has smth to do with the RUU (if it's embedded in the Boot animation zip (basically pictures+ sound)) or has smth to do with the nature of your tempering (S-OFF/SuperCid etc.)
with this device and serves as a warning for users/devs/internal testing.
You should find your answers on a different section. More active. I see no activity here. And it's HTC's fault for dying" on us. I myself bought the U12 just to own (probably) the last flaghsip device they make. Here's to the comeback.... but I am not sure it will be real. HTC was one of the fastest to update, for example.. until 2019. We are still with bugs and on the July patch. Right not, in reality I am just hoping for one last Pie update to fix bugs and that's it. Will give this device a 1 year run and buy something better.
So go to the Android general section where you can ask how can you compile your ROM on this device. They should help. I can not offer sufficient knowhow on this topic.

Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!

Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Interesting. Will look into your tutorial. So thank you. If the boot animation.zip was modified you will find in in root/system/[search for it] -you can lookup up each image that forms the animation to check. I myself modified the ZIP to not include the annoying audio, so i deleted it. )
So is the GSI good for daily use? I would mess around with it until i sell my HTC U11. Still using the U11 as a daily driver for the past 2 weeks. And by selling it i mean practically giving a perfectly good phone away for scrap... because it's old.

Deonix said:
I myself modified the ZIP to not include the annoying audio, so i deleted it.
Click to expand...
Click to collapse
That's clever! The HTC boot sound was annoying when I had trouble booting the bootloader, because of the tactile buttons.
Deonix said:
So is the GSI good for daily use?
Click to expand...
Click to collapse
At this point I have a big problem with AOSP 10.0: brightness is blocked at 100%. There's a workaround involving adb, but for some reason adb isn't working with this firmware, even though I've activated developer options and USB debugging. I haven't had the time to tinker yet, I'll give it a try asap and I'll report back!
Thank you again for your help

Romano2K said:
Thank you for these clarifications
The **GREEN** or **ORANGE** overlay is shown for a few seconds on the vendor logo, before boot animation. It wasn't showing before I started messing with firmwares, but nevermind
Yes unfortunately HTC is kind of dead on the smartphone front. They deserved it at the end, U12 Plus' firmware is badly translated and full of bloatware. I've been a long fan, I've had four Orange branded Windows Mobile phones and PDA phones from 2002 (17 years ago!) to 2007, then a few Android smartphones (HTC Desire <3), so I think it's sad.
Anyway I've been able to flash AOSP 10.0 GSI by phhusson with his help.
So I've just shared a quick tutorial:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-install-generic-image-gsi-t4019151
Thank you for your help Deonix!
Click to expand...
Click to collapse
Did Bluetooth work for you on AOSP? Tried to install a few GSIs over the last couple of days but I cannot get Bluetooth working for calls or media. Apparently it's a known issue but none of the fixes I can find here on the forums seem to work for me. Just wondered what your experience was on another U12. I even tried your guide but still no Bluetooth for me.

Useful post about the GREEN message.

[Huawei P20] getting root on AOSP 10 Preview 2

After several days reading into topic, many tries, (including bricking and unbricking my P20 two times down to fastboot access only..), I still not at my goal: Taking full ownership aka. get root of slick & clean device.
Thanks to @OldDroid and his crew (THX!) now I have a working AOSP 10 Preview 2. It was flashed over a fully working EML-L29 9.0.0.293 (C432E7R1P11), bootloader & FRP unlocked, installed from eRecovery internal download(after second brick..) Thankfully I refused to update to 9.1 before due to /system read-only problems i red about. So everything, including recovery should be genuine. I will try to keep all the Google inside an Island and restrict it as far as possible with firewall.
Now I question myself how I can obtain root without bricking this wonderful machine again. I guess I will need Canary Magisk Manager from this link:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Switching channel to canary too, going the recovery_ramdisk patching route. (TWRP I already miss you!!)
I already downloaded EML-LGRP2-OVS 9.0.0.293 (FullOTA-MF) via Firmwarefinder to extract recovery_ramdisk from it. As I only flashed system I guess this should be the version I need to patch with Magisk?
I know, this is pretty unknown territory, but on OmniROM 5 beta I the non working touchscreen bug. Would give it a second try if there is no other way, maybe starting from a lower EMUI 9 version? If anybody could confirm my plan, or tell me its rubbish, I would be thankful.
@mods: This whole Treble thing makes it quite confusing, if you believe this post would get more attention in another place, feel free to move it. thx!

My first attempt at rooting a OnePlus 7 Pro has made my phone unusable [EPIC FAIL]

I followed a tutorial by Max on XDA's youtube channel (I'm a new user so unfortunately I cannot provide the link but I'm sure you can find it if you wish)
First mistake was going into this thinking it was a simple process to unlock bootloader, install TWRP, and root with Magisk . . .
Anyways I was looking for the fast boot files linked in the description of the video (my build number is 10.3.4 GM21AA) But could not find any past 10.0.5 (which was the most recent uploaded). [Cannot post the link however it is posted on androidfilehost]
I decided to go with the 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT.zip file, i dug into the images.zip folder to find the boot.img file (which is the one I used in my rooting process)
I followed the steps exactly as Max did them in his video but ended up with no camera working, no cellular network, cannot toggle the wifi on, no sound through speakers . . . now suddenly my phone has become a standard wallpaper background and nothing else.
Freaking out (but also I should've known what i was getting into being as naive as I am) I contacted OnePlus Support which basically told me my warranty is void now . . .
I guess I have no choice but to figure out how to root this properly or my 1000$ phone goes into the trash
Do I need to find the boot.img file for the One Plus 7 Pro Oxygen 10.3.4 GM21AA? Was that the mistake I made that messed up everything by deciding to flash the wrong boot.img
Any help is much appreciated!
Thanks guys!

https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/amp/

GeekMcLeod said:
https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/amp/
Click to expand...
Click to collapse
Thanks for your rapid response however that doesn't seem to do it for me I still cannot access camera, wifi, phone calling, and there is no sound . . .
[EDIT] I think I have discovered the problem however I do not know how to fix it. I flashed the wrong boot img file. Issue is that I do not know where to find the boot.img for 10.3.4

The best medicine against such issues is to MSM tool. I'm using you have the 1917, 1910 models i.e. the global editions and not the EU version. If you have EU version, I don't know if the MSM tool will work. Next, if you have successfully complete the MSM setup, then you can go about rooting the device by following this tutorial https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
On a side note, I have been swinging between root and full stock and frankly I don't see the real need to root the device. Stock unrooted OOS is really a good OS and rooting really doesn't add much value IMO.
rapurepie said:
I followed a tutorial by Max on XDA's youtube channel (I'm a new user so unfortunately I cannot provide the link but I'm sure you can find it if you wish)
First mistake was going into this thinking it was a simple process to unlock bootloader, install TWRP, and root with Magisk . . .
Anyways I was looking for the fast boot files linked in the description of the video (my build number is 10.3.4 GM21AA) But could not find any past 10.0.5 (which was the most recent uploaded). [Cannot post the link however it is posted on androidfilehost]
I decided to go with the 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT.zip file, i dug into the images.zip folder to find the boot.img file (which is the one I used in my rooting process)
I followed the steps exactly as Max did them in his video but ended up with no camera working, no cellular network, cannot toggle the wifi on, no sound through speakers . . . now suddenly my phone has become a standard wallpaper background and nothing else.
Freaking out (but also I should've known what i was getting into being as naive as I am) I contacted OnePlus Support which basically told me my warranty is void now . . .
I guess I have no choice but to figure out how to root this properly or my 1000$ phone goes into the trash
Do I need to find the boot.img file for the One Plus 7 Pro Oxygen 10.3.4 GM21AA? Was that the mistake I made that messed up everything by deciding to flash the wrong boot.img
Any help is much appreciated!
Thanks guys!
Click to expand...
Click to collapse

Roll back to 10.3.3 and use the patched boot.img from here: https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345

Thanks everyone. I finally solved the issue

From what I know, it's practically impossible to brick a Onleplus, I lost two Samsung's, and a LG, relocking bootloader while rooted, rushing to get the phone up, and forgetting to uninstall Magisk, TWRP, haven't ever had that problem with OnePlus or Xiaomi devices though. I've relocked this bootloader a couple of times while rooted, and nothing happened. Root is still very necessary for me, I don't buy anything I can't hack. I just noticed icon burn-in on my notifications bar, really pissed.

Is there a SUPER NOOB thread anywhere to help me with my 7 Pro??

Hello Everyone.
Been rooting since my first HTC Hero- never thought of myself as a noob until this One Plus 7 Pro! Its the US/Global unlocked model. This thing is KILLING ME!
I've followed about 5 different "rooting for beginners" threads from different sites and I still cannot get a basic, working root. I have unlocked bootloader with no issue.
I've had fastboot bootloops, lineage OS bootloops, stock Rom bootloops, stock rom booting up but wifi did not work. I've tried everything on Oxygen 9 and 10 (using the respective TWRP). I've used official and unofficial TWRPs, different versions of Magisk.
I've used the msm tool to reset this thing about 7 times! So as you can see, I'm at a loss.
The only thing I can think of is that I'm screwing something up as it relates to TWRP and Magisk and my flashing/booting process with the A/B slot stuff. Read threads on the benefits of A/B phones...but since I'm having so much trouble, I hate it!
Overall my goal is to get a stock rom rooted; but I couldn't resolve the no wifi toggle issue. I read on one thread that I just needed to flash a custom kernel. If that is the only actual fix, then I should be good to go, but I'm skeptical and figured I messed something up.
So like my title says - Is there any thread out there that someone can refer me to?
Thanks in advance.

Bruce777 said:
Hello Everyone.
Been rooting since my first HTC Hero- never thought of myself as a noob until this One Plus 7 Pro! Its the US/Global unlocked model. This thing is KILLING ME!
I've followed about 5 different "rooting for beginners" threads from different sites and I still cannot get a basic, working root. I have unlocked bootloader with no issue.
I've had fastboot bootloops, lineage OS bootloops, stock Rom bootloops, stock rom booting up but wifi did not work. I've tried everything on Oxygen 9 and 10 (using the respective TWRP). I've used official and unofficial TWRPs, different versions of Magisk.
I've used the msm tool to reset this thing about 7 times! So as you can see, I'm at a loss.
The only thing I can think of is that I'm screwing something up as it relates to TWRP and Magisk and my flashing/booting process with the A/B slot stuff. Read threads on the benefits of A/B phones...but since I'm having so much trouble, I hate it!
Overall my goal is to get a stock rom rooted; but I couldn't resolve the no wifi toggle issue. I read on one thread that I just needed to flash a custom kernel. If that is the only actual fix, then I should be good to go, but I'm skeptical and figured I messed something up.
So like my title says - Is there any thread out there that someone can refer me to?
Thanks in advance.
Click to expand...
Click to collapse
What version of the is are you on right now

I just reset with the msm tool, so it's back to OOS 9.5.3GM21AA.
It will take OTA updates fine up until before the 11 beta
My model is GM1917 (12GB RAM + 256GB ROM)

Bruce777 said:
Hello Everyone.
Been rooting since my first HTC Hero- never thought of myself as a noob until this One Plus 7 Pro! Its the US/Global unlocked model. This thing is KILLING ME!
I've followed about 5 different "rooting for beginners" threads from different sites and I still cannot get a basic, working root. I have unlocked bootloader with no issue.
I've had fastboot bootloops, lineage OS bootloops, stock Rom bootloops, stock rom booting up but wifi did not work. I've tried everything on Oxygen 9 and 10 (using the respective TWRP). I've used official and unofficial TWRPs, different versions of Magisk.
I've used the msm tool to reset this thing about 7 times! So as you can see, I'm at a loss.
The only thing I can think of is that I'm screwing something up as it relates to TWRP and Magisk and my flashing/booting process with the A/B slot stuff. Read threads on the benefits of A/B phones...but since I'm having so much trouble, I hate it!
Overall my goal is to get a stock rom rooted; but I couldn't resolve the no wifi toggle issue. I read on one thread that I just needed to flash a custom kernel. If that is the only actual fix, then I should be good to go, but I'm skeptical and figured I messed something up.
So like my title says - Is there any thread out there that someone can refer me to?
Thanks in advance.
Click to expand...
Click to collapse
If you are still on Android 10,take a look at the following guide.
[Guide] [Android 9/10] [7/7Pro] Unlock, TWRP, Root, and Update
------------------------------------------ Latest update to guide: Jul. 5, 2020 ------------------------------------------ Hi everyone! Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides...
forum.xda-developers.com

Gr8man001 said:
If you are still on Android 10,take a look at the following guide.
[Guide] [Android 9/10] [7/7Pro] Unlock, TWRP, Root, and Update
------------------------------------------ Latest update to guide: Jul. 5, 2020 ------------------------------------------ Hi everyone! Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides...
forum.xda-developers.com
Click to expand...
Click to collapse
I did that exact one a couple of times and when I get it back booted into stock the Wi-Fi does not work. The toggle stays in the off position.

Gr8man001 said:
If you are still on Android 10,take a look at the following guide.
[Guide] [Android 9/10] [7/7Pro] Unlock, TWRP, Root, and Update
------------------------------------------ Latest update to guide: Jul. 5, 2020 ------------------------------------------ Hi everyone! Many users browse these forums coming from Google or YouTube and have trouble navigating between many guides...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks Gr8man001.
Thought I had done this guide before and done it correctly but I buckled down and tried it once more (slow as molasses) and was able to get twrp and root! Appreciate it.

How to sideload into OP 8T (KB05AA)? Help!

My current OxygenOS is the latest "12" version which after the OTA, OnePlus has strangely removed from their support site. It has some issues I don't like as well as many others who have posted on the OP Community board. The inactive partition is corrupted and I'm not sure what happened except I was rooted and tried to use Magisk protocol to keep root, but I got a bootloop afterwards. I changed the active slot to the old slot and got the new "12" version running. The inactive slot is corrupted and I get a Qualcom error message.
I want to go back to the previous ver "11" or LineageOS 18.1. However, I cannot get anything to allow me to sideload to the inactive partition or any partition. If I use adb while the phone is in normal operation, I get adb to show devices so I know I have a link. However, I cannot do adb sideload from the normal booted phone. So I have to reboot it to recovery where it looses it's connection to the adb command on the PC. It sees the phone but says it is unauthorized. It is a loop where adb works while phone is booted but not when I am in recovery. I have USB debugging set on and have revoked usb debugging and reset the whole scenario many times to see if different sequences might work so that I can do a sideload. Nothing has gotten me past this yet. I have even tried the Oxygen Updater app but OxygenOS system update won't let you install a prior version if you have the current one.
Any suggestions. Thanks

zzjea said:
My current OxygenOS is the latest "12" version which after the OTA, OnePlus has strangely removed from their support site. It has some issues I don't like as well as many others who have posted on the OP Community board. The inactive partition is corrupted and I'm not sure what happened except I was rooted and tried to use Magisk protocol to keep root, but I got a bootloop afterwards. I changed the active slot to the old slot and got the new "12" version running. The inactive slot is corrupted and I get a Qualcom error message.
I want to go back to the previous ver "11" or LineageOS 18.1. However, I cannot get anything to allow me to sideload to the inactive partition or any partition. If I use adb while the phone is in normal operation, I get adb to show devices so I know I have a link. However, I cannot do adb sideload from the normal booted phone. So I have to reboot it to recovery where it looses it's connection to the adb command on the PC. It sees the phone but says it is unauthorized. It is a loop where adb works while phone is booted but not when I am in recovery. I have USB debugging set on and have revoked usb debugging and reset the whole scenario many times to see if different sequences might work so that I can do a sideload. Nothing has gotten me past this yet. I have even tried the Oxygen Updater app but OxygenOS system update won't let you install a prior version if you have the current one.
Any suggestions. Thanks
Click to expand...
Click to collapse
I've tried to sideload OOS 11 using Los recovery, but it doesn't work. And, since OOS recovery doesn't support sideloading I'd say that sideloading isn't an option.
However, using payload dumper and fastbootd may be an option. I would have tried this but I'm on 12 and there's no full install zip. But you're going back to 11 so this is a possibility.
But I wouldn't make these changes in the current working slot - don't break what's working.
I'm also not sure whether to use the OOS recovery for the fastbootd stuff or use one from a custom rom.
As you can gather, I've not done this. So you have to work out the details yourself and be prepared to be a guinea pig for the process.
If you do go down this path I'd be very interested in the outcome.
Of course, you could always use the MSM tool to go back to an older version.

Since there is no TWRP for OP8T and recovery is non-existent on it, how is anyone installing ROMs on this device. I have just jumped from my original purchase of OnePlus One that still works except for the power button (it is current with LineageOS 18.1 and rooted), to the OP8T over a month ago and a lot has changed since the OPO. I have looked up fastbootd but still don't understand the differences. Comments about installing ROMS are made all over this forum but most assume you know how to do it. I have gotten spoiled with TWRP on the OPO and can flash a new ROM in around a minute almost with my eyes closed. This is getting confusing. I successfully rooted this OP8T after I got it and that was a very touchy thing having to jump through a bunch of hoops to get it done. I was surprised that it worked after all the steps that were required. It used to be that there was info on how to do this kind of thing on this forum, but now it seems that most everyone thinks you should already know the basics. Well the basics are part of my problem right now. A and B slots are new to me and I think I understand that but have not seen an explanation of how that all works when loading ROMS. I have a working phone at the moment in the active slot, but the "other" slot is corrupted. I tried to duplicate the active slot to the inactive slot and of course I can't get adb to work.... Isn't anyone else having these issues? I will look into the MSM tool again.
If you know where the info is that I'm looking for is, please give me the links. Thanks

zzjea said:
Since there is no TWRP for OP8T and recovery is non-existent on it, how is anyone installing ROMs on this device. I have just jumped from my original purchase of OnePlus One that still works except for the power button (it is current with LineageOS 18.1 and rooted), to the OP8T over a month ago and a lot has changed since the OPO. I have looked up fastbootd but still don't understand the differences. Comments about installing ROMS are made all over this forum but most assume you know how to do it. I have gotten spoiled with TWRP on the OPO and can flash a new ROM in around a minute almost with my eyes closed. This is getting confusing. I successfully rooted this OP8T after I got it and that was a very touchy thing having to jump through a bunch of hoops to get it done. I was surprised that it worked after all the steps that were required. It used to be that there was info on how to do this kind of thing on this forum, but now it seems that most everyone thinks you should already know the basics. Well the basics are part of my problem right now. A and B slots are new to me and I think I understand that but have not seen an explanation of how that all works when loading ROMS. I have a working phone at the moment in the active slot, but the "other" slot is corrupted. I tried to duplicate the active slot to the inactive slot and of course I can't get adb to work.... Isn't anyone else having these issues? I will look into the MSM tool again.
If you know where the info is that I'm looking for is, please give me the links. Thanks
Click to expand...
Click to collapse
I presume that A and B slots are partitions
Code:
lrwxrwxrwx 1 root root 16 1970-01-03 04:30 /dev/block/bootdevice/by-name/boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-03 04:30 /dev/block/bootdevice/by-name/boot_b -> /dev/block/sde35
So try using MSM tool to restore them or find a copy of that partition from a working phone and flash on yours.
Maybe this can help you as well.

zzjea said:
Since there is no TWRP for OP8T and recovery is non-existent on it, how is anyone installing ROMs on this device. I have just jumped from my original purchase of OnePlus One that still works except for the power button (it is current with LineageOS 18.1 and rooted), to the OP8T over a month ago and a lot has changed since the OPO. I have looked up fastbootd but still don't understand the differences. Comments about installing ROMS are made all over this forum but most assume you know how to do it. I have gotten spoiled with TWRP on the OPO and can flash a new ROM in around a minute almost with my eyes closed. This is getting confusing. I successfully rooted this OP8T after I got it and that was a very touchy thing having to jump through a bunch of hoops to get it done. I was surprised that it worked after all the steps that were required. It used to be that there was info on how to do this kind of thing on this forum, but now it seems that most everyone thinks you should already know the basics. Well the basics are part of my problem right now. A and B slots are new to me and I think I understand that but have not seen an explanation of how that all works when loading ROMS. I have a working phone at the moment in the active slot, but the "other" slot is corrupted. I tried to duplicate the active slot to the inactive slot and of course I can't get adb to work.... Isn't anyone else having these issues? I will look into the MSM tool again.
If you know where the info is that I'm looking for is, please give me the links. Thanks
Click to expand...
Click to collapse
Here's some information that I found helpful:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
Dynamic Partitions | Android Open Source Project
source.android.com
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Here's a couple of ways to get one partition to look like another one:
1. The Los pre-installation instructions have instructions on how to sync the partitions. Note: it doesn't sync boot, dtbo, or vbmeta.
2. If you're rooted you can copy one partition to the other using
Code:
dd if=/dev/block/by-name/xxxx_(active-slot) of=/dev/block/by-name/xxxx_(inactive-slot)
For example:
Code:
dd if=/dev/block/by-name/boot_b of=/dev/block/by-name/boot_a
Note that you can find out which is the active slot using getprop ro.boot.slot_suffix
I've written a shell script based on the Los zip in 1. (see attachment) that will do all partitions - use at your own risk. Don't run it unless you understand what it's doing.