My carrier (C Spire) has found a problem with the device on their network that makes the device lose it's signal all the time. They claim it is a device problem anyway. I have unlocked the bootloader on the phone, but have not flashed any roms or made any other changes to the phone. Just the unlocked bootloader. They have said that since they know it is a problem with the device, they will let owners come in and exchange the phone for a Galaxy SIII free and clear. The only stipulation is it has to be in like new condition. My phone is perfect except for the unlocked bootloader. They'd probably never notice if it wasn't for that notification screen when the phone reboots that would tell them. I need to relock the bootloader to make that screen go away.
So, my question is, how do I do that? I've tried doing 'fastboot oem lock' but that doesn't work.
This is what I get when I try:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.014s]
finished. total time: 0.016s
If I run the command as it suggests I get:
Code:
C:\Users\adear\AppData\Local\Android\android-sdk\platform-tools>fastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.246s]
finished. total time: 0.248s
I'm not sure what to do to get it to lock again.
Can anyone please help?
The problem is, you've unlocked it 'officially' from Moto... so it's registered in the database as unlocked.
You can try to change the boot logo, I haven't tried yet... Supposedly you can to get rid of that annoying screen.
Maybe you will just have to take it in and hope they don't reboot it. Kinda sucks that we have official unlocks now, because they can now easily track who has unlocked their phones and who hasn't :/
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
adear11 said:
According to Moto, you can relock the bootloader, although the warranty remains voided. I know Moto knows about it, but I doubt very much that the carrier is going to go so far as to check it.
I just need to know why the 'fastboot oem lock' command didn't work. And what I can do to relock it.
Click to expand...
Click to collapse
Did you try using the same key to unlock to relock?
I've never bothered relocking...
arrrghhh said:
Did you try using the same key to unlock to relock?
I've never bothered relocking...
Click to expand...
Click to collapse
Is the key required to relock? I had not tried using it.
adear11 said:
Is the key required to relock? I had not tried using it.
Click to expand...
Click to collapse
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
arrrghhh said:
I said I've never tried to relock.
It makes sense tho. Same process to relock as it was to unlock. Give it a shot, what do you have to lose.
Click to expand...
Click to collapse
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
adear11 said:
Just gave it a try, got the same result. "Fail: Please run fastboot oem lock begin first!"
Click to expand...
Click to collapse
You entered fastboot oem lock begin <key>?
arrrghhh said:
You entered fastboot oem lock begin <key>?
Click to expand...
Click to collapse
When I do 'fastboot oem lock begin [key]' I get "(bootloader) Ready to flash signed images".
From here, if I do 'fastboot oem lock' again, I get "Re-Lock Failure. See display." On the phone's display, I get:
Code:
No valid PIV block in SP for system
piv validation failed (system)
Re-lock failure
Hrm. I was poking around Moto's FAQ's and community site, and they talk about relocking - but not in detail unfortunately. They cryptically state that they will not release any stock recoveries at this time - so perhaps if you don't have the stock recovery, you can't relock...?
I would post up on Moto's forums or call their support... Not sure how much help they will be, but their website leaves much to be desired about the relocking process...
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
shabbypenguin said:
oh dear some anonymous person had pasted motorola's flashing script, perhaps you can use it to figure out how to fix your device
http://pastebin.com/Ca8wcGAv windows
http://pastebin.com/SnxrbdaW linux/mac
im just really glad i happened to be browsing around pastebin and found that in it.
Click to expand...
Click to collapse
so, if one were interested in using this anonymous persons script, how would one proceed?
adear11 said:
so, if one were interested in using this anonymous persons script, how would one proceed?
Click to expand...
Click to collapse
i would imagine gathering all the files and putting them in the proper spots/folders would assemble a replica of this script. i was just mentioning you should look thru to see if there is anything taht helps you tho
In short, in order to relock the bootloader, you have to flash signed software in the process.
Ugh why did I try this lol.. Still having problems. I restarted my computer and that fixed the problem "waiting for device" now in cmd it will at least recognize the phone BUT, I get this trying to figure out some information
getvar:cid FAILED (command write failed (unknown error))
Related
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.
geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/
geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
Hello,
I messed with my Pixel phone and now I feel it bricked. It was working fine until I update it to 8.0 Oreo. Then I rooted it using magisk.
Later, I decided to re-lock my bootloader, which was really a big mistake. I did re-lock it using the following command:
fastboot oem lock
It showed me if I lock my bootloader, it would wipe everything. I hit yes.
After that, this issue started, my phone won't start, as soon as the google logo shows up, it restarts and does the same thing everytime.
I tried to install the factory image, "sailfish" for Pixel 8.1.0, using the following command:
flash-all
it gave me an error message. It said I need to unlock the bootloader.
Of course, I tried to unlock the bootloader using the following command:
fastboot flashing unlock
It also gave me an error message, it said:
FAILED (remote: oem unlock is not allowed)
I don't know what else should I do. I tried to find a solution for my problem, but there is no clear answer.
One of the common solution is to enable the USB debugging/OEM unlocking from the developer settings. But, again, I can't even turn on my phone and use it normally.
The only thing that I can access to is the bootloader screen.
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
KittyRgnarok said:
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
Click to expand...
Click to collapse
You are totally right. I'll contact them to RMA my phone.
hamooz92 said:
You are totally right. I contact them to RMA my phone.
Click to expand...
Click to collapse
Good luck. Update the thread with the results cuz I'm curious if they will rma a phone bricked like that
I lock bootloader on Verizon Google Pixel when my device have TWRP and i have brick! Device Loading up to logo Google on 1 sec and reboot. Fastboot work, but i don't unlock bootloader. In recovery is don't enter. Please help me!
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
kkjb said:
https://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614 ....very important advice. With my limited knowledge NEVER relock unless you have signed OEM images correctly reloaded into device before locking.
Click to expand...
Click to collapse
There is still no solution to this problem? ((
Unlock again.
lafester said:
Unlock again.
Click to expand...
Click to collapse
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
Put the phone in fastboot mode, then run `fastboot flashing unlock` from a PC. If it says unlocking not allowed, you're out of luck, it's a brick now. Never lock your phone without being 100% stock on both slots
Groh12 said:
how can I unlock it now?
I already wrote to a man who used to be for money unlocked Verizon bootloader, but he says "No solution for this problem yet"
Click to expand...
Click to collapse
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
lafester said:
No idea. I've never relocked unless I am completely stock and take at least one ota first to make sure, along with full factory resets before and after updating.
There are others here that claim they where able to unlock again and save their phones though so maybe it's possible.
Click to expand...
Click to collapse
In this topic https://forum.xda-developers.com/pi...bootloader-t3540772/post77016940#post77016940 man has unbrick Pixel XL, but i think that method will work on Pixel.
I have a TracFone moto g pure (XT2163DL) running android 12, build number S3RHS32.20-42-13-2-1. I managed to get my oem unlock to show up and turned it on. First I tried using the Motorola unlock site to unlock my bootloader but it said it wasn't eligible. So then I tried using fastboot command "fastboot oem unlock" and a screen popped up telling me I can choose to unlock my bootloader and when I told it to unlock I received a message saying it was successful. But it isn't. It said it's unlocked but yet it is still locked anyway. I know TracFone has problems unlocking bootloader's but why would it let me get that far if it is impossible to unlock? Is there anything else I can do? If anyone knows something else I can try please point me in the right direction. I don't mind doing my homework after all that's how I learn but I'm just at a point where I need some guidance.please help me and always thank you so much for your time in advance...
If the bootloader reports unlocked, what makes you say it's still locked?
V0latyle said:
If the bootloader reports unlocked, what makes you say it's still locked?
Click to expand...
Click to collapse
Nothing is wiped and it still says OEM secured on the fastboot page. The only difference now is when I try to reboot back into system it will first boot back into the bootloader again and then it will boot into system when I reboot a second time
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
TimmyP said:
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
Click to expand...
Click to collapse
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
TimmyP said:
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
Click to expand...
Click to collapse
Permanent unlock is sim unlocking, has nothing to do with OEM unlocking
Thats great thanks
I got it. Set to midi connection so ADB detects phone.
adb shell
pm disable-user com.qualcomm.qti.uim
Now OEM unlocking is ungreyed
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
TimmyP said:
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
Click to expand...
Click to collapse
Maybe the site down, probably wait a bit, got the same error too
Thanks Ill get all prudent info in a text file. What a pita. I loathe having a new phone and not knowing whether I can root it. So much setting up already.
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
TimmyP said:
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
Click to expand...
Click to collapse
i got mine around an hour later after applying mine, maybe check hourly to see if you gotten it or not?
Nothing. Tbh I think Im gonna return this. Its only 128gb version and I was much happier with rooted A32 5G.
Sucks cant even use tasker for fun stuff.
Look through the OP9 forums for the OnePlus Tool..... it helps you get the number you write down to request the unlock code from OnePlus, also it can ungrey the OEM switch
Thanks but I already got that stuff requested. Still no token :-( Been talking to support tho they said they are on it!
underworld737 said:
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Click to expand...
Click to collapse
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
barguybrady said:
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
Click to expand...
Click to collapse
Try ,,,,,,fastboot oem unlock,,,,
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
TimmyP said:
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
Click to expand...
Click to collapse
I already have that... Hence my confusion.
I'm thinking that there's Just One Little Thing I'm doing wrong here... Can't figure it out..!
Aha. I had been doing it in the wrong order.
Bash:
fastboot devices
fastboot flash cust-unlock unlock_code.bin
fastboot oem unlock