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.
Hi everyone
I am trying to back up my TA partition using @j4nn's tool and I successfully downgraded to 47.1.A.8.49 and archived my partition. Now I am trying to unlock my bootloader.
In the service menu, the rooting status states:
>Bootloader unlock allowed: Yes
and the "ro.oem_unlock_supported" property is set to 'True'.
However, in developer options, the toggle for OEM Unlocking is greyed out and the "ro.boot.flash.locked" property is also set to 1. Also unlocking in fastboot fails with 'command not allowed'
Has anyone encountered a situation like this where bootloader unlocking is allowed but the toggle is disabled? Is it related to downgrading to 47.1.A.8.49?
tabbed said:
Hi everyone
I am trying to back up my TA partition using @j4nn's tool and I successfully downgraded to 47.1.A.8.49 and archived my partition. Now I am trying to unlock my bootloader.
In the service menu, the rooting status states:
>Bootloader unlock allowed: Yes
and the "ro.oem_unlock_supported" property is set to 'True'.
However, in developer options, the toggle for OEM Unlocking is greyed out and the "ro.boot.flash.locked" property is also set to 1. Also unlocking in fastboot fails with 'command not allowed'
Has anyone encountered a situation like this where bootloader unlocking is allowed but the toggle is disabled? Is it related to downgrading to 47.1.A.8.49?
Click to expand...
Click to collapse
You truly got me. Just checked it on my (still locked) xz1c and I had the option greyed too, could not be enabled.
I guess it is not enabled by default unless the phone goes online on internet at least one time.
As suggested with the option, if you connect to internet, it gets enabled - just tested it.
Please post your results in the exploit thread. Thanks.
j4nn said:
You truly got me. Just checked it on my (still locked) xz1c and I had the option greyed too, could not be enabled.
I guess it is not enabled by default unless the phone goes online on internet at least one time.
As suggested with the option, if you connect to internet, it gets enabled - just tested it.
Please post your results in the exploit thread. Thanks.
Click to expand...
Click to collapse
That was it, thank you! I'll post results in the other thread.
Need Help to root Sony Xperia xz1 compact g8342 dual oreo 8.0 build number 47.1.A.2.281 kernel version 4.4.74-perf+ [email protected] #1 Baseband version 8998-8998.gen.prodQ-00147-03
I have tried every which method that I am aware of to gain root access and have been unsuccessful if anyone knows a proper proven method please give me a step-by-step walkthrough I would be very grateful
ZCustomComputers said:
Need Help to root Sony Xperia xz1 compact g8342 dual oreo 8.0 build number 47.1.A.2.281 kernel version 4.4.74-perf+ [email protected] #1 Baseband version 8998-8998.gen.prodQ-00147-03
I have tried every which method that I am aware of to gain root access and have been unsuccessful if anyone knows a proper proven method please give me a step-by-step walkthrough I would be very grateful
Click to expand...
Click to collapse
Some phones cannot be rooted.
Have you enabled OEM Unlocking in the developer options?
Have you checked that your phone can be unlocked?
Open the phone and dial *#*#7378423#*#* to access the service menu. Then look under Service info/Configuration
Rooting Status:
Bootloader unlock allowed: No
If the phone has been locked by the service provider before sending it to you, there's little you can do. Some providers do this to stop returns 'waaa, I unlocked my phone and now it's broke'
If both of these are ok, then it's most likely a driver issue, Windows10 is notorious for not installing drivers, but not giving you an error that it didn't. Boot into safe mode and use 'driver signing disabled' to get the drivers to work.
Also Windows assigns the wrong drivers by default, so connect the phone is fastboot mode, go the device manager, find the phone and manually update the driver.
You might need the Sony driver
Bootloader unlock is allowed
unlock is allowed downloaded driver will update after next attempt flickr.com/photos/[email protected]/48559170576/in/datetaken-public/
@ZCustomComputers, just backup your locked TA before unlocking the bootloader - see here for the guide.
Possibly you even would not need to reflash/downgrade stock fw to get temproot for drm keys backup as it seems you are running the supported version already.
That is a lot of information I am going to have to rehearse before I am comfortable enough to attempt all of this so as to not make a mistake I am having some other pressing matters at the moment not pertaining to anything related to these that are higher priority so I will have to come back to this at a later time in the very near future. Thank you all for your help and please do keep this thread active so I may come back to it I will return as soon as I can.
Again Thank You
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.
My rog 3 tencent version is not unlocking bootloader, bootloader is failed to unlock your device plz help me
How did you attempt to do it? Steps please.
Same issue here. Previously I was just downloading the Unlock Device app here and running it. (I already had developer options enabled) and the device would reboot but not do anything (I reckon I tried 10+ times). Since then I formatted the device and tried again and got the same results so I set the device backup normally today (running build 18.0410.2108.158) and tried it again (with and without developer options enabled as I forgot to check) and I just get a standard error message saying it couldn't unlock my device and to try again later. Same result multiple times. I don't see any option for OEM unlocking in Dev options which I see some people mention. I'm updating to the latest OS I can see in the link I provided and I will try again after installing that.
I'm updating to the latest OS I can see in the link I provided and I will try again after installing that.
Click to expand...
Click to collapse
Or not as it fails saying System update fails immediately after I select the update file and press go. :/
Qabala said:
My rog 3 tencent version is not unlocking bootloader, bootloader is failed to unlock your device plz help me
Click to expand...
Click to collapse
Hello
Your phone has already been unlocked earlier and has the flag removed. Someone blocked it again for sale.
So you won't do anything with Asus tools.
I recommend the EDL mode
Regards