Uninstalling Android R Preview - Google Pixel 3a XL Questions & Answers

Hello everyone. I installed the developer preview for Android R and i'm over it. I wanna go back to stock and I tried sideloading the OTA image and I get this message
update package is older than the current build. Downgrade not allowed.
My bootloader is locked so I can't flash the image through fastboot. I need help.

May update released might want to try that one.

hedgehogmd said:
May update released might want to try that one.
Click to expand...
Click to collapse
I tried but it didn't work.
I was on the phone with t-mobile to see if they could unlock my phone but we're having issues with the unlock app.
I miss the days of typing in a code and getting your phone unlocked.

As you have just learned, the developer previews are not the same as beta releases. With the beta releases, you can "quit" the beta program and have the old OS version reinstalled via an OTA update The preview releases have no such OTA reset ability. Therefore, you should not participate in the preview releases unless your phone is unlocked.
If the May release doesn't let you revert back, then I think the only option you will have is to wait until the beta is released. Join the beta and have it installed on your phone and then quit the beat and hope that the OTA update takes you back to stock Android 10. In theory I think it will.

you should use the flashall.bat script if you're installing the factory image. Though this will earase data. Just make sure you have USB debugging on
EDIT: I think you should still be able to unlock your bootloader
EDIT2: After reading a bit more I see that on carrier specific devices, OEM unlocking is greyed out until the phone is sim unlocked. But after you get the app working everything should work fine. Did you use another sim thats not from T Mobile?

RicardoSal24 said:
you should use the flashall.bat script if you're installing the factory image. Though this will earase data. Just make sure you have USB debugging on
EDIT: I think you should still be able to unlock your bootloader
EDIT2: After reading a bit more I see that on carrier specific devices, OEM unlocking is greyed out until the phone is sim unlocked. But after you get the app working everything should work fine. Did you use another sim thats not from T Mobile?
Click to expand...
Click to collapse
I put a different sim on the phone and it worked but it's b/c I did the temporary unlock. After 30 days the phone will be locked again. The phone won't let me unlock the bootloader unless it's a permanent unlock. The problem is I'll have to wait 30 days for the phone to re-lock. I wish t-mobile could just give me a code...
Lucky for me this phone isn't my daily driver but I wanted to revert to stock android b/c I got an invite to test out the Ratio launcher by Blloc. It's incompatible with Android R.

chivamex10 said:
I put a different sim on the phone and it worked but it's b/c I did the temporary unlock. After 30 days the phone will be locked again. The phone won't let me unlock the bootloader unless it's a permanent unlock. The problem is I'll have to wait 30 days for the phone to re-lock. I wish t-mobile could just give me a code...
Lucky for me this phone isn't my daily driver but I wanted to revert to stock android b/c I got an invite to test out the Ratio launcher by Blloc. It's incompatible with Android R.
Click to expand...
Click to collapse
Your best bet would be to just wait until you can permanently unlock it. I got mine from best buy and only recently did I bother with flashing roms on it.

I have a TMO device and had a temp unlock, and obviously it doesn't allow oem unlocking to be enabled. I DM'd TMOhelp on twitter and was able to get a permanent unlock there. They told me that I'd have to wait for my temp unlock to expire before I could perm unlock, but I didn't. If you have trouble with the app, just clear the storage and cache data for it. Once it is actually perm unlocked you'll immediately get a notification and be prompted to restart the phone. After that you should see oem unlocking enabled in dev options and be able to hit bootloader and unlock it.

Related

[Q] R800a can not OTA update or enter fastboot, root problems? mode.

I recently purchased a R800 from someone on Craigslist. The phone is already rooted, permanantly I think since it is rooted after doing a factory restore. It is not sim locked, I believe its factory unlocked.
I tried to do the OTA update, which downloads, but fails to install. It appears to get about 3/4 of the way done, reboots and gives me an "update failed" message.
I wanted to unlock the boot loader, I got the unlock key from SE. I must of tried 10 times to get the phone to boot into fastboot mode, it NEVER does it. It simply boots up normally. I even got an app that makes it easy to reboot into restore or fastboot modes (just click an option and it reboots), however just like before the phone simply reboots normally. I even did a factory restore prior to trying the update... no go.
Should I try to remove the root access? Is this what is giving me all the problems. I was able to successfully install root explorer and titanium backup and both of those programs worked fine.
R800i, Android 2.3.3, Kernel 2.6.32.9-perf [email protected] #1, Build number 3.0.1.A.0.145
Edit: Title should be "Can not OTA or enter fastboot mode, root problems?"
Is your phone sim locked? Sim locked phones need to be unlocked before able to unlock bootloader or fast load. After you unlock bootloader make sure you never ota update.
Sent from my XPlay using XDA App.
Your phone has a locked bootloader and a factory lockout on fastboot.
Best advice to you is flash the r800a world generic 2.3.2 root it with gingerbreak then ota update. Use a program called wontanserver as its super easy.
Dont get anyone to remove your factory locks on fastboot until you read tons of threads on these fourms from the last couple months.
Ok, lets see....
Deoxlar said:
"Is your phone sim locked? Sim locked phones need to be unlocked before able to unlock bootloader or fast load. After you unlock bootloader make sure you never ota update."
Click to expand...
Click to collapse
My phone is the R800a. It was my understanding that this phone was never locked (factory unlocked). It came in an official Sony Ericsson box and has no carrier branding on it what-so-ever. It was not purchased through a carrier. It does have a weird stock data APN called "Telekila"?!?!?
sdlaurin said:
"Your phone has a locked bootloader and a factory lockout on fastboot.
Best advice to you is flash the r800a world generic 2.3.2 root it with gingerbreak then ota update. Use a program called wontanserver as its super easy.
Dont get anyone to remove your factory locks on fastboot until you read tons of threads on these fourms from the last couple months."
Click to expand...
Click to collapse
Doesn't wontonserver require credits to run? How expensive does this get?
I didn't know the phone could have a factory lock on the bootloader. I did go to the SE website where you get the unlock key and it was successful in giving me a key... Well I shouldn't exactly say "successful", it did give me a key code to use if and when I can unlock the bootloader, weather or not that code is actually legit remains to be seen. I'm a bit skeptical now since you said the phone is bootloader locked from the factory. I though SE was allowing their phones to be unlocked. I recently unlocked my Motorola Atrix and was expecting to do the same with this phone.
Thank you guys for the advice. I love this phone so far but I can't wait to get a custom rom on it
It uses credits but they are free.
There are currently 2 gentlemen on these forums that can remove your fastboot locks and unlock your bootloader.
Have a look for thier threads on this matter
I would like to have this done now, so gentlemen, whomever is able to do this please message me and we can work something out. Im dieing to get a new rom on this awesome phone/game console.
Sent from my R800i using xda premium
If you need help with unlocking your phone contact Alejandrissimo he does Unlocks
I flashed the r800a world generic 2.3.2 rooted it with gingerbreak then ota updated.I get the same thing as DMpire , reboots and gives me an "update failed" message.
Is this because I removed some of the stock apps that came on the phone after it was rooted? Anyone know about this?
Does it matter if the SD card is mounted or not?
Removing stock apps then trying to ota isnt going to happen. Reflash, root, ota, then remove your stock apps
Is there any easy way to do this? can I reflash it as it has a locked bootloader, or do I have to get the bootloader unlocked?
JDMpire said:
I would like to have this done now, so gentlemen, whomever is able to do this please message me and we can work something out. Im dieing to get a new rom on this awesome phone/game console.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Christian6809 said:
Is there any easy way to do this? can I reflash it as it has a locked bootloader, or do I have to get the bootloader unlocked?
Click to expand...
Click to collapse
Add me to gtalk pals: alejandrissimo[at]gmail.com
Google wontanserver its free

14 day wait for bootloader unlock?

Is this possible to skip? Can we unlock with adb / fastboot or is that not going to work / likely to brick the device?
Unlock Resposibly
adb or fastboot unlock will only work after 14 days of waiting. It is to allow you to rethink your decision. OEM unlock will obviously void your warranty and applications like Android pay will stop working. Trust me, relocking will not be easy as unlocking. Even if you somehow get it relocked, Android pay will still not work for you. So, unlock responsibly.
Thanks for the reply . I'm really doing it for root access, modifying the hosts file, changing fonts and boot animation, but the latter two aren't necessities.
I don't use Android pay (don't use contactless) but I am a little concerned that online banking will cease to function when the phone is on a stock firmware and rooted. If there's an effective system wide ad blocker I may use that instead.
For hosts file, I recommend dns66, available through fdroid, no root required.
i have found that many banking apps will continue to work with root provided you also have a hide root app installed but android pay is a no go.
jk77 said:
For hosts file, I recommend dns66, available through fdroid, no root required.
Click to expand...
Click to collapse
Thanks! First I've heard of fdroid, looks very useful, and dns66 does exactly what I was planning on doing.
Need to put Android 10 so only way is custom ROM. How to put custom rom without OEM unlock?
cutom rom
Albert612103 said:
Need to put Android 10 so only way is custom ROM. How to put custom rom without OEM unlock?
Click to expand...
Click to collapse
there is no way. Should be rooted
CHEERS
Hello guys.
For those having bootloader unlock server issue (normally everybody), there's a post on the Lenovo forum that gives the origin of the issue:
https://forums.lenovo.com/t5/P2-P2a...-bootloader/m-p/4574568/highlight/true#M12457
In fact, the problem seems coming from an non renewed SSL Certificate in the Lenevo server tracking the OEM Unlocking requests.
The suggestion given by fls2 is to change the date of the P2 phone to a previous date than the 10 July 2019 and the Bootloader Unlocking process should be launched.
That's what I've done with a second P2 I bought that has its bootloader locked.
I set the date to 10th of April 2019 and the phone is now waiting for 14 complete days to engage the OEM Bootloader unlock instead of the usual Lenovo ID error pop-up.
I'll wait for the process to end and see if everything went fine, but it seems that it should be OK as it was with my first P2 phone.
I'll keep you informed if there are some trouble in the process but I stay confident.
In case of success, we should address a very big "thank you" to fls2 for pointing out the issue with Lenovo server.
20 days have passed since registered. Always shows error.
Unable to unlock OEM.
Don't know what to do...
Hello everyone,
As I have written in my last post, I've used the suggested method of manually changing the date to one before the 10th July 2019.
So, as I've said, the 14 days counter has been correctly launched and I was able to see the counter evolving from 14 to 2 days.
Then I was a little bit busy and I haven't followed my P2 phone until last week-end.
When I tried to consult the status of the bootloader unlocking request, I had the same annoying pop-up telling me there's a problem with my account.
The date was fixed to 10th of April 2019 manually, but still had connection error pop-up.
I then tried to switch to current day date of the week-end (29/02/2020), and tried to check again the bootloader unlock status: Annoying pop-up again.
Before giving up, I've tried putting another date manually but at least 14 days after the one I've put when I made my first request and still before the 10th of July 2019, so I switched to 10th of June 2019.
This time, when I checked the bootloader unlock request, I've got no error and had a positive bootloader unlock message that told me the phone is going to reboot and erase all user data that are present.
The phone has rebooted in Fastboot mode and I was able to send the awaited "fastboot oem unlock" command from my laptop.
I didn't try to reboot the system and see if the fastboot command will work if I go in fastboot mode by myself, because I didn't want to miss the opportunity to succeed in unlocking the bootloader of this phone.
I let the people brave enough to try if they feel comfortable with that.
Now this phone is working with an AICP Android Q ROM that seems very stable.
@ Albert612103
20 days have passed since registered. Always shows error.
Unable to unlock OEM.
Don't know what to do...
Click to expand...
Click to collapse
Try to follow my steps.
There's no reason I've succeded and you cannot.
I'm sure you'll be able to unlock your bootloader as I've done.
If you have some question, just feel free to ask.
I'm trying to unlock the bootloader too. Is there any way to avoi waiting 15 days? I'm still using the Stock Rom by default (Android 6).
According to the last comment in the Lenovo forum, the changing date no longer works.
Thanks
xavicosco said:
I'm trying to unlock the bootloader too. Is there any way to avoi waiting 15 days? I'm still using the Stock Rom by default (Android 6).
According to the last comment in the Lenovo forum, the changing date no longer works.
Thanks
Click to expand...
Click to collapse
AFAIK, no. You need to wait that. Also there is bigger problem than that which its the unlocking bootloader (server problem). Just you can read above, for no reason you cannot unlock bootloader.
mahmutpekkara said:
AFAIK, no. You need to wait that. Also there is bigger problem than that which its the unlocking bootloader (server problem). Just you can read above, for no reason you cannot unlock bootloader.
Click to expand...
Click to collapse
@mahmutpekkara somehow I managed to unlock the OEM. It took me few attempts tho, so I'm guessing their servers are not always operating. No needed to change the date in my case.
Only 3 days remaining, so hopefully everything goes well.
So, after 15 days waiting I was getting the message ''Server sync data success'. I managed to get thru by signing off and signing in again with another account. Flashed properly and enjoying Syberia OS

Android 8.1 with unlocked bootloader, update to Pie? What can I expect

I did some searching and I see the threads for unlocking and rooting 8.1 and 9 but couldn't find much reference to updating from 8.1 to 9 when I am already unlocked and rooted.
So if I accept the update Verizon is pushing down, is this going to basically lock the bootloader and unroot me back to stock essentially?
I just don't want to brick my phone because I am not comprehending some details I am reading in all these threads.
Just decided to go for it and see what happens..
after taking the OTA it restarted and bootloader still unlocked..
Android launched fine
had to reactivate Developer Options
OEM Unlock grayed out but says "Bootloader already unlocked" so that's good
Thanks for posting this. I'm assuming from your post that you're using the Verzon branded model?
I'm using the unlocked version on Verizon, and there's no way in hell I would take an OTA update. However, I'm about to update to 9 via image.
MuGGzyx said:
Just decided to go for it and see what happens..
after taking the OTA it restarted and bootloader still unlocked..
Android launched fine
had to reactivate Developer Options
OEM Unlock grayed out but says "Bootloader already unlocked" so that's good
Click to expand...
Click to collapse
Yes you'll be fine on Android P it give Verizon Pixel the option to unlock the boot loader
absolvi said:
I'm using the unlocked version on Verizon, and there's no way in hell I would take an OTA update. However, I'm about to update to 9 via image.
Click to expand...
Click to collapse
I'm back with an update. I used the Google notification on my rooted phone (Magisk/TW) to begin the installation. The update went okay, but custom recovery and Magisk root were wiped out. I was still able to use OEM Unlock to unlock the bootloader. The downside is, if I install custom recovery again I will lose access to my encrypted storage, meaning I'll have to reset my phone.
If your going to update, backup everything you can first; you'll need to reset.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
My advice has always been to never OTA update between Android versions, always better to fastboot flash a fresh image with a complete wipe of the system.

How to Lock Bootloader

Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Do you have a computer? If so what OS do you use?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I do have a computer, a Windows 10 Pro
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
sliding_billy said:
Are you planning on rooting? If so, you can use Magisk Hide (after using Magisk to root of course) to get Google Pay to work. I would be hesitant to re-lock the BL unless you are certain that it is completely stock otherwise. Re-locking a modified phone can brick the device. Better to just learn how to root, etc and keep it unlocked. You have come to the right place to learn.
Click to expand...
Click to collapse
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
eec007 said:
No, I don't plan on rooting. But I am afraid of bricking the phone since I don't know what has been done to it. Is there a way to determine what was done to unlock the bootloader? Otherwise I will follow your recommendation of using Magisk Hide. I would prefer to keep the phone stock. Thanks.
Click to expand...
Click to collapse
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
coolhandz said:
If you live in Denver I'll trade you my Verizon one for yours. It has a locked bootloader.
Click to expand...
Click to collapse
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
sliding_billy said:
The two obvious things you can check are that you have stock recovery and that the phone is not rooted. Manually power on to bootloader (hold volume down and press power then use the volume keys to select recovery and press power. you should get a no command android screen if in stock recovery. assuming you don't have a Magisk icon, you are probably not rooted but you can confirm by installing and running a root app like root checker. likely, the previous owner did nothing but unlock the BL given how recently it came out, but if someone where really creative they could have done work in the other partition. there are no exploites, so doing it normally (running fastboot flashing unlock from a prompt) is pretty much all that would have been done other than enabling developer options and OEM unlocking in settings.
Personally, I think you have a good chance to learn your device, root (you need to be rooted for Magisk hide) and keep the bootloader unlocked. Besides rooting, being able to install a full factory image instead of an OTA is so much better in my opinion. The amount of work it would take to be 100% confident that the only thing done was the BL unlock would take as much work as at least getting a working knowledge of rooting and reinstalling the OS.
P.S. Keeping a phone "stock and rooted" has advantages. That is how I run my 3 XL and how I ran my OG XL. No custom OS. Not even a kernel.
Click to expand...
Click to collapse
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
sliding_billy said:
Hope it all works out for you. I assume you did a factory reset on the device since you got it used. Re-locking will do another factory reset.
Click to expand...
Click to collapse
Yeah, so I locked using "fastboot flashing lock" but then it doesn't start, saying that there is no operating system or something like that. I freaked out and was able to unlock again using "fastboot flashing unlock". Now all is wiped. I guess I need to flash the oem rom first, then lock. I'll have to do this all later tonight. Just glad that I didn't brick it yet.
eec007 said:
Thank you! Root Checker says that "root access is not properly installed on this device". The recovery mode screen just has a warning about the bootloader is unlocked and a link to a google help page. I figure that I can always unlock the bootloader again if I need to later, but for now I just want everything to work (bank and pay app) and not worry about updating anything myself. I think I may try fastboot to lock the bootloader for now. Thanks for all the help.
Click to expand...
Click to collapse
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
bobby janow said:
I haven't rooted or bl unlocked in some time now so if I make a mistake someone please correct me. After buying it from a 3rd party I'd wipe the device entirely. Download the correct image and install the latest platform tools for Windows (here) https://developer.android.com/studio/releases/platform-tools and make sure you can connect with adb devices and fastboot devices commands. Then extract the latest full image from here https://developers.google.com/android/images to your platform-tools directory and run the flashall.bat command if you wish to wipe the entire device and get rid of anything the previous owner might have "inadvertently" installed. (this is what I would do but not necessarily what you should do if you want to keep the current apps and system intact) This will reset your device and then you can lock the bootloader with no worry and you'll have a stock system.
I agree that since you can unlock it at any time and you don't need it now then relock it. But there are those here that disagree with me and fight with Magisk and OTAs constantly. But they are not noobs and know what they're doing. If you want to learn there is a wealth of information here so it's your call. Just my 2 cents. But please check my steps before you do anything that might cause issues.
edit: darn, sorry I just saw above that you already tried to lock it. I hope what I said to do will get you out of the predicament.
Click to expand...
Click to collapse
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
eec007 said:
Your steps are basically what I will try tonight. Currently the phone is working again, so there was no harm done yet (just the restore of all apps and such). But I'm going to flash the oem image tonight and start all over again.
Click to expand...
Click to collapse
One thing I would do before I relocked the bl would be to do the full login procedure, email everything other than apps. Then make sure you're on the Nov update in about phone, I'm sure you will be, and then fastboot relock the bl with the proper command. It will wipe the device again but it's a small price to pay for about 10 minutes of work. Then once it reboots and there is no more error message you'll be fully stock. Enable dev options again and make sure the oem switch is active allowing bl unlock. Then you're done. I've gotten to the point on my 5X where I even flip the oem switch so it can't be bl unlocked until I go in and flip it back. Dangerous if you're flashing stuff but not so much if you're just taking OTAs. That's of course your call entirely. Good luck.
eec007 said:
lol, what I don't get is that I thought the google edition could have the bootloader unlocked in the developer options. So why go to this hassle of unlocking the bootloader from fastboot? FYI, in the Developer options the OEM unlocking is greyed out and says "Bootloader is already unlocked".
Click to expand...
Click to collapse
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
eec007 said:
Hello, I purchased a Pixel 3 XL off craigslist and it is working fine, but the bootloader is unlocked therefore I am receiving a warning when restarting the phone and Google Pay does not work. How can I re-lock the bootloader? Do I need to flash the latest standard google image? The build number is: "crosshatch-userdebug 9 PQ1A.181105.013 5027108 dev-keys". When in bootloader the bootloader version is: b1c1-0.1-5004167. Obviously a n00b here, please be gentle. Thank you for any help.
Click to expand...
Click to collapse
They're right to mention that relocking a modified device can result in a brick.
Your best bet is to go to https://developers.google.com/android/images#taimen
Follow the directions to the "T", then relock it if you are really really sure that the unlock screen bothers you.
Would suggest to do this anyway, no matter future unlock status.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
I agree with most of your post other than waiting for the next OTA before you lock the bootloader. Why would he need to do that? If he's stock, and he'll see that immediately, then relock it. He doesn't want root or Magisk but only wants banking and Pay. With the slider allowing bl unlock he's in no danger whatsoever. Lock and relock whenever he wants. OTA will not disallow the slider once it's set.
TonikJDK said:
That will stay grayed out until you relock the bootloader. That slider "allows" unlocking. Then you boot into fastboot and unlock it.
So you would reverse the process, hit fastboot and relock the bootloader. Then you can toggle the slider back to not allow unlocking.
Relocking the bootloader will wipe your phone.
You should not do this until you first flash the full factory image to make sure the phone is 100 percent stock. And if it were my phone I would wait for the next OTA update after flashing it back to stock to make sure it goes ok. Then lock it.
And then I would wait awhile before hitting the slider.
You are playing with fire here, if you mess it up and lock it and hit the slider you will not be able to fix it. And no offense, but since you have not done this all before on this phone chances are good you will mess it up.
So, flash to stock and leave it unlocked.
Then wait for the next OTA.
Then lock it.
Then wait a bit more before you hit the slider.
And remember, since you are not the original buyer you will not be able to warranty it.
Click to expand...
Click to collapse
Thank you for explaining this. I had thought that the Developer Option slider was to unlock the bootloader, but your explanation clarifies it, the slider is to allow the bootloader to be unlocked...
Ok, so I tried to flash the factory image using adb flash-all and it keeps getting the error:
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file)
Now the phone is not working at all and says that "device is corrupt" and will not boot past the white google screen. I can try again using adb, but it is the same error each time. I tried to download the image again and same sparse error. I can also fastboot in TWRP, but not sure what to do in there. What am I doing wrong? I guess I should've rooted and used Magisk like others have said.
turns out changing to a different cable resolved my sparse error and I was then successfully able to apply the factory image and lock the device. Thanks everyone for the help.

Downgrade back to Pie

I am on the official Android 10 firmware and would like to downgrade back to Pie. Is this possible without unlocking the bootloader? The T-Mobile unlock app apparently don't work on 10 yet so I need to get back to Pie to unlock then I can go back to 10.
Yes, I think you can. You can sideload an OTA image without unlocking the bootloader. Even though it says OTA, it is a full factory image. The files and directions are both available at that link. If possible, I would certainly do a full factory reset of your phone as soon as it booted however. You never want to back into an older version of Android without doing a full factory reset.
sic0048 said:
Yes, I think you can. You can sideload an OTA image without unlocking the bootloader. Even though it says OTA, it is a full factory image. The files and directions are both available at that link. If possible, I would certainly do a full factory reset of your phone as soon as it booted however. You never want to back into an older version of Android without doing a full factory reset.
Click to expand...
Click to collapse
Ok, I just tried that and part way through installation it aborted. "E:Failed to verify package compatibility" along with some other errors...
To revert to pie you have to use the full image and the platform tools available over at Goog but for this you need to unlock the bootloader. If you want to stay on a locked bootloader you then lock it after you're up on stock pie again. Keep in mind you'll want to do the works before you move any data back to the phone and that unlocking the bootloader will wipe the phone so you'll need to back up everything before you unlock.There are specific instructions for all of that and the images and tools at https://developers.google.com/android/images
Don't be afraid of unlocking the bootloader, it can be unlocked and locked again at your whim over and over. Doesn't hurt anything other than you get a wipe in the process.
krabman said:
To revert to pie you have to use the full image and the platform tools available over at Goog but for this you need to unlock the bootloader. If you want to stay on a locked bootloader you then lock it after you're up on stock pie again. Keep in mind you'll want to do the works before you move any data back to the phone and that unlocking the bootloader will wipe the phone so you'll need to back up everything before you unlock.There are specific instructions for all of that and the images and tools at https://developers.google.com/android/images
Don't be afraid of unlocking the bootloader, it can be unlocked and locked again at your whim over and over. Doesn't hurt anything other than you get a wipe in the process.
Click to expand...
Click to collapse
I cant unlock the boot loader because the phone is SIM locked to T-Mobile. This is the whole reason I want to go back to Pie so the unlock app will work. This sucks
You can get it sim unlocked by phone if you meet their unlock requirements, or at least you used to be able to do so, I did it that way there myself a few years ago. If that's not the case anymore then... yeah, you're in a pretty sucky spot.
krabman said:
You can get it sim unlocked by phone if you meet their unlock requirements, or at least you used to be able to do so, I did it that way there myself a few years ago. If that's not the case anymore then... yeah, you're in a pretty sucky spot.
Click to expand...
Click to collapse
I do meet their unlock requirements..They have a ticket open with engineering for over a week but I’ve found out from other means that the unlock app isn’t compatible with Android 10.
Do you mean there’s another way to SIM unlock then the app? If so please enlighten me.
"You can get it sim unlocked by phone..." You call them on the good old fashioned telephone and tell them you want to remove the sim lock. Customer service can do it without the app, to my knowledge this was possible as recently as the 6T; Tmo guys were calling up and getting it done in essentially the same scenario you're in.

Categories

Resources