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.
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
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...
Hi Guys,
first off i am no dev but i am a tech nerd and want to gain access to everything on my phone.
After some digging around i finally figured out how to Unlock the Bootloader of my Xiaomi Black Shark (Global Version).
The steps might vary for the Chinese Version but i guess they might be the same.
CAUTION! THIS WILL ERASE YOUR WHOLE DATA AND SETTINGS!
What you need:
Your Xiaomi Black Shark
Drivers installed (you can use the miunlock tool for that but dont need it to unlock the Bootloader)
ADB installed.
A Backup tool.
If you want to unlock the bootloader do the following:
First Backup all your files and Settings.
Go to Settings/System/About the Phone and Tap on the Build Number to gain Dev Settings
In the Dev Settings enbale USB Debugging and OEM Unlock.
Connect your device to your computer.
Install the ADB Drivers if you did not already do so
Open a command prompt as admin
Type in
Code:
adb devices
to see if your device is recognized. If not try again to install them through the MiUnlock tool.
If it is recognized it will look like this:
{
"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"
}
After that type
Code:
adb reboot bootloader
as soon as your phone restarts remove it from the USB Cable. Otherwise it might want to reboot right after you tried it.
Connect it to the cable again as soon as you are in Fastboot.
In your console type
Code:
fastboot flashing unlock
Type
Code:
fastboot reboot bootloader
or use the menu of the Bootloader to reboot to the Bootloader. As you will see your device is now unlocked.
thats it ?
Yes. That`s it. Proof right here https://i.imgur.com/tRgWSpi.jpg Unfortunately the forum wouldnt scale it down.
I would love to tamper with it further but unfortunately i can not backup the boot.img caused by missing root which i would need to install root with the Magisk Manager since there is no TWRP for it yet.
in china rom cant unlock, please tell me,.. thanks
siliwangi said:
in china rom cant unlock, please tell me,.. thanks
Click to expand...
Click to collapse
Seems it is different for the Chinese Version then. So im not able to help you since i do not have the Chinese Version.
Failed <Unlock is not allowed on device has sales on market!>
It happens on Black Shark CN version.
Zerohexer said:
Failed <Unlock is not allowed on device has sales on market!>
It happens on Black Shark CN version.
Click to expand...
Click to collapse
Like i already wrote under the MIUI Forum Post. It seems that the way to do this for the chinese Version is different and since i do not own the Chinese Version i can not test anything aside from that that would be way over my abilities.
Invisan said:
Yes. That`s it. Proof right here https://i.imgur.com/tRgWSpi.jpg Unfortunately the forum wouldnt scale it down.
I would love to tamper with it further but unfortunately i can not backup the boot.img caused by missing root which i would need to install root with the Magisk Manager since there is no TWRP for it yet.
Click to expand...
Click to collapse
If you already unlocked device and you want to try to root it you can download stock rom for your model (same build that you are using), extract boot.img, put it in your sdcard, install Magisk apk and patch it through the app, then move your patched-boot inside adb folder to your pc and flash it using fastboot; in order to can reboot device is probably that you need to format data, maybe not. But it´s possible too that device refuses permanently to boot and you need to flash the stock boot image again.
this is irritating, i believe Xiaomi or Blackshark itself should do something regarding this.
Hello guys, i am in the same situation. I have the Black Shark's chinese version and i'm stuck here "Failed <Unlock is not allowed on device has sales on market!>"
I have 2 days left to decide if i keep or not the phone but in this state (not rooted, and doesn't know if i could do it a day or not), i can't keep it.
If someone have a solution, i'll be really grateful and i'm sure i'm not the only one.
Thanks.
Yotatouch said:
Hello guys, i am in the same situation. I have the Black Shark's chinese version and i'm stuck here "Failed <Unlock is not allowed on device has sales on market!>"
I have 2 days left to decide if i keep or not the phone but in this state (not rooted, and doesn't know if i could do it a day or not), i can't keep it.
If someone have a solution, i'll be really grateful and i'm sure i'm not the only one.
Thanks.
Click to expand...
Click to collapse
Honestly?
Just return it. Community is almost dead, no root/unlocked bootloader, limited Google Services support (Google Home and Assistant have problems, Android Auto won't mirror).
There seemed to be a little hope with the unlocked bootloader but if that's achieved only on the Global version, it's useless to us unfortunately.
Invisan said:
Like i already wrote under the MIUI Forum Post. It seems that the way to do this for the chinese Version is different and since i do not own the Chinese Version i can not test anything aside from that that would be way over my abilities.
Click to expand...
Click to collapse
If you are willing to share some ideas to test and try to unlock the chinese version, I'd be very happy to help.
I have a chinese Black Shark.
Offical Xiaomi unlock tool seems to recognize the phone but gets an error at 99%
The command you provided gives the error someone else posted (about the market).
loriz said:
Honestly?
Just return it. Community is almost dead, no root/unlocked bootloader, limited Google Services support (Google Home and Assistant have problems, Android Auto won't mirror).
There seemed to be a little hope with the unlocked bootloader but if that's achieved only on the Global version, it's useless to us unfortunately.
Click to expand...
Click to collapse
Thank you for your feedback.
This is what will happen at the end... i still have 2 or 3 days left but if i don't have any hope, i'll probably do it with regrets cause i love the phone. Technically it is a monster and i don't get why people doesn't work harder on it to figure out how to root the chinese version.
is you phone is BlackShark 2 (helo),this one ,2 have rgb logo in back.
https://unwire.hk/2018/11/02/helo/shop_guide/
BlackShark 1 not have Global version
1 https://www.mi.com/blackshark/
2 https://www.mi.com/blackshark2/
Blackshark 1 has a global Version!
Band 20 LTE, an other rom and unlockable bootloader.
We only need twrp to flash gsi roms.
black shark versione globale banda 20
mi e arrivato ieri questo smartphone, ma fin dalla accensione non mi e piaciuto. italiano si c'è, multilingue ma un android stock non c'è praticamente nulla, si servizi google funzionanti, ma non ci sono impostazioni tipo miui in un telefono così e proprio un castrone.
inservibile praticamente, con una rom xiaomi.eu sarebbe il top, ma questi sviluppatori non si trovano nemmeno a pagarli.
Invisan said:
Hi Guys,
first off i am no dev but i am a tech nerd and want to gain access to everything on my phone.
After some digging around i finally figured out how to Unlock the Bootloader of my Xiaomi Black Shark (Global Version).
The steps might vary for the Chinese Version but i guess they might be the same.
CAUTION! THIS WILL ERASE YOUR WHOLE DATA AND SETTINGS!
What you need:
Your Xiaomi Black Shark
Drivers installed (you can use the miunlock tool for that but dont need it to unlock the Bootloader)
ADB installed.
A Backup tool.
If you want to unlock the bootloader do the following:
First Backup all your files and Settings.
Go to Settings/System/About the Phone and Tap on the Build Number to gain Dev Settings
In the Dev Settings enbale USB Debugging and OEM Unlock.
Connect your device to your computer.
Install the ADB Drivers if you did not already do so
Open a command prompt as admin
Type in
Code:
adb devices
to see if your device is recognized. If not try again to install them through the MiUnlock tool.
If it is recognized it will look like this:
After that type
Code:
adb reboot bootloader
as soon as your phone restarts remove it from the USB Cable. Otherwise it might want to reboot right after you tried it.
Connect it to the cable again as soon as you are in Fastboot.
In your console type
Code:
fastboot flashing unlock
Type
Code:
fastboot reboot bootloader
or use the menu of the Bootloader to reboot to the Bootloader. As you will see your device is now unlocked.
Click to expand...
Click to collapse
this metod is working thank you !!!!!
model skr-h0 international
the comand fastboot flashing unlock works !!!!!!
now we need the patched boot
patched_boot.img for the black shark please !!!!!
we need root
3B3RT said:
this metod is not working .
model skr-h0 international
the comand fastboot flashing unlock is not working
Click to expand...
Click to collapse
Well that is not really an answer we can help you with without Screenshots or an error message.
Invisan said:
Well that is not really an answer we can help you with without Screenshots or an error message.
Click to expand...
Click to collapse
it works !!!!
now we need a patched boot
patched_boot.img i hope someone do this
3B3RT said:
it works !!!!
now we need a patched boot
patched_boot.img i hope someone do this
Click to expand...
Click to collapse
Unfortunately BlackShark is Not willing to provide us with the full Image so that wont Happen in the near Future.
3B3RT said:
it works !!!!
now we need a patched boot
patched_boot.img i hope someone do this
Click to expand...
Click to collapse
rooted and unrooted. many crashing things happened a lot. including mine was bricked twice. lol.
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.
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.