Develop Bugs

Corrupted Deviced, Unlocked Bootloader Vendor Parsing Failed, can get in TWRP.

Hey guys.
Yesterday, I swapped out my Oneplus 6T, and got a new Pixel 3 XL 64GB.
I managed to have no issues unlocking the bootloader, and I do have relative familiarity with adb tools.
I'm running a Dell XPS 13 which has a USB Type C port which I have been using for cmd through Windows 10 in the beginning much to my own success.
After unlocking the bootloader, I had opt'd in for the ota update for Android Q and downloaded without hesitation.
I booted into TWRP, and when attempting to flash through the USB OTG cable it failed. I do not recall, and didn't think to use the webcam on my PC at the time to screenshot the errors.
I can get into the bootloader, however now when I run adb devices nothing appears.
If I boot a TWRP img, go to advanced > adb sideload and run a session. I can then proceed to run adb devices and successfully it reports back my serial number of the device. ( can provide screenshots of this if it's of any assistance )
However, no way have I been able to flash the Factory images, from as early as September 2018 to the latest for Android 9.0, nor have I have been able to reflash the Android Q factory images using cmd and the flash-all.bat
I've also followed this guide step by step uninstalling every ADB and Android related driver prior to installing the "lastest google drivers" https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page6
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file) is where it hangs, and I'm absolutely at a stand still I wouldn't be posting if I hadn't searched and tried everything I could find any way related to it.
Also seems to be missing multiple sig files when running the flash-all.
If anyone can be of assistance it would be greatly appreciated I do not want to have to RMA to Google.
Thanks guys!

You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.

hatdrc said:
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
Click to expand...
Click to collapse
Sadly, I can't get to a USB A to C cable for 6 more days.
I did manage to get to Q, and I don't know what rushed me to thinking I could be flashing twrp on the beta.
I have been using factory images, I haven't sideloaded with adb, as I can't quite seem to figure out the flashing process for TWRP. Is there a method you could recommend we try?
I have the latest tools, and I'm 99.9% positive in one of the 20+ flashes I tried Today of various factory images, flashing the last factory with Q did not solve the trick with or without the -w.

If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL

I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.

Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
As the other user has mentioned, I may be at a loss at being able to flash with TWRP after installing Q.
Gordietm said:
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Click to expand...
Click to collapse
Could you give me a detailed step by step, perhaps with the url's for the drivers & SDK tools.
I've used the links provided in the Soft Brick guide, and got the drivers direct from google themselves.
Although when I currently plug in my phone, it does install "Lemobile Android Drivers", the Google Drivers remove this but appear to be older drivers?

Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools

Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Gordietm said:
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Okay will do, please confirm if this is correct.
Extra Android platform-tools, and factory image to the same folder, then extract the zip file found within the folder itself with the zip found from the Factory Image
I erase system a & b, and boot a & b
Flash-All should work start to finish right?
What are the odd's I'm going to be stuck with a RMA?
I'm sure I've exhausted myself trying this exact process so many times yesterday.

Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.

Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
This sounds identical to what I've be doing, which has been causing the vendor_a issue, but I will give it another run for you shortly here. Just woke up, and rather be fully awake before I go tackling this.
If you can think of any other method, or even an explanation why the vendor img doesn't seem to work that would be awesome.
Also, there is threads I found through google here on XDA with users have a similar issue hanging at vendor, but not due to the same mistake. I'll find you the URL's shortly here.

It's because you were using r28.0.1 before, download r28.0.2

Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
Gordietm said:
It's because you were using r28.0.1 before, download r28.0.2
Click to expand...
Click to collapse
I've been using r28.0.02 just confirmed by looking at everything I had downloaded for trying to fix this yesterday :/

Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.

Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,

Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
I have access to another phone here, and can make a video of what I'm exactly doing?
Would this be of any use to troubleshoot, I really don't want to end up on the path to an RMA.

At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!

Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Gordietm said:
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Click to expand...
Click to collapse
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.

XZeeWhy said:
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
Click to expand...
Click to collapse
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?

XZeeWhy said:
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Click to expand...
Click to collapse
After failing on the Vendor image, you can sideload the OTA and that should get you back up and running......for some strange reason I always seem to fail there and sideload the OTA at that point has ALWAYS fixed me.
GL!!

hatdrc said:
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
Click to expand...
Click to collapse
There is another PC here, but it doesn't have a Type C port, and I don't have an adapter on hand either.
Certainly willing to give Windows a clean install or do a live boot or install of linux to see if a fresh install or another operating system may help resolve it.
So stock factory images can not be flashed via TWRP?
It does seem to change various images on the device when rebooting to bootloader after using Flash All so I feel like it's getting quite a large amount of the partial install.
If I have boot loader & TWRP, I mean there has got to be a way right?

Touch screen not working, even after factory reset

My phone arrived last night. I immediately, following the instructions I found here, magisk'd it. As soon as I flashed the patched image and rebooted... I found that the touch screen had stopped working.
So I booted into recovery (which was hard, because I can't figure out any way to shut my phone down), and wiped data / factory reset. The bootloader is still showing as unlocked. And the touch screen is still not working.
Does anybody know why this might be or what I should do about it? Note that I didn't buy from Google, I bought new from a well-reputed ebay seller...

Send it back. It sounds like a hardware issue.

sic0048 said:
Send it back. It sounds like a hardware issue.
Click to expand...
Click to collapse
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?

DanHakimi said:
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
Click to expand...
Click to collapse
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:

Reflash the factory image and relock the bootloader... It is an official process from Google, if that fails contact the seller and RMA the unit.

Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!

As it's new and you've got nothing to worry about saving I'd just flash the latest factory image via fastboot and once it's up extract the boot from that image and patch it. The fellow above is probably correct but there is one other thing, use an A to C cord, not the C to C cord for all your flashing.

Bob nesta said:
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Click to expand...
Click to collapse
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.

DanHakimi said:
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
Click to expand...
Click to collapse
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
As far as Q - maybe? That's why I said "supposedly" it comes out the 3rd (https://www.theverge.com/platform/a...ndroid-10-pixel-september-3-release-leak-date) , but there are no guarantees in life (except death & taxes).

Again, just to be sure, you are using a USB A to C and not a C to C, correct?

DarkShadowMX said:
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
Click to expand...
Click to collapse
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...

krabman said:
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
Click to expand...
Click to collapse
Yes, A to C.

Bob nesta said:
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
Click to expand...
Click to collapse
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...

DanHakimi said:
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
Click to expand...
Click to collapse
Please do. I'm no dev & can probably offer little to no help, but if you post your errors someone else may be able to help you out.
It could just be a cable/driver/fastboot issue & not the phone, so please provide error info.

Ok, do the full smash. This assumes a basic familiarity with flashing mechanics.
1. Download and install the latest fastboot package.
2. Download the latest image from google again.
3 Use a known good A to C usb cord
4 Before flashing the image type all the following commands one by one in fastboot...
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
5 Flash the image using the flash all script.
6 Once you're up extract the boot from the image you flashed and patch it in magisk.
7 Flash the patched boot image.

DanHakimi said:
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
Click to expand...
Click to collapse
I don't either. I used a USB OTG cable

Had a **** ton load of issues trying to go from rooted and TWRP with custom rom to Android 10.. Every time I ran the flash-all.bat it would fail at one stage or another.. Finally grabbed the Pie Ota from the site, sideloaded it through TWRP then wiped everything through stock recovery and then took the Android 10 update. My point is, use the OTA and sideload it

I was rooted on Android 10 beta 6 and trying to download the OTA through the phone update failed every time. I uninstalled magisk and restored images..but still failed. I finally had to sideload the OTA image and it finally updated. That was the only way to get mine to work. Then I took the boot image from beta 6 that was already patched through magisk and re-flashed it because the boot image from Android 10 official patched through magisk would not give root...kept failing. Then when I re-flashed last months beta 6 image, upon reboot the screen would freeze and no apps would load. I then booted into recovery and did a factory reset and upon reboot magisk was identified and root was acquired....phone worked perfectly after that and no issues....weird. I then just reloaded all of my apps from backup and was on Android 10 official, rooted through magisk.

I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...

DanHakimi said:
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
Click to expand...
Click to collapse
I suspect you are running out of hard disk space on the computer that you are using to try to flash all this with. I ran into a similar issue once when the C drive of my computer was nearly full. The system file ends up needing a lot of disk space in order for it to be unpacked. The error you are getting is that you are running out of space and it cannot unpack it. Again, this isn't phone memory space, this is actual computer hard drive space.

Cannot flash factory firmware after a failed root attempt

Thanks in advance if anyone can help me with this.
I tried to root my phone via Magisk using a tutorial on YouTube. I noticed after Magisk had patched the boot.img it reduced in size from around 65MB to 30MB, which seemed odd. Flashed it, and phone became stuck in a boot loop. I tried to use fastboot to put the original boot.img back, and ended up being told the system was corrupted.
Thought I would just flash the factory firmware back on to the phone - however, that is failing partway through, when it tries to flash vendor.img, with an error "write to device failed in SendBuffer()"
I've tried multiple different versions of ADB and Fastboot, from HighOnAndroid and Google, tried flashing from a different laptop, but it fails at the same point regardless. The only thing I haven't been able to try is a different cable, but it would seem odd if that was the cause?
My device was originally on Bonito 10.0.0 (QQ1A.191205.011, Dec 2019) - I've tried to flash that back, and also tried 10.0.0 (QQ1A.200105.002, Jan 2020), neither of them working.
I'm using ADB and Fastboot from the Platform Tools at https://developer.android.com/studio/releases/platform-tools - a lot of posts I've read talk about "installing ADB and Fastboot", but they're just executables that run fine without any installation, unless I'm missing something.
Does anyone have any ideas of what I could try please?

Same old story - different cable, different port, worked.
I also suspect that the platform tools were not compatible with QQ1A.200105.002, Jan 2020, since the one I successfully managed to flash in the end was the December version.
Since I changed both cable and version at the same time, I can't say which one it was.
Hope this helps someone else.

smimon said:
Same old story - different cable, different port, worked.
I also suspect that the platform tools were not compatible with QQ1A.200105.002, Jan 2020, since the one I successfully managed to flash in the end was the December version.
Since I changed both cable and version at the same time, I can't say which one it was.
Hope this helps someone else.
Click to expand...
Click to collapse
I wonder if this is why Magisk Installer doesn't like my boot image, consequently failing to patch it.

clayndwoods said:
I wonder if this is why Magisk Installer doesn't like my boot image, consequently failing to patch it.
Click to expand...
Click to collapse
Known issue with Cannery Channel. Try latest Stable. Also checkout Magisk thread.

Android
I figured it out. I was trying to patch the wrong file, apparently.
I'm a bit concerned, though, as the patched file is 29.6Mb and the orignal boot.img is around 60Mb.
I don't want to hose this phone, has I just got it as a replacement from Google. I tried sideloading the Android 10 update using TWRP (my original phone had TWRP and Magisk installed) and bricked the phone. Well, not exactly bricked. It was stuck in recovery, the only thing that would work was the bar code display.
You never know what you like so much about the pixel until you have to use a Samsung while waiting for your replacement Pixel to arrive. I can't survive without call screening LOL!

clayndwoods said:
Android
I figured it out. I was trying to patch the wrong file, apparently.
I'm a bit concerned, though, as the patched file is 29.6Mb and the orignal boot.img is around 60Mb.
Click to expand...
Click to collapse
The patched file is normally smaller than the stock boot.img. That's OK and expected.

How To Guide adb doesn't discover phone but fastboot does - trying to install Lineage OS

I'm trying to install Lineage OS on my phone and I have followed all the steps (plus many more they just assume you'll know) from this site, up to configuration because adb no longer discovers my phone.
.\adb devices
.\adb fastboot bootload
literally anything to do with adb doesn't work but it did an hour ago. Now I'm worse off because my phone will only upload to bootload and not to the actual homescreen so there's no going in and double checking if my USB debugging is on (it was before the reset) and I can't access my phone at all, nor can I get things configured. I've updated the drivers via web, deleted and retried the drivers, and restarted the computer. I don't know what I'm supposed to have on my computer that would better upload the drivers. I don't have a clue what any of this is supposed to mean, I was forced to do all of this **** because of the recent Adroid 12 update that I couldn't get rid of without just getting a different OS. Please please please make it dumb for me and tell me how I can get my phone back and download this OS.

Try fastboot commands in bootloader

yesca213 said:
Try fastboot commands in bootloader
Click to expand...
Click to collapse
Yes fastboot commands work but I need to copy this in the command prompt
.\adb sideload copy-partitions-20210323_1922.zip
The tutorial says it isn't an optional step. When I try doing this with fastboot, it tells me:
fastboot: usage: unknown command sideload

Try "fastboot reboot" or "fastboot reboot bootloader"

yesca213 said:
Try "fastboot reboot" or "fastboot reboot bootloader"
Click to expand...
Click to collapse
Thanks! I tried it with no change. adb can still not discover my phone and it doesn't start back up, only brings me to FastBoot mode screen.

If it's Windows your using it may be a driver issue.

yesca213 said:
If it's Windows your using it may be a driver issue.
Click to expand...
Click to collapse
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?

johnmtrowbridge said:
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
Click to expand...
Click to collapse
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222

heyhowyoudoin said:
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
Click to expand...
Click to collapse
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment

johnmtrowbridge said:
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
Click to expand...
Click to collapse
just i'm sure what i can fix all that thing fast and want to help you
i have signal too

heyhowyoudoin said:
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
Click to expand...
Click to collapse
Yeah I'm gonna just have to try in a few hours because the only way Signal works on my desktop is if I verify it on my phone lol. Again, the phone is completely stuck on FastBoot mode and anytime I restart it it takes me right back, which I think is probably because of the recovery mode I just installed.

bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool

heyhowyoudoin said:
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
Click to expand...
Click to collapse
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?

i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware

heyhowyoudoin said:
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
Click to expand...
Click to collapse
There wasn't a recovery version of 11 at the time that I could find, not for the 9 Pro. So what do I do now, do you know how I at least get my phone off of FastBoot mode to try this **** all over again?

johnmtrowbridge said:
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
Click to expand...
Click to collapse
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself

can you tell me which version your phone have? IN/CN/GLOBAL/INDIA

Index of /list/Unbrick_Tools/OnePlus_9_Pro
or download version for your phone from link above

heyhowyoudoin said:
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
Click to expand...
Click to collapse
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
heyhowyoudoin said:
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Click to expand...
Click to collapse
NA I'm in America

johnmtrowbridge said:
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
NA I'm in America
Click to expand...
Click to collapse
yes, that's what I mean. is your phone linked to t mobile?
at the moment it is not possible to install any custom OS from version 12 of android, not only lineageos

Can't flash custom roms. Hangs and never finishes.

Ptxel 2xl. Stock. I can root and i can flash stock firmware. I have used productpartition-pixel2xl-extended.zip. I have changed cables and insured the google drivers are installed. On the same PC i can flash custom roms on my 3xl 4a5G 6Pro and 7Pro.
I have flashed the latest stock to both slots and done a factory reset to bith slots. I just can not get a rom to flash. I can flash partitions individually like vbmeta and boot and system. Can't get a rom to go.
I have tried all the recoveries that come with the roms and also i have tried several versions of twrp and PBRP to no availl.
Any ideas would be great. Not a noob but this has me stumped. I wil even mail it to someone that thinks they can get it flashed with a custom rom! lol
Ideas?
And.........GO!

Slim2none4u said:
Ptxel 2xl. Stock. I can root and i can flash stock firmware. I have used productpartition-pixel2xl-extended.zip. I have changed cables and insured the google drivers are installed. On the same PC i can flash custom roms on my 3xl 4a5G 6Pro and 7Pro.
I have flashed the latest stock to both slots and done a factory reset to bith slots. I just can not get a rom to flash. I can flash partitions individually like vbmeta and boot and system. Can't get a rom to go.
I have tried all the recoveries that come with the roms and also i have tried several versions of twrp and PBRP to no availl.
Any ideas would be great. Not a noob but this has me stumped. I wil even mail it to someone that thinks they can get it flashed with a custom rom! lol
Ideas?
And.........GO!
Click to expand...
Click to collapse
Doubt I can help you here, but mailing it would not be a good idea, using remote control software could be smarter.

I know you've already tried, but these two things are practically always the problem:
1) Using a new USB port on the computer. USB-C is particularly problematic.
2) Wrong drivers. The PC can use different drivers depending on whether the phone is in normal, bootloader or recovery mode. So you need to check your drivers while the phone is in recovery.

Arealhooman said:
Doubt I can help you here, but mailing it would not be a good idea, using remote control software could be smarter.
Click to expand...
Click to collapse
Yeah not sure i really would mail it although it just a $50 toy and thats why i bought it...kind of a google fan boy and want the box set lol
Remote software would work and i would be willing as there is no sensative data on this PC.
But who would be willing?

Have you tried PixelFlasher

Arealhooman said:
Have you tried PixelFlasher
Click to expand...
Click to collapse
Only to flash stock and to root. Most roms are a sideload updates and i can't figure out how to use PF to do custom roms.

I had the same issue in recovery mode. I resolved it by buying a USB hub and connecting the phone through that.

zpunout said:
I had the same issue in recovery mode. I resolved it by buying a USB hub and connecting the phone through that.
Click to expand...
Click to collapse
I have a hub...may give that a try. Haven't touched the phone for a while now.