[Guide] How to root the Pixel 3a with or without twrp & take OTA updates once rooted
THIS IS A DRAMA FREE THREAD, I'M NOT GOING TO BASH OTHERS THREADS, NOR AM I GOING TO GO AROUND TO THOSE THREADS AND BASH THEM IN IT BECAUSE I SOMEHOW FEEL SUPERIOR TO THEM.
Standard you do this at your own risk and I'm not responsible for anything warning.
There are a few ways you can go about rooting. You can either use twrp, manually patch the stock boot image and flash it, or just flash a pre-patched boot image. I'll be going over all three, but keep in mind i have depreciated the pre-patched method now that we have twrp. twrp is dead on 10
Do these first if you haven't already:
Update your fastboot and adb
I just toss these 4 highlighted files into the windows folder, but you may have a different set up(I put them in the windows folder so I don't have to add them to PATH.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Googles USB driver if you need it
right click the start menu icon, click device manager, then locate your phone(should have a yellow symbol on it, right click it, then click update driver, then click browse my computer, click the browse button and then navigate to where you extracted the drivers, click the main folder(usb_driver) and then click ok, then click next and ok through any prompts.
CMD = Command Prompt
Unlocking your bootloader:
This wipes your phone
Run through the initial setup if you haven't already, if you haven't don't bother logging into your google account.
Enable dev options(settings>about phone>build number>tap it 7 times).
Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
While still in dev options scroll down a little and enable usb debugging.
Plug your phone into your pc.
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Open up command prompt(powershell works to but i always use command prompt) type into the cmd window
Code:
adb reboot bootloader
The phone will reboot into fastboot mode.
Now type into the cmd window
Code:
fastboot devices
See if it lists a device, if not you need to install the drivers I linked to. If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
type in
Code:
fastboot flashing unlock
You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.
Your bootloader is now unlocked and you follow one of the below root methods.
Onto the root methods:
these are for stock phones, not ones using a custom kernel
IF ON Q YOU MUST USE MAGISK 19.4+
Grab your boot.img from here
it's inside the zip that is inside the folder in the main zip you download
patching and flashing the stock boot.img:
This is the only way to root on android 10+ as twrp doesnt work
Reboot your phone.
Run through the initial setup again, this time you can log into your google account and set the phone up how you want. Re-enable dev options, enable adb, and turn off auto updates.
Grab the stock boot.img for your matching build(from the link above).
Put the boot.img on your phone, location doesn't really matter, as long as you know where you put it.
Download and install Magisk Manager.
Open up magisk manager and click install, then select the "Select and Patch a File" option, let it do its thing.
Move the patched image from your phone to your pc(magisk stores the patched image in your downloads folder).
Open up a cmd window and type in
Code:
adb reboot bootloader
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Once you are in the bootloader(fastboot) type in
Code:
fastboot getvar current-slot
This will tell you the currently active slot of your phone, remember it.
Now to flash your patched boot.img.
- If the cmd window location does not match the location of the boot.img you will have to enter that too.
- If you're on windows 10(this only works on English as far as i know) you can use my Tools Menu it will give you some handy options in your right click context menu. It makes things a lot easier as you can just right click in the location of the boot.img and open a cmd window there.
- If your cmd window is opened in the same location as the boot image you can just do(don't include the ")
Code:
fastboot flash boot_"slot "whatever the boot.img is named"
- If your cmd window was not opened in the same location as the boot image you will need to do one of these.
Code:
cd C:\Users\pbanj\Desktop\android
the cd command changes the current directory to where you tell it. then you can just do
Code:
fastboot flash boot_"slot" "whatever the boot.img is named"
- Or you can type out the location to the boot.img or just drag the boot.img file onto the cmd window. example:
Code:
fastboot flash boot_"slot" C:\Users\pbanj\Desktop\boot.img
Once that's done flashing just type in
Code:
fastboot reboot
MAKE SURE YOU GO INTO DEV OPTIONS AND TURN OFF AUTO UPDATES.
You should use the twrp method over this next one. I'll no longer be adding updated pre-patched boot images as they're completely pointless now that we have twrp.
Do NOT use this method, it's here just for history sake
Method 3 booting a prepatched boot.img and direct installing Magisk:
This gets you rooted a bit faster. thanks to @Uzephi for reminding me about this.
Grab the boot.img that matches your build number in about phone. These were made using the newest canary build of magisk at the time of adding them to the post. If I update them I'll mark them as updated. I used the canary builds for these as it's what I personally use
- PD2A.190115.029
- PD2A.190115.032 Updated to newest canary build as of May-28-2019
- PQ3B.190605.006 This is the June update Updated to the 19.4-c1602d25(19301) canary build
- PQ3B.190705.003 this is the July update
Save it somewhere and rename it if you want.
If not already in fastboot mode open up a command prompt window and type in
Code:
adb reboot bootloader
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Once you are in the bootloader(fastboot) type in
Code:
fastboot boot "whatever the boot.img is named".img
- If the cmd window location does not match the location of the boot.img you will have to enter that too.
- If you're on windows 10(this only works on English as far as i know) you can use my Tools Menu it will give you some handy options in your right click context menu. It makes things a lot easier as you can just right click in the location of the boot.img and open a cmd window there.
- If your cmd window is opened in the same location as the boot img you can just do(don't include the ")
Code:
fastboot boot "whatever the boot.img is named".img
- If your cmd window was not opened in the same location as the boot image you will need to do one of these.
Code:
cd C:\Users\pbanj\Desktop\android
the cd command changes the current directory to where you tell it. then you can just do
Code:
fastboot boot "whatever the boot.img is named".img
- Or you can type out the location to the boot.img or just drag the boot.img file onto the cmd window. example:
Code:
fastboot boot C:\Users\pbanj\Desktop\android\boot.img
Once booted run through the initial setup again(if you haven't already after unlocking the bootloader), this time you can log into your google account and set the phone up how you want.
MAKE SURE YOU GO INTO DEV OPTIONS AND TURN OFF AUTO UPDATES.
After you've run through the initial setup(if you had to) open up Magisk Manager(it will most likely say the manager needs to be installed as it is currently only a stub) and then click on the top install option, then click install in the popup that comes up, then click the direct install option.
After it finishes click reboot and you're good to go
UPDATING
There are a couple methods of updating.
Uninstall the edge sense plus mod before you update or you won't be able to root again/you'll end up in a bootloop and will have to enter safemode to disable it.
WHEN UPDATING TO ANDROID 11 DISABLE ALL MAGISK MODS AND REBOOT ONCE BEFORE UPDATING.
If you're using any custom kernel you'll have to flash the stock boot.img first before updating for the sideload method. The magisk method it might not matter but I'm not 100% sure on that. I'd think it'd be fine if you had magisk backup the stock image before you flashed the custom kernel, I don't use one so I cant be 100% sure though.
magisk has removed the ota method for pixel devices so these are the ways to update now.
My personal favorite way to update is to use the full system image as it's fastest. Disable any custom themes or modules that are known to cause bootloops when updating. Then:
grab the system image from here, unzip the folder and inside of it you will find another zip. open that up and pull the boot.img out.
Use magisk manager on your phone to patch that and then take the patched image and rename it to boot.img and put it back in the zip you pulled the stock one from.
Open the "flash-all.bat or .sh if on linux" and remove the -w from the end(this is important as it stops your device from being wiped) save the bat file.
put your phone into fastboot mode and run the flash-all script. should take about 5 min and then your phone will reboot and you are good to go.
I made a telegram group where I'll be posting the system images ready to flash. I typically make them within a few days of the update coming out. https://t.me/joinchat/EC3ivRhc2-t4y1J4REtuqg
Alternative Update method
Grab the OTA update from here.
Reboot the phone into recovery, you can just use
Code:
adb reboot recovery
Once in recovery press power and up and you should see the options.
Go down to apply update from adb(use the volume keys to change options and the power button to select).
Open a cmd window if you haven't already and type in
Code:
adb sideload "ota update file"
Location matters just like it did during the initial flashing, if you didn't open the cmd window in the same location as the update file andyou don't remember what to do, just take a look at one of the root methods as they tell you how to go about fixing that. Or just type in "adb sideload" and then drag the update file onto the cmd window.
After the ota is done select the "reboot to bootloader option".
Once in the bootloader(fastboot) just flash the pre-patched boot.img like you did before. remember the slot changes with each update so make sure you get the current slot, or if you remember what slot it was using before the update just switch input the other one. so if it was on slot a you would flash the patched image to b and vise versa.
BOOT IMAGES:
This is a google drive folder, it will have both stock and patched images. I also provide the newest Magisk manager These are zip files, you must unzip them to use them.
- https://drive.google.com/drive/folders/1wH7pvsHYznbDJ_vTsb_dWBNJBDcx2wHx?usp=sharing
Pass Safetynet
Open Magisk & go into its settings
Scroll down to the "Magisk" category and turn "Zygisk (beta)" on, & "Enforce DenyList" on.
Tap on "Configure DenyList"
Then tap the 3 dot menu and check "show system apps"
Add "google play services", google play store", "google pay", and any of your banking apps or apps that ***** about root.
Reboot
Install Universal Safetynet Fix and reboot
Install Yasnac from the Play Store
Open Yasnac and tap "run SafetyNet attestation" you should get pass on both basic and CTS.
How to use Netflix
Grab the newest apk from here.
Install the apk.
Add the apk to your Magisk DenyList.
if you need help you can ask here in the thread or in the Telegram group
pbanj said:
So I figured I would make a single thread out of the posts I've made. I made prepatched boot.img files to save everyone time.
I assume everyone here knows you need an unlocked bootloader and how to flash them.
Standard you do this at your own risk and I'm not responsible for anything warning.
Update your fastboot and adb
Googles USB driver if you need it
Grab the boot.img that matches your build number in about phone. These were made using the newest canary build of magisk at the time of this thread.
pd2a.190115.029
pd2a.190115.032
Save them somewhere and rename it if you want. then flash
To get google pay to work you may have to do some tinkering(I had to). To get it working go into magisk hide, enable show system apps then make google play services, the play store and pay look like this
Now comes the fun part.
- Plug your phone into your pc
- Grab your root app of choice that allows you to freeze apps
- Freeze google play services this will make your phone pissed and you will get a bunch of notifications, ignore them for now
- Open your favorite command line utility and do
Code:
adb shell
then
Code:
su
grant it root on your phone.
- Then while still in adb shell enter
Code:
rm -rf /data/data/com.google.android.gms
- Go into settings, then apps
- Clear the data of pay, and the play store
- Click disable on the playstore and then yes to restoring the factory version, reenable it
- Reboot your phone. It will ***** about lack of play services again, still ignore it.
- Reenable google play services
- Wait a min so it can do its thing
- Now you can add your cards to pay.
Click to expand...
Click to collapse
Dang, mine worked after I hid Google pay with magisk! That's an intensive process. I clicked hide them rebooted and added my amex without issue. Had to **** system apps to hide play store so I could download Netflix too.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:57 PM ----------
jmtjr278 said:
Dang, mine worked after I hid Google pay with magisk! That's an intensive process. I clicked hide them rebooted and added my amex without issue. Had to click system apps to hide play store so I could download Netflix too.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
Almost forgot to mention, thanks for the patched image. Saved me some time
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
Dang, mine worked after I hid Google pay with magisk! That's an intensive process. I clicked hide them rebooted and added my amex without issue. Had to **** system apps to hide play store so I could download Netflix too.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:57 PM ----------
Almost forgot to mention, thanks for the patched image. Saved me some time
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
Ya I had them hid and it wouldn't let me add my cards. so I went oh it must have triggered before I hid them. So I did the old "clear all their data" trick and it still wouldn't let me do it. I was talking in my discord server and was told about how the play services remembers. They told me to do all the stuff I posted and then run that command from twrp. Well we dont have twrp yet so I was like **** am I screwed until then. then another one was like if you freeze the play services and then try the command it might work. So I did and it worked. wasted about an hour of my time lol.
pbanj said:
Ya I had them hid and it wouldn't let me add my cards. so I went oh it must have triggered before I hid them. So I did the old "clear all their data" trick and it still wouldn't let me do it. I was talking in my discord server and was told about how the play services remembers. They told me to do all the stuff I posted and then run that command from twrp. Well we dont have twrp yet so I was like **** am I screwed until then. then another one was like if you freeze the play services and then try the command it might work. So I did and it worked. wasted about an hour of my time lol.
Click to expand...
Click to collapse
The things we do to have fun! That's what I love though, seeing a problem and figuring out the solution. Android is the best. Teaches me things every day
Sent from my Pixel 3a using Tapatalk
Does this work with US carrier Pixel 3a's? (TMobile, Version, AT&T, etc.)
lovelockdown said:
Does this work with US carrier Pixel 3a's? (TMobile, Version, AT&T, etc.)
Click to expand...
Click to collapse
If they will allow you to unlock the bootloader yes. Otherwise no
pbanj said:
If they will allow you to unlock the bootloader yes. Otherwise no
Click to expand...
Click to collapse
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
razrlover said:
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
Click to expand...
Click to collapse
man that sucks. i would just return it and buy it from google. or hell even bestbuy will give you an unlocked one and let you add it to your tmobile account.
pbanj said:
man that sucks. i would just return it and buy it from google. or hell even bestbuy will give you an unlocked one and let you add it to your tmobile account.
Click to expand...
Click to collapse
Yeah i had already downloaded your boot.imgs. thanks for doing that for everyone.
I've been on a S9 for a while so I'm used to finding work arounds for no root. I will try to make it work for a while and see.
razrlover said:
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
Click to expand...
Click to collapse
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
That's awesome!
A work around indeed! Appreciate it
havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
I will give it a try right now and report back. Thanks.
havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
still grayed out for me after factory reset with no sim
ill try it with a new phone as well
edit: also grayed out on my fresh out of the box phone as well
both from tmobile
havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
Did you actually unlock the bootloader?
Thanks
I thought that oem unlock was greyed until you inserted a sim and connected to a network. Seems like this is the way it's always been on pixels.
gtuansdiamm said:
still grayed out for me after factory reset with no sim
ill try it with a new phone as well
edit: also grayed out on my fresh out of the box phone as well
both from tmobile
Click to expand...
Click to collapse
Did you connect to wifi? It was still grelayed out for me until I connected to wifi. Then went back one menu, and returned to developer options and it wasn't grayed out anymore
---------- Post added at 03:40 PM ---------- Previous post was at 03:39 PM ----------
alphahere said:
Did you actually unlock the bootloader?
Thanks
Click to expand...
Click to collapse
Yes, I did. You need to connect to wifi first before it will allow you to enable OEM unlock.
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
Chronzy said:
I thought that oem unlock was greyed until you inserted a sim and connected to a network. Seems like this is the way it's always been on pixels.
Click to expand...
Click to collapse
Yes, it's grayed out until you connect to a network, but that network doesn't have to come from a SIM card (at least not in my case) it can come from wifi
Didn't work for me, factory reset for nothing. Now time to reinstall everything. ugh.
razrlover said:
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
Click to expand...
Click to collapse
When the device is paid off and unlocked (permanently, not a travel unlock) through the Unlock app, the OEM unlock option will no longer be grayed out. I can confirm it first hand and I'll add that this is how foreign carriers operate as well with regards to the Pixel.
The way that OEM unlocking works on *all* Pixels is through IMEI whitelisting. Factory Unlocked Pixels sold through Best Buy, Google Fi, Google Store and a few other retailers are whitelisted as being eligible for OEM unlocking. The option will be grayed out until the phone is connected to the internet so as to receive the eligibility state from Google.
Devices branded for T-Mobile are marked as ineligible, but T-Mobile (like virtually all carriers that sell the Pixel except for Verizon and NTT Docomo) updates the OEM Unlock eligibility flag at the same time they deem the device SIM unlock eligible. The device will check in with Google, receive the new eligibility state and unrestrict the OEM Unlock option.
The final bit of weirdness with the T-Mobile variant is how T-Mobile uses the Device Unlock app. Google has a custom SIM unlock solution for carriers that does not involve a carrier app or traditional unlock codes. It is similar to what the iPhone does & how OEM Unlock eligibility works - the carrier sends a request to Google for a phone associated with said carrier to be unlocked. Google processes the request, the phone checks in with Google and displays a notification stating that the SIM unlock was complete. For non Verizon/NTT Docomo carriers, that notification also means that you can now OEM Unlock.
T-Mobile doesn't use that functionality, for whatever reason, if there is even a reason. Maybe on account of Google not supporting temporary unlocks.
T-Mobile has long tied bootloader unlock eligibility to SIM unlock eligibility. You can buy a Moto whatever from T-Mobile, get denied a bootloader unlock code from Motorola's website, pay the device off and, boom, Moto changes their tune. The same is true with the OnePlus 6T and all current T-Mobile devices that have a sanctioned bootloader unlock mechanism.
Beware: My T-Mobile Pixel 3a Came With a SIM Card =(
My new-in-box T-Mobile Pixel 3a had a SIM card installed already. I booted it up, connected to wifi, and now I can't root it. =( Factory reset did not help.
darkmeridian said:
My new-in-box T-Mobile Pixel 3a had a SIM card installed already. I booted it up, connected to wifi, and now I can't root it. =( Factory reset did not help.
Click to expand...
Click to collapse
See above comment for a great explanation of why you can't unlock your TMobile carrier device.
Sent from my Pixel 3a using Tapatalk
Related
I found a very small number of posts about how to get ADB to recognize the V20, but no success. I did just install the latest platform tools.
Any suggestions?
Did you activate developer settings with USB debugging
ewingr said:
I found a very small number of posts about how to get ADB to recognize the V20, but no success. I did just install the latest platform tools.
Any suggestions?
Click to expand...
Click to collapse
i see you have decided to root it now LOL! well. first things first. go into developers options and activate debugging. mode. If there is OEM unlock option, also activate that (after all you are going to root, but be aware because it will erase all your data) Also install the proper drivers for your phone on the computer. All these are critical. after that you should be able to detect your device. But just in case, what update of ADB have you downloaded? I used one from the pixel's section on XDA which allowed me to see the prompt box and give permission to my computer to access and make changes to my device.
FijNNY said:
Did you activate developer settings with USB debugging
Click to expand...
Click to collapse
I thought sure I had turned that on, but it was off. But that was before I had done a software update to 10f. Maybe it changed back. Thanks.
jinkerz9430 said:
i see you have decided to root it now LOL! well. first things first. go into developers options and activate debugging. mode. If there is OEM unlock option, also activate that (after all you are going to root, but be aware because it will erase all your data) Also install the proper drivers for your phone on the computer. All these are critical. after that you should be able to detect your device. But just in case, what update of ADB have you downloaded? I used one from the pixel's section on XDA which allowed me to see the prompt box and give permission to my computer to access and make changes to my device.
Click to expand...
Click to collapse
Well, actually, I'm not quite ready to root. But I'll be appreciating your input when it comes time. (I forget...are you on a US996?).
Here's what I am trying to do: I am messing with apps to try to improve battery life while still not rooted. I installed Greenify again, hoping I don't have the same problem you and I discussed over in my Journey thread.
So, I just also installed Forcedoze, which typically 'requires' root. But on first run, it says that if not rooted you can give it the rights to do what it needs to do with the following command:
adb -d shell pm grant com.suyashsrijan.forcedoze android.permission.dump
Click to expand...
Click to collapse
All being on the same line.
Any idea if that's a bad idea?
[edit]
I just found that I can do a similar command for Greenify and have it do an aggressive doze. I think I'll try that. I may pop back into my Journey thread to update what's going on.
ewingr said:
I thought sure I had turned that on, but it was off. But that was before I had done a software update to 10f. Maybe it changed back. Thanks.
Well, actually, I'm not quite ready to root. But I'll be appreciating your input when it comes time. (I forget...are you on a US996?).
Here's what I am trying to do: I am messing with apps to try to improve battery life while still not rooted. I installed Greenify again, hoping I don't have the same problem you and I discussed over in my Journey thread.
So, I just also installed Forcedoze, which typically 'requires' root. But on first run, it says that if not rooted you can give it the rights to do what it needs to do with the following command:
All being on the same line.
Any idea if that's a bad idea?
Click to expand...
Click to collapse
Hmm it wouldnt hurt to try. I mean, without root priviliges there are not changes that can affect the system of the phone internally speaking. So... What adb did you download? I used the one from the pixel because my system wouldnt show me the prompt box asking me whether i want to allow my laptop to make changes to my phone.
I'm getting device unauthorized from ADB. I'm Googling now to find the problem. I am NOT getting stack overflow with it.
[fixed]
Rebooted PC and PHone. When I plugged in a pop-up came up on the phone to authorize debugging mode. That had not happened before. That got it to working.
ewingr said:
I'm getting device unauthorized from ADB. I'm Googling now to find the problem. I am NOT getting stack overflow with it.
[fixed]
Rebooted PC and PHone. When I plugged in a pop-up came up on the phone to authorize debugging mode. That had not happened before. That got it to working.
Click to expand...
Click to collapse
see? hahaha that's what you needed to find. the prompt asking you to authorize. in my case it didnt show it until i used the adb from pixel's forum since it appear that the adb shown on the rooting method's thread is missing a file which wouldnt allow to work properly so, then after i opened the adb , it did ask me for the authorization box
I bought a used Essential (love it!). It came with the bootloader unlocked, so every reboot I get the "your device software can't be checked for corruption. Please lock the bootloader."
I am not really concerned about that (should I be?), but when I try to set up Google Pay I get this:
"Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
I'm not sure that the Pay issue is because of the unlocked bootloader, but I don't need it rooted/unlocked, so I might as well re-lock to eliminate it as an issue.
There's a lot of info on the forums about *not* relocking when you have a custom rom, but I'm pure Pie.
So - is there a straightforward way to relock? I have things backed up/etc.
back to official rom, before that
First of all make sure you are pure stock
Then boot into fastboot by holding vol- and power button together.
Download android platform tools https:REMOVEME//developer.android.com/studio/releases/platform-tools?hl=th, unzip it, go into the folder, open cmd there, and type
Code:
fastboot flashing lock
And it's finished!
r_w said:
I bought a used Essential (love it!). It came with the bootloader unlocked, so every reboot I get the "your device software can't be checked for corruption. Please lock the bootloader."
I am not really concerned about that (should I be?), but when I try to set up Google Pay I get this:
"Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
I'm not sure that the Pay issue is because of the unlocked bootloader, but I don't need it rooted/unlocked, so I might as well re-lock to eliminate it as an issue.
There's a lot of info on the forums about *not* relocking when you have a custom rom, but I'm pure Pie.
So - is there a straightforward way to relock? I have things backed up/etc.
Click to expand...
Click to collapse
Look at the other threads about rooting.
You can do a couple of things to solve the issue:
Install ElementalX kernel
Install Magisk
VoidWalkerAlpha said:
First of all make sure you are pure stock
Then boot into fastboot by holding vol- and power button together.
Download android platform tools https:REMOVEME//developer.android.com/studio/releases/platform-tools?hl=th, unzip it, go into the folder, open cmd there, and type
Code:
fastboot flashing lock
And it's finished!
Click to expand...
Click to collapse
Perfect! Flashed the latest original from Essential per HapRow's comment, pulling from Essentials current build website.
Had to wait a long time to restore everything. Then the "fastboot flashing lock" erases everything, so I had to restore again.
Took a while, but was thankfully uneventful.
And now Google Pay works!
Thank!
As most of you know if you try to enroll your 3A device into the Preview Program, it will not show up and will see that Google is preventing them until June. However you can still install the official build directly from Google now which includes the May 5th, 2019 Security Patch.
Don't use the Factory image, as a lot of people are taking advantage of carrier specific promotions, most of these devices cannot yet be OEM Unlocked until they are SIM unlocked. So you will not be able to install the Factory Image unless that condition is met.
You can Sideload the OTA.
Keep in mind you will be installing Beta software on your device and doing so at your own risk.
I will be writing this guide in the perspective for someone who has never installed a custom rom or used ADB before on a PC.
Ensure your device is setup and you can access the home screen.
Swipe down from the top to access the settings menu.
Scroll down to and click "About Phone."
Scroll to "Build Number", tap on it 6 times in a row until it says developer options enabled.
Click back in the setting menu.
Click on "System"
Click the "Advanced" Dropdown.
Click "Developer Options"
Scroll down to "USB Debugging" and enable it, accept the warning.
Download the "SDK Platform Tools" from here: https://developer.android.com/studio/releases/platform-tools.html
Unzip them to a folder on your desktop.
Download the latest "Full OTA Image" from here: https://developer.android.com/preview/download-ota (3A Files were removed, I have mirrored the non-XL OTA, but I don't have the XL)
Pixel 3A: sargo-ota-qpp3.190404.015-dde326a4.zip (https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc)
Pixel 3A XL: bonito-ota-qpp3.190404.015-d4e9922f.zip (No current mirror)
Move that ZIP file into the Platform Tools folder on your desktop, do not unzip it.
Connect your Pixel to your PC via the USB A to C cable, the driver should automatically install.
A popup will appear on your pixel to grant debugging access to the connected computer, allow it.
Open the "Platform Tools" folder on your desktop, click the file explorer bar where it says "This PC>..." and type "CMD" and click enter, it will open the command prompt with access to that folder.
Enter the following command
Code:
adb reboot recovery
The phone will reboot, when it goes to a screen with the android mascot and exclamation mark hold the power button and click volume up this will access the recovery menu.
Select "Apply update from ADB." and hit the power button to choose it.
Enter this command into command prompt on the PC
Pixel 3A:
Code:
adb sideload sargo-ota-qpp3.190404.015-dde326a4.zip
Pixel 3A XL:
Code:
adb sideload bonito-ota-qpp3.190404.015-d4e9922f.zip
It will take a couple minutes, once done hit "Reboot System Now"
Congratulations, you are now on the official Android Q Beta 3 software for Pixel 3A!
Thanks for the mirror
I've been around this place for a while, but the Pixels have been a bit tricky. Just to clarify, the only prerequisite to flash is to be OEM unlocked?
I've never sideloaded like this, especially with the default bootloader/recovery.
Lastly, can we revert back if need be?
stevew84 said:
I've been around this place for a while, but the Pixels have been a bit tricky. Just to clarify, the only prerequisite to flash is to be OEM unlocked?
I've never sideloaded like this, especially with the default bootloader/recovery.
Lastly, can we revert back if need be?
Click to expand...
Click to collapse
If you want to flash the Factory Image than you need to be OEM Unlocked.
If you're not you can Sideload the OTA via the method in the main post.
I've updated the main post with a mirror for the 3A OTA: https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
Bulls729 said:
If you want to flash the Factory Image than you need to be OEM Unlocked.
If you're not you can Sideload the OTA via the method in the main post.
I've updated the main post with a mirror for the 3A OTA: https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
Click to expand...
Click to collapse
Thanks. Reverting back via same method?
crackedvenom2 said:
Latest version I see is sargo-qpp3.190404.015-factory-29c0085a.zip and I'm getting
E: footer is wrong
Update package verification took 0.1 s (result 1).
E:Signature verification failed
E:error:21
Installation aborted.
Do I have to factory reset or anything? It's been a little bit since I flashed anything but I know I followed the instructions except the version you show isn't on there. Can you make a mirror? Could it possibly be that? The version I'm finding is sargo-qpp3.190404.015-factory-29c0085a.zip
Click to expand...
Click to collapse
The file you mentioned is the factory image, which you can't use unless OEM unlocked, you need to sideload the OTA image using those steps, they were removed but heres a mirror: https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
Thank you! I thought I was out of luck, but couldn't complain because by turning in an S8 it's a free pixel.
Now it's a free pixel with Android Q
So confirmed working using the Mega linked OTA and sideload method?
stevew84 said:
So confirmed working using the Mega linked OTA and sideload method?
Click to expand...
Click to collapse
I'm sure you'd like another source, but the MEGA mirror is the exact file I downloaded from the Google Dev Page prior to it being removed. I'm just bummed I didn't grab the XL OTA zip.
Bulls729 said:
I'm sure you'd like another source, but the MEGA mirror is the exact file I downloaded from the Google Dev Page prior to it being removed. I'm just bummed I didn't grab the XL OTA zip.
Click to expand...
Click to collapse
Oh no I don't care about the source. Just curious if the file itself and the method you provided is working for everyone.
EDIT: Confirmed working.
Bulls729 said:
The file you mentioned is the factory image, which you can't use unless OEM unlocked, you need to sideload the OTA image using those steps, they were removed but heres a mirror: https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
Click to expand...
Click to collapse
Yes thank you. I had edited the post once I saw you provided mirrors
Just out of curiosity, is anyone keeping track of 'known' bugs? I think it should be an edit attached to these kinds of posts if there are any major ones only one I know of so far is listed below:
-Samsung Wearable (does not open at all or communicate with watch)
Vonsk said:
Just out of curiosity, is anyone keeping track of 'known' bugs? I think it should be an edit attached to these kinds of posts if there are any major ones only one I know of so far is listed below:
-Samsung Wearable (does not open at all or communicate with watch)
Click to expand...
Click to collapse
The Top Issues are listed here: https://developer.android.com/preview/release-notes
you can also file bug reports there as well.
Sent from my iPhone using Tapatalk
Bulls729 said:
The Top Issues are listed here: https://developer.android.com/preview/release-notes
you can also file bug reports there as well.
Click to expand...
Click to collapse
I followed that link and did not see mention of the bug I just listed, which I did indeed file. I followed up on it and it was actually reported as a duplicate since others have already reported it (which leads me to call it a known issue). The only thing I found was some vague "financial apps might not work as expected" and that's about it.
I know it's hard to ask for here, but things that are lay-user or layperson friendly are SUPER NICE. Just calling out that Samsung Wearable literally doesn't work at all right now I think is nice for people to know going into it. *shrug*
It is still possible to find the original images for both 3a devices on the "Downloads for Pixel" page on the android developer website, the forum won't let me post the link.
ClawMacaw said:
It is still possible to find the original images for both 3a devices on the "Downloads for Pixel" page on the android developer website, the forum won't let me post the link.
Click to expand...
Click to collapse
Yes the Factory images are and have still been up, but these are only useful to those who have a device that is OEM Unlocked. A good amount of people took advantage of the T-Mobile $400 credit trade in. And those devices are not able to be OEM Unlocked until they get a SIM unlock, while silly they tied the SIM Unlock status to the OEM Unlock ability. So for those with OEM Locked phones they can only use the side-load procedure wit an OTA zip which have been removed.
Sent from my iPhone using Tapatalk
Bulls729 said:
Yes the Factory images are and have still been up, but these are only useful to those who have a device that is OEM Unlocked. A good amount of people took advantage of the T-Mobile $400 credit trade in. And those devices are not able to be OEM Unlocked until they get a SIM unlock, while silly they tied the SIM Unlock status to the OEM Unlock ability. So for those with OEM Locked phones they can only use the side-load procedure wit an OTA zip which have been removed.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see. How embarrassing, I didn't realize there was a difference between the OTA and the factory images.
CAExempt said:
How would I go about reverting back to Pie? I've downloaded the correct image file for Pie on the Pixel 3a (non XL)
Click to expand...
Click to collapse
If you have a device that is able to be OEM Unlocked you can restore using the Factory Image. If not you can go to this reddit link which shows information to context Pixel Support to revert your device.
https://reddit.com/r/android_beta/comments/bpjxhb/pixel_3axl_and_android_beta/
Bulls729 said:
Yes the Factory images are and have still been up, but these are only useful to those who have a device that is OEM Unlocked. A good amount of people took advantage of the T-Mobile $400 credit trade in. And those devices are not able to be OEM Unlocked until they get a SIM unlock, while silly they tied the SIM Unlock status to the OEM Unlock ability. So for those with OEM Locked phones they can only use the side-load procedure wit an OTA zip which have been removed.
Click to expand...
Click to collapse
The other problem is that when you unlock bootloader, you don't pass safetynet (so apps like Google pay, boxer, many banking apps, etc won't work at all). You could unlock bootloader, flash Q beta 3 image, then relock bootloader, but unlocking it wipes your phone so you'd need to set up from scratch. Wait for the beta ota and you won't have to wipe to use Q
OTA sideload won't erase data, correct?
I've used the search function and found nothing for this phone. I've used Google and found nothing about rooting this exact model.
I'm looking for the technique to root this phone and I'm finding nothing. Has anybody rooted and flashed a Custom ROM/custom recovery on this device and how did you do it?
I just got this phone as well, and I have been looking and also have found nothing for this exact variant. I have tried the usual one-click methods to no avail. Is there any development in the works? If you need a test dummy, let me know. I have several other phones to use as spares, so I am not afraid of a soft brick.
Rooting ZTE Blade a7 Prime
I too can be a test dummy to root this phone. Since Visible is such a hands off company you really need your phone to be rooted to do things for yourself. Currently for some reason my ZTE BLADE A7 Prime can’t send or receive calls and their techs are telling me 3 to 5 business days... counting yesterday and today that’s a week! Ridiculous! The APN settings look off compared to my wife’s phone but you can’t edit the settings.
ZTE Blade prime A7 Visible
I've been having the exact same problem with making and receiving calls also with losing service(for the service prob. Found great n easy solution- till find permanent one-**go to airplane mode in settings turn it on for 30secs to a minute then turn airplane mode back off TAKES SIGNAL FROM 0-4 BARS EVERYTIME AND I CAN GET/MAKE CALLS INSTANTLY ETC AGAIN ?)
Data saver seems to work for resetting connection as well. I too would be interested in rooting. I kinda like the phone, but it does have its issues.
First glance at unlocking bootloader
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.
Has anybody tried this?
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
I don't own this phone (yet), so I can't give it a shot myself.
I'm not very familiar with mediatek processors in general, but that looks rather promising with some restrictions... If I have time over the weekend, I'll give that a whirl and report back whether it works or bricks my device
seems lke ts gonna be a long process before were able to fiddle with roms but im atleast glad this is close to stock android.
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
Ditto here too. Couldn't get it working at first. Turned out I miss read the instructions and put all files in the init.d folder instead od the two files in the bin folder. Then your tip on using the 32bit binary got it working. Thanks.
Anybody figured out a way to change build.prop to make it stick after reboot? I am trying to enable APN editing by modifying /system/build.prop, but whenever I reboot I lose the changes.
/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.
wunderdrug said:
/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.
Click to expand...
Click to collapse
Looks like we can not add an APN even with root then? It's a bummer.
sasuke33 said:
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.
Click to expand...
Click to collapse
They removed the fastboot command to unlock the bootloader. I found it out by comparing the similar ZTE Blade 10 and Blade 10 Prime. The Blade 10 non-prime has the unlock command and it works whereas the prime version has the command removed but funnily enough the lock command is still there but is useless. I then looked at the bootloader for the a7 prime and same thing the unlock command is removed from the bootloader. So there isn't much hope for it unless a bypass can be found.
virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
+1 to another confirmation that the above works. Root is available, but there are limitations. I cannot install many of the modules from magisk, but this is still a great start. Thanks for the links :good:
I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.
I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?
ultrasoul said:
I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?
Click to expand...
Click to collapse
I was also able to add and APN by just clicking on the "+" icon on the top-right corner of the APN configuration screen. When I inserted by MINT SIM Card (T-Mobile MVNO) there were not default populated APNs, but was able to get everything to work after adding an APN -- even after rebooting.
Big Tip: After entering the APN data and before leaving the data entry screen, make sure that you save the APN or it will not be persisted. Click on the "three dots" menu on the top-right corner and hit the Save menu item.
---------- Post added at 05:49 AM ---------- Previous post was at 05:39 AM ----------
AmazerG said:
I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.
Click to expand...
Click to collapse
After studying the process a bit, I've come to conclude that this isn't really permanent root. All this does is the equivalent of running a script to gain temporary root after after reboot. This is done very late in the boot process, if you can even call it a part of the boot process since it's really just a user-space application auto-starting.
The modules are probably trying to be instantiated well before the root is made available through the pseudo "init.d" scripts.
It's still nice to have root access using this technique, but its usability is pretty limited. For example, I can't even get AFWall+ to start up, even if I configure it with a startup delay (hoping that it kicks in after temporary root).
So what are the odds we can make this a permanent root using a firehose file and QPST/QFIL? Similar to the Visible R2 phone?
Got a question that I am not sure has a proper answer (and yes I know this is a sus question to begin with).
I have an old s7 and I forgot the pattern to unlock it. Developer mode is enabled but since I can't get through the lock screen I can't whitelist my PC on the phone when I connect it. I need to access my google authenticator app because I want to export it to my new phone (use to have it on my new phone but for other reasons it got wiped). I've tried using the samsung service mode code to put it into service mode from the emergency call dialer but that doesn't work. Is there anything else I might be able to try?
use droidkit or drfone screen unlock? I think dr.fone has a free trial, maybe you can screen unlock with it. Or just look for any other 3rd party free screen unlocker. They usually don't need root, nor adb.
Ive tried both but both don't support the s7. At this point I would pay for one of these apps to get into this damned thing.
Is it's bootloader unlocked?
Yes you may try with - UFED4PC_7.49.0.2.tar
This is supported to remove or read screenshot without lock data For Android & specially working on many SAMSUNG devices
AzimBahar said:
Yes you may try with - UFED4PC_7.49.0.2.tar
This is supported to remove or read screenshot without lock data For Android & specially working on many SAMSUNG devices
Click to expand...
Click to collapse
Is that something you can flash via odin or?
Did some research, looks like a full mobile forensic device suite. I don't have 2000 dollars to drop on trying to open a phone.
NO.
This is a tool which can read your phone lock
I wonder if there is a way to use Odin to flash TWRP for a single boot. It might be enough to push the ADB keyfile to the directory or to delete the sqlite keys for the pattern.
AzimBahar said:
NO.
This is a tool which can cellebrite your phone lock
Click to expand...
Click to collapse
That doesn't mean anything Cellebrite is the name of the company that produces UFED.
metalblaster said:
I wonder if there is a way to use Odin to flash TWRP for a single boot. It might be enough to push the ADB keyfile to the directory or to delete the sqlite keys for the pattern.
Click to expand...
Click to collapse
you use fastboot to boot a twrp image on a device, without actually flashing it, but im not entirely sure if you can do it with a locked bootloader. Google it i guess?
PhotonIce said:
you use fastboot to boot a twrp image on a device, without actually flashing it, but im not entirely sure if you can do it with a locked bootloader. Google it i guess?
Click to expand...
Click to collapse
I wonder if I could mount the system partition that way or not bootloader aside. Unlocking the bootloader would kill all the data too which is a no-no.
It does seem possible to flash TWRP on some devices without unlocking the bootloader. How would I go about booting from it with fastboot without flashing it if I tried it? edit: nevermind I know how to do it.
I assume I would have to use the herolte img to try to get it to work since there isn't one specifically for the sprint variant.
Well I tried but I can't seem to read the phone with fastboot. I tried Odin and it predictably threw out the flash because it wasn't properly authenticated either.
Did you install the correct drivers? You need the samsung usb drivers for odin, and some adb and fastboot drivers for adb.
PhotonIce said:
Did you install the correct drivers? You need the samsung usb drivers for odin, and some adb and fastboot drivers for adb.
Click to expand...
Click to collapse
Yeah, of course. I have the Samsung drivers and I tried working with linux and had the same issue. Feels like my only recourse at this point is to setup a kali nethunter.
You also need to manually install adb and fastboot drivers for your device, which for me is pain, but maybe it'll be easy for you.
PhotonIce said:
You also need to manually install adb and fastboot drivers for your device, which for me is pain, but maybe it'll be easy for you.
Click to expand...
Click to collapse
Yeah I have them both. For some reason though Fastboot just doesn't see the device. I tried pinging it with the linux version and its vendor id but it didn't do any good. Kind of a real pain this is becoming. I may just convert my old nexus 11 into a kali nethunter and try to brute force it.
Still haven't found a solution and now I am feeling the consequences. My Nintendo 2FA is on this damned phone. Going to try to call support and get it removed tomorrow but its a real big pain.
Metablaster,
Is there an update to this?
My wife's S8 is pattern locked, she didn't set up a Samsung account prior, and the Google Find my Phone web tool PIN option has been changed/ deleted. Maybe there's an older html version of this somewhere?
ADB keeps coming back that the device access is "unauthorized" even after reboot, so although I thought I enabled USB Debugging before giving her the phone (it used to be mine), she may have restored to factory without enabling it again.
Kali will delete all of the data like a factory reset so that defeats the purpose except to just get use of the phone at all again.
Is there anyone on here that knows of a professional grade service that can do this?
So frustrating...! Why , upon proof of ownership, can't something be done?
Please pm me, I'd want to try the MD-Next option first.
If I run the risk of losing her data than anything more intrusive probably isn't worth it.
mat68046 said:
Please pm me, I'd want to try the MD-Next option first.
If I run the risk of losing her data than anything more intrusive probably isn't worth it.
Click to expand...
Click to collapse
MetalBlaster,
I did manage to get the S8 to boot into Recovery Mode, please PM me about trying the MD-Next step via USB bridge.
mat68046 said:
MetalBlaster,
I did manage to get the S8 to boot into Recovery Mode, please PM me about trying the MD-Next step via USB bridge.
Click to expand...
Click to collapse
Have you already tried to unlock the device with a locked SIM?