Related
Hello guys,
I have this phone and is the developer edition. What can I do with is phone?
Is this phone Unlocked for other networks such as t-mo?
My phone is from ATT but I was wondering if it comes unlocked as well. I know is boot loader unlocked but will like to know if I can use it with tmo since my phone got disconnected.
Thanks guys
Sent from my MB886 using XDA Premium
SVLAN said:
Hello guys,
I have this phone and is the developer edition. What can I do with is phone?
Is this phone Unlocked for other networks such as t-mo?
My phone is from ATT but I was wondering if it comes unlocked as well. I know is boot loader unlocked but will like to know if I can use it with tmo since my phone got disconnected.
Thanks guys
Sent from my MB886 using XDA Premium
Click to expand...
Click to collapse
OMG!!!
Is this the developer edition with an unlockable bootloader!!!!????
We have been looking for one of these.
If you help the community, we will surly help you.
So why don't you go over to http://forum.xda-developers.com/showthread.php?t=2145602
Just do the following instructions and I will help you to see if it is unlocked.
MAKE SURE TO PM ME THE FILES!!!
Do not post or motorola will detect that it is you and will do bad things (IDK what, but you don't want it to happen)
Thank you for joining our community.
Cheers and Hope you enjoy your atrix hd dev edition!!!
I was told is the Developer Edition when I got it from ATT since at that time they had both versions bro. The unlocked bootloader I got it from the net on some searches I did that the Developers Editions are boot loader unlocked. How can I check this? To make sure is what you guys need?
So u got this from the AT&T stores?
It might not be a dev edition,
But...
go here (never know): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a and follow the steps until it says either your not qualified or not and tell us what it does.
I hope this is a dev edition...
Hello bro Im trying to get the Devise ID but I dont get that part right there mate
Code:
TO GET YOUR DEVICE ID
Put your device in fastboot mode (press the power button and volume down button at the same time and connect your device to your computer with a USB cable).
On your computer, open a command prompt or Terminal session.
Go to the Directory where you installed the Android SDK tools, and type:
$ fastboot oem get_unlock_data
I get this error when trying to get the Devise ID
Code:
C:\Users\aSolis\AppData\Local\Android\android-sdk>$ fastboot oem get_unlock_data
'$' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\aSolis\AppData\Local\Android\android-sdk>
SVLAN said:
Hello bro Im trying to get the Devise ID but I dont get that part right there mate
Code:
TO GET YOUR DEVICE ID
Put your device in fastboot mode (press the power button and volume down button at the same time and connect your device to your computer with a USB cable).
On your computer, open a command prompt or Terminal session.
Go to the Directory where you installed the Android SDK tools, and type:
$ fastboot oem get_unlock_data
I get this error when trying to get the Devise ID
Code:
C:\Users\aSolis\AppData\Local\Android\android-sdk>$ fastboot oem get_unlock_data
'$' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\aSolis\AppData\Local\Android\android-sdk>
Click to expand...
Click to collapse
You should type fastboot oem get_unlock_data without "$".
huatz84 said:
You should type fastboot oem get_unlock_data without "$".
Click to expand...
Click to collapse
nope, I have tried many different things and is actually not comunicating with the phone I believe
Is there a way I can start the server first just to make sure is comunicating?
also from what folder I open the Command promt?
from the main folder or from the platforms-tools folder?
sorry but Im new to this phone and is making mad already. lol
You can try a simple fastboot tool HERE. Just extract the zip and copy the fastboot folder to root dir C. Then,open cmd and type cd C:\fastboot. And the command to get device ID : moto-fastboot oem get_unlock_data. I used this simple fastboot to unlock Photon,Atrix and Xoom bootloader. It should work fine on AHD.
SET UP TEAMVIEWER between tcf38012 & SVLAN. That is the best way do it quickly and correctly.
Otherwise this can only end in frustration and disappointment :/
that worked perfectly mate and thank you but unfortunaly it does not qualify for bootloader unlock
So you don't have a dev edition. Damn Lol.
sent from my JokerMATRIX HD MAXX
SVLAN said:
that worked perfectly mate and thank you but unfortunaly it does not qualify for bootloader unlock
Click to expand...
Click to collapse
Can you give a screenshot of the cmd result?
Sent from my DROID4 using Tapatalk 2
Dang false alarm.
Go and demand a refund from AT&T. They told me it had an unlockable bootloader also .
Those assholes.
lyers :|.
Dear all,
I have an issue that has dazzled me for a few days ..
I have a 4.2.2 Kitkat HTC one google play edition and would like to install a custom rom.
The first step should be to unlock its bootloader
I've gone through the online tutorial and did exactly what is needed .
1) Loaded into fastboot mode
2) fastboot oem get_identifier_token
3) I received the token and pasted it in HTCdev and got back the unlock_code.bin file
4) entered fastboot flash unlock token Unlock_code.bin in the terminal ..
This is supposed to trigger my phone to display the "Unlock Bootloader?" screen, as attached ... and this is not happening
I have all drivers installed properly and my phone has responded to the fastboot oem get_identifier_token command
but there is no screen displayed .. only the fastboot mode .
What should I do?
Appreciate any help you can give
rabeeh80 said:
Dear all,
I have an issue that has dazzled me for a few days ..
I have a 4.2.2 Kitkat HTC one google play edition and would like to install a custom rom.
The first step should be to unlock its bootloader
I've gone through the online tutorial and did exactly what is needed .
1) Loaded into fastboot mode
2) fastboot oem get_identifier_token
3) I received the token and pasted it in HTCdev and got back the unlock_code.bin file
4) entered fastboot flash unlock token Unlock_code.bin in the terminal ..
This is supposed to trigger my phone to display the "Unlock Bootloader?" screen, as attached ... and this is not happening
I have all drivers installed properly and my phone has responded to the fastboot oem get_identifier_token command
but there is no screen displayed .. only the fastboot mode .
What should I do?
Appreciate any help you can give
Click to expand...
Click to collapse
I though for the GPE you only needed to fastboot OEM unlock.
jawmail said:
I though for the GPE you only needed to fastboot OEM unlock.
Click to expand...
Click to collapse
It didn't work .. I guess it doesn't work for 4.2.2 .. Not sure ..
Thanks
rabeeh80 said:
It didn't work .. I guess it doesn't work for 4.2.2 .. Not sure ..
Thanks
Click to expand...
Click to collapse
Unlocking the bootloader on GPe 4.2.2 is not possible any more. Also if you have an unlocked bootloader from before 4.4.2 OTA, don't ever relock cause you will not be able to unlock again. Google removed the partition that had the unlock splash screen. I have tried. The only way to unlock it is to find a signed 4.3 GPe RRU and downgrade. So if you are not rooted and S-on a signed RRU is our only hope! There is way to unlock if you are rooted or S-off.
Sent from my HTC One using xda app-developers app
Unfortunately you can NOT run a signed RUU to downgrade. This is going to have to come as a patch/update from google now
rabeeh80 said:
Dear all,
I have an issue that has dazzled me for a few days ..
I have a 4.2.2 Kitkat HTC one google play edition and would like to install a custom rom.
The first step should be to unlock its bootloader
I've gone through the online tutorial and did exactly what is needed .
1) Loaded into fastboot mode
2) fastboot oem get_identifier_token
3) I received the token and pasted it in HTCdev and got back the unlock_code.bin file
4) entered fastboot flash unlock token Unlock_code.bin in the terminal ..
This is supposed to trigger my phone to display the "Unlock Bootloader?" screen, as attached ... and this is not happening
I have all drivers installed properly and my phone has responded to the fastboot oem get_identifier_token command
but there is no screen displayed .. only the fastboot mode .
What should I do?
Appreciate any help you can give
Click to expand...
Click to collapse
This is really pain in ass. I am contacting both HTC and Google support for this. You can read it here
http://forum.xda-developers.com/showthread.php?t=2547894
Sent from my HTC One using Tapatalk
Thanks for your replies ..
I have to say that I now hate my phone .. I moved from IOS because I wanted the freedom of customizing my phone and installing ROMs and now I'm stuck
I thought a pure Google edition phone will be the least restrictive version of Android. .
I should have chosen the Sense 5.5 one ..
Hey everyone really need some assiat,help,guide, or any resources to make my device Unlocked.As i'm not a new guy on this stuff, also this is my second times having this ivy (Z3+) used to be the single sim variants and now with the Dualsim Variants,. Today i decided to unlock the bootloader after i've backing up the TA partitions with IOVYTools, so i do checked the bootloader status with *#*#7378423#*#* so its clearly said Allowed, then all i need is head to sony developer site to pull the secret codes unlock, received the email and put the imei numbera inside and ta daa the secret code comes up , put the devices into fastboot mode, and try to copy that codes but failed ,okay perhaps i need to type that codes manualy and i type with 5times checked that the codes/commad was correct but same result its FAILED,downgrading to some firmware and upgrading even to the latest one really not even help, same error Failed remote command not allowed, CRAP i give up so i put the thread/post here hoping someone or anyone here can tell me where i'm wronged?? I put some pictures here so everyone can see the situations i have.
SH1M4BD3 said:
Hey everyone really need some assiat,help,guide, or any resources to make my device Unlocked.As i'm not a new guy on this stuff, also this is my second times having this ivy (Z3+) used to be the single sim variants and now with the Dualsim Variants,. Today i decided to unlock the bootloader after i've backing up the TA partitions with IOVYTools, so i do checked the bootloader status with *#*#7378423#*#* so its clearly said Allowed, then all i need is head to sony developer site to pull the secret codes unlock, received the email and put the imei numbera inside and ta daa the secret code comes up , put the devices into fastboot mode, and try to copy that codes but failed ,okay perhaps i need to type that codes manualy and i type with 5times checked that the codes/commad was correct but same result its FAILED,downgrading to some firmware and upgrading even to the latest one really not even help, same error Failed remote command not allowed, CRAP i give up so i put the thread/post here hoping someone or anyone here can tell me where i'm wronged?? I put some pictures here so everyone can see the situations i have.
Click to expand...
Click to collapse
Download Flashtool from this link install it, run it and follow the bootloader unlock process, enter the code received from sony and unlock it.
For patched kernel, recovery and other things, check the following thread
https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
[email protected] said:
Download Flashtool from this link install it, run it and follow the bootloader unlock process, enter the code received from sony and unlock it.
For patched kernel, recovery and other things, check the following thread
https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
Click to expand...
Click to collapse
not its dioes not work sir, even with imei 2 the result failed (remote: Command not allowed), can i just root and flashing twrp and flash the custom rom like LOS??
SH1M4BD3 said:
not its dioes not work sir, even with imei 2 the result failed (remote: Command not allowed), can i just root and flashing twrp and flash the custom rom like LOS??
Click to expand...
Click to collapse
How is that supposed to work if the Bootloader is locked ?
Make sure you have USB debugging enabled
It is probably only a minor oversight that hinders it from succeeding
Also remove the screenshots( too much info)
SH1M4BD3 said:
not its dioes not work sir, even with imei 2 the result failed (remote: Command not allowed), can i just root and flashing twrp and flash the custom rom like LOS??
Click to expand...
Click to collapse
You need to create a text file called ulcode.txt containing the unlock code you received from Sony. Then put this file in a folder with your device (phone) name (eg. My device name is CB5A2B7CSV yours should be something similar. You can get the name using fastboot command devices. I see the name of your device in the first line of the third image you posted above!). Then put this folder inside the following path (create the necessary folders):
C:\users\your defult user name\.flashTool\mydevices
Then unlock your bootloader using flash tool. It will take your unlock code from the above mentioned text file and asks for permission for unlocking and will unlock the bootloader smoothly.
Good luck
hai guys i tried to unlock bootloader by official sony method by selecting xperia xz(because xz1c not listed) and got my unlock code by my imei,but when i hit the unlock command ,its not working, can someone please help me to unlock my bootloader i am on the version(47.1.a.8.49), one more doubt is as iam on the latest version(1st december 2017 security patch) does the twrp for the older security patch works for my version,because i didnt find the proper twrp for the latest security patch
jinishpv said:
hai guys i tried to unlock bootloader by official sony method by selecting xperia xz(because xz1c not listed) and got my unlock code by my imei,but when i hit the unlock command ,its not working, can someone please help me to unlock my bootloader i am on the version(47.1.a.8.49), one more doubt is as iam on the latest version(1st december 2017 security patch) does the twrp for the older security patch works for my version,because i didnt find the proper twrp for the latest security patch
Click to expand...
Click to collapse
Did you enable OEM unlocking in the developer options?
You know you're going to lose you camera right? I mean no pictures whatsoever.
No I'm not sure TWRP is working for December update yet.
You can't flash old version TWRP with new 47.1.A.8.49
Didgesteve said:
You know you're going to lose you camera right? I mean no pictures whatsoever.
Click to expand...
Click to collapse
There's actually a recently released DRM fix, which reportedly fixes the camera: https://forum.xda-developers.com/xp...lopment/oreo-xz1c-drmfix-root-ricoff-t3727029
Didgesteve said:
No I'm not sure TWRP is working for December update yet.
Click to expand...
Click to collapse
modpunk just updated TWRP with December security patch: https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
BetaLyte said:
There's actually a recently released DRM fix, which reportedly fixes the camera: https://forum.xda-developers.com/xp...lopment/oreo-xz1c-drmfix-root-ricoff-t3727029
modpunk just updated TWRP with December security patch: https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Click to expand...
Click to collapse
My mistake, it's only been out a day so I hadn't spotted it.
Looks like there's some success on the thread, but I'll hold back a bit before I jump.
Didgesteve said:
Looks like there's some success on the thread, but I'll hold back a bit before I jump.
Click to expand...
Click to collapse
Yeah, me too. sToRm// is taking a look at it, at will include it in XperiFix. But it's still important to notice, that it's a fix, and not a DRM backup / restore solution, so the original TA partition / DRM keys will still be lost and won't be recoverable.
BetaLyte said:
Yeah, me too. sToRm// is taking a look at it, at will include it in XperiFix. But it's still important to notice, that it's a fix, and not a DRM backup / restore solution, so the original TA partition / DRM keys will still be lost and won't be recoverable.
Click to expand...
Click to collapse
Yes, it's a one way step and you're reliant on the developer bringing a new version of the fix each time there's a firmware update.
No offence to the developer, but I know nothing of M-Rom or aledoom, it would be good to know a little of their background before I open my phone to some software from a unkown forum.
Since nobody bothered to give an answer...
1. Go to the Sony Bootloader Unlock page here
2. Follow the steps for the Xperia XZ
3. Get the email, click the link, type in your IMEI
4. Follow the instructions on the page.
lokio27 said:
Since nobody bothered to give an answer...
1. Go to the Sony Bootloader Unlock page here
2. Follow the steps for the Xperia XZ
3. Get the email, click the link, type in your IMEI
4. Follow the instructions on the page.
Click to expand...
Click to collapse
It looks more like you didn't bother to read OP's post.
He has already done all that, he's asking why the unlock command isn't working.
Unfortunately, up until recently, unlocking the bootloader on this phone is extremely unappealing, so like almost no one has tried unlocking it, and those who did probably didn't run into this problem, so no one was able to offer an actual answer.
The first reply actually provided some suggestions. If you bothered to read.
mhaha said:
It looks more like you didn't bother to read OP's post.
He has already done all that, he's asking why the unlock command isn't working.
Unfortunately, up until recently, unlocking the bootloader on this phone is extremely unappealing, so like almost no one has tried unlocking it, and those who did probably didn't run into this problem, so no one was able to offer an actual answer.
The first reply actually provided some suggestions. If you bothered to read.
Click to expand...
Click to collapse
I couldn't find any help anywhere when I was looking for help on that, so I felt like a post was needed in general.
problem solved
tried bootloaderunlock on my desktop pc and it worked,flashed latest twrp ,flashed drm fix every thing is working fine,anyone had sucess in magisk and viper4android?
jinishpv said:
tried bootloaderunlock on my desktop pc and it worked,flashed latest twrp ,flashed drm fix every thing is working fine,anyone had sucess in magisk and viper4android?
Click to expand...
Click to collapse
Hi, I have maybe the same issue :
Code:
fastboot -i 0x0fce oem unlock 0xMyKey
returns only
Code:
...
and seems stuck : nothing happens.
So I would like to unlock my bootloader, but I cannot manage to do it (of course *#*#7378423#*#* then Service info > Configuration > Rooting Status Bootloader unlock allowed says Yes).
How did you manage to unlock your bootloader?
OldBeurt said:
How did you manage to unlock your bootloader?
Click to expand...
Click to collapse
I did not find a proper solution. It is still impossible to unlock my XZ1c with my laptop. Fortunately, I did manage to unlock it using my (very) old former laptop (it’s 32 bits, I had to use the old ADB v23), and it worked like a charm.
I don’t know why it failed on my current laptop (either with my usual OS Linux, nor with Windows 10).
Old thread is old? i don't care. because i want to say that looks like Sony finally give the XZ1c into the data base and there is a hot to guide over the Dev mode of the Phone. i will past the Sony guide to it here so this info will spread where it needed:
"To be able to unlock your Xperia XZ1 Compact, prepare it by following these steps:
Go into Settings > About phone and tap seven times on Build number to enable developer options.
From Settings, go into Developer options and enable OEM unlocking.
Warning:
Camera stops working on certain software releases.
Device protection features will not work on this device while this setting is turned on. Note: It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialer and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
"
Source: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
/€: Again, you guys are way to deep into the matter and i found several things that was never mention by any tutorial.
after several testings and also failings i will add: under windows 10, you have to check the Drivers double and make sure you use one that works!
EVEN IF IT APPEARS THAT THE DRIVER IS CORRECT IT MAY NOT THE CASE!
To check this you have to use "ADB DEVICES" and "FASTBOOT DEVICES".
Only if your device appears in the list IN BOTH (!) cases the driver setting is correct. This is very important.
Also you have to consider that after reboot into bootloader ("adb reboot bootloader") the device will NOT RECOGNIZE (!) by windows and appears as new device without any driver! (check Device Manager for this) so you can't access it in that state EVEN it was recognized before!
You have to install the Google Android USB Driver in this case. Also you have to check if the device appears still in both (adb, fastboot) lists.
Only then you can preform the Guides correctly!
summary: you have to install two (!) driver to get proper access to your device, one driver can only be installed in a certain state of your device (bootloader state) you have to make sure that your device is accessible in all states to preform your unlocking AND img pushing correctly.
Your bootloader is unlocked if on Power up the message appears "Your device has been is unlocked and can't be trusted. Your device will boot in 5 seconds"
...and now i go and found a way to get rid of the "non access on external cards for apps" _feature_ ...ands no all the tools and images and guides DON'T WORK.
muhschaf said:
To check this you have to use "ADB DEVICES" and "FASTBOOT DEVICES".
Only if your device appears in the list IN BOTH (!) cases the driver setting is correct. This is very important.
Click to expand...
Click to collapse
So how did you manage to work this out? I have this exact problem. When the phone is in fast mode (volume up) it shows in the "fastboot devices" but not in the "adb devices". When it's turned on it does show up in "adb devices" but (obviously) not in fastboot devices...
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere. I'm tried to unlock the bootloader (settings, show it's possible) for 5h and haven't managed to do it yet... I'm really thinking about sending it back, this is just too annoying... please please help me...
mosbyxz1c said:
So how did you manage to work this out? I have this exact problem. When the phone is in fast mode (volume up) it shows in the "fastboot devices" but not in the "adb devices". When it's turned on it does show up in "adb devices" but (obviously) not in fastboot devices...
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere. I'm tried to unlock the bootloader (settings, show it's possible) for 5h and haven't managed to do it yet... I'm really thinking about sending it back, this is just too annoying... please please help me...
Click to expand...
Click to collapse
Have you checked that your phone can be unlocked?
Some providers sell phones that can't be unlocked so that they don't have to deal with the warranty mess.
Open your phone and type *#*#7378423#*#* - then look under Service info\Configuration under Rooting status it should say Bootloader unlock allowed: Yes
If it says No, then you need to stop, there is no way round this.
Didgesteve said:
Have you checked that your phone can be unlocked?
Some providers sell phones that can't be unlocked so that they don't have to deal with the warranty mess.
Open your phone and type *#*#7378423#*#* - then look under Service info\Configuration under Rooting status it should say Bootloader unlock allowed: Yes
If it says No, then you need to stop, there is no way round this.
Click to expand...
Click to collapse
I bought it straight from amazon without any carriers but yes it is allowed (that's what I meant with "settings show it's possible", sorry if that was unclear).
I just double checked, just to be 100% sure. And yes:
Rooting status:
bootloader unlock allowed: Yes
mosbyxz1c said:
I bought it straight from amazon without any carriers but yes it is allowed (that's what I meant with "settings show it's possible", sorry if that was unclear).
I just double checked, just to be 100% sure. And yes:
Rooting status:
bootloader unlock allowed: Yes
Click to expand...
Click to collapse
Presumably you've enabled OEM unlocking in the developer options?
Otherwise it's a driver problem, good luck with that.
mosbyxz1c said:
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere.
Click to expand...
Click to collapse
I got the same problem, I just removed the "-i 0x0fc" part, so it became "fastboot oem unlock 0x<insert your unlock code>".
I think there may be a newer version of fastboot that lacks the -i option.
Nerre said:
I got the same problem, I just removed the "-i 0x0fc" part, so it became "fastboot oem unlock 0x<insert your unlock code>".
I think there may be a newer version of fastboot that lacks the -i option.
Click to expand...
Click to collapse
Thanks for trying to help.
Got a little hopeful but now i get a
Code:
FAILED (remote: Command did not succeed)
I'm going crazy... I'm really thinking about setting up a dualboot linux (or boot from usb). you guys think thats useful? I have no problems with drivers at least. If yes, ubuntu enough? I don't have a lot of linux experience..
mosbyxz1c said:
So how did you manage to work this out? I have this exact problem. When the phone is in fast mode (volume up) it shows in the "fastboot devices" but not in the "adb devices". When it's turned on it does show up in "adb devices" but (obviously) not in fastboot devices...
As it is, when i try the "fastboot -i 0x0fce oem unlock 0x<insert your unlock code>" it tells me that it doesn't know command -- i. I have found nothing about this problem at all. nowhere. I'm tried to unlock the bootloader (settings, show it's possible) for 5h and haven't managed to do it yet... I'm really thinking about sending it back, this is just too annoying... please please help me...
Click to expand...
Click to collapse
Your mention of "Volume up" button indicates that your try to reboot it per button pressing. Try to avoid that. Your device should reboot by typing in the fast boot command and press enter. then you have to check the driver state in the Device manager and their install the correct driver (Google ADB driver). Don't unplug your Phone during this.
I bought a secondhand Sony XZ2 AU version. When I try to unlock the bootloader using command prompt, it'll say the command isn't allowed. When I use flashtool to unlock the bootloader, it'll give me java error.
Are you sure you have ADB installed correctly on that computer? If so, are you navigating to your ADB folder in CMD before you execute the command?
TypicalNoob said:
I bought a secondhand Sony XZ2 AU version. When I try to unlock the bootloader using command prompt, it'll say the command isn't allowed. When I use flashtool to unlock the bootloader, it'll give me java error.
Click to expand...
Click to collapse
It can be unlocked using qunlock tools. You need to pay around 30$ . I am using AU version sony xz2. I unlocked the boot loader and now using lineage os.
XDARoni said:
Are you sure you have ADB installed correctly on that computer? If so, are you navigating to your ADB folder in CMD before you execute the command?
Click to expand...
Click to collapse
I have installed ADB from XDA and Google, both don't work
Japan version usually not allowed bootloader to be unlocked.
Have you check your phone is allowed?
Go to : *#*#7378423#*#*
Then Select Service Menu, then select configuration. You'll see something like this.
If you see unlocked allowed : NO, then try this
https://forum.xda-developers.com/t/...ed-no-to-yes-is-now-finally-possible.4044091/
But prepare some money for it.
hibikase said:
Japan version usually not allowed bootloader to be unlocked.
Have you check your phone is allowed?
Go to : *#*#7378423#*#*
Then Select Service Menu, then select configuration. You'll see something like this.
If you see unlocked allowed : NO, then try this
https://forum.xda-developers.com/t/...ed-no-to-yes-is-now-finally-possible.4044091/
But prepare some money for it.
Click to expand...
Click to collapse
Have you tried unlocking bootloader using those website, and if so is it trustable?
TypicalNoob said:
Have you tried unlocking bootloader using those website, and if so is it trustable?
Click to expand...
Click to collapse
I'm not use that website. I was ask person as same with my country to buy credit for qunlock tools as mentioned up there. Then execute it by myself.