Database Info

[Q] Is my Maxx bricked?

Greets,
I think I may have bricked my Droid Maxx but I'm hoping someone can verify before I deem it a paperweight. I was on SU-2-3.3 and used Sunshine on it to unlock it and then TWRP to root it. After fully booting up the phone and verifying root, I rebooted into TWRP and ran a full back up w md5. After that, I booted up the phone and used supersu survival mode and then took the OTA update. Now the phone boots to fastboot, but says "boot failed" under any of the options. It won't go into recovery nor will it normally boot up. I tried to use RSD to reflash to the latest version but it just said flash failed at the first file and says something about downgraded security, etc. So now, I can get into fastboot mode and the phone connects and is detected but won't let me flash anything... it was unlocked via Sunshine, but I may have borked it up somehow. Thoughts?

Try a more recent firmware but check your recovery
Sent from my D6616 using Tapatalk

I took the OTA... is there something more recent? Also, I've tried to flash other recoveries but I get "boot failed" at the fastboot menu.

ohhhh you must mean try and use a more recent firmware via RSD. I'll give that a shot

Ok i tried a newer firmware via RSD, now the fastboot mode shows "failed to read signatures for partition aboot" RSD fails at flashing partition gpt.bin

Since I seem to have a partition related error, would this LINK help my situation at all?

Does anyone know of a way I can restore or rewrite the partitions via fastboot?

t3knokon said:
Does anyone know of a way I can restore or rewrite the partitions via fastboot?
Click to expand...
Click to collapse
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.

crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
t3knokon said:
Since I seem to have a partition related error, would this LINK help my situation at all?
Click to expand...
Click to collapse
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.

BladeRunner said:
well he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet.
---------- Post added at 08:30 AM ---------- Previous post was at 08:27 AM ----------
If you can get into fastboot then I don't think you need to go that route just yet. You can try flashing the individual images via fastboot i.e. fastboot flash recovery recovery.img etc. It's been a while but I'd skip flashing the motoboot.img and gpt.bin and flash the boot.img, recovery.img and system.img.
Click to expand...
Click to collapse
Ok to clarify, after I unlocked via sunsine on 2-3.3, I rooted and I took the over the air so now I'm on the newer bootloader. Post those events I started to receive "failed to erase partition xxxx" I also just tried reflashing individual images from 4.4.4 su6-7 release and I still receive back "failed to erase... failed to flash... etc." I can get into fastboot mode but it seems crippled somehow.

crack.mech said:
Okay, So if you think you device is completely bricked, and I mean "NOT RECOVERABLE AT ALL" , you can try this: This may be a long shot, you might want to try uploading 'sbl2.mbn' file. If you are able to flash that, then you can try flashing a "Broken" sbl2 file and try uploading the ROM using Qualcomm emergency downloader. This method is very dangerous, and not for the faint hearted. It is used to root the droids which cannot be rooted by sunshine (post SU4-21) and you may lose your rooting capabilities all together, as this method uploads a non rootable bootloader (SU6-7). If you can get your hands on a copy of the bootloader you already have ( SU-2-3.3) , you should use that to unbrick from the bootloader mode. Try to refer this post for further details.
Click to expand...
Click to collapse
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?

t3knokon said:
This sounds like a promising method. If I attempt this method, will I be able to recover root since I was previously unlocked via sunshine prior to bricking/soft-bricking?
Click to expand...
Click to collapse
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
BladeRunner said:
well, he's not a hardbrick as he can get into fastboot so I don't think he needs to use THIS method just yet
....
Click to expand...
Click to collapse
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!

crack.mech said:
I don't think you can downgrade from SU6-7 to SU2-3.3. But I guess trying won't hurt. If you are able to flash a new sbl1.mbn and sbl2.mbn files, you might want to try rsd lite / mfastboot to flash the ROM image before you try the more dangerous path (CrashXXL's protocol, intentionally flash the broken bootloader and the using the qualcomm emergency mode to access the partitions) .
And answering your question:This WILL revoke your rooting capabilities and you will no longer have root. Though you can then use CrashXXL's method (same post linked above) to get root. But your bootloader will be locked, so no custom ROMs for you..
Good luck!
---------- Post added at 12:47 PM ---------- Previous post was at 12:42 PM ----------
I think his bootloader is in a conflict as it might be looking for the certificates that are allowed, and sunshine is messing with the new installations. That is why I recommended a clean install of the device. But this is just guess work, I might be completely wrong!
Click to expand...
Click to collapse
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?

t3knokon said:
Bummer. I'm not able to flash anything. All I get back is "Failed to erase partition." I did some extensive reading on the BLBroke/Qualcomm method and attempted that and still the bootloader replies back "failed to erase partition." I don't know what I should try next. Thoughts? Is the partitioning or memory bad on the phone?
Click to expand...
Click to collapse
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.

BladeRunner said:
sent you a PM directing you to a different site. Not sure they can help but it's worth a try.
Click to expand...
Click to collapse
Thanks for that. I posted there as well... from a software standpoint, I'm curious to know what would be denying access to the partitions...

I messaged jcase and he looked at logs for the sunshine preinstall and they were clean. It's possibly a hardware failure unless someone else with bootloader knowledge, knows how to get around the partition permissions access. thoughts?

I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?

t3knokon said:
I've tried a myriad of different methods... i just seems the partitions are locked down... "Access Denied" "Flash Failed" I have no idea what else to try. What do ya'll think? Brick city?
Click to expand...
Click to collapse
the prognosis is not good.

VBlack messaged me about shorting a pin to put the phone in Qualcomm Downloader mode... and then pushing software onto it to at least try to the partitions set up and get the bootloader in a manner which will allow for writing. If that doesn't work, there's nothing else to do. I read up on it extensively, and it's now a last ditch effort. I've never take apart a phone in that manner before, so it'll be a first for me.

Similar boat, here...using a programmer cord, I can flash a ROM onto the Maxx, but it stumble-boots into BP Tools mode after 3 or so failed 0-battery/unlocked bootloader warning screen loops. I can get it into bootloader with program cord, or first thing with factory cord. It won't charge at all, battery is new. Izzit hosed?
Sent from my XT1254 using XDA Free mobile app

Essential Bootloader Unlock - Official Advice

Links attached for those interested from Essential Web Site, and source.android.
https://support.essential.com/hc/en-us
https://source.android.com/source/running

The real question is kernel source. Not much reason to unlock the bootloader without that.

Goronok said:
The real question is kernel source. Not much reason to unlock the bootloader without that.
Click to expand...
Click to collapse
Exactly.
I'm not holding my breath.
I think I'm jumping ship.

thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol

gqukyo said:
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
Click to expand...
Click to collapse
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.

drocny87 said:
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
Click to expand...
Click to collapse
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition

graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
Some people got the update today. If you happen to get it can you try to pull the boot?

I have the update waiting to be installed.

graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
in the build thread, a user was able to capture the OTA url. the only issue, the boot.img is stored in the payload.bin file. Are you familiar with this file and how to extract it?

So is this phone rootable?
Sent from my SM-G950U using XDA-Developers Legacy app

canynballa said:
So is this phone rootable?
Click to expand...
Click to collapse
At this time no. Hopefully soon that will change.

In the Andy Rubin AMA, the official Essential reddit account posted that the kernel and factory images would be released to the public "in the next few days". That probably means next week, business days and all, but it looks like they fully intend to support external development of this phone, and soon. Makes sense--why else would they allow a bootloader unlock from the get-go?

In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help

Sarzeck said:
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Click to expand...
Click to collapse
You need to select correct driver in device manager, maybe even install different drivers
See
https://forum.xda-developers.com/es...nofficial-usb-drivers-essential-ph-1-t3678231
Sent from my PH-1 using Tapatalk

Thanks buddy! It worked

i love unlocking bootloader on mine but for now until no ROM's mod i will stay locked mode. im a Android Pay dude lol

Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.

Yeah, try another computer. Seriously, my main PC just didn't want to work with the phone. Used my laptop, worked fine. Can't think of anything different, both are Win10, both have the same drivers and sdks. Both work for my other phones, just not this one. Didn't hurt to try. Of course you'll need access to another computer but if you have one or more extras, worth a try. Worked for me.

oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Did you reboot the computer? I've seen that help alot when device is not recognize

I'm having same issue, flashing unlock command do not work. I am on the oreo beta version. Someone help please.

Can the bootloader be repaired or restored?

Let me preface this by saying I'm an idiot, I know just enough to be dangerous. Rooted and I wanted to restore and relock the bootloader. Instead of flashing the factory image first, I skipped that step and relocked the bootloader thinking it would wipe everything anyway. Of course now I realize I'm an idiot and I should not have skipped that step. Now I am soft bricked in the bootloader, and nothing will flash properly. Pretty sure I damaged the bootloader.
So my plea for help is, is there any way to repair or restore the bootloader?

I'm pretty sure as long as you can get into fastboot you can run the flash all bat.
You will have to download and extract the full factory image tho...and it should be like starting from fresh.oem
Also if you just wanted to flash a new bootloader you would just have to make sure it was the one extracted from the factory image you were already on.

noXcape said:
I'm pretty sure as long as you can get into fastboot you can run the flash all bat.
You will have to download and extract the full factory image tho...and it should be like starting from fresh.oem
Also if you just wanted to flash a new bootloader you would just have to make sure it was the one extracted from the factory image you were already on.
Click to expand...
Click to collapse
Well I've tried flash-all multiple times, it runs almost as normal except for one fail in the script (I'll show a pic of that after I go home and try again), and finishes as though it worked but when it reboots it can't get past bootloader. I'll try flashing the bootloader separately too.
Plus whenever I lock or unlock bootloader now it goes through the motion and then says "locked" or "unlocked" but it's faster than it should be and doesn't do that wiping animation at all.

Might be time to delete the old factory images and redownload new stuff

noXcape said:
Might be time to delete the old factory images and redownload new stuff
Click to expand...
Click to collapse
Already using the most recent, been playing around with that twrp beta, magisk, and v4a

Are you on current fastboot/adb?

cntryby429 said:
Are you on current fastboot/adb?
Click to expand...
Click to collapse
I think so, I downloaded it fresh a few weeks ago

trhacker01 said:
I think so, I downloaded it fresh a few weeks ago
Click to expand...
Click to collapse
Check again, I think a new version (late October) is in the most recent package.
I ran into the "stuck in bootloader" issue earlier today after running flash-all, but got out of it using some script by someone named Deuce that flashes the images one by one. I'll try and find a link.
Edit: here it is. This worked for me. Read carefully - you have to unzip the factory image that you've downloaded, then unzip the zip file that's in THAT zip.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

JayBlack_686 said:
Check again, I think a new version (late October) is in the most recent package.
I ran into the "stuck in bootloader" issue earlier today after running flash-all, but got out of it using some script by someone named Deuce that flashes the images one by one. I'll try and find a link.
Edit: here it is. This worked for me. Read carefully - you have to unzip the factory image that you've downloaded, then unzip the zip file that's in THAT zip.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Trying this now but still not working for me. Everytime where it fails is writing the bootloader, and everything else works fine. The bootloader writing fails in this deuce script, the regular flash-all, and flashing the bootloader separately.
Attached pics, 2 during deuce script, one during flash-all, and one during separate bootloader flash.

trhacker01 said:
Trying this now but still not working for me. Everytime where it fails is writing the bootloader, and everything else works fine. The bootloader writing fails in this deuce script, the regular flash-all, and flashing the bootloader separately.
Attached pics, 2 during deuce script, one during flash-all, and one during separate bootloader flash.
Click to expand...
Click to collapse
Sorry to hear that. I also got a bunch of failures during the process, and I don't think it automatically rebooted at the end of the process, but it ended up working on the first try (I was shocked when it did, since I saw so many failure warnings). He says in the thread that if it doesn't work, try formatting user data when prompted...I didn't have to, but may be worth a try, since you expected everything to be wiped anyway. Good luck.

trhacker01 said:
Trying this now but still not working for me. Everytime where it fails is writing the bootloader, and everything else works fine. The bootloader writing fails in this deuce script, the regular flash-all, and flashing the bootloader separately.
Attached pics, 2 during deuce script, one during flash-all, and one during separate bootloader flash.
Click to expand...
Click to collapse
A locked boot loader means you can't flash anything, that's the point. You can still flash an OTA.zip if you can get into stock recovery (you can still side load it in stock recovery I believe). Otherwise, you'll need to unlock the boot loader, and if it won't, and you can't get into Android to allow unlocking, then I'm not sure what, if anything, you can do.
Sent from my Pixel 2 using Tapatalk

danaff37 said:
A locked boot loader means you can't flash anything, that's the point. You can still flash an OTA.zip if you can get into stock recovery (you can still side load it in stock recovery I believe). Otherwise, you'll need to unlock the boot loader, and if it won't, and you can't get into Android to allow unlocking, then I'm not sure what, if anything, you can do.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Exactly.
At this point I'd try sideloading the latest ota.zip. If that doesn't work, I'd consider calling support and telling them your phone won't boot, without mentioning how you got there.

foosion said:
Exactly.
At this point I'd try sideloading the latest ota.zip. If that doesn't work, I'd consider calling support and telling them your phone won't boot, without mentioning how you got there.
Click to expand...
Click to collapse
yeah, good point. If I remember correctly, the Deuce script prompts you to unlock the bootloader at the beginning of the process - have you done that?

JayBlack_686 said:
yeah, good point. If I remember correctly, the Deuce script prompts you to unlock the bootloader at the beginning of the process - have you done that?
Click to expand...
Click to collapse
Yes, it's unlocked whenever trying to flash deuce or anything else. That's one of the strange things actually, it will respond to locking and unlocking, but it goes too quickly, skipping the process of wiping. Yeah I think I might be out of luck on this one.

JayBlack_686 said:
Sorry to hear that. I also got a bunch of failures during the process, and I don't think it automatically rebooted at the end of the process, but it ended up working on the first try (I was shocked when it did, since I saw so many failure warnings). He says in the thread that if it doesn't work, try formatting user data when prompted...I didn't have to, but may be worth a try, since you expected everything to be wiped anyway. Good luck.
Click to expand...
Click to collapse
Yeah I formatted to no avail.
Btw I ran out of my daily thanks, I'll continue as I get more. Thank you all very much for bothering to help me with this!

"System update installation failed" while trying to install Q dp3, what did I miss?

"System update installation failed" while trying to install Q dp3, what did I miss?
I am currently on oxygenOS 9.0.8, both slots completely stock. I have unlocked the bootloader and enabled USB debugging.
I am trying to install Q dp3, but everytime I select Q dp3 zip file and press ok, update manager immediately says "System update installation failed" with no specific error code or any leads.
I have tried:
-Redownloading the Q dp3 file from here (https://oxygenos.oneplus.net/OnePlus6Oxygen_22_OTA_003_all_1907120020_wipe_ae2a3b38959345b1.zip)
-Rebooting and trying again
-Relock and unlock the bootloader
-factory reset within the settings
The strange thing is, I can normally install oxygenos 9.0.8 full update file. So I suspected problem of the dp3 file. But redownloading didn't solve the problem.
Is there something I have missed out? Some settings I have to do? Specific conditions?
Searching haven't helped me much(I searched everywhere, but I think nobody has my problem).
If someone can help me, I will be grateful. Thanks!

Since your bootloader is unlocked anyway, you can flash Android Q DP3 zip using TWRP. Flash it on both slots. Haven't tried blu_spark, but mauronofrio's TWRP works with Q. Don't forget to format data.

remewer said:
Since your bootloader is unlocked anyway, you can flash Android Q DP3 zip using TWRP. Flash it on both slots. Haven't tried blu_spark, but mauronofrio's TWRP works with Q. Don't forget to format data.
Click to expand...
Click to collapse
Thanks! Will try that!
Can I ask you one more question? What is the best and convenient way to go back to stock? I used nexus 4 and mi a1 before, and both devices just had to use
fastboot roms to go back to complete stock. Is it same with OP6? Or do I have to use MSM tool or other things?

ddaggebi said:
Thanks! Will try that!
Can I ask you one more question? What is the best and convenient way to go back to stock? I used nexus 4 and mi a1 before, and both devices just had to use
fastboot roms to go back to complete stock. Is it same with OP6? Or do I have to use MSM tool or other things?
Click to expand...
Click to collapse
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.

remewer said:
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
Click to expand...
Click to collapse
Thanks you! Now I can flash away~

remewer said:
I think it's down to your preference. I prefer the fastboot ROMs simply because I haven't tried MSM download tool yet. But yeah, both fastboot ROMs and MSM download tool are available for OP6.
Click to expand...
Click to collapse
I successfully flashed Q dp3 thanks to you.
However, I can't boot TWRP with fastboot boot twrp.img method. Before updating to Q, it worked. Now, cmd line shows FAILED (remote: 'unknown command').
I have tested with newer versions of Fastboot, but the results were the same. Anybody knows how to solve this problem?

ddaggebi said:
I successfully flashed Q dp3 thanks to you.
However, I can't boot TWRP with fastboot boot twrp.img method. Before updating to Q, it worked. Now, cmd line shows FAILED (remote: 'unknown command').
I have tested with newer versions of Fastboot, but the results were the same. Anybody knows how to solve this problem?
Click to expand...
Click to collapse
Yep, it's a known issue with DP3 (or possibly earlier builds). Anyway, every time you flash a ROM, may it be stock or custom, you should always flash TWRP next. For now, you could try downgrading to Pie using fastboot ROMs.

remewer said:
Yep, it's a known issue with DP3 (or possibly earlier builds). Anyway, every time you flash a ROM, may it be stock or custom, you should always flash TWRP next. For now, you could try downgrading to Pie using fastboot ROMs.
Click to expand...
Click to collapse
Thank you so much. I don't know what I could've done without you. I'll try to downgrading. Still not accoustomed to how roms work in OP6. Guess I'll study more.
Again, thank you for kindly answering my noobish questions! It means a lot to me

ddaggebi said:
Thank you so much. I don't know what I could've done without you. I'll try to downgrading. Still not accoustomed to how roms work in OP6. Guess I'll study more.
Again, thank you for kindly answering my noobish questions! It means a lot to me
Click to expand...
Click to collapse
No problem. Read more about A/B partitions. It's actually just as easy to mod our phone once you know how A/B partitions work.

Please help me flash factory image of Pixel 3?

[EDIT:] I actually ended up solving this, as mentioned in the lower post, but I'm still having a bit of trouble with the part below where trying to flash twrp gives the error "FAILED (remote: Not allowed to flash (recovery))" so I'd still like help with that if possible. Thanks!
Hello,
I have a Pixel 3 that I got when it first came out, there was only one custom rom for it which I installed with TWRP, but the rom was kind of broken, so i just used the phone as a media player for a couple years, until I thought to check for new roms, and there are lots now. So I'm following the PixelDust installation instructions which say I absolutely must start by reverting stock rom. On my Samsung I used Odin, but there's nothing like that for this, except sources pointing to Android Flash Tool website, but after I tried flashing with that site, it just went into bootloader and said "no valid slots to boot", so it evidently failed. So my next thought was to flash it manually, so I downloaded the latest Blueline image from here. I'm using this guide, but it says to extract the zip and use the flash-all command, but when I extract this image I only get these files (see screenshot attachment). Another guide says there will be a file in that folder that I should extract that too but the only one that makes any sense is payload.bin and 7zip doesn't recognize that. And I haven't been able to get anything really comprehensible through Google searches. So I'm at a dead end. :/
So basically I'm hoping someone can give me a step-by-step instruction how to flash this rom. I'm not really a tech guy but I have a basic understanding, I've used ADB and fastboot before, following instructions though. If you can take the time to give me an idiot-proof instruction I'd really appreciate it because at the moment the phone's useless
Thanks!
EDIT:
I actually tried to at least flash TWRP so I could try to restore my nandroid of the other rom, but when I tried, I got the error:
Code:
D:\D Backup\Misc\nandroid\adbfastboot samsung a5>fastboot flash recovery
twrp-3.4.0-0-twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (4560 KB)...
OKAY [ 0.255s]
writing 'recovery'...
[B]FAILED (remote: Not allowed to flash (recovery))[/B]
finished. total time: 0.317s
And searches on that said it was because the bootloader is locked... but it's not. So I don't know why I can't even do that. :/ I'd like to at least get to something functional. >.< So I'd appreciate any help. Thanks!

Okay, well good news, I figured the main thing out by accident. I didn't realize there was a difference between factory image and ota image and I guess I got the ota, not the factory, which was when I unzipped it it just had meta-inf and not flash-all. But I also discovered how to sideload that ota and i did that, and now the phone is back to stock, hooray!
But I'm still having trouble getting TWRP back on it for the same reason listed above, so can you guys help me with that part?
lol thanks ^^;
PistolSlap said:
Hello,
I have a Pixel 3 that I got when it first came out, there was only one custom rom for it which I installed with TWRP, but the rom was kind of broken, so i just used the phone as a media player for a couple years, until I thought to check for new roms, and there are lots now. So I'm following the PixelDust installation instructions which say I absolutely must start by reverting stock rom. On my Samsung I used Odin, but there's nothing like that for this, except sources pointing to Android Flash Tool website, but after I tried flashing with that site, it just went into bootloader and said "no valid slots to boot", so it evidently failed. So my next thought was to flash it manually, so I downloaded the latest Blueline image from here. I'm using this guide, but it says to extract the zip and use the flash-all command, but when I extract this image I only get these files (see screenshot attachment). Another guide says there will be a file in that folder that I should extract that too but the only one that makes any sense is payload.bin and 7zip doesn't recognize that. And I haven't been able to get anything really comprehensible through Google searches. So I'm at a dead end. :/
So basically I'm hoping someone can give me a step-by-step instruction how to flash this rom. I'm not really a tech guy but I have a basic understanding, I've used ADB and fastboot before, following instructions though. If you can take the time to give me an idiot-proof instruction I'd really appreciate it because at the moment the phone's useless
Thanks!
EDIT:
I actually tried to at least flash TWRP so I could try to restore my nandroid of the other rom, but when I tried, I got the error:
Code:
D:\D Backup\Misc\nandroid\adbfastboot samsung a5>fastboot flash recovery
twrp-3.4.0-0-twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (4560 KB)...
OKAY [ 0.255s]
writing 'recovery'...
[B]FAILED (remote: Not allowed to flash (recovery))[/B]
finished. total time: 0.317s
And searches on that said it was because the bootloader is locked... but it's not. So I don't know why I can't even do that. :/ I'd like to at least get to something functional. >.< So I'd appreciate any help. Thanks!
Click to expand...
Click to collapse

PistolSlap said:
Okay, well good news, I figured the main thing out by accident. I didn't realize there was a difference between factory image and ota image and I guess I got the ota, not the factory, which was when I unzipped it it just had meta-inf and not flash-all. But I also discovered how to sideload that ota and i did that, and now the phone is back to stock, hooray!
But I'm still having trouble getting TWRP back on it for the same reason listed above, so can you guys help me with that part?
lol thanks ^^;
Click to expand...
Click to collapse
If you flashed the latest image, you are on Android 11. TWRP will not work with Android 11. There is not even an official Pixel 3 TWRP for Android 10.

dcarvil said:
If you flashed the latest image, you are on Android 11. TWRP will not work with Android 11. There is not even an official Pixel 3 TWRP for Android 10.
Click to expand...
Click to collapse
THIS! theres no functional twrp and it looks like there may not be one at all. i recently reverted to android 10 so that i could go back to DirtyUnicors. i recommend waiting awhile longer for stable R ROMs.

Ok but this happened with Android 8. I didn't flash the latest image but actually the earliest. And come to think of it it happened even before the flash when there wasn't even an OS at that point. (The phone was wiped but no OS was installed.) so I tried it both then and after I got Android 8 installed and same disallowed error.
dcarvil said:
If you flashed the latest image, you are on Android 11. TWRP will not work with Android 11. There is not even an official Pixel 3 TWRP for Android 10.
Click to expand...
Click to collapse

PistolSlap said:
Ok but this happened with Android 8. I didn't flash the latest image but actually the earliest. And come to think of it it happened even before the flash when there wasn't even an OS at that point. (The phone was wiped but no OS was installed.) so I tried it both then and after I got Android 8 installed and same disallowed error.
Click to expand...
Click to collapse
Are you sure you are on Android 8? The Pixel 3 shipped with Android 9. There is no Android 8 for the Pixel 3 listed in the link you gave in your original post.
If you really are on Android 8, or even Android 9, try the instructions on the Pixel 3 TWRP website at https://twrp.me/google/googlepixel3.html. The instructions you listed in your original post are for a Nexus 6, not a Pixel 3.

dcarvil said:
Are you sure you are on Android 8? The Pixel 3 shipped with Android 9. There is no Android 8 for the Pixel 3 listed in the link you gave in your original post.
If you really are on Android 8, or even Android 9, try the instructions on the Pixel 3 TWRP website at https://twrp.me/google/googlepixel3.html. The instructions you listed in your original post are for a Nexus 6, not a Pixel 3.
Click to expand...
Click to collapse
Ah sorry I meant Android 9.
Okay, cool I followed those instructions and it worked. Thanks! I'm not sure what I did wrong before.
One other question: My older phone is a Samsung Galaxy A5, which doesn't have A/B slots, and I've looked into it but I'm still not exactly sure how they work. Is it correct that they're both system images? So if I have stock in slot A can I install a custom rom in slot B and switch between them? Or have I got that wrong?
Also, when I was first flashing a rom onto this Pixel 3, I tried to do a nandroid backup, which for some reason failed to restore properly, and someone mentioned it was because it was a slot device? So does that mean nandroid backups don't work on the PIxel 3?
Thanks for your help. I'm not a compsci guy or android dev, so this stuff takes a bit more for me to quite understand. :")

PistolSlap said:
Ah sorry I meant Android 9.
Okay, cool I followed those instructions and it worked. Thanks! I'm not sure what I did wrong before.
One other question: My older phone is a Samsung Galaxy A5, which doesn't have A/B slots, and I've looked into it but I'm still not exactly sure how they work. Is it correct that they're both system images? So if I have stock in slot A can I install a custom rom in slot B and switch between them? Or have I got that wrong?
Also, when I was first flashing a rom onto this Pixel 3, I tried to do a nandroid backup, which for some reason failed to restore properly, and someone mentioned it was because it was a slot device? So does that mean nandroid backups don't work on the PIxel 3?
Thanks for your help. I'm not a compsci guy or android dev, so this stuff takes a bit more for me to quite understand. :")
Click to expand...
Click to collapse
I have no experience with TWRP on a Pixel 3, so I can't answer your question about nandroid backups. Perhaps someone else can answer. The question on the A5 should be asked in a different forum.
The difference in the instructions for the Nexus 6 and Pixel 3, is that you boot TWRP, then install from TWRP for the Pixel 3.