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)
Related
Can any developer please please help me out quickly? i'm out of time seriously I need help but quick.
I'm trying to unlock my device Redmi Note 3 Snapdragon varient. All the other commands like
* adb devices
* adb reboot edl
* fastboot devices
* fastboot oem device-info
everyone of it is working fine but when I write
* fastboot oem unlock-go
I get the above mentioned error.
Does anybody know the solution to it? Before answering please consider that other commands are working except this one, I didn't found any proper solution that's why posted the problem here and I already did revoke USB debugging permissions and turned it on again but that didn't helped.
So please give me a working solution as quick as possible or else any help is appreciable.
enable oem unlock in developer options
Enable OEM Unlock option in Developer Options.
caesar13th said:
enable oem unlock in developer options
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
superboy123 said:
Enable OEM Unlock option in Developer Options.
Click to expand...
Click to collapse
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Gurkirat_Singh said:
It's already enabled, I don't know what's causing the problem. Please help me with another solution. Ask everything at once, I will answer. But I really need a solution.
Click to expand...
Click to collapse
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
superboy123 said:
That fastboot oem unlock-go command won't work.
OK, follow these steps:-
a) Reboot to Fastboot mode by pressing Power and Vol down buttons for 10 seconds.
b) Download the MiUnlock tool and enter your credentials first. It will check whether your Mi account has permission to unlock (you must have permission from Xiaomi to unlock).
c) It will detect your phone as Mi Phone and proceed to unlock.
d) It will verify whether the Mi account in your phone and the credentials of the Mi account you entered on the PC are the same.
e) It will unlock your device for sure!
If it says some sort of verification error aka. the famous stuck at 50%, wait for some days like for a week and try again, it may work even in 2 days! Keep trying!
Good Luck!:good::highfive:
Thank you!
Click to expand...
Click to collapse
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Gurkirat_Singh said:
Thanks for the help but I don't even want to try that method first it's very problematic, it takes a lot of time and it's not even sure if it works. So if you can help me with the problem I'm having that would very very very appreciable :good:.
And why the command will not work, can you please tell me? Also this command gives the same error "fastboot OEM unlock bootloader". Hope you can help .
Click to expand...
Click to collapse
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
superboy123 said:
It's not that problematic, actually it is the easiest way to unlock bootloader!
Unofficial bootloader is the very "problematic" method.
Anyhow, Are you looking for unofficial bootloader unlock? Then go here and follow the steps correctly, dont skip any step.
And for your second question, Xiaomi has complicated the bootloader unlock process by heavy encryption. That's why you couldn't unlock Redmi Note 3 as any Moto device!
Click to expand...
Click to collapse
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Gurkirat_Singh said:
OK that's why I'm having so much problem to unlock it. I just want to ask do you know any other way to fix the problem I'm having with this error. Cause the post you gave me tells how to unlock the RN3 temporary :crying: but the thread I followed helps to unlock it permanently :good: (how I know cause I used similar commands on my Canvas A1) and I followed almost every step properly.
I don't understand why companies emerged as custom ROMs stops supporting customisation, at least don't make it hard. I just wanted to flash my RN3 with a Custom ROM like CM13 cause MIUI is not supporting 4G networks properly of multiple operators that's why, for which I needed a custom recovery and for which I needed unlocked bootloader.
I just don't understand , all this so that no one could copy their ROM or I don't know for what . It's just makes things difficult for normal people and no one else. Locks can't keep a thief away. If anyone wants to break into their system than one will, if he/she uses right tools properly. Why make normal people lives' difficult?
ALSO I WANT TO ASK MORE THING, if in first case, I get into fastboot mode just after the ROM flash & before very first ROM boot and run this command and if in second case, the room gets booted and then I go into fastboot mode & run the command, DOES IT CREATES ANY CHANCE OF NON-OCCURRENCE OF THAT ERROR IN FIRST CASE?.
Click to expand...
Click to collapse
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
Thanks for all the support and help you gave me.
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
caesar13th said:
I got this error too but i forgot how to fix it.
Something about the 'disable driver signature' or the modified rom that you flash before you trying to unlock.
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
superboy123 said:
The thread I gave you was not temporary, it is permanent and it is temporary till you get the official unlock permission. Actually it's a permanent 'safe' solution.
Xiaomi did it for security of data, not to stop customising. If it had to stop users from customising, xiaomi wouldn't have given you warranty even if you root or it may not even have given you an option to unlock bootloader!
Click to expand...
Click to collapse
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Gurkirat_Singh said:
I unlocked the bootloader and also flashed the ROM successfully but still I'm not able to use the 4g service.
Click to expand...
Click to collapse
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
superboy123 said:
By your name, I think you are an Indian, so which Sim you are using? You need to do a 4G pack recharge first to use LTE, VoLTE won't work in custom ROMs right now.
Edit: you could see this thread but this is a bit complicated: http://en.miui.com/thread-335643-1-1.html
Click to expand...
Click to collapse
I appreciate your help but the post you gave me is for non-asian countries so it will not work for me. As you already know I'm an Indian so that's why. Are you an Indian, only asking cause in that way you may already faced the problems i'm having.
I'm only familiar with only 2 4G networks for now. One is Airtel 4G, what they say have FDD LTE network, I don't what that is, but that's why it's not working on my phone, I contacted them and they said that my phone doesn't support it, I don't know why cause it support much more LTE Bands other than any smartphone in that price range. Second is Jio 4G, my sim gets detected, shows network in manual selection but doesn't get registered on them. I see only the message of 'No Service' or 'Emergency calls only' when I insert it.
@Gurkirat_Singh
It worked for me.
I had the same problem!
superboy123 said:
@Gurkirat_Singh
It worked for me.
I had the same problem!
Click to expand...
Click to collapse
What worked for you and how? Can you please answer/clarify my questions/doubts please also?
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
superboy123 said:
I tried that fix that I gave you and 4G started working for me. You cannot use jio on second sim slot. 2nd sim only connects to 2g.
Click to expand...
Click to collapse
OK I'll try when got time and will update you with the result.
Dear all,
I bought Mi Pad 4 and it was running well, and I want to update the ROM. The device is comes with Locked bootloader.
I unlocked my Mi Pad 4 using MI Unlock. And when I try to relock it using "fastboot oem lock" command, it become suddenly comes with black screen with written: "The system has been destroyed. Press power button to shutdown".
So I entered the fastboot mode and try some command/solutions:
- My device status is locked:
E:\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
finished. total time: 0.006s
- I can't unlock it using Mi Unlock:
- Flashing using MiFlashalso not allowed since it is still locked:
- I tried to unlock using fastboot, also failed:
E:\adb>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.003s
- The faastboot screen in my mi pad is only for around 10 Second. After that it goes to "The System has been Destroyed" stage...
Any help is appreciated, because I cant use it anymore...
Why did you even want to close the BL again?!? I dont understand anyone who does that.
And AFAIK you can flash an original Image from Xiaomi even with locked BL. But I have never done it and the guide shows a working phone..
http://en.miui.com/thread-835254-1-1.html
You need the Mi-Flash Tool. And these damn Indian people with their fake titles on youtube.. The title is english and the freaking video is hindi or whatever.. SO ANNOYING!!!
Hi, the tutorial you gave is for 'normal' xiaomi phone, where it boot normally (even its BL is locked).
In my case, I cant load the BL (It said: Destroyed). The only thing I can do is restart to fastboot state, and after 20 seconds it goes again to Destroyed state.
Ok, so I have read some other threads and what seems the "only" solution is to unlock the bootloader again.. But the other people had no problem running "oem unlock".. And you get an error, what is kinda strange.
What happens in MiUnlock? Error?
Hi, I think the main problem is current status is "The System has been Destroyed", therefore it cannot load the BL.
Meanwhile, the BL is in Locked status. So it need to be un-locked first, so I can load the new ROM.
MIUnlock is error, it said: "Current account is not bound to this device", which is strange, because previously I unlocked using it before.
I assume MIUnlock said this because the status of "System destroyed"...
Never lock if there is not 100% Xiaomi official rom inside, and better use MiFlash with "clean all and lock" option for locking.
Thanks for your suggestion. Will do that after I fix this problem..
I think you have a bricked device.. Some devices have this "test-pins", where you can enable some debug-bridge and there you could flash it (mi5 or redmi5 was that in that thread). I dont know if the Pad4 has such Pins and you would have to open the whole device.. (its not something you can access from the outside).
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Noted on that, but too risky for me to open the case..
Any other solution would be really appreciated.
thE_29 said:
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Click to expand...
Click to collapse
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
P.Kosunen said:
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
Click to expand...
Click to collapse
Yup, and I cant do that since cannot load the BL, because it's "Destroyed" right now..
Up.
Does anyone have the solution on this?
Thanks.
Seemed "bricked" to me, welcome to the bricked world dude, I have had 2 beautiful paper holder on my desk.
mac_erot said:
Up.
Does anyone have the solution on this?
Thanks.
Click to expand...
Click to collapse
The only solution was already posted several times -> open device, find test-pins, use them and flash ROM. And yet, you still ignore it everytime. THERE is no other solution for bricked devices.
And: NEVER close the bootloader again on NON official ROMs.
2 ways to try out...
1st run
"fastboot flashing unlock"
2nd
"fastboot oem reboot EDL"
Or this link if the command doesn't work
https://www.google.com/amp/s/forum....e-how-to-reboot-to-edl-fastboot-t3394292/amp/
go to service centre they will be able to restore the device using edl i hope
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Looks like it is straightforward to remove the back cover. Perhaps you can find the EDL test points on the motherboard?
https://www.youtube.com/watch?v=RZpj0k9HKTQ
Is there no possibility to enable USB Debugging without entering the miui surface?
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Edl with test points should work, try some different ones, maybe the ones you are trying are wrong
---------- Post added at 06:47 AM ---------- Previous post was at 06:47 AM ----------
Also, try to run fastboot erase vbmeta
Im on the Oct 1 security update.
I ran the Nokia unlock apt I side loaded. There app gives me a error message of device not supported.
When I got into Developer Options turn on OEM unlocking Allow the boot loader to be unlocked I still get the message Device not supported, When I run there app
I know the boot loader is still locked because when I try to flash TWRP recovery I get this message
fastboot boot twrp.img
Sending 'boot.img' (38732 KB) OKAY [ 0.902s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
So it very much seems like the boot loader is still locked.
Any suggestion thanks
raven.warsong said:
Im on the Oct 1 security update.
I ran the Nokia unlock apt I side loaded. There app gives me a error message of device not supported.
When I got into Developer Options turn on OEM unlocking Allow the boot loader to be unlocked I still get the message Device not supported, When I run there app
I know the boot loader is still locked because when I try to flash TWRP recovery I get this message
fastboot boot twrp.img
Sending 'boot.img' (38732 KB) OKAY [ 0.902s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
So it very much seems like the boot loader is still locked.
Any suggestion thanks
Click to expand...
Click to collapse
Sigh,
1. There is absolutely no official bootloader unlock for this phone.
2. Though there is no official bootloader unlock, you can still Bloader unlock your phone using a paid service by TechMesto @Singhsk ...
usernamedoesnotexist said:
Sigh,
1. There is absolutely no official bootloader unlock for this phone.
2. Though there is no official bootloader unlock, you can still Bloader unlock your phone using a paid service by TechMesto @Singhsk ...
Click to expand...
Click to collapse
I did see a tread about that thanks for the info.
my guess is its most likely not worth doing I dont see very many roms listed for the phone.
I guess its not very popular for that reason. Its a shame it seems like a nice phone. But the market is flooded with phones I dont see any thing that makes this one stand out
thanks for answer my question
raven.warsong said:
I did see a tread about that thanks for the info.
my guess is its most likely not worth doing I dont see very many roms listed for the phone.
I guess its not very popular for that reason. Its a shame it seems like a nice phone. But the market is flooded with phones I dont see any thing that makes this one stand out
thanks for answer my question
Click to expand...
Click to collapse
Yeah, not much dev for this device. Probably because of no official bootloader unlocks and popularity of the 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.).
Hi! I have a big problem. I have a Chinese version of the phone without google services. I tried to flash the firmware from the motorola and it worked, but since when the bootloader is unlocked, google pay does not work, I blocked it with the fastboot oem unlock command and that was a mistake. after which he broke.
I've tried recovery mode / factory mode in fastboot, but it still goes into bootloop.
I have downloaded the firmware, and have my 20-character alphanumeric code to unlock the device bootloader.
When I enter this code in ADB using fastboot oem unlock CODE it says 'Check 'Allow OEM Unlock' in Android Settings > Developer'.
But I can't Check 'Allow OEM Unlock' in Android settings as I can't boot the phone, and I never 'Checked it' when the phone was working properly.
Is there anyway to 'Allow OEM Unlock' while the phone is in fastboot mode, without being able to boot the phone properly?
Any attempt to flash the phone with native firmware or any other leads to the message "FAILED (remote failure)"
i'm tried different options with xda but nothing helps ... do I really have to throw the device in the trash ... it makes me very sad.
I can't believe that the manufacturer didn't come up with a normal recovery option.
I will be very grateful for your help.
What is the bootloader status? if it is Flashing_Locked, then its a high chance that isn't fixable, like my G6 Plus, i tried everything, but nothing appears to help. My phone is on the wardrobe, just waiting for some expert to come with a solution to this...
Tsumetaay said:
What is the bootloader status? if it is Flashing_Locked, then its a high chance that isn't fixable, like my G6 Plus, i tried everything, but nothing appears to help. My phone is on the wardrobe, just waiting for some expert to come with a solution to this...
Click to expand...
Click to collapse
yes, unfortunately bootloader status Flashing_Locked ((
Mit1332424 said:
yes, unfortunately bootloader status Flashing_Locked ((
Click to expand...
Click to collapse
sadly, there isn't a known fix for flashing_locked, there is some people that had the luck to lock it on OEM_Locked and could reflash stock, but for Flashing_Locked you cant
there is 3 options now:
-Play dumb and get a replacement from motorola
-Wait for a fix
-Replace the motherboard
Tsumetaay said:
sadly, there isn't a known fix for flashing_locked, there is some people that had the luck to lock it on OEM_Locked and could reflash stock, but for Flashing_Locked you cant
there is 3 options now:
-Play dumb and get a replacement from motorola
-Wait for a fix
-Replace the motherboard
Click to expand...
Click to collapse
Is it really possible to wait for a fix? It seems to me that the motorola is not very worried about it.
Mit1332424 said:
Is it really possible to wait for a fix? It seems to me that the motorola is not very worried about it.
Click to expand...
Click to collapse
there must be a way by using EDL or JTAG pins to unlock it since motorola doesn't want to share stock factory images to us. I don't think the solution is going to be available soon, so just try to play dumb with motorola and get a replacement...
Mit1332424 said:
Is it really possible to wait for a fix? It seems to me that the motorola is not very worried about it.
Click to expand...
Click to collapse
unfortunately my phone is no longer under warranty. Yes, and I tried EDL, it doesn't work. Bootloader lock is too good
Mit1332424 said:
unfortunately my phone is no longer under warranty. Yes, and I tried EDL, it doesn't work. Bootloader lock is too good
Click to expand...
Click to collapse
Sadly mine is also no longer under warranty... About EDL, i don't mean blankflashing it, instead there must be a way to access the bootloader lock related partition directly from the EMMC then unlocking it...
Mit1332424 said:
unfortunately my phone is no longer under warranty. Yes, and I tried EDL, it doesn't work. Bootloader lock is too good
Click to expand...
Click to collapse
I think that if this happens then the protection of all devices will be compromised and the manufacturer will definitely not want it. most likely the phone died forever
Mit1332424 said:
I think that if this happens then the protection of all devices will be compromised and the manufacturer will definitely not want it. most likely the phone died forever
Click to expand...
Click to collapse
yea it was a bad call from my side... So i was doing a quick search here and i found something that can be useful
the Medusa JTAG Pro Box can skip the "permission" thing and flash the stock, but its kinda expensive in my country and i don't know anyone that has it...
Tsumetaay said:
yea it was a bad call from my side... So i was doing a quick search here and i found something that can be useful
the Medusa JTAG Pro Box can skip the "permission" thing and flash the stock, but its kinda expensive in my country and i don't know anyone that has it...
Click to expand...
Click to collapse
gave the phone to a local service, maybe they have something similar. I'll tell you the result within two days
Mit1332424 said:
gave the phone to a local service, maybe they have something similar. I'll tell you the result within two days
Click to expand...
Click to collapse
ok, i still have hopes that they know how to fix it and it is easy to do so.