OEM Unlock Bootloader

Search This thread
By:
Advanced…
shafiq01

shafiq01

Senior Member
Oct 6, 2008
174
109
Z5C has an option now to check/un-check OEM Unlock (bootloader)
(tap mutiple times on buildnumber in 'about phone' and go to 'developer options')

But it seems very uncertain what the DRM loss is. MyXperia, maybe low light camera features? And etc.
I do not take any responsibility of any DRM loss.
 

Attachments

  • Screenshot_2015-09-14-22-49-19.png
    Screenshot_2015-09-14-22-49-19.png
    82.9 KB · Views: 16,693
  • Screenshot_2015-09-14-22-49-30.png
    Screenshot_2015-09-14-22-49-30.png
    75.3 KB · Views: 11,014
  • Screenshot_2015-09-14-22-49-38.png
    Screenshot_2015-09-14-22-49-38.png
    84.4 KB · Views: 10,967
Last edited:
  • Like
Reactions: turbo5, 1927hdiqhdg, arismelachrinos and 1 other person
thesebastian

thesebastian

Senior Member
Sep 25, 2012
1,874
445
Barcelona
Thanks for sharing this.

I take the opportunity to ask. Sony voids the warranty if you unlock the bootloader? (Like Motorola and almost every other company with the exception of Nexus/GPE devices and maybe some more).

Thanks!
 
Last edited:
I

itaq

Member
Sep 29, 2015
21
12
Here is a list of supported devices if you want to keep track.
developer.sonymobile com/unlockbootloader/unlock-yourboot-loader

I got my z5c yesterday. If I follow the step-by-step guide for z3c (because z5c is not listed, yet?) and call *#*#7378423#*#*, go to service info > configuration > rooting status, it says "Rooting status: Bootloader unlocked allowed: yes".

Continuing the process and providing a mail and then my IMEI, I received a unlock link for my Sony Xperia Z5 Compact using the Z3 Compact guide. I have not tried to use it yet but I will when I get home.
 
  • Like
Reactions: kringger, thesebastian and NPK06
I

itaq

Member
Sep 29, 2015
21
12
I tried doing it but I can connect to fastboot. With z3c, this was done like this:

1. Turn off your Xperia™ Z3 Compact.
2. Connect a USB-cable to your computer.
3. On your Xperia™ Z3 Compact, press the Volume up button at the same time as you connect the other end of the USB-cable. For Windows users, when asked for a driver, point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
4. When your device is connected, open a command window on your computer and go to the platform-tools folder within the Android SDK folder.
5. Enter the following command:
fastboot devices
6. Verify that you get an answer back without any errors.

This does not seem to apply on z5c. Any ideas?
 
lowtraxx

lowtraxx

Senior Member
Sep 20, 2007
632
1,239
Augsburg
blog.toshsoft.de
I tried and the device boots into fastboot mode just fine. It also is listed normally using
Code: 
fastboot devices
But I am too much of a coward to try
Code: 
fastboot oem unlock
because I bought the device mostly for the camera and don't want to break it.
 
M

M!tch

Senior Member
Apr 8, 2010
112
24
i hope there will be a way to root the device without losing the drm-keys (finally).
i will receive my z5c today and don't want to use it without e.g. adaway.

why is the thread starter thinking that the new developer option would affect the losing of drm-keys?
 
I

itaq

Member
Sep 29, 2015
21
12
lowtraxx said:
I turned the device off and while holding the volume up key I plugged it in. Then the blue light for fastboot lit up and I had access. Volume down and plugging it in just just very shortly lights up the green flashmode led. I hope flashing still works with flashtool.
Click to expand...
Click to collapse

Okey, so I tried what you said. I turned it off, plugged the cable in the computer, held down the volume up button and plugged in the cable in the phone. The light turned red and then blue and stayed blue. Here is what I got:
Code: 
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>fastboot devices

C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>
No output, it did not find the device. I also tried this:
Code: 
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
The computer did not find my device. I tried changing USB port and I tried doing it when the phone was on, no luck.

Did it find your device when you did
Code: 
fastboot devices
?
 
thesebastian

thesebastian

Senior Member
Sep 25, 2012
1,874
445
Barcelona
itaq said:
Okey, so I tried what you said. I turned it off, plugged the cable in the computer, held down the volume up button and plugged in the cable in the phone. The light turned red and then blue and stayed blue. Here is what I got:
Code: 
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>fastboot devices

C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>
No output, it did not find the device. I also tried this:
Code: 
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
The computer did not find my device. I tried changing USB port and I tried doing it when the phone was on, no luck.

Did it find your device when you did
Code: 
fastboot devices
?
Click to expand...
Click to collapse

Do you hear the Windows' sound when you connect your phone in Bootloader (Fastboot) mode?

If so, then you'll probably need to "manually install" the fastboot driver using the Windows "Device Manager". Selecting the .inf file from the Android SDK folder (the Extras folders where Google USB Drivers are installed). Or using the "Have Disk" option in the device manager (and then selecting the .inf file) or something like that.

Then you put "Fastboot devices" and your device should appear.
 
lowtraxx

lowtraxx

Senior Member
Sep 20, 2007
632
1,239
Augsburg
blog.toshsoft.de
Yes, I got the device listed when I did fastboot devices. I am using linux so I cannot say what the specific problem is, but as @thesebastian suggested I would guess that the fastboot driver is not installed or not installed correctly.



itaq said:
Okey, so I tried what you said. I turned it off, plugged the cable in the computer, held down the volume up button and plugged in the cable in the phone. The light turned red and then blue and stayed blue. Here is what I got:
Code: 
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>fastboot devices

C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>
No output, it did not find the device. I also tried this:
Code: 
C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
The computer did not find my device. I tried changing USB port and I tried doing it when the phone was on, no luck.

Did it find your device when you did
Code: 
fastboot devices
?
Click to expand...
Click to collapse
 
  • Like
Reactions: itaq
I

itaq

Member
Sep 29, 2015
21
12
lowtraxx said:
Yes, I got the device listed when I did fastboot devices. I am using linux so I cannot say what the specific problem is, but as @thesebastian suggested I would guess that the fastboot driver is not installed or not installed correctly.
Click to expand...
Click to collapse

That most be it. I'll look in to drivers and report back if I get it working.

---------- Post added at 05:15 PM ---------- Previous post was at 05:08 PM ----------
thesebastian said:
Do you hear the Windows' sound when you connect your phone in Bootloader (Fastboot) mode?

If so, then you'll probably need to "manually install" the fastboot driver using the Windows "Device Manager". Selecting the .inf file from the Android SDK folder (the Extras folders where Google USB Drivers are installed). Or using the "Have Disk" option in the device manager (and then selecting the .inf file) or something like that.

Then you put "Fastboot devices" and your device should appear.
Click to expand...
Click to collapse

That's it, thank you. I hear the sound when I plug it in. Checking the drives was the next thing I was going to do.
 
shafiq01

shafiq01

Senior Member
Oct 6, 2008
174
109
you would also need a code for the fastboot oem unlock command from sony dev site, right?
 
You must log in or register to reply here.

Similar threads

K
  • Poll
Bounty Z5 Lineup - Root with locked bootloader & working DRM-keys
Replies
387
Views
109K
S
schumifer
Xerwulf
Unlock Bootloader Z5 Compact
Replies
7
Views
20K
9
934573457
I
Root and bootloader unlock discussions
Replies
18
Views
13K
williamgrant
williamgrant
N
Pre-rooted 32.0.A.5.32 firmware - one-click root for unlocked BL
Replies
43
Views
35K
M
mahferer
K
Z5 Compact unlocked bootloader - problems that may occur
Replies
18
Views
5K
thesebastian
thesebastian

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    shafiq01
    shafiq01
    Z5C has an option now to check/un-check OEM Unlock (bootloader)
    (tap mutiple times on buildnumber in 'about phone' and go to 'developer options')

    But it seems very uncertain what the DRM loss is. MyXperia, maybe low light camera features? And etc.
    I do not take any responsibility of any DRM loss.
    View
    3
    I
    itaq
    Here is a list of supported devices if you want to keep track.
    developer.sonymobile com/unlockbootloader/unlock-yourboot-loader

    I got my z5c yesterday. If I follow the step-by-step guide for z3c (because z5c is not listed, yet?) and call *#*#7378423#*#*, go to service info > configuration > rooting status, it says "Rooting status: Bootloader unlocked allowed: yes".

    Continuing the process and providing a mail and then my IMEI, I received a unlock link for my Sony Xperia Z5 Compact using the Z3 Compact guide. I have not tried to use it yet but I will when I get home.
    View
    1
    lowtraxx
    lowtraxx
    I turned the device off and while holding the volume up key I plugged it in. Then the blue light for fastboot lit up and I had access. Volume down and plugging it in just just very shortly lights up the green flashmode led. I hope flashing still works with flashtool.

    itaq said:
    How did you do it? Nothing showed up for me.
    Click to expand...
    Click to collapse
    View
    1
    lowtraxx
    lowtraxx
    Yes, I got the device listed when I did fastboot devices. I am using linux so I cannot say what the specific problem is, but as @thesebastian suggested I would guess that the fastboot driver is not installed or not installed correctly.



    itaq said:
    Okey, so I tried what you said. I turned it off, plugged the cable in the computer, held down the volume up button and plugged in the cable in the phone. The light turned red and then blue and stayed blue. Here is what I got:
    Code: 
    C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>fastboot devices

C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>
    No output, it did not find the device. I also tried this:
    Code: 
    C:\Users\itaq\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
    The computer did not find my device. I tried changing USB port and I tried doing it when the phone was on, no luck.

    Did it find your device when you did
    Code: 
    fastboot devices
    ?
    Click to expand...
    Click to collapse
    View
    1
    D
    derrider
    Z5 (not compact) listed on Sony´s developer site now

    shafiq01 said:
    you would also need a code for the fastboot oem unlock command from sony dev site, right?
    Click to expand...
    Click to collapse

    As an FYI

    Sony now lists the Z5 (not compact, but should apply the same way) on their unlocking site:

    "To be able to unlock your Xperia Z5, prepare it by following these steps:
    1.Go into Settings > About phone and tap seven times on Build number to enable developer options.
    2.From Settings, go into Developer options and enable OEM unlocking"

    So it looks like this is all that´s required, no more code requesting process like on previous devices. However, nothing specific mentioned on the DRM aspect.. I have checked the option, still had "myXperia" enabled and all was good. Also, have not seen a difference in Camera quality, but would not bet on it...
    View

New posts