Database Info

Sideloading OTAs, in order or can skip?

So I was away from my computer when the January Security update came out so Im on the December update.
I would like to know can I just jump straight to the Feb update when its available or do I need to do Jan first then Feb?
im unlocked, rooted, ex kernel, google store phone. thanks.

You can just jump.

my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks

kidhudi said:
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
Click to expand...
Click to collapse
I think downgrading via OTA it's quite impossible.
You have to wipe and flash the full factory image.

damn it thats what i was afraid of.
thanks

kidhudi said:
damn it thats what i was afraid of.
thanks
Click to expand...
Click to collapse
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.

TonikJDK said:
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
Click to expand...
Click to collapse
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.

kidhudi said:
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
Click to expand...
Click to collapse
Time to start clearing data on the dialer related apps, or reset the phone. I am hopeful that will help you. If it was soley update related the forum would be blowing up with complaints.
Now did something go wrong with your update... I'll buy that.

i just assumed it was the april security update it started acting up around the same time. i thought maybe a crappy download
i already did a few factory resets. tried third party dialers. everything i could think of.
what really sucks is i am 3 months out of the 1 year google warranty. so i am pretty much screwed.
thanks for your help bro
i will try to sideload the latest ota.. if it is still jacked up then it is probably hardware related
what sucks is i am still paying it off and it is virtually unusable lol.. at least i can text

Locking bootloader removes root? Also more Questions. [Phone Gone Now]

I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.

Superorb said:
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Click to expand...
Click to collapse
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.

BakedOnSomeSour said:
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
Click to expand...
Click to collapse
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?

Superorb said:
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985

BakedOnSomeSour said:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
Click to expand...
Click to collapse
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?

Superorb said:
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Click to expand...
Click to collapse
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.

BakedOnSomeSour said:
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
Click to expand...
Click to collapse
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.

Superorb said:
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Click to expand...
Click to collapse
Same. if you need any additional help with the process just let me know.

BakedOnSomeSour said:
Same. if you need any additional help with the process just let me know.
Click to expand...
Click to collapse
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.

Superorb said:
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Click to expand...
Click to collapse
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.

BakedOnSomeSour said:
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
Click to expand...
Click to collapse
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.

Superorb said:
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Click to expand...
Click to collapse
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.

BakedOnSomeSour said:
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
Click to expand...
Click to collapse
Ok, I've downloaded all 3 zip files from my build at over 2gigs.

Superorb said:
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Click to expand...
Click to collapse
Ok now extract the files from the update.zip folder. Then take the UPDATE.app from the extracted files and open it with update extractor: https://forum.xda-developers.com/showthread.php?t=2433454
After that your ready to follow the steps on the other guide.

So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?

Superorb said:
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Click to expand...
Click to collapse
Edit: Before trying below steps. Just put the files from "BLN-L24_hw_usa"(b360) into dload folder and flash with dload. It might update the version.img without the needs for the steps below. if that brings the build number back to b360 use the hisui(PC) application to connect to the phone and update
Ok i forgot to mention something. The reason you dont have a update option is because you are on b360 which never had a button. Your build number on your phone will say b366 but thats incorrect. You cant receive an ota automatically because the phone thinks its already on the latest version. You need to take the UPDATE.APP from the "BLN-L24_hw_usa" (b360) folder and extract the VERSION.IMG file. It needs to be flashed with TWRP because fastboot wont work for some reason. That file will fix the build number and change it back to b360 so you can receive the OTA which will also restore the missing apps and features. That means you have to unlock the bootloader. Flash twrp. Flash the vendor.img with twrp and then do the dload method.
You have all the files and have done it already so this time will be easier. Ive done this way too many times with this phone. Sorry i forgot the mention the one step

Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.

Superorb said:
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Click to expand...
Click to collapse
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.

BakedOnSomeSour said:
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
Click to expand...
Click to collapse
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.

Superorb said:
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Click to expand...
Click to collapse
Its not difficult. In order to connect to hisuite you need to enable developer settings and allow usb debugging or type hisuite in the settings search bar and click "allow HiSuite to use HDB". I got this phone for christmas and i already know a ton about it. It may seem complicated now but its really nothing.

VZN locked, Pixel stuck at bootloader, recovery mode fails -- what now?

Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK

TromboneKenny said:
Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK
Click to expand...
Click to collapse
Try reflashing the same factory image ur on

If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.

shagbag913 said:
If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.
Click to expand...
Click to collapse
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA

KittyRgnarok said:
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA
Click to expand...
Click to collapse
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong

shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
Yeah that's what I'm thinking. OP test this and if anything breaks report back

That's pretty odd that it would just break like that. If he hasn't messed with anything software related it could be a hardware issue

shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?

TromboneKenny said:
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?
Click to expand...
Click to collapse
I don't think it would be different. This sounds like a hardware issue, not software.

Pixel bricked after trying to install the newest Android Q Beta

Hey everyone,
I have the following issue with my recently purchased Google Pixel smartphone. The other day I was trying to update to the Android Q Beta, but in the middle of the process the phone turned off.
All I have now is a phone with a locked bootloader. I cannot neither unlock the bootloader nor sideload any OTA (when I try doing so I get a "no devices/emulators found" message). I tried unlock the bootloader with the Unified Anroid Toolkit, but no go because of the same message.
Any thoughts how to revive it?

To get more, better answers. Full battery?, what was working system, unlocked?, update Q well exactly how, ota? Verify cables, different pc, verify drivers? When described as brick= what, how, display?. No matter what you will need bootloader to get working. Then factory images flash.

kkjb said:
To get more, better answers. Full battery?, what was working system, unlocked?, update Q well exactly how, ota? Verify cables, different pc, verify drivers? When described as brick= what, how, display?. No matter what you will need bootloader to get working. Then factory images flash.
Click to expand...
Click to collapse
It bricked while installing the beta and simultaneously charging approximately at 60% battery. Prior to trying to install the latest beta 3 I had the beta 2. Updated the system officially via Settings. Unsure if it was unlocked and I'd just bought the Pixel and randomly decided to update it.
The usb-c cable is fine and is working with other devices. It's also the same with other PCs.
All I have is a bootloader with some options - Start/ Restart Bootloader/Recovery mode (it won't load)/Barcodes.

So when using adb "fastboot devices" command do you get your device number returned? If so, was the data important to keep not wiped? Because a factory images flash is next. Or can look search on manually flashing bootloader or recovery or twrp recovery too. Data most likely gone with Q beta 2 but you may get it back. I would factory flash since you have fastboot available... Best so all of memory is correctly wiped, flashed.

kkjb said:
So when using adb "fastboot devices" command do you get your device number returned? If so, was the data important to keep not wiped? Because a factory images flash is next. Or can look search on manually flashing bootloader or recovery or twrp recovery too. Data most likely gone with Q beta 2 but you may get it back. I would factory flash since you have fastboot available... Best so all of memory is correctly wiped, flashed.
Click to expand...
Click to collapse
Yes, I get a device number with this command. I usually back up all the necessary data, so I don't really need what's on the phone and I can wipe it.
How can I do a factory image flash?

Best case then is to flash factory image, download either Q beta 3 or May stock image. Completely wipes and starts from scratch. Look at the many instructions, if need more guidance under flashing factory images. Q beta 3 is good, but if you flash Q through this process can't OTA to next version. So if that's a issue do May image then go back to ota through as before.

kkjb said:
Best case then is to flash factory image, download either Q beta 3 or May stock image. Completely wipes and starts from scratch. Look at the many instructions, if need more guidance under flashing factory images. Q beta 3 is good, but if you flash Q through this process can't OTA to next version. So if that's a issue do May image then go back to ota through as before.
Click to expand...
Click to collapse
But as far as I understand, I can't flash a factory image with a locked bootloader, can I? Also I don't have OEM unlocked

Correct. When you got the device number back from fastboot I guessed it was authorized. Which means OEM unlock. So I am at a loss at how much more to "help". Is your pixel unlockable in the first place? Verizon or carrier locked?

kkjb said:
Correct. When you got the device number back from fastboot I guessed it was authorized. Which means OEM unlock. So I am at a loss at how much more to "help". Is your pixel unlockable in the first place? Verizon or carrier locked?
Click to expand...
Click to collapse
Well, I have no idea if it's unlockable. I'm from Russia, so it's not Verizon or any other.

Pixels have unlockable or not bootloaders. Carrier sim lock (Verizon us carrier) have a exploit to unlock. In your case, if I have it right- accepted ota
Update to Q beta. As first post. So when failed, and would not boot to G screen. Power off then on if you hold down power + volume get bootloader. Now options are limited to restart bootloader, off, start, recovery. Tried and nothing, then went to recovery....got android icon laying down with red warning. So when you have that screen a different set of button pushes will give more options. So search how to factory erase through recovery. Hopefully will wipe bad q and return to before system...the one that was running correctly before last accept ota q.

kkjb said:
Pixels have unlockable or not bootloaders. Carrier sim lock (Verizon us carrier) have a exploit to unlock. In your case, if I have it right- accepted ota
Update to Q beta. As first post. So when failed, and would not boot to G screen. Power off then on if you hold down power + volume get bootloader. Now options are limited to restart bootloader, off, start, recovery. Tried and nothing, then went to recovery....got android icon laying down with red warning. So when you have that screen a different set of button pushes will give more options. So search how to factory erase through recovery. Hopefully will wipe bad q and return to before system...the one that was running correctly before last accept ota q.
Click to expand...
Click to collapse
Recovery mode is not working for me either. Any chance to factory erase it any other way?

https://www.androidexplained.com/pixel-factory-reset/ explains hard factory reset with bootloader. If still can't reset through that method, then I believe no options. I would search pixel threads with "hard brick" or "soft brick" and see if any other way.

im in the same boat. bootloader locked, can not access recovery. OEM-Unlock from system unchecked. fastboot commands needs unlocked bootloader. no idea what to do.

kkjb said:
https://www.androidexplained.com/pixel-factory-reset/ explains hard factory reset with bootloader. If still can't reset through that method, then I believe no options. I would search pixel threads with "hard brick" or "soft brick" and see if any other way.
Click to expand...
Click to collapse
Unfortunately, it explains the reset only in case a pixel can be turned on or factory mode is available.

wahur1 said:
im in the same boat. bootloader locked, can not access recovery. OEM-Unlock from system unchecked. fastboot commands needs unlocked bootloader. no idea what to do.
Click to expand...
Click to collapse
Just checked your thread and all I have to say I'm in a completely similar situation.

Might be a longshot but I remember a few people saying about using the fastboot continue command to get a soft bricked pixel booted. Not sure on their mileage using it but worth a punt.

junglism93 said:
Might be a longshot but I remember a few people saying about using the fastboot continue command to get a soft bricked pixel booted. Not sure on their mileage using it but worth a punt.
Click to expand...
Click to collapse
Yeah, I tried this one, but still no go. Thanks.

mighty_ok said:
Just checked your thread and all I have to say I'm in a completely similar situation.
Click to expand...
Click to collapse
I guess its a paperweight now.

Pixel 3 Phone keeps shutting down randomly after July security update

Hi All,
My wife's phone (stock Pixel 3 - not rooted) updated to the July security release last night and since then, the phone keeps shutting down after 30-60 seconds. I've performed a factory reset and it's stable all through the setup process until it updates what looks like the play libraries. Any thoughts on how to keep it stable? Thanks in advance, I've been on XDA for a while and the forums have been awesome.

rbillings said:
Hi All,
My wife's phone (stock Pixel 3 - not rooted) updated to the July security release last night and since then, the phone keeps shutting down after 30-60 seconds. I've performed a factory reset and it's stable all through the setup process until it updates what looks like the play libraries. Any thoughts on how to keep it stable? Thanks in advance, I've been on XDA for a while and the forums have been awesome.
Click to expand...
Click to collapse
Is her phone bootloader unlocked (or capable of being unlocked)? If so, you can do a flash-all of the factory image (you can edit the flash-all batch file to get rid of the -w and retain apps/user files or leave the batch file as is and do a full reset). https://developers.google.com/android/images Otherwise, possibly the best place to start (and it can be done without unlocking the bootloader) would be to sideload the July OTA. https://developers.google.com/android/ota

sliding_billy said:
Is her phone bootloader unlocked (or capable of being unlocked)? If so, you can do a flash-all of the factory image (you can edit the flash-all batch file to get rid of the -w and retain apps/user files or leave the batch file as is and do a full reset). https://developers.google.com/android/images Otherwise, possibly the best place to start (and it can be done without unlocking the bootloader) would be to sideload the July OTA. https://developers.google.com/android/ota
Click to expand...
Click to collapse
Thanks - I'll start with the sideloading of the July OTA. I've tried unlocking the bootloader, but it seems the refurb phones I purchased came from Verizon stock, so the setting to allow the bootloader to be unlocked is grayed out (unless there's another way - flashing unlock_critical or unlock_bootloader isn't supported).

rbillings said:
Thanks - I'll start with the sideloading of the July OTA. I've tried unlocking the bootloader, but it seems the refurb phones I purchased came from Verizon stock, so the setting to allow the bootloader to be unlocked is grayed out (unless there's another way - flashing unlock_critical or unlock_bootloader isn't supported).
Click to expand...
Click to collapse
Unfortunately, there is no other method to unlock. The Verizon units are locked down very hard. The OG Pixels from Verizon had an exploit found early on that was patched immediately and another that was found right as the Pixel 2 was coming out. The Verizon Pixel 2 never got exploit unlocked nor has the 3 in almost a year of various peoples' attempts. In reality, there is little incentive for anyone with the necessary skills to crack it since Google sells the version that is unlockable.
Good luck with the sideload. Keep in mind that the sideload will install to the other slot and then reboot to the sideloaded image (in case you have more issues). If you continue to have issues, the dreaded factory reset is the next step.

sliding_billy said:
Unfortunately, there is no other method to unlock. The Verizon units are locked down very hard. The OG Pixels from Verizon had an exploit found early on that was patched immediately and another that was found right as the Pixel 2 was coming out. The Verizon Pixel 2 never got exploit unlocked nor has the 3 in almost a year of various peoples' attempts. In reality, there is little incentive for anyone with the necessary skills to crack it since Google sells the version that is unlockable.
Good luck with the sideload. Keep in mind that the sideload will install to the other slot and then reboot to the sideloaded image (in case you have more issues). If you continue to have issues, the dreaded factory reset is the next step.
Click to expand...
Click to collapse
Sadly, that didn't work, and I've already done the factory reset mode, since that was the only way to get into the phone originally. I'll keep playing, I have some logcats, but I'm not seeing anything out of the ordinary, except previously, once all of the the software finally got reloaded from the backup (multiple reboots) it shutdown at a similar point.
I'll update with results after I try a few other things. Thinking possible HW issue, but strange that it was working until yesterday's update...

rbillings said:
Sadly, that didn't work, and I've already done the factory reset mode, since that was the only way to get into the phone originally. I'll keep playing, I have some logcats, but I'm not seeing anything out of the ordinary, except previously, once all of the the software finally got reloaded from the backup (multiple reboots) it shutdown at a similar point.
I'll update with results after I try a few other things. Thinking possible HW issue, but strange that it was working until yesterday's update...
Click to expand...
Click to collapse
Possibly hardware, but too hard to diagnose that. The only thing I would say is to not restore any backed up apps or anything. They will be in your library if you need to install them. Just keep it as stock as possible after the factory backup until you have at least had a chance to put it through its paces for a little while.