PS C:\adb> fastboot flashing unlock_critical
...
FAILED (remote: Unlock is not allowed on device has sales on the market!
)
finished. total time: 0.007s
PS C:\adb>
bouyhy01 said:
PS C:\adb> fastboot flashing unlock_critical
...
FAILED (remote: Unlock is not allowed on device has sales on the market!
)
finished. total time: 0.007s
PS C:\adb>
Click to expand...
Click to collapse
Bro, you have not unlock your boot loader?
chaict said:
Bro, you have not unlock your boot loader?
Click to expand...
Click to collapse
Ithought it would but i got this message , there is a guy who pretend doing it he posted a thread in this section , give it a try maybe he can do it for you
bouyhy01 said:
Ithought it would but i got this message , there is a guy who pretend doing it he posted a thread in this section , give it a try maybe he can do it for you
Click to expand...
Click to collapse
Meant your device still locked. ? That guy you mentioned hard to trust.
R
chaict said:
Meant your device still locked. ? That guy you mentioned hard to trust.
Click to expand...
Click to collapse
I left his telegram number
bouyhy01 said:
R
I left his telegram number
Click to expand...
Click to collapse
Good unlocked.. You use miunlock to do it ?
chaict said:
Good unlocked.. You use miunlock to do it ?
Click to expand...
Click to collapse
No contact him and he will do it remotely for you ,he is a proffessiinal
This will allow you to root the black shark 3 pro?
Is this working?
https://www.cyanogenmods.org/forums/topic/unlock-bootloader-black-shark-3-pro/
kamer4u said:
Is this working?
https://www.cyanogenmods.org/forums/topic/unlock-bootloader-black-shark-3-pro/
Click to expand...
Click to collapse
Tried.. wont unlock..
kamer4u said:
Is this working?
https://www.cyanogenmods.org/forums/topic/unlock-bootloader-black-shark-3-pro/
Click to expand...
Click to collapse
Can you visit the link again and try the new instructions and see if that unlocks the bootloader?
Can you run
HTML:
fastboot oem bs_unlock
and see if that unlocks the bootloader?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem bs_unlock
...
FAILED (remote: unknown command)
finished. total time: 0.004s
shibaa987 said:
Can you visit the link again and try the new instructions and see if that unlocks the bootloader?
Can you run
HTML:
fastboot oem bs_unlock
and see if that unlocks the bootloader?
Click to expand...
Click to collapse
shibaa987 said:
Can you visit the link again and try the new instructions and see if that unlocks the bootloader?
Can you run
HTML:
fastboot oem bs_unlock
and see if that unlocks the bootloader?
Click to expand...
Click to collapse
adb reboot bootloader works, the phone goes in bootloader / fastboot mode.
fastboot oem bs_unlock doesnt work.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem bs_unlock
...
FAILED (remote: unknown command)
finished. total time: 0.003s)
Damn it. Xiaomi has a real poor strategy. Indirectly it wants us to pay its employees for bootloader unlock.
Its been repeated MULTIPLE times, You can only unlock BL, using some guy in China.
need unlock via unlock.bin but the tool only chinese sell
Related
Im back with another problem im now unlocking the bootloader and i followed the instructions from [PUDDING] International House of Pudding! BL Unlock/root thread so when i go into cmd and type "fastboot oem unlock" i get this message:
<bootloader> OEM unlock is not implemented
OKAY [0.000s]
finished. total time: 0.016s
any ideas?
It seems Pudding didn't take. If my memory serves me correct, the message you received is for when the bootloader is still "encrypted". Can you give a brief "step-by-step" of what you did and what you saw on your phone while using Pudding?
carolinakidd said:
Im back with another problem im now unlocking the bootloader and i followed the instructions from [PUDDING] International House of Pudding! BL Unlock/root thread so when i go into cmd and type "fastboot oem unlock" i get this message:
<bootloader> OEM unlock is not implemented
OKAY [0.000s]
finished. total time: 0.016s
any ideas?
Click to expand...
Click to collapse
i used the instructions from here http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader and jumped to step 13 like it said in the guide cause i have 2.3.4 stock on my phone. i did what it said..got into fastboot mode, vol up to got into Fastboot protocol support mode and went into cmd found where i dl the extracted fastboot files and when i did the fastboot oem unlock i got that message on cmd
Unfortunately, that article was written before the "Official" release of gingerbread. At that time, they only had a "leaked" build that actually already had the un-encrypted bootloader. Since you have the "Official" build you will need to do all the steps.
carolinakidd said:
i used the instructions from here http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader and jumped to step 13 like it said in the guide cause i have 2.3.4 stock on my phone. i did what it said..got into fastboot mode, vol up to got into Fastboot protocol support mode and went into cmd found where i dl the extracted fastboot files and when i did the fastboot oem unlock i got that message on cmd
Click to expand...
Click to collapse
Ah well have to done tonight when I get off work lol thanks fir the info and help
Sent from my T-Mobile Atrix using xda
I do have 1 question when I do all that will I loose my sim unlock status and have to redo the unlock code?
Sent from my T-Mobile Atrix using xda
I'm almost positive you will not lose your sim unlock.
carolinakidd said:
I do have 1 question when I do all that will I loose my sim unlock status and have to redo the unlock code?
Sent from my T-Mobile Atrix using xda
Click to expand...
Click to collapse
Lol ok good looking out
Sent from my T-Mobile Motorola Atrix using xda
I did a Google search and found a bunch of results of people saying that you will not lose the sim unlock by flashing custom ROMs and doing OTA updates. SO, I'm guessing you should be safe but, as always, use caution.
carolinakidd said:
Lol ok good looking out
Sent from my T-Mobile Motorola Atrix using xda
Click to expand...
Click to collapse
*wipes brow* the operation was a success lol it jus said unlocked when it rebooted..i was kinda worried when i got the
SVF:105.1:2
Failed to boot 0X1000 error but it had a whole bunch of numbered options with it so i jus continued the fastboot process and wha-la i have a unlocked bootloader lol
Hello,
every Time i end this command
fastboot -i 0x0fce oem unlock IMEI-Number
i get this answer:
FAILED (remote: Command not allowed)
finished. total time: 0.006s
What do i wrong?
Can someone help me please?
cheers
Why don't you read official guide?
http://developer.sonymobile.com/unlockbootloader/
-i ?
check your USB-driver (if on Windows) and fastboot binary
on Windows 10?
-> http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
AndroPlus said:
Why don't you read official guide?
http://developer.sonymobile.com/unlockbootloader/
Click to expand...
Click to collapse
great help -.-
i followed these instructions before, but it didnt work
DHGE said:
-i ?
check your USB-driver (if on Windows) and fastboot binary
on Windows 10?
-> http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
Click to expand...
Click to collapse
yes -i .... its a command where sony says u must use it.
i am on windows 7
how can i check fastboot binary?
how can i check fastboot binary?
Click to expand...
Click to collapse
http://developer.sonymobile.com/downloads/drivers/
You really want to unlock the BL?
DHGE said:
http://developer.sonymobile.com/downloads/drivers/
You really want to unlock the BL?
Click to expand...
Click to collapse
yes?
i think u need it for rooting?
I don't even get to fastboot part - every time I reboot with adb reboot bootloader the tablet goes into some mode with a black screen, green led indicator and fastboot devices returning nothing.
At the same time the device is recognized by windows as something S1???? and unknown driver, and I totally failed to find a proper driver for that.
Any help will be appreciated. Btw, Windows 10 here
@XBOHDPuKC
READ this thread!
DHGE said:
@XBOHDPuKC
READ this thread!
Click to expand...
Click to collapse
Which one...
Some bootloaders are unlockable. Mine is the same way. I have to wait for a root method that does not unlock the bootloaders.
Sent from my Nexus 6
Some bootloaders are unlockable
Click to expand...
Click to collapse
= you can unlock them
to be expected with SGP712 and SGP771
Maybe with some provider branded Tablets in Japan they are "not unlockable".
interesting read (!) with a warning:
http://forum.xda-developers.com/xperia-z4/help/rooting-status-uknown-t3160932
DHGE said:
Maybe some Japanese provider branded.
But not SGP712 or SGP771. We are in the tablet forum.
Click to expand...
Click to collapse
my service menu shows bootloader as unlockable
Sent from my SGP771 using Tapatalk
I need to do a warranty exchange and my bootloader is unlocked, how can i relock it?
How can i relock it without using a USB?
Cannot relock without USB. You would need to run
fastboot oem lock
Sent from my LG-H901 using Tapatalk
Did you end up successfully locking it? Does it still display the 'unlocked' message on the logo boot screen?
-LBT- said:
Did you end up successfully locking it? Does it still display the 'unlocked' message on the logo boot screen?
Click to expand...
Click to collapse
Necro to say: YES, you can run "fastboot oem lock" to RELOCK the bootloader. "fastboot getvar unlocked" returns "unlocked: no".
Just tried it on my (two hour old) phone here.
Code:
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: no
finished. total time: 0.007s
C:\Assorted Programs\LGV10 Toolkit>fastboot oem unlock
...
OKAY [ 3.374s]
finished. total time: 3.374s
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.008s
C:\Assorted Programs\LGV10 Toolkit>fastboot oem lock
...
OKAY [ 1.764s]
finished. total time: 1.765s
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: no
finished. total time: 0.005s
hi guys
am not able to boot into bootloader to unlock it
I tried
adb reboot bootloader
and
adb reboot boot-loader
it's just making a restart
even I tired the manual way by pwr + - volume but didn't work
my model is LG-H960
any ideas!!
I'm going to be upgrading real soon and I'm stuck between the v10 and note 5. I must have root
Sent from my Nexus 6 using Tapatalk
How did you unlock the bootloader ?
melorib said:
How did you unlock the bootloader ?
Click to expand...
Click to collapse
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
KAsp3rd said:
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks, I will do it when/if I move to marshmallow
melorib said:
Thanks, I will do it when/if I move to marshmallow
Click to expand...
Click to collapse
Hi, Have you been able to Relcok it successfully? Does bootloader unlock still appears on your screen or it is gone?
Waxim1 said:
Hi, Have you been able to Relcok it successfully? Does bootloader unlock still appears on your screen or it is gone?
Click to expand...
Click to collapse
I dont think my phone bootloader was ever unlocked, at least I never noticed such message, but since I rooted in lolipop I get this funny screen everytime I reboot, even after upgrading to marshmallow
KAsp3rd said:
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks, it worked
if we relock the bootloader after doing root and debloat the stock rom, when they factory reset everything the root stay or just be gone after do the relock? are we able to unlock it again if we need TWRP?
other thing, the "cant check software for corruption" message will still appear or be gone when re-locked?
Hi guys!
A little background. I am trying to unlock the bootloader, after seeing the root status: unknown, a second time after re-flashing back to stock rom. I could unlock the bootloader perfectly fine on the first try on firmware .251 but after updating to .260, the
Code:
fastboot -i 0x0fce oem unlock 0x<key>
command keeps failing. I was trying to flash a custom rom from FreeXperia, but after several attempts of not being able to send the system.img into the tablet, I decided to re-flash to stock using Flashtool, and had selected all the option for wipe and no exclude.
Which leads to my question: Does the
Code:
fastboot getvar all
retrieves anything at all? I also tried
Code:
fastboot getvar boot
fastboot getvar version-main
but also retrieves nothing.
This is the log:
Code:
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot devices
CB5A27L24G fastboot
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar all
all:
finished. total time: 0.007s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar version-main
version-main:
finished. total time: 0.006s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar boot
boot:
finished. total time: 0.013s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x0fce oem unlock 0x<key>
...
FAILED (remote: Command not allowed)
finished. total time: 0.014s
special flash command for the large partitions
flash system like outlined here:
http://developer.sonymobile.com/kno...ocked-xperia-devices/#build-aosp-lollipop-5-1
What do you expect from the getvar command?
DHGE said:
flash system like outlined here:
What do you expect from the getvar command?
Click to expand...
Click to collapse
Hi, thanks for the reply! I was trying to get back root and unlock bootloader after splendidly failing to successfully flash a custom rom to my Z4 tablet. I was searching around Google for the remote: command not allowed error, and actually found out that some of the users actually have output for the getvar all command, which was bootloader version information and other stuff. I should also point out that I have successfully unlocked the bootloader the first time but not the second time.
Another question: Will downgrading the firmware change the rooting status in the service menu?
Edit: Will re-flashing the stock rom lock the bootloader?
Going to try the link you posted! Will report back if there's any disaster that I've made.
you better search here on XDA and not on the web
SONY devices are a bit special in terms of partitions and bootloaders:
http://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
AFAIK bootloader stays unlocked whatever you flash after unlocking and only using Flashtool or SONY PC Companoin (the latter useless for unlocked devices) you should be on the safe side.
fastboot flash ... is a bit more dangerous but I would never flash anything were I have a hunch the developer is taking too many chances and were there is no README. And it really has to be for your specific device!
Sometimes I think people complaining here have flashed obscure phone ROMs to their tablet or Wifi ROM to their LTE device or any weird pre Lollipop root tricks (there are scams easiliy found via web search).
I just tried downloading the Flashtool from Sony's website. The Emma one.
However, the program says that my bootloader is locked for some odd reason. I'm inclined to think I am in a state where I can't unlock my bootloader any more though.
I also did enable My Xperia after I reflashed the stock rom during the initial setup, but immediately deactivated it. I wonder if this is causing it to have this error.
the fora for newer Xperia devices are plastered with MyXperia "accidents"
riveria said:
I also did enable My Xperia after I reflashed the stock rom during the initial setup, but immediately deactivated it. I wonder if this is causing it to have this error.
Click to expand...
Click to collapse
Emma is useless. Does not work on our Lollipop devices. Updates of Emma seem to be automatic but no improvement. Maybe they forgot to switch off their update bot.
You bricked your device.
From SONY (READ before you do risky things!!!):
After unlocking your device, you should not enable My Xperia (found in the settings menu under security on some devices running Android 5.0) as this might cause the device to malfunction.
Click to expand...
Click to collapse
source: http://developer.sonymobile.com/unlockbootloader/
DHGE said:
Emma is useless. Does not work on our Lollipop devices. Updates of Emma seem to be automatic but no improvement. Maybe they forgot to switch off their update bot.
You bricked your device.
From SONY (READ before you do risky things!!!):
Click to expand...
Click to collapse
Oh ok, so there's no chance of me unlocking the bootloader? The device still boots up normally though.
riveria said:
Oh ok, so there's no chance of me unlocking the bootloader?
Click to expand...
Click to collapse
I do not know.
I do not think so though - if you could unlock the MyXperia Software would be no protection at all. Thieves could just unlock the BL of the stolen device and lough at SONY.
The device still boots up normally though.
Click to expand...
Click to collapse
You are lucky then - there are reports where only a repair at SONY could revive the device:
http://fxpblog.co/2015/07/03/dont-destroy-your-unlocked-device.html
DHGE said:
I do not know.
I do not think so though - if you could unlock the MyXperia Software would be no protection at all. Thieves could just unlock the BL of the stolen device and lough at SONY.
You are lucky then - there are reports where only a repair at SONY could revive the device
Click to expand...
Click to collapse
Alright! Thanks for the help! I guess no more rooting for me then. I'll try reflashing the stock rom again and see what are the results.
Reflashing doesn't change the rooting status. So a reminder to all: Don't enable My Xperia.
Hello guys I'm trying to save my bricked P20 Lite but I am running into some issues. I unlocked the bootloader using testpoint but twrp won't flash or boot. Flashing gives me a flash write failure, booting gives me a invalid command error and I can't wipe cache either. I could really use your help.
Advanced07 said:
flash write failure
Click to expand...
Click to collapse
"flash write failure" - it might be due to a locked bootloader or hardware issue, AFAIK.
Try explaining what exactly happened, step by step.
-Alf- said:
"flash write failure" - it might be due to a locked bootloader or hardware issue, AFAIK.
Try explaining what exactly happened, step by step.
Click to expand...
Click to collapse
I unlocked my bricked P20 lite bootloader with the test pin method, then I tried to flash TWRP in fastboot and I got those errors.
Advanced07 said:
I unlocked my bricked P20 lite bootloader with the test pin method, then I tried to flash TWRP in fastboot and I got those errors.
Click to expand...
Click to collapse
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Have you enabled in Developer menu
"OEM unlock" ?
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
Are you sure that bootloader is unlocked? (With unlocked BL you will see that message each time when you reboot: "Your device has been unlocked and can't be trusted").
Have you enabled in Developer menu
"OEM unlock" ?
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
1. Yes I do get that message that it's unlocked.
2. My device is bricked so that's impossible to enable. I unlocked it after it started bootlooping.
3. Gonna do those commands and tell the results
(bootloader) :ANE-LX1 9.1.0.372(C432E7R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
(bootloader) :ANE-LX1-CUST 9.1.0.7(C432)
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
What shows Fastboot screen, at the bottom, Phone unlocked and FRP unlock ?
-Alf- said:
What shows Fastboot screen, at the bottom, Phone unlocked and FRP unlock ?
Click to expand...
Click to collapse
Phone unlocked and FRP unlock.
I unlocked the phone and the frp went away but it still gave me errors. Rebooted and frp lock was back + bootloader unlock gives error
Advanced07 said:
Rebooted and frp lock was back + bootloader unlock gives error
Click to expand...
Click to collapse
as i mentioned a month ago :
-Alf- said:
IMO it might be the HW problem , dead memory or damaged motherboard
Click to expand...
Click to collapse
Probably your emmc memory is fried. Not being able to unlock BL & FRP permanently is a sure sign. But I'm just an amateur and an android fan, maybe I'm wrong.
-Alf- said:
as i mentioned a month ago :
Probably your emmc memory is fried. Not being able to unlock BL & FRP permanently is a sure sign. But I'm just an amateur and an android fan, maybe I'm wrong.
Click to expand...
Click to collapse
It does have water damage could it be because of that? That would be unfortunate.
Advanced07 said:
It does have water damage could it be because of that? That would be unfortunate.
Click to expand...
Click to collapse
- known failure due to water exposure , although the write failures are intermittent.
P.S.: since January are you trying unbrick a water damaged phone?
-Alf- said:
- known failure due to water exposure , although the write failures are intermittent.
P.S.: since January are you trying unbrick a water damaged phone?
Click to expand...
Click to collapse
Nope i already know it was dead (repairs say it was total loss) but when I saw the new unlock method I thought it might be saved. Guess I was wrong but oh well I tried anyways.
Advanced07 said:
Nope i already know it was dead (repairs say it was total loss) but when I saw the new unlock method I thought it might be saved. Guess I was wrong but oh well I tried anyways.
Click to expand...
Click to collapse
Hi i have a query, the phone that you unlocked was it running on emui 9.1? If yes did you use potato nv to unlock? I wanna try it myself
apexashwin said:
Hi i have a query, the phone that you unlocked was it running on emui 9.1? If yes did you use potato nv to unlock? I wanna try it myself
Click to expand...
Click to collapse
It was running on the latest version and yes I did use potato NV
Advanced07 said:
It was running on the latest version and yes I did use potato NV
Click to expand...
Click to collapse
Hello thanks for your quick reply,I finally managed to unlock my p20 lite using potato nv.