Related
I have an Xperia tablet Z, I've checked the service menu and confirmed that the bootloader unlock allowed value is "Yes".
I've requested and received the unlock key, and following the instructions on http://unlockbootloader.sonymobile.com/instructions.
I've prepared my computer for the process, and can confirm that the device connects to fastboot without issue.
Upon using the fastboot.exe -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXX, I receive the following error:
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
What do?
Doc_rockulus said:
I have an Xperia tablet Z, I've checked the service menu and confirmed that the bootloader unlock allowed value is "Yes".
I've requested and received the unlock key, and following the instructions on http://unlockbootloader.sonymobile.com/instructions.
I've prepared my computer for the process, and can confirm that the device connects to fastboot without issue.
Upon using the fastboot.exe -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXX, I receive the following error:
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
What do?
Click to expand...
Click to collapse
The unlock code is case sensitive - are you using the right case ?
GretaLewd said:
The unlock code is case sensitive - are you using the right case ?
Click to expand...
Click to collapse
I've copied and pasted it from sony's email, unless it was provided to me in the incorrect case, I doubt that's the issue.
I've worked a way around my task that did not require bootloader unlocking, but any additional assistance would be appreciated.
I've got the same problem with unlocking the bootloader from my Sony Xperia Tablet Z Wifi (SGP312,FW 10.3.1.C.0.136). In service menu there is written, that my device is unlockable, so i get unlock key from sony, but i can't unlock.
When i write in cmd
Code:
fastboot.exe -i 0x0fce getvar version
then i get as result
Code:
version: 0.5
finished. total time: -0.000s
. That's fine.
When i write in cmd
Code:
fastboot.exe -i 0x0fce oem unlock 0xMyKey
where MyKey is the key i received from sony email, then this error returns:
Code:
...
FAILED (remote: Command did not succeed)
finished. total time: 0.031s
I'd like to install Cyanogenmod-ROM and a recovery like clockworkmod. i'm familiar with rooting HTC- and Samsung-Devices, but i got no idea how to unlock this bootloader!
There's a program on this forum I used that unlocks it pretty much for you just gotta give code its called flashtool used it a couple days ago
Sent from my SGP311 using XDA Premium HD app
this is from Sony
http://unlockbootloader.sonymobile.com/
---------- Post added at 09:41 AM ---------- Previous post was at 09:41 AM ----------
this is from Sony
http://unlockbootloader.sonymobile.com/
@ Beastint: Doomlords flashtool doesn't work with FW 10.3.1.C.0.136.
@ MikeViller: yes, that's how i did it
i tried unlocking bootloader with upper and lower case letters in key, but still getting error message.
There is a tool called vroot to root the tablet, but i'd like to unlock the bootloader too, so that i can install CWM -> h t t p : //forum.xda-developers.com/showthread.php?t=2433466
What are the benefits of unlocking the Bootloader ? Sorry for the newbie question am kind of new to Sony
N1NJATH3ORY said:
What are the benefits of unlocking the Bootloader ? Sorry for the newbie question am kind of new to Sony
Click to expand...
Click to collapse
Allowing use of custom kernel needed to use non stock rom ( CM, omni, aosp based roms)
Sorry to jump in on this post but....
I have rooted my SGP321 (Tablet Z 16GB LTE) but I get when I check and enter the code to see if I can unlock my bootloader I get a NO returned
Does this mean there is no way around unlocking it?
Sorry for the questions. (I wish it was as easy as installing ROM's on my HTC One)
Finally bootloader is unlocked!
I sent another email with IDID to Sony instead of serialnumber and the key i received worked to unlock bootloader.
@N345H: i'not sure, but NO seems to be NO
so if we contact sony to get the bootloader unlocked. if anything went wrong after that, can we just relock, and restore the drm key and send it in for warranty? any has any experiences to share?
so if we contact sony to get the bootloader unlocked. if anything went wrong after that, can we just relock, and restore the drm key and send it in for warranty? any has any experiences to share?
I know HTC keeps track of unlocks not sure if Sony does if you were able to restore ta and.go.back to stock I would think it would be ok. Sony is pretty good. I had a xperia arc unlocked had some issues restored and sent it in and they still fixed it no charge
Sent from my C6506 using Tapatalk
xuanphucn said:
so if we contact sony to get the bootloader unlocked. if anything went wrong after that, can we just relock, and restore the drm key and send it in for warranty? any has any experiences to share?
Click to expand...
Click to collapse
I unlocked my drive and read the warnings, and Sony says it depends on your warranty. you should check your own if you have one. Mine is voided. They also mention additional cost for repair for an unlocked device.
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,
I got from a friend of Poco, she has a pattern that she does not remember - she does not have a google account - she wants to keep the data.
- usb debugging is disabled
- rom is locked
- not have xiaomi mi account
- fastboot return: FAILED (remote: Erase is not allowed in Lock State)
How to remove the code without losing data?
thanks
herwaldi said:
Hello,
I got from a friend of Poco, she has a pattern that she does not remember - she does not have a google account - she wants to keep the data.
- usb debugging is disabled
- rom is locked
- not have xiaomi mi account
- fastboot return: FAILED (remote: Erase is not allowed in Lock State)
How to remove the code without losing data?
thanks
Click to expand...
Click to collapse
no accounts on phone? so what data she want to keep?
anyway all stock? phone not unlock?
herwaldi said:
Hello,
I got from a friend of Poco, she has a pattern that she does not remember - she does not have a google account - she wants to keep the data.
- usb debugging is disabled
- rom is locked
- not have xiaomi mi account
- fastboot return: FAILED (remote: Erase is not allowed in Lock State)
How to remove the code without losing data?
thanks
Click to expand...
Click to collapse
It's impossible to keep any data. Even if you could unlock the bootloader, this will forcefully delete all data in the F1.
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)
Hi Please help for this ..
I have Redmi 8 (China) and sim port is broken , Currently i can't use any goolge service , so i want to change global or some other rom . Sim port is broken so can't add Mi account Official unlocking way . I tried with these cmd fastboot flashing unlock and it show
FAILED (remote: 'Token verification failed, reboot the device')
fastboot: error: Command failed . how can i unlock boodloader ?
i dont think there is another way
do you have any other phone that you can recieve the sms activation for mi account
LR7875 said:
do you have any other phone that you can recieve the sms activation for mi account
Click to expand...
Click to collapse
yes I have
chanmyae.emc said:
Hi Please help for this ..
I have Redmi 8 (China) and sim port is broken , Currently i can't use any goolge service , so i want to change global or some other rom . Sim port is broken so can't add Mi account Official unlocking way . I tried with these cmd fastboot flashing unlock and it show
FAILED (remote: 'Token verification failed, reboot the device')
fastboot: error: Command failed . how can i unlock boodloader ?
Click to expand...
Click to collapse
By the official method, you have to add your Mi account to that device, turn off WiFi, and turn on the mobile data, so without a SIM inserted you can´t do it.
Fastboot flashing unlock command, only worked for Xiaomi devices with Android One, for the rest you have Mi Unlock tool.