Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
LordManhattan said:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
Click to expand...
Click to collapse
I've re-flashed the ROM a few times on different versions. I'm currently on 4.2.2 - 14.1.B.2.257.
Mandersoon said:
Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Click to expand...
Click to collapse
I had the same problem when I tried to unlock.
Tried 5 times and then was finally successful. Ensure that you have typed out the commands correctly. Don't copy and paste as that wont work.
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
LordManhattan said:
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
hamdogg said:
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
Click to expand...
Click to collapse
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Mandersoon said:
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Click to expand...
Click to collapse
Hi Mandersoon,
I am in same problem and do you have any link or email to get new Unlock code from sony?
Thanks.
Encountered this on my first try. Then on the second attempt, it went through.
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
I just removed "0x" from the unlock code given by sony, it worked like a charm. :good:
I dont know why.
BlackCatAlex said:
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
Click to expand...
Click to collapse
can you please share the code i cant understand where to add 0x. i am facing the same issue. reply ASAP
Do not share the code/key. That's your unique key.
@psylbaba: it says "added "0x" before my code", so I assume he means 0x in front of the key when you're unlocking in Flashtool.
I just.....removed 0x and the <> in my code and it worked like a charm. Curious. (XZ1 user here)
Hi, found this thread when I was trying to unlock a Xperia z2, for me worked removing only the <> like this: fastboot oem unlock 0x"CODE"
Right click, administrator mode
Related
Hi I've tried searching about quite a bit but can't seem to find the correct solution.
I've had the bootloader unlocked once by following DoomLords instrucions but locked it as an upgrade popped up on my pc companion, now I can't seem to unlock it again.
I've followed the same process as before, even through the sony bootloader unlock site (this gave me the same unlock key as before) I've attached my error from the command prompt screen.
Anyone??
the screenshot is not readable.
maybe you forgot to remove the last number form the unlock key.
or flash a firmware first then try again
Sorry here's another screen.
I tried to re unlock the bootloader after an update via pc companion, it didn't work then.
I've now flashed ICS onto the phone with flash tool and unlocking the bootloader still doesn't work.
I've tried taking the last digit off the unlock code, with no luck!
Random post to keep the thread alive, hopefully someone will know whats up
Last try, anyone?
You're not using 0xFFFFFFF as the key are you?
No definitely not. That was the error the 2nd time round trying.....
hi, here I am again to ask:
I installed about 2 hours, never restart the phone, the FW: V20C_00 EUR.
I tried to unlock the bootloader but when I reboot instead of giving me the scermata release, I simply restarts.
Question: What firmware should I install? and where can I download?
Thank you very much again for your patience
A lot of people are in your shoes, and this is not fully figured out yet. Some people recently suggested adb version may have something to do with it. Look for their posts for discussion and possible solution. We don't need another post on this.
Meanwhile, you can try again, at least for a few more times (30 min to 1hour waiting with phone on network needed for each try). I got my unlocked the "last time" I would like to try before giving up.
mrmathematica said:
A lot of people are in your shoes, and this is not fully figured out yet. Some people recently suggested adb version may have something to do with it. Look for their posts for discussion and possible solution. We don't need another post on this.
Meanwhile, you can try again, at least for a few more times (30 min to 1hour waiting with phone on network needed for each try). I got my unlocked the "last time" I would like to try before giving up.
Click to expand...
Click to collapse
hello, today I had an idea, I plugged the phone in fastboot mode by following this guide: http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
I tried if the phone was plugged in, all ok I found. I tried to type the command "fastboot oem unlock" it gives me an error. Now, do you think you could use fastboot to unlock the bootloader?
tonysgh89 said:
hello, today I had an idea, I plugged the phone in fastboot mode by following this guide: http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
I tried if the phone was plugged in, all ok I found. I tried to type the command "fastboot oem unlock" it gives me an error. Now, do you think you could use fastboot to unlock the bootloader?
Click to expand...
Click to collapse
Negative.
Not all OEM allow that command. LG fastboot don't even allow getvar all.
I succeeded in doing the following:
1) downgrade my tablet to a rootable fw version
2) rooted with doomlord tool
Now I need to unlock my bootloader: I had requested the key a while ago, but never got around to using it.
I followed all the instructions and succeeded in connecting the tablet in fastboot mode to my pc (drivers installed fine and I receive a reply when issuing the trial command getvar version, meaning, I presume that the device is connected and able to receive commands and reply to them).
However when I issue the command in the instructions on http://unlockbootloader.sonymobile.com/instructions and replace the final "KEY" with the key provided by Sony via email I receive a reply "FAILED (remote: Command did not succeed)": what could I be doing wrong? I also copied and pasted the command in order to make sure that the syntax was correct and checked the code I input many times to make sure I did not miss or messed up something, but it all seems OK. I issued the command from within the same directory where the getvar command was issued, i.e. within Android SDk/Tools folder (the procedure on the website doesn't suggest to change folder, so I didn't!) , but no success at all!
Can anyone suggest some way out?
Thanks
Luca
astrovale said:
I succeeded in doing the following:
1) downgrade my tablet to a rootable fw version
2) rooted with doomlord tool
Now I need to unlock my bootloader: I had requested the key a while ago, but never got around to using it.
I followed all the instructions and succeeded in connecting the tablet in fastboot mode to my pc (drivers installed fine and I receive a reply when issuing the trial command getvar version, meaning, I presume that the device is connected and able to receive commands and reply to them).
However when I issue the command in the instructions on http://unlockbootloader.sonymobile.com/instructions and replace the final "KEY" with the key provided by Sony via email I receive a reply "FAILED (remote: Command did not succeed)": what could I be doing wrong? I also copied and pasted the command in order to make sure that the syntax was correct and checked the code I input many times to make sure I did not miss or messed up something, but it all seems OK. I issued the command from within the same directory where the getvar command was issued, i.e. within Android SDk/Tools folder (the procedure on the website doesn't suggest to change folder, so I didn't!) , but no success at all!
Can anyone suggest some way out?
Thanks
Luca
Click to expand...
Click to collapse
Sorry if this is a dumb question, but is bootloader unlocking allowed on your tablet ?
Some service providers have blocked bootloader unlocking.
GretaLewd said:
Sorry if this is a dumb question, but is bootloader unlocking allowed on your tablet ?
Some service providers have blocked bootloader unlocking.
Click to expand...
Click to collapse
I followed the procedure on the Sony website to check that and the answer is yes, it can be unlocked.
I tried some other tutorials and no results. It seems that it might be connected to the doomlord exploit (which I used to gain root access), but all the instructions on how to get around that have failed to allow me the unlocking!!!!
astrovale said:
I followed the procedure on the Sony website to check that and the answer is yes, it can be unlocked.
I tried some other tutorials and no results. It seems that it might be connected to the doomlord exploit (which I used to gain root access), but all the instructions on how to get around that have failed to allow me the unlocking!!!![/QUOTE
SOLVED
Click to expand...
Click to collapse
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
marceloariel said:
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
Click to expand...
Click to collapse
Thanks for the reply. I actually tried this as well but it did not work. MiFlash just appears to be running the flash_all_lock.bat script on Windows and it failed because the bootloader was not already unlocked according to its debug logs when I ran it. I should have mentioned that above.
Not sure if it will help but did you try a factory reset?
Press and hold the Power+Volume Down buttons untill you see the android with the no command. Press and hold the Power button. Press and release the Volume Up button once then release the Power button. Then you should see some recovery options.
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
sensig said:
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
Click to expand...
Click to collapse
The issue is caused by fastboot rom containing dummy system_b image and flashing script "forgetting" to force partition A as active. If a phone has B as an active partition and someone uses flash_all_lock.bat script, the phone's screwed. No idea what brought Xiaomi to this "brilliant" idea, not only there is a higher chance to brick the phone, but the zip file is also unnecessarily larger.
With locked bootloader it isn't possible to switch active partition anymore, so the phone is a (semi)brick. EDL mode is usually used to reflash locked bootloaders.
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
There are two commands for setting active partition, depending on the fastboot version. It's either old
fastboot set_active a
or newer
fastboot --set-active=a
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
if you open flashing script file (.bat or .sh) in a text editor, you will see that fastboot is flashing system.img to system_a partition and system_other.img to system_b partition. That system_other.img is a dummy image and is not bootable. You either:
Option 1: Set active partition to A before running any stock flashing script.
Option 2: Replace system_other.img to system.img in the script.
Option 3: Force partition A after flashing userdata.img and before any lock or reboot command.
dephekt said:
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
Click to expand...
Click to collapse
I am in the same exact position with my Mi A3... did you ever resolve this and if so how?
mewcatchew said:
I am in the same exact position with my Mi A3...
Click to expand...
Click to collapse
What causes led to this behavior ?
htn711 said:
What causes led to this behavior ?
Click to expand...
Click to collapse
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
Click to expand...
Click to collapse
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting).
Click to expand...
Click to collapse
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
garylawwd said:
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
Click to expand...
Click to collapse
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
---------- Post added at 02:40 PM ---------- Previous post was at 02:30 PM ----------
htn711 said:
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
Click to expand...
Click to collapse
Did you read my posts? I get "locked state error" with fastboot commands. I can reboot bootlader in fastboot, and it tjust reboots into fastboot - thats just about all i can do. It wont let me change anything, can only get info and reboot...
mewcatchew said:
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
Click to expand...
Click to collapse
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
garylawwd said:
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
Click to expand...
Click to collapse
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
Ya I wouldn't go trusting some random Russian site either. I don't think there is anything you can do without either
A) going into edl and using a verified mi account
B) bringing it to a service centre (which nobody wants to do)
In fastboot you can't get any commands to work now right? Your device is fully locked again?
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
That Russian site is run by the XDA guy from what I understood. There are other paid services which have Xiaomi service accounts, I only pointed you to the cheapest "verified" eshop. Just Google another one if you don't trust Russians. All of them will need to connect to your PC over Teamviewer and do the flashing, you will just follow the instructions (connect the phone, reboot it etc.).
Hello im new to the XDA forum and sorry for my bad writing but i am not an expert in english.
I wantet to unlock my bootloader of my nokia X20 only get the error:
FAILED (remote: 'Failed to unlock, decrypt failed!')
fastboot: error: Command failed
with both commands fastboot oem unlock & fastboot flashing unlock
i found out that my phone was encryptet from box.
i found a command to decrypt my phone but it can only run from recovery.
here is the point my phone doesn't have a recovery!
the bootloader doesn't show a recovery (video) + the recovery command brings me to a mini recovery with nothing in it (photo)
Everywhere in the internet it does all work fine only my phone is so or what?
Even Oem unlocking is blocked (greyed out) in the Settings of my phone [its in german because i am a swiss but translated i get the error] connect to the internet or contact your carrier but i have internet
when i try to reset via fastboot
Erasing 'data' FAILED (remote: 'did not have permission to erase')
fastboot: error: Command failed
Nothing works i just want to unlock the bootloader of my nokia X20 please someone help (ive already searched everything but nothing really helped.
Datas of my phone: Nokia X20 TA-1341 Newest android 12 update bootloader locked recovery desn't work phone like new no damages i can make resets via the os nothing unlocked Adb / fastboot drivers on newest versoin on my pc orginal cable not secondhand buyed direct from nokia.com nothing works please help me i want that bootloader unlocked
zip6como said:
Hello im new to the XDA forum and sorry for my bad writing but i am not an expert in english.
I wantet to unlock my bootloader of my nokia X20 only get the error:
FAILED (remote: 'Failed to unlock, decrypt failed!')
fastboot: error: Command failed
with both commands fastboot oem unlock & fastboot flashing unlock
i found out that my phone was encryptet from box.
i found a command to decrypt my phone but it can only run from recovery.
here is the point my phone doesn't have a recovery!
the bootloader doesn't show a recovery (video) + the recovery command brings me to a mini recovery with nothing in it (photo)
Everywhere in the internet it does all work fine only my phone is so or what?
Even Oem unlocking is blocked (greyed out) in the Settings of my phone [its in german because i am a swiss but translated i get the error] connect to the internet or contact your carrier but i have internet
when i try to reset via fastboot
Erasing 'data' FAILED (remote: 'did not have permission to erase')
fastboot: error: Command failed
Nothing works i just want to unlock the bootloader of my nokia X20 please someone help (ive already searched everything but nothing really helped.
Datas of my phone: Nokia X20 TA-1341 Newest android 12 update bootloader locked recovery desn't work phone like new no damages i can make resets via the os nothing unlocked Adb / fastboot drivers on newest versoin on my pc orginal cable not secondhand buyed direct from nokia.com nothing works please help me i want that bootloader unlocked
Click to expand...
Click to collapse
Sorry, but you're ****ing out of luck. Nokia ****ing dead-locked their phones, and there's no way to unlock them. Next time, go buy another phone from another OEM instead of this ****ing one.
https://forum.xda-developers.com/t/how-do-i-unlock-the-bootloader-for-nokia-x10.4323507/ I've also asked a similar question to yours before, and...People told me that there's no ways to unlock those new Nokia phones' bootloaders anymore. You can try contacting their customer support, but I don't think it will work. I contacted them before so I can unlock my Nokia X10's bootloader, but they just kept dodging my question and sent some automated answers instead
AltFantasy said:
Sorry, but you're ****ing out of luck. Nokia ****ing dead-locked their phones, and there's no way to unlock them. Next time, go buy another phone from another OEM instead of this ****ing one.
Click to expand...
Click to collapse
okay this is sad but still thank you for letting me know
zip6como said:
okay this is sad but still thank you for letting me know
Click to expand...
Click to collapse
no problem, and now I'm charging at the customer service email again. I will try to annoy them, and see if that'll make them unlock my bootloader
AltFantasy said:
no problem, and now I'm charging at the customer service email again. I will try to annoy them, and see if that'll make them unlock my bootloader
Click to expand...
Click to collapse
if you get a solution please let me know i really want to unlock my phone
zip6como said:
if you get a solution please let me know i really want to unlock my phone
Click to expand...
Click to collapse
I hope so, past attempts has proven unsuccessful, as said before. I hope that I will manage to talk them into unlocking my bootloader though. I wish I am good at social engineering or something similar to that, lol
AltFantasy said:
I hope so, past attempts has proven unsuccessful, as said before. I hope that I will manage to talk them into unlocking my bootloader though. I wish I am good at social engineering or something similar to that, lol
Click to expand...
Click to collapse
could you please say me where i can find the nokia or hmd support infomartion? i want to try my own luck.
zip6como said:
could you please say me where i can find the nokia or hmd support infomartion? i want to try my own luck.
Click to expand...
Click to collapse
Right here. Scroll down a little bit, and you can contact support via live chat, or email.
AltFantasy said:
Right here. Scroll down a little bit, and you can contact support via live chat, or email.
Click to expand...
Click to collapse
thanks
zip6como said:
thanks
Click to expand...
Click to collapse
A whole full year later....
How did your attempt go? Was you able to talk them into unlocking the bootloader, or did they use excuses like "security" and "stability" again?
AltFantasy said:
A whole full year later....
How did your attempt go? Was you able to talk them into unlocking the bootloader, or did they use excuses like "security" and "stability" again?
Click to expand...
Click to collapse
Wow i didn't think this thread is gonna get revived in a year.
Well i did contact Hdm but exactly like you staded they used security as an excuse so i wasn't able to unlock the bootloader.
My phone still works but when it breaks i will switch over to smasung because bootloader unlock there is very easy.
zip6como said:
Wow i didn't think this thread is gonna get revived in a year.
Well i did contact Hdm but exactly like you staded they used security as an excuse so i wasn't able to unlock the bootloader.
My phone still works but when it breaks i will switch over to smasung because bootloader unlock there is very easy.
Click to expand...
Click to collapse
well, here's some news for hoping: Hikari_Calyx acquired a few prototype units of HMD/Nokia phones (some of which look suspiciously similar to the Nokia X10/20), and with cases like this (he extracted a prototype ABL image for bootloader unlocking), one can hope that the Nokia X10/20 will be unlocked in the same way as the XR20 (minus the step of acquiring full access to tri-color company's Device Kit, of course, **** that kit)