Related
hi all,
i have recently aquired Sony Xperie SP C5303, and i now i'm lost since i never had android phone. all i used was various emulators for PC and stuff...
but now there is many stuff to be noisy about. and probably this has been answered many times but please, do me a favor and pretty please answer again if possible.
1. Phone is SIM locked (i'm working on getting unlock code from provider, since i have right to do so, after contract expires..which has)..but is there any way to unlock phone before i get the code? i'm wondering how technitians in local services do that. they ask about 30€ for unlocking device, and i doubt they have acces to provider's unlock code.
2. I tried to flash phone with custom firmware (using flashtool) but it failed on me even though i used right firmware, and phone bricked. however i managed to recover phone with sony PC companion and it now works same as when i got it. Firmware 12. 1. A. 1. 205, android version 4.3. i have no idea why it failed on me during flash. can it be cause phone is no rooted, and have no root support? (whill connect to this on 3.) do i have to root phone before flashing? i would really like to have root access.
3. i was unable to do hard reset of phone with power + volume down button. or any other trick didn't work. i couldn't not enter android recovery options. i followed instruction on how to root my phone on
Code:
developersonymobile(dotcom)/unlockbootloader/unlock-yourboot-loader/
. i entered
Code:
*#*#7378423#*#*
to check if my device is unlockable, it says boot loader unlock allowed : No. Does this mean i won't be able to have root acces on my phone? or i still have to learn difference between terms or what they mean.
also is that really true what they warn about that there is no turning back after i root phone and all. won't just hard reseting phone or repair device with all defaults troubh pc sofware bring back and vipe everything back? how will than service know if phone has been rooted ever?
thank you in advance for all your answers.
"Bootloader unlock allowed : No" <= this means you can't use UBL ROMs or custom kernels.
You can always root and use LBL ROMs though. There are plenty of LBL ROMs out there to try.
You can always un-root your phone. And you can always repair your phone's OS by flashing the Stock ROM via flashtool. Doing so would remove root access as well, no one would know you ever rooted.
Root using towelroot.
Get recoveries by Dssmex.
Then flash LBL ROMs, mods, ports etc. that you want.
and Be careful when you flash anything,
Read the threads, don't try to flash any UBL ROM as it may brick your device.
First thank you for helping.
UBL is unlocked boot loader right? and L is locked. sorry to doubt your last tip but i need to double check was it typo or...? you said don't flash UBL. isnt that supposed to say don't flash LBL. or i have totally got this wrong. maybe i don't know what what's LBL and UBL.
but just to be safe? where can i find stock ROM? i tried official site, they don't let me download firmware manualy. only trough sony PC companion automatic repiar. Which is ok too i guess. else i can download sony flash tool callsed emma, but i cannot get login info since they need about 7 days to approve my registration.
so my first step is to root my phone. ok i will do that. i might do it manualy, not trough application though.
what about sim lock? after i root phone, is there sim unlock command or what? and do i need code...how do you unlock your phone to be able to use other SIM.
IrethTassartir said:
First thank you for helping.
UBL is unlocked boot loader right? and L is locked. sorry to doubt your last tip but i need to double check was it typo or...? you said don't flash UBL. isnt that supposed to say don't flash LBL. or i have totally got this wrong. maybe i don't know what what's LBL and UBL.
but just to be safe? where can i find stock ROM? i tried official site, they don't let me download firmware manualy. only trough sony PC companion automatic repiar. Which is ok too i guess. else i can download sony flash tool callsed emma, but i cannot get login info since they need about 7 days to approve my registration.
so my first step is to root my phone. ok i will do that. i might do it manualy, not trough application though.
what about sim lock? after i root phone, is there sim unlock command or what? and do i need code...how do you unlock your phone to be able to use other SIM.
Click to expand...
Click to collapse
Welcome.
And no, I did mean "Don't flash UBL ROMs"
UBL = Unlocked Bootloader
LBL = Locked Bootloader
The ROMs that are made for Unlocked Bootloaders are UBL ROMs.
Unlocked Bootloader users can use both LBL and UBL ROMs.
But since your device's Bootloader cannot be unlocked, you can only use LBL ROMs.
It's written in almost all ROM threads if it's a LBL or an UBL ROM. But if it isn't specified, then be sure it's UBL. (Like all 5.1 ROMs are for UBL)
Download stock ftf from here.
Use Flashtool v0.9.18.5
and I can't say about the last one as I don't use a carrier locked device.
Try and see what happens.
thank you again for reply. you've been very helpfull with all info.
Zenith said:
Download stock ftf from (link deleted, i'm not allowed to post it)
Click to expand...
Click to collapse
that is exactly from where i got it the first time. also same flashtool version. after i tried to use that firmware, my phone bricked.
even though it's stock ROM, probably cause my phone had locked bootloader (i finally found article on what is bootloader and i got it now).
but after this, i have used sony software to recover my phone and it works again.
now important stuff. so my device's bootloader cannot be unlocked. does that 100% means that i'm stuck with locked bootloader and no way of getting it unlocked.
even on sony offical site there is process tutorial how to unlock bootloader, and it says "if you device isn't listed, than you cannot unlock bootloader".
but it IS listed and I AM able to get the unlock code for it. now i'm confused. can i still do the process showed?
another confusing thing is where i read about bootloader, it says that for to be able to root i need to flash custom ROM, and to do that i need to unlock bootloader.
but you have provided link for "towelroot" which was able to get my phone root acces. is it different from rooting my phone manualy after unlocking bootloader. how did it manage to root it anyway? and with towelroot it still has bootloader locked. actually it says "boot loader unlock allowed: NO!". now begs the question does that mean, not allowed, but i can be unobidient one and still unlock it without clearance, or does it mean .."you're stuck with locked bootloader. deal with it!. if you try to unlock bootloader your phone will brick"!.
i think after i get answer to this, than it would be my last question for this topic
also again, thank you for answering all previous questions...and this one, hopefully
IrethTassartir said:
thank you again for reply. you've been very helpfull with all info.
that is exactly from where i got it the first time. also same flashtool version. after i tried to use that firmware, my phone bricked.
even though it's stock ROM, probably cause my phone had locked bootloader (i finally found article on what is bootloader and i got it now).
but after this, i have used sony software to recover my phone and it works again.
now important stuff. so my device's bootloader cannot be unlocked. does that 100% means that i'm stuck with locked bootloader and no way of getting it unlocked.
even on sony offical site there is process tutorial how to unlock bootloader, and it says "if you device isn't listed, than you cannot unlock bootloader".
but it IS listed and I AM able to get the unlock code for it. now i'm confused. can i still do the process showed?
another confusing thing is where i read about bootloader, it says that for to be able to root i need to flash custom ROM, and to do that i need to unlock bootloader.
but you have provided link for "towelroot" which was able to get my phone root acces. is it different from rooting my phone manualy after unlocking bootloader. how did it manage to root it anyway? and with towelroot it still has bootloader locked. actually it says "boot loader unlock allowed: NO!". now begs the question does that mean, not allowed, but i can be unobidient one and still unlock it without clearance, or does it mean .."you're stuck with locked bootloader. deal with it!. if you try to unlock bootloader your phone will brick"!.
i think after i get answer to this, than it would be my last question for this topic
also again, thank you for answering all previous questions...and this one, hopefully
Click to expand...
Click to collapse
Did you install the drivers properly (Flashmode, fastboot, viskan common) ?
You need to disable driver signature verification before installing drivers if you're on Win 8/8.1/probably 10 too.
And flashtool should work perfectly in both LBL and UBL phones.
You said your service menu says, "Bootloader unlock allowed : No"
Even if you get a BL unlock code you can't unlock it coz it's not allowed.
And by messing with the bootloader or trying to flash UBL ROMs may permanently brick your phone.
And different phones have different rooting processses. Rooting our SP is easier than most other phones by TowelRoot.
And "Bootloader unlock allowed : No" is more like a "You're stuck with locked bootloader. deal with it!. If you try to unlock bootloader your phone will brick!".
And you can still use a lot of LBL ROMs, from 4.3 to 5.0. So don't worry Lol.
Welcome
i did install fastboot and drivers and everything acording to tutorial. i payed attention on par "pay attention to this. be sure to install drivers correctly, lol"
i'm using win 7 64bit sp1. i have disabled UAC. i'm alaways running as admin. as for flashtool. software works perfectly..it just fail flashing.
it goes to part where i need to unplug phone and plug in holding volume something button..it says on poppup. than i plug in phone and it starts flasshing..it goes up to 40% something percent. if finish few files but when it comes to system.(something) i forgot extension, it says failed. flasshing stopped. than after that i can't turn on phone again.
i couldn't untill i recovered via Sony PC companion. i did try to flash it several times with several roms. i think it's cause my provider messed with bootloader. they locked it together with sim. on official sony site. it says:
"Note! Even if your device is listed here, certain releases of the device model may not be supported due to operator restrictions. Please select your device on the Start tab to check if your particular device can be unlocked."
anyway, i even got my provider's firmware trough flashtool download system, got my provider's name and exact same firmware that was installed. it still failed on same file.
than after i recovered i didn't try to flash anymore. i don't even know what's the point, if i can have root access without it.
i'm not so keen on installing other android version, unless this one gives me problem. for that i need to unlcok phone first to be able to even use it or test it so far it's has been t urned off most of the time
IrethTassartir said:
i did install fastboot and drivers and everything acording to tutorial. i payed attention on par "pay attention to this. be sure to install drivers correctly, lol"
i'm using win 7 64bit sp1. i have disabled UAC. i'm alaways running as admin. as for flashtool. software works perfectly..it just fail flashing.
it goes to part where i need to unplug phone and plug in holding volume something button..it says on poppup. than i plug in phone and it starts flasshing..it goes up to 40% something percent. if finish few files but when it comes to system.(something) i forgot extension, it says failed. flasshing stopped. than after that i can't turn on phone again.
i couldn't untill i recovered via Sony PC companion. i did try to flash it several times with several roms. i think it's cause my provider messed with bootloader. they locked it together with sim. on official sony site. it says:
"Note! Even if your device is listed here, certain releases of the device model may not be supported due to operator restrictions. Please select your device on the Start tab to check if your particular device can be unlocked."
anyway, i even got my provider's firmware trough flashtool download system, got my provider's name and exact same firmware that was installed. it still failed on same file.
than after i recovered i didn't try to flash anymore. i don't even know what's the point, if i can have root access without it.
i'm not so keen on installing other android version, unless this one gives me problem. for that i need to unlcok phone first to be able to even use it or test it so far it's has been t urned off most of the time
Click to expand...
Click to collapse
I see.. I'm not actually sure why Flashtool isn't working.
Anyways some good 4.4.4 LBL ROMs are 'CM11 by Bagyusz', 'Omni-X by NeildownX', PA etc.
Try them if you want.
Zenith said:
I see.. I'm not actually sure why Flashtool isn't working.
Anyways some good 4.4.4 LBL ROMs are 'CM11 by Bagyusz', 'Omni-X by NeildownX', PA etc.
Try them if you want.
Click to expand...
Click to collapse
can i use flashtool to install CM11 by Bagyusz. on CM11 thread, under tutorial it says enter recovery mode..i can't do that. nothing happens when i power up+volume down ..or up..or any other combination. i installed clockwork mod, but i cannot install cwm recovery sincy my device is not listed. if i try to restart phone in recovery mode, nothing happens! it just restarts phone normaly!
IrethTassartir said:
can i use flashtool to install CM11 by Bagyusz. on CM11 thread, under tutorial it says enter recovery mode..i can't do that. nothing happens when i power up+volume down ..or up..or any other combination. i installed clockwork mod, but i cannot install cwm recovery sincy my device is not listed. if i try to restart phone in recovery mode, nothing happens! it just restarts phone normaly!
Click to expand...
Click to collapse
I assume you're now on a rooted stock ROM.
Follow this to get recoveries.
Reboot, when you see the Blue LED burn, press vol down to enter TWRP recovery.
can i use cm-11-20150822-UNOFFICIAL with flashtool so i avoid installing recoveris or CWMP?
flashtool worked for me it just gave me an error during flashing one of the files....that might be cause i didn't know difference between LBL roms and UBL roms. maybe problem was incorrect rom type for my phone.
i tried to install recovery tools. and i had some problems...when i swhitched on phone there was no light showdown,,just red led...and after phone entered safe mode. but not in recovery menu.
i sure have no idea what to do...now everything is so strange.
to be honest i'm considering dropping this whole thig of and use stock rom as it is...
it would be cool if there would be automatic debloat application which will remove all bloatware...
or at least bloatware list of apps i can delete manually, without loosing important function on my phone. than i would not need custom rom!
IrethTassartir said:
can i use cm-11-20150822-UNOFFICIAL with flashtool so i avoid installing recoveris or CWMP?
flashtool worked for me it just gave me an error during flashing one of the files....that might be cause i didn't know difference between LBL roms and UBL roms. maybe problem was incorrect rom type for my phone.
i tried to install recovery tools. and i had some problems...when i swhitched on phone there was no light showdown,,just red led...and after phone entered safe mode. but not in recovery menu.
i sure have no idea what to do...now everything is so strange.
to be honest i'm considering dropping this whole thig of and use stock rom as it is...
it would be cool if there would be automatic debloat application which will remove all bloatware...
or at least bloatware list of apps i can delete manually, without loosing important function on my phone. than i would not need custom rom!
Click to expand...
Click to collapse
If you're on CM11 by Bagyusz, Open Terminal Emulator and enter the following codes,
su
./system/bin/recovery.sh
^ it will give you access to recovery when you see the red LED while booting.
If you decide to go back to stock, you can freeze/remove these apps.
I made the list when I was on stock. Take a backup before removing them just to be safe.
thank you a lot! this has all been so helpful!
IrethTassartir said:
thank you a lot! this has all been so helpful!
Click to expand...
Click to collapse
Welcome
I wanted to share my experience with working with a T-MO G4 (H81120i) that I had rooted, unlocked the bootloader, and had a custom ROM. My goal was to return it to stock so that I can turn it in(to jump). I tried:
The 2014 LG Flash tool. It failed out multiple times with a "Cannot connect to server" error.
LG Bridge tool which failed multiple times too. The device was not recognized.
LGUP which was reccommended by someone. I have no idea how you would flash or restore wit hthat tool. So, that was a dead end.
So, what worked?
I downloaded the flashable complete zip for the stock t-mo G4(20i) and then left it at that. Its still showing bootloader unlocked on startup so I asm wondering about setting going into fastboot and OEM locking or relocking. The question is...is this last step necessary?
gpmartinson said:
I wanted to share my experience with working with a T-MO G4 (H81120i) that I had rooted, unlocked the bootloader, and had a custom ROM. My goal was to return it to stock so that I can turn it in(to jump). I tried:
The 2014 LG Flash tool. It failed out multiple times with a "Cannot connect to server" error.
LG Bridge tool which failed multiple times too. The device was not recognized.
LGUP which was reccommended by someone. I have no idea how you would flash or restore wit hthat tool. So, that was a dead end.
So, what worked?
I downloaded the flashable complete zip for the stock t-mo G4(20i) and then left it at that. Its still showing bootloader unlocked on startup so I asm wondering about setting going into fastboot and OEM locking or relocking. The question is...is this last step necessary?
Click to expand...
Click to collapse
its only if you want to send to LG... so they wont noticed it was bootloader unlocked.... if you relock it will you .. take a video of it...
someone claim it can be relocked... mines locked... so if it can be relocked then i would unlock it..
but it will be nice to see a video that it can be done...
http://forum.xda-developers.com/tmobile-g4/help/relock-bootloader-h811-t3372970
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Still stucked?
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse
Salik Iqbal said:
Still stucked?
Click to expand...
Click to collapse
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.
Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Cesarisg said:
I have a Moto X First Gen XT1058, it had 5.1, then I upgraded with LineageOS to 6.0, it had some issues so I wanted to get back to 5.1, so I downgraded to 4.2.2 and then installed the OTA update, while rebooting after the install, my phone got full bricked, would not respond until I managed to get it into bootloader with a tutorial, but now I can't do anything pass that.
In the bootloader menus says:
Failed to hab check for gpt_main: 0x4e
CID Read Failure
Invalid CID status 0x69
Custome ID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
USB Connected
I am running fastboot 30.BE, I am trying to get the bootloader unlocked but everytime I try to get the "fastboot oem get_unlock_data" and get the error message "bootloader could not get unlock data".
I've tried almost 5 different adb tools, and drivers, I've read about 50+ post and tried all the commands , tried rsd but it wont flash gpt, maybe I haven't found the right post, but after several hours of research I running out of ideas, what can I try, what am I doing wrong?
Click to expand...
Click to collapse
Cesarisg said:
Sadly yes, I haven't figured out, I can't unlock bootloader, I can't flash a rom without unlocking bootloader, I've tried 5.1, 4.2.2 and 4.4.4, none of them work without unlocking bootloader, RSD Lite wont work, gets fail message, I'm really running out of ideas, still reading lots of threads from all over the world, even translating some foreign languages.
Click to expand...
Click to collapse
Salik Iqbal said:
Download this:
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Make sure your battery is charge enough, and you are getting battery ok, unrar the folder, and flash the . xml from rsd lite, hope your device boot again.
Best of luck.
Click to expand...
Click to collapse
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.
I am ARSH and Iive in india if some one is having brazzers membership p lzz give me for one day p lzz share with me my e-mail [email protected] plzzzzzz
No problem..
Cesarisg said:
OH WOW, it worked, I tried dozens of gpt files and none of them worked, THANK YOU so much!!, saved my butt from buying a new phone, I will retire from flashing my moto x, stock rom for ever.
Click to expand...
Click to collapse
I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.
mwaterbu said:
I'm glad your phone is working again. Just curious, what were the issues you had with LOS 13 (ghost)?
I've been considering putting that on my phone, but would hold off or find another option if something won't work right. I'm still on stock 5.1.
Click to expand...
Click to collapse
There was 2 main reasons why I had to go back to stock, the main one was that the OS would not let me uninstall any app, I tried everything I read online to try to fix it, even flashing the rom again, nothing work and the other reason was the phone app would not let me hear from the earpiece, it got fixed after getting back to 5.1 and many other bugs and sudden restarts, some of them might be cause by my phone or not, but since 5.1 everything is a lot more stable.
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.
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.