Related
Hey guys.
I have a Verizon pixel, once the 7.1.2 files were released too Google I decided to get wild and crazy and sideloaded the OTA myself.
The problem is I sideloaded the J series rom by mistake, and not the E series rom. The J series is the euro spec version
I tried to correct it by reflashing the E series but I received an error that the timestamp on the OTA was sooner than the J series and downgrading was not allowed
Does anyone have a download link to the Verizon specific OTA file for 7.1.2 so I can attempt to flash and correct???
Is the only other fix trying to do a full system reimage or the previous 7.1.1 build ??
Thanks
Sent from my Pixel using Tapatalk
Joe92T said:
Hey guys.
I have a Verizon pixel, once the 7.1.2 files were released too Google I decided to get wild and crazy and sideloaded the OTA myself.
The problem is I sideloaded the J series rom by mistake, and not the E series rom. The J series is the euro spec version
I tried to correct it by reflashing the E series but I received an error that the timestamp on the OTA was sooner than the J series and downgrading was not allowed
Does anyone have a download link to the Verizon specific OTA file for 7.1.2 so I can attempt to flash and correct???
Is the only other fix trying to do a full system reimage or the previous 7.1.1 build ??
Thanks
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Use the full E image and take out the -w from flash-all.bat so you don't wipe SD.
Sent from my Pixel using XDA-Developers Legacy app
That may work except I would be on googles branch and not Verizon's. So I wouldn't get any Verizon otas, correct?
Sent from my Pixel using Tapatalk
Joe92T said:
That may work except I would be on googles branch and not Verizon's. So I wouldn't get any Verizon otas, correct?
Click to expand...
Click to collapse
I currently have N2G47E on my Verizon purchased Pixel now. No issues that I've run into.
Joe92T said:
That may work except I would be on googles branch and not Verizon's. So I wouldn't get any Verizon otas, correct?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Use E. The new VZW firmware isn't on Google's site. I flashed E and all is just fine.
Sent from my Pixel using XDA-Developers Legacy app
Joe92T said:
Hey guys.
I have a Verizon pixel, once the 7.1.2 files were released too Google I decided to get wild and crazy and sideloaded the OTA myself.
Click to expand...
Click to collapse
Are you bootloader unlocked?
No
Sent from my Pixel using Tapatalk
So I tried to flash the stock Google firmware for the E build and got told no due to locked bootloader... I can't even flash official images?
Sent from my Pixel using Tapatalk
Joe92T said:
So I tried to flash the stock Google firmware for the E build and got told no due to locked bootloader... I can't even flash official images?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Not with a locked bootloader.
Sent from my Pixel using XDA-Developers Legacy app
So the only option I have is to find ota packages with a older timestamp?
Sent from my Pixel using Tapatalk
Joe92T said:
So the only option I have is to find ota packages with a older timestamp?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
If it is running fine on J then why not wait until May and sideload or take the OTA then.
I'm hearing there is a known Verizon issue with Volte on the K build anyway.
Sent from my Pixel using XDA-Developers Legacy app
I really wish I could factory flash the entire new image. I almost feel like I've "corrupted" it by installing this incorrect OTA and that even if I flash a new ota going forward that there may be some old lingering stuff kicking around from this old one
Sent from my Pixel using Tapatalk
Joe92T said:
I really wish I could factory flash the entire new image. I almost feel like I've "corrupted" it by installing this incorrect OTA and that even if I flash a new ota going forward that there may be some old lingering stuff kicking around from this old one
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Nothing is corrupted, relax. Wait for the OTA next time and then factory reset it if that will ease your mind. But it's really not necessary the phone is fine. You might be able to sign up for the beta, it will wipe the device, then roll back with another wipe and accept the OTA when it arrives. Probably more trouble than it's worth.
Sent from my Pixel using XDA-Developers Legacy app
Protibus said:
Use the full E image and take out the -w from flash-all.bat so you don't wipe SD.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Okay, this one caught my eye. The OP, like me, has a Verizon Pixel. So my phone's bootloader is locked until someone finds an appropriate exploit and publishes it, if ever. And I also sideloaded the N2G47J image by mistake, didn't know it was Deutsche Telekom, thought it was just the latest *sigh*. Learned my lesson about doing research.
After sideloading N2G47J, I did try to sideload the N2G47E image, and that failed because the E image is earlier than the J image, and it won't let me flash an earlier image (bootloader locked).
Are you saying that I can flash the E image on top of the J image without failing if I take out the -w from flash-all.bat? That would be great, but doesn't make a lot of sense to me. Can you please tell me if that's really the case, that if I don't use -w during the flash, it will allow an older image to be flashed?
Otherwise I'll have to wait for next month's update to get my phone working right again. At the moment, it has the "Wi-Fi calling" setting set to "Cellular preferred", which causes the phone to use up a lot of battery trying to make a low cellular signal work. When I've had "Wi-Fi calling" set to "Wi-Fi preferred", that doesn't happen since if you prefer Wi-Fi calling, apparently the phone doesn't care about the cell signal as long as you're on Wi-Fi. So at home, I have to set it on Airplane mode and turn Wi-Fi back on to keep my battery from getting drained too quickly. I'm anxious to get this problem fixed, since I forget to turn Airplane mode off when I leave the house and miss calls and texts.
Thanks!
RogerSC said:
Are you saying that I can flash the E image on top of the J image without failing if I take out the -w from flash-all.bat? That would be great, but doesn't make a lot of sense to me. Can you please tell me if that's really the case, that if I don't use -w during the flash, it will allow an older image to be flashed?
Click to expand...
Click to collapse
No you can not do that, you are bootloader locked.
RogerSC said:
Okay, this one caught my eye. The OP, like me, has a Verizon Pixel. So my phone's bootloader is locked until someone finds an appropriate exploit and publishes it, if ever. And I also sideloaded the N2G47J image by mistake, didn't know it was Deutsche Telekom, thought it was just the latest *sigh*. Learned my lesson about doing research.
After sideloading N2G47J, I did try to sideload the N2G47E image, and that failed because the E image is earlier than the J image, and it won't let me flash an earlier image (bootloader locked).
Are you saying that I can flash the E image on top of the J image without failing if I take out the -w from flash-all.bat? That would be great, but doesn't make a lot of sense to me. Can you please tell me if that's really the case, that if I don't use -w during the flash, it will allow an older image to be flashed?
Otherwise I'll have to wait for next month's update to get my phone working right again. At the moment, it has the "Wi-Fi calling" setting set to "Cellular preferred", which causes the phone to use up a lot of battery trying to make a low cellular signal work. When I've had "Wi-Fi calling" set to "Wi-Fi preferred", that doesn't happen since if you prefer Wi-Fi calling, apparently the phone doesn't care about the cell signal as long as you're on Wi-Fi. So at home, I have to set it on Airplane mode and turn Wi-Fi back on to keep my battery from getting drained too quickly. I'm anxious to get this problem fixed, since I forget to turn Airplane mode off when I leave the house and miss calls and texts.
Thanks!
Click to expand...
Click to collapse
You cannot flash a full image with a locked bootloader, must be unlocked. With a locked bootloader you are only able to sideload an OTA using ADB.
Sent from my Pixel using XDA-Developers Legacy app
Protibus said:
You cannot flash a full image with a locked bootloader, must be unlocked. With a locked bootloader you are only able to sideload an OTA using ADB.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, that's what I did, adb sideloaded the J OTA that I downloaded from the Google Android Developers site: https://developers.google.com/android/ota . From what the OP said, that's what they did, too. And then adb sideloading the E OTA on top of that failed, since it is an earlier OTA. So I'm currently looking for a solution for getting the E update on my phone.
So you're not talking about using adb sideload, then, like the OP was? I'm totally confused, what were you suggesting to the OP that he do to be able to get the E image on a Verizon Pixel that already had the J image? I guess that I'm not following how I can do this with a locked bootloader? I'd love to get a clue how this could be done? Doesn't matter to me how much work it is, I'm open to learning about how to do this, and gathering whatever tools I would need?
It just occurred to me, were you assuming that the OP has an unlocked bootloader, then? I made the opposite assumption I guess, since they were using adb sideload in the first place
Thanks!
RogerSC said:
Yes, that's what I did, adb sideloaded the J OTA that I downloaded from the Google Android Developers site: https://developers.google.com/android/ota . And then adb sideloading the E OTA on top of that failed, since it is an earlier OTA. So I'm currently looking for a solution for getting the E update on my phone.
So you're not talking about using adb sideload, then? I'm totally confused, what were you suggesting to the OP that he do to be able to get the E image on a Verizon Pixel that already had the J image? I guess that I'm not following how I can do this with a locked bootloader? I'd love to get a clue how this could be done? Doesn't matter to me how much work it is, I'm open to learning about how to do this, and gathering whatever tools I would need?
Thanks!
Click to expand...
Click to collapse
Sideloading an OTA you use ADB, bootloader does not have to be unlocked. Flashing a full image, you use Fastboot which requires an unlocked bootloader. The beauty of having an unlocked bootloader is if you mess up it gives you the ability to flash a full image to put you back to some full stock condition.
Sent from my Pixel using XDA-Developers Legacy app
I would bet that the Verizon OTA has a later timestamp then both of the Google official images. So we should be able to flash that to fix it over E or J
The problem is I can't find a download link to the Verizon OTA anywhere at all. No one has it
Sent from my Pixel using Tapatalk
Joe92T said:
I would bet that the Verizon OTA has a later timestamp then both of the Google official images. So we should be able to flash that to fix it over E or J
The problem is I can't find a download link to the Verizon OTA anywhere at all. No one has it
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
I would try it if I had a copy of it.
Sent from my Pixel using XDA-Developers Legacy app
Have a major issue. lyft driver app will not work on the pixel 2 with Pie if you do a fresh install. it only works if you do an upgrade.
No clue what causes it, don't really care.
I need to roll back to oreo immediately but when I try to use adb to do the full ota oreo update and it errors out and says "update package is older than the current build.....downgrade not allowed"
Can anyone assist?
Have you try this
https://android.gadgethacks.com/how-to/downgrade-from-android-9-0-pie-back-oreo-your-pixel-0183424/
Sent from my Pixel 2 using Tapatalk
Voloshvett said:
Have you try this
https://android.gadgethacks.com/how-to/downgrade-from-android-9-0-pie-back-oreo-your-pixel-0183424/
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I presume that the bootloader is locked and thus there is no way to roll back. If it's bl unlocked then he can always flash an older factory image but not an OTA.
https://www.essential.com/developer/current-builds
Also, just received it on my phone this very moment.
Downloading now! Came to post this exact thing.
UPDATE
Screen shot for those interested
changelog?
mookiexl said:
changelog?
Click to expand...
Click to collapse
Check the screenshot one post right before your!
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
ziddey said:
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
Click to expand...
Click to collapse
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
If I try to unroot by restoring images it says "Stock backup does not exist!"
sruel3216 said:
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
Click to expand...
Click to collapse
I believe you'd fail the OTA if you have an altered boot, but you can try.
oracleoftruth said:
If I try to unroot by restoring images it says "Stock backup does not exist!"
Click to expand...
Click to collapse
I dumped the old boot before rebooting just in case: https://drive.google.com/file/d/11MjB4kTOHuxbUyHe_kIwZ1d0wqp6-Nmf/view?usp=sharing
You can flash it to your boot slot while rooted, take the OTA, and then install magisk to the other slot before rebooting.
Drop a shell.
Determine current boot slot: getprop |grep boot.slot
Flash the boot: dd if=/path/to/boot_b.img of=/dev/block/by-name/boot_b (change to boot_a if that's your slot)
Of course, don't reboot since you'll lose root. Instead, you should now be able to take the OTA, and then use magisk to patch the other slot before rebooting.
Magisk should now have a backup for next time, so you can uninstall/ota/install in the future.
Nice...4 days in, and patched with the security update already.
ziddey said:
I believe you'd fail the OTA if you have an altered boot, but you can try.
Click to expand...
Click to collapse
Was curious cuz I was able to update the OTA on my pixel when rooted with custom kernel.
For some reason after I ran the magisk uninstaller and made sure to flash the stock boot image I still ran into problems updating via OTA and after sideloading the OTA for the Sept Update with success I found that TWRP would seem to freeze whenever it got to the main screen for some reason. I was able to use adb commands to reboot to bootloader and flash the stock kernel for the update and was able to boot normally. Just wondering if anybody else is having issues with TWRP freezing after installing the security update and yes I did remove fingerprint and lock screen security before booting into TWRP so I know its not something from that causing it to freeze.
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Just installed patch. Scrolling feels so much better, especially when scrolling slow.
gorm said:
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Click to expand...
Click to collapse
That's exactly what happened to me.. a user on /r/essential said they had the same issue; frustrating!
I'm going to be going back to 8.1 via fastboot, and then flashing 9.0 august, THEN fastbooting september, and if that doesn't work, I'm going to fastboot 9.0 august and then try OTA to
get my screen back.
Really weird stuff.
EDIT: Here's a supposed fix for those with the touchscreen issue - https://www.reddit.com/r/essential/comments/9d0lg3/for_anyone_having_trouble_with_touchscreen_not/
I don't know if we're allowed to link to reddit or not, but I'm doing that fix now.
Thanks!
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
jon_ybanez said:
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
Click to expand...
Click to collapse
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
beard805 said:
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
Click to expand...
Click to collapse
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Sadly, I don't know much about the SIM side of the issue
Hope someone with more knowledge can chime in!
jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Are you rooted? Here are the unlocked modemst files: https://drive.google.com/file/d/1LQC-2QOC-PWX7vza-82tpwFrnUjaGZVq/view?usp=sharing
You can try to dd them:
Code:
dd if=/path/to/modemst1.img of=/dev/block/by-name/modemst1
dd if=/path/to/modemst2.img of=/dev/block/by-name/modemst2
Would be a good idea to backup your current images
from https://forum.xda-developers.com/essential-phone/how-to/discussion-brainstorm-sim-unlock-t3724135
after update experienced problem with BLOD.
after freezing I've managed to boot but for short time.
is there any fix that available like for nexus6p and nexus5x?
Can you get to fastboot/bootloader?
yes, except bootloader locked. can't get enough time to unlock it in settings
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
guotti said:
thanks for suggesting, but it wouldn't fix the phone. in order to get to recovery i still have to heat up phone to start appropriately
Click to expand...
Click to collapse
Have you uhhhhhhhh /tried it/
KittyRgnarok said:
Have you uhhhhhhhh /tried it/
Click to expand...
Click to collapse
yes, the phone reboots before finish
So, it is heating when you try booting bootloader and then recovery?
Sent from my Google Pixel using XDA Labs
yep, it won't start without heating
So it's heating itself even when booted to only bootloader?
That's very weird, never heard of that before.
When that's the case, maybe it's time for a replacement
Any warranty left maybe?
Sent from my Google Pixel using XDA Labs
Sgace said:
Tried to boot recovery from bootloader? I believe it's possible to flash a full ota image with lock bootloader, but someone correct me if i am wrong.
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
Bro, i also have the same problem as OP. I am able to reach recovery and i also did a OTA flash but the device is still bootlooping. Presently, I am trying to flash a factory image but my device's bootloader is locked and i cant turn on OEM unlock from developer options as its greyed out and unpressable.
Please help me in flashing the factory image, the phone has no passwords or google account signed in atm.
Thanks in advance, I will be waiting anxiously for ur reply.
Click to expand...
Click to collapse
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Sgace said:
If it's bootlooping, how did you see OEM unlock is greyed out?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
jman315 said:
I have 2 Pixels that both have the same symptom. I was lucky enough to get them to boot so I could unlock the bootloader, but flashing the factory image didn't make any difference. Based on what I've seen on the Google forums, it appears some of theses devices have faulty memory which is most likely the cause of the bootloop. Both of mine have Samsung memory. I'd be curious if your device does as well.
Click to expand...
Click to collapse
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
Do you have a Verizon pixel maybe? Cause OEM unlock should not be grayed out, even with locked bootloader.
Sent from my Google Pixel using XDA Labs
Cosmic Radiation said:
It boots up sometimes for 2-3 mins, reaches the lockscreen etc, i can get to the settings and turn on dev tools and then i see thats its greyed out. Within 2-3mins, the device restarts again
Yes, in the bootloader its written that mine also has samsung memory. Is this repairable? have you gotten yours working?
Click to expand...
Click to collapse
No, neither device is reliable or usable. Sometimes after it's been off for a while, it will power on and be functional for a short period of time. If the memory is faulty, then I believe the motherboard has to be replaced which isn't worth the cost of the repair. I may contact google support and see if they may give me a trade in credit for a pixel 2 or 3.
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Cosmic Radiation said:
my pixel turned out to be verizon, i was able to unlock bootloader and flash a factory image.. The problem still exists. Bootloops are still happening:crying:
Click to expand...
Click to collapse
Yep. Same issue here. Our devices are likely paperweights I'm afraid.
Can confirm, I woke up to an infinite bootloop this morning after applying the December security patch. Seems to be a hardware issue that just kills the phone.
Have you guys have tried to cool the phone down like putting it on top of an ice bag with saltwater, like a zip lock bag, give it a minute on top of the brine and then try? Should give you some time until you can get into the rom and tap the unlock button?
Has anyone else given it a go on this phone yet? So far I think its working pretty well, with only a couple slowdowns.
Has anyone else noticed a bit of a slowdown with wifi? Sometimes I have to kick it over to LTE to login to apps, even though I can run speed tests and things.
Just wanted to see what other people were experiencing with the beta, sorry if this the wrong place for this.
Other than poor "stand by" battery drainage for me, I think it works pretty good.
But, Android Q it's not on Pixel 3A, isn't it?
Xtremeviper said:
But, Android Q it's not on Pixel 3A, isn't it?
Click to expand...
Click to collapse
Not via OTA, you can pick up the system image from the website and flash it manually though.
As to the OP, I gave it a shot for a couple days but I kept getting a bug where I'd unlock the phone and just get a black screen so I got frustrated and flashed back lol I hope the OTA thats supposedly coming next month fixes it up so it could be a daily driver.
Thanks antp121
I tried to find from official website the Android Q image for Pixel 3A and flash it via sideload or similar.
Can you help me how to do?
Xtremeviper said:
Thanks antp121
I tried to find from official website the Android Q image for Pixel 3A and flash it via sideload or similar.
Can you help me how to do?
Click to expand...
Click to collapse
You know how to use fastboot? I believe the instructions are right on the Google factory image site where you grab the beta 3 image.
Sent from my Pixel 3a using Tapatalk
Thats the point...
I can't found it on Google Factory image, the Beta 3.
Hello,
Do you know if Android Q will brings face unlock ?
Even if it's not safe as the finger print sensor
Xtremeviper said:
Thats the point...
I can't found it on Google Factory image, the Beta 3.
Click to expand...
Click to collapse
Here you go bud. They took it down.
https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
And if you need any instructions:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-install-android-q-beta-3-june-t3930217
jmtjr278 said:
You know how to use fastboot? I believe the instructions are right on the Google factory image site where you grab the beta 3 image.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
crackedvenom2 said:
Here you go bud. They took it down.
https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
And if you need any instructions:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-install-android-q-beta-3-june-t3930217
Click to expand...
Click to collapse
Many Thanks!!! I succeed!
antp121 said:
Not via OTA, you can pick up the system image from the website and flash it manually though.
As to the OP, I gave it a shot for a couple days but I kept getting a bug where I'd unlock the phone and just get a black screen so I got frustrated and flashed back lol I hope the OTA thats supposedly coming next month fixes it up so it could be a daily driver.
Click to expand...
Click to collapse
I've actually been getting the same thing. I also keep having an issue with wifi, I think I'm going go back to pie and see if it's still doing it. I just really like the new gestures and don't wanna give them up lol
I've been running it for a few weeks. Side loaded the OTA as soon as I got the phone. They took down the OTA file but it's posted in this thread. I've had no issues other than a few apps not being comparable yet and there is no working Magisk out for Pixels 3/3a with Q beta.
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
bejunk said:
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
Click to expand...
Click to collapse
Yes
sd_N said:
Yes
Click to expand...
Click to collapse
bejunk said:
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
Click to expand...
Click to collapse
On a related note, does anyone know if opting out of the Beta will delete any esim profiles?
Axe_L_Thief said:
On a related note, does anyone know if opting out of the Beta will delete any esim profiles?
Click to expand...
Click to collapse
Simply "opting out" of the beta by pressing the button on the web page will not change anything. But as soon as you (download and) install Pie, my guess is that it will erase everything including any esim profiles. When you go from one major release to another - especially a downgrade - the phone is typically going to be wiped completely. It purposefully erases all information to ensure there isn't any conflicts between the two OS versions.
Just enrolled in the beta myself, does anyone know if it is being pushed OTA yet?
Sent from my Pixel 3a using Tapatalk
upinsmoke7610 said:
Just enrolled in the beta myself, does anyone know if it is being pushed OTA yet?
Click to expand...
Click to collapse
DP4 was pulled iirc. You can still sideload it.
Anybody having any issues with it so far?
Sent from my Pixel 3a using Tapatalk
So far I'm having no issues with the beta, but did anyone else get a small update today? Any idea why?