Database Develop

[GUIDE] Flash SBF to Motorola Atrix 4G

WARNING
DO NOT FLASH ON BELL ATRIX
​If you appreciate this guide, please visit my website (maybe check out my sponsors!), subscribe on Twitter, press the thanks button below, or donate to Fixter, DesignGears, Fenny and other great helpers/devs for the Atrix 4G.
Download
1.2.6
http://bandbinnovations.com/Atrix.7z
Password: atrixbl
1.5.2
HTTP (Rename from .rar to .gz)
HTTP (Rename from .rar to .gz)
MultiUpload
Hotfile.com
DepositFiles
UPDATE: Linux SBF guide here --> http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html --> Thank you "relaxed"
Flash Guide (Instructions)
Prerequisites
Download RSDLite 5.0 (MediaFire mirror)
Install the program
Download SBF file from above links
Bricked phone or test device
Fully charged device
Drivers installed (if you rooted your phone, your computer has the necessary drivers)
32-bit
64-bit
Problems
Some users experiencing WiFi connectivity weirdness
SIM-unlocked devices may still have WiFi problems
Market might not show all applications (easy fix on the way)
Do not flash this file unless absolutely necessary. It will help those who’ve bricked their device to recover, but this is not for flashing just for fun. BriefMobile cannot be held responsible for device damage due to this guide.
Make sure your phone is turned off
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD
Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Load up the SBF file
The SBF file is located inside of the .gz file, you must extract it out before loading it into RSD Lite
Use WinRAR or 7-Zip to extract the .gz file on your computer
Plug your device into your computer
Use the USB ports on the back side of your computer for safety
RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
Press the “Start” button
Be patient while the phone reboots. It will take a long time.
Congratulations!

Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.

designgears said:
Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.
Click to expand...
Click to collapse
Good tip! Didn't know that!

Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?

tianqi said:
Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?
Click to expand...
Click to collapse
Yes. This isn't a confirmed issue, but others have experienced WiFi problems with this SBF flash over their SIM unlocked devices.

Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.

cellzealot said:
Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.
Click to expand...
Click to collapse
That's very odd. Mine most definitely shows as "NS Flash Olympus."

im a noob sorry, but what does this actually do?

fRenZy-_- said:
im a noob sorry, but what does this actually do?
Click to expand...
Click to collapse
If you mess around with your device and break it, this can save your life by unbreaking it!

I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.

kennethpenn said:
That's very odd. Mine most definitely shows as "NS Flash Olympus."
Click to expand...
Click to collapse
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.

cellzealot said:
I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.
Click to expand...
Click to collapse
Thanks for the info! Duly noted... editing the post.

jimmydafish said:
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.
Click to expand...
Click to collapse
100% positive I purchased my device retail. I'll screenshot the RSD Lite for you in a moment when I recover from my soft brick (screwed up framework-res).

RSD Lite reports "NS Flash" for me too
{
"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"
}
purchased through Amazon

kmiller8 said:
RSD Lite reports "NS Flash" for me too
purchased through Amazon
Click to expand...
Click to collapse
Perhaps "NS Flash" does not mean developer phone on the Atrix?

kennethpenn said:
Perhaps "NS Flash" does not mean developer phone on the Atrix?
Click to expand...
Click to collapse
Or maybe we both got incredibly lucky is there any way to further verify if RSD Lite is reporting incorrectly?
Also off topic, why is the "Start" grayed out for me?

mine also says NS, purchased directly from AT&T
start is greyed out if there is no file/an incorrect file to flash, notice that the file properties pane is blank, it has not actually loaded the file in the select box in that screenshot

Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device

tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
Mainly just recovers you from a soft-bricked or improperly hacked device. It flashes you back to stock (or as close to stock as we have right now.)
No new features. No bug fixes. Nothing different from stock except a few new possible issues.

tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
It changes some stuff, but I can hardly see anything different at face value.

Bootloader unlock failed: Command not allowed and OEM unlock option not available

Hello guys,
in these days I’m struggling for unlocking my Huawei P9 (Build number EVA-AL00C00B176).
I got the bootloader code, I installed last version of ADB and Fastboot and so on... (by the way I already did with several phones, so I have some experience about this)
The problem is when I launch the fastboot oem unlock ... command, I always get:
...
FAILED (remote: Command not allowed)
finished. total time: 0.014s
something that make me suspicious, is that I can enable the "USB debugging", but I cannot find the option "Enable OEM unlock". In all the guides I found even on this forum I always found that if I cannot find this option I can easily ignore, but now I found I have an "FRP Lock" that I have to bypass in some way.
I really have no idea about how to do... anyone can send me to right direction? Thank you so much!

How to enable OEM Unlock:
http://techbeasts.com/how-enable-oem-unlock-android-lollipop-marshmallow/
https://www.youtube.com/watch?v=5AoDVMVlJEU

Thank you hanniSK,
the problem is that I cannot find that option anywhere.
ScareIT said:
..
something that make me suspicious, is that I can enable the "USB debugging", but I cannot find the option "Enable OEM unlock".
...
Click to expand...
Click to collapse
Anyway, accordingly to the link you provided, it seems I cannot find it until I have enabled the PIN/Password/Lock protection.
I'm trying to disable it (and with this kind of Huawei, seems also quite difficult...), then I will report back.

ScareIT said:
Thank you hanniSK,
the problem is that I cannot find that option anywhere.
Click to expand...
Click to collapse
You must unlock Developer options in Menu..
Go to Settings-About device.
In About device locate the build number of your device. Tap the build number for 7 times to enable Developer options.

Problem solved! I've been able to unlock the bootloader.
First of all, I confirm that my smartphone doesn't have the "OEM Unlock" option. Of course I correctly enabled the Developer options menu (otherwise, how could I enable the USB Debugging option?), but the OEM Unlock was simply not visible (take a look to the following picture), anyway that is NOT important.
{
"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"
}
In the guide you posted, hanniSK, I found this sentence: "Custom images will be only flashed on your Android device if the option is enabled, if your device is already protected by some password or pin, no user will be able to enable this option" so, I passed the next 4-5 hours to find a way to disable the password request for the screen unlocking. Yes, you read well: more than 4 hours to do that, because I had to disable options, delete fingerprints, revoke certificates and so on... after every attempt to disable the screen unlock security, I found it "Disabled by administrator, encryption policy or credential storage".
Finally I solved with a soft reset (Advanced settings -> Backup & reset -> Reset all settings) and I managed to unlock the bootloader on the first try (yes, I lost all settings, but in any case is something that must happen when unlocking the bootloader).

Please explain the steps in detail
ScareIT said:
Problem solved! I've been able to unlock the bootloader.
Finally I solved with a soft reset (Advanced settings -> Backup & reset -> Reset all settings) and I managed to unlock the bootloader on the first try (yes, I lost all settings, but in any case is something that must happen when unlocking the bootloader).
Click to expand...
Click to collapse
Hello, Please explain in detail as to how you exactly unlocked because i also tried resetting all settings but nothing happened.

nukman5k said:
Hello, Please explain in detail as to how you exactly unlocked because i also tried resetting all settings but nothing happened.
Click to expand...
Click to collapse
What kind of error you get?
By the way, these is in detail my unlock process:
I obtained the unlock code (I asked it through Huawei support forms on their website)
I downloaded the ADB, Fastboot, drivers and so on, I recommend this post where you can find instructions and download links: http://forum.xda-developers.com/showthread.php?t=2588979
I did the soft reset (Advanced settings -> Backup & reset -> Reset all settings)
I connected the phone, than launched the command "fastboot oem unlock myunluckcodepoint1 "
After the reboot, my phone was unlocked.
Before, when I started this thread, I was stuck on the point 4 because the command didn't succeed and I always got error (I was jumping from point 2 directly to point 4), after I did the setting reset I managed to unlock immediately.

On step 4 my phone just says Waiting For Device. None of the drivers are missing. Also phone does not have OEM Unlock options, even after factory reset. Not sure what to do.

ScareIT said:
Hello guys,
in these days Iâ??m struggling for unlocking my Huawei P9 (Build number EVA-AL00C00B176).
I got the bootloader code, I installed last version of ADB and Fastboot and so on... (by the way I already did with several phones, so I have some experience about this)
The problem is when I launch the fastboot oem unlock ... command, I always get:
...
FAILED (remote: Command not allowed)
finished. total time: 0.014s
something that make me suspicious, is that I can enable the "USB debugging", but I cannot find the option "Enable OEM unlock". In all the guides I found even on this forum I always found that if I cannot find this option I can easily ignore, but now I found I have an "FRP Lock" that I have to bypass in some way.
I really have no idea about how to do... anyone can send me to right direction? Thank you so much!
Click to expand...
Click to collapse
Hey bud I have the same model as you with later firmware. I am unable to unlock my bootloader. It says waiting for device. When I put the phone in fastboot mode I see phone locked at the bottom of the Android robot

GodKingKnight said:
Hey bud I have the same model as you with later firmware. I am unable to unlock my bootloader. It says waiting for device. When I put the phone in fastboot mode I see phone locked at the bottom of the Android robot
Click to expand...
Click to collapse
The fastboot screen you see is right, the "waiting for device" message is usually connected to a missing driver problem, but you also said that no driver is missing.
Anyway, I recommend you to double check the drivers, to check if any device is missing or wrongly marked in your (windows) device manager, finally try to type these 2 commands (from command line):
fastboot devices (then post here the ouput)
and
adb devices (then post here the ouput)
Try to run these 2 commands also with phone booted normally and let's see...

ScareIT said:
The fastboot screen you see is right, the "waiting for device" message is usually connected to a missing driver problem, but you also said that no driver is missing.
Anyway, I recommend you to double check the drivers, to check if any device is missing or wrongly marked in your (windows) device manager, finally try to type these 2 commands (from command line):
fastboot devices (then post here the ouput)
and
adb devices (then post here the ouput)
Try to run these 2 commands also with phone booted normally and let's see...
Click to expand...
Click to collapse
Both those commands return nothing. Drivers are confirmed to be correct. After a lot of research I'm finding this Chinese variant has yet to be rooted or even custom recovery. I'm sad to report my Huawei may just be incompatible and permenantly locked. Bootloader code was also purchased through unofficial app DC unlocker

GodKingKnight said:
Both those commands return nothing. Drivers are confirmed to be correct. After a lot of research I'm finding this Chinese variant has yet to be rooted or even custom recovery. I'm sad to report my Huawei may just be incompatible and permenantly locked. Bootloader code was also purchased through unofficial app DC unlocker
Click to expand...
Click to collapse
Try to post as much information you can about "this Chinese variant" (I thought we have the same one), anyway the adb and fastboot commands must respond something, independently if the phone could be unlocked or not.
What do you get if you run the commands when the phone is switched on normally?
Did you also try to disable/enable the "USB Debugging" option?
Also try to post a screen of your device manager. Can help.

ScareIT said:
Try to post as much information you can about "this Chinese variant" (I thought we have the same one), anyway the adb and fastboot commands must respond something, independently if the phone could be unlocked or not.
What do you get if you run the commands when the phone is switched on normally?
Did you also try to disable/enable the "USB Debugging" option?
Also try to post a screen of your device manager. Can help.
Click to expand...
Click to collapse
I have tried that. EVA-AL00 Huawei P9. Unfortunately I just can't get it to work.

Hi,
I had the same problem, same fault while trying to unlock boot loader. After I disabled “Phone-Finder“ in the Huawei menu or security option, then I could unlock the bootloader.
Also in my dev-menu, the “oem-unlock“ option is not available. Seems, on the EVA-AL versions, those options are linked to each other.
Please check, and reply, if this also worked for you, then we may can mark this topic as “solved“
Please give it a try, good luck
Settings/Advanced-settings/Security/Phone-Finder/ enable Phone-Finder off

raTHiopA said:
Hi,
I had the same problem, same fault while trying to unlock boot loader. After I disabled “Phone-Finder“ in the Huawei menu or security option, then I could unlock the bootloader.
Also in my dev-menu, the “oem-unlock“ option is not available. Seems, on the EVA-AL versions, those options are linked to each other.
Please check, and reply, if this also worked for you, then we may can mark this topic as “solved“
Please give it a try, good luck
Settings/Advanced-settings/Security/Phone-Finder/ enable Phone-Finder off
Click to expand...
Click to collapse
You are genius bro ! Worked for me thanks ! :victory:

This also worked for me, thanks. "After I disabled “Phone-Finder“ "

If you can't see anything after these commands, computer doesn't see your device. Make sure that you enabled USB Debugging in Developer's setting and installed all needed drivers. In some case it's important to use original cable for your device and not to connect other devices while you are working with yours

I ain't getting unlock code from emui

I have a Ascend P7 L07 here with same problem, how i can flash boot.img? My smartphone is bricked and not entering on system

OmegaMotorolaBr said:
I have a Ascend P7 L07 here with same problem, how i can flash boot.img? My smartphone is bricked and not entering on system
Click to expand...
Click to collapse
This is the P9 forum, you need to post in the correct device forum.

OEM Unlock Fail

I finally received the OEM unlock toggle today and enabled it and easily installed magisk.
through restoring my apps, the phone froze.
When I rebooted it displayed a message in RED at the top "only official released binaries are allowed to be flashed" and would not go past the samsung logo.
in download mode it shows that FRP and OEM are both set to OFF. however i cannot flash my patched boot.tar, or even TWRP.
I get the same message in red...
N950F dual

mlkemac said:
I finally received the OEM unlock toggle today and enabled it and easily installed magisk.
through restoring my apps, the phone froze.
When I rebooted it displayed a message in RED at the top "only official released binaries are allowed to be flashed" and would not go past the samsung logo.
in download mode it shows that FRP and OEM are both set to OFF. however i cannot flash my patched boot.tar, or even TWRP.
I get the same message in red...
N950F dual
Click to expand...
Click to collapse
I can restore to stock in Odin, and I still have OEM lock off in download mode.
However I'm not able to modify anything. OEM lock has dissapeared from developer options, and it seems KNOX was tripped by flashing magisk.
Googling that RED message turns up zero results.. whats going on here??

mlkemac said:
I can restore to stock in Odin, and I still have OEM lock off in download mode.
However I'm not able to modify anything. OEM lock has dissapeared from developer options, and it seems KNOX was tripped by flashing magisk.
Googling that RED message turns up zero results.. whats going on here??
Click to expand...
Click to collapse
i read in the OEM unlock thread some were thinking that OEM unlock was on a timer for some? that it only displayed after a certain amount of time.. If that is true then its possible when you flashed back to stock it reset the timer.
Note: Just trying to help , i have never had this OEM issue
Maybe try looking in the oem unlock thread also might be worth checking out the root / TWRP thread

Mr.Ash.Man said:
i read in the OEM unlock thread some were thinking that OEM unlock was on a timer for some? that it only displayed after a certain amount of time.. If that is true then its possible when you flashed back to stock it reset the timer.
Click to expand...
Click to collapse
There is some type of time delay. it took 8 days for option to show up in the first place.
However the phone was successfully rooted with Magisk. and Google play was restoring my apps when it froze.
Currently restoring apps again on stock XSP.. no OEM in developer options.. but it still shows OEM lock off in Download mode
Any help is greatly appreciated.
{
"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: screen is not cracked.. glass screen protector did it's job

I'm facing the same problem. OEM Lock is OFF but am unable to flash custom recovery (currently unable to boot into OS either). Was working fine with Magisk and TWRP until I flashed custom ROM...(more details for my case: https://forum.xda-developers.com/showpost.php?p=73985590&postcount=27)
Anyone made any progress with this yet? I'm going to try flashing stock back and try again. Hoping for the best XD

I have the same issue. I've had OEM unlock as an option since day 1 and it never disappeared on me. Using an N950FD XSP I flashed TWRP/Verity. Rebooted into my stock ROM. I checked and the OEM unlock option had disappeared. Finished downloading a custom ROM and went to reboot into TWRP and I got the 'official binaries' message. So I went back into download mode and my FRP/OEM lock are both off. I can't flash TWRP again, I get the 'official binaries' message again. Going back to stock rather than letting an expensive brick sit on my desk.

mlkemac said:
I can restore to stock in Odin, and I still have OEM lock off in download mode.
However I'm not able to modify anything. OEM lock has dissapeared from developer options, and it seems KNOX was tripped by flashing magisk.
Googling that RED message turns up zero results.. whats going on here??
Click to expand...
Click to collapse
I'm in same boat. SM-N950F Australian TEL/TEL/TEL. Had to go back to stock as well after the soft brick.

Out of curiosity based on the screenshot above, what is the code to know if you tripped Knox on a Note 8?
I see it shows 1 (0x0303). Mine shows 1 (0x030c). I am back on the stock ROM and tried to use Samsung Pay. No luck, warning message about modifications to the device. I only made it as far as TWRP/Verity, so I guess that was far enough to destroy any possibility of me using it.
Also, I have no more OEM lock option. It shows off in download mode, but I guess I'm waiting until next week before having any chance of seeing it again. Perhaps it being off is why Samsung Pay isn't working?

wgpshadow said:
Out of curiosity based on the screenshot above, what is the code to know if you tripped Knox on a Note 8?
I see it shows 1 (0x0303). Mine shows 1 (0x030c). I am back on the stock ROM and tried to use Samsung Pay. No luck, warning message about modifications to the device. I only made it as far as TWRP/Verity, so I guess that was far enough to destroy any possibility of me using it.
Also, I have no more OEM lock option. It shows off in download mode, but I guess I'm waiting until next week before having any chance of seeing it again. Perhaps it being off is why Samsung Pay isn't working?
Click to expand...
Click to collapse
Warranty void 1 is tripped. Warranty void 0 is not tripped.

mlkemac said:
I finally received the OEM unlock toggle today and enabled it and easily installed magisk.
through restoring my apps, the phone froze.
When I rebooted it displayed a message in RED at the top "only official released binaries are allowed to be flashed" and would not go past the samsung logo.
in download mode it shows that FRP and OEM are both set to OFF. however i cannot flash my patched boot.tar, or even TWRP.
I get the same message in red...
N950F dual
Click to expand...
Click to collapse
Can you explain exactly what you were using to restore apps? and were you restoring app and system data also?
--->

Mentalmuso said:
Can you explain exactly what you were using to restore apps? and were you restoring app and system data also?
--->
Click to expand...
Click to collapse
I was using TIBU (official/paid) to restore. was restoring missing apps/data, & system data
I've since sold that model and went with the N950N which doesn't have the OEM issue.
I'm actually using your rom right now. Love the audio options. Thank you!

yo lo quite subiendo a android 8 en n950f single sim

this is my problem with S6 Edge+/ SM-G9280 China Carrier
after opening Odin and starting to flash twrp .. Installation Failed..

Renz Kell said:
this is my problem with S6 Edge+/ SM-G9280 China Carrier
after opening Odin and starting to flash twrp .. Installation Failed..
Click to expand...
Click to collapse
You'll have to tell or show us the error Odin message to help.

[GUIDE] Unlock bootloader of Lenovo Tab 4 10 with OEM unlock "greyed out" (TB-X304F/L and other Qcom tablets)

WARNING: DO THIS AT YOUR OWN RISK !!!!
I AM NOT RESPONSIBLE IF YOU START CRYING INTO YOUR BRICKED TABLET
This guide is only for devices with "OEM Unlocking" option greyed out !!!
Others can follow the simpler procedure mentioned in the TWRP thread...
Prerequisites:
QDLoader_HS_USB_Driver (Google it and find)
Hex Editor (eg. HxD)
PC and some brain to understand....
Procedure:
Install the drivers and hex editor.
Clone this repo to PC - https://github.com/Naveen3Singh/BLUnlocker (Thanks to the dev )
Extract the firehose file from stock rom. (eg. "prog_emmc_firehose_8917_ddr.mbn" for TB-X304)
Boot into edl mode using key combo
or using adb
Code:
adb reboot edl
Check the port number in device manager and run " dump_devinfo.bat ".
Mention port number and full path to "*.mbn" file (eg. D:\where\every\it\is\prog_emmc_firehose_8917_ddr.mbn)
A file named " devinfo.img " will be dumped to the working dir. Edit it using an HEX editor as shown below.
{
"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"
}
Save the devinfo.img after editing and run " unlock.bat "
Reboot after success message.
Voila !! You have Successful unlocked the bootloader. Reboot to system by holding the power button.
EDIT (13/01/2020): After unlocking bootloader and restarting, if it asks for password, Reboot to recovery and format data...
Flash TWRP and Enjoy rooting...
PS: The same procedure can be done using QFIL tools (QPST)
Attached:
Firehose file of TB-X304F and TB-X304L (DONT USE ON OTHER DEVICES!!!)
Credits:
Thanks to the dev who wrote the code ( https://github.com/Naveen3Singh )
@hk96 (Myself)
Hit thanks if this helped....

Reserved !!!

Thank you very much! It worked perfectly!

Firehose file for X304L if anyone needs it

Hb20032003 said:
Thank you very much! It worked perfectly!
Click to expand...
Click to collapse
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!

njascgil said:
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!
Click to expand...
Click to collapse
After unlocking, when u Boot into system it asks for a password, even if u didn't set one to start with (atleast in my case).
So you need Boot into recovery and wipe data.
Short answer: yes, factory reset is necessary.
Regarding file version, I hav no idea... May be u can give it a try...

Hb20032003 said:
Firehose file for X304L if anyone needs it
Click to expand...
Click to collapse
Thanks...
Let me add this to OP, so that it is easier for others.

Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.

Chhayank_Sharma said:
Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.
Click to expand...
Click to collapse
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.

hk96 said:
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.
Click to expand...
Click to collapse
ok thanks.

hk96 said:
Regarding file version, I hav no idea... May be u can give it a try...
Click to expand...
Click to collapse
I was going to try it, but it's my daughter's tablet and she didn't let me do it... She is afraid of loosing some games' progress...

Nothing work for me

Eagle-no1 said:
Nothing work for me
Click to expand...
Click to collapse
May be you would have missed something....
This seems to work for most people.

hk96 said:
May be you would have missed something....
This seems to work for most people.
Click to expand...
Click to collapse
I got to work now, I had an old bad cable in use. Thank you.

hk96 said:
PS: The same procedure can be done using QFIL tools (QPST)
Click to expand...
Click to collapse
How? I watched a video and I can load the mbn but I don't know what to put in the xml thing box. I tried doing the method steps but it says Failed to write hello response back to device Did not receive Sahara hello packet from device

Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.

Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
could you explain how you did it pleasssee

Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
Haha... Everything happens gradually...
rustyrust said:
could you explain how you did it pleasssee
Click to expand...
Click to collapse
I think, the instructions are crisp and clear as possible...
Can u tell where u got stuck ??

Work! You're GENIUS

hello,
I already root some device but here I'm stuck because I don't find the port number in device manager :-( drivers installed and "lenovo tab4 10" displayed in device manager. in properties I have : port_#0002.hub_#0005
I tried use 0002 or 0005 as port number but the .bat script failed each time. do I have correct port number ?
[EDIT] I have "failed to write hello response back to device" message and my tablet is in FFBM Mode.
[EDIT] in FFBM mode, my device is recognized in device manager (but i'm not sure to find the correct port and the script don't work) and in FastBoot Mode (first menu), my device seems to be not recognized in device manager. I guess that the script must be launched in this mode but I miss a driver. I install "adb drivers" + QDLoader-HS-USB_Driver_64bit_Setup drivers. What do I miss ?

How To Guide Unlock Bootloader on Xiaomi 11T Pro (All Variants)

Perform this at your own risk. You will LOSE all data on your phone.
( I'm not responsible for any damage to your device )
This guide will walk you through the process of Unlocking your bootloader on Xiaomi 11T Pro.
Prerequisites:
Backup all the files on phone as we will be resetting the phone to unlock the bootloader.
Install ADB and Fastboot Drivers from here (Select the latest) -> https://androidmtk.com/download-minimal-adb-and-fastboot-tool )
Install drivers for Xiaomi 11T Pro -> https://droidfilehost.com/download/download-xiaomi-usb-driver-for-windows
Download MiUnlock Tool -> https://en.miui.com/unlock/download_en.html
Unlocking the Bootloader:
Go to "About Phone" in Settings and keep tapping on MIUI Version until it shows "You are now a developer"
Navigate to "Additional Settings>Developer Options" and enable "OEM unlocking"
Make sure you have a Mi account and your sim is inserted. In Developer options, select "Add account". Now your Mi Account is linked with your Device.
On your PC, open MiUnlock Tool and login with the same Mi account you have used login to the tool.
Power off your phone and boot into fastboot mode by long pressing the power button + volume down button.
Connect your phone to your PC and click refresh in the MiUnlock Tool
After clicking unlock, it will give your a wait duration. (Generally 168 hours, there's no known way to bypass this wait time) You can continue to use your phone meanwhile, but remember to backup before clicking unlock after your wait time is complete.
After your wait is complete, click unlock and then click reboot. Your phone will now reset and boot up.
Enjoy.

Is this true about warranty? I think that i read that unlocking bootloader is not reason to void it

I have attempted to unlock bootloader, it ask for 336h wait. Did they changed waiting time from one week to two? Is it because device is quite new and they don't want them to be unlocked?

Pichulec said:
I have attempted to unlock bootloader, it ask for 336h wait. Did they changed waiting time from one week to two? Is it because device is quite new and they don't want them to be unlocked?
Click to expand...
Click to collapse
depends on the Mi Account, is it a new sim or an old one? I checked and added a new one to the device and it gave 2 weeks of wait time. I just added my old one and it gave 7.4 days of waiting.

Doktor-X said:
Is this true about warranty? I think that i read that unlocking bootloader is not reason to void it
Click to expand...
Click to collapse
Unlocking the boot loader shouldn't Void the warranty, installing a custom ROM will.

Jaistah said:
Unlocking the boot loader shouldn't Void the warranty, installing a custom ROM will.
Click to expand...
Click to collapse
Updated, thanks

I have very weird problem , trying to use mi unlock tool and can`t sign in to my MI account because the verification code not sent to my phone number.
when i tried to sign in from website no issues and the verification sms code sent to my phone with no problem , only mi unlock code tool didn`t send any verifications
any help or suggestion?

Jaistah said:
Unlocking the boot loader shouldn't Void the warranty, installing a custom ROM will.
Click to expand...
Click to collapse
does systemless root also void the warranty?
I just need the adblocking stuff only

You don't have to root to have adblocking. Use private dns.
{
"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"
}

Hello guys i have a problem unlock tool not recognize my devices can i gat some help should be the driver problem any solution pls?

adryan360 said:
Hello guys i have a problem unlock tool not recognize my devices can i gat some help should be the driver problem any solution pls?
Click to expand...
Click to collapse
https://dl.mi-globe.com/download/InKLvVR8oS/mi-globe.com_Xiaomi_Mi-UnlockTool_4.5.813.51.zip
Use the "driver_install" to fix the issue. Connect the phone both normally and in Fastboot mode. It automatically installs the drivers.

Hi guys, same problem here, Mi Unlock won't recognise my phone. Actually when I connect the phone to the PC in fastboot mode, nothing happens... I've tried to use the solution above but it doesn't change anything. When I click on the "driver_install" nothing happen neither.
On the Mi Unlock software when I go to the parameters and that I check driver installation, it says it can't find "miusbdriver.exe" (something like that). I took the miusbdriver.exe from the other version folder (from the message of arash74 above) but it's a loop : It finds the file but it asks me to reconnect my phone and so on.
Any help would be nice ! Thanks

Cocheton said:
Hi guys, same problem here, Mi Unlock won't recognise my phone. Actually when I connect the phone to the PC in fastboot mode, nothing happens... I've tried to use the solution above but it doesn't change anything. When I click on the "driver_install" nothing happen neither.
On the Mi Unlock software when I go to the parameters and that I check driver installation, it says it can't find "miusbdriver.exe" (something like that). I took the miusbdriver.exe from the other version folder (from the message of arash74 above) but it's a loop : It finds the file but it asks me to reconnect my phone and so on.
Any help would be nice ! Thanks
Click to expand...
Click to collapse
Did you try the 64bit version (driver_install_64) too?
It's worth a try to disable driver signature verification as well.

arash74 said:
https://dl.mi-globe.com/download/InKLvVR8oS/mi-globe.com_Xiaomi_Mi-UnlockTool_4.5.813.51.zip
Use the "driver_install" to fix the issue. Connect the phone both normally and in Fastboot mode. It automatically installs the drivers.
Click to expand...
Click to collapse
Thanks Bro but the samne problem in device manager shows android nootloader interface thats ok but in my unlock tool or fastboot nothing i try on windos 11 10 and now 7 nothing i try since 2 mounth i am dissapointed i expected moore from new xiaomi devices!

arash74 said:
Did you try the 64bit version (driver_install_64) too?
It's worth a try to disable driver signature verification as well.
Click to expand...
Click to collapse
Thank you Arash for your answer mate, I just did it with this tutorial :
I was stuck at this step actually, I didn't understand that by unpluging and pluging back my phone it would install the drivers !
So now I guess I have to wait 161 hours to continue my unlocking thing but I'm glad I could fix that problem of undected phone, and if it helps someone else here it's also a good thing then.

Cocheton said:
Thank you Arash for your answer mate, I just did it with this tutorial :
I was stuck at this step actually, I didn't understand that by unpluging and pluging back my phone it would install the drivers !
View attachment 5531737
So now I guess I have to wait 161 hours to continue my unlocking thing but I'm glad I could fix that problem of undected phone, and if it helps someone else here it's also a good thing then.
Click to expand...
Click to collapse
Glad I could help. I had the same problem and was struggling with it for a few days.

adryan360 said:
Thanks Bro but the samne problem in device manager shows android nootloader interface thats ok but in my unlock tool or fastboot nothing i try on windos 11 10 and now 7 nothing i try since 2 mounth i am dissapointed i expected moore from new xiaomi devices!
Click to expand...
Click to collapse
So guys i solve the problem it will sound a liitle strange but i pot here maybe someone will face this in the future.
My problem was not the driver because fastboot shows my device and any flash tool no so and i tryed many many version nothing but at least i accidentally extracted the tool on the desktop and i didnt move in to a folder so and open and boom the villi was here!
I tryed move in a folder and not worked i think the problem was permission maybe i didn't know i am happy cuz it's fixed now so i have to wait 360 hours until unlock!

I have a question about warranty. If I will install my original ROM back would it make warranty valid again ?

kisiol3 said:
I have a question about warranty. If I will install my original ROM back would it make warranty valid again ?
Click to expand...
Click to collapse
If you unlock bootloader, no your warranty will not be void. However if you show up to a Mi service center with an unlocked bootloader and a custom ROM, they will consider your warranty voided.

NOSS8 said:
If you unlock bootloader, no your warranty will not be void. However if you show up to a Mi service center with an unlocked bootloader and a custom ROM, they will consider your warranty voided.
Click to expand...
Click to collapse
So there is no way to bring phone back to factory state.
PS.
Is there any other way to turn on call recording ?