Nexus 6 unlocked without "Enable OEM unlock" - Nexus 6 Q&A, Help & Troubleshooting

I did "oem unlock" on my new Nexus 6, because i wanted to upgrade directly to the newest image of Android 6.
However after that, i discovered, that i had to "Enable OEM unlock" in developer settings, to "oem lock" and "oem unlock" the device.
But I didn't had to do this the first time.
So is this feature not implemented in the first firmware version of the Nexus 6, or is my "new" device not realy new?

Looks like it was already unlocked when you got it. Usually you get a few messages about unlocking the phone to warn you and tell you the device will be wiped aka factory reset.

JulianPascal said:
I did "oem unlock" on my new Nexus 6, because i wanted to upgrade directly to the newest image of Android 6.
However after that, i discovered, that i had to "Enable OEM unlock" in developer settings, to "oem lock" and "oem unlock" the device.
But I didn't had to do this the first time.
So is this feature not implemented in the first firmware version of the Nexus 6, or is my "new" device not realy new?
Click to expand...
Click to collapse
are the dev options in settings witthout you unlocking them? if yes, then your new phone isnt new.

simms22 said:
are the dev options in settings witthout you unlocking them? if yes, then your new phone isnt new.
Click to expand...
Click to collapse
No, the developer options were not enabled. I got into fastboot mode, made sudo fastboot oem unlock, clicked yes and it was unlocked. I flashed the Android 6 image manually and after that i couldn't relock it. I had then to activate the developer options to relock the device.

gee2012 said:
Looks like it was already unlocked when you got it. Usually you get a few messages about unlocking the phone to warn you and tell you the device will be wiped aka factory reset.
Click to expand...
Click to collapse
I got this warning, but i didn't have to activate “Enable OEM Unlock” in the developer options to unlock the device.

JulianPascal said:
I got this warning, but i didn't have to activate “Enable OEM Unlock” in the developer options to unlock the device.
Click to expand...
Click to collapse
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch ?

gee2012 said:
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch ?
Click to expand...
Click to collapse
i think ive read about two more phones that had that "glitch", but its not common for sure.

simms22 said:
i think ive read about two more phones that had that "glitch", but its not common for sure.
Click to expand...
Click to collapse
I`am glad there is still some magic left in this world

gee2012 said:
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch
Click to expand...
Click to collapse
i've got only 1 Warning the first time: "Unlock bootloader? - yes(may void waranty / no)"
after the upgrade i get: the red "Waring" and then "Unlock bootloader?" - yes(may void waranty / no)

JulianPascal said:
i've got only 1 Warning the first time: "Unlock bootloader? - yes(may void waranty / no)"
after the upgrade i get: the red "Waring" and then "Unlock bootloader?" - yes(may void waranty / no)
Click to expand...
Click to collapse
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?

simms22 said:
i think ive read about two more phones that had that "glitch", but its not common for sure.
Click to expand...
Click to collapse
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?

JulianPascal said:
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
Click to expand...
Click to collapse
Thats probably it, had that on a N4 too once when i used CF Auto-Root (not wiped)

JulianPascal said:
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
Click to expand...
Click to collapse
na. it was there on the very first version of pre 5.0 that the phone came with. so it was there on all bootloader versions.

gee2012 said:
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
Click to expand...
Click to collapse
I did a full wipe before flashing, so I'm not shure if the upgrade process itself reseted the device.

gee2012 said:
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
Click to expand...
Click to collapse
simms22 said:
na. it was there on the very first version of pre 5.0 that the phone came with. so it was there on all bootloader versions.
Click to expand...
Click to collapse
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.

JulianPascal said:
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
Click to expand...
Click to collapse
i ran the very first version of software on my n6, back in november of last year, and it had to be unlocked with hitting the oem unlock option first. calling people at motorola is just going to get you talking to people that dont know whats going on.

simms22 said:
i ran the very first version of software on my n6, back in november of last year, and it had to be unlocked with hitting the oem unlock option first. calling people at motorola is just going to get you talking to people that dont know whats going on.
Click to expand...
Click to collapse
Ok, this is strange, the Device was new and the package sealed. I mean, could realy someone have somehow re-sealed it? Someone at Nexus Help Forum suggested, maybe someone at Motorola made a mistake in the final preparation process, so there are just some devices affected.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/nexus/ZoVKdHn-cM4/xwaB-b8MAQAJ
So, do you think the Device is safe to use(regarding the devices firmware (bootloader etc.) isn't altered/ some sort of maleware embedded)? Or should I return it, if I can?

JulianPascal said:
Ok, this is strange, the Device was new and the package sealed. I mean, could realy someone have somehow re-sealed it? Someone at Nexus Help Forum suggested, maybe someone at Motorola made a mistake in the final preparation process, so there are just some devices affected.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/nexus/ZoVKdHn-cM4/xwaB-b8MAQAJ
So, do you think the Device is safe to use(regarding the devices firmware (bootloader etc.) isn't altered/ some sort of maleware embedded)? Or should I return it, if I can?
Click to expand...
Click to collapse
mistakes do happen. ive seen people buy a n6 from tmobile but receive an att version, with all the att trimings. if you want to check if locking it is possible, you probably should. but, i think it probably is safe to use.

Theoretically someone could have bought it, opened it, unlocked it and did what ever with it, somehow reasealed it and returned it to the retailer(you have the right to return something you bought online in a 14 day period in germany).
I noticed something there are two numbers which are each 11 digits long, one on the the bottom and one on the side of the packaging.
(I covered them on the pictures, but marked where they are)
The two numbers differ at my packaging, Is this normal or should the two numbers be the same?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

JulianPascal said:
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
Click to expand...
Click to collapse
I have read this as well.

Related

[Q] Can't figure anything out

So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.
EvoTheBoy said:
So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.
Click to expand...
Click to collapse
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.
Seanie280672 said:
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.
Click to expand...
Click to collapse
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?
EvoTheBoy said:
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?
Click to expand...
Click to collapse
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968
For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)
Seanie280672 said:
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968
Click to expand...
Click to collapse
EddyOS said:
For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)
Click to expand...
Click to collapse
I keep getting this error :/ Idk if this helps but it says s-on and hboot is 1.54 and my OS is 5.11.1700.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
It is weird. I googled it and came about people saying to downgrade (Which I have 0 knowledge of when it comes to HTC devices.. coming from LG as my device with experience). Idk. Thanks for the help hopefully someone can help me out about this.
The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss
EddyOS said:
The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss
Click to expand...
Click to collapse
Guess that isn't the problem :/ I triple checked to make sure I had the right fastboot and I kept getting the same error.
EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
I've never seen that.. It's very odd.
graffixnyc said:
I've never seen that.. It's very odd.
Click to expand...
Click to collapse
I read online about it and saw some say to call google and they could help fix the problem cause it is a problem within the actual device. I called them and they didn't help lol. Anyways, my device is still under warranty and has the purple camera tint problem so I will try to send it in and hopefully get a new model back.
OT: if anyone has had this error before please say how you fixed it thanks
UPDATE: After some googling I found out that after 4.4.2 fastboot oem unlock does not work anymore with this devices (I am on 5.0.1)

Was told the VerizonDroid Turbo was rooted and needed to be unrooted.........plz help

did a lil research on google by what I was told........downloaded RSD Lite. When I went to look for phone info, noticed that there was NO IMEI info! No MIN, PRL Version, MEID,ICCID, IMEI, IMEI SV Unkown......No IP Address, No Wifi MAC Address or Bluetooth info...................there is a serial number tho. I can turn it on and play with it; it will go into bootloader or fastboot mode or what ever its called. From what ive read it came with kitkat version, it has lollipop installed. Is there anything I can do?
I'm thinking all that stuff should populate once you install a SIM card and put it on the network. If you really want a rooted phone, do it now with sunshine and unlock your bootloader. Otherwise, after you update to the latest marshmallow version, you will be forever hosed and not able to root at all. If the bootloader of states it is already unlocked, it's likely that sunshine has already been used.
A phone can't simply be unrooted to bet an update. The update will see the ROM is not pure stock, and fail. RSD can put a phone right, but can wipe the data. If rooted, why not put TWRP on, flash a stock rom in TWRP, saving data, reflash stock recovery in ADB, take update, TWRP back on, back up pure new-stock, mess with ROM. Little involved? Sure. More so than re-doing all your apps and settings? HELL NO!
Sent from my XT1254 using Tapatalk
cannon8694 said:
did a lil research on google by what I was told........downloaded RSD Lite. When I went to look for phone info, noticed that there was NO IMEI info! No MIN, PRL Version, MEID,ICCID, IMEI, IMEI SV Unkown......No IP Address, No Wifi MAC Address or Bluetooth info...................there is a serial number tho. I can turn it on and play with it; it will go into bootloader or fastboot mode or what ever its called. From what ive read it came with kitkat version, it has lollipop installed. Is there anything I can do?
Click to expand...
Click to collapse
Bootloader unlocked or nah? TWRP installed or nah?
cannon8694 said:
Was told the VerizonDroid Turbo was rooted and needed to be unrooted.........plz help
Click to expand...
Click to collapse
Who told you it was rooted?
Who told you it "needed" to be unrooted? Your post is very confusing.
I won't have a phone that is not rooted. All my phones WILL be rooted. Rooted means you are the "admin", you are the real owner.
In bootloader mode, what does the "status code" say? O, 3 ? What number do you see?
ChazzMatt said:
Who told you it was rooted?
Who told you it "needed" to be unrooted? Your post is very confusing.
I won't have a phone that is not rooted. All my phones WILL be rooted. Rooted means you are the "admin", you are the real owner.
In bootloader mode, what does the "status code" say? O, 3 ? What number do you see?
Click to expand...
Click to collapse
i just want the phone to work! would prefer it to be rooted, never had a rooted phone! status code = 0
TheSt33v said:
Bootloader unlocked or nah? TWRP installed or nah?
Click to expand...
Click to collapse
New to this........wtf is TWRP?
Okay, if status code is 0, that means your bootloader is locked. As long as you haven't taken all the over the air updates, you can still unlock it (and then root it). Follow this guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
cannon8694 said:
i just want the phone to work! would prefer it to be rooted, never had a rooted phone! status code = 0
Click to expand...
Click to collapse
TheSt33v said:
Okay, if status code is 0, that means your bootloader is locked. As long as you haven't taken all the over the air updates, you can still unlock it (and then root it). Follow this guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
Click to expand...
Click to collapse
If your bootloader is locked with status code of 0 (zero), your phone has NEVER been rooted and the bootloader has never been unlocked.
As @TheSt33v says, as long as you are not on the very latest firmware from March 2017, then you can unlock your bootloader and root your phone. Verizon released an update last month to block unlocking the bootloader on the Droid Turbo XT1254. Do NOT take any OTA updates!
TWRP is a "custom recovery" to replace stock recovery. It lets you make backups of your system (to restore your phone to earlier time in case of disaster) but also lets you "flash" zipped files like SuperSu to root.
If you are new to this, go read his guide in the link above, VERY CAREFULLY. All the information can be a little overwhelming. But do NOT take any OTA updates if you have not already. Because if you are on the very latest firmware, you are out of luck in unlocking the bootloader and rooting. Good luck.
when i type "fastboot flash recoveryTWRP.img"
ChazzMatt said:
If your bootloader is locked with status code of 0 (zero), your phone has NEVER been rooted and the bootloader has never been unlocked.
As @TheSt33v says, as long as you are not on the very latest firmware from March 2017, then you can unlock your bootloader and root your phone. Verizon released an update last month to block unlocking the bootloader on the Droid Turbo XT1254. Do NOT take any OTA updates!
TWRP is a "custom recovery" to replace stock recovery. It lets you make backups of your system (to restore your phone to earlier time in case of disaster) but also lets you "flash" zipped files like SuperSu to root.
If you are new to this, go read his guide in the link above, VERY CAREFULLY. All the information can be a little overwhelming. But do NOT take any OTA updates if you have not already. Because if you are on the very latest firmware, you are out of luck in unlocking the bootloader and rooting. Good luck.
Click to expand...
Click to collapse
when I type "fastboot flash recovery TWRP.img" into Minimal ADB and Fastboot it comes back "targer reported max download size of 536870912 bytes ; error: cannot load 'TWRP.img : No error"
did I possibly put the file in wrong place when it said to copy it to same directory as Minimal ADB and Fastboot?
cannon8694 said:
when I type "fastboot flash recovery TWRP.img" into Minimal ADB and Fastboot it comes back "targer reported max download size of 536870912 bytes ; error: cannot load 'TWRP.img : No error"
did I possibly put the file in wrong place when it said to copy it to same directory as Minimal ADB and Fastboot?
Click to expand...
Click to collapse
Reading the guide we told you about, have you unlocked your bootloader yet with Sunshine exploit? That's necessary prerequisite before trying to flash TWRP recovery.
If you haven't done that yet, which firmware version are you on? Settings/About Phone/Firmware -- or something close to that. Let's make sure you are eligible to unlock your bootloader before we get into detailed discussion. If you've already unlocked the bootloader, then ignore this question.
ChazzMatt said:
Reading the guide we told you about, have you unlocked your bootloader yet with Sunshine exploit? That's necessary prerequisite before trying to flash TWRP recovery.
If you haven't done that yet, which firmware version are you on? Settings/About Phone/Firmware -- or something close to that. Let's make sure you are eligible to unlock your bootloader before we get into detailed discussion. If you've already unlocked the bootloader, then ignore this question.
Click to expand...
Click to collapse
I downloaded the sunshine.apk. I moved it to the internal storage via usb cable, but cant seem to find it on phone to open it? if that's even how im suppose to do it? the droid razr m that im using now has a file manager app. thlis turbo doesn't seem to have on?
cannon8694 said:
I downloaded the sunshine.apk. I moved it to the internal storage via usb cable, but cant seem to find it on phone to open it? if that's even how im suppose to do it? the droid razr m that im using now has a file manager app. thlis turbo doesn't seem to have on?
Click to expand...
Click to collapse
You can install a file manager app from the play store. ES is probably the most popular free one but I prefer File Manager+.
Definitely do more research on unlocking the bootloader and flashing things, once you get root you can make mistakes which can brick your phone. But with that responsibility comes more freedom to do what you want to your device.
Sent from my XT1254 using Tapatalk
ChazzMatt said:
If you haven't done that yet, which firmware version are you on? Settings/About Phone/Firmware -- or something close to that. Let's make sure you are eligible to unlock your bootloader before we get into detailed discussion.
Click to expand...
Click to collapse
cannon8694 said:
I downloaded the sunshine.apk. I moved it to the internal storage via usb cable, but cant seem to find it on phone to open it? if that's even how im suppose to do it? the droid razr m that im using now has a file manager app. thlis turbo doesn't seem to have on?
Click to expand...
Click to collapse
Before we go any further, please go to Settings/About Phone, and look at your build number.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's some examples above. It will look something like this, on one of those screenshots. We need you to tell us EXACTLY what the "Build Number" says on your phone, please?
My WiFi is saying unavailable. Can't connect in order to get app store
cannon8694 said:
My WiFi is saying unavailable. Can't connect in order to get app store
Click to expand...
Click to collapse
Not asking about Wi-Fi or anything in the apps store.
Just tell us the build number in Settings/About Phone. Type in the exact numbers and letters, please.
Take a screenshot if you have to.
Capture a Screenshot - DROID TURBO by Motorola. To capture a screenshot, simultaneously press and hold the Power and Volume Down buttons. To view the screenshot you've taken, navigate: Apps > Photos from a Home screen.
Click to expand...
Click to collapse
But you can also just look at the screen and type.
SpyderPride said:
You can install a file manager app from the play store. ES is probably the most popular free one but I prefer File Manager+.
Definitely do more research on unlocking the bootloader and flashing things, once you get root you can make mistakes which can brick your phone. But with that responsibility comes more freedom to do what you want to your device.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
but how do I get it to install on my phone with no sim card, service or wifi
ChazzMatt said:
Not asking about Wi-Fi or anything in the apps store.
Just tell us the build number in Settings/About Phone. Type in the exact numbers and letters, please.
Take a screenshot if you have to.
But you can also just look at the screen and type.
Click to expand...
Click to collapse
SU4TL-49
cannon8694 said:
SU4TL-49
Click to expand...
Click to collapse
Fantastic. You're eligible for bootloader unlock. Just don't take any OTA updates from Verizon.
ChazzMatt said:
Fantastic. You're eligible for bootloader unlock. Just don't take any OTA updates from Verizon.
Click to expand...
Click to collapse
ok but im stuck on installing the sunshine.apk on the phone, and it said to copy the twrp.img to the same directory that minimal adb and fastboot? what that mean
cannon8694 said:
but how do I get it to install on my phone with no sim card, service or wifi
Click to expand...
Click to collapse
SIM cards are free, go pick one up or order one and activate the phone?
Sent from my XT1254 using Tapatalk

Easy way to relock bootloader?

Hi All,
Just wondering, is there way to relock the bootloader on the exynos Note8?
I see lots of guides to unlock and root but none to relock the bootloader. Any advice please?
Many, if not all, Exynos models on the Note 8 have an unlocked bootloader by default so unlike other Android devices, Motorola for example, there is no ADB command you can use to lock it.
If you want to provide more context, I would be happy to assist further.
A_H_E said:
Many, if not all, Exynos models on the Note 8 have an unlocked bootloader by default so unlike other Android devices, Motorola for example, there is no ADB command you can use to lock it.
If you want to provide more context, I would be happy to assist further.
Click to expand...
Click to collapse
Hello.
Thanks for replying. I have an Australian Note8 with Vodafone.
I went into developer settings and toggled the OEM Unlock/Bootloader unlock option. That is the only action I have taken.
Next time I went to use Android Pay it told me my bootloader was unlocked and it will no longer work.
I went back into developer settings and there it is, bootloader status is unlocked! Is this normal for Samsung devices?
All I want to do is relock the bootloader so that I may use Android Pay again.
I have not rooted the phone. All other apps pass safetynet.
Any advice would be greatly appreciated.
VerucaSalt said:
Hello.
Thanks for replying. I have an Australian Note8 with Vodafone.
I went into developer settings and toggled the OEM Unlock/Bootloader unlock option. That is the only action I have taken.
Next time I went to use Android Pay it told me my bootloader was unlocked and it will no longer work.
I went back into developer settings and there it is, bootloader status is unlocked! Is this normal for Samsung devices?
All I want to do is relock the bootloader so that I may use Android Pay again.
I have not rooted the phone. All other apps pass safetynet.
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Once you unlock the BL on Sammy you trip knox which also kills Samsung pay and other knox apps. Not possible to revert it.
me2151 said:
Once you unlock the BL on Sammy you trip knox which also kills Samsung pay and other knox apps. Not possible to revert it.
Click to expand...
Click to collapse
That's the really strange thing. Secure Folder, Samsung Pay and S-Health all still work.
Only the toggle has been done in dev settings, nothing else.
uhhhhh. i have no comment then >.>
VerucaSalt said:
That's the really strange thing. Secure Folder, Samsung Pay and S-Health all still work.
Only the toggle has been done in dev settings, nothing else.
Click to expand...
Click to collapse
What happens when you turn the oem switch to off and reboot? Might have to wait a bit.
Have you tried doing a factory reset?
Or reflashing the stock firmware? (Make sure oem is turned off first. )
BluePhnx said:
What happens when you turn the oem switch to off and reboot? Might have to wait a bit.
Have you tried doing a factory reset?
Or reflashing the stock firmware? (Make sure oem is turned off first. )
Click to expand...
Click to collapse
Thanks for the suggestions. I will have to wait until OEM unlock reappears as I reflashed the stock VAU firmware only yesterday hoping to fix. It didn't.
But before that I did try FR from the settings menu and from recovery. Same problem unfortunately
So a few things:
Knox should only be tripped if you introduce a foreign element to the device; flashing recovery to obtain root.
Turning on 'OEM Unlock' would do nothing to the device concerning Knox as it doesn't touch/alter the container reserved for Knox.
Thus if you were going to root, you would certainly need to have 'OEM Unlock' enabled to flash recovery.
This explains explain why Secure Folder, Samsung Pay and S-Health still work; the Knox container wasn't altered and the fuse not blown.
My suggestion is now that you have reset your device, don't bother toggling 'OEM Unlock' again unless you plan to root.
VerucaSalt said:
Thanks for the suggestions. I will have to wait until OEM unlock reappears as I reflashed the stock VAU firmware only yesterday hoping to fix. It didn't.
But before that I did try FR from the settings menu and from recovery. Same problem unfortunately
Click to expand...
Click to collapse
I basically had similar experience,( as you.) with toggling OEM toggle etc and it showed me that it was unlocked.
However a factory reset, should sort everything out.
My OEM showed after factory reset, that it was locked again.
Just wait the 7 days and check. Should be ok.
on a side note,....
I see even in my Google Play /Settings /Device
certification, it showing... Certified.
When my OEM was unlocked it showed
something like not verified / not certified or something like that.
A_H_E said:
So a few things:
Knox should only be tripped if you introduce a foreign element to the device; flashing recovery to obtain root.
Turning on 'OEM Unlock' would do nothing to the device concerning Knox as it doesn't touch/alter the container reserved for Knox.
My suggestion is now that you have reset your device, don't bother toggling 'OEM Unlock' again unless you plan to root.
Click to expand...
Click to collapse
Thanks man, I guess I have to wait a few more days until OEM unlock reappears and I can verify the status.
All I can say is that right now, android pay is telling me the bootloader is unlocked and from within download mode, OEM Lock = OFF
willcor said:
I basically had similar experience,( as you.) with toggling OEM toggle etc and it showed me that it was unlocked.
However a factory reset, should sort everything out.
My OEM showed after factory reset, that it was locked again.
Just wait the 7 days and check. Should be ok.
.
Click to expand...
Click to collapse
This is absolutely correct. OEM unlock toggled back and reboot.
BL now shows as locked.
Thanks. :good:
VerucaSalt said:
This is absolutely correct. OEM unlock toggled back and reboot.
BL now shows as locked.
Thanks. :good:
Click to expand...
Click to collapse
Thanks this worked for me as well.
Initially google play showed uncertified when i reset google play app everything back to normal
Hello my note 8 exynos device not support OEM unlock button ): help me please
Tayfnergin1997 said:
Hello my note 8 exynos device not support OEM unlock button ): help me please
Click to expand...
Click to collapse
Which model do you have? How long have you had it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3 day ago buy phone
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
3 day ago buy. SM-N950F
Tayfnergin1997 said:
3 day ago buy phone
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
3 day ago buy. SM-N950F
Click to expand...
Click to collapse
Ok thanks. It usually takes 7 days for the oem unlock toggle to appear in the developers options. So wait another few days (make it 8 in total to be safe) and then reboot. See if you have the toggle at that point. In the meantime, read through the oem unlock thread for more details.
sefrcoko said:
Ok thanks. It usually takes 7 days for the oem unlock toggle to appear in the developers options. So wait another few days (make it 8 in total to be safe) and then reboot. See if you have the toggle at that point. In the meantime, read through the oem unlock thread for more details.
Click to expand...
Click to collapse
Thanks bro. Oem unlock thread link please
Tayfnergin1997 said:
Thanks bro. Oem unlock thread link please
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=73796529
It's a large thread...suggest starting with the first and last 10 pages
VerucaSalt said:
Hi All,
Just wondering, is there way to relock the bootloader on the exynos Note8?
I see lots of guides to unlock and root but none to relock the bootloader. Any advice please?
Click to expand...
Click to collapse
snapdragon users are crying a lil right now.

Need Help Unlocking Bootloader and Rooting ROG Phone 3 by Asus

Update:
____________________________
FINALLY SUCCESS!
Downgrading my ROG Phone 3 to android 10 and using the unlock too (NOT OBIWAN) and finally success! For other peoples reference, the Firmware version I used was:UL-ASUS_I003_1-ASUS-18.0823.2104.147-1.1.95-user.zip, and the unlock tool I used was AsusUnlock_1.0.0.7_210127_fulldpi(1).Zip.
Many thanks for all the assistance and suggestions!! If this thread needs to be marked in someway to show the issue was fixed, please let me know, I'm still a little new here. Thanks!
I do have one final question ( for now)
If I upgrade to android 12 via dropping the file and running the upgrade through the phone like normal, the boot loader should STAY unlocked, correct?
Original Post:
_____________________________
Alrighty! I'm average linux user with a ROG Phone 3, I'm not completely sure as to whether it's the strix edition or not - at first I didn't think so but I got the model "ASUS_I003DD" so? Not really sure what to make of it. I'm not a pro with adb but any advice and pointers that can be offered I'd really appreciate - end goal is to root the phone but I feel confident I can figure that out if I can get the bootloader unlocked... which all traditional and googled answers seem to not work.
I've tried unlocking the bootloader with both Strix and normal Asus bootloader unlock apps(links at the botttom). I even downgraded to Android 11 because I noticed that Asus had a separate tool specific for android 11 but to no avail, I run
(bashshell)~$ adb reboot-bootloader
(bashshell)~$ fastboot oem device-info
and every time it has returned:
(bashshell-output):
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Device Authorized: false
I am not sure what steps to take next. Suggestions? Advice from someone who has unlocked the rog3 before??
Strix firmware/support and app
ROG Phone 3 Strix Edition | ROG Phone 3 Strix Edition | Gaming Phones|ROG - Republic of Gamers|ROG Global
ROG Phone 3 Strix Edition is everything you’ve always wanted for mobile gaming! Play Cooler. Play Faster. Absolute Control.
rog.asus.com
Normal Rog3 firmware/support and app
ROG Phone 3
ROG Phone 3 sets the new standard for mobile gaming! Absolute Power. Absolute Visuals. Absolute Control.
rog.asus.com
Is the device original Global version or converted from a Chinese version that has been unlocked and then re-locked before you bought it? That may be the explanation. My guess is your device id is not being validated by the ASUS server when using the unlock tool. These devices cannot be unlocked through the conventional OEM unlock methods (unfortunately) because ASUS have removed that as an option.
I think this is not a problem since my rog and the Chinese version that was converted I used, I used Asus' own app to unlock it, I rooted everything perfect
hermam said:
I think this is not a problem since my rog and the Chinese version that was converted I used, I used Asus' own app to unlock it, I rooted everything perfect
Click to expand...
Click to collapse
What steps did you take? What firmware did you use? I’ve used both versions of android (11 & 12) and both unlock apps (for 11 and for 12) and the boot-loader remains locked. What steps did you take? What information can I relay to you to help? The most that ever happens, is unless there’s a “network error” for the app, it will reboot the phone, not reset and not unlock the phone.
Andrologic said:
Is the device original Global version or converted from a Chinese version that has been unlocked and then re-locked before you bought it? That may be the explanation. My guess is your device id is not being validated by the ASUS server when using the unlock tool. These devices cannot be unlocked through the conventional OEM unlock methods (unfortunately) because ASUS have removed that as an option.
Click to expand...
Click to collapse
What would you recommend to test if that is the situation or not? If it is, do we know how to unlock it “unconventionally”?
meisnerwest said:
What would you recommend to test if that is the situation or not? If it is, do we know how to unlock it “unconventionally”?
Click to expand...
Click to collapse
Does the ASUS unlock tool complete successfully followed by a reboot? If not that's a very good indication.
In that case, I believe a solution that I belive has worked for some folks has been to change the device fingerprint to it's original in order to pass the ASUS unlock server, then root the device and change it back to Global.
I haven't done it myself, i strictly only buy original Global version of ROG phones only for exactly reasons like this, but I believe there are posts to be found here that explains out what you need to change.
I don't know any other 'unconventional' ways of unlocking this device unfortunately.
Andrologic said:
Does the ASUS unlock tool complete successfully followed by a reboot? If not that's a very good indication.
In that case, I believe a solution that I belive has worked for some folks has been to change the device fingerprint to it's original in order to pass the ASUS unlock server, then root the device and change it back to Global.
I haven't done it myself, i strictly only buy original Global version of ROG phones only for exactly reasons like this, but I believe there are posts to be found here that explains out what you need to change.
I don't know any other 'unconventional' ways of unlocking this device unfortunately.
Click to expand...
Click to collapse
The Asus unlock tool will either (A) reboot the phone, but change nothing (nothing is reset, bootloader still locked) or (B) run a error that it complains could be a network error.
When you say "change the device fingerprint" do you mean the firmware? so if it is a China model or UK model for instance, flashing it back to that models firmware, running the unlock, and then flashing it the user's preference?
If so-> Do we have a way to tell what the appropriate firmware for the devices should be?( UK,CN, etc)
If someone does have "unconventional" methods I have LG phone I'd love to unlock at some point smh. One phone at a time! I'll troll the forums some more.
Andrologic said:
Does the ASUS unlock tool complete successfully followed by a reboot? If not that's a very good indication.
In that case, I believe a solution that I belive has worked for some folks has been to change the device fingerprint to it's original in order to pass the ASUS unlock server, then root the device and change it back to Global.
I haven't done it myself, i strictly only buy original Global version of ROG phones only for exactly reasons like this, but I believe there are posts to be found here that explains out what you need to change.
I don't know any other 'unconventional' ways of unlocking this device unfortunately.
Click to expand...
Click to collapse
By the way! I did some looking and the strix and normal edition appear to have writing on the back of the phone on the sim tray side - "strix edition" and "areodynamic '???'tek" - which my phone apears to have neither?? I have attached the photo i took as well as the photos I'm referencing. Could I get some thoughst on this? Does this help knowing where this phone came from? (CN WW TW etc)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
QUICK UPDATE: I did a little digging on this page:https://forum.xda-developers.com/t/...-ww-with-final-android-9-1910-64-raw.4002279/
and attached a screenshot of my device hardware info. From that am I to believe that the phone already has the global fingerpint and global firmware?
@meisnerwest
my phone is from tencent CN version Rog3 and it is irrelevant even if it's strix or whatever. if nothing is working for you try to downgrade to A10 , that's the firmware i had when i unlocked my bootloader using the applicatiom from their website.
if it just reboot and nothing happen try the older version of the application.
meisnerwest said:
By the way! I did some looking and the strix and normal edition appear to have writing on the back of the phone on the sim tray side - "strix edition" and "areodynamic '???'tek" - which my phone apears to have neither?? I have attached the photo i took as well as the photos I'm referencing. Could I get some thoughst on this? Does this help knowing where this phone came from? (CN WW TW etc)View attachment 5796715View attachment 5796717View attachment 5796721
View attachment 5796717
QUICK UPDATE: I did a little digging on this page:https://forum.xda-developers.com/t/...-ww-with-final-android-9-1910-64-raw.4002279/
and attached a screenshot of my device hardware info. From that am I to believe that the phone already has the global fingerpint and global firmware?
Click to expand...
Click to collapse
this is strix edition. did you manage to root your phone?
osomakohj said:
this is strix edition. did you manage to root your phone?
Click to expand...
Click to collapse
I have gotten the boot loader unlocked but I have not rooted it yet. If you have advice I'm all ears!
meisnerwest said:
I have gotten the boot loader unlocked but I have not rooted it yet. If you have advice I'm all ears!
Click to expand...
Click to collapse
we're on same boat. I've used the app you mentioned and unlock my a12 rog3. Just confuse about rooting. Does rooting active slot enough? Or should I root both slot? Because I am afraid about flashing TWRP. The root method I like to do is to patch the booting ang flash via fastboot
osomakohj said:
we're on same boat. I've used the app you mentioned and unlock my a12 rog3. Just confuse about rooting. Does rooting active slot enough? Or should I root both slot? Because I am afraid about flashing TWRP. The root method I like to do is to patch the booting ang flash via fastboot
Click to expand...
Click to collapse
Gotcha, I’ll let y’all know if I come across anything good then I’ll let y’all know what happens.
meisnerwest said:
Update:
____________________________
FINALLY SUCCESS!
Downgrading my ROG Phone 3 to android 10 and using the unlock too (NOT OBIWAN) and finally success! For other peoples reference, the Firmware version I used was:UL-ASUS_I003_1-ASUS-18.0823.2104.147-1.1.95-user.zip, and the unlock tool I used was AsusUnlock_1.0.0.7_210127_fulldpi(1).Zip.
Click to expand...
Click to collapse
Hi, this method works for me, April 10 2023
Thank you very much
Faye Reagan said:
Hi, this method works for me, April 10 2023
Thank you very much
Click to expand...
Click to collapse
Not working for me, on the same firmware and using the latest unlock tool.

General Progress/How to in modding(rooting, recoveries,etc)

Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
EDIT: IT SEEMS LIKE WE CANT UNLOCK THE BL
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
#YetAnotherPerson said:
Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
Click to expand...
Click to collapse
Hi! Thanks for requesting this page!
For anyone considering buying this phone, just like OP said, DON'T buy if you want to MOD it in any way!
Also, if anyone has any information on this phone, like the firmware, exploits, etc. PLEASE share it since this device is not even that known in XDA.
Sad update, I backed up my Linux computer to install windows and use many apps to retrieve stock firmware for rooting and when device gets bricked, but no success, and I installed Linux again. I did not dual boot because of storage issues
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
#YetAnotherPerson said:
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
Click to expand...
Click to collapse
But wouldn't we need to at least unlock the bootloader to flash anything?
JoeBro19 said:
But wouldn't we need to at least unlock the bootloader to flash anything
Click to expand...
Click to collapse
There is a bootloader unlock option in settings, developer options
#YetAnotherPerson said:
There is a bootloader unlock option in settings, developer options
Click to expand...
Click to collapse
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
JoeBro19 said:
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
Click to expand...
Click to collapse
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
#YetAnotherPerson said:
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
Click to expand...
Click to collapse
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
JoeBro19 said:
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
Click to expand...
Click to collapse
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
#YetAnotherPerson said:
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
Click to expand...
Click to collapse
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
#YetAnotherPerson said:
Ok, but
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
Click to expand...
Click to collapse
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
JoeBro19 said:
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#YetAnotherPerson said:
View attachment 5902653
Click to expand...
Click to collapse
Just as I thought.... damn this companies...
So, unless some miracle happens and someone discovers an exploit on the processor or something that allows us to decipher the unlock code, there is absolutely nothing than we can do...
You can only unlock the bootloader on the new Honor at the Honor office. But this is only possible if the Honor employee is your friend.
volkodav1975 said:
You can only unlock the bootloader on the new Honor at the Honor office. The workers there have such smartphones, I have a friend among such workers and he made a request for me in a friendly way. I think that you will not see such a photo anywhere else. Alas, as long as it's useless, I need a custom one Recovery, But I don't know where to get it.
Click to expand...
Click to collapse
Well that's... disappointing... can't believe we have to even consider that. In my case, we don't have those centers, so I'm definitely screwed... good job Honor...

Categories

Resources