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.
Related
Courtesy of Android Central, thanks for the heads up!
This is essential to get an unlocked bootloader.
https://www.youtube.com/watch?v=mp07dPusJNA&feature=youtube_gdata_player
How come they have done that?
hahaha that was awesome!
This reminds me of the taps @ Andrioid Version to get the Zombie art
Jordanooo said:
How come they have done that?
Click to expand...
Click to collapse
Because they are trying to make it a consumer phone as well as a developers phone. The average user doesn't need these settings, and could very easily mess up their phone by using them. With such an easy method to re enable them, why not do it?
jak3z said:
This reminds me of the taps @ Andrioid Version to get the Zombie art
Click to expand...
Click to collapse
And the BumbleBee in HC, the NyanDroid in ICS, and the Jellybean in JB
Tapatalk² from my Optimus V
LOL at the "now you are 3...2...1 steps to becoming a developer" xD
Google has some humor
lol at least it keeps those who don't know what they are doing from messing up their phone
mjybarr said:
This is essential to get an unlocked bootloader.
Click to expand...
Click to collapse
Sure good to know, but what does it have to do with the bootloader? I thought that to unlock bootloader, you only need to "fastboot oem unlock"?
It's unlikely that I need to change an option in the menu in order to unlock... What if I somehow screw up and can't boot, and then lock to bootloader? Stuck with a brick?
My Gnexi said:
Sure good to know, but what does it have to do with the bootloader? I thought that to unlock bootloader, you only need to "fastboot oem unlock"?
It's unlikely that I need to change an option in the menu in order to unlock... What if I somehow screw up and can't boot, and then lock to bootloader? Stuck with a brick?
Click to expand...
Click to collapse
You need to get into developer settings and activate USB debugging so you can use adb to proceed to unlock the bootloader.
Also I find the way to unlock developer settings to be quite humorous! Sadly I can see many impatient users looking to access said settings the first time be be put off by this, hopefully they will see reason!
Awwwwsome
Sent from my GT-N7100 using Tapatalk 2
mjybarr said:
Courtesy of Android Central, thanks for the heads up!
This is essential to get an unlocked bootloader.
https://www.youtube.com/watch?v=mp07dPusJNA&feature=youtube_gdata_player
Click to expand...
Click to collapse
That, my friend ,is Awesome!
The Unnamed Time Lord said:
You need to get into developer settings and activate USB debugging so you can use adb to proceed to unlock the bootloader.
Click to expand...
Click to collapse
You don't need adb to unlock the bootloader! Unlocking is done in fastboot mode, so saying "This is essential to get an unlocked bootloader" is wrong.
You can get to the bootloader (fastboot mode) by pressing the buttons during boot.
My Gnexi said:
You don't need adb to unlock the bootloader! Unlocking is done in fastboot mode, so saying "This is essential to get an unlocked bootloader" is wrong.
You can get to the bootloader (fastboot mode) by pressing the buttons during boot.
Click to expand...
Click to collapse
Your wrong my friend.
http://forum.xda-developers.com/showthread.php?t=1972508
Read step 5 in the link above ^^
Sent from my HTC VLE_U using Tapatalk 2
The guide is wrong.
Never mind.
Hello,
mjybarr said:
Your wrong my friend.
http://forum.xda-developers.com/showthread.php?t=1972508
Read step 5 in the link above ^^
Click to expand...
Click to collapse
Please read this reply by efrant:
http://forum.xda-developers.com/showpost.php?p=33727130&postcount=27
efrant said:
This is not just directed at the OP:
I think people should wait until they get a hold of the device before posting guides and directing others on what to do. Unless you actually try something and it works, I wouldn't be posting any guides.
Just to clarify some mis-information in this thread:
1) You do not need to install the SDK (and you do not need it to install the driver) -- the SDK is just a bunch of stuff that, unless you are developing, you will never need;
2) The driver for the N4 may not even be included in the SDK -- the GNex driver certainly wasn't;
3) For the fastboot driver to install (and for fastboot commands to work), your device must be booted in fastboot mode;
4) USB Debugging is a feature of Android, and to use it, you have to be booted into Android -- it has nothing to do with the bootloader;
5) Currently, there is no exploit to gain root on any build of Android higher than 4.1.1, so, there is no way to gain root without unlocking the bootloader at this time.
Click to expand...
Click to collapse
Also, 2 responders above in the same page say that.
Also, it doesn't make sense to me that fastboot's operation will check an option that is selected while you are in the OS.
If someone that has the device can check it then great, until then I'll assume USB Debugging is NOT needed to unlock bootloader.
it is well-known that the bootloader of SO-02K is often unlockable.
with little knowledge of sony devices,i bought a SO-02K mistakenly.
i tried my best to provide any thought to unlocked it.
after a lot of research work i found a software that isn't free and it's really expensive when compared with the price of SO-02k.
the software is called qunlocked tool.
sourcepage:
带vmp壳的qunlocktool - 『脱壳破解讨论求助区』 - 吾爱破解 - LCG - LSG |安卓破解|病毒分析|www.52pojie.cn
从万能的群友那里弄到一份工具，说能解锁某尼手机，解锁一次要接近200块钱首先查壳打开软件点击check credits然后就根据bad username，OD载入，跟随401000删除分析 ... 带vmp壳的qunlocktool ,吾爱破解 - LCG - LSG |安卓破解|病毒分析|www.52pojie.cn
www.52pojie.cn
this software could be downloaded here:
qUnlockTool.exe - 蓝奏云
文件大小：3.7 M|
topjohnwu.lanzous.com
the software first check the credits with the server and if the account had the credits,which is sold about $25 per credit,then will calculate a unlockcode for the device,and then unlocked the device.
i didn't pay for it,since i had no acess to either google or paypal.
there is a old chinese proverb goes that "wan neng de tao bao",which means you could pay to someone on the web site Taobao.com to solve almost anything, so i just turn to it.
form one advertisement i found the process of the software,which is also mentioned in the source page.
i found that the unlocked code calculated by the software is simply "1234567890ABCDEF",which is too easy to be an unlock code.
i tried to unlock my own phone with the code,but it failed.
i guess the software may have 2 ways to unlock xperia phones:
1:the fastboot itself provides the ways to use extra functions defined by manufactors,which won't be shown with just simple command line like "fastboot -h",e,g :"fastboot oem unlock"
maybe the sony had define 2 functions like "fastboot oem unlock","fastboot oem unlock2",then they uses "fastboot oem unlock" to verify whether you had the right,if yes,then turn to "fastboot oem unlock2" to do the real process of bootloader unlock.
2:the software had do something to my phone ,cheated my phone to recognize the fake code.
maybe someone would help?
hupengwei said:
maybe someone would help?
Click to expand...
Click to collapse
@hupengwei
The tool is legit? What was the bootloader unlock status before "Bootloader unlock allowed: No"? One thought on the alternate fastboot unlock command is a value known as remoteUnlock. You could extract the .exe with 7zip to further unravel the unlocking commands utilized along with decompiling other files code (if neccessary). Have an XZs that could benefit from this as it is currently "Bootloader unlock allowed: No"
I
&(*) said:
@hupengwei
The tool is legit? What was the bootloader unlock status before....
Click to expand...
Click to collapse
In fact I donn know either the software is legit nor how the software works.i just guess it may work in 2 ways.in fact it is not only the fastboot.exe provided by Sony but also any fastboot.exe works.
I'll try the remote unlock command,but could kindly tell me how you get the commands?
hupengwei said:
I
In fact I donn know either the software is legit nor how the software works.i just guess it may work in 2 ways.in fact it is not only the fastboot.exe provided by Sony but also any fastboot.exe works.
I'll try the remote unlock command,but could kindly tell me how you get the commands?
Click to expand...
Click to collapse
I didn't get the command from the bootloader; there is a value that is stored on some phones in the device info known as RemoteUnlockState. Finding all the commands for the bootloader will require digging through Qualcomm's documentation and/or finding something that has been leaked indicating other commands able to be used. My guess isn't neccessarily correct, but I think you are right, there are other commands that allow rooting the device and those commands must have some other context that can be found withing a module or system (i.e. SELinux).
$25 to unlock a device thought to be unlockable. I'd have paid already to find out.
SXUsr said:
$25 to unlock a device thought to be unlockable. I'd have paid already to find out.
Click to expand...
Click to collapse
Here's the thread with the info to do so. Post your experience, feedback, results, and device used.
&(*) said:
Here's the thread with the info to do so. Post your experience, feedback, results, and device used.
Click to expand...
Click to collapse
My post is directed at owners of a SO-02K.
Did it work?
The tool works. I already unlocked a bunch of Japan locked Xperia phones. i.e XZ3, 5, 1 .
I tried to install Android 12 Developer Preview 3 on my Pixel 5 via OTA Sideload but it failed at 94% with the message 'adb: failed to read command: No error' on cmd and 'Install from ADB completed with status 0' on phone.
After this when I try to boot, I get the following message: 'Can't find valid operating system. The device will not start.' (attached image)
I'm able to access the bootloader but when I tried going into recovery mode through the bootloader, it shows the same message: 'Can't find valid operating system. The device will not start.'
Seems like the recovery is corrupted as well.
Unfortunately I had not enabled OEM unlocking in the developer options before trying to install the Developer Preview, which is now not letting me unlock the bootloader.
Please help me fix the issue or help me find a way to unlock the bootloader without enabling OEM unlock.
Thanks in advance.
I had the same thing happen to me just now. Have you managed to figure anything out?
Nothing from my side, since bootloader is locked I can't flash the system image and I can't unlock bootloader because my OEM unlock is turned off in developer settings and the Recovery and Rescue mode are also corrupted.
I contacted Google support and their only solution was to bring it in for service as my device is still under warranty.
I'm in the same boat here with a Pixel 4a 5G. Got to 94%.
First time I've experienced an issue while sideloading. . .
Contacted google support and they are shipping me a refurbed replacement... disappointed, to say the least.
Not sure what to make of this, it's developer preview and now beta. Issues will possibly occur and it warns you of such.
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As an additional this let me get my phone back to loading the custom ROM I was on, to then reenable debugging mode, I then rebooted back into fastboot mode and used Googles online factory restore mode to flash stock ROM back on and I was back up and running
leddra3k said:
**Possible Fix**
I would believe this might be due to the boot_a & boot_b when trying other custom ROMs or OTA updates.
I used the fastboot/ADB files from the lineageOS ROM page and used the command: fastboot flashing unlock
to unlock the bootloader again, this then allowed me to go back into the rescue mode and use googles online image reinstall and got me back onto the stock ROM. Hope this helps some people
Click to expand...
Click to collapse
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
k7nanjappan said:
As I had mentioned earlier: I had NOT enabled OEM unlocking in the developer options before trying to install the Developer Preview.
So this method does not work for me. It will be helpful if I can find a way to force unlock the bootloader somehow.
Thank you for your reply. Hope your method helps someone else resolve their issue.
Click to expand...
Click to collapse
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
leddra3k said:
This might not work but have you tried plugging the phone into the computer using the pixel online factory recovery and tried the first step of the process which is a prompt to unlock the boatloader?
Click to expand...
Click to collapse
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
V0latyle said:
I'm going to state what should be obvious here - you should not attempt to use pre-release firmware with a locked bootloader, because you will ne severely limited on what you can do to recover if something goes wrong.
Unlocking the bootloader is not possible if OEM Unlocking is not enabled.
What exactly are you referring to? The Android Flash Tool requires an unlocked bootloader to start with, and does not unlock the bootloader itself.
Click to expand...
Click to collapse
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
leddra3k said:
Are you not aware of the Google online tool for their Pixel phones? https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
I am aware. However, this tool does not function like adb and is not meant for flashing factory images like the Android Flash Tool is. The Pixel Repair Tool works specifically from Rescue Mode.
leddra3k said:
This has additional flashing options within the 'online' version of fastboot/adb, and found that when trying locally downloaded adb/fastboot it didnt work. But when using the online version it allowed me to unlock the phones boatloader.
Click to expand...
Click to collapse
It sounds like your Platform Tools may be out of date. Current version is 31.0.3, Aug '21.
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
Buying it "unlocked" means you bought it free of a carrier, such as Verizon, who lock the bootloader, and can't be unlocked.
But you still need to unlock the bootloader, it comes locked, for security reasons. So if you never unlocked it, it's locked.
I haven't installed beta 12 yet.
Do you have the latest SDK tools? (adb, fastboot, etc)
I was under the impression though, that you can't downgrade with a locked bootloader. But not sure.
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
This probably isn't of any help now, but going forward, it may be. In Developer options, you can enable 'OEM unlocking'. As you can see now, it may well be a very good idea to enable that **before** you start messing with the phone, because if something does go wrong (as it has for you), then you can (hopefully) still get to fastboot and do 'fastboot flashing unlock'.
So, knowing this, you may want to keep an eye out for some tool or something that will allow you to possibly turn on oem unlocking (because your device won't boot).
Another thing to try is switching slots and see if the other slot boots? If you can get to fastboot try; fastboot --set-active=(a or b), then fastboot reboot. (If you don't know which slot is active, do 'fastboot getvar all', in the output it will tell you which is current.
cheers
Your bootloader being locked should not affect your ability to restore factory images/OTAs from Google. They are signed by Google and will pass the signature checks. You should try to download the latest factory image (either 11 or 12beta) and flash it via recovery => adb sideload.
Hey guys,
I've searched the forum but nobody seems to have reported the issue I'm experiencing. The way the posts are worded, unlocking the Tab S8+ is a given. I know the US S22 has no OEM Unlocking officially supported. I've followed all the workarounds to get the option to appear to no avail.
My only theory is that VZW hasn't yet unlocked my S8+ (if it was ever locked to begin with, nevertheless I've owned it less than 60 days). Can anybody confirm if this model can be bootloader unlocked by conventional means either prior or after carrier unlock?
Hi! I'm going to try to find the other user's post who enlightened me in this section, but I might have trouble finding it.
Effectively, no U.S. carrier's version of previous and current Samsung Galaxy Tabs can have the bootloader unlocked - at least that's what I remember them telling me. You have to buy the Wi-Fi only version to be able to unlock the bootloader.
Now - SIM unlock, I know nothing about on the Tabs. Normally no matter what U.S. carrier, that I'm aware of, once you pay off your device (if financed), they'll SIM unlock the device, and although you can relate the two things (SIM and bootloader unlocking), they are completely separate and it's only certain U.S. phones (not Samsung phones or tablets) that getting SIM unlock enables you to also do OEM unlocking, and therefore be able to unlock the bootloader.
Verizon never allows the bootloader to be unlocked on any kind of device, no matter what, and all U.S. Samsung carrier devices - both phones and tablets, are never able to get their bootloader unlocked. I'm not including the rare exception that there's a hack to be able to get root - but most hacks circumvent the locked bootloader - they don't often actually allow the bootloader to be unlocked, and this sort of thing is rarer and rarer anymore.
Edit: I believe this is the post, by @googlephoneFKLenAsh.
Thank you for your thorough explanation. I was expecting the Tab to be the same situation as with the U.S. Galaxy phones, I just wasn't able to find confirmation of that.
I know Verizon is hostile to bootloader unlocking (case in point Pixel). So it was either gonna be my carrier and if not that my region.
Tablets do on rare occasion are exceptions (iirc ATT doesn't carrier lock tablets) so barring an explanation elsewhere I figured I'd post and have that question answered for myself and those concerned.
I don't understand the motivation behind it given that unlocking is already a process that can't be exploited by malware/spyware and carries a myriad of drawbacks/risks.
GlitterFartzz said:
... given that unlocking is already a process that can't be exploited by malware/spyware and carries a myriad of drawbacks/risks.
Click to expand...
Click to collapse
You're welcome!
I'm not sure I understand what you're saying here, or I'm not sure if you meant to say it differently.
An unlocked (or unlockable) bootloader can definitely be exploited without our awareness.
I agree that I don't understand the motivation - at least in contrast to AT&T and T-Mobile which apparently do allow bootloaders to be unlocked once their phones are paid for and SIM unlocked. I also don't know why or if AT&T and T-Mobile would not allow Samsung tablets to be bootloader-unlocked while allowing other brands.
Overall I think the motivation is the prevention of potentially more problems that users will have and also potentially brick their device and then they wind up with an unhappy customer because the carrier won't consider the device under warranty since it had been fiddled with in a way they're not willing to support (understandably).
Additionally, root malware would potentially be using their mobile network for nefarious purposes.
GlitterFartzz said:
Hey guys,
I've searched the forum but nobody seems to have reported the issue I'm experiencing. The way the posts are worded, unlocking the Tab S8+ is a given. I know the US S22 has no OEM Unlocking officially supported. I've followed all the workarounds to get the option to appear to no avail.
My only theory is that VZW hasn't yet unlocked my S8+ (if it was ever locked to begin with, nevertheless I've owned it less than 60 days). Can anybody confirm if this model can be bootloader unlocked by conventional means either prior or after carrier unlock?
Click to expand...
Click to collapse
I have the same s8+ 5G model and I'm unable to get to the unlock option from download mode. I have however managed to turn on the OEM unlock from android. It is very fiddly to get to the OEM unlock option, and it will disappear afterward. The method I used is to quickly go to the developer's options before the tablet fully started after a reboot. It will let you toggle the OEM unlock.
I'm waiting if someone found a way to get the bootloader unlock from download mode. Obviously I have tried all other methods ( e.g> cable + up+down volume )
It's actually not possible to unlock via download mode. Download mode is only used for Odin flashing and the like.
You have to get to the bootloader which I believe is power and vol up WITHOUT using the cable afaik.
If by some catastrophic reason you can't get into the bootloader after that, you can boot the device, enable USB debugging, plug into pc, and run adb reboot bootloader or adb reboot recovery.
killerzac said:
I have the same s8+ 5G model and I'm unable to get to the unlock option from download mode. I have however managed to turn on the OEM unlock from android. It is very fiddly to get to the OEM unlock option, and it will disappear afterward. The method I used is to quickly go to the developer's options before the tablet fully started after a reboot. It will let you toggle the OEM unlock.
I'm waiting if someone found a way to get the bootloader unlock from download mode. Obviously I have tried all other methods ( e.g> cable + up+down volume )
Click to expand...
Click to collapse
Have you been able to get the OEM unlocking switch to reappear after you've already toggled it?
If so, is it still on when it reappears? If it is then there's a high likelihood the device can then be unlocked.
GlitterFartzz said:
Have you been able to get the OEM unlocking switch to reappear after you've already toggled it?
If so, is it still on when it reappears? If it is then there's a high likelihood the device can then be unlocked.
Click to expand...
Click to collapse
yes, it remains as OEM unlocked. I even tried to see if this could be false positive by flipping OEM unlock back and forth. It has shown the setting is persistence, if you set OEM unlock it will stay unlock. If you set it back to OEM lock. It stays as OEM lock.
GlitterFartzz said:
It's actually not possible to unlock via download mode. Download mode is only used for Odin flashing and the like.
You have to get to the bootloader which I believe is power and vol up WITHOUT using the cable afaik.
If by some catastrophic reason you can't get into the bootloader after that, you can boot the device, enable USB debugging, plug into pc, and run adb reboot bootloader or adb reboot recovery.
Click to expand...
Click to collapse
nope, doesn't work. I tried ADB reboot bootloader or use the recovery to boot to bootloader, still no joy. I just can't get to the bootloader option which allows me to see the "Unlock bootloader options"
killerzac said:
nope, doesn't work. I tried ADB reboot bootloader or use the recovery to boot to bootloader, still no joy. I just can't get to the bootloader option which allows me to see the "Unlock bootloader options"
Click to expand...
Click to collapse
You are supposed to boot into bootloader mode and then use the fastboot tool to trigger the unlock.
Either fastboot flashing unlock or fastboot oem unlocking. Something like that.
GlitterFartzz said:
You are supposed to boot into bootloader mode and then use the fastboot tool to trigger the unlock.
Either fastboot flashing unlock or fastboot oem unlocking. Something like that.
Click to expand...
Click to collapse
yes, that is not working ( bootloader mode - doesn't let you choose ). Fastboot doesn't work with samsung, they deliberately change their code, try it yourself.
GlitterFartzz said:
You are supposed to boot into bootloader mode and then use the fastboot tool to trigger the unlock.
Either fastboot flashing unlock or fastboot oem unlocking. Something like that.
Click to expand...
Click to collapse
These are the necessary steps on this tablet to unlock the bootloader - it doesn't involve Fastboot from the Platform Tools. I am aware that on standard Android/AOSP that it does involve Fastboot since for my phones I choose Google Pixel devices.
skrowl said:
Step 1 - Prepare your Tablet (only necessary for first install on unrooted device)
While Frija is downloading the firmware, prepare your device by doing the following:
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Turn on OEM unlocking
NOTE: If the OEM Unlocking option doesn't appear, connect the device to the internet, wait a few minutes, then try again
Power tablet completely off (Hold volume down + power button if you haven't changed the Bixby settings)
While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
Press and hold volume up for 5 seconds, the screen will change to a confirmation prompt
Press volume up again to confirm, the tablet will reboot
Unplug your tablet from USB
Go through initial setup. Don't bother copying files or installing anything.
Skip signing in to your Google account and Samsung account. You won't be using them for this step.
Settings > About Tablet > Software Information > Click Build Number 7 times quickly
Developer Options (just below About Tablet on the left column)
Turn on USB Debugging
Reboot the tablet
Click to expand...
Click to collapse
roirraW edor ehT said:
These are the necessary steps on this tablet to unlock the bootloader - it doesn't involve Fastboot from the Platform Tools. I am aware that on standard Android/AOSP that it does involve Fastboot since for my phones I choose Google Pixel devices.
Click to expand...
Click to collapse
Ah I wasn't aware that some devices do not require fastboot to finalize unlock and instead immediately unlock when toggling OEM Unlocking.
Is it possible to confirm the unlock by getting the bootloader vars using fastboot however?
Alternately, what's the easiest way to confirm the bootloader is unlocked?
killerzac said:
yes, that is not working ( bootloader mode - doesn't let you choose ). Fastboot doesn't work with samsung, they deliberately change their code, try it yourself.
Click to expand...
Click to collapse
According to this post, you should have your bootloader unlocked now. Could you try following the instructions listed and report back?
Could you also explain in more detail how you can get the OEM unlocking option to appear?
I seem to be having no luck. You do own a US model, correct?
roirraW edor ehT said:
These are the necessary steps on this tablet to unlock the bootloader - it doesn't involve Fastboot from the Platform Tools. I am aware that on standard Android/AOSP that it does involve Fastboot since for my phones I choose Google Pixel devices.
Click to expand...
Click to collapse
GlitterFartzz said:
Ah I wasn't aware that some devices do not require fastboot to finalize unlock and instead immediately unlock when toggling OEM Unlocking.
Is it possible to confirm the unlock by getting the bootloader vars using fastboot however?
Alternately, what's the easiest way to confirm the bootloader is unlocked?
Click to expand...
Click to collapse
Actually, although the instructions don't make it clear without the context of seeing what's on the screen, steps 5 through 7 are what unlock the bootloader. OEM Unlocking still only (normally) enables unlocking the bootloader:
5. While holding volume up and volume down, plug the tablet into your PC via USB
Let go of volume keys as soon as the blue-green screen shows up
6. Press and hold volume up for 5 seconds, the screen will change to a confirmation prompt
7. Press volume up again to confirm, the tablet will reboot
Click to expand...
Click to collapse
Also, just as on the Google Pixel and many or all other devices, the easiest way to see that your bootloader is unlocked is the (IMHO) big honking stupid advertisement when you reboot or turn on your device that the bootloader is unlocked and the (paraphrasing) "hey thieves, if you just stole this device, you're in luck because you can hack into someone's account easier since this device's bootloader is unlocked" that stays on the screen seemingly forever.
I know that if they're actually technically savvy they'd be able to find that out anyway, but all this forced pre-boot screen does is punish those who unlock their bootloader. End Rant.
Ah I see what you mean, so It's been stated that US devices either resist BL unlocks e entirely or require alternative solutions.
That being said, has there been reports of UI bugs causing the option to appear on USA models under certain circumstances?
roirraW edor ehT said:
Actually, although the instructions don't make it clear without the context of seeing what's on the screen, steps 5 through 7 are what unlock the bootloader. OEM Unlocking still only (normally) enables unlocking the bootloader:
Also, just as on the Google Pixel and many or all other devices, the easiest way to see that your bootloader is unlocked is the (IMHO) big honking stupid advertisement when you reboot or turn on your device that the bootloader is unlocked and the (paraphrasing) "hey thieves, if you just stole this device, you're in luck because you can hack into someone's account easier since this device's bootloader is unlocked" that stays on the screen seemingly forever.
I know that if they're actually technically savvy they'd be able to find that out anyway, but all this forced pre-boot screen does is punish those who unlock their bootloader. End Rant.
Click to expand...
Click to collapse
GlitterFartzz said:
That being said, has there been reports of UI bugs causing the option to appear on USA models under certain circumstances?
Click to expand...
Click to collapse
No. I've read every post in this section starting from when I pre-ordered mine (February?), and the only post I've seen about being able to enable OEM Unlocking was from @killerzac.
Too bad that doesn't easily lead to actually being able to unlock, even if the OEM Unlocking aspect was widely reproducible.
killerzac said:
yes, that is not working ( bootloader mode - doesn't let you choose ). Fastboot doesn't work with samsung, they deliberately change their code, try it yourself.
Click to expand...
Click to collapse
Have you found a solution?
I'm in such a weird place. I'm in the UK my first Tab S8 Ultra unlocked originally but after relocking the bootloader I can't get the OEM Unlock to reappear. I needed an unlocked tablet so I bought another one and this one has never had the OEM Unlock option. Waited many sets of 7 days trying different Samsung accounts and Google accounts. I do notice like you that if you get to dev options quickly after boot OEM Unlock is there but it definitely hasn't loaded properly at this point and changing it does nothing. Tablet never gives the bootloader unlock option when you go through the process.
The only thing ive noticed is on both devices the KG Status is Active (Viewed in Download Mode). My S22 which has the OEM Unlock option shows it as inactive. Samsung have told me that I can send the tablet to them and they will look at it but I can't be without it at the moment. Don't know if both my tablets are wrongly reporting that they are in finance and MDM is locking it potentially following my Samsung account to the new tablet I bought.
Really annoyed with Samsung now spent hours on web chats with them where they keep making you reset the tablet and won't escalte it.
Even more annoying they won't look at my first tablet because it did unlock initially so the warrenty is void now that it won't unlock they have said they will replace the mainboard for £800.
@Jono0907 That really sucks! I'm sorry to hear about all the trouble. I "swear" - customer service these days. Someday, companies will just stop even having the (mostly) nearly useless customer service that they do now, and they just won't have any at all.
Jono0907 said:
Have you found a solution?
I'm in such a weird place. I'm in the UK my first Tab S8 Ultra unlocked originally but after relocking the bootloader I can't get the OEM Unlock to reappear. I needed an unlocked tablet so I bought another one and this one has never had the OEM Unlock option. Waited many sets of 7 days trying different Samsung accounts and Google accounts. I do notice like you that if you get to dev options quickly after boot OEM Unlock is there but it definitely hasn't loaded properly at this point and changing it does nothing. Tablet never gives the bootloader unlock option when you go through the process.
The only thing ive noticed is on both devices the KG Status is Active (Viewed in Download Mode). My S22 which has the OEM Unlock option shows it as inactive. Samsung have told me that I can send the tablet to them and they will look at it but I can't be without it at the moment. Don't know if both my tablets are wrongly reporting that they are in finance and MDM is locking it potentially following my Samsung account to the new tablet I bought.
Really annoyed with Samsung now spent hours on web chats with them where they keep making you reset the tablet and won't escalte it.
Even more annoying they won't look at my first tablet because it did unlock initially so the warrenty is void now that it won't unlock they have said they will replace the mainboard for £800.
Click to expand...
Click to collapse
Hi Jono,
I haven't look at it since and I'm pretty sure your finding is very much same as mine, Quote "Table never gives the bootloader unlock option". I gave my s8+ to my 5 years old son as his toy now. Piece of garbage without ROOTing for me. I'm reverting back to using my tabS6. You might hapend to see me on the northen line with my TabS6, very rare scene.