Hello!
I am trying to root my phone, which requires and unlocked bootloader.
Here are the steps i have completed:
1. Got the unlock code.
2. Installed adb and fastboot drivers.
3. Installed HiSuite
4. Connected the phone to my desktop (windows 10).
Here i have to mention that the pc recognises my phone, and it is listed under devices. USB debugging and OEM unlock are enabled.
5. I opened cmd in the folder where abd is installed. Checked that abd devices finds my phone (which it does).
Here is where the problem comes in. After booting phone into fastboot (using adb reboot bootloader), i tried to find my phone using the command fastboot devices.
This doesn't find the phone. If i try to unlock anyways, it gets stuck on waiting for devices. I tried the same steps on a laptop (also running windows 10) and the problem stays the same.
Help is appreciated.
EDIT: solved the problem by using a windows 8 installed laptop.
Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.
monoxian said:
Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.
Click to expand...
Click to collapse
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.
Nastmi said:
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.
Click to expand...
Click to collapse
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone
monoxian said:
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone
Click to expand...
Click to collapse
Will try the tool when i get home from school, but fastboot devices doesn't detect my device.
EDIT: The tool didn't work. It is stuck on waiting for device.
Fixed the problem by unlocking on another laptop (has windows 8).
Nastmi said:
Fixed the problem by unlocking on another laptop (has windows 8).
Click to expand...
Click to collapse
Glad to hear that you got it working, I had windows 10 and that worked on mine =\
Sent from my iPhone using Tapatalk
Related
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
nathlynn22 said:
cannot connect to pc i have unlocked bootloader with htcdev and installed cwm touch v 6.0.4.4 one Flyhalf205's thread. that all worked fine.
but after doing a nandroid backup for my uk EE htc one cid htc_001. i then rebooted phone from recovery but now when i connect phone to laptop it does not recognize it through windows. nothing happens when i fastboot devices either please help thanks.
Click to expand...
Click to collapse
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
[email protected] said:
You cannot do fastboot devices in recovery mode.
in recovery mode you can do adb devices to check if your phone is recognized by your laptop
in fastboot usb mode, you can do fastboot devices to check if your phone is recognized by your laptop
Click to expand...
Click to collapse
I tried fast boot devices in fast boot USB by going into minisdk. Didn't try in recovery would have been good to try adb devices in recovery because I was stuck in that when first tried the custom recovery but a hard reset kicked it back out. Got recovery sorted just wanted to take nandroid backup off phone to PC and put root files which I'm still trying to get best 1's any idea where to get them where URL link is working? I've tried fastboot so doesn't work and basic trying to connect phone to PC for file transfer doesn't work either
stovie_steve said:
I have the same. Was working fine beforehand now nothing. When I connect to the PC with the phone booted it connects then a second or two later disconnects, like it "doesn't like" the connection. It tried to install HTC MTP driver but fails as it says the "device is disconnected." Fastboot USB works fine though and I can carry out fastboot commands from bootloader, but no ADB
Click to expand...
Click to collapse
Ok so not only person. When I try connect mine doesn't even flag up I've connected a device USB debugging starts up on phone but have just noticed USB connection doesn't show. Plus I connect to PC and doesn't make the sound as I've it recognized my connecting anything. Fastboot USB comes up empty. I've been spending a couple hours here and there for past 2 nights trying to set phone up ready for rum runner. But my other question is if I'm already on htc_001 there's no need for me to change CID num anyways? Thanks
Try going to command prompt and typing in set devmgr_show_nonpresent_devices=1 followed by start devmgmt.msc
Click on view and show hidden devices. This will show devices which are not connected but have been installed. Look for something like android phone or android device and update the drivers by selecting update driver > let me select > have disk and then select the driver from here:
http://forum.xda-developers.com/showthread.php?t=2386956
Try that and see if it works
I'm all sorted now thanks just kept at it.
Sent from my HTC One using XDA Premium 4 mobile app
Hi. I decided to flash my Honor 3c with Cyanogenmod 12.1. My problem is that i need TWRP (now I have CWM) but i can't flash it to my device. I try to do it by SP Flash Tool, but after i connect my turned off device, I get this error:
BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (0x7D4)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]: 1. There's an cable communication problem between FlashTool and BootROM. 2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION] 1. Try again. 2. Proceed H/W checking in download cable and target side com port. 3. Monitor if power-drop occured in target side.
Click to expand...
Click to collapse
Where is the problem? I've tried with 2 different cables and 2 different computers
Ceranzuo said:
Hi. I decided to flash my Honor 3c with Cyanogenmod 12.1. My problem is that i need TWRP (now I have CWM) but i can't flash it to my device. I try to do it by SP Flash Tool, but after i connect my turned off device, I get this error:
BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (0x7D4)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]: 1. There's an cable communication problem between FlashTool and BootROM. 2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION] 1. Try again. 2. Proceed H/W checking in download cable and target side com port. 3. Monitor if power-drop occured in target side.
Where is the problem? I've tried with 2 different cables and 2 different computers
Click to expand...
Click to collapse
Is your phone in bootloader mode? Hold Vol down+power to enter fastboot mode and then connect your phone to PC.
If you are already doing that or the problem still persists and have an unlocked bootloader(which I am sure you have), try to flash twrp manually.
muradulislam said:
Is your phone in bootloader mode? Hold Vol down+power to enter fastboot mode and then connect your phone to PC.
Click to expand...
Click to collapse
When I do it, my phone just turns on normally.
How can I check if I have unlocked bootloader? I have unlocked it about 1 year ago, but I did full wipe yesterday.
Ceranzuo said:
When I do it, my phone just turns on normally.
How can I check if I have unlocked bootloader? I have unlocked it about 1 year ago, but I did full wipe yesterday.
Click to expand...
Click to collapse
Vol down+power should boot into fastboot. Turn off the phone, hold both until honor logo shows up, let go of power but hold vol down for about 5 sec more.
If still the same, Turn off your phone, connect USB cable to phone, hold Vol down and connect the cable to computer. It should boot into bootloader now.
If it can not boot into bootloader still, the last is to try adb but that is a bit lengthy.
In bootloader mode, it will be written on phone screen in red whether phone is locked, unlocked or relocked.
Wipe does not effect bootloader status so it's still unlocked imo.
muradulislam said:
If still the same, Turn off your phone, connect USB cable to phone, hold Vol down and connect the cable to computer. It should boot into bootloader now.
Click to expand...
Click to collapse
After this, I got this text on my screen:
FASTBOOT&RESCUE MODE
Please connect usb cable to your computer and open hisuite
Click to expand...
Click to collapse
Ceranzuo said:
After this, I got this text on my screen:
FASTBOOT&RESCUE MODE
Please connect usb cable to your computer and open hisuite
Click to expand...
Click to collapse
It did not say anything about phone unlocked in red?
muradulislam said:
It did not say anything about phone unlocked in red?
Click to expand...
Click to collapse
Nope. Maybe I was wrong and I have never unlocked it? I don't remember, but I did something when I was upgrading my phone to Android 4.4.2
Ceranzuo said:
Nope. Maybe I was wrong and I have never unlocked it? I don't remember, but I did something when I was upgrading my phone to Android 4.4.2
Click to expand...
Click to collapse
At least it should say, phone locked. Saying nothing is a phenomenon i never heard before but I usually go for newer versions. May be that's the case.
Anyways use adb to fire this command
Fastboot OEM device-info
To be sure if its locked or not.
To setup adb, download and install latest Android SDK, run the program and only download platform-tools.
Your phone is international variant and it came with locked bootloader, I am sure sp tools unlocked it coz otherwise CWM could not be flashed.
Right click platform-tools folder and select run command prompt window here and type the above command
If the bootloader is unlocked (it will tell you if it is), copy the twrp image to platform-tools folder and rename it to twrp.img and fire this command
Fastboot flash recovery twrp.img
And try to reboot into recovery after disconnecting from pc and simultaneously holding power+ Vol up.
edit: nevermind, i forghot about something...
muradulislam said:
If the bootloader is unlocked (it will tell you if it is), copy the twrp image to platform-tools folder and rename it to twrp.img and fire this command
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Should I do this when my phone is switched off?
Ceranzuo said:
Should I do this when my phone is connected to pc or not? Switched off?
Click to expand...
Click to collapse
When your phone is connected to your pc in fastboot mode.
Lemme know how did it go, will reply back in the morning. Hope everything works fine for you.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
When your phone is connected to your pc in fastboot mode.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Ok, after I typed this command, there appeared this message in window:
<waiting for any device>
Click to expand...
Click to collapse
after this I reboot into recovery mode, but there is still CWM, not TWRP
Ceranzuo said:
Ok, after I typed this command, there appeared this message in window:
<waiting for any device>
after this I reboot into recovery mode, but there is still CWM, not TWRP
Click to expand...
Click to collapse
You dont have your phone drivers installed. Google Huawei USB drivers and install them or use hisuite to install drivers for your phone.
After driver installation, do the same process again.
My bad. I assumed you would have drivers already installed
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You dont have your phone drivers installed. Google Huawei USB drivers and install them or use hisuite to install drivers for your phone.
After driver installation, do the same process again.
My bad. I assumed you would have drivers already installed
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
I have already installed many drivers from different sites. I will try with hisuite
Ceranzuo said:
I have already installed many drivers from different sites. I will try with hisuite
Click to expand...
Click to collapse
Hisuite is the best option. Even if that does not work (there is a chance of that), Google Kouch's universal drivers and install those.
May have to manually install dribers if nothing works.
Lemme know how did it go. Will get back to you in the morning if nobody else came along (but someone surely will before that).
Have a nice day/night depending on your time zone
Sent from my PLK-L01 using XDA Labs
---------- Post added at 07:41 PM ---------- Previous post was at 07:31 PM ----------
Lemme get my teacher for you
@DigiGoon
Sent from my PLK-L01 using XDA Labs
I installed Hisuite and connected my phone. Windows have downloaded drivers automatically. And still the same...
But I forgot to tell you that when I connecting my switched off phone, my pc says "USB Device Not Recognized" (or something like that, I dont have english version of windows). Everything is ok when my phone is switched on...
This phone is cursed. I try to give up and stay on my current ROM, so I installed Nova Launcher, but setting it as default doesn't work :/
Thanks for trying to help me anyway.
Ceranzuo said:
I installed Hisuite and connected my phone. Windows have downloaded drivers automatically. And still the same...
But I forgot to tell you that when I connecting my switched off phone, my pc says "USB Device Not Recognized" (or something like that, I dont have english version of windows). Everything is ok when my phone is switched on...
This phone is cursed. I try to give up and stay on my current ROM, so I installed Nova Launcher, but setting it as default doesn't work :/
Thanks for trying to help me anyway.
Click to expand...
Click to collapse
I was awake just for your post. I think I got the problem. You need fastboot drivers imo but I would have to read a bit before I can suggest how to go about it.
Am busy tomorrow but will try to get back to you in the evening (GMT+5 time zone).
Can never be 100% sure but still I am confident, your problem has a solution. Just bear with me a day or two
Sent from my PLK-L01 using XDA Labs
Ceranzuo said:
I installed Hisuite and connected my phone. Windows have downloaded drivers automatically. And still the same...
But I forgot to tell you that when I connecting my switched off phone, my pc says "USB Device Not Recognized" (or something like that, I dont have english version of windows). Everything is ok when my phone is switched on...
This phone is cursed. I try to give up and stay on my current ROM, so I installed Nova Launcher, but setting it as default doesn't work :/
Thanks for trying to help me anyway.
Click to expand...
Click to collapse
Boot into recovery mode, no matter on which recovery are you on, and execute this command:
Code:
adb devices
And see the output, if it says something like:
Code:
**some_number** recovery
then it means there is no problem in the detection of your device by PC, if it does not, then check if the micro USB socket in the device is in good condition.
And I must ask: Are you able to do any operations on device via PC after connecting it?
DigiGoon said:
Boot into recovery mode, no matter on which recovery are you on, and execute this command:
Code:
adb devices
And see the output, if it says something like:
Code:
**some_number** recovery
then it means there is no problem in the detection of your device by PC, if it does not, then check if the micro USB socket in the device is in good condition.
Click to expand...
Click to collapse
I did it and it says some number and recovery
DigiGoon said:
And I must ask: Are you able to do any operations on device via PC after connecting it?
Click to expand...
Click to collapse
In "usb storage media" or something like that? Yes, I do.
Ceranzuo said:
I did it and it says some number and recovery
Click to expand...
Click to collapse
Okay, then it means that there is no problem in the connection. You are using SP Flash tool in which mode?
Sent from my PLK-L01 using Tapatalk
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Quaczi said:
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Click to expand...
Click to collapse
I had this problem in my Nokia 7 Plus, then i used and installed "minimal adb and fastboot" file which detected my phone in fastboot. It installs in program file with a folder named "minimal adb and fastboot"
Sent from my Redmi K20 Pro using Tapatalk
You need to enable "USB debugging" in the developper options
ImEraaz said:
You need to enable "USB debugging" in the developper options
Click to expand...
Click to collapse
It is enabled.
And ill try with the minimal adb option
Update:
Still not working
I have same problem, there is no way to recognize my 9t pro in fastboot mode... i cant do anything
First it should be intel pc
Try to install Xiaomi drivers and adb
Boot to recovery and fastboot while connecting to usb to install the drivers
Then check again
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
simpn said:
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
Click to expand...
Click to collapse
Try changing ports / connect to another pc
Install proper drivers .
Is your bl unlocked now ?
Got it to work under win7 with great help from this post.
What I did was:
Update to the latest miui version (to MIUI Global 11.0.3, as prompted in system settings, I hadn't bothered to update because I just want to throw miui out)
Disable OEM unlock
Reboot
Enable OEM unlock again
Reboot into fastboot
Then the phone showed up as an unknown device in Device Manager
Right clicked the device and updated the driver, chose to search for drivers in the miflash_unlock-en-3.5.1108.44\driver\xp-win7-win8 folder
The device now lists as an Android Bootloader Interface device
And now:
$ fastboot devices
e150445 fastboot
MiFlash unlock detects the phone, and I could proceed with unlocking. Still have to wait though. Tried the older-version-trick as suggested here, but that just told me to update to the latest version. Guess I'll have to wait a week then...
Hope this helps someone. This is the most tedious unlocking procedure I've encountered so far...
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
jm_sanders said:
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
Click to expand...
Click to collapse
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
riyan65 said:
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
Click to expand...
Click to collapse
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
jm_sanders said:
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
Click to expand...
Click to collapse
To get adb device, you need to enable adb debugging and enable for your pc on phone
riyan65 said:
To get adb device, you need to enable adb debugging and enable for your pc on phone
Click to expand...
Click to collapse
Of course enabled as stated in my first post.
Regards
My rednote is not being recognised by my Win10 PC when in fastboot mode. ADB is fine but the moment it boots into fastboot, it disappears. I've tried numerous different drivers now, and restarted the PC to disable driver signature but nothing seems to work. Fastboot mode is recognised when the phone is connected to my linux laptop.
Is there a trick to it? Or a guaranteed set of drivers that work both adb and fastboot?
I want to unlock my phone but cannot run the official MiUnlock tool.
LesGirauds said:
My rednote is not being recognised by my Win10 PC when in fastboot mode. ADB is fine but the moment it boots into fastboot, it disappears. I've tried numerous different drivers now, and restarted the PC to disable driver signature but nothing seems to work. Fastboot mode is recognised when the phone is connected to my linux laptop.
Is there a trick to it? Or a guaranteed set of drivers that work both adb and fastboot?
I want to unlock my phone but cannot run the official MiUnlock tool.
Click to expand...
Click to collapse
there is hundreds of tutos in youtube, go and check them
tutibreaker said:
there is hundreds of tutos in youtube, go and check them
Click to expand...
Click to collapse
And I've viewed a number of them. Could you link to one that actually works?
Seriously, I'm not stupid. I've tried a number of supposed solutions. I'm not a Windows geek, it's true, but I'm happily techie on UNIX platforms. Maybe this is something other than the actual driver. I'm more than happy to learn.,
LesGirauds said:
And I've viewed a number of them. Could you link to one that actually works?
Seriously, I'm not stupid. I've tried a number of supposed solutions. I'm not a Windows geek, it's true, but I'm happily techie on UNIX platforms. Maybe this is something other than the actual driver. I'm more than happy to learn.,
Click to expand...
Click to collapse
For those who have problems installing , you need to create a new folder called "Desktop" in C:/Users/*Your user*
LesGirauds said:
My rednote is not being recognised by my Win10 PC when in fastboot mode. ADB is fine but the moment it boots into fastboot, it disappears. I've tried numerous different drivers now, and restarted the PC to disable driver signature but nothing seems to work. Fastboot mode is recognised when the phone is connected to my linux laptop.
Is there a trick to it? Or a guaranteed set of drivers that work both adb and fastboot?
I want to unlock my phone but cannot run the official MiUnlock tool.
Click to expand...
Click to collapse
This is exactly my problem on Redmi note 11S. I already tried a lot of drivers and tutorials and still no succes. In linux fastboot works.
PS: Les Girauds, you can unlock bootloader by mtkclient (linux), not just via official tool (Mi unlock). I already did it.
Magic Cucumber said:
you can unlock bootloader by mtkclient
Click to expand...
Click to collapse
Thanks, might give that a go.
I tried another UNIX based unlock solution yesterday (a python prog from GitHub) and whilst it didn't work cleanly (nor successfully unlock the device) I did see in the garbled error message returned about having to wait 121 hours. So maybe the phone will be successfully unlocked on Tuesday!
tutibreaker said:
For those who have problems installing , you need to create a new folder called "Desktop" in C:/Users/*Your user*
Click to expand...
Click to collapse
Thanks, that's worked. The Yt video didn't show for me so I copied it's URL and opened in a separate browser window. The video went through the process for Win 11 but I guess it's the same for Win10 (my system), and it worked so that's OK. Weird thing is, it was only an install of the generic adb drivers which I'd installed previously anyway, and had been using for some time, doing updates on my Lenovo tablet etc. So they were there and working once upon a time. I can only assume that the process of installing the MiUnlock screwed them up somehow.
@Magic Cucumber - it might be worth you simply reinstalling the standard adb platform tools, It might give you back fastboot access
Magic Cucumber said:
you can unlock bootloader by mtkclient (linux),
Click to expand...
Click to collapse
Thank you. It worked. The MIUnlock said I had to wait but mtkclient did it immediately.
Now I'm going to flash a custom ROM, and maybe twrp, just have a device I'm happier with. Xiaomi phones maybe good value but I don't like the stock software.