Database Develop

[SOLVED] Please Help! Can't get fastboot to recognize device, but adb does

Former-Prime R1 HD 16GB
Windows v8.1
TL;DR:
I am unable to get my phone to be recognized in fastboot by the fastboot utility, yet it is recognized by adb. I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). Besides the fact that adb sees the phone fine with the cable I'm using, it's the same cable I have successfully used with my Samsung and Nexus devices. I'm at my wit's end. :crying: I could really use some help.
Full version:
I've followed the instructions from this thread to flash my phone into an OEM non-Prime device:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
It's now running V12. I want to verify the state of the bootloader and jump through the hoops to safely put V17 on it (without whacking the preloader, etc.). My problem is that when I try fastboot devices no devices are listed. However, adb devices shows the phone.
I installed ADB and fastboot v1.4.3 using the package from this thread:
https://forum.xda-developers.com/showthread.php?t=2588979
I've tried a couple of different sources for drivers, both signed and unsigned. Each time I've installed drivers I've gone into Device Manager and removed previous disconnected device instances along with the drivers (checked remove driver box). I've got tzul's signed drivers installed which were obtained from this post using the enclosed instructions (both those in the "Android" and "CDC" folders):
https://forum.xda-developers.com/showpost.php?p=67927242&postcount=23
I also have the Android SDK's Platform Tools and Google USB driver installed and tried the adb and fastboot from there with the same results.
When booted to the Android OS, the phone shows up as Android Composite ADB Interface in Device Manager. When I use adb to try and reboot the phone into fastboot via adb reboot fastboot it merely reboots into the OS. To get into fastboot mode I have to do it via the bootloader (power+vol. up). When attatched in fastboot mode the phone shows up in device manager under "Other devices" as "Android" with The Yellow Triangle of Doom, and says drivers for the device aren't installed (Code 28). From what I've read, the drivers it's looking for are the in the "Android" folder of the drivers .zip I downloaded, which I have installed per the instructions.
Can someone please help me figure out what I've done incorrectly?

Fixed
As I had surmised, it was a driver issue. One of the driver bundles I had downloaded from androidmtk.com or another site foobar'd me. But before I had this straightened out, I gave up and used a Linux Mint virtual machine to verify my bootloader status, etc.
The way my drivers got straightened out was that I coincidentally ran Windows Update as I had updates available for which enough time had passed without reports of problems. Update offered me the following updates:
Important
Windows 8.1 Drivers
Microsoft - Other hardware - MTP Device
TP-LINK - Other hardware - Android Bootloader Interface
Windows 8.1 and later drivers
Samsung - Other hardware - Samsung Mobile MTP Device
Optional
Windows 8.1 Drivers
MediaTek - Other hardware - Android Composite ADB Interface
After installing these I again tried to use fastboot from my Windows box and it worked fine. So, one of the driver packs I installed screwed up my MTP drivers evidently (both the updates offered were from early last year). The TP-LINK driver was the VCOM I needed for fastboot to work.
So, all's well that ends swell.

Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!

OldSkewler said:
Amazon Prime running on V.6.1
Windows 7 x64
I am having similar issues but I don't fully understand how the OP solved this problem. I believe I am connecting properly with ADB but no response from fastboot. Here is what I have done so far:
1) Installed the "15 Sec ADB Tool". Drivers seem to be working but could not located the ADB folder the tool was supposed to create. I suspect drivers were installed correctly because under Device Manager I have "Android Phone > Android Composite ADB Interface"
2) Directly downloaded latest SDK Platform Tools, which includes adb.exe & fastboot.exe, among other files. Tried testing the tools with the following results:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
5DFYRKKFQWBEQ4LJ unauthorized
Click to expand...
Click to collapse
This shows adb is on , on your phone but you did not allow the connection. =. When you first connect pc to phone with usb cable and adb enabled , you should get a pop up window on the phone. You may need to wake the screen and unlock to see it. The window asks you to authorize the connection
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>fastboot devices
Click to expand...
Click to collapse
You also missed a step here. You needed to reboot phone to bootloader /fastboot mode before asking to list fastboot devices.
So before that line you should have done "adb reboot bootloader"
OldSkewler said:
C:\Users\Phantom\Dropbox\Personal\IT\Android\SDK Platform Tools\platform-tools>
Phone is turned on while doing the commands above. Could someone shed some light? Is the ADB response adequate? And should I get a fastboot response as well? If so, what could be the problem?
Lastly, phone has UBS Debug mode enabled.
Thanks in advance!
Click to expand...
Click to collapse

mrmazak, you are absolutely right on both items. I wish I had come across something explaining this earlier... spent a lot of time sorting this out!
Hopefully this will help someone in the future!

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 5

Hello Everyone !!​
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD​
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008​
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you

reserved

@vasu97
We already have a dedicated thread on the same topic.

what can i edit so it won't relock the bootloader? or does it relock it?

vasu97 said:
Hello Everyone !!​
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD​
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008​
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you
Click to expand...
Click to collapse
Holy crap! I literally spent the last 12 hours trying to get my phone fixed. This was the only solution. Thank you so much!!!

If anyone had problems with the MSM tool "Sahara communication failed," unplug your phone. Turn it off by holding the power button for a while. Hold the power up for 10 seconds, then keep holding the volume up and plug your phone in to the PC. The MSM tool should automatically detect and restore your phone.

vasu97 said:
reserved
Click to expand...
Click to collapse
thank you so much

I've tried all the steps on multiple ports and different computers but I got always the errno 258 while loading the cache.img. Don't know what else to do...

[GUIDE]-[Unlock Bootloader+TWRP+Root] Huawei MediaPad M3 8.4 [BTV-W09, BTV-DL09]

{
"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"
}
The official Huawei bootloader unlock program has been shut down! This guide describes how to use DC-Unlocker which will cost you about $5 USD. I am NOT affiliated with DC Unlocker in any way!!. This is simply the cheapest and easiest method I could find...
I have only tested this method on BTV-W09 running Android 7 and EMUI 5.0.3.,
If you have a BTV-DL09 device, please reply and let me know how everything goes...
You need ADB and Fastboot installed on your PC.
This will FACTORY RESET your tablet!!! and as always: Don't blame me for Bricks & FOLLOW THIS GUIDE AT YOUR OWN RISK!!
-Unlock Bootloader-
0. Enable USB Debugging and OEM Unlock in developer options.
1. Download DC Unlocker and extract it on your PC.
2. Open the program and choose 'Huawei phone' under manufacturer and 'Auto detect' under model.
3. Plug your device into your PC and put it into 'manufacturer mode'.
3.1 Open the Calculator app in LANDSCAPE mode
3.2 Enter this code: ()()2846579()()=
3.3 Tap on 'Project Menu' - 'Background settings' - 'USB ports settings' - 'Manufacture mode'.​4. Click the search button in DC Unlocker and make sure your tablet is detected.
5. Click on 'Buy Credits' under the About section.
6. Use the website to buy 4 credits for a new account.
7. Click on 'Server' in DC Unlocker and log in using info obtained in step 6.
8. Once your logged in click 'Unlocking' then select 'Read Bootloader Code'
9. Wait until your code is displayed then copy and save the code.
10. Turn off manufacturer mode.
11. Open a CMD Prompt and type the following commands.
Code:
adb devices
//make sure your device is listed.
adb reboot-bootloader
//Wait for your device to reboot (white screen)
fastboot oem unlock XXXXXXXXXX
//replace XXXX with your code
12. Wait... your device should now reboot and do a Factory Reset...
13. After reset, boot your device and go through android setup.
Congrats your bootloader in now unlocked.​
-Flash Greatslon TWRP-
0. Download TWRP for your device.
TWRP - BTV-W09 EMUI 5 (This is the only Model & Version I have tested)
TWRP - BTV-W09 EMUI 4
TWRP - BTV-DL09 EMUI 5
TWRP - BTV-DL09 EMUI 4
1. Enable USB Debugging
2. Plug your device into your PC.
3. Open a CMD prompt in the same folder as TWRP image.
4. Enter the following commands.
Code:
adb devices
//make sure device is listed
adb reboot bootloader
//wait for device to reboot
fastboot devices
//make sure device is listed
fastboot flash recovery XXXXXX
//replace xxxx with your TWRP file name
5. Completely shut down your device and unplug any USB cables. (some devices have problems booting TWRP when a USB cable connected)
6. Boot into recovery (PWR+VolUP).
Congrats You have flashed TWRP.​-Root Device-
0. Download the latest Magisk release.
1. Download Magisk Manager APK file.
2. Open a CMD prompt in the same folder as files
3. Type the following commands
Code:
adb devices
//make sure your device is listed
adb push Magisk-v20.4.zip sdcard/
//change name if needed
adb push MagiskManager-v7.5.1.apk sdcard/
//change name if needed
adb reboot recovery
//wait for device to reboot
4. Install Magisk | 'Install' -> Select: Magisk zip -> Swipe to confirm.
5. Wipe Cache/Dalvik.
6. Reboot to Android.
7. Install Magisk Manager to confirm root..
Congrats your device is now Unlocked and Rooted running a custom Recovery.​
:: EDIT ::
LienageOS 15.1 now available on this device., Visit the following thread for my install guide.
[GUIDE]-[ROM][8.1][LineageOS 15.1 - Huawei Mediapad M3 8.4][BTV-W09, BTV-DL09]​

Thanks very much for the write up! All worked perfectly and using this to prep for lineage os.
One thing I had to do using Windows 10 is install hisuite to get the USB drivers so adb/DC unlocker could recognize the device.
Thanks again!

Phone not found!
4. Click the search button in DC Unlocker and make sure your tablet is detected.
After I click search button that warning "Phone not found!" I don't know why Help me, plz

traihams said:
4. Click the search button in DC Unlocker and make sure your tablet is detected.
After I click search button that warning "Phone not found!" I don't know why Help me, plz
Click to expand...
Click to collapse
Does you already connected USB cable between your tablet & desktop ? Does you already installed Huawei Drivers on your desktop ? Does you already enabled Android debugging inside Developer options on your tablet ?
EDIT:
From what you see there are many reasons why you do not see the tablet connected there ... unfortunately we don't have any prophet here to guess what you did or didn't do there

i follow those steps to root my d-01j, thanks so much

iFilae said:
i follow those steps to root my d-01j, thanks so much
Click to expand...
Click to collapse
Hello, could you show your unlock code? I want to see some examples for d-01j unlock code. Thank you.

baobinhday said:
Hello, could you show your unlock code? I want to see some examples for d-01j unlock code. Thank you.
Click to expand...
Click to collapse
unlock code is different for each imei

Phew, got it unlocked! Moments of terror when entering the commands on the cmd...
A few mentions where I got stuck that may help someone else:
Regarding point 3:
In case your model has LTE (i.e. BTV-DL09), you actually should have a dialer application that you have to use instead of the calculator app, which didn't work for me. This is also mentioned in the DC unlocker app. In case you do it with the dialer, you have to enter following code: *#*#2846579#*#*
Regarding point 4:
Inside the "DC unlocker" app, I also got the "device not found" error, and I was wondering why. Two things I noticed:
- To enable USB debugging, it was not sufficient for me to activate the switch in the developer options, as the default USB mode for me is "charging only". I had to change it to i.e. "Device File Manager (MTP)" by tapping on the notification and then re-activate USB debugging in the developer options (which turned off after switching to MTP mode) to get USB debugging working.
- After enabling "manufacturer mode", the mode was turned off as soon as I quit the menu. So I had to stay in the menu to make sure manufacturer mode is on.
- You can check your device manager in Windows to see if the current mode is active: When doing USB debugging, the device "Android Composite ADB Interface" should show up under "Android Phone" list, whereas when you turn on manufacturer mode, some COM ports should show up under "Ports (COM and LPT)"; the one DC unlocker is searching should be named "Android Adapter PCUI". If you got some devices with not properly installed drivers you should consider installing HiSuite software on Windows first.
Regarding point 8
- When I bought the credits for DC unlocker for PayPal, I had to click on a link arrived to the PayPal e-mail for confirming your account. I then still got the "Server login error", but closing and reopening DC unlocker eventually fixed it.
Hope this helps! Happy unlocking to everybody!

Moving on to next step (flashing greatsIon TWRP)...
There seem to be no download mirrors for TWRP - BTV-DL09 EMUI 5 at the moment, so I have to retry later.
I though noticed a strange thing: looking at the greatsIon M3 download list, it seems that there are 2 versions of the TWRP for the BTV-DL09 with EMUI 5: the one linked in this thread, and another one, having same name ("twrp_BTV-DL09_5_greatslon.img") which has been uploaded earlier (March 2 vs August 7 2017) and its quite larger (35.4 vs 24.7 MB). Now the funny thing is that this file actually has mirrors available right now, but I don't want to flash something unless I'm quite sure it's the right one. Plus I'm quite a noob, so that gives me another minus...
For all other BTV-DL09 users out there: did you try flashing this one? Why are there 2 versions hanging around?
EDIT:
Now it seems that there are again mirrors for the DL09 TWRP linked in this post. After downloading it, I extracted both versions (the smaller and larger .img files), and by doing a byte-per-byte compare of the extracted payload, it seems that the two images are identical. One is just packed in a bigger IMG file, if I got it right.
Anyways: After flashing via fastboot, I cannot eventually directly boot into TWRP recovery using the "Power+ Volume Up" combination. It boots every time in the warning screen stating "your device has been unlocked", giving me two options: Pressing "Power" will boot normally, whereas pressing "Volume Up" for at least 3 secs will boot into recovery. If I then press "Volume Up", it goes in the "Huawei eRecovery" instead of going into TWRP. Is that expected? The only way to reach TWRP for me is via adb by entering "adb reboot recovery". Why?
EDIT 2:
Sorry guys, I'm such a noob at this. I evenutally was able to boot directly in to TWRP by pressing "Power + Volume Up" a bit longer. If I press it and release when I feel the vibration, it will take it as a "Power" only command and it'll boot into the warning screen with normal boot / Huawei eRecovery options, but if you continue pressing it until you see the LCD turn on, it will boot into TWRP.
All right, seems that I'm slowly moving on. Sorry for this exhaustive reports :cyclops:

I found the calculator (my bad) but now the problem is this message in Twrp "failed to mount '/3rdmodem" and "failed to mount '/cust" Whay can i do? Please, help me.

I've just created an account, to say thank you bro.
Your guide works also perfectly fine on a BTV-DL09 device.
I also can confirm the necessarry additional steps which "the wing" mentioned. Also a great guy
A little note from me: In the windows powershell, I had to start the code lines with a "." expample ---> .\adb.exe fast boot reload
Now I am taking a sip of my coffee, lean back and simply enjoy my taken of handcuffs of my MediaPad. Twek8 is now a free elf.
Thanks a lot for your great guide and stay gangsta.

Hi Guys,
Hoping someone has had some luck with this point as I am getting really frustrated....
I have the MediaPad M3 Lite 10 (BAH-W09). I am trying to get DC_Unlocker to recognize my device. No matter what combination I try and do things (from the points above), I continue to get 'Phone not found'. If I select MTP mode, manufacture mode changes, if I change to manufacture mode, it changes to 'charge only'. I also thought I would fool the system and set 'allow adb debugging in charge only mode' but this still is not working. Of note, ADB does recognize my device and I have also installed the drivers (should that help troubleshoot).
Frustrating when you are stuck on Step 1 of so many!!
Click to expand...
Click to collapse
Just following up on this...finally got things moving along, a bit. I was finally able to unlock the bootloader, install TWRP and attempted installation of MAGISK. I have ran into a couple of problems...
1. TWRP, I installed the version that is meant for EMUI5.1 (3.2.0.0?)
2. Via TWRP, I attempted to install MAGISK.
During step 2 above, though it was running, it clearly was not succeeding and gave a long list of permission errors; thus failing.
On top of that, when I try and reboot the warning comes up that I have an unlocked device, if I continue with the boot, it gets to the Huawei logo and then reboots; over and over. The other option is to enter into Huawei's recovery system.
Anyone have any thoughts on what could have gone wrong that would have caused TWRP to fail?

Hi! Thanks so much for this guide, I've got my M3 up to the point where I flashed TWRP and rebooted into recovery.
Unfortunately, the TWRP BTV-W09 EMUI 5 image put it me into a boot-loop. I also tried both of the twrp 3.3.1-2 and 3.3.1-3 images from here. These images both got it stuck on the TWRP 'Teamwin' screen and doesn't boot into recovery. Any ideas on where to go with this issue?
Edit: I found a post stating I needed twrp 3.2.0-0, this worked for me.

Eilermoon said:
Hi! Thanks so much for this guide, I've got my M3 up to the point where I flashed TWRP and rebooted into recovery.
Unfortunately, the TWRP BTV-W09 EMUI 5 image put it me into a boot-loop. I also tried both of the twrp 3.3.1-2 and 3.3.1-3 images from here. These images both got it stuck on the TWRP 'Teamwin' screen and doesn't boot into recovery. Any ideas on where to go with this issue?
Edit: I found a post stating I needed twrp 3.2.0-0, this worked for me.
Click to expand...
Click to collapse
I don't understand why you flashed a TWRP for Kirin devices on your Qualcomm device

Bootloader unlocked but TWRP does not work, flash ok but does not start, advice?
Huawei mediapad M3 Lite 10
I need to ROOT:

It also works on BAH-W09 version?

GiammyA7X said:
It also works on BAH-W09 version?
Click to expand...
Click to collapse
NO, this is only for Huawei MediaPad M3 8.4 and not for Huawei MediaPad M3 Lite ... and it's stated clearly in the title !

surdu_petru said:
NO, this is only for Huawei MediaPad M3 8.4 and not for Huawei MediaPad M3 Lite ... and it's stated clearly in the title !
Click to expand...
Click to collapse
Yes, but I'm a bit confused about the "compatibility" between models (m3 lite 10/8, WiFi only/data). For the TWRP i've seen that it's compatible BAH-W09, but is possible make root on it?
Thanks

GiammyA7X said:
Yes, but I'm a bit confused about the "compatibility" between models (m3 lite 10/8, WiFi only/data). For the TWRP i've seen that it's compatible BAH-W09, but is possible make root on it?
Thanks
Click to expand...
Click to collapse
Unfortunately I did not test TWRP 3.2.0-0 in stock EMUI firmware Android N ... so I created that TWRP just with the intention of installing LOS 16.0 !
Basically after I installed TWRP, I formatted /data, and installed LOS 16.0 - so I can't guarantee that it works properly with android stock EMUI !
My advice is to use TWRP only if you want to update to LOS 16.0 and later to LOS 17.1 - and after installing LOS there is no way to downgrade to android stock EMUI .

Hi,
Thank your for your job but currently I'm a little bit frustrated. I can't unlock my BTV-W09 bootloader.
In step 4, DC Unlocker does not seem to find my device. It does not show any data after, "Found Applications port COM5".
===================================================================
DC - Unlocker 2 Client 1.00.1431
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM5
===================================================================
- The ROM version is BTV-W09C100B308
- I use windows 10
- I installed hisuite
- USB debugging, OEM Unlock and manufacturer mode are enabled
- In device manager, I see "Android Composite ADB Interface" and "Huawei HDB Interface" under "Android Phone" and "Android Adapter PCUI (COM5)", "DBAdapter Reserved Interface (COM4)", "HUAWEI Mobile Connect - Fake Acm Interface (COM3)" under "Ports (COM and LPT)"
- After many tries, I uninstalled hisuite because it was started automatically after each usb connection. After uninstall, device manager still shows interfaces and ports.
Any idea about this issue? Do I need to buy credits before step 4?
Best regards,
EDIT: Sorry, I was expecting more verbose from DC Unlocker like, model, serial, firmware. In the end I succeeded. Thanks.

[LIVE] Xiaomi Redmi Note 8 goes AICP

Hey guys,
this will be my live thread of bringing AICP 16.1 to my new redmi note 8 device.
I will follow this GUIDE
I will install AICP 16.1 and TWRP
- Enable Developer Options in your phone by tapping the "MIUI Version" 7 times in About Phone. OK
- Go to Settings > Additional Settings > Developer Options. OK
- Enable OEM Unlocking, USB Debugging and USB Debugging (Security Settings) . OK
- Also add account in Mi Unlock Status (Can be found in Developer Options). OK
- Install the required ADB and Fastboot drivers in your PC from here. OK
- Download Mi Unlock to PC from here, and sign in with your Mi Account. OK
- Shut down your phone manually, and hold volume down key and power button to enter Fastboot mode. OK
- Connect your phone to PC using USB cable and click "Unlock" in Mi Unlock Tool. #error1 #solved
- wait for 163 hours OK
- unlock OK
- flash twrp #error2 #solved
- flash AICP, OpenGApps & Magisk #error3 #solved
Happy User of AICP on Redmi Note 8
Best, dj

#error1 #solution
my phone in fastboot mode is not recognized by mi_unlock_tool
For me it looks like as fastboot drivers dont work properly, adb seems to work fine
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
141a4895 device
for fastboot drivers pls, see attached file
SOLUTION:
1) Google for "Disable driver signature enforcement"
2) Update drivers manually ( see attached files )

Check adb drivers:
Connect device with booted ROM and type in cmd:
adb devices
--> If drivers are properly installed your device is recognized there
Check fastboot drivers:
Connect device in fastboot mode and type in cmd:
fastboot devices
--> If drivers are properly installed your device is recognized there

#error2 #solution
TWRP is gone after reboot
Solution:
Start TWRP directly from fastboot mode with Hold Power & Vol+ unitil TWRP Logo comes up

#error3 #solved
Magisk does not work.
Solution:
Flash ROM
Boot ROM
Flash Magisk

Question Mi 11 Ultra not detected in FASTBOOT

Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.

Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.

Sathelp said:
Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.
Click to expand...
Click to collapse
I'm able to detect device in "ADB Devices" when phone is booted into android OS, even the MiFlashTool also detects the device when phone in booted into OS.
But after i type ADB reboot bootloader, phone restarts into FASTBOOT, i can see RED "FASTBOOT" logo in phone screen but it doesn't get detected.
How come phone gets detected in ADB when Phone is booted into OS MIUI13 but not in FASTBOOT.
I'm on windows 11 .
I changed the cable also with a new Xiaomi cable purchased recently, still the same result.

You can never see a result to detect mi 11 ultra through ADB devices. Rest assured your device is already detected and ready to use. Even though can not see device address.

I had the same case. Make sure all the necessary drivers are installed.
At first mine was also not detected in fastboot. When I first ran MI Flash Tool, it automatically installed some drivers. And I also manually installed USB driver of MI 11 Ultra.
After that MI Flash detected my phone in fastboot.
A small suggestion from me: Use "Xiaomi ADB Fastboot Tools" for flashing. MI Flash was giving me, timeout error and my device got into fastboot loop. After flashing with "Xiaomi ADB Fastboot Tools" all went well.

hello, I also had this problem and to solve it I used the driver of Mi unlock which is at the level of the parameters and launch it in fastboot then connect it to the pc and the drivers must be installed

I had a similar problem with my Mi 10. Found via ADB but wouldn't show in fastboot. Tge way I solved it was to boot into TWRP recovery (assuming you have it) and then go to their reboot menu and choose fastboot from there. It will then put you into their version of fastboot and your computer should recognise the phone in fastboot mode.
I hope this helps

jaggub4u said:
Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.
Click to expand...
Click to collapse
Adb and Fastboot is not the same thing!
If you're phone is detected in ADB, it means you have install the Adb Driver ( which more than probably is Google Driver or Xiaomi driver for ADB ).
In order for you phone to be in Fastboot do the following:
- Reboot to Fastboot and connect your phone to PC with original Xiaomi cable from the box
- Go to Device Manager > Other Devices > Android Device ( you will see a yellow sign, which means you don't have the Fastboot Driver )
- Download XiaomiMi11 Ultra Bootloader Driver.zip, unzip it
- Click on the Android Device with yellow sign > Update driver > Browse my computer for drivers > Select the Xiaomi Bootloader Folder
It will install the driver.
From here you're good to go!