Database Users

Pixel XL bricked by switching to Slot B in TWRP No rom, bootloader, recovery,fastboot

Hey,
I just wanted to inform you about an issue that happens in TWRP. I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B. I think TWRP should inform the user that rebooting will brick the device. What are your thought on that? It could be done similar to how TWRP informs the user to install supersu if the phone isnt rooted.
This would be really helpful as it would prevent many people like myself from bricking their phones.
Now if I connect my pixel it only shows Qualcomm HS-USB Diagnostics 900E (COM3). No bootloader, fastboot, or recovery is present.
Here are a coupe of links of other people that did the same thing:
https://productforums.google.com/forum/#!topic/phone-by-google/sXjCoQ8glac
http://forum.xda-developers.com/pixel-xl/help/pixelxl-bricked-t3517310
Thanks!
Edit
I contacted the devolper of TWRP and he says that it should have boot loader regardless.
Here is the history: At work 3pm, froze Android system apk and some other telephone apps to troubleshoot something, I know I shouldn't do this. Resulted into boot loop. Go into twrp recovery and wipe data. It boots up fine and I see it downloading updates but it never goes through, I attempt to go back to recovery and apparently it's back to the stock recovery even though I originally had TWRP rc1.
I get home at 7 pm, I want to install TWRP rc1 so I send the command to boot into TWRP and then I install the zip, then I install sr5 SuperSU. I change to slot b and it's been bricked since.
It arrived November patch and it stayed like that since I was rooted. It attempted to install 7.1.1 but it returns installation problem. I think the bootloader was removed because of the failed update.

Your in download mode. I had this happen once on my Nexus 7. I held power for 90 seconds and it went back to bootloader. However I dont know about the pixel. Its still a new and uncharted device.
You also have to realize TWRP is in an unstable stage. You really should not flash anything until its in final release mode. I know I know... Hindsight is 20/20.
If you have insurance you could get it replaced.
Good luck.

sorry to hear dude..

bahehs said:
I think TWRP should inform the user that rebooting will brick the device. What are your thought on that?
Click to expand...
Click to collapse
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?

bahehs said:
I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B.
Click to expand...
Click to collapse
Does anyone have an understanding about how something like this could potentially happen? Do these phones ship without information on the second slot? After my phone OTA updated, I switched slots without issue back to the previous version by following the information from Android Police. I'm not clear on what exactly would need to happen for the noted situation, and how someone could potentially get into a similar situation, unless the phone ships without information on the second slot. Switching slots worked without issue the times I tried it, but my phone had been through a typical OTA update before switching slots, so there was definitely information on both slots when I tried it.

Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI

Scott said:
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Click to expand...
Click to collapse
Same, mine is on slot B. Dunno if it came that way, but it is only two days old. I let it take the OTA then flashed Francos kernel and then booted the root su image.
I really regret not watching more closely how all of impacted which slot it was on.
Sent from my Pixel XL using XDA Labs

Everytime you get OTA update you will switch slots. If you update via flashall it will say on the same slot.
This mode can't be a complete brick but it doesn't look like anyone has a solution yet. Maybe we will need some HTC tool?
Also when you root or modify you take responsibility for anything that happens. There is always a chance of a brick. At least Google will still probably warranty these devices.
Sent from my Pixel using Tapatalk

CZ Eddie said:
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
Click to expand...
Click to collapse
This comment is unnecessary and serves no purpose in this thread.
Sent from my Pixel XL using XDA-Developers mobile app

I'm okay with that.

Updated op with more info

I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.

reb1995 said:
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
Click to expand...
Click to collapse
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.

I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Sent from my Pixel XL using Tapatalk

bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
Sorry for the long delay. No I was not rooted.

yearn2burn said:
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Click to expand...
Click to collapse
Bump

The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
You are right a failed OTA could brick a pixel phone

DR3W5K1 said:
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
You are right a failed OTA could brick a pixel phone
Click to expand...
Click to collapse
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones

aholeinthewor1d said:
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
Click to expand...
Click to collapse
Failed bootloader flash? The Google .IMG files contain bootloader's.
EDIT I do believe the flash_all.sh flashes the bootloader

So you cant even run ADB commands ( a.k.a Bootloader / Recovery mode ), its a hard brick or soft ?
Does your PC detect the device when its on and connected via USB ?
Why did you switch slots in the first place ? if your taking an OTA on a rooted device with SU an OTA wont even apply via TWRP, you have to manually flash with the flash-all.bat script or part by part and the A / B boot slots are handles by the updates so you don't accidentally boot with a slot with no bootloader.
There is no need to swap A / B manually and if your going to flash and want to play with the A / B slots you should at least flash the partitions first but hindsight is a wonderful thing.
Aboot here might be your friend, but as this device is still quite new to many devs and or the tools might not be publicly available . . .

Is this normal after unlock/root?

I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.

convolution said:
I did a long, messy, and convoluted way of getting root. I messed up several times. Now I think I finally have root and a working phone. But, when I first turn on the phone, it gives me a screen warning me that it can't check for security loopholes, so i should relock my bootloader. That's normal.
But I also get another screen saying that my device is corrupted, and that my device may no longer properly work. Press power to continue. I press power, and it's able to either boot to the phone OS, or boot to TWRP, depending on what I was doing.
Question is, is my phone really corrupted during my messy install? Or is it also normal for all rooted and unlocked phones?
Thanks.
Click to expand...
Click to collapse
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk

dogen18 said:
I believe the corrupted message is standard for Android on all phones. I always ignored it. There are threads on how to get rid of that message. I never bothered with that.
Sent from my PH-1 using Tapatalk
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
Oh, the message is normal when bootloader is unlocked. Furthermore, I have read that relocking bootloader can cause problems with Essential Phone, but I don't know why.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...

convolution said:
But the error message I get literally pauses the boot sequence until I press power to acknowledge it. That's normal?
Pretty annoying if it is...
Click to expand...
Click to collapse
It has been awhile since I rooted any phone, but yes, pressing power to continue was what I remember. And, yes annoying, but not fatal !
Sent from my PH-1 using Tapatalk

It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.

GryphKid44 said:
It sounds like you might only have one good slot and the other corrupted. The bootloader message as you indicated is normal but the other message is not. I had this at one point as well because fastboot erased system but failed to flash it. Reflashing stock fixed it.
Click to expand...
Click to collapse
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?

I would think that would do the trick. In my case I knew the system was issue so I just flashed system. I find fastboot extra finicky on this phone. Did you happen to notice if something errored in the script?

convolution said:
How did you flash stock? I tried
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Flashing NMJ88C, and i downloaded it, extracted it, ran the BAT after I have both bootloader and critical unlocked, and now I can load the phone with NMJ88C, but like I said, I got that error. Isn't this method supposed to have fixed both slots?
If you didn't use this method, i was wondering what method you did?
Click to expand...
Click to collapse
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck

wolfu11 said:
http://mata.readthedocs.io/en/latest/
Sounds like you have the red verity message.
Read this guide down toward the bottom it explains it further and there is a fix.
Good Luck
Click to expand...
Click to collapse
I do... but my wifi doesn't work as well, so I think I did something wrong.

convolution said:
I do... but my wifi doesn't work as well, so I think I did something wrong.
Click to expand...
Click to collapse
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.

wolfu11 said:
https://download.invisiblek.org/mata/boot.fix.red.img
install this via fastboot flash boot boot.fix.red.img
that should clear out your error after a reboot and fix your wifi.
if it doesn't simple go back to stock and start over.
Click to expand...
Click to collapse
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?

convolution said:
Which stock should I choose? There are so many builds and versions? Do. I have to match my current one?
Click to expand...
Click to collapse
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.

wolfu11 said:
yeah there are a lot lol I'm using OB 8.1 and it's solid flashed it from the back to stock section then rooted it via modified boot, super easy (no need for twrp)
I would choose the most current one. since it will have the latest security patches. but within a day or 2 we should be getting the March update in a new build.
Click to expand...
Click to collapse
no need for twrp?
you follow this one?

convolution said:
no need for twrp?
you follow this one?
Click to expand...
Click to collapse
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.

wolfu11 said:
What I mean is if you are staying stock and just want magisk and root you don't need to do it via twrp. There are modified boot images you can fastboot flash. But if you want custom ROMs you still need twrp.
I have been satisfied with stock rooted.
Click to expand...
Click to collapse
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...

convolution said:
I think I did it! I'm now running 8.1 + Magisk. But I kind of want to add TWRP so I can run a custom kernel...
Click to expand...
Click to collapse
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.

spotmark said:
You CAN'T add TWRP. It's installed as BOOT, so you need to install it every time you use it.
Click to expand...
Click to collapse
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.

delete

If it works, you should worry about that message at all.

convolution said:
Ahhhh. I had a light bulb moment as to why I had difficulty... I installed twrp but didn't install the boot image after.
Strange how that works. I'm coming from an older school phone that doesn't do that slot system thing.
Any reason why this phone would have TWRP replace the boot image?
Or maybe you know of a thread that explains it?
Thanks.
Click to expand...
Click to collapse
The slot thing is pretty new in general. This doc has some explanation for the architecture of our phones: http://mata.readthedocs.io/en/latest/
Once you get the hang of it, it's pretty simple to deal with.
BTW, awesome signature. PTL, SDG. :victory:

Dual Rom On Both Slot

Is It Possible To Use Both Slots For Dual Rom ?
Don't Give E.g Of Dual Boot Patcher I Am Just Asking That Question

I don't think so because the partitions aren't designed that way. The purpose of the dual partitions is to provide seamless updates and allow the phone to recover if an update fails. But if you are rooting and flashing custom ROMs the dual partitions have no benefit. They were designed by Google specifically for OTA updates but custom ROMs normally can't be updated without user intervention. If you run a custom ROM on a dual partition phone normally you can't update the ROM without connecting your phone to a computer. The dual partition setup and Safety Net seem to have been created by Google largely to discourage flashing but it hasn't really worked.

Yes you can install dual roms on dual partitions. But since the data partition is shared between those 2 partitions, it's likely either one of the ROMs will be stable for which the data belongs to. Eg. If you run LOS 15.1 on slot a and stock oreo on slot b, and if you initially booted with slot a and the data belongs to LOS, then you can switch to slot b but you'll face lot of issues and Force closes. So this dual partition is meant to hold same ROM and not different ROMs.

Uvneshkumar said:
Yes you can install dual roms on dual partitions. But since the data partition is shared between those 2 partitions, it's likely either one of the ROMs will be stable for which the data belongs to. Eg. If you run LOS 15.1 on slot a and stock oreo on slot b, and if you initially booted with slot a and the data belongs to LOS, then you can switch to slot b but you'll face lot of issues and Force closes. So this dual partition is meant to hold same ROM and not different ROMs.
Click to expand...
Click to collapse
What you said actually amounts to no because one of the two ROMs won't function properly.

jhs39 said:
What you said actually amounts to no because one of the two ROMs won't function properly.
Click to expand...
Click to collapse
That's what I said

Uvneshkumar said:
That's what I said
Click to expand...
Click to collapse
Not really. What you said was yes, but.... which isn't the same as no.

jhs39 said:
Not really. What you said was yes, but.... which isn't the same as no.
Click to expand...
Click to collapse
Well the actual answer is YES. You can install dual ROMs on dual partitions. But the thing is one will not work as expected. And that's what I've clearly said in my first comment. Now enough of this argument.

FYI
https://source.android.com/devices/tech/ota/ab/

wifi not working on android p

I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work

TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk

Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...

Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.

crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.

jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue

Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).

tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!

rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked

Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.

Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?

1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since

jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference

Edited. We are all just trying to help others. Lets keep it that way.

so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips

jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...

rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.

jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob

OnePlus 8 Pro refuses to install TWRP. Qualcomm Crash Dumps every time. Any advice?

I want to install TWRP as my recovery I've tried at least four different versions that are listed here and a few others from other links:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8-pro-unified-stable.4101313/
I'm not having driver issues anymore so I'm working with adb and fastboot fine. All commands are going through fine and I've tried flashing to recovery_a and recovery_b. Factory resetting doesn't resolve the issue. Every walkthrough I find I get to says flash then boot to TWRP but every time I flash it qualcomm dumps and every time I boot to it it qualcomm dumps.
Is there something corrupted in my recovery I need to wipe somehow? If so how do I wipe it because the only command I found online that would run was fastboot -w and that didn't fix the issue either.
Honestly really annoying at this. This is my 4th OnePlus phone and I've never had so many issues flashing it.
Edit:
I have also tried to do whatever steps are needed to go back to base stock and OS and it doesn't seem to work either. Any help would be appreciated.
Edit 2:
I did it. For anyone who finds this thread in the future the MSM tool did finally work. This is the video I used in the end
(I muted it.) and the first few starts it failed. I went into the properties of the MSM exe and under compatibility checked ran as admin. I also did install the qualcomm driver at some point way before this so not sure if that helped. The MSM tool still didn't work until I started it, turned my phone off, held both volume buttons (not the power) while plugging the phone in. All the stuff online I saw had people starting the program at this point but mine had started already and was in a "waiting for device" state when it worked.
What a lifesaver. Won't be messing around with this again until TWRP is available.

Because you are unable to flash phone's Stock ROM take phone to authorized service center and let them fix it.

Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Edit: not

Lossyx said:
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Click to expand...
Click to collapse
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.

TheFloppyDisk said:
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
Click to expand...
Click to collapse
Meant to say it's **not** compatible with Android 11 yet.

Lossyx said:
Meant to say it's **not** compatible with Android 11 yet.
Click to expand...
Click to collapse
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.

TheFloppyDisk said:
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
Click to expand...
Click to collapse
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch

Lossyx said:
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Click to expand...
Click to collapse
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.

TheFloppyDisk said:
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
Click to expand...
Click to collapse
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though

Lossyx said:
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Click to expand...
Click to collapse
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.

TheFloppyDisk said:
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
Click to expand...
Click to collapse
It is very sensitive to which USB port you use. For some people only USB2.0 works, for me USB3 works fine as long as it's chipset USB3. The second ASMedia controller doesn't work.
Also, use original cable, and switch off the phone completely, get MSM to the point it's waiting for device so start the download before connecting phone, then while holding the volume keys connect the USB cable and it should instantly start flashing.