does resetting phone change the unlock code? - Honor 7X Questions & Answers

i am trying to lock the bootloader again with my unlock code and it keeps saying the code is wrong, and it worked fine for unlocking.
my question is does the code change after a reset? i completely reset the phone to stock with stock loader,ercovery/recovery just cant seen to be able to relock the device.

darkmage1991 said:
i am trying to lock the bootloader again with my unlock code and it keeps saying the code is wrong, and it worked fine for unlocking.
my question is does the code change after a reset? i completely reset the phone to stock with stock loader,ercovery/recovery just cant seen to be able to relock the device.
Click to expand...
Click to collapse
I don't think it is supposed to have changed. At least it hasn't before.
fastboot oem relock *code_here*
what do you mean "stock loader"?
but if code is not working , it seems safe to say if you do lock it, and it will not work to unlock again......, if needed.

EDIT: god im stupid... this was the code they sent me: https://i.imgur.com/Zz2VgQz.png
so i was putting in 64ZR9670112GJ3F8 the code is supposed to be 64ZR96701I2GJ3F8
so lesson learned. make sure you really look at the code one's can look like i's in a pic.

Related

[Q] Gio doesn't prompt for unlock code

I flashed the cm9 and my phone shows no service and doesn't prompt for unlock code. all the others rom i had asked me to imput, but not cm9, so now i can't make calls/text.
btw i have the code, i dont know how to input as it doesnt prompt for one like usual
anyway to fix this or manually put in unlock code?
Do wipe
tried that, didnt work :/
This may be stupid question, but is airplane mode turned on?
Sent from my HTC Optimus Ray S
Most custom roms do not have the ability to perform this operation. The only way to unlock is to use odin to flash back to a stock ROM. I havent been able to unlock my phone either for this very reason.
Did you put in the sim card that you want to unlock?
I came up with this untested idea a few weeks ago, that would allow an unlock on a phone running AOSP/CM...
http://forum.xda-developers.com/showpost.php?p=23488092&postcount=12
thank you all, but didnt work so far, maybe because i have the canadian version (5660M) :/
Then you would be not able to use bluetooth, Wi-Fi and screen rotation, because of different drivers. But the rest should work just fine...
bump, any way to make phone ask for unlock code? i really want to use ics on my gio, but sim not working is a dealbreaker for me :/
alkspo said:
bump, any way to make phone ask for unlock code? i really want to use ics on my gio, but sim not working is a dealbreaker for me :/
Click to expand...
Click to collapse
Did you try darkshado's method? Cause other than that it is IMPOSSIBLE to do. Sorry.
Oh and instead of making a new thread, i have my own question. I know you only have a limited number of sim unlock attempts. Lets say 3 just cause. If i input the correct unlock code, does it count as an attempt? or do only the wrong numbers count as attempts?
AlwaysDroid said:
Did you try darkshado's method? Cause other than that it is IMPOSSIBLE to do. Sorry.
Oh and instead of making a new thread, i have my own question. I know you only have a limited number of sim unlock attempts. Lets say 3 just cause. If i input the correct unlock code, does it count as an attempt? or do only the wrong numbers count as attempts?
Click to expand...
Click to collapse
from my experience, i believe it doesn't count as an attempt when you get it correct, its like unlocking your phone with pattern/pin, it only counts the wrong ones, and once you unlock it, the attempt meter restarts
Wait,
Does this mean that if you're phone was previously sim-unlocked, it gets
re-locked when you flash CM9 ??
That would be a real bummer. I sim-unlocked my phone using the BML5 method
and flash a couple of stock roms using Odin, and never got the question for an unlock code again.
Do all custom roms re-lock your phone ??
Sorry for hijacking your topic. Hope you figure it out.
WalkerOfTheDay said:
Wait,
Does this mean that if you're phone was previously sim-unlocked, it gets
re-locked when you flash CM9 ??
That would be a real bummer. I sim-unlocked my phone using the BML5 method
and flash a couple of stock roms using Odin, and never got the question for an unlock code again.
Do all custom roms re-lock your phone ??
Sorry for hijacking your topic. Hope you figure it out.
Click to expand...
Click to collapse
im not sure if it is cm9 that locks it or maybe i was just unlucky once, i will try it again when i get my phone which is in factory as i broke the microsd slot
and no, not all custom roms, as i used plenty, only the cm roms (7, 7.2,9) have locked in my experience, but like i said before, maybe i was unlucky
Solution
Please remove
alkspo said:
im not sure if it is cm9 that locks it or maybe i was just unlucky once, i will try it again when i get my phone which is in factory as i broke the microsd slot
and no, not all custom roms, as i used plenty, only the cm roms (7, 7.2,9) have locked in my experience, but like i said before, maybe i was unlucky
Click to expand...
Click to collapse
Hi , is your phone sim locked or do you have a pin code on your simcard ? if the pin is on your simcard then the solution is to flash a stock rom and disable the simcard lock then flash a custom rom , I had the same issue with my HTC wildfire a couple of years ago

[Q] Issues unlocking bootloader Sony Xperia Arc S LT18i

Hello all,
I've got an Arc S that I've been trying to unlock the bootloader on using Sony's method, without success.
1. I have fastboot and adb installed on my machine (Linux Mint 14 32bit)
2. I've pulled the unlock code from Sony's website
3. I set my udev rules as laid out in this tutorial.
4. I have checked my bootloader to confirm that it can be unlocked (and currently is locked)
5. Fastboot is working (When I type in sudo fastboot devices, I get a hexadecimal string in response)
6. However, when I try to unlock, it always fails.
Initially, it gave me a "oem unlock failure code". After I rebooted thought, the code changed. Instead of something like this
Code:
oem unlock failed!
it gave me this
Code:
...
and did nothing. I let it sit for a few minutes and then forcibly shut down terminal, no damage done to the phone.
I'm quite confused at this point. From all my google searching I can't figure out why the booloader won't unlock. I'm pretty sure that I have the right unlock code.
A second and curious thing that may or may not be related is that the phone is rooted, but when I tried to transfer CWM via fastboot it threw an error, saying that the phone needed to be rooted first. However, it is rooted and apps such as Titanium Backup work just fine, verifying the root. Can anyone give me some direction on this?
I know there is a video on the how to unlock lt18i bootloader. It also has step by step process on fixing issues for unlocking bootloader. Lemme get.it for ya.
Sent from my LT18i using xda premium
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
sinkster said:
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
Click to expand...
Click to collapse
I don't believe that it is simlocked. I don't believe the phone was purchased through a carrier. For clarification, this is a friend's phone so I would need to ask them as to where they purchased it.
sinkster said:
May be a relatively simple thing. Is your phone simlocked? This may have some bearing on it.
Click to expand...
Click to collapse
No, it is not simlocked, else it would not show Bootloader Unlock Allowed: Yes
To OP: Write out the command you used to unlock the bootloader.
Someguyfromhell said:
No, it is not simlocked, else it would not show Bootloader Unlock Allowed: Yes
To OP: Write out the command you used to unlock the bootloader.
Click to expand...
Click to collapse
As taken from the Cyanogenmod Wiki page for Anzu devices:
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY was the bootloader unlock I received from Sony.
The dots indicate the software's not detecting your device. I had the same problem. Try reinstalling the drivers. If it still fails, maybe you can give the method outlined in the link below a go. It's for the relatively newer Sony devices, but maybe it'd work with the Arc. I haven't personally tried unlocking via Flashtool, but for me, the Fastboot command-based experience hasn't been all too good. I now use the Fastboot option in Flashtool, as opposed to standalone Fastboot, to flash every kernel that I use. Works like a charm each time, and what's more, it does away with the need to key in commands in the exact syntax.
http://forum.xda-developers.com/showthread.php?t=1971363
MarcSinger said:
The dots indicate the software's not detecting your device. I had the same problem. Try reinstalling the drivers. If it still fails, maybe you can give the method outlined in the link below a go. It's for the relatively newer Sony devices, but maybe it'd work with the Arc. I haven't personally tried unlocking via Flashtool, but for me, the Fastboot command-based experience hasn't been all too good. I now use the Fastboot option in Flashtool, as opposed to standalone Fastboot, to flash every kernel that I use. Works like a charm each time, and what's more, it does away with the need to key in commands in the exact syntax.
http://forum.xda-developers.com/showthread.php?t=1971363
Click to expand...
Click to collapse
I tried unlocking the bootloader via Flashtool and I got the same result of
Code:
oem unlock failed!
. So that means that something is wrong with my fastboot installation (not likely)my udev rules(possible) or for some crazy reason the phone is not reporting back correctly. A curious thing I noted is that when the phone is detected via adb it doesn't return the phone's IMEI. It does return a number, but it does not match the IMEI. Has anyone ever heard of that situation?
Guanfy said:
I tried unlocking the bootloader via Flashtool and I got the same result of
Code:
oem unlock failed!
. So that means that something is wrong with my fastboot installation (not likely)my udev rules(possible) or for some crazy reason the phone is not reporting back correctly. A curious thing I noted is that when the phone is detected via adb it doesn't return the phone's IMEI. It does return a number, but it does not match the IMEI. Has anyone ever heard of that situation?
Click to expand...
Click to collapse
I don't believe Fastboot returns the phone's IMEI. It's always looked to me like a random number that's generated to show successful connectivity between the device and the Fastboot program. But then again, I could be wrong.
Anways, despite the message you got, it's looking increasingly likely that your bootloader cannot be unlocked.
PS: You retired your SGS III, but kept your Arc? The decision really befuddles me.
MarcSinger said:
I don't believe Fastboot returns the phone's IMEI. It's always looked to me like a random number that's generated to show successful connectivity between the device and the Fastboot program. But then again, I could be wrong.
Anways, despite the message you got, it's looking increasingly likely that your bootloader cannot be unlocked.
PS: You retired your SGS III, but kept your Arc? The decision really befuddles me.
Click to expand...
Click to collapse
After much research I've found that when you get the "remote: oem unlock failed!" message it means you've enter an incorrect unlock code. Thing is, I know that I have entered the IMEI correctly on Sony's website, so I'm stumped there. I tried this setup in windows and got the same result, so I don't think it's fastboot or drivers anymore. It makes me wonder why I would be getting an incorrect unlock code...
To answer your PS, this phone belongs to a friend of my whom I'm doing a favor for. Note I don't have the Arc S in my sig. My retired SIII went to my wife, who was quite happy to have it.
Guanfy said:
After much research I've found that when you get the "remote: oem unlock failed!" message it means you've enter an incorrect unlock code. Thing is, I know that I have entered the IMEI correctly on Sony's website, so I'm stumped there. I tried this setup in windows and got the same result, so I don't think it's fastboot or drivers anymore. It makes me wonder why I would be getting an incorrect unlock code...
To answer your PS, this phone belongs to a friend of my whom I'm doing a favor for. Note I don't have the Arc S in my sig. My retired SIII went to my wife, who was quite happy to have it.
Click to expand...
Click to collapse
Are you sure that you left out the LAST number of the IMEI, when entering it on the website? You need to do that, else you get invalid code.
Someguyfromhell said:
Are you sure that you left out the LAST number of the IMEI, when entering it on the website? You need to do that, else you get invalid code.
Click to expand...
Click to collapse
Yup, that I have. I originally entered the 15 digit code and the website threw an error, so I deleted the last digit to get the unlock code that I tried.
same issue as LT26ii
Well I have exactly the same issue at my Xperia SL LT26ii, it just shows "oem unlock failed", do anyone know how to fix this ?
nkiy said:
Well I have exactly the same issue at my Xperia SL LT26ii, it just shows "oem unlock failed", do anyone know how to fix this ?
Click to expand...
Click to collapse
oem unlock failed
Problem solved!
Hey guys, I just unlocked my LT26ii after many times of "oem unlock failed". Here's my solution:
0. well first just remember your IMEI code, cause later it will changed.
1. Download a new firmware in ftf format.
2. Update firmware with Flashtool.
3. Turn on your phone and get you imei code. Now you should got a new one different from the previous one.
4. Use the NEW imei to unlock your phone.
Good Luck !
PS: dont guarantee that worked but if it does please let'me know.

Network unlock unsuccessful with code

I purchased a network unlock code from a site ive used many times. I put in a different sim in and it prompted for a code. I entered the code it said it was unsuccessful so i tried it again with same outcome. I read about having to use *#7465625# to unlock it so i tried that with no results. I figured if i flashed back to stock maybe those codes would work but that didnt make a difference. Now it no longer prompts me to enter an unlock code but will not register on the network. Ive read that it may be frozen but im not sure how to enter the unfreeze code. Can anyone help me please?
Did you get any codes other than the sim unlock code? You'll need a complete set of codes to unfreeze the phone asit is probably hard locked at the moment.
What phone do you have (i.e. i747 or i747m)? What stock ROM did you install on the phone?
vdiablo69 said:
I purchased a network unlock code from a site ive used many times. I put in a different sim in and it prompted for a code. I entered the code it said it was unsuccessful so i tried it again with same outcome. I read about having to use *#7465625# to unlock it so i tried that with no results. I figured if i flashed back to stock maybe those codes would work but that didnt make a difference. Now it no longer prompts me to enter an unlock code but will not register on the network. Ive read that it may be frozen but im not sure how to enter the unfreeze code. Can anyone help me please?
Click to expand...
Click to collapse
Are you on Android 4.3? If not you just need to flash the 4.1.1 radio to free unlock the phone. By the way, i heard that after 5 failed attempts of inputting the network unlock code your phone will need a master unlock code to unlock.
RA017 said:
Are you on Android 4.3? If not you just need to flash the 4.1.1 radio to free unlock the phone. By the way, i heard that after 5 failed attempts of inputting the network unlock code your phone will need a master unlock code to unlock.
Click to expand...
Click to collapse
Im on 4.1.1 but would like to use a custom rom will that affect it? Ive read that it may be frozen after 3 unsuccessful attempts but I dont think i entered it 3 times. I do have a defreeze code aswell but how do i enter it?
Are you on completely stock 4.1.1, including the bootloader? If you are, did you try unlocking the phone using the free method from here: http://forum.xda-developers.com/showthread.php?t=2176719 ?
audit13 said:
Are you on completely stock 4.1.1, including the bootloader? If you are, did you try unlocking the phone using the free method from here: http://forum.xda-developers.com/showthread.php?t=2176719 ?
Click to expand...
Click to collapse
No i have clockworkmod but its been so long I forget how to uninstall it though Ive figured it would help me unlock it. Ive read that free unlock doesnt work on all custom roms plus I already have the code so i might as well use it
audit13 said:
Did you get any codes other than the sim unlock code? You'll need a complete set of codes to unfreeze the phone asit is probably hard locked at the moment.
What phone do you have (i.e. i747 or i747m)? What stock ROM did you install on the phone?
Click to expand...
Click to collapse
I have the i747m with 4.1.1 and clockworkmod. Also I have network, provider, subprovider, defreeze codes.
Did you try any of these methods: http://www.mobileunlocked.com/samsung-instructions.asp ?
audit13 said:
Did you try any of these methods
Click to expand...
Click to collapse
haha yes Ive tried them but those codes do nothing when I dial them in. Only code that works is to get the imei and *#197328640#.
vdiablo69 said:
haha yes Ive tried them but those codes do nothing when I dial them in. Only code that works is to get the imei and *#197328640#.
Click to expand...
Click to collapse
I recently bought 2 i747M, one comes with 4.1.2 and one comes with 4.3.
For the 4.1.2, I just need to flash back to the 4.1.1 stock radio (the ROM is still 4.1.2), then I just follow the instruction below:
http://forum.xda-developers.com/showthread.php?t=2024514
(You need to be on stock rom in order to have the dialer code working)
For the 4.3, I play it safe and bought an unlock code for it which works on the 1st try.

WARNING - Don't bootloader LOCK your phone.

a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
gercdgcat said:
Do you refer to lock and unlock the bootloader? I locked and unlocked it much times and I've never had problems (obviously considering the bootloader version).
Click to expand...
Click to collapse
Thanks for replying - could you perhaps write a guide as to exactly how you unlock your bl after using fastboot lock?
I have seen a few folks who appear stuck at that point and I and they would be happy campers if they could get around that!!!
Thanks!
EDIT: I added a comment about "correct stock" to the first post... This may be key to the folks that are having trouble...
You might look at thread
https://forum.xda-developers.com/moto-z-play/help/please-help-urgently-t3814260
But I guess I would have to call anyone who successfully locks and unlocks again their bootloader as darn lucky. Some, (many?) can't.
In the end I still have to ask "why the heck are you locking your phone" - what could you possibly gain? It's totally unnecessary. it can be a very expensive little line of code.
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
pkadavid said:
I lock my phone all the time, multiple times per day even! It's really easy to unlock: I simply put my finger on the sensor and voila!
Maybe you mean the bootloader? That would be a helpful little detail to add to the title of your post.
Click to expand...
Click to collapse
LOL - right! Thanks!!!
bump
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
IncendiaryPyro said:
I've locked mine as I upgraded to a Pixel 2 XL and gave my Z Play to my father, so I don't really care if I can't unlock it again, but I'm sure that wouldn't be an issue anyway.
Click to expand...
Click to collapse
How's the 2xl?
hithere
KrisM22 said:
a) There is no logical reason to bootloader lock a phone. You will gain nothing.
b) If you lock it there is a high probability you won't ever be able to bootloader unlock it again - no more mods - ever.
EDIT: Perhaps if you flash the "correct stock" meaning one like/identical to the one that you originally had on your phone when you unlocked it the first time, it will work...
Think about this, please, before you flash things!!!
Click to expand...
Click to collapse
I prefer stock without modifications but sometimes when i have time to try news modifications or roms i used to unlocked the phone and after this relock again, the process that i use is very simple, i just unlock with the same code that Motorola gaves to unlock bootloader, i don't have sure but if you request unlock codes to many times can be a problem but i use the same code and works good.
Basically: relock as are specifcified in another topic in this device forum( using the last stock version that you used)
And after this unlock with code again
Obs.: Is not recommended to unlock/relock to many times.
Obs2.: I only did this three times and i don't know if has a limit
bumpsi
It is my opinion also that relocking is a bad idea. But if someone likes to do it, eg to get Google Pay working without Magisk, why do you want to warn him?
Relock only is possible in combination with flashing a complete correctly firmware. If something is wrong with the firmware you flash, relocking won't succeed. Your device won't be locked if it does not fully succeed or the firmware is not correctly signed. The unlock code is supposed to stay valid, you should be able to unlock your device as many times as you want using the same code.
a) is fine, but does not consider Android SafetyNet
b) is just wrong, and this already was written in a comment.
Please do not bump wrong warnings.

Any way to remove unlocked bootloader message?

I do not want to relock my bootloader, but I want to get rid of the nag screen at boot that bootloader is unlocked. Just in case my phone will get into wrong hands that is like an open invitation to hack it.
I remember I used to replace this logo with a neutral black screen on one of my previous devices. Isn't that possible anymore nowdays?
Yes, I understand that is not a perfect security. A perfect security is if my phone will be kept in a safe in a swiss bank with keys lost. Just trying not to give obvious hints.
EDIT:
LOL sorry I don't know how but I missed first 8 words in Your post. Don't read my reply it won't help.
Hi.
I was converting from Tmobile to global. To get rid from that messege I simply locked the bootloader. I'm not sure if u want to lock it or you are looking for some kind of way around it. If you would like to do it remember its very important to do it after taking OTA otherwise you can have some problems with your phone. That was mine steps:
Unlock bootloader.
Flash global.
Do OTA.
Lock bootloader with "fastboot oem lock".
Hope it helps. Regards.
thardy00 said:
EDIT:
LOL sorry I don't know how but I missed first 8 words in Your post. Don't read my reply it won't help.
Hi.
I was converting from Tmobile to global. To get rid from that messege I simply locked the bootloader. I'm not sure if u want to lock it or you are looking for some kind of way around it. If you would like to do it remember its very important to do it after taking OTA otherwise you can have some problems with your phone. That was mine steps:
Unlock bootloader.
Flash global.
Do OTA.
Lock bootloader with "fastboot oem lock".
Hope it helps. Regards.
Click to expand...
Click to collapse
LOL, yeah! This happens

Categories

Resources