Database Info

Inaccessible function

Hello
Unfortunately after rooting my honor 6x the standby function (standby timming) is grayed. I can't access this.
how to recovery this option ? i tried to reset identification info but don't work.
Thanks

boubaka said:
Hello
Unfortunately after rooting my honor 6x the standby function (standby timming) is grayed. I can't access this.
how to recovery this option ? i tried to reset identification info but don't work.
Thanks
Click to expand...
Click to collapse
Can you provide a screenshot?

Developer option inaccessible
Oem unlocking option is Grey out
Help me resolve my issue because of which i cant use adb commands n other so many thing
It would be a favor if you will help me.
{
"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"
}

nagrale.prem said:
Oem unlocking option is Grey out
Help me resolve my issue because of which i cant use adb commands n other so many thing
It would be a favor if you will help me.
Click to expand...
Click to collapse
As much as I know once you updated into nougat rooted, the OEM function is greyed out but you will retain the unlock bootloader functions. Its the same with mine the oem function is also greyed out but I can use ADB Commands on it. Try booting into fastboot then use adb then type adb devices to make sure if its detected. If not, maybe you have no driver installed or hiSuite?

darKz22 said:
As much as I know once you updated into nougat rooted, the OEM function is greyed out but you will retain the unlock bootloader functions. Its the same with mine the oem function is also greyed out but I can use ADB Commands on it. Try booting into fastboot then use adb then type adb devices to make sure if its detected. If not, maybe you have no driver installed or hiSuite?
Click to expand...
Click to collapse
Hisuit is installed but im not confirmed about driver
I tried adb device so my device havent detected
Plz will uh provide drivers link

nagrale.prem said:
Hisuit is installed but im not confirmed about driver
I tried adb device so my device havent detected
Plz will uh provide drivers link
Click to expand...
Click to collapse
Hey sorry for the wrong info on my previous reply. If you have Hisuite and the comp recognizes it, means the hisuite already installed yhe necesarry drivers so maybe you have not unlock the bootloader?

darKz22 said:
Hey sorry for the wrong info on my previous reply. If you have Hisuite and the comp recognizes it, means the hisuite already installed yhe necesarry drivers so maybe you have not unlock the bootloader?
Click to expand...
Click to collapse
I have already unlocked bootloader before when I was using marshmallow emui 4.0 and it have also root with twrp recovery then i have got official nought update emui 5.0 i have updated then after I'm getting such problems

darKz22 said:
Can you provide a screenshot?
Click to expand...
Click to collapse
Yes !
Here :
thanks

boubaka said:
Yes !
Here :
thanks
Click to expand...
Click to collapse
Hey for your problem I can see that the battert saver option is turned on. It automatically set the screen time off to 15 seconds. Turn off battery saver and this function will be unlocked
---------- Post added at 10:51 AM ---------- Previous post was at 10:47 AM ----------
nagrale.prem said:
I have already unlocked bootloader before when I was using marshmallow emui 4.0 and it have also root with twrp recovery then i have got official nought update emui 5.0 i have updated then after I'm getting such problems
Click to expand...
Click to collapse
Then the oem function being greyed out means you already unlocked bootloader so adb commands must work without issues. Naybe try booting to fastboot then in adb enter command fastboot oem unlock.

darKz22 said:
Can you provide a screenshot?
Click to expand...
Click to collapse
darKz22 said:
Hey for your problem I can see that the battert saver option is turned on. It automatically set the screen time off to 15 seconds. Turn off battery saver and this function will be unlocked
Click to expand...
Click to collapse
Whouaaaaa !! :laugh::good: it work completly fine !
tanks a lot !! :good:

boubaka said:
Whouaaaaa !! :laugh::good: it work completly fine !
tanks a lot !! :good:
Click to expand...
Click to collapse
Happy to help

Oem unlock greyed and cannot access
boubaka said:
Whouaaaaa !! :laugh::good: it work completly fine !
tanks a lot !! :good:
Click to expand...
Click to collapse
my battery saver is off and still the option cannot be accessed , please help

[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.

TMobile KB2007 Rooting options

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.

Question P11 [Solved] [HELP] Bootloader unlock, Unknown Command

Hi! I'm trying to unlock the bootloader of my Lenovo Tab P11 (TB-J606F, Latest software), but none of the command (without fastboot devices) works...
I've tried :
fastboot oem unlock
fastboot flashing unlock
Also, I got sn.img from zui website but it also didn't work.
When I type
fastboot flash unlock sn.img
(Which is based on their description)
{
"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"
}
FAILED (remote : unknown command)
I've tried both my laptop and desktop (which is all AMD-based) but nothing worked.
Is their any tips for me?
Thanks

I have Lenovo TB-J706F, maybe it's same.
I successfully installed TWRP and root.
Do you try fastboot oem unlock-go ?
Please read this and this.

d1m-ON said:
I have Lenovo TB-J706F, maybe it's same.
I successfully installed TWRP and root.
Do you try fastboot oem unlock-go ?
Please read this and this.
Click to expand...
Click to collapse
On my tablet the process failed, I don't know at what point.
I think because of the step of flashing vbmeta (I think) and now I can not even enter TWRP, it does not start Android and neither recovery, it only returns to fastboot every time it turns on.
Do you know any solution to this?
I have already tried to reinstall the OS with the Lenovo tool

byraan said:
On my tablet the process failed, I don't know at what point.
I think because of the step of flashing vbmeta (I think) and now I can not even enter TWRP, it does not start Android and neither recovery, it only returns to fastboot every time it turns on.
Do you know any solution to this?
I have already tried to reinstall the OS with the Lenovo tool
Click to expand...
Click to collapse
Well, I was able to fix it by making various combinations and attempts in the Qualcomm QFIL application until it answered correctly
Now I rooted without flashing vbmeta.img and the file no-verity-opt-encrypt.zip and it still works (those files gave me a bad feeling)

Congratulations! I didn't get it right the first time either.
Install TWRP, set up your tablet, make a copy in TWRP. Note that TWRP does not make a copy of the Storage folder - pictures, videos, music. But it makes and restores a copy of everything else perfectly. I had a chance to see this yesterday.

byraan said:
Well, I was able to fix it by making various combinations and attempts in the Qualcomm QFIL application until it answered correctly
Now I rooted without flashing vbmeta.img and the file no-verity-opt-encrypt.zip and it still works (those files gave me a bad feeling)
Click to expand...
Click to collapse
Um.. Did fastboot oem unlock-go worked in your case?

byraan said:
Well, I was able to fix it by making various combinations and attempts in the Qualcomm QFIL application until it answered correctly
Now I rooted without flashing vbmeta.img and the file no-verity-opt-encrypt.zip and it still works (those files gave me a bad feeling)
Click to expand...
Click to collapse
Where you bought your tablet?
Can you take a look insyde /system/app_backup folder? What apps are there? Give me a screenshot, please, if you don't mind, or just list it.

d1m-ON said:
I have Lenovo TB-J706F, maybe it's same.
I successfully installed TWRP and root.
Do you try fastboot oem unlock-go ?
Please read this and this.
Click to expand...
Click to collapse
Well, It still doesn't work..
fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.029s

jupitkr said:
Well, It still doesn't work..
fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.029s
Click to expand...
Click to collapse
A hour ago I was trying get serial number for TB-J606F on zui website and answer was: Enter correct serial numer, ahaha

d1m-ON said:
A hour ago I was trying get serial number for TB-J606F on zui website and answer was: Enter correct serial numer, ahaha
Click to expand...
Click to collapse
Oh I solved that problem by selecting Lenovo Phone(which is the first option : "Lenovo手机") and wrote imei1 000000000000000 (0*15). It worked in my case.

d1m-ON said:
A hour ago I was trying get serial number for TB-J606F on zui website and answer was: Enter correct serial numer, ahaha
Click to expand...
Click to collapse
And One more, Lenovo's mail would be in your spam mail folder!

jupitkr said:
And One more, Lenovo's mail would be in your spam mail folder!
Click to expand...
Click to collapse
Thank you, will try again. I know about Spam folder, was checked.
Did you manage to unlock it or not?
PS. Successfully received sn.img, thanks so much !!!

d1m-ON said:
Thank you, will try again. I know about Spam folder, was checked.
Did you manage to unlock it or not?
PS. Successfully received sn.img, thanks so much !!!
Click to expand...
Click to collapse
I'm happy to hear that.
I still failed to unlock it... Ahaha...
Can you try it on your device please?

jupitkr said:
I'm happy to hear that.
I still failed to unlock it... Ahaha...
Can you try it on your device please?
Click to expand...
Click to collapse
I have a different tablet. TB-J706F, I was trying to get a sn.img for a forum mate. He was going to try the unlock today. I will let you know the result when it happens.

d1m-ON said:
I have a different tablet. TB-J706F, I was trying to get a sn.img for a forum mate. He was going to try the unlock today. I will let you know the result when it happens.
Click to expand...
Click to collapse
Thanks. I'll wait for your reply!

jupitkr said:
Thanks. I'll wait for your reply!
Click to expand...
Click to collapse
jupitkr, I remember, look this: https://forum.xda-developers.com/t/pad-11-tb-j606f-unlock-magisk-rooooot.4288159/​

[None]

d1m-ON said:
jupitkr, I remember, look this: https://forum.xda-developers.com/t/pad-11-tb-j606f-unlock-magisk-rooooot.4288159/​
Click to expand...
Click to collapse
Thanks. Do you know what the firmware version is? Mine is 210421 but still doesn't work.
If it has lower version, I'll try downgrade.

jupitkr said:
Thanks. Do you know what the firmware version is? Mine is 210421 but still doesn't work.
If it has lower version, I'll try downgrade.
Click to expand...
Click to collapse
Asked him, waiting for answer...
PS Got answer! S120184_210520_ROW, upgraded two days ago.
PSS. Third user got unlock: https://4pda.to/forum/index.php?showtopic=1014576&view=findpost&p=107206283

d1m-ON said:
Asked him, waiting for answer...
PS Got answer! S120184_210520_ROW, upgraded two days ago.
PSS. Third user got unlock: https://4pda.to/forum/index.php?showtopic=1014576&view=findpost&p=107206283
Click to expand...
Click to collapse
No update available through OTA, so I'm flahsing the firmware by Lenovo rescue and smart assistant.

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.