Related
hey guys everyone esle seems to be getting thier bootloaders unlocked with out a problem but im running into a problem maybe i can get some advice
I have all the drivers and everything required to unlock my bl and the key is the same i double checked it. here is my issue while going through the fastboot commands heres what happens
upon entering "fastboot.exe -i 0x0fce getvar version" i get 0.3 back which is what i need to get according to everything i have read good right?
now when i enter "fastboot.exe -i 0x0fce oem unlock 0x************************" i get the response "remote: oem remote unlock failed"
the same response i get when using flashtool to unlock the bootloader can some one possibly give me any ideas whats stopping my bootloader from being unlocked?
thanks in advance
darkharbinger81 said:
hey guys everyone esle seems to be getting thier bootloaders unlocked with out a problem but im running into a problem maybe i can get some advice
I have all the drivers and everything required to unlock my bl and the key is the same i double checked it. here is my issue while going through the fastboot commands heres what happens
upon entering "fastboot.exe -i 0x0fce getvar version" i get 0.3 back which is what i need to get according to everything i have read good right?
now when i enter "fastboot.exe -i 0x0fce oem unlock 0x************************" i get the response "remote: oem remote unlock failed"
the same response i get when using flashtool to unlock the bootloader can some one possibly give me any ideas whats stopping my bootloader from being unlocked?
thanks in advance
Click to expand...
Click to collapse
You have to pay someone to unlock your bootloader for you and flashtool won't cut it. R800x as far I know there is no key to unlocking bootloader for free. I highly recommend Alejandrissmo a fellow reputablesite and xda member.
Site. unlock-bootloader.com
Sony allows bootloader unlocking now
Sent from my R800x using xda premium
chery2k said:
You have to pay someone to unlock your bootloader for you and flashtool won't cut it. R800x as far I know there is no key to unlocking bootloader for free. I highly recommend Alejandrissmo a fellow reputablesite and xda member.
Site. unlock-bootloader.com
Click to expand...
Click to collapse
This is incorrect. I had my phone bootloader unlocked by ashergrey over a year ago via an unlock code. Even though I am unlocked I went to the sony unlock site and it gave me an unlock code to my email. So you should only need to get that unlock code, and make sure you have the latest flashtool drivers. There are tutorials on this in the Development and General section
OK but the problem is that the one driver(android_winusb.inf) they specifically ask you to install isn't installing...device manager doesn't show bootloader interface file... Thats what's stopping it from unlocking...
Sent from my R800x
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.
I'm really considering getting this device, my brother just got it and it seems great but, before I commit to it I want to make sure the bootloader is unlockable. Can anyone confirm that you can unlock the bootloader with the OEM unlock command?
BL is not unlockable at this time.
That's too bad hopefully that changes in the future. Either officially or unofficially.
there was a topic on nokia 6 forum for unlocking bootloader for 2nd gen but there are no codes available anymore we missed the boat
Oh come on. Can you send me the link, maybe there is something in the wayback machine?
Dingybeatup said:
Oh come on. Can you send me the link, maybe there is something in the wayback machine?
Click to expand...
Click to collapse
Usually oem provided unlock codes are generated on a per device basis so doing this would be pointless. Basically you send a command to the device it gives you a number and you give than to the OEM and they give you another code to use with OEM unlock and mark your warranty void. Which is honestly probably illegal now (in the us at least) based on what the FCC had been doing lately. I mean them voiding your warranty like that is illegal. That's probably one of the reasons they would stop giving it codes.
Sent from my A0001 using Tapatalk
just up on nokia 6 forum paid codes will be starting soon its starts tomorrow for china ,cant wait it will be $5 per device very resonable
@safron35
just up on nokia 6 forum paid codes will be starting soon its starts tomorrow for china ,cant wait it will be $5 per device very resonable
Click to expand...
Click to collapse
Can you share the link of the thread for buying bootloader.... all i want is to root my Nokia 6.1 just for Viper4Android nothing else
[GUIDE] How to unlock bootloader for your Qualcomm based Nokia Android Phone
safron35 said:
[GUIDE] How to unlock bootloader for your Qualcomm based Nokia Android Phone
Click to expand...
Click to collapse
This doesn't have a link.
Sent from my A0001 using Tapatalk
xda-developers 8 search plus
Home Nokia 6 Nokia 6 Guides, News, & Discussion [GUIDE] How to unlock bootloader for your Qualcomm based Nokia Android Phone by hikari_calyx
https://forum.xda-developers.com/no...-to-unlock-bootloader-qualcomm-t3769930/page1
Sent from my A0001 using Tapatalk
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-unlock-bootloader-qualcomm-t3769930
safron35 said:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-unlock-bootloader-qualcomm-t3769930
Click to expand...
Click to collapse
Hopefully someone can find a free way to generate the codes but if not we'll see if this method works on this device and if it leads to it getting twrp and Lineage OS or other roms.
Sent from my A0001 using Tapatalk
All I want is to be able to flash original firmware
The official answer of Nokia about bootloader
These is the official answer Nokia customer when I ask about bootloader
yes its unlockable you just have to pay $5 for the service. my question is why is there no twrp or root yet? I cant post the link to the unlock but you can do a google search.
Nokia havent relesed yet bootloader codes. If you buy one (its a tool that is like server and they have a guy in the nokia or maybe have hack nokia server and the send you your unlock.bin file) these is the commands that you need but first you must unlock the dev option and put on oem unlocking
install fastboot drivers for phone.
power off phone.
run
fastboot -i 0x2e04 flash unlock <signature file>
connect phone to cable
run
fastboot -i 0x2e04 oem unlock-go
follow instructions on phone display if any
if you are in android 7.1 and not updated ,there's a way ,through 9008 mode to unlock it.
if you already updated through ota, there's only paid way to unlock it till now.
PM me for unlock bootloader
Is it too soon to start a bounty for a bootloader unlock? Do we even have any devs using this device(Lm-G710TM)? Im good for $100+.
It's not soon for USA unlocked (G710ULM) because 11th July was the release, till now why there's no bootloader for this unlocked variant! Already European variant enjoying root.
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
totally agree, this is a great and solid phone. Could use a few tweaks and it'll be even better!
Alcolawl said:
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
Click to expand...
Click to collapse
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I know VZW it's all locked The OEM switch is missing also. I'm assuming for at least Verizon there needs to be an exploit if ever found.
For now, I am just talking about the TMO version.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-g7-thinq/help/t-mobile-oem-unlock-t3833156
runningnak3d said:
For now, I am just talking about the TMO version.
-- Brian
Click to expand...
Click to collapse
Welcome aboard mate, been looking for your presence here but was doubting it as you don't have this device as of yet. I'm happy to see you and say that I was wrong, can't thank you enough for the work you have done on other devices.
Will be more than willing to help anyway I can, although I am currently on the sprint variant for the moment.
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
runningnak3d said:
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
Click to expand...
Click to collapse
LG G710ULM owner here. I know it's not specifically a T-Mobile version but it does allow OEM unlocking by default. I could be wrong, but I'm guessing the differences between the G710TM and G710ULM aren't that big (if any at all). If you need any info from my end, let me know. I'd love to get the ball rolling on bootloader unlocks for this phone. Lots of untapped potential here.
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Upon rebooting into Bootloader I'm presented with a quick guide for unlocking the phone:
1) Read Device ID
:fastboot oem device-id
2) Write Unlock Key
:fastboot flash unlock unlock.bin
3)Check bootloader is unlocked
:fastboot getvar unlocked
fastboot oem unlock results in a FAILED (remote: 'unknown command') message. Screenshot attached. My first attempt didn't work because I guess I didn't have the right bootloader drivers installed.
So it looks like even the unlocked models are in the same boat as everyone else, except Europe.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
20degrees said:
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
Click to expand...
Click to collapse
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Alcolawl said:
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Click to expand...
Click to collapse
Be forewarned, I've noticed that fastboot doesn't always work, despite latest drivers. As of late, the Pixel has been known to hang on these same commands at times as well. My Moto Z2 Force suffers from this error as well.
---------- Post added at 04:11 AM ---------- Previous post was at 04:04 AM ----------
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I hope you know many are INCREDIBLY excited to have you on board! I'm not advanced, but once I receive my computer back, I'll definitely be available to help with providing info and helping test, as I have a TMO variant (I may or may not work for TMO as well, so yeah... )
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Own a TMobile variant, oem unlocking option is there, fastboot commands do not work (or are extremely limited)
getprop | grep unlock (if it means anything)
[Ro.oem_unlock_supported]: [1]
[Sys.oem_unlock_allowed]: [1]
I know I probably didn't help out much, if you have any other questions feel free to ask I'll help out as much as I can. thank you for contributions and congrats on the V30 root.
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I have the tmobile variant. Let me know what you might need.
Unlock Slider is present in developer settings and is not greyed out. Unlock command just hangs.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Sprint variant also has "Allow OEM unlocking" available and it is changeable
So you can issue fastboot flashing unlock_critical but not fastboot flashing unlock -- that is just weird.
If you issue the unlock_critical, do you get the warning that your phone is possibly corrupt, but will continue to boot?
-- Brian
unlocking the bootloader is a fairly easy process
it took me about 5 minutes
You can follow the motorrola guide here
the short version:
Go to the site
agree to terms
Download fastboot and the fastboot drivers
turn phone off , connect to pc, and power on + volume down
type: fastboot oem get_unlock_data
Paste the key into website, and ask for unlock key. That will be delivered to your inbox within 5 minutes,
and then paste it into fastboot: fastboot oem unlock UNIQUE_KEY
anyway, the provided guide by motorrola is quite nice, just follow that instead of my mumbling
edit:
ps. the device will reset itself to factory default. you don't get any warning
This same process should work on the Moto g stylus as well I believe. May just try it when mine arrives next week
talkingmonkeys said:
This same process should work on the Moto g stylus as well I believe. May just try it when mine arrives next week
Click to expand...
Click to collapse
It's similar with other moto phones
I unlocked G6, G7, Z3 Play, Z4, and One Hyper same way
"the device will reset itself to factory default. you don't get any warning"
Do you mean a factory wipe of all data and reinstall or just default settings?
androiddiego said:
"the device will reset itself to factory default. you don't get any warning"
Do you mean a factory wipe of all data and reinstall or just default settings?
Click to expand...
Click to collapse
it will be a factory wipe, so you lose every setting and all data you have on the phone.
If you are using it actively, make a backup ( for instance with LMSA) ) prior to unlocking.
I think this has been the case sincce a long time on any android version / any brand. as soon as you unlock the boot loader, it will wipe your phone
pjottrr said:
it will be a factory wipe, so you lose every setting and all data you have on the phone.
If you are using it actively, make a backup ( for instance with LMSA) ) prior to unlocking.
I think this has been the case sincce a long time on any android version / any brand. as soon as you unlock the boot loader, it will wipe your phone
Click to expand...
Click to collapse
Thanks for the reply. Yeah, I just finally got the phone all set up so don't really want to wipe it. The only reason I want to root is to increase the color saturation. My LG V20 has a similar lcd screen. Once rooted and a kernel with Kcal, and boosting the saturation, it looks almost as good as a Samsung. Thanks for the tip on LMSA. Didn't even know what it was. That might just solve the dilemma.
Why the phone manufacturers don't give us more control over the screen is beyond me. The screens are capable.
I'm having some trouble getting the bootloader unlocked for my Moto G Power
I followed the instructions, and pasted the long string into the field on the Motorola website, but It popped up and said that my device does not qualify for unlocking. I did not purchase my phone through any carrier, but got an unlocked version via Best Buy.
Any help or suggestions on what to do next would be most appreciated!
Thanks.
Hybrid Divide said:
I'm having some trouble getting the bootloader unlocked for my Moto G Power
I followed the instructions, and pasted the long string into the field on the Motorola website, but It popped up and said that my device does not qualify for unlocking. I did not purchase my phone through any carrier, but got an unlocked version via Best Buy.
Any help or suggestions on what to do next would be most appreciated!
Thanks.
Click to expand...
Click to collapse
Did you try using the tool on the website? I used that and I got the same message, so I ended up just pasting it in and manually erasing all the extraneous text and it went through without an issue. Try that and see if it works, if not...sorry I'm all out of ideas.
HosSeagull said:
Did you try using the tool on the website? I used that and I got the same message, so I ended up just pasting it in and manually erasing all the extraneous text and it went through without an issue. Try that and see if it works, if not...sorry I'm all out of ideas.
Click to expand...
Click to collapse
Thanks for your reply.
Yes. I've tried it both ways, pasting the text, and using their scrubber tool. I'll try it again, though and report back.
EDIT: Just tried it again, and still nothing. This is maddening.
Hybrid Divide said:
I'm having some trouble getting the bootloader unlocked for my Moto G Power
I followed the instructions, and pasted the long string into the field on the Motorola website, but It popped up and said that my device does not qualify for unlocking. I did not purchase my phone through any carrier, but got an unlocked version via Best Buy.
Any help or suggestions on what to do next would be most appreciated!
Thanks.
Click to expand...
Click to collapse
Depends on which terminal you use
It it's regular command prompt, right click the top left code (make sure pound sign highlighted)
Drag to highlight the code and right click to copy
Now open the notepad and paste the code. Click the end of the line and press delete to let the next line join the current line
It should be like: 123abc#123abc#123abc#123abc#123abc#
Make 5 line into one line
Select all → copy
Paste the line and try again
I did bootloader unlock with few Moto phones this way and I had no problem
mingkee said:
Depends on which terminal you use
It it's regular command prompt, right click the top left code (make sure pound sign highlighted)
Drag to highlight the code and right click to copy
Now open the notepad and paste the code. Click the end of the line and press delete to let the next line join the current line
It should be like: 123abc#123abc#123abc#123abc#123abc#
Make 5 line into one line
Select all → copy
Paste the line and try again
I did bootloader unlock with few Moto phones this way and I had no problem
Click to expand...
Click to collapse
Thank you for your reply. I've tried that with no luck. Still get the "not qualified" error.
Hybrid Divide said:
Thank you for your reply. I've tried that with no luck. Still get the "not qualified" error.
Click to expand...
Click to collapse
Something is suspicious
Which phone service are you using?
mingkee said:
Something is suspicious
Which phone service are you using?
Click to expand...
Click to collapse
I'm using T-Mobile, but the phone was not bought through them. It's an unlocked model bought via Best Buy.
The Securestate is OEM Locked.
I should add that I do not have my SIM in the phone at this time, but that's never made a difference for me in the past.
so i was wondering, what i the state of "oem unlocking" in developer options?
is it enabled ? , can you enable it, or is it greyed out?
i found this guide but I'm not sure if it might help. it does describe multiple options for bootloader unlocking.
https://www.****************/2017/0...w-to-enable-oem-unlock-on-any-android-device/
i believe android sage is blocked . it just blocks it out aparently
then google:
pjottrr said:
so i was wondering, what i the state of "oem unlocking" in developer options?
is it enabled ? , can you enable it, or is it greyed out?
i found this guide but I'm not sure if it might help. it does describe multiple options for bootloader unlocking.
Click to expand...
Click to collapse
OEM Unlocking is enabled. I just checked to reconfirm.
I will check the link and report back. Thanks for replying.
EDIT: That link went nowhere. It appears that part of the URL was starred out.
Hybrid Divide said:
OEM Unlocking is enabled. I just checked to reconfirm.
I will check the link and report back. Thanks for replying.
EDIT: That link went nowhere. It appears that part of the URL was starred out.
Click to expand...
Click to collapse
i see, it was starred out, android sage is not allowed i guess? probably bad rep. but the info there does seem ok.
but i added my google search term to the post, and you should be able to find it .
Just don't install any software from there
pjottrr said:
i see, it was starred out, android sage is not allowed i guess? probably bad rep. but the info there does seem ok.
but i added my google search term to the post, and you should be able to find it .
Just don't install any software from there
Click to expand...
Click to collapse
I found the tutorial, but it wasn't helpful. It seems quite dated. And one of the listed commands "fastboot oem device-info" wasn't even a recognized command.
I was able to enable OEM Unlock in the developer options, get the long 5-line code in ADB Fastboot, and I can get lots of info from "fastboot getvar all", but Motorola still says my device isn't qualified for bootloader unlocking.
And I know it isn't the "Moto G8 Power" here in the US, just the "Moto G Power", but I've heard of other US users being able to unlock. What gives??
Hybrid Divide said:
I found the tutorial, but it wasn't helpful. It seems quite dated. And one of the listed commands "fastboot oem device-info" wasn't even a recognized command.
I was able to enable OEM Unlock in the developer options, get the long 5-line code in ADB Fastboot, and I can get lots of info from "fastboot getvar all", but Motorola still says my device isn't qualified for bootloader unlocking.
And I know it isn't the "Moto G8 Power" here in the US, just the "Moto G Power", but I've heard of other US users being able to unlock. What gives??
Click to expand...
Click to collapse
hmm, maybe it's time to contact lenovo / motorola and see what might be the cause of this.
they can probably figure it out
pjottrr said:
hmm, maybe it's time to contact lenovo / motorola and see what might be the cause of this.
they can probably figure it out
Click to expand...
Click to collapse
EDIT: I tried it again this morning, and it worked on my first try! Not sure what suddenly made it work, but I'm certainly not complaining! Thanks to everyone who tried to help!
I was afraid of that. I've heard them swearing up and down that devices aren't qualified to be unlocked because they're not on the list, BUT said list is old, and doesn't have anything newer than the G7 line. But I've already seen multiple G8, G Stylus, and G Power users gain their unlocks.
In case it may be helpful, below is the "fastboot getvar all" and "fastboot oem get_unlock_info" results.
Info removed, issue solved.
Hybrid Divide said:
EDIT: I tried it again this morning, and it worked on my first try! Not sure what suddenly made it work, but I'm certainly not complaining! Thanks to everyone who tried to help!
I was afraid of that. I've heard them swearing up and down that devices aren't qualified to be unlocked because they're not on the list, BUT said list is old, and doesn't have anything newer than the G7 line. But I've already seen multiple G8, G Stylus, and G Power users gain their unlocks.
In case it may be helpful, below is the "fastboot getvar all" and "fastboot oem get_unlock_info" results.
Click to expand...
Click to collapse
Check you PM