Develop Bugs

How do I check bootloader status?

Hi.
Just like the title says:
How do I check my LG G3 bootloader status?
Thanks

tarzan2003 said:
Hi.
Just like the title says:
How do I check my LG G3 bootloader status?
Thanks
Click to expand...
Click to collapse
G3 bootloader is locked and there is no unlock method except bump

The G3's bootloader is locked, no matter which variant you have.
The only reason we have TWRP working and all is because of an exploit named Bump!
Basically, it signs the images so the bootloader allows them to be run.

tarzan2003 said:
Hi.
Just like the title says:
How do I check my LG G3 bootloader status?
Thanks
Click to expand...
Click to collapse
Ariac Konrel said:
The G3's bootloader is locked, no matter which variant you have.
The only reason we have TWRP working and all is because of an exploit named Bump!
Basically, it signs the images so the bootloader allows them to be run.
Click to expand...
Click to collapse
@Ariac Konrel well that's bull****. D851 = T-Mobile version is just fine and unlocked.
About the other versions yes they are all locked. Perhaps to verify it if you really want you could go to fastboot and input command: fastboot oem device-info
What I get with the command is this:
< waiting for device >
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.023s]
finished. total time: 0.024s

I'm using a D855 variant (international), I just flashed it, root it, get custom recoveries days ago ..and I'm using CyanogenMod 13 now.. Does that mean its bootloader's unlocked ?!

[Resolved] OEM Unlocking disabled on Google Store purchased phone

EDIT: Resolved: While the OS had said it was up-to-date when I originally checked. It was not. After a bit of time it alerted me that an update was available. After updating the OS the OEM Unlocking option was no longer disabled.
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.

Gregyski said:
(Since this isn't specifically about alternate firmware, I believe this is the correct forum and not the dev forum.)
I purchased a Pixel XL specifically from Google Store because I wanted to receive either an bootloader unlocked or bootloader unlockable phone without resorting to any hacks that may not work in the future. It just arrived and I enabled Developer Options and enabled USB Debugging. However, the OEM Unlocking option is off and disabled (greyed).
I booted into the bootloader, it shows as locked. If I try to unlock it I get:
>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
If I try to flash it with the temporary TWRP boot up image:
>fastboot boot <path-to>\twrp-3.0.2-0-alpha2-fastboot-marlin.img"
downloading 'boot.img'...
OKAY [ 0.874s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.975s
I'd appreciate any suggestions for proceeding. Thank you.
Click to expand...
Click to collapse
The command should be fastboot oem unlock

ilatimer1 said:
The command should be fastboot oem unlock
Click to expand...
Click to collapse
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s

Gregyski said:
Unfortunately, that is also disallowed:
>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.046s
Click to expand...
Click to collapse
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.

ilatimer1 said:
Did you go into Developer options is Settings and enable OEM unlocking first? If you don't have Developer Options in settings go to Settings/About Phone and then tap Build Number a bunch of times to enable it.
Click to expand...
Click to collapse
Thanks for your help ilatimer1, but I have resolved it now. I had edited the original post to indicate this but probably should have followed up at the end for your sake. I was just trying to avoid bumping it. At the time I asked the question, I mentioned that that option was disabled.
When I originally setup the phone I didn't enter WiFi data since I knew a factory reset would occur when I unlocked the bootloader. However, as a result of this, I didn't get alerted to the presence of an OS update. Ultimately, I setup WiFi and discovered the availability of an update. I proceeded to update and the OEM Unlocking feature then became enabled. Thanks again.

I unwapped and went stright to fastboot. didn't know update needed. thanks

Same issue unresolved
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?

[email protected] said:
When I go into developer options OEM unlocking is still greyed out even after I downloaded the software update. Any leads on what to do?
Click to expand...
Click to collapse
Where did you buy your Pixel?

Mr. Orange 645 said:
Where did you buy your Pixel?
Click to expand...
Click to collapse
verizon store

[email protected] said:
verizon store
Click to expand...
Click to collapse
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.

Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
so there is no solution if Ive already updated to 7.1.1?
any chance a solution will open up in the future?

No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.

Mr. Orange 645 said:
No there no solution right now. I wouldn't say there's absolutely no chance of finding another exploit, this is XDA after all, but I wouldn't count on it.
Click to expand...
Click to collapse
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?

[email protected] said:
so this toolkit isnt gonna work: http://www.wugfresh.com/nrt/
?
Click to expand...
Click to collapse
No. That's for Nexus devices not Pixels anyway.

Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?

integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
Im on Verizon

integraGSR said:
Mine is in off position but once selected, it asks for pin. Bought through google and on at&t. Only thing I can think of is that I put sim that was still on contract from my Nexus 6. Maybe contact at&t?
Click to expand...
Click to collapse
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.

Mr. Orange 645 said:
The Allow OEM Unlocking switch asks for a PIN? Do you have a PIN set up for the lockscreen? I'm guessing that's what it's asking for. Your contract status with ATT has nothing to do with the bootloader status. If you think so, just try it without your SIM card in it.
Click to expand...
Click to collapse
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.

integraGSR said:
LoL that was it. Sometimes it's back to the basics, think outside the box. Didn't think about lockscreen pin as I use fingerprint scanner all the time. Thanks.
Click to expand...
Click to collapse
LOL! Glad I could help!

Mr. Orange 645 said:
The Pixels purchased from Verizon do not have unlockable bootloaders, so the switch will stay greyed out. If it is still on 7.0, you can use dPixel8 to bypass and unlock the bootloader. If you updated to 7.1.1, you are stuck with a locked bootloader.
Click to expand...
Click to collapse
But pixels purchased at Google store with 7.1.1 are still unlockable correct?
Sent from my Pixel XL using Tapatalk

Trying to Flash January OTA

I still haven't received the January Security Update, so i tried updating via the OTA. But i get the following error message. When i type adb reboot recovery. Its like my stock recovery is broken because i get a no command error. My phone isnt' recognized in win10 anymore. Anyone else having this issue? My bootloader is unlocked. Not sure why that would matter.

Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version

It maybe a bad data cable I had the same issue kinda cable must have put out to much power or something next day I tried it and everything worked.
Adb wouldn't work but fastboot commands would sometimes then next day was able to do all the commands to root and install kernal
Sent from my Pixel 2 XL using Tapatalk

sjpritch25 said:
Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version
Click to expand...
Click to collapse
The boot loader not matching usually means you did not fully unlock it. I would bet you did unlock, but skipped unlock critical. You need the second one to be able to flash the bootloader. Otherwise you can only flash the same bootloader.

sjpritch25 said:
Tried flashing factory image. I can't install because my bootloader doesn't match. Any ideas? I'm wondering if the January update isn't ready for my phone version
Click to expand...
Click to collapse
Saw this same issue with another user on another thread. First of all, do you have OEM unlocking and USB debugging turned on in developer options?
Did you already run BOTH bootloader unlocking commands?
Since your OTA and factory image flash didn't work, you'll need to go back to the factory image you were on before you started this process.
If your able to get this all accomplished, then you can proceed to the January update. Best of luck :good:

How do I go about fully unlocking the bootloader? My phone came with 8.0. I do recall that after unlocking I got the mo command booting into recovery.

I do have OEM unlocking turned on

sjpritch25 said:
I do have OEM unlocking turned on
Click to expand...
Click to collapse
And you ran both bootloader unlocking commands?
---------- Post added at 04:06 AM ---------- Previous post was at 04:00 AM ----------
sjpritch25 said:
I do have OEM unlocking turned on
Click to expand...
Click to collapse
You probably should read this thread my friend.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Thanks. I see things I didn't do correct

I had to re flash december ota and now i just got done flashing January. Had to wipe phone again though to fix the unlocked bootloader.

sjpritch25 said:
I had to re flash december ota and now i just got done flashing January. Had to wipe phone again though to fix the unlocked bootloader.
Click to expand...
Click to collapse
unsuccessful updated to January image. I updated adb and still got the corrupt bootloader message. flashed december image and have a phone again. I guess, I might need to relock the bootloader and then unlock again? my current working bootloader is TMZ12a. The January image is TMZ12b i believe and for some reason its not working.

sjpritch25 said:
unsuccessful updated to January image. I updated adb and still got the corrupt bootloader message. flashed december image and have a phone again. I guess, I might need to relock the bootloader and then unlock again? my current working bootloader is TMZ12a. The January image is TMZ12b i believe and for some reason its not working.
Click to expand...
Click to collapse
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.

sjpritch25 said:
I still haven't received the January Security Update, so i tried updating via the OTA. But i get the following error message. When i type adb reboot recovery. Its like my stock recovery is broken because i get a no command error. My phone isnt' recognized in win10 anymore. Anyone else having this issue? My bootloader is unlocked. Not sure why that would matter.
Click to expand...
Click to collapse
Don't do adb reboot recovery.
Turn it off, hold volume down, press power, and when bootloader screen shows, move volume button to choose Recovery.
When little green Android symbol shows, press Power, then Volume Up for a moment. You're now in Recovery.
Choose Apply Update from ADB, then follow instructions here: https://developers.google.com/android/ota
It will update you without wiping.

michaelbsheldon said:
Don't do adb reboot recovery.
Turn it off, hold volume down, press power, and when bootloader screen shows, move volume button to choose Recovery.
When little green Android symbol shows, press Power, then Volume Up for a moment. You're now in Recovery.
Choose Apply Update from ADB, then follow instructions here: https://developers.google.com/android/ota
It will update you without wiping.
Click to expand...
Click to collapse
Or adb reboot bootloader if you happen to be there but yes most of the time I just hit power to bring up restart then I hold volume down till it loads into bootloader
Sent from my Pixel 2 XL using Tapatalk

TonikJDK said:
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.
Click to expand...
Click to collapse
I didn't have that & that was the issue earlier. I've done that & device was wiped again. Let me try those commands & I'll post them

TonikJDK said:
In fastboot mode type
Fastboot oem device-info
Is unlock critical still locked?
If so, issue the command to unlock it. If that fails, yeah it looks like you will have to do what the other thread suggests and relock it.
Click to expand...
Click to collapse
bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.038s]
finished. total time: 0.048s

sjpritch25 said:
bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.038s]
finished. total time: 0.048s
Click to expand...
Click to collapse
Download the full factory image. Not just the OTA. Open the flash-all.bat file and look near the end and edit out the -w and save it.
As long as you remove the -w that will flash the whole factory image but save your date, apps and set up.
So after the edit put it back in fastboot mode and run the flash-all.bat file.

Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker

sjpritch25 said:
Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker
Click to expand...
Click to collapse
Have you verified the sha-256 of the image you downloaded to ensure it's not corrupt?
Goto https://developers.google.com/android/images and copy the SHA-256 checksum from the Full Image you downloaded and compare it to the file downloaded here: http://onlinemd5.com/
- Make sure to choose sha-256 on the md5 site. This will rule out if the downloaded image you have is corrupted or not.

sjpritch25 said:
Tried the January image & did that. Phone won't boot & I get corrupt message at bootlicker
Click to expand...
Click to collapse
what version of adb/fastboot are you using ?
adb version
fastboot --version
---------- Post added at 04:53 PM ---------- Previous post was at 04:51 PM ----------
michaelbsheldon said:
Don't do adb reboot recovery.
Click to expand...
Click to collapse
Why should they not do that ?

Fake UBL help...

dear.. all
i got redmi note 5 china version ram 4/64
checking in dev options status is unlock but i checked on fastboot oem device-info got this
D:\Whyred>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.003s]
finished. total time: 0.003s
so please help me ...what should i do to get unlocked boot loader
thx

kucingbaik2 said:
dear.. all
i got redmi note 5 china version ram 4/64
checking in dev options status is unlock but i checked on fastboot oem device-info got this
D:\Whyred>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.003s]
finished. total time: 0.003s
so please help me ...what should i do to get unlocked boot loader
thx
Click to expand...
Click to collapse
Did you unlocked officially and waited 360hrs via Mi Unlock tool? Also what is the MIUI Global/China version your currently using?

I had similar experience with a Redmi 5 Plus. If you're willing to open the phone up. You can short the two pins using tweezers. Then use Xiaomi MiFlash to flash the China ROM. Once done, you can now bound the account and wait 360 hours.
Otherwise return it and get your money back.

but add account on binding options , i didnt
mi account status just unlocked

Flynhx said:
Did you unlocked officially and waited 360hrs via Mi Unlock tool? Also what is the MIUI Global/China version your currently using?
Click to expand...
Click to collapse
i dont have any options
just
current account is not bound to this devices
add your account and device in miui setting---developer options---mi unlock status
BUT
in my devices MI Unlock status is UNLOCKED, so i didnt add account to binding

kucingbaik2 said:
i dont have any options
just
current account is not bound to this devices
add your account and device in miui setting---developer options---mi unlock status
BUT
in my devices MI Unlock status is UNLOCKED, so i didnt add account to binding
Click to expand...
Click to collapse
So, you can still use your phone then, no hard brick whatsoever.. Well you didn't answer my question, what miui version you are using? Cause i assume that may be a bug from a tampered rom that's why your seeing Unlocked in your Dev Options and in reality it is still locked. If you can bind your account, bind it then try to unlock it officially via Mi Unlock tool using PC, see if you will get the 360hr waiting time.

sir iam sorry to late answer
well is fix i got fake rom from i buy from distributor
i see only the test point to flashing again
can you give me recomend rom ??

i use phonecell can't upload the pic

Finaly...I find same problem with my "Whyred"...
I have ready to try with other way to fix it, until now I still can't find the way....
Maybe to fix this problem only flash rom with test point way
But until now there's still no courage to do it....

Try flashing with fastboot rom and choose clean all and lock. Otherwise you can try with edl mode

edl mode is mean i must test point ??
sad of me

abusalza said:
Try flashing with fastboot rom and choose clean all and lock. Otherwise you can try with edl mode
Click to expand...
Click to collapse
I have tried, still a fake ubl.....:crying:

i was doing test point and flashingb chinese rom
but , still got fake ubl, in mi flash tool a was select clean & lock or clean all both of them is not affected...still got fake ubl

kucingbaik2 said:
i was doing test point and flashingb chinese rom
but , still got fake ubl, in mi flash tool a was select clean & lock or clean all both of them is not affected...still got fake ubl
Click to expand...
Click to collapse
Try the Global 9.5.17 ROM. It is still safe.

finsx said:
Try the Global 9.5.17 ROM. It is still safe.
Click to expand...
Click to collapse
are you was tried ??

kucingbaik2 said:
are you was tried ??
Click to expand...
Click to collapse
I am in 9.5.17 now, it has anti v3, but 9.5.19 has anti v4 already, so don't upgrade to 9.5.19. You can see this article https://forum.xda-developers.com/re...warning-update-to-recent-miui-builds-t3814895 about ARP.

Hi, i also have the same issue as yours.
I believe you purchase the phone in Indonesia as i did. i have tried this method -> en.miui.com/thread-2109262-1-1.html but the issue is still there.
hopefully someone will find the solution for this.

flint88 said:
Hi, i also have the same issue as yours.
I believe you purchase the phone in Indonesia as i did. i have tried this method -> en.miui.com/thread-2109262-1-1.html but the issue is still there.
hopefully someone will find the solution for this.
Click to expand...
Click to collapse
yes...iam so confosed...:crying::crying:
i hope this get resolved soon
are you from indonesian...?

flint88 said:
Hi, i also have the same issue as yours.
I believe you purchase the phone in Indonesia as i did. i have tried this method -> en.miui.com/thread-2109262-1-1.html but the issue is still there.
hopefully someone will find the solution for this.
Click to expand...
Click to collapse
I am from Indonesia too. I bought the device from Batam. The first time i got it, the ROM is Global Stable 9.5.6 (i think it is). So, i upgraded it to 9.5.17 by downloading the full ROM and flashed it by updater, it succeed with nothing wrong happened. I was so lucky i didn't upgrade it to 9.5.19 as it has anti v4.
Have you tried to unlock using Mi Flash tool with present condition? What was the error message? I read this topic from the beginning and you haven't mention the result.
---------- Post added at 01:44 PM ---------- Previous post was at 01:39 PM ----------
Or may be you can try to flash the ROM with built in updater app. Any possible solution is worth to try right? The worst case, you just take your phone to service center, may be they can help you with it.

finsx said:
I am from Indonesia too. I bought the device from Batam. The first time i got it, the ROM is Global Stable 9.5.6 (i think it is). So, i upgraded it to 9.5.17 by downloading the full ROM and flashed it by updater, it succeed with nothing wrong happened. I was so lucky i didn't upgrade it to 9.5.19 as it has anti v4.
Have you tried to unlock using Mi Flash tool with present condition? What was the error message? I read this topic from the beginning and you haven't mention the result.
---------- Post added at 01:44 PM ---------- Previous post was at 01:39 PM ----------
Or may be you can try to flash the ROM with built in updater app. Any possible solution is worth to try right? The worst case, you just take your phone to service center, may be they can help you with it.
Click to expand...
Click to collapse
Hi, i have tried using miflash tool and error occur in 99% said that i need to bind my account in developer option.
The thing is that miui status is unlocked in the developer option, so there is no option to bind mi account. Thats why it is called fake ubl.

Question Install stock RETUS firmware on tracfone variant?

I recently purchased a Tracfone (StraightTalk from Walmart) Moto E 2020
I immediately noticed this device had bloatware on it, and want to install the "RETUS" or retail "stock" firmware like you'd find on one purchased directly from Motorola
So I installed ADB and the Motorola drivers on my computer and attempted to flash the stock firmware I downloaded and got these errors
sending 'recovery_a' (65536 KB)...
OKAY [ 1.436s]
writing 'recovery_a'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing recovery image.
(bootloader) *****************************************************
(bootloader) flash permission denied
sending 'super' (262140 KB)...
OKAY [ 5.759s]
writing 'super'...
(bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing super image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.333s
as you can see, it says "Flash permission denied"
the screen on the phone reports OEM_locked for the bootloader status
I then thought the bootloader needed to be unlocked, so I went to the Motorola site for unlocking the bootloader and it said that this device's bootloader isn't unlockable
So now I'm stuck with an issue, am I doing something wrong or is there some workaround to get the retail stock firmware on this device?
If not, is there a way I can root this device to remove the Tracfone bloatware?
If I can't do anything and am stuck with the Tracfone image I may just return it

The Tracfone variant of these phones come with bloatware like the important sounding "Mobile Services" which started downloading and installing apps like TikTok and Facebook and "Game Center" and stuff without my permission or ever even opening up the app the moment my device connected to WiFi which thankfully I was able to disable and then uninstall the apps it installed, however the "Device Pulse" app which Tracfone installs to give themselves remote diagnostics to your phone isn't disableable which sucks

Followup after conducting my own research, yep the bootloader is NOT unlockable, and this prevents you from both rooting the device or switching the firmware out for something else.
To anyone who is wanting to purchase one of these devices, I'd avoid the Tracfone StraightTalk/Total Wireless, etc. versions entirely

my own experience with a boost version from walmart was that though it was not listed on the motorola website as supported for bootloader unlocking, I tried following their process/webform anyway, and they did give me a bootloader unlock code which did work for mine.

It's not rooting, but it helps stop the bleed:
AppMgr III(com.a0soft.gphone.app2sd)-(App 2 SD, Hide and Freeze apps)
https://www.apkmirror.com/apk/sam-lu/appmgr-iii-app-2-sd-hide-and-freeze-apps/#variants
was a great help in Freezing these minions
All-In-One Toolbox(imoblife.toolbox.full)
https://www.apkmirror.com/apk/aio-s...toolbox-cleaner-booster-app-manager/#variants
disable startup of apps
Adblock Plus(org.adblockplus.android)
https://aapks.com/apk/adblock-plus/version/
old, but blocks ads by proxy

Well that's the exact model I have and I just successfully unlocked my bootloader... Seriously, it's now unlocked.

6j6s69 said:
Well that's the exact model I have and I just successfully unlocked my bootloader... Seriously, it's now unlocked.
Click to expand...
Click to collapse
If you can list the steps you followed, sure would be helpful.

6j6s69 said:
Well that's the exact model I have and I just successfully unlocked my bootloader... Seriously, it's now unlocked.
Click to expand...
Click to collapse
I also have the exact model and version so i would like to know how you unlocked it.

Polayis said:
I also have the exact model and version so i would like to know how you unlocked it.
Click to expand...
Click to collapse
Just looke, one post on the site, and nothing since. Unlikely to ever be back.
Given that, what is the purpose of Tracfone locking the bootloader for a phone they will never get a penny of revenue?

6j6s69 said:
Well that's the exact model I have and I just successfully unlocked my bootloader... Seriously, it's now unlocked.
Click to expand...
Click to collapse
Motorola xt2093

MotoDad said:
Motorola xt2093
Click to expand...
Click to collapse
I doubt you will get a response. 6j6s69 is a one post wonder. wonder if he's blowing smoke or telling tall tales. One post never to return...

GrumpyUnk said:
I doubt you will get a response. 6j6s69 is a one post wonder. wonder if he's blowing smoke or telling tall tales. One post never to return...
Click to expand...
Click to collapse
Thanks. I didn't think I get an actual response but figured I'd take the bait haha