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
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've been trying at this for a couple days now,no success but no brick either Every phone I've owned up to this one I've been able to root and flash recoveries and custom roms as I pleased but this phone been tricky for me so I need someone here maybe to tell me my next move... So I called TMobile and I got the rep to give me a permanent unlock for my phone and I checked the Tmobile unlock app and its says permanently unlocked ...So my question now is since I cant seem to get the adb to "fastboot oem unlock" to change the device state to unlocked in the bootloader without asking me for my unlock code ,how to I get this to work? Is the next step requesting the unlock code from Oneplus because I have all the info for the form for Oneplus but don't know how to find unlock code for the form.... Help me out guys ... Thanks
bfreshdadon said:
I've been trying at this for a couple days now,no success but no brick either Every phone I've owned up to this one I've been able to root and flash recoveries and custom roms as I pleased but this phone been tricky for me so I need someone here maybe to tell me my next move... So I called TMobile and I got the rep to give me a permanent unlock for my phone and I checked the Tmobile unlock app and its says permanently unlocked ...So my question now is since I cant seem to get the adb to "fastboot oem unlock" to change the device state to unlocked in the bootloader without asking me for my unlock code ,how to I get this to work? Is the next step requesting the unlock code from Oneplus because I have all the info for the form for Oneplus but don't know how to find unlock code for the form.... Help me out guys ... Thanks
Click to expand...
Click to collapse
You now need to convert to Int. version, you can't "fastboot oem unlock" on T-Mo version without a stupid unlock token! Follow these instructions ===> https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
So I called TMobile and I got the rep to give me a permanent unlock for my phone and I checked the Tmobile unlock app and its says permanently unlocked
After this, you need to enable OEM unlock. See here.
Once you have enabled OEM Unlock under developer options, the fastboot oem unlock will work.
DanDroidOS said:
You now need to convert to Int. version, you can't "fastboot oem unlock" on T-Mo version without a stupid unlock token! Follow these instructions ===> https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
Click to expand...
Click to collapse
Thanks man,,gonna try that...
itskapil said:
So I called TMobile and I got the rep to give me a permanent unlock for my phone and I checked the Tmobile unlock app and its says permanently unlocked
After this, you need to enable OEM unlock. See here.
Once you have enabled OEM Unlock under developer options, the fastboot oem unlock will work.
Click to expand...
Click to collapse
Thanks man...Gonna check it out ..
ok so I have got a moto g pure (XT2163DL) with a tracfone bootloader and ive accepted that I cant find anyway so far to get my unlockable bootloader unlocked. I have looked and tried everything I could find without using a paid service which is probably what I need to do or just get another phone but first I have one more idea but I just dont know if it is even still possible or not. Can I use the cyanogenmod installer on my phone and unlock my bootloader and then switch back and keep an unlocked bootloader? Im running android 12. My oem unlock switch is not greyed out and it is set to unlock and even though I have tried using fastboot oem unlock and it said it was successful , it wasnt really unlocked afterall. motorola site just says my bootloader cant be unlocked. Is this a viable option?
ronnieshane1 said:
motorola site just says my bootloader cant be unlocked. Is this a viable option?
Click to expand...
Click to collapse
So why wasting time with this?