Related
Hello all,
I've got an Arc S that I've been trying to unlock the bootloader on using Sony's method, without success.
1. I have fastboot and adb installed on my machine (Linux Mint 14 32bit)
2. I've pulled the unlock code from Sony's website
3. I set my udev rules as laid out in this tutorial.
4. I have checked my bootloader to confirm that it can be unlocked (and currently is locked)
5. Fastboot is working (When I type in sudo fastboot devices, I get a hexadecimal string in response)
6. However, when I try to unlock, it always fails.
Initially, it gave me a "oem unlock failure code". After I rebooted thought, the code changed. Instead of something like this
Code:
oem unlock failed!
it gave me this
Code:
...
and did nothing. I let it sit for a few minutes and then forcibly shut down terminal, no damage done to the phone.
I'm quite confused at this point. From all my google searching I can't figure out why the booloader won't unlock. I'm pretty sure that I have the right unlock code.
A second and curious thing that may or may not be related is that the phone is rooted, but when I tried to transfer CWM via fastboot it threw an error, saying that the phone needed to be rooted first. However, it is rooted and apps such as Titanium Backup work just fine, verifying the root. Can anyone give me some direction on this?
I know there is a video on the how to unlock lt18i bootloader. It also has step by step process on fixing issues for unlocking bootloader. Lemme get.it for ya.
Sent from my LT18i using xda premium
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
sinkster said:
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
Click to expand...
Click to collapse
I don't believe that it is simlocked. I don't believe the phone was purchased through a carrier. For clarification, this is a friend's phone so I would need to ask them as to where they purchased it.
sinkster said:
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
Click to expand...
Click to collapse
No, it is not simlocked, else it would not show Bootloader Unlock Allowed: Yes
To OP: Write out the command you used to unlock the bootloader.
Someguyfromhell said:
No, it is not simlocked, else it would not show Bootloader Unlock Allowed: Yes
To OP: Write out the command you used to unlock the bootloader.
Click to expand...
Click to collapse
As taken from the Cyanogenmod Wiki page for Anzu devices:
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY was the bootloader unlock I received from Sony.
The dots indicate the software's not detecting your device. I had the same problem. Try reinstalling the drivers. If it still fails, maybe you can give the method outlined in the link below a go. It's for the relatively newer Sony devices, but maybe it'd work with the Arc. I haven't personally tried unlocking via Flashtool, but for me, the Fastboot command-based experience hasn't been all too good. I now use the Fastboot option in Flashtool, as opposed to standalone Fastboot, to flash every kernel that I use. Works like a charm each time, and what's more, it does away with the need to key in commands in the exact syntax.
http://forum.xda-developers.com/showthread.php?t=1971363
MarcSinger said:
The dots indicate the software's not detecting your device. I had the same problem. Try reinstalling the drivers. If it still fails, maybe you can give the method outlined in the link below a go. It's for the relatively newer Sony devices, but maybe it'd work with the Arc. I haven't personally tried unlocking via Flashtool, but for me, the Fastboot command-based experience hasn't been all too good. I now use the Fastboot option in Flashtool, as opposed to standalone Fastboot, to flash every kernel that I use. Works like a charm each time, and what's more, it does away with the need to key in commands in the exact syntax.
http://forum.xda-developers.com/showthread.php?t=1971363
Click to expand...
Click to collapse
I tried unlocking the bootloader via Flashtool and I got the same result of
Code:
oem unlock failed!
. So that means that something is wrong with my fastboot installation (not likely)my udev rules(possible) or for some crazy reason the phone is not reporting back correctly. A curious thing I noted is that when the phone is detected via adb it doesn't return the phone's IMEI. It does return a number, but it does not match the IMEI. Has anyone ever heard of that situation?
Guanfy said:
I tried unlocking the bootloader via Flashtool and I got the same result of
Code:
oem unlock failed!
. So that means that something is wrong with my fastboot installation (not likely)my udev rules(possible) or for some crazy reason the phone is not reporting back correctly. A curious thing I noted is that when the phone is detected via adb it doesn't return the phone's IMEI. It does return a number, but it does not match the IMEI. Has anyone ever heard of that situation?
Click to expand...
Click to collapse
I don't believe Fastboot returns the phone's IMEI. It's always looked to me like a random number that's generated to show successful connectivity between the device and the Fastboot program. But then again, I could be wrong.
Anways, despite the message you got, it's looking increasingly likely that your bootloader cannot be unlocked.
PS: You retired your SGS III, but kept your Arc? The decision really befuddles me.
MarcSinger said:
I don't believe Fastboot returns the phone's IMEI. It's always looked to me like a random number that's generated to show successful connectivity between the device and the Fastboot program. But then again, I could be wrong.
Anways, despite the message you got, it's looking increasingly likely that your bootloader cannot be unlocked.
PS: You retired your SGS III, but kept your Arc? The decision really befuddles me.
Click to expand...
Click to collapse
After much research I've found that when you get the "remote: oem unlock failed!" message it means you've enter an incorrect unlock code. Thing is, I know that I have entered the IMEI correctly on Sony's website, so I'm stumped there. I tried this setup in windows and got the same result, so I don't think it's fastboot or drivers anymore. It makes me wonder why I would be getting an incorrect unlock code...
To answer your PS, this phone belongs to a friend of my whom I'm doing a favor for. Note I don't have the Arc S in my sig. My retired SIII went to my wife, who was quite happy to have it.
Guanfy said:
After much research I've found that when you get the "remote: oem unlock failed!" message it means you've enter an incorrect unlock code. Thing is, I know that I have entered the IMEI correctly on Sony's website, so I'm stumped there. I tried this setup in windows and got the same result, so I don't think it's fastboot or drivers anymore. It makes me wonder why I would be getting an incorrect unlock code...
To answer your PS, this phone belongs to a friend of my whom I'm doing a favor for. Note I don't have the Arc S in my sig. My retired SIII went to my wife, who was quite happy to have it.
Click to expand...
Click to collapse
Are you sure that you left out the LAST number of the IMEI, when entering it on the website? You need to do that, else you get invalid code.
Someguyfromhell said:
Are you sure that you left out the LAST number of the IMEI, when entering it on the website? You need to do that, else you get invalid code.
Click to expand...
Click to collapse
Yup, that I have. I originally entered the 15 digit code and the website threw an error, so I deleted the last digit to get the unlock code that I tried.
same issue as LT26ii
Well I have exactly the same issue at my Xperia SL LT26ii, it just shows "oem unlock failed", do anyone know how to fix this ?
nkiy said:
Well I have exactly the same issue at my Xperia SL LT26ii, it just shows "oem unlock failed", do anyone know how to fix this ?
Click to expand...
Click to collapse
oem unlock failed
Problem solved!
Hey guys, I just unlocked my LT26ii after many times of "oem unlock failed". Here's my solution:
0. well first just remember your IMEI code, cause later it will changed.
1. Download a new firmware in ftf format.
2. Update firmware with Flashtool.
3. Turn on your phone and get you imei code. Now you should got a new one different from the previous one.
4. Use the NEW imei to unlock your phone.
Good Luck !
PS: dont guarantee that worked but if it does please let'me know.
Need to re-unlock my phone. It states the unlock has been tampered. I have a Windows 8.1 system and need to unlock the phone, again. Does anyone have this fix???? The command prompt does not give you a C:\ it gives you a C:\>. How do you get past this??
suzyq42 said:
Need to re-unlock my phone. It states the unlock has been tampered. I have a Windows 8.1 system and need to unlock the phone, again. Does anyone have this fix???? The command prompt does not give you a C:\ it gives you a C:\>. How do you get past this??
Click to expand...
Click to collapse
It doesn't show the unlock has been tampered. lol. It shows your phone has been tampered with (unlocked your bootloader) and also shows on a different line that your bootloader has been relocked.
You need to unlock it like the first time. Go to the HTC dev site and get the unlock code. I would try to run the first one I got again first if you still have it in your email.
Need win 8 drivers
Sent from my unknown using XDA Free mobile app
xunholyx said:
It doesn't show the unlock has been tampered. lol. It shows your phone has been tampered with (unlocked your bootloader) and also shows on a different line that your bootloader has been relocked.
You need to unlock it like the first time. Go to the HTC dev site and get the unlock code. I would try to run the first one I got again first if you still have it in your email.
Click to expand...
Click to collapse
Have phone in fastboot but the PC in command prompt is c:\>. Doesn't let me get any farther. able to get the command prompt and codes but now the disclaimer will not come up on my phone to finish the process. Ideas????
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
I believe you're not able to relock the bootloader until Motorola release a signed bootloader. I had the page once before I'll see if I can find it again and add an edit if I do.
mapki said:
Is it possible to relock bootloader without wiping data? All my previous devices didn't require wipe, but I received such strange warning when tried to relock bootloader on Z2 Force Sprint
Click to expand...
Click to collapse
Don't relock your bootloader unless you want a brick. Technically you can relock it, but everything has to be legit. You've already voided the warranty, relocking won't reinstate that, all that will happen is you'll be bricked with nothing to do about it because you've locked the bootloader.
Why do you want to relock it?
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
jeffritz1 said:
I would like to relock my bootloader and wondering the accuracy of this last post. Will relocking my Sprint Z2 Force bootloader brick my device?
I'm running completely stock via OTA 8.0.0 no root. The reason I want to relock my bootloader is bringing my phone to out of box status and pass SafetyNet. I don't want to root to get this done and I want to continue receiving OTA's.
I understand that my warranty is void when I unlocked bootloader originally and I understand relocking my bootloader will wipe data (factory reset).
Will this brick my phone?
Can I relock anymore?
What are the fastboot commands to relock the Z2?
Thanks!
Click to expand...
Click to collapse
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Uzephi said:
I would suggest flashing one of the flash alls for sprint before doing it to ensure being fully stock. The command is below. Also i f you ever have any issues and want to reunlock, you always can with your original unlock code.
"fastboot oem lock"
You'll get a "are you sure" message. Type in the command again and poof, relocked status.
Click to expand...
Click to collapse
So, I did a "fastboot oem lock" and it re locked the bootloader. Restart bootloader, shows locked. Restart phone and still getting a splash screen similar to the one when your unlocked but this time it says "Device has loaded a different Operating System". Continues to boot normally into the system without issues. This was odd so I unlocked again did a Flashall w/ "XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" and "fastboot oem lock". Both times said the lock was successful. But I'm still getting this boot splash screen with test reading "Device has loaded a different Operating System". System boots but still fails SafetyNet.
What gives? What am I missing?
From what I can muster up on XDA I can see that "you need a signed boot.img". Does this mean something and how can I find this?
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
jeffritz1 said:
Can anyone who has unlocked and then relocked their bootloader report on the behavior of your phone? Do you get the same "different OS" splash screen? Has anyone been successful at making it go away and passing safetynet?
Click to expand...
Click to collapse
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
jeffritz1 said:
Thanks for the reply! As of now I am stock latest Sprint 8.0.0 July update with bootloader locked. I get the "Your device has loaded a different Operating System" splash screen when I boot up with a "ID:" followed by nothing. I don't know what this "ID:" with nothing following this means. Also when I run a SafetyNet status app is says failed. But, everything else in the OS appears to be working. Google Play shows "Certified" status and all my apps that require SafetyNet is working (Banking apps, Netflix, Hulu, Google Pay, etc...). So I accomplished my mission in getting these apps working and everything else appears stock. The only thing that troubles me is this "Your device has loaded a different Operating System" splash screen and the failed status in the SafetyNet app. Would love to know how to fix this or an explanation on why.
Click to expand...
Click to collapse
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Marcowe said:
That message appear because you've unlocked your bootloader before, I'm getting that message too and I can update my device via OTA. If you change that splash screen OTAs will fail.
Click to expand...
Click to collapse
Yeah, I was trying to find out if the phone could be reverted back to an out of back state. Another words, no splash screen saying "HEY! I HAVE BEEN MESSED WITH!" like you can on any other phone I have ever owned.
Thanks!
Yes you can
thomas.raines said:
I've been working on this all morning trying a couple different methods. But none have been successful. But the best I can figure, when in bootloader, there is a message stating that your system is "Modified". Somehow, that needs to get changed to what I can only speculate as "unmodified", or something alike.
I tried 3 different versions of returning to stock
First one I tired I cannot seemed to find now
Secondly, I tired:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Posted by Uzephi
I added the command "fastboot oem lock" 2 times just above the fastboot reboot command; thus locking bootloader.
But upon reboot, I still get the modified OS message.
Lastly, I tried this method
https://forum.xda-developers.com/showpost.php?p=76850077&postcount=6
I downloaded https://mirrors.lolinet.com/firmware/moto/nash/official/TMO/XT1789-04_NASH_TMO_C_8.0.0_OCX27.109-36_subsidy-TMO_regulatory-DEFAULT_CFC.xml.zip
Followed the instructions (to some degree) and modified them for Linux since I am not a windows user.
After reboot, radio did not work. No WiFi, not data, nothing. Developer options was already enabled, but oem bootloader unlocking option was grayed out. Now I cannot unlock my bootloader and flash an updated OS.
Click to expand...
Click to collapse
Yes you can , I already had this issue with my moto z2 force in Morocco , so what I did is I connected the phone to internet via bluetooth and when I added my google accounte the unlocking oem in dev option was normal , so I was able to flash roms again . Hope this will help you
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
EddiePR said:
I think there is no way to relock bootloader without wipe the device. Also you can relock the bootloader and you will not have any problems. I've already done it, at least with my sprint moto z2 force. the message there is no way to remove it, only flashing a logo.bin, "the boot splash" or replacing the logo.bin of the flash all package by the one of your preference.
Click to expand...
Click to collapse
If you do that OTAs will fail
Marcowe said:
If you do that OTAs will fail
Click to expand...
Click to collapse
Yes, you are rigth
So, which of the methods to re-lock did finally work? I was running on Android 8 before, OTA failes for at least 10 times, but suddenly it worked to upgrade to Android 9. Now I am weirdly not passing SafetyNet-check anymore (was working fine on Android 8, GooglePay etc).
Any recommendations? I just need the stupid GPay thing working
So I followed instructions on how to unlock bootloader on my pixel xl. And now I'm unable to connect to my network. I put the sim card in and it doesn't recognize it. I've tried multiple times to restart phone with no luck. So I did this last night and the only solution was to hard reset the phone once more. But that untenable that oem unlock function! So I unlocked it once more just now and I'm in the same situation! Should I proceed by unlocking oem and than do a hard reset? I'm not really sure how to proceed from here if someone could give me some insight i would really really appreciate it!!!
[email protected] said:
So I followed instructions on how to unlock bootloader on my pixel xl. And now I'm unable to connect to my network. I put the sim card in and it doesn't recognize it. I've tried multiple times to restart phone with no luck. So I did this last night and the only solution was to hard reset the phone once more. But that untenable that oem unlock function! So I unlocked it once more just now and I'm in the same situation! Should I proceed by unlocking oem and than do a hard reset? I'm not really sure how to proceed from here if someone could give me some insight i would really really appreciate it!!!
Click to expand...
Click to collapse
Are you saying that it isn't recognizing your SIM, and saying there is no SIM inserted, or are you saying that it's simply not applying the right APN settings and so you can't get cellular data and such
hi , its easy , just remove your sim card , and flash the phone again
Once you OEM unlock your phone a hard reset should not relock your phone. The only way your phone should relock is by using issuing the command OEM lock or OEM flashing lock.
There is an issue with some phones and systems where the "allow OEM unlocking" check box will come unchecked, this doesn't mean the phone is relocked though.
I got it figured out thanks! Now I'm just trying to install twrp but I'm not having much luck lol
[email protected] said:
I got it figured out thanks! Now I'm just trying to install twrp but I'm not having much luck lol
Click to expand...
Click to collapse
You have to boot to TWRP from fastboot with the TWRP image file and then flash TWRP from within that recovery.
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.