I've rooted, flashed, custom recoveried many many devices but only one on a MAC. I used Android Studio for MAC to be able to use ./adb commands and it was super easy for my Le Eco LE3 x522. Unfortunately, xiaomi forces their bootloaders to be unlocked via their own ****ing app that has no MAC terminal version. Why couldn't they just be like every other phone that uses the Android SDK? I've been working on this for 3 hours and I don't think I can do it on a MAC. Any help would be greatly appreciated.
yes you can do it, there is one miui tool for mac. i will try to find. i am mac user too
edit:
i find it http://en.miui.com/thread-2421616-1-1.html
THANK YOU!!!
Thank you so much man I really appreciate it, you saved me a couple hours.
well now I'm getting error 20041: unlock number has reached the upper limit... the search continues thanks for the help
So they make you wait a week then when the week is up they change it to another week, then after that it's 2 weeks and by the time you realize they were ****ing with you it's too late to return it... I'm just going to get rid of this Chinese piece of ****. Why the **** would they hold your phone hostage like this? I'm pretty mad, okay CHINA. Sorry, I'm not buying this ****ty brand ever again.
I tired both tools 1 & 2 both not working here is the CLI
[17:19:14][INFO ] Starting login procedure
[17:19:19][INFO ] Login procedure succeeded
[17:19:19][INFO ] Checking account unlock permission
[17:19:21][INFO ] Unlock permission confirmed
[17:19:21][INFO ] Waiting for a fastboot device
[17:19:21][INFO ] Device connected: a secret number was here
[17:19:21][INFO ] Obtaining device info...
[17:19:21][INFO ] Device info obtained
[17:19:21][INFO ] Checking if unlock will erase data and server message
[17:19:23][INFO ] Unlock procedure will erase userdata
[17:19:23][INFO ] Server message: An unlocked device is an easy target for malware which may damage your device or cause financial loss.
[17:19:23][INFO ] Querying unlock server for unlock key
[17:19:25][ERROR ] Unlock request replied with error code 20041
[17:19:25][ERROR ] Error meaning: Unknown error: %d
Admins-MacBook-Pro:MiUnlockTool Admin$
CryptoKnight614 said:
I tired both tools 1 & 2 both not working here is the CLI
[17:19:14][INFO ] Starting login procedure
[17:19:19][INFO ] Login procedure succeeded
[17:19:19][INFO ] Checking account unlock permission
[17:19:21][INFO ] Unlock permission confirmed
[17:19:21][INFO ] Waiting for a fastboot device
[17:19:21][INFO ] Device connected: a secret number was here
[17:19:21][INFO ] Obtaining device info...
[17:19:21][INFO ] Device info obtained
[17:19:21][INFO ] Checking if unlock will erase data and server message
[17:19:23][INFO ] Unlock procedure will erase userdata
[17:19:23][INFO ] Server message: An unlocked device is an easy target for malware which may damage your device or cause financial loss.
[17:19:23][INFO ] Querying unlock server for unlock key
[17:19:25][ERROR ] Unlock request replied with error code 20041
[17:19:25][ERROR ] Error meaning: Unknown error: %d
Admins-MacBook-Pro:MiUnlockTool Admin$
Click to expand...
Click to collapse
I am also a Mac user
The error code basically means that you need to wait 2 weeks or 15 days before you can unlock. It's a hassle, but everyone has to wait 15 days, the waiting period used to be longer. Sorry for the bad news. But at least you know that you can unlock it soon. Go ahead and make sure that you are syncing to Mi-Cloud so your account has established activity. The unlock policy Is a measure that Xiaomi has undertaken to protect its customers from unscrupulous vendors selling Chinese devices marketed as Global devices.
You can read more about the Mac compatible tool here: https://forum.xda-developers.com/an.../tool-miunlocktool-unlock-bootloader-t3782444
You can read more about the steps and the unlocking policy here : https://c.mi.com/thread-1635834-1-1.html
Enjoy you new phone, you will love it!
exactly, error code means that you have to wait 2 weeks or how to unlock phone. When it will time to unlock pass you will pass without error code.
slavke1976 said:
exactly, error code means that you have to wait 2 weeks or how to unlock phone. When it will time to unlock pass you will pass without error code.
Click to expand...
Click to collapse
So guys is possible to unlock Xiaomi bootloader with mi tool in mac os? and after this error if u try again 2 weeks is gonna be unlocked?
and can u flash twrp? please tell me
OnlyMpeka said:
So guys is possible to unlock Xiaomi bootloader with mi tool in mac os? and after this error if u try again 2 weeks is gonna be unlocked?
and can u flash twrp? please tell me
Click to expand...
Click to collapse
yes you can unlock xiaomi on OS X
yes you can flash twrp too
you need platform tools https://www.xda-developers.com/install-adb-windows-macos-linux/
you have to uzip, then in that folder you copy twrp
then you flash twrp by fastboot commands
Related
Researching length of code: http://pastebin.com/zHh76h60
After researching, I can conclude the code is going to be between 1-20 digits (assuming I am reading syntax correct)
Looks like we need the code for it for work, normally fastboot tells you the code for use and explains how to do it...but this is much better than success story than Razr, I believe the unlocking bootloader tool from Motorola WILL support this device! [UPDATE: NOPE! Motorola at this time is not supporting this device, but this method is the proper way anyway. ]
Code:
C:\Users\matt>fastboot devices
(My device ID) fastboot
C:\Users\matt>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.104s]
finished. total time: 0.107s
C:\Users\matt>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.104s]
finished. total time: 0.107s
This is not a special Atrix HD, it still says "Device is LOCKED. Status Code: 0" on the AP Fastoot Flash Mode (S) screen.
Code:
C:\Users\matt>fastboot oem get_identifier_token
...
(bootloader) Restricted oem command
FAILED (remote failure)
finished. total time: 0.100s
EDIT: (August 14th 2012)
Code:
C:\Users\matt>fastboot oem get_unlock_data
...
(bootloader) --redacted--
(bootloader) --redacted--
(bootloader) --redacted--
(bootloader) --redacted--
(bootloader) --redacted--
OKAY [ 0.351s]
finished. total time: 0.353s
Put this into your own device and find out your unlock data
Below is an excerpt from a strings.exe of the abootBackup partition:
Code:
Device already unlocked!
%s: START
%s: value = %s
fastboot oem unlock [ unlock code ]
OEM unlock failure!
Could not get unlock data!
Above you can see... we HAVE the unlock data now. We just have to figure out how to use it.
Status codes shown in AP Fastboot:
Code:
Device is LOCKED. Status Code: 0
Device is UNLOCKED. Status Code: 1
Device is LOCKED. Status Code: 2
Device is UNLOCKED. Status Code: 3
More strings.exe:
Code:
Error while unlocking device
mot_sst_validate_token: Token header incorrect
mot_sst_validate_token: Format version incorrect
mot_sst_validate_token: Length incorrect
mot_sst_validate_token: Binding information incorrect
mot_sst_validate_token: Unable to validate token integrity
mot_sst_validate_token: Token integrity invalid
unlock failed in sst oem unlock handler %02x
unlock data invalid!
Password incorrect
Password incorrect!
Cannot provide unlock data
Cannot provide unlock data!
general failure in sst oem unlock handler %02x
General system failure! %02x
Unlock completed! Wait to reboot
General Unlock failure!
unlock failed in sst oem unlock handler
Set MOT SST values
Done Setup my special MOT SST values
mot_sst_create_token: Unable to retrieve PUID
mot_sst_create_token: Unable to retrieve FUID
mot_sst_create_token: Getting PSV
mot_sst_create_token: Unable to retrieve PSV
mot_sst_create_token: Generate token code
mot_sst_create_token: token code generated!
mot_sst_create_token: Writing token
mot_sst_create_token: Unable to generate token code
create_token status: %d
mot_sst_create_token: Creating token
mot_sst_create_token: Getting flash uid
%s START
mot_sst_oem_lock_handler: invalid state
mot_sst_oem_lock_handler: load and validate failed
Re-lock failure
lock complete
%s failure to delete or create token
mot_sst_oem_lock_handler
From what it seems like... the device itself must create the same token that I believe a webkit will give us. [UPDATE: Proven right lol ]
I dont have the HD, so I'm just going on what I'm reading on my forum, the og Atrix, but alot of people there are having problems unlocking with replaced atrixes. Seems moto blocked the bootloader on them, so maybe its the same for the HD. I've been following the attempts at rooting the HD and the "promise" of moto releasing unlockable bootloaders, so hopefully progress is made soon. Good luck!
pre4speed said:
I dont have the HD, so I'm just going on what I'm reading on my forum, the og Atrix, but alot of people there are having problems unlocking with replaced atrixes. Seems moto blocked the bootloader on them, so maybe its the same for the HD. I've been following the attempts at rooting the HD and the "promise" of moto releasing unlockable bootloaders, so hopefully progress is made soon. Good luck!
Click to expand...
Click to collapse
As far back as I remember, any device from Motorola that shipped locked before disabled the command "fastboot oem unlock." This is the first time I have personally seen it possible on a release-keys "Retail" device like this.
With the Photon Q coming soon as well.. I would like to personally see this as a sign of us getting the unlock as well. Hopefully
mattlgroff said:
As far back as I remember, any device from Motorola that shipped locked before disabled the command "fastboot oem unlock." This is the first time I have personally seen it possible on a release-keys "Retail" device like this.
With the Photon Q coming soon as well.. I would like to personally see this as a sign of us getting the unlock as well. Hopefully
Click to expand...
Click to collapse
Im hoping too! I wont ever leave my og atrix, but still hoping with google acquiring moto mobility, that something sweet is coming! Im dedicated to moto.
Updated OP with some important new information.
Would be awesome to get something similar to revolutionary before the official "void your warranty" tool...
My tab's Flyer than yours (unless this is posted in a Flyer thread... Then it's just as Flyer...)
http://android-gz.com
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
cropythy said:
You need a code, even for the dev edition, just typing fastboot oem unlock generates:
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.082s]
finished. total time: 0.082s
and the device still shows:
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
flashallthetime said:
I had to manually put the numbers in, make sure you do not put any spaces between any number, letters. It took me twice
Sent on my Moto X
Click to expand...
Click to collapse
I tried manually entering it (3 times) i have tried copying it directly, and I have tried copying into notepad and making sure there are no spaces, but it still says my devices is not eligible for a bootloader unlock. Guess I'm calling motorola after work tomorrow.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
I just tried unlocking a Rogers Canada phone and it told me the phone isn't eligible. It certainly should be and I know I'm doing everything correctly as I unlocked a different one a few days ago.
So being you're seeing the same thing my conclusion is that the backend server which the website communicates with to manage the unlocking is broken at the moment.
cropythy said:
I got my Moto X dev edition the other day and am finally getting around to actually unlocking the bootloader, but the thing is when I follow the steps on the Motorola site and enter the code generated from fastboot oem get_unlock_data it gives me a message that my device is not eligible to unlock the bootloader. Have any of you had this issue? If so how did you deal with it? I would prefer not to have to call Motorola about this.
Click to expand...
Click to collapse
Try it again today, so far from my testing the unlock website is working again.
sarshadd said:
if my understanding is correct, boot loader is unlocked, you don't need a code. just type fastboot oem unlock.
Click to expand...
Click to collapse
As others have said, you need a code. The reason is you have to see like five warnings that the warranty will be voided before you get the code. They want to make sure people can't use the "I didn't know it would void the warranty" response if something goes wrong.
GSM Dev Can't go into CWM recovery
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
hondamarlboro said:
Unlocked bootloader successfully as instructed on motorola developer website.
But my GSM Dev version can't go into CWM recovery. If select "Recovery" on fastboot mode, normally reboot...
Could someone give me any advise?
# fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.710s]
writing 'recovery'...
OKAY [ 0.819s]
finished. total time: 1.529s
Click to expand...
Click to collapse
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Volume UP is the "select"
lensgrabber said:
Are you hitting volume up when you select recovery from the bootloader menu? It's not the power button to select, it's volume up.
Click to expand...
Click to collapse
Thank you!!! This is my first moto device and I don't know this manner. Successfully recovery into CWM. Thank you again!
Welcome.
Sent from my XT1053 using Tapatalk
Is possible, Lock bootloader ?
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
I'm trying to figure out the same thing. I followed motorola's instructions on reflashing https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images but it does not re-lock. It tells me "No valid PIV block in SP for userdata"
edit - deleted userdata and it locked, but i still get the warning screen on boot
warranty
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
vespadaddy said:
I thought Moto had reversed course, and now honors warranty issues on unlocked dev. devices...?
Click to expand...
Click to collapse
Anyone knows anything about that?
Also, is the image altered in any way after a unlock? or is it exactly the same as a factory reset?
---
edit:
apparently it is all fine
Requesting an unlock code will no longer void the device’s warranty
We will start posting return-to-factory software images
Click to expand...
Click to collapse
-- http://motorola-blog.blogspot.com/2013/11/you-asked-we-listened-announcing.html
Why really lock?
felipendc2012 said:
Hello, I wonder if when I unlock the bootloader Moto X, I can lock bootloader again?
like nexus 4 ? and be guaranteed again?
is it possible?
Click to expand...
Click to collapse
Why would you unroot and/or unlock?
If it is a dev edition, it will not hurt the warranty.
The reason for this phone is for unlocking, rooting, flashing and roming.
Once you have saved a nandroid with a custom recovery (TWRP) you can't mess anything up. Go crazy and have fun
Hi there,
I have a bricked ALE-L04, rooted with KingRoot without unlocking bootloader.
It worked well, until I flashed custom recovery. After that, when the phone rebooted it keeps complaining about modified recovery image with bootloader in locked state.
Since then (15 days ago) I'm asking at [email protected] for the unlocking code, with no answers (more than 10 mails already)
I have several issues when trying to get the code by entering at:
http://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
It needs a 16 characters Serial Number, and the phone and the box tells a 12 chars S/N
Removing the back cover I've found a 16 chars code printed inside, and thought it would be THE serial number.
When using this 16 code, it says that serial number and IMEI are mismatched.
It's so frustrating. Trying with another ALE-L04 (one that is working), I have the same problems...
If someone has any ideas, or any chance to get direct contact with huawei (they don't answer the mails), please help me
You doesn't need Huawei to email an unlock code for you.
You can get it from here, straight away: http : // emui . huawei . com/en/plugin.php?id=unlock&mod=detail
1. Download this Product ID generator and extract it somewhere: https : // drive . google . com/open?id=0B303_1pmtlHIdDVFb0llMGU3bjQ
2. Open it up, select the model HUAWEI C8812 (it should be already selected), type in your IMEI, and voila, you got your Product ID(8-digit number)
3. Go to this link: http : // emui . huawei . com/en/plugin.php?id=unlock&mod=detail and fill it out with your details.
4. You'll get your unlocking code straight away.
I managed to get my phone unlocked via this method.
Sorry for the links, i'm not allowed to post them, only this way.
Thank you for your answer!
I just tried again using the model you told, and same results:
SN and IMEI are mismatched
Do you know where can I get the 16 digits serial number? It's not on the box, nor in the phone neither.
You can find both of these numbers in the phone itself.
Go to Settings > About phone > Status and scroll down, the IMEI and the Serial number should be on the bottom.
If you have multiple SIM slots, then use the first IMEI number.
If it still says mismatched, then try other phone types.
Also, the Product ID generator tells me a different Product ID than my phone, but I was able to get the right unlock code via that number...
I also read somewhere, that some Huawei devices can be unlocked via the fastboot oem unlock UUUUUUUUUUUUUUUU command too. It's worth a try.
Thank you!
The problem is that the serial number is 12 digits only, it's not 16 and the unlock page doesn't like it.
By the way, I have a brick, and can't look into system settings because the phone doesn't boot up.
I've tried the UUUUU.. thing but this is the result:
Code:
$ fastboot oem unlock UUUUUUUUUUUUUUUU
...
FAILED (remote: Invalid key,unlock fail)
finished. total time: 0.134s
Still waiting more help! thank you very much for your time bro!
I've looked up few hits on the google, and seems you're not the only one with this problem.
In the Product ID generator app, you can find several phone models. Try each one of them and copy that Product ID onto the Unlock Code Request page with the same device selected there as in the program.
It'll take some time to get each one checked but I have no better solution.
Just for the record.. I have access to another p8 lite ALE-L04 and both have printed in the inside (removing the back cover) this:
1873UIF421X0xxxx
where xxxx are different.
And this doesn't match any code from the phone or in the box neither.
What I can't do:
The phone doesn't start
I can't look in the phone any data (serial, product ID, etc), because it doesn't start
I can't flash anything, because the bootloader is locked and don't allow me
daviddosa said:
You doesn't need Huawei to email an unlock code for you.
You can get it from here, straight away: http : // emui . huawei . com/en/plugin.php?id=unlock&mod=detail
1. Download this Product ID generator and extract it somewhere: https : // drive . google . com/open?id=0B303_1pmtlHIdDVFb0llMGU3bjQ
2. Open it up, select the model HUAWEI C8812 (it should be already selected), type in your IMEI, and voila, you got your Product ID(8-digit number)
3. Go to this link: http : // emui . huawei . com/en/plugin.php?id=unlock&mod=detail and fill it out with your details.
4. You'll get your unlocking code straight away.
I managed to get my phone unlocked via this method.
Sorry for the links, i'm not allowed to post them, only this way.
Click to expand...
Click to collapse
Unfortunately, the link for the unlock code site requires a phone # check and it's only for a few countries (NOT the US). The email signup page just doesn't work (presumably because I'm trying to sign up from a US web address). You can enter an email, password, veri code, but dead link, just doesn't go anywhere, so this is not usable, unfortunately. Not now anyway.
Hey
My huawei p8-lite ale-l21
Is totally bricked.
I haven't unlock it's bootloader.
Anyone please help me for unlock code
Device:huawei p8-lite (ale-l21)
imei 1:868755029772738
imei 2:868755029802741
S/n:W3DDU15A16002476
I dont know produt id
But I use huawei product id generator,it doesnot work
So
Please help me and send me unlocking code
Please
sagargrg12 said:
Hey
My huawei p8-lite ale-l21
Is totally bricked.
I haven't unlock it's bootloader.
Anyone please help me for unlock code
Device:huawei p8-lite (ale-l21)
imei 1:868755029772738
imei 2:868755029802741
S/n:W3DDU15A16002476
I dont know produt id
But I use huawei product id generator,it doesnot work
So
Please help me and send me unlocking code
Please
Click to expand...
Click to collapse
Hey Hey hey. Remove that, quickly. NEVER show your IMEI or SN on the internet. Do it via pm
I'm hoping someone can help:
I've been rooting/unlocking android phones for years. I've run Linux as my desktop OS for 15 years and I'm used to using fastboot.
I've had an Xperia Zr for a few years and when I saw them new on Ebay new for <$100 I bought another one.
So the first thing I try and do is unlock the bootloader, I have done this on several phones, including the ZR I use as my main phone.
I get the IMEI off the back of the phone and make sure it's the same as the one I get when I *#*#SERVICE#*#* and it is.
In Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes
I go to sony and get the unlock code for that IMEI (I've done this 4 times, it's always the same, I've double checked all the fields).
When I enter the command from fastboot to unlock the bootloader I get this:
[email protected]:/media/rolf/Data/Android$ sudo fastboot -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.598s]
finished. total time: 1.598s
So no error, it looks like it worked. When I reboot the phone it's like new again it wiped itself as it does after you unlock the bootloader.
But when I go back to Service->Info->Configuration it does say Rooting status: Bootloader unlock allowed: Yes , but it should now say bootloader unlocked.
When I go back to fastboot and try and flash anything it behaves like it still locked.
[email protected]:/media/rolf/Data/Android$ sudo fastboot flash recovery cm-13.0-20160930-NIGHTLY-dogo-recovery.img
sending 'recovery' (11570 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.369s
The phones both look identical, the new one looks genuine, the FCC ID and model number and Type are the same. The old phone was made in the 25th week of 2013 the new one is 30th week 2014.
Does anyone have any idea what is going on?
Thanks,
Rolf
Use flashtool to unlock bootloader.maybe this will work.I used flashtool to unlock my zr bootloader easily.
Flashtool is just a way for people who don't use the command line to issue commands.
Just to be sure I installed it under Linux and Windows and tried the bootloader unlock from there with the same results on both OSs.
01/004/2016 11:04:58 - INFO - Device connected in fastboot mode
01/007/2016 11:07:45 - INFO - Unlocking phone using key 3214A89EDE406752
01/007/2016 11:07:47 - INFO - ...
01/007/2016 11:07:47 - INFO - OKAY [ 1.385s]
01/007/2016 11:07:47 - INFO - finished. total time: 1.385s
01/007/2016 11:07:47 - INFO - Device will reboot into system now
01/007/2016 11:07:47 - INFO - Unlock code saved to C:\Users\rolf\.flashTool\registeredDevices\EP74168AM1\ulcode.txt
01/007/2016 11:07:47 - INFO - Device disconnected
Like when I use fastboot directly the device factory resets itself but remains a locked bootloader.
Has anyone ever seen a phone that says Bootloader unlock allowed: Yes but when you issue the command it fails silently?
Just to be sure, I have tried many different versions of flashtool. I have also tried using the wrong key to see what happens.
If I change the last digit of the unlock code then the command fails.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406751
...
FAILED (remote: Command did not succeed)
finished. total time: 0.035s
If I give the correct unlock code the command succeeds, but the phone never unlocks.
[email protected]:~/Documents/Protected/Android/FlashTool/x10flasher_lib$ sudo /home/rolf/Documents/Protected/Android/flashtoolbetalinux/x10flasher_lib/fastboot.linux.64 -i 0x0fce oem unlock 0x3214A89EDE406752
...
OKAY [ 1.569s]
finished. total time: 1.569s
I've tried using 2 different computers now so I have ruled out the computer hardware or software.
It seems to be the phone, this one is made in Malaysia the other one does not say where it was made.
Does anyone have any ideas?
This won't happen if your zr isn't carrier locked.So check it otherwise i'm unable to help you.Here are some great members in zr community can help you with this wired problem.PM with daedroza or sigprof.without PM it's not hard to get help from great members.
Never seen something like this, so the following is mostly a guesswork…
What ROM do you currently have on this phone, and did you reflash it? In theory it's possible that some strange (carrier-specific) ROM version relocks the bootloader during boot; another possibility is that the unlocking process is broken with some bootloader versions. Because creating the TA backup before unlocking needs root, I used old ROMs when unlocking — maybe even something ancient like 10.3.1.A.2.67, which can be rooted with opensource rootkitZ, and definitely not something which requires the malware-infested King Root. So flashing a stock ROM with a different bootloader version may help (the bootloader version number in boot_delivery.xml inside FTF must be different from the installed verson, otherwise flashtool will skip the bootloader parts when flashing — e.g., 10.6.x and 10.7.x stock ROMs have the same VERSION="1264-2309 S1_Boot_Lagan_1.1_10").
Thank you for some excellent advice. I had already re-flashed 5.1.1 with no change, so I tried 5.0.1 and there was also no change.
I found the oldest KitKat Rom I could and flashed that, as before the bootloader unlock command appeared to have worked but this time it rebooted into a boot loop.
I dropped back into fastboot and was able to flash a new boot.img and installing cm13 was quick and easy. The bootloader now shows as unlocked in SERVICE.
What software did you use to flash an old rom?
Hey everyone really need some assiat,help,guide, or any resources to make my device Unlocked.As i'm not a new guy on this stuff, also this is my second times having this ivy (Z3+) used to be the single sim variants and now with the Dualsim Variants,. Today i decided to unlock the bootloader after i've backing up the TA partitions with IOVYTools, so i do checked the bootloader status with *#*#7378423#*#* so its clearly said Allowed, then all i need is head to sony developer site to pull the secret codes unlock, received the email and put the imei numbera inside and ta daa the secret code comes up , put the devices into fastboot mode, and try to copy that codes but failed ,okay perhaps i need to type that codes manualy and i type with 5times checked that the codes/commad was correct but same result its FAILED,downgrading to some firmware and upgrading even to the latest one really not even help, same error Failed remote command not allowed, CRAP i give up so i put the thread/post here hoping someone or anyone here can tell me where i'm wronged?? I put some pictures here so everyone can see the situations i have.
SH1M4BD3 said:
Hey everyone really need some assiat,help,guide, or any resources to make my device Unlocked.As i'm not a new guy on this stuff, also this is my second times having this ivy (Z3+) used to be the single sim variants and now with the Dualsim Variants,. Today i decided to unlock the bootloader after i've backing up the TA partitions with IOVYTools, so i do checked the bootloader status with *#*#7378423#*#* so its clearly said Allowed, then all i need is head to sony developer site to pull the secret codes unlock, received the email and put the imei numbera inside and ta daa the secret code comes up , put the devices into fastboot mode, and try to copy that codes but failed ,okay perhaps i need to type that codes manualy and i type with 5times checked that the codes/commad was correct but same result its FAILED,downgrading to some firmware and upgrading even to the latest one really not even help, same error Failed remote command not allowed, CRAP i give up so i put the thread/post here hoping someone or anyone here can tell me where i'm wronged?? I put some pictures here so everyone can see the situations i have.
Click to expand...
Click to collapse
Download Flashtool from this link install it, run it and follow the bootloader unlock process, enter the code received from sony and unlock it.
For patched kernel, recovery and other things, check the following thread
https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
[email protected] said:
Download Flashtool from this link install it, run it and follow the bootloader unlock process, enter the code received from sony and unlock it.
For patched kernel, recovery and other things, check the following thread
https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
Click to expand...
Click to collapse
not its dioes not work sir, even with imei 2 the result failed (remote: Command not allowed), can i just root and flashing twrp and flash the custom rom like LOS??
SH1M4BD3 said:
not its dioes not work sir, even with imei 2 the result failed (remote: Command not allowed), can i just root and flashing twrp and flash the custom rom like LOS??
Click to expand...
Click to collapse
How is that supposed to work if the Bootloader is locked ?
Make sure you have USB debugging enabled
It is probably only a minor oversight that hinders it from succeeding
Also remove the screenshots( too much info)
SH1M4BD3 said:
not its dioes not work sir, even with imei 2 the result failed (remote: Command not allowed), can i just root and flashing twrp and flash the custom rom like LOS??
Click to expand...
Click to collapse
You need to create a text file called ulcode.txt containing the unlock code you received from Sony. Then put this file in a folder with your device (phone) name (eg. My device name is CB5A2B7CSV yours should be something similar. You can get the name using fastboot command devices. I see the name of your device in the first line of the third image you posted above!). Then put this folder inside the following path (create the necessary folders):
C:\users\your defult user name\.flashTool\mydevices
Then unlock your bootloader using flash tool. It will take your unlock code from the above mentioned text file and asks for permission for unlocking and will unlock the bootloader smoothly.
Good luck