The Nokia 7.2, surprisingly, comes with an unlockable bootloader. The information is shared by TechMesto and I am just re-using it to create this guide.
Notes:
Unlocking the bootloader may void the device's warranty.
All existing data on the device will be erased.
To unlock:
Update: Nokia has disabled the unlock ability with the December MR. You can only unlock if you downgrade your phone to an old release first. You can get it at Nokia Care or by buying remote flashing services.
Before you start: Make sure that you have platform-tools downloaded on your PC. You need to open a CMD or Terminal window in the folder where you have saved the platform-tools, unless you have installed them system-wide.
• First of all, enable Developer Options by tapping 7 times on BuildID in "About phone".
• Then go to developer options and enable OEM Unlocking option.
• Now reboot the phone into bootloader/fastboot mode. You can use the adb command:
Code:
adb reboot-bootloader
or else use hardware keys to reboot to bootloader mode.
• Make sure the phone is detected in fastboot mode. Then send the OEM unlocking command:
Code:
fastboot flashing unlock
• Confirm the unlock on the phone.
{
"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 it!
You can also do the unlock_critical if you plan to flash the bootloader.
Reserved for future use.
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
KohGeek said:
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
Click to expand...
Click to collapse
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
singhnsk said:
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
Click to expand...
Click to collapse
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
KohGeek said:
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
Click to expand...
Click to collapse
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
singhnsk said:
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
Click to expand...
Click to collapse
I was curious too, it kicked me off the bootloader screen when I was doing that on version 060, but it seems all is well now
https://nokiamob.net/2019/11/02/off...nlock-the-nokia-7-2-and-nokia-6-2-bootloader/
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Coolboy996 said:
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Click to expand...
Click to collapse
You can use TWRP or patched image to root the 7.2
Can confirm that it is still unlockable. Got 2 of them today from Argos in the UK (Scotland). They are on 00WW_1_130 with security batch from 2019/08/05.
Only thing I had to do was enable internet and reboot to get the option to stop being greyed out.
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Are you sure? Has Horrendously Menacing Dicks actually started blocking people having reasonable control of their 7.2 devices after letting them have it for so long?
allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Yep. They blocked the ability with the most recent December MR.
singhnsk said:
Yep. They blocked the ability with the most recent December MR.
Click to expand...
Click to collapse
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
CGarz said:
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
Click to expand...
Click to collapse
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
That really sucks. Now no devs will buy it =(.
allc0re said:
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
Click to expand...
Click to collapse
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
bkttk2 said:
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
Click to expand...
Click to collapse
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Lamtanloc512 said:
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Click to expand...
Click to collapse
Think we may be out of luck then, but one last suggestion. I noticed when reading through the thread on user indicated they were using "flash" instead of "flashing" when trying to unlock the bootloader.
I know I personally did the same thing at first. Did anyone confirm that "flashing" was used?
I know the older methods used flash. Just asking.
Related
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
I was surprised to not find this information in any of the forums.
This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone Buyers" from Oppo's decision.
Oppo has of this year decided to "lock the access to its Bootloader".
By "access" i mean no way to access it with "adb reboot fastboot" and "adb reboot bootloader" and any "Bootup Button combination".
Its not only hitting new phones but also old phones.
All the latest ColorOS Firmwares will prevent you from accessing the Bootloader.
All Project Spectrum alpha/beta's for OLD and NEW phones will prevent you from accessing the Bootloader.
If you are using a custom rom and want to try out any of the above stock roms. Be !WARNED! you will lose access to the Bootloader!
They not only removed the access to the Bootloader but also removed the "fastboot binarys" itself.
If by chance you are able to access the Bootloader and want to use fastboot commands. All commands will result in "FAILED (remote: unknown command)"
I noticed this and raised questions in the official Oppo forum:
{
"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"
}
this is the official reply:
I hope this helps enthusiastic users in their "phone choice".
For me access to the Bootloader and having fastboot commands are on top of the list when it comes to choosing a new phone.
Update:
It seems like that Oppo decided to bring back fastboot and the possibility to unlock the bootloader in their "Project Spectrum" ROM.
But apparently not in all devices!
ColorOS (The Stock ROM) is unaffected and remains with a defunct fastboot. Confirmed by Oppo R9 Plus users. Which is Oppo's latest Qualcomm based phone.
Thank God i didn't upgrade !
You can unlock the bootloader and access the fastboot by downloading the old version of the ColorOS.
Thanks.
Mulham82 said:
You can unlock the bootloader and access the fastboot by downloading the old version of the ColorOS.
Thanks.
Click to expand...
Click to collapse
this is only true for devices which had firmware releases in 2015. my Oppo R7S (European Version) for example was already shipped with a firmware that is hit by their new strategy. no old firmware to unlock the bootloader or access fastboot.
celoxocis said:
Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016
I was surprised to not find this information in any of the forums.
This is why I'm posting this thread to prevent further confusion and future xda-enthusiastic "Phone Buyers" from Oppo's decision.
Oppo has of this year decided to "lock the access to its Bootloader".
By "access" i mean no way to access it with "adb reboot fastboot" and "adb reboot bootloader" and any "Bootup Button combination".
Its not only hitting new phones but also old phones.
All the latest ColorOS Firmwares will prevent you from accessing the Bootloader.
All Project Spectrum alpha/beta's for OLD and NEW phones will prevent you from accessing the Bootloader.
If you are using a custom rom and want to try out any of the above stock roms. Be !WARNED! you will lose access to the Bootloader!
They not only removed the access to the Bootloader but also removed the "fastboot binarys" itself.
If by chance you are able to access the Bootloader and want to use fastboot commands. All commands will result in "FAILED (remote: unknown command)"
I noticed this and raised questions in the official Oppo forum:
this is the official reply:
I hope this helps enthusiastic users in their "phone choice".
For me access to the Bootloader and having fastboot commands are on top of the list when it comes to choosing a new phone.
Click to expand...
Click to collapse
Thanks for the info, it´s something to keep in mind certainly.
Thank you for your effort in this. Any process on the r7s front?
Website signature
Yes , I got caught out by this
I purchased my R7s due to Oppo's previously root friendly attitude only to find I could not root when I had updated my phone to the latest version
I have expressed my displeasure to Oppo
this is exactly what happened to me when I purchased the R7S. I did my research before purchase and saw that all previous Oppo phones were unlockable using fastboot. when I bought the phone. fastboot binarys were removed in LK.
there has been alot of effort by xda-dev's to find a way to unlock the affected phones.
I can only say this much. a way has been found. which was used to put pressure on Oppo including all the incoming complains.
Im a project Spectrum beta tester and the good news is. that the project Spectrum beta roms have fully working fastboot binarys. which will allow an bootloader unlock.
if you look in the Oppo forum. you will see that I provided an official TWRP and am currently working on a CyanogenMod.
no need to give up or to pass on this mid-ranger at all. just patients
is there really no way to root the phone? i don't understand Chinese and in the original way i can't use the OPPO R9 Phone
If anyone can point me towards where to find older R7 PlusF firmware that would be great. Doesn't seem to be listed on oppo website anymore.
"R7plusfEX_11_OTA_005_all_201508180100"
Is available by host server aborts download at 100mb/1.3gb
Looks like I missed out this thread... Only recently I discovered such situation at Oppo forum. Very disappointed by this...
is there any way for unlocking fastboot for oppo a37 which only has coloros3.0.0 rom?
hamzachaudhry36 said:
is there any way for unlocking fastboot for oppo a37 which only has coloros3.0.0 rom?
Click to expand...
Click to collapse
Have you checked if you have fastboot access at all? Install minimal adb & fastboot enable debugging mode in developer options and issue the command "adb reboot fastboot".
If the phone simply reboots then Oppo has not included fastboot binarys for your device.
celoxocis said:
Have you checked if you have fastboot access at all? Install minimal adb & fastboot enable debugging mode in developer options and issue the command "adb reboot fastboot".
If the phone simply reboots then Oppo has not included fastboot binarys for your device.
Click to expand...
Click to collapse
Yeah phone simply reboots but is there any solution for flashing new fastboot bunarys on my device
hamzachaudhry36 said:
Yeah phone simply reboots but is there any solution for flashing new fastboot bunarys on my device
Click to expand...
Click to collapse
No unless an older ROM version had it and it was removed with an upgrade.
Try reverting to the oldest ROM version you can find and try again.
celoxocis said:
No unless an older ROM version had it and it was removed with an upgrade.
Try reverting to the oldest ROM version you can find and try again.
Click to expand...
Click to collapse
The problem is my phone got out with latest rom version .....
Is there any way to port fastboot binarys from some other rom to mine ....?????
There is a phone named Xaomi 2 Prime which has same specs(GPU, CPU and RAM) is there a way to port those files ....??
hamzachaudhry36 said:
The problem is my phone got out with latest rom version .....
Is there any way to port fastboot binarys from some other rom to mine ....?????
There is a phone named Xaomi 2 Prime which has same specs(GPU, CPU and RAM) is there a way to port those files ....??
Click to expand...
Click to collapse
NO!!! You will brick your phone!
Different manufacturer totally different signature's!
There is no way! Because Oppo locked it down!
You should have done research before buying a phone. If you wanted root, Xposed, custom ROM, etc
celoxocis said:
NO!!! You will brick your phone!
Different manufacturer totally different signature's!
There is no way! Because Oppo locked it down!
You should have done research before buying a phone. If you wanted root, Xposed, custom ROM, etc
Click to expand...
Click to collapse
Yeah i just bought it cuz people said it is the best phone in medium budget... and it is popular....
but if anything happens to my phone i won't be able to install even stock rom in it with PC....
can i atleast port twrp for my device to get root and randroid backup functions which i really want...?????
hamzachaudhry36 said:
Yeah i just bought it cuz people said it is the best phone in medium budget... and it is popular....
but if anything happens to my phone i won't be able to install even stock rom in it with PC....
can i atleast port twrp for my device to get root and randroid backup functions which i really want...?????
Click to expand...
Click to collapse
NO! Again! for TWRP to work you need an unlocked bootloader which you don't have and can't have because of Oppo removing fastboot!
Return your phone and get a different phone.
Avoid Oppo at all costs!
I suggest Asus Zenfone 2 it has all you want and even official CyanogenMod support!
It's close to the specifications of the a37f.
https://wiki.cyanogenmod.org/w/Z00L_Info
And stop using so many questions marks!
It only makes you look stupid.
celoxocis said:
NO! Again! for TWRP to work you need an unlocked bootloader which you don't have and can't have because of Oppo removing fastboot!
Return your phone and get a different phone.
Avoid Oppo at all costs!
I suggest Asus Zenfone 2 it has all you want and even official CyanogenMod support!
It's close to the specifications of the a37f.
https://wiki.cyanogenmod.org/w/Z00L_Info
And stop using so many questions marks!
It only makes you look stupid.
Click to expand...
Click to collapse
Thanks but it won't be refunded in my country. So i am stuck. I can get Samsung J5 2015 which is rooted and has many functions which i like from my brother in exchange of it but Oppo provides many functions which samsung does not like Oppo has almost no bloatwares, Built-in app locker, more ram, 4G, built-in customizations, and a camera that is the best.
Thanks for all the help. I just wanted to confirm, my friend said that we can make a port of twrp so i asked.
and i am an idiot and a noob so i use many question marks sometimes
First of all I apologize for my bad English
Remember that you have to have the bootloader unlocked to make this process
We started;
1 - DOWNLOAD THIS FILE
Oficial EGTV - http://bit.ly/OficialROOTP9EGTV
-
Mirror - http://bit.ly/Mirror2ROOTp9
2 - Put the phone in fastboot mode
Power off device
Press the volume button down and keep
USB connected to the computer, connect the phone, hold the volume down
3- INSTALL TWRP
Open folder 1
Doble click in windows the .bat file.
4- INSTALL SUPER SU
Open FOLDER 2
Take the .zip in the Micro SD or USB OTG (Internal memory TWRP not mounted)
Enter TWRP turning off the device, turn it on by pressing volume up
Press install
Search the .ZIP file SuperSU
SCREENSHOOT
{
"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"
}
NOTE:
2 reboots after installing the SuperSU
TWRP mini bug No internal memory detected
FOLDER 3 IS INSTALL RECOVERY STOCK - EVA-L09 MODEL
Video installation SPANISH
https://www.youtube.com/watch?v=tsE4XWbo5oE
DEVICE TREE: https://github.com/huawei-dev-kirin/android_device_huawei_eva
Sorry my bad English
Regards the ELOYGOMEZ!
Thanks for this tutorial ?? @djeloy
Thx! This is great
Could anyone point me to a guide on how to unlock the bootloader? Also is it possible to relock the bootloader without evidence? Point is to keep warranty intact.
cheers
clouds5 said:
Thx! This is great
Could anyone point me to a guide on how to unlock the bootloader? Also is it possible to relock the bootloader without evidence? Point is to keep warranty intact.
cheers
Click to expand...
Click to collapse
this would be really interesting! on P8 and Mate 8 it was possible to unlock and relock with DC-Unlocker and bootloader did not show "RELOCKED", instead it showed "LOCKED" like never unlocked before. i hope this also works on the P9. maybe some brave one could try this.
in response to my e-mail i sent to DC-Unlocker support i got the following answer:
On Tue, Apr 26, 2016 at 10:39 AM, xxxxxxx wrote:
Hello!
Do you know when you will support Huawei P9 bootlaoder unlock / relock (with "LOCKED" in bootloader menu)?
greets
Click to expand...
Click to collapse
Hello,
Download this HCU tool https://files.dc-unlocker.com/share.html?v=share/B94BAEFE0A754B33AD2D62DBFC609355 detect phone on it and try to read bootloader code from there.
Click to expand...
Click to collapse
It seems to be simple guide, but...First question-how i can unlock bootloader on P9, to get that guide work???
Thanks!
DC-unlocker has already support for p9 unlocking. or maybe e-mail huawei like on the last models.
Gesendet von meinem EVA-L09 mit Tapatalk
i got already payed unlock code for bootloader, but if i try to unlock with fastboot oem unlock (and my unlock code),
i got always error msg - "FAILED (remote: Command not allowed)
finished. total time: 0.015s"
What could be here wrong?
ValVK said:
i got already payed unlock code for bootloader, but if i try to unlock with fastboot oem unlock (and my unlock code),
i got always error msg - "FAILED (remote: Command not allowed)
finished. total time: 0.015s"
What could be here wrong?
Click to expand...
Click to collapse
Did you set the switch to unlock in developer settings? its easy to forget
Ah,ye-that is, my old bad head...
Thank you!
ValVK said:
Ah,ye-that is, my old bad head...
Thank you!
Click to expand...
Click to collapse
no problem... i know i've done it before... struggled for hours with other phones... and then was like duh.......
If the phone is rooted will this also unlock it from the network?
UK.
02 selling the phone for £369.99 which is way cheaper than £449 from Huawei or CarphoneW.
thus tempted to buy and then root IF this will also unlock phone?
or..
how would I simply unlock the phone for any network ?
Hello all, i Unlock the BL of my phone, but now, i have a message, in orange letter say to me that my hone can't be trusted. What that message ?
sorry for my poor english)
would it be also possible to just boot the twrp (fastboot boot twrp.img) instead on flashing it? for rooting with supersu it should be enough to flash it once with a bootet twrp and the original recovery would be intact. this would be better for OTAs so we don`t have to revert every time to stock recovery.
also interesting would be the fastboot commad to backup the original recovery (and maybe the other partitions too)!
edit: just booting twrp does not work, you have to flash it.
what do we have to do for a OTA update? unroot with supersu and flash back stock recovery?
Has anyone tried this way? http://www.sadroid.com/how-to-root-huawei-p9-in-5-minutes/
Is there any roms made yet?
strictlys said:
Has anyone tried this way? http://www.sadroid.com/how-to-root-huawei-p9-in-5-minutes/
Is there any roms made yet?
Click to expand...
Click to collapse
seriously ... this method gives you confidence?
Enviado desde mi EVA-L09 mediante Tapatalk
gingermobile said:
If the phone is rooted will this also unlock it from the network?
UK.
02 selling the phone for £369.99 which is way cheaper than £449 from Huawei or CarphoneW.
thus tempted to buy and then root IF this will also unlock phone?
or..
how would I simply unlock the phone for any network ?
Click to expand...
Click to collapse
just a heads up I hear O2 phones are usually bootloader locked
So with this dc unlocker tool, can I relock the bootloader without leaving evidence of it being unlocked? Seems like the most efficient method to me...
King p1n said:
just a heads up I hear O2 phones are usually bootloader locked
Click to expand...
Click to collapse
Bootloader unlocked and network unlocked are two separate things.
scook94 said:
Bootloader unlocked and network unlocked are two separate things.
Click to expand...
Click to collapse
I didn't say they were the same?
Phones from O2 usually have bootloaders that are permanently locked, with no way to unlock
Which I was drawing the person's attention too, as this method requires an unlocked bootloader for example.
King p1n said:
just a heads up I hear O2 phones are usually bootloader locked
Click to expand...
Click to collapse
King p1n said:
I didn't say they were the same?
Phones from O2 usually have bootloaders that are permanently locked, with no way to unlock
Which I was drawing the person's attention too, as this method requires an unlocked bootloader for example.
Click to expand...
Click to collapse
Okay, I thought you were replying specifically to the OP's query.
MOD EDIT: LINK REMOVED
Per the forum rules:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
THREAD CLOSED
I watched the same video. My phone came from Sprint with the bootloader already unlocked. Hmm
Sent from my Essential Phone using XDA Labs
Updated OP with important info regarding the vendor ID and fastboot not recognizing the PH-1
CRasH180 said:
I watched the same video. My phone came from Sprint with the bootloader already unlocked. Hmm
Click to expand...
Click to collapse
Interesting. The gf bought one from Sprint Saturday and the bootloader is locked.
Those having issues with adb or bootloader, may need to update drivers for such
Figured out my issue no worries
Just in case you were wondering, relocking your bootloader WILL wipe your device.
I updated my drivers and it is still not recognizing it in fastboot. Any suggestions?
mangordi8901 said:
I updated my drivers and it is still not recognizing it in fastboot. Any suggestions?
Click to expand...
Click to collapse
Which drivers are you using? I had to download the Google USB Driver and then manually select Bootloader from the the Driver Selection screen in Devices.
notjaykay said:
Which drivers are you using? I had to download the Google USB Driver and then manually select Bootloader from the the Driver Selection screen in Devices.
Click to expand...
Click to collapse
That's the one that I chose, the 11.0 version
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Did you see my thread?
https://forum.xda-developers.com/es...nofficial-usb-drivers-essential-ph-1-t3678231
Sent from my PH-1 using XDA Labs
updating the drivers manually like in your thread did the trick. Thanks!
In case anyone is trying this on a Mac, you need
1: The latest SDK Platform-tools for Mac
2: cd to platform-tools in terminal and enter: ./adb devices
(I couldn't get my Mac to discover my phone at all in ADB until I used ./ before the command, which I never had to do with other phones.
I was able to discover the device in fastboot without these steps and ./, but only when entering the vendor id, and the unlock command failed with or without the id.)
3: Once you see your ADB device show in terminal, you should get the prompt on your PH1 screen to allow your Mac to access it.
4: You should now be able to reboot to fastboot from the terminal using: ./adb reboot bootloader
5: Check device again: ./fastboot devices
6:. Lastly: ./fastboot flashing unlock (vendor id was not needed for me)
Hope this helps.
notjaykay said:
Just in case you were wondering, relocking your bootloader WILL wipe your device.
Click to expand...
Click to collapse
Does unlocking bootloader wipe the device also? Thanks
treIII said:
Does unlocking bootloader wipe the device also? Thanks
Click to expand...
Click to collapse
Yes it does. It'll warn you too when you do the lock or unlock code.
Can anyone help?
PM1LHMA790900113 is what it says my device is
This is a sprint essential ph1
2.0.c4-M1.3. 1 baseband version
4.4.21-perf+
[email protected] #1 kernel version
Android version 7.1.1
BOOTLOADER WILL NOT UNLOCK
---------- Post added at 12:38 AM ---------- Previous post was at 12:36 AM ----------
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Same problem... Can anyone help?
This is my problem...
CRasH180 said:
I watched the same video. My phone came from Sprint with the bootloader already unlocked. Hmm
Sent from my Essential Phone using XDA Labs
Click to expand...
Click to collapse
https://ibb.co/hCqviR
https://ibb.co/dwRqHm
{
"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"
}
Can anyone help? I cannot unlock my bootloader...
ampink7756 said:
https://ibb.co/hCqviR
https://ibb.co/dwRqHm
Can anyone help? I cannot unlock my bootloader...
Click to expand...
Click to collapse
Have you looked at the video by Chris Panton on unlocking your bootloader?
https://www.youtube.com/watch?v=_DNWCqSAAVM?
This video explains how to unlock your bootloader. There is also the post on Essential's official advice on unlocking the boot loader: https://forum.xda-developers.com/essential-phone/how-to/essential-bootloader-unlock-official-t3671997
Hope that helps,
CRasH180
This is the video I watched
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
CRasH180 said:
Have you looked at the video by Chris Panton on unlocking your bootloader?
https://www.youtube.com/watch?v=_DNWCqSAAVM?
This video explains how to unlock your bootloader. There is also the post on Essential's official advice on unlocking the boot loader: https://forum.xda-developers.com/essential-phone/how-to/essential-bootloader-unlock-official-t3671997
Hope that helps,
CRasH180
Click to expand...
Click to collapse
This is the video I used, but I believe the problem is that I'm using a sprint phone... Please see my other posts...
I have benn using Pixels since 2XL.
I am used to images being released immediately and where to get them from Google.
I havent had a OP since OP2.
I now have a TMob 8T, bootloader is unlocked, but I havent considered rooting yet as I cant find images anywhere.
Should I expect them to appear on OnePlus's website?
I would appreciate it if anyone has any historical knowledge.
thanks
parakleet said:
I have benn using Pixels since 2XL.
I am used to images being released immediately and where to get them from Google.
I havent had a OP since OP2.
I now have a TMob 8T, bootloader is unlocked, but I havent considered rooting yet as I cant find images anywhere.
Should I expect them to appear on OnePlus's website?
I would appreciate it if anyone has any historical knowledge.
thanks
Click to expand...
Click to collapse
How exactly did you bootloader unlock your device? OP's site is drunk for everybody how did you do it? Or do you mean to say that you are SIM unlocked?
I tweeted tmobile help
Explained to them I am a developer and purchased this phone because I want to get root access
They asked me to pay it off, so I did.
They unlocked the sim
Them OEM unlock switch became active
I did the fastboot commands and here I am trying to figure out how to root
parakleet said:
I tweeted tmobile help
Explained to them I am a developer and purchased this phone because I want to get root access
They asked me to pay it off, so I did.
They unlocked the sim
Them OEM unlock switch became active
I did the fastboot commands and here I am trying to figure out how to root
Click to expand...
Click to collapse
Ok, you basically are a step before unlocking the bootloader, the device comes with a locked bootloader and you must request a Bootloader unlock token from OnePlus to be able to unlock the bootloader, the problem is that their site is completely drunk and keeps giving everybody the same error so as of now there is no way to unlock the bootloader
Here you can read how to unlock and bootloader for a OnePlus device purchased from T-Mobile
https://support.oneplus.com/app/ans...-to-unlock-bootloader-for-oneplus-smart-phone
Not be of which is my concern per my original post
The thread has gone off topic.
Again
I'm concerned about images
parakleet said:
Not be of which is my concern per my original post
The thread has gone off topic.
Again
I'm concerned about images
Click to expand...
Click to collapse
You can't root before being bootloader Unlocked
SmileBigNow said:
You can't root before being bootloader Unlocked
Click to expand...
Click to collapse
Yes I know that.
Again what you are discussing is not the topic of this thread.
parakleet said:
Yes I know that.
Again what you are discussing is not the topic of this thread.
Click to expand...
Click to collapse
You need to do two things, first, please stop being rude. People are trying to help you so don't be a butt. Second, you have to boot a TWRP img, DD your current booted kernel image, patch it with magisk, boot the patched img. Then direct install via magisk. As a developer you should not have any issues, but as the previous people said, you need to wait for an unlock bin to unlock your bootloader or you cannot flash anything. And thus no ROOT.
Soooooo, once you get the code, actually unlock your bootloader then boot TWRP and dd your boot image.
And remember,
Be nice
My BL is unlocked
{
"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"
}
SmileBigNow said:
Ok, you basically are a step before unlocking the bootloader, the device comes with a locked bootloader and you must request a Bootloader unlock token from OnePlus to be able to unlock the bootloader, the problem is that their site is completely drunk and keeps giving everybody the same error so as of now there is no way to unlock the bootloader
Here you can read how to unlock and bootloader for a OnePlus device purchased from T-Mobile
https://support.oneplus.com/app/ans...-to-unlock-bootloader-for-oneplus-smart-phone
Click to expand...
Click to collapse
I have gotten the Network Unlocked and can boot into fastboot.
Using the command: fastboot.exe oem get_unlock_code
I get: < waiting for device >
I've used adb to do some debloating so the USB drivers seem to be working.
Anyway to determine the root cause (other then my ignorance
SmileBigNow said:
Ok, you basically are a step before unlocking the bootloader, the device comes with a locked bootloader and you must request a Bootloader unlock token from OnePlus to be able to unlock the bootloader, the problem is that their site is completely drunk and keeps giving everybody the same error so as of now there is no way to unlock the bootloader
Here you can read how to unlock and bootloader for a OnePlus device purchased from T-Mobile
https://support.oneplus.com/app/ans...-to-unlock-bootloader-for-oneplus-smart-phone
Click to expand...
Click to collapse
Can I unlock my KB2007? I'm not from the US but a friend gave me one as a gift. Now I can't use it because it's locked by T Mobile. What can I do? Is there a safe way to root it? I don't even use T Mobile and this carrier isn't in my country.
highland180 said:
I have gotten the Network Unlocked and can boot into fastboot.
Using the command: fastboot.exe oem get_unlock_code
I get: < waiting for device >
I've used adb to do some debloating so the USB drivers seem to be working.
Anyway to determine the root cause (other then my ignorance
Click to expand...
Click to collapse
Have you rebooted the phone into fastboot?
adb reboot bootloader
If you have it sound like a driver error.
Gabrielguti said:
Can I unlock my KB2007? I'm not from the US but a friend gave me one as a gift. Now I can't use it because it's locked by T Mobile. What can I do? Is there a safe way to root it? I don't even use T Mobile and this carrier isn't in my country.
Click to expand...
Click to collapse
As I have understood it from other threads on here, you need to get it sim unlocked with the help of TMobile first and then you can request a bootloader unlock token from oneplus. This seem to be difficult to do even for legit customers see https://forum.xda-developers.com/t/t-mobile-bootloader-unlock.4181339/
You need a unlocked booloader to root it or convert to a non T-Mobile rom.
Please all, lets keep it on topic and with respect.
Thanks for your help.
I have an alcatel 1b which I am trying to install Magisk and TWRP on (any decent guides on that would be appreciated).
I'm told I first need to unlock the bootloader.
I am on a mac so I have installed ADB via homebrew
If I run
Code:
adb devices
, the device shows up.
I then run
Code:
adb reboot bootloader
and the device boots up into a screen which says "fastboot mode" at the top
I then try
Code:
fastboot oem unlock
and get
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I tried
Code:
fastboot flashing unlock
and
Code:
fastboot oem unlock-go
and
Code:
fastboot oem get_unlock_code
and get the same response.
I also tried
Code:
ADB fastboot flashing unlock
and got
Code:
ADB: unknown command fastboot
If I enter recovery mode and then select "enter fastboot" I get a different screen with big red text saying "fastbootd" at the top.
If I then try
Code:
fastboot oem unlock
I get
Code:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Anybody know what I'm doing wrong/what I can do to get past this?
Same issue here!?
same here its because the bootloader is not unlocked and queries all say it is we need a backup or pull of someones boot.img to make a magisk boot img for our particular phone (seoul tct alcatel 5002s 1b) greatly appreciated if i could get a copy of that
To get Fastboot working try to use Alcatel's USB Driver
Download Alcatel USB Driver for Windows (Latest Driver)
Download the latest and original Alcatel USB Driver to connect any Alcatel Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
I'm also having the exact same issue. Anyone have a solution yet?
jokey carrot said:
I'm also having the exact same issue. Anyone have a solution yet?
Click to expand...
Click to collapse
Try fastboot flashing unlock-critical, I'm sceptical of it'll work
this is a goid phone to remove bloatware ob and use it for simple things, like an MP3 player. can someone pull the boot.img or show me where i can learn how to do it myself? and how would i patch it with Magisk?
i may just be a newbie, but doesnt putting the device in download mode let you flash anything? could i be able to flash majisk and obtain root while in download mode? or flash TWRP?
I am hoping to unlock the bootloader and use any customer recovery like TWRP or orangefox. Also Alcatel 1b 5002s (Canada) firmware would greatly appreciate if some one can help?
Its not yet possible to unlock the bootloader. For the past year i worked hard to figure this phone out. All of that lead to this
new link down below, the original file had alcatel protection not removed causing imei loss
that file contains firmware, flash tools and has intstructions on how to restore a lost imei.
Hope it helps you. You can also try to look at the bootloader file and try to unlock the phone.
If you need anything more feel free to dirrect message
KashiNEC said:
Its not yet possible to unlock the bootloader. For the past year i worked hard to figure this phone out. All of that lead to this
.........................................................................
that file contains firmware, flash tools and has intstructions on how to restore a lost imei.
Hope it helps you. You can also try to look at the bootloader file and try to unlock the phone.
If you need anything more feel free to dirrect message
Click to expand...
Click to collapse
Where is the firehose loader.bin file located?
I made an error zipping the file. New link here
It is in description
*firehose included*
I have noticed that in other devices they manage to unlock the bootloader through the EDL mode, who removes and needs to perform Test Point or needs more than that, for example a special EDL cable may be necessary, this morning I was trying to backup my Stock ROM with the Inferno Unitool, the funny thing is that it recognized the port but I don't know, it seemed that something else was missing, in the end I ended up flashing the @KashiNEC ROM with the guide of your audit. I'm still interested in installing GSI to at least get an upgrade to A12, I won't give up in the meantime.
Alain+ said:
I have noticed that in other devices they manage to unlock the bootloader through the EDL mode, who removes and needs to perform Test Point or needs more than that, for example a special EDL cable may be necessary, this morning I was trying to backup my Stock ROM with the Inferno Unitool, the funny thing is that it recognized the port but I don't know, it seemed that something else was missing, in the end I ended up flashing the @KashiNEC ROM with the guide of your audit. I'm still interested in installing GSI to at least get an upgrade to A12, I won't give up in the meantime.
Click to expand...
Click to collapse
For now its is not possible to unlock. Alcatel/TCL have clearly thought of someone dumping the system and have taken measures. boot partition doesnt contain the usual "unlock" stuff and bootloader seems to be modified and needs to be signed for the phone to accept it. The only thing you can do is upgrade to the newer russian version of the firmware by changing traceability.bin. But theres a little bit of hope. The bootloader makes a few references to a "secret key" and that it needs to be updated. If we can somehow get the secret key, we can unlock
This device is full of secrets everywhere, it obviously looks like a safe.
{
"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"
}
There were days when I knew there was an engineer mode, however I didn't know how to access that corner, until with the utility shown in the image, I also got the code: *#*#825364 #*#* although not much can be done with this...
Alain+ said:
This device is full of secrets everywhere, it obviously looks like a safe.
View attachment 5685055
There were days when I knew there was an engineer mode, however I didn't know how to access that corner, until with the utility shown in the image, I also got the code: *#*#825364 #*#* although not much can be done with this...
Click to expand...
Click to collapse
Interesting discovery. I think i got how to unlock bootloader now. There is a hidden app on this device called TCL TOKEN. It enables you to unlock bootloader, but requires a valid connection. I couldnt get it to connect
KashiNEC said:
Interesting discovery. I think i got how to unlock bootloader now. There is a hidden app on this device called TCL TOKEN. It enables you to unlock bootloader, but requires a valid connection. I couldnt get it to connect
Click to expand...
Click to collapse
I'm in the same situation. It seems that something else is missing or that service is disabled.
For a moment I thought it was my connection or that I was doing something wrong.