Database Info

Guide - root huawei p9

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.

Verizon Bootloader Unlock

Is anyone else working on unlocking the bootloader for verizon pixels? Its clearly possible as people are doing it but but not releasing it publicly. All the other threads on this are locked because people keep trying to offer services outside of XDA. Are there theories on how its being done? Spoofing the verizon IMEI check server? Temp root and modifying a system file?

Quada said:
Is anyone else working on unlocking the bootloader for verizon pixels? Its clearly possible as people are doing it but but not releasing it publicly. All the other threads on this are locked because people keep trying to offer services outside of XDA. Are there theories on how its being done? Spoofing the verizon IMEI check server? Temp root and modifying a system file?
Click to expand...
Click to collapse
I have been poking around on google for a long time checking for Verizon bootloader unlock activity and I noticed that as well. This got me thinking, and while I haven't done a lot of digging to see if my idea if feasible here's what I got. I was thinking to leverage Spectre "https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)" somehow to leak a signature that can then be passed in an api call to unlock the bootloader. If i recall, I think I remember seeing a function in android source somewhere that took a prm specifying unlock/lock and then a signature created by the vendor to allow the unlock. if you could figure out the appropriate offsets in memory, maybe it would be possible? As said, I have not done much research on this but just figured I'd share and see what others thought.

Pixel 2 Verizon unlock bootloader instructions are here below
Unlocking the Bootloader WILL WIPE YOUR DEVICE!! so backup important files.
Install ADB/Fastboot Drivers
Enable Developer Options
Enable USB Debugging in Developer Options
Plug Pixel 2 into PC
Open a Command Prompt window;
In Command Prompt, type adb start-server
and hit ENTER
If you see * daemon started successfully *
continue to next step
In Command Prompt, type adb devices
and hit ENTER
If you see "List of devices attached" as well as "Your Devices Serial Number device or unauthorized"
continue to next step
On Pixel 2 - Allow PC for USB Debugging
In Command Prompt, type adb reboot bootloader
Once your Pixel 2 has rebooted into the bootloader
In Command Prompt, type fastboot flashing lock_critical
and hit ENTER Then follow the instructions on your Pixel 2 to finish Unlocking Bootloader.
Correct on the steps, including the entire discussion found here. https://forum.xda-developers.com/pix...el-2s-t3726294
***PATCHED BY OUT-OF-CYCLE JANUARY UPDATE***
If you have received the OTA patch for your pixel2, and now are on OPM2.171019.016, you will no longer be able to run the command. And downgrade is not available at this time.
As of 1/24/2018 users who have purchased new phones have been able to remove the SIM, refuse internet (WiFi) connection at the initial startup. After completing the initial setup, you can sideload 8.1 to take advantage of the command in the OP. If you connect to the internet with WiFi or with your SIM, chances are high you will receive the update and this method WILL NOT work. To date, there are no other ways to unlock the bootloader on VZW PIX2 other than this method. Instructions to sideload stock OTA's are found here along with the downloads. https://developers.google.com/android/ota Once again, DO NOT USE 8.1.0 (OPM2.171019.016, Jan 2018, Verizon) but instead use 8.1.0 (OPM1.171019.013, Jan 2018) The command is not available on 8.0.
There is also another alternative way which has worked for me this week on Pixel 32GGB Verizon. Its called depixel8. more info can be found @ http://theroot.ninja/depixel8.html
Usage:
Step 1) Install fastboot and adb on your PC, ensure both are working with your Pixel.
Step 2) Run "adb push dePixel8 /data/local/tmp", "adb shell chmod 755 /data/local/tmp/dePixel8" and finally run the program "adb shell /data/local/tmp/dePixel8"
(put the depixel files in the same folder as your ADB/FASTBOOT drivers are where you do your command prompt commands)
Step 3) Wait for the phone to reboot to the bootloader. If it is not rebooting you can try to run various apps until it does, or you may have to reboot and start over.
Step 4) Issue the command "fastboot oem unlock", this will open up the unlock prompt and warning on the screen. You can now unlock. If you get an error, about unlocking not being allowed, start all over again.

MpandAUS said:
Pixel 2 Verizon unlock bootloader instructions are here below
Click to expand...
Click to collapse
dePixel8 is patched in Android 7.1.1 and newer.

lock bootlooader without power button
How can i relock my bootloader without use of my power button its broken

Keetoowah said:
How can i relock my bootloader without use of my power button its broken
Click to expand...
Click to collapse
Are you rooted?

Keetoowah said:
How can i relock my bootloader without use of my power button its broken
Click to expand...
Click to collapse
I personally recommend not relocking your bootloader. If you aren't on pure stock it will give you problems and even if you are on pure stock, an unlocked bootloader is a devices most powerful recovery tool and OTAs have been known to fail on occasion and other problems you would want to recover from can occur.
As to the answer to your question, if you can boot the device normally at all then you can turn on adb debugging and from there open an adb shell and use adb reboot bootloader to get to fastboot mode and then use fastboot oem lock I believe

KittyRgnarok said:
I personally recommend not relocking your bootloader. If you aren't on pure stock it will give you problems and even if you are on pure stock, an unlocked bootloader is a devices most powerful recovery tool and OTAs have been known to fail on occasion and other problems you would want to recover from can occur.
As to the answer to your question, if you can boot the device normally at all then you can turn on adb debugging and from there open an adb shell and use adb reboot bootloader to get to fastboot mode and then use fastboot oem lock I believe
Click to expand...
Click to collapse
Thank I've decided to have the power button repaired at my own expence since I have a Verizon Pixel 2 with an unlocked bootloader. The replacement they sent me wasn't unlockable. The unlocked bootloader with TWRP and root are well worth the price of the power button.

Keetoowah said:
Thank I've decided to have the power button repaired at my own expence since I have a Verizon Pixel 2 with an unlocked bootloader. The replacement they sent me wasn't unlockable. The unlocked bootloader with TWRP and root are well worth the price of the power button.
Click to expand...
Click to collapse
How much was the replacement button and installation by the way, I'm rather curious

getting back on track, it looks like someone claims to be able to OEM unlock after getting the April OTA? Can anyone support or contradict this claim? https://www.reddit.com/r/GooglePixel/comments/89rnoa/google_pixel_verizon_oem_unlock/

[GUIDE] unlock your G7 bootloader

Now Motorola supported has updated to support G7. You should be able to unlock open market model.
Prerequisites:
1. ADB installed
2. Motorola drivers installed
3. Your phone has enabled OEM unlock (hit build number few times to enable developers options) and USB debugging
4. Backup your internal storage. ALL PERSONAL DATA ON INTERNAL STORAGE WILL BE WIPED DURING OEM UNLOCK PROCESS!
----------------
Process:
1. Enter bootloader. After your phone connected to host computer, use the following:
Code:
adb devices
After your phone has been shown up, use the following command to enter bootloader
Code:
adb reboot bootloader
2. Retrieve your phone unlock data and submit
Go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Retrieve your phone unlock data using the following and open notepad or any text editor
Code:
fastboot oem get_unlock_data
You should see 5 lines of data starting (bootloader). Right click and mark the data on the line 2-5, drag until all data highlighted and right click once.
Paste the 4 line data on your favorite text editor and locate the cursor to the end of the line and press delete once, and repeat until 4 lines of data become a single line, and press Ctrl+a (select all) followed by Ctrl+c (copy)
Paste the single line to the box under #6 and verify. Accept the terms and press the blue button
3. Unlock your bootloader
After the unlock code delivered, highlight and copy 20 characters code
Enter the following command and press space once and paste the code
Code:
fastboot oem unlock
It should be fastboot oem unlock XXXXX (20 characters code)
You have to enter same command again to finish the process.
Your phone bootloader now unlocked and it's ready to install root

is there a way to relock once unlocked?

shaDNfro said:
is there a way to relock once unlocked?
Click to expand...
Click to collapse
Yes. fastboot oem lock but doing so will wipe the device back to factory settings.

adb backup -all
will back up your phone to a cable connected laptop. Is there anything else one needs to back up before unlocking the bootloader wipes your data off the phone?
**Specifically, will it backup
1. Documents folder
2. Download folder
3. Other custom created folders like saved photographs, etc.
Thank you.

For anyone looking at this thread and wondering, yes, Amazon branded device's bootloaders can be unlocked.

Could someone with an unlocked bootloader test out how well the Android Q GSI works?

kaiomatico said:
Could someone with an unlocked bootloader test out how well the Android Q GSI works?
Click to expand...
Click to collapse
Until a custom recovery is created, we're stuck on stock

Omegapsy said:
Until a custom recovery is created, we're stuck on stock
Click to expand...
Click to collapse
Nope, the beauty of GSI's are that you can simply do an "fastboot flash system NameOfGSI.img" and the rom is flashed. No need for a custom recovery

Now that TWRP is finally available I'm picking up my courage to unlock and root my Moto G7. Thank you for all your instructions here and in the root thread.
Because I'm not an android expert and am scared I want to be sure I understand everything correctly.
1. ADB is installed and works. (I used adb to create an adb backup to my laptop).
2. Not sure what you mean by installing Motorola drivers. (I can see the Moto G7 when I connect it by cable to my W 10 laptop).
4. Backing up:
I used a cable connection to copy all the visible files to my laptop using Windows file explorer. I also have the adb backup mentioned above.
Final question:
What will need to be restored after unlocking the bootloader? Everything I backed up or only parts?
Thank you.

I would appreciate someone helping to answer @maybeme2 questions above in post #9. Specifically question 2 about drivers. I've downloaded the Lenovo MOTO Smart Assistant and can ADB connect to my device. However when I set the device to fastboot mode then the connection is dropped.

5 seconds delay on boot after unlocking bootloader
I unlocked my bootloader using the excellent instructions above. But now, everytime I reboot I get a screen that says
Your device has been unlocked and can't be trusted.....
ID (is blank)
your device will boot in 5 seconds.
bad key
Click to expand...
Click to collapse
How do I get rid of that?
Thanks.

maybeme2 said:
I unlocked my bootloader using the excellent instructions above. But now, everytime I reboot I get a screen that says
How do I get rid of that?
Thanks.
Click to expand...
Click to collapse
That's part of unlocking and that warning is there for a reason. That said you can either relock or find another logo.bin to flash that covers it up. Flashing another logo.bin does not make your phone secure again it's just cosmetic.

ptn107 said:
That's part of unlocking and that warning is there for a reason. That said you can either relock or find another logo.bin to flash that covers it up. Flashing another logo.bin does not make your phone secure again it's just cosmetic.
Click to expand...
Click to collapse
Thank you for replying.
My next step is to root the phone. Will that get rid of it?
If not, where do I get another compatible logo.bin?
Thank you again.

maybeme2 said:
Thank you for replying.
My next step is to root the phone. Will that get rid of it?
If not, where do I get another compatible logo.bin?
Thank you again.
Click to expand...
Click to collapse
It will not remove the warning. In fact rooting is even less secure fyi.
You'll have to search on xda for a modified logo.bin.

ptn107 said:
It will not remove the warning. In fact rooting is even less secure fyi.
You'll have to search on xda for a modified logo.bin.
Click to expand...
Click to collapse
Less secure than letting Google access all my data? ? I have firewalls and tools to protect me. I'm just new to Moto.

maybeme2 said:
Thank you for replying.
My next step is to root the phone. Will that get rid of it?
If not, where do I get another compatible logo.bin?
Thank you again.
Click to expand...
Click to collapse
I used the information from this thread.
https://forum.xda-developers.com/moto-g7/themes/mod-custom-boot-logos-t3923110
The logo.bin file has several images. I found that the image named "orange" was the one displayed when my device boots.

cou94114 said:
I used the information from this thread.
https://forum.xda-developers.com/moto-g7/themes/mod-custom-boot-logos-t3923110
The logo.bin file has several images. I found that the image named "orange" was the one displayed when my device boots.
Click to expand...
Click to collapse
Thank you.
Does removing "orange" also remove the 5 second delay?

maybeme2 said:
Thank you.
Does removing "orange" also remove the 5 second delay?
Click to expand...
Click to collapse
I never said that I removed the image named "orange". I did extract the "orange" image from logo.bin, edited the orange.png to black out the warning text, replaced the orange.png file in logo.bin and then flashed the modified logo.bin "fastboot flash logo modified-logo.bin".
I concur with ptn107's recommendation that you lock your bootloader and return your device to stock. That way you won't have to wait the five seconds which seems to be your concern.

cou94114 said:
I concur with ptn107's recommendation that you lock your bootloader and return your device to stock. That way you won't have to wait the five seconds which seems to be your concern.
Click to expand...
Click to collapse
Yes it is the imposed delay that I objects to. I've had other rooted phones and none had this warning and delay after unlocking the bootloader. So it is not part of android but something added by Moto.
It's not a big deal, but an unnecessary annoyance which is why I asked in a moto thread.

Help me, I got oem unlock but I can't enable it!

[Guide] Unlocking the bootloader

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.

unlocking bootloader for Alcatel 1B

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.