Rooting problem and strange phone behaviour while it - Redmi 9A Questions & Answers

Hello. I'm an owner of a Xiaomi Redmi 9A and I have following rooting problems with it:
1. while beeing in phone's fastboot mode and after sending from the computer's terminal (after sucessfull connection):
"fastboot oem unlock"
the phone "thinks" for a short bit before restarting itself without doing anything
2. I have a Xiaomi account bound to the phone and when selecting the "check unlock state" the phone ask me to turn off wifi, enable the (paid) data transfer and bind the phone to the account
3. while using the official Xaiomi unlock tool (with was downloaded from the phone producer's website), the phone isn't even seen in it
Could anyone help me ?

Try installing usb drivers or the phone will never be detected.

VD171 said:
Try installing usb drivers or the phone . never be detected.
Click to expand...
Click to collapse
in case of adb and fastboot, I had used them on Linux.
Only the official unlocking tool was for Windows, on with the usb drivers were installed.
Linux detect it without any issue

Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com

VD171 said:
Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com
Click to expand...
Click to collapse
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.

mcgiwer said:
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.
Click to expand...
Click to collapse
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?

VD171 said:
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?
Click to expand...
Click to collapse
yes in both cases... I have even enabled the "oem unlock" option in the setting

Install windows on partition 30Gb, change cable

yaro666 said:
Install windows on partition 30Gb, change cable
Click to expand...
Click to collapse
The cable is new and I won't wipe my Linux to install a Windows (about with I have a bad opinion)

Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.

yaro666 said:
Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.
Click to expand...
Click to collapse
Question: Why do you push so much on me to install Windows?
This forum is dedicated to mobile phones and my topic is about anormal phone behaviour of a phone while attempt to root it. Wiping out a safe Linux and installing a Windows won't help at all....
I tryed to root the phone on friend's laptop with a Windows (with the latest drivers and software installed) and it didn't worked.
I suspect that the producer probably has fabrically instaled a damaged or improper firmware

As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly

yaro666 said:
As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly
Click to expand...
Click to collapse
hello. You had missread my post. I wrote that it isn't seen only in the unlock software. Fastboot and ADB detect it correctly

Related

[Q] Soft brick but no adb/fastboot connection

Hey
A couple of days ago i tried to install the latest CM12 nightly. After updating it my phone crashed everytime it booted up. I did a factory reset and tried to flash older versions but nothing seemed to work so i went into CWM recovery 6.0.4.5 and pretty much formatted everything.
I still have access to the bootloader and recovery but my Windows 8.1 PC doesn't recognize my phone ("Unknown usb device" "Windows has stopped this device because it has reported problems. (Code 43)") I can't access my phone with adb or fastboot now. This looks like a driver problem but i tried a lot of different drivers on multiple PC's.
What can i do now?
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Darth said:
Try this thread, could help...
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
zagorteney said:
He said that he can't access his phone with adb or fastboot. Maybe he must try to resolve driver problems first?
Click to expand...
Click to collapse
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer. ?
Darth said:
It's a driver issue likely. Starting from scratch in the thread I linked addresses drivers. Likely ones he hasn't tried.
Though, a few other ideas are trying another cable, another USB on the computer. And last... Try another computer.
Click to expand...
Click to collapse
And in future: please, stay on stock.
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
dermaxe said:
No driver seems to work. Is it possible to install a zip from an usb flash drive with OTG?
Click to expand...
Click to collapse
Try this: http://nirsoft.net/utils/usb_devices_view.html
It helped me a few times.
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
I uninstalled everything from there that was android-related. After plugging in my phone (in bootloader mode) my PC detects it as " Google Nexus BootLoader Interface" but "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
Did you use USBDeview or you just manually removed all drivers that you saw?
I went into USBDeview and uninstalled everything that was android related
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
How do i enable usb debugging without any os?
dermaxe said:
How do i enable usb debugging without any os?
Click to expand...
Click to collapse
chaco81 said:
ummm why hasnt everyone mentioned the very basics? USB Debbugin enabled?
you already flashed and reset phone...
because after any reset, that will default back to unchecked and u wont be able to adb or fastboot until that is checked
Click to expand...
Click to collapse
USB debugging enabled is only needed when using Adb from within the Android OS. It's not needed for adb use in recovery mode, and never needed for fastboot.
??
good to know
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
dermaxe said:
Okay so i don't have to do this but i still have that driver problem. It is recognized as Android Bootloader Interface but i still get "this device cannot start. (code 10) an invalid parameter was passed to a service or function"
Click to expand...
Click to collapse
For me this sounds more like computer realted problem rather than device. If you can try all of those steps ( installign drivers, etc ) on another pc maybe this will solve your issue
Just tried it on a fresh installation of W7 but my device wasn't recognized and i couldn't install any drivers for it. How can it be a PC related problem if it doesn't work on so many different configurations?
If you run it on VirtualBox, see this answer (prepend http, I can't post links): superuser.com/a/887249/239087
To make it short, you need VirtualBox Extension Pack, and you need to configure the USB port to use USB 2.0 at least.

Can't unlock bootloader after upgrade

Hi
My phone is international NXT-L29
I was on Ephemeral B180 rom but i decided to upgrade it to get emui 4.1
I flashed back stock b180 rom, and after I flashed stock b321 rom
ROM works great but i would like to get root and twrp back again, but everytime I try to go through fastboot i get this screen on picture.
I logged into my dc unlocker again and followed the procedures (manufacture mode, unlocking,...) and dc unloccker tool informs that the phone was unlocked...but no, when I do adb reboot bootloader i still get the same message on the picture.
I saw other suggestions here on XDA, i confirm oem unlock is activated on developer options...i made factory reset and then "vol+- power" (with or without phone connected to PC) but i dont't get any option to unlock bootloader. I always arrive to a menu saying that the phone is looking for upgrade and tries until 5% is reached... (if I keep waiting it does not fisplat error message, only waits and waits and after a while it reboots normally (i don't have any dload folder either on phone or sd card)
Any suggestion to solve this is highly appreciated
many thanks
Try to get ur unlock code from huawei website maybe this can help.
Did you run the bootloader unlock command with your unlock code again?
Ephemera said:
Did you run the bootloader unlock command with your unlock code again?
Click to expand...
Click to collapse
the only command my phone accept is adb reboot bootloader
Then i get the screen of picture that I posted, which says that it is a cold reboot (?)
Whem I reach this point it doens not respond to anything else taht I type on Command line (I type fastboot oem unlock (and the code) but on pc screen i read 'ewaiting device' and nothing happens on phone
gm007 said:
Try to get ur unlock code from huawei website maybe this can help.
Click to expand...
Click to collapse
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Can I replace the stock boot.img that comes inside the UPDATE.APP file byone decrypted boot image of same rom?
If that would be possible then flashing this "modified" UPDATE.APP would solve the problem?
Many Thanks
pasil.pt said:
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Click to expand...
Click to collapse
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
grofock said:
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
Click to expand...
Click to collapse
I don't see any kedacom usb device folder...
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Ephemera said:
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Click to expand...
Click to collapse
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
pasil.pt said:
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
Click to expand...
Click to collapse
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
grofock said:
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
Click to expand...
Click to collapse
YES!!!!!!
many thanks to you. grofock, and to ephemera, and XDA
At last i got it done. (Huawei are so tricky compared to samsung...but at least they do not explode
gm007 said:
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
Click to expand...
Click to collapse
You were probably right because i recently changed PC and aeverytime w10 upgrades I pray...
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
timasan said:
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
Click to expand...
Click to collapse
try grofock's hints about control panel and Device manager on windows....
pasil.pt said:
try grofock's hints about control panel and Device manager on windows....
Click to expand...
Click to collapse
I try it on four different PCs and still error 43 "wrong descriptor".
timasan said:
I try it on four different PCs and still error 43 "wrong descriptor".
Click to expand...
Click to collapse
Maybe explain more what you did,what are you trying to do and which tools you used.
gm007 said:
Maybe explain more what you did,what are you trying to do and which tools you used.
Click to expand...
Click to collapse
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
timasan said:
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
Click to expand...
Click to collapse
Did you install hisuite it has all the drivers and make sure to enable allow hisuite to use hdb in phone settings under security.

Question Fastboot not working in Windows 11 [Resolved]

Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
WhiteCoffeeCat said:
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
Click to expand...
Click to collapse
Thanks for the suggestion! I will attempt these. Fingers crossed
I have previously attempted to install adb driver but had some trouble. When installing using Device Manager, the locate .inf dialog refuses to accept my selection. I dont seem to be any error. When attempting to do so via the folder (and sub folders) it says no drivers found. Perhaps i'm doing this totally wrong?
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
eshlad said:
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
Click to expand...
Click to collapse
Put Windows into testing mode before installing drivers in Miflash, adb.. Run cmd prompt as admin and type bcdedit -set TESTSIGNING ON or bcdedit -set TESTSIGNING OFF for disabling testing mode.
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
how?
goila said:
how?
Click to expand...
Click to collapse
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
jholfran3 said:
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
Click to expand...
Click to collapse
Thanks, but that doesn't help, otherwise I've already done it. I had m1 mac and with parallel desktop only the possibility to install win 11.. win 11 sucks.. I installed win10 on an intel mac in parallel and that solved my problem
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
ItsmeeVishal said:
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
Click to expand...
Click to collapse
Have you tried to disable driver signature enforcement in windows 11.
istampal said:
Have you tried to disable driver signature enforcement in windows 11.
Click to expand...
Click to collapse
Yeah, i tried it.
Nothing happened.
ItsmeeVishal said:
Yeah, i tried it.
Nothing happened.
Click to expand...
Click to collapse
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
eshlad said:
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Click to expand...
Click to collapse
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
What VM were u using?
I'm using parallels Desktop 18
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
I tried to do what u said but don't know what to do next.
Plz see the attached video video and tell me what wrong I'm doing.
After clicking on legacy hardware, what are other steps......
And, thank you so much for reply!
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Titek said:
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Click to expand...
Click to collapse
Hi Tek,
I have had many issues with windows and fastboot,
some cables would work with some of the ports and then not.
My pc has 12 usb ports, yet it was still hit and miss whether fastboot would work on my Poco F3.
I tried your tip and after using a cheapy Targus 4 port usb adaptor, my "FASTBOOT PROBLEMS ARE NOW SOLVED"
now what am i going to do with my 7 surplus USB-C Cables
Many thanks for your TIP

redmi go in bootloader. any ideas what to boot into it?

yes:
my desktop (cause im in bootloader mode i'll need to use it) is artix linux with kde. sadly i cant install on it adb/fastboot and other drivers due to lack of systemd and empty repos so will do it probably from a random linux-based bootable usb...
my mobile is (as was in title) - xiaomi redmi go - european version.
what means ? my mobile have encryption after removing system what makes me unable to boot things... for the now i can still boot stock ROM. although i wanted to remove all associations with google in system (all google apps, bugs caused by removal etc...)
any ideas what i should do with it? wanna have it to tomorrow cause we use our mobiles at work and my current mobile got "marked as over outdated" by boss so i cant use
why noone ?
This same things happen with me also but You need a USB cable to connect your phone to PC. You need to download ADB and Fastboot Tools to your PC and Extract it First of all, you need to enable the developer option and activate the USB debugging on Xiaomi Redmi Go. Now activate the OEM unlock status on your Xiaomi Redmi Go DinarGuru.com
Christinakim said:
This same things happen with me also but You need a USB cable to connect your phone to PC. You need to download ADB and Fastboot Tools to your PC and Extract it First of all, you need to enable the developer option and activate the USB debugging on Xiaomi Redmi Go. Now activate the OEM unlock status on your Xiaomi Redmi Go
Click to expand...
Click to collapse
this i actually know. i have one heavily modded lg so im not a newbie. its more about "encryption unsuccesful" broked roms leading to non-booting state (bootloop) etc... nothing from xda surely doesnt work, yep
surely nothing from : https://forum.xda-developers.com/m/techyminati.8245761/ works. was trying loads of times always bootloop. recovery posible to load but then tends to not make factory reset and lock in "encryption unusccesful", and thats worst... im in europe but have global version btw...
dead chat ?

Question Need Help - ROG 5s bootloop

Hi All
I have ROG 5s tencent edition. it was modified by seller to global. I have been using it for more than 1 year now. Last night something happened and it went off. I tried turn it on but it kept bootlooping at logo. It is not detetedable by computer because bootloader was locked by seller before selling. I had no idea about that at that time.
MY device is now in bootloop. I can open bootloader but it won't take me to recovery mode. Fastboot commands are also not working . Phone not found by computer in any state. Can any one provide me with some pointers on how an i flash firware,
Recoery is not opening. When I select it from bootloader it keeps bootlooping
Fastboot is not seen by computer. Tried many cables, both ports.
If anyone can guide me that be a huge favor as this is my daily driver
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Andrologic said:
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Click to expand...
Click to collapse
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
dksoni411 said:
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
Click to expand...
Click to collapse
If there isn't a hardware issue with the device, you should be able to.
Try to delete the driver and re-install it. Use the official Android USB driver from the SDK as opposed to Qualcomm drivers from random places on the net. Plug it in from the side port and try to turn it on while connected. Have Device Manager in Windows open and notice changes. Read out what it is recognized as. If absolutely nothing, then it's the cable, Windows or the device may really have a motherboard defect.
I believe it's more likely motherboard. Is there any fix for it?

Categories

Resources