Developer option shows bootloader as locked but after reboot bootloader shows as unlocked . twrp working but Fastboot not working so I'm afraid I might brick my device as I can't flash fastboot rom. Please help.
I wanna know what you mean by 'Fastboot not working'. Does it mean you can't boot into fastboot mode, or does it mean you can't access fastboot commands on your pc?
Also i wanna know, while unlocking Bootloader. Did you used commands
Code:
fastboot oem unlock
and
Code:
fastboot oem unlock_critical
?
The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool
pythonner said:
The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool
Click to expand...
Click to collapse
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.
It's same for me.
You can ignore that safely.
eleven.co said:
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.
Click to expand...
Click to collapse
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom
VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
Actually when I type fastboot devices in platform tools the device is not even detected. So I'm afraid that if I flash custom rom and brick it I will be unable to flash even the official fastboot rom.
pythonner said:
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom
Click to expand...
Click to collapse
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.
eleven.co said:
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.
Click to expand...
Click to collapse
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device
pythonner said:
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device
Click to expand...
Click to collapse
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
Now developer options is showing as unlocked and adb is also working good
but fastboot is still not working when I type fastboot devices It returns nothing
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
What could be possible explanation to adb working but fastboot not working. The usb cable is tight and bootloader is unlocked even in developer options
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
I just realised that I flashed twrp using the root app flashify. Could that be the reason for root not working
VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
If you're rooted and have magisk hide enabled, it's normal, Magisk spoofs locked bootloader to pass safetynet in MIUI
Related
My C6903 in LP 5.1.1 doesn't take photos (or videos) when the app tries to focus. Without focus enabled (using other app) it goes perfectly. I've tried with 14.6.A.1.236 Customized BAL, 15.5.A.0.242 Movistar AR and a few more, all obtained from XperiFirm.
I tried pushing that "4k and timeshift" .zip which I read could fix the camera but no luck.
Curious thing is that Rooting Status shows "Unknown", I don't know if this could be related or not. I bought the phone on eBay (used) and I couldn't tell you if it's been unlocked or not.
But I know that everything can't be messed up because in JB 4.3 (14.2.A.1.136 Generic BAL from XperiFirm) camera works well, and Rooting Status shows "Bootloader Unlock Allowed: Yes"; And in KK 4.4 (updated via OTA from mentioned JB firmware) camera stops working in the same way but Rooting Status keeps on "Bootloader Unlock Allowed: Yes".
What could I try? I think I've already read everything related to the Rooting Status Unknown and Camera freeze problems in this forum and still have no clue (even in other Xperias forums too).
Thanks by the way
PS: Yet I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
matidx said:
PS: Yes I didn't tried unlocking bootloader just because it may bring more problems, but if needed I would do it in a blink
Click to expand...
Click to collapse
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
kentexcitebot said:
This is definitely a bad way to troubleshoot your problem, but go ahead and make yourself a backup of your phone's TA partition and unlock the bootloader of your phone. As long as you made a backup of the partition, the DRM keys will stay intact when you re-lock the bootloader; thus, you won't lose any exclusive Sony features upon restore. Make sure you have the proper adb and fastboot drivers before you begin.
Backup TA partition: http://forum.xda-developers.com/showthread.php?t=2292598
Unlock bootloader: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Flash any custom ROM (don't flash the Marshmallow ROMs) found in either the Android Development or Original Development page for Z1. You can also flash a modified Sony ROM in the Android Development section that has mostly all of the features in Sony's stock ROM plus some additional ones picked from CM/AOSP ROMs. Either way, if your problem is fixed, then it's a problem with the FTFs you flashed. If not, restore your TA/DRM keys (it'll re-lock your phone's bootloader) and report back.
Good luck fixing your problem!
Click to expand...
Click to collapse
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
matidx said:
Tried that but it looks like the volume up button isn't recognized when booting or something like that. What really matters is I can't enter to fastboot mode, tried everything. Any ideas?
Click to expand...
Click to collapse
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
kentexcitebot said:
Install proper drivers for fastboot. Power the phone off completely, then while plugging your phone into the computer, hold the top volume button. You should be able to enter fastboot if fastboot drivers are properly set up.
Click to expand...
Click to collapse
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
matidx said:
Is there a way to know if fastboot drivers are properly installed? I've checked and reinstalled them about 5 times, but I'll try again tomorrow just to be sure I'm not missing anything.
Click to expand...
Click to collapse
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Code:
fastboot.exe devices
you'll know that fastboot is working and drivers are set up correctly. If you look at your device LED, the LED will be lit blue. Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
matidx said:
I don't know if there are different drivers but always installed the flashtool ones. By the way I'm running Win10 but also tried in Win7 and no luck.
Click to expand...
Click to collapse
Go here to download the correct fastboot driver files: http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS4zLTIwMTQwMjA5
If your computer can successfully detect the device and output it's serial number when you input through command prompt:
Click to expand...
Click to collapse
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Remember: you need to already have downloaded and installed the applications through the executabe in the adt folder to get the fastboot and adb applications.
Click to expand...
Click to collapse
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
By the way, I'm also having this issue... http://forum.xda-developers.com/xperia-z1/help/baseband-lost-reboot-t3352858
Maybe it could be related someway (like motherboard going bad or something else).
matidx said:
What is the adt folder? You mean adb or the obsolete Android Development Tools (now Android Studio)?
Click to expand...
Click to collapse
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
matidx said:
Right, I know what that command line does, but that will work only when drivers are properly installed AND phone is detected. What I believe is that there are some kind of problems with the phone to not go into fastboot mode, so it wont be detected at fastboot, always in flashmode.
Is there a way to know if drivers are properly installed even if the phone isn't recognized?
Click to expand...
Click to collapse
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
kentexcitebot said:
My apologies, I should've been more clear and double-checked the information!
They apparently renamed the file. I was referring "adt" to my folder that's dated all the way back to 2013, so....whoops!
You can grab the download from here: http://developer.android.com/sdk/index.html. If you don't want the entire bundle, search for "Get just the command line tools" and click on the links for your platform.
Just download the S1 driver file through the link I provided earlier, install, reboot computer, then run the same command as I told you from my previous post: if it outputs the serial number of your phone, then you're fine; but if it doesn't, post back. As long as your computer can establish a basic connection to your Z1 (PC can see it in flash mode, could access it somehow), your phone is capable of fastboot.
Click to expand...
Click to collapse
I think I've followed everything right but to be clear I'm gonna explain what I've done so far:
- Installed Android Studio (I believe it comes with those "just the command line tools").
- Installed Flashtool's driver (same as the DoomLord link you provided, even a later update than that link), also did that thing about "Disable Driver Signature Enforcement" because I'm on Win10 64bit.
- Always checked by cmd command line "fastboot.exe devices", I've never get any error (so cmd always detected it as a valid command line) or any other cmd print.
- I have a TA backup but after I made it tried to unlock bootloader but no luck. Anyway, just restored the backup and only sign I got is "Upgrading NFC firmware" or something like that after booting, the "NFC upgrade" went well but still no fastboot access.
---
- When I plug the usb + press volume up button to try get fastboot mode, phone's led goes red then green then it goes off and in flashtool I get flashmode with no led on.
---
By the way, I have an Xperia SP and already unlocked bootloader so I pretty know how it should go. Having no problem with it accessing fastboot or even locking or unlocking on the XSP.
Because of this and baseband problem, I can't stop thinking motherboard is messed up.. But anyway, whatever you think I could try just let me know.
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
hammy88 said:
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
Click to expand...
Click to collapse
i recommend for you to KDZ 20p refurbished..
and heres the instruccions same as 20i
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
hammy88 said:
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
Click to expand...
Click to collapse
did you click on screen when you gave the command to go into fastboot it shows some sort of numbers and leters and asks you if you want to allow phone .??/ did you
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
hammy88 said:
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
Click to expand...
Click to collapse
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
raptorddd said:
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
Click to expand...
Click to collapse
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
hammy88 said:
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
Click to expand...
Click to collapse
can try another computer maybe. i use the drivers from LGUP..
am afraid i do not know how to proceed from here. am pretty sure you are not alonei gave read someting similar but.. i didnt pay attention
I tried 3 other computers , did not help resolve the issue
hammy88 said:
I tried 3 other computers , did not help resolve the issue
Click to expand...
Click to collapse
i came across this try it.
http://forum.xda-developers.com/showpost.php?p=69339003&postcount=2
Use Linux dude, also try different cables. My stock g4 came with a bad cable that only charged.
I've had exactly the same problem as hammy88. Is what is referred to as "fastboot mode" the same as download mode? I know it's relatively easy to get into download mode. But "adb reboot bootloader" doesn't work for me.
Fastboot mode ≠ Download mode
If you did tick "Enable OEM unlock" , and adb reboot bootloader doesn't work, then I guess is BL is locked now.
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
hammy88 said:
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
Click to expand...
Click to collapse
Brother, be calm. Find the fastboot drivers. And update.
You will figure it out. Just do it.
With your phone on, make sure under developer options oem unlocking is allowed. . .
Then plug in the device to the computer....
Time for the fun to begin....
In ADB
Adb reboot bootloader (it takes your phone to bootloader mode)
Fastboot flashing unlock (warns you not to)
Click Yes when prompted on phone. (YAY!!!)
Please don't forget to save anything you need from ur phone , unlocking your bootloader will fully wipe your device ?
Quick question, Is it supposed to just be text on the bottom left that says fastboot mode?. I've done this on a couple of other phones but this is the first time I haven't seen a menu, also when I run fastboot flashing unlock I'm stuck on fastboot flashing unlock.
TheRedPandaSSN said:
Quick question, Is it supposed to just be text on the bottom left that says fastboot mode?. I've done this on a couple of other phones but this is the first time I haven't seen a menu, also when I run fastboot flashing unlock I'm stuck on fastboot flashing unlock.
Click to expand...
Click to collapse
Yes fastboot mode ... On the left bottom.
Do u have mediatek drivers installed ?
Did u go into developer options and click on the allow oem unlocking ?
greeneyez15o said:
Yes fastboot mode ... On the left bottom.
Do u have mediatek drivers installed ?
Did u go into developer options and click on the allow oem unlocking ?
Click to expand...
Click to collapse
I believe I have them installed but I'll try again, thanks.
TheRedPandaSSN said:
I believe I have them installed but I'll try again, thanks.
Click to expand...
Click to collapse
Edit: I've tried a couple of drivers but none seem to work.
TheRedPandaSSN said:
Edit: I've tried a couple of drivers but none seem to work.
Click to expand...
Click to collapse
https://androidmtk.com/download-mtk-driver-auto-installer
Try this
Tied all sorts of drivers but no luck. I'm stuck in fastboot <waiting for device>. Any suggestions?
USB debugging
ycgr2002 said:
Tied all sorts of drivers but no luck. I'm stuck in fastboot <waiting for device>. Any suggestions?
Click to expand...
Click to collapse
Have you enabled USB DEBUGGING?
ycgr2002 said:
Tied all sorts of drivers but no luck. I'm stuck in fastboot <waiting for device>. Any suggestions?
Click to expand...
Click to collapse
Here
fastboot does not respond to commands
brunkonjaa said:
Here
Click to expand...
Click to collapse
Same issues, run adb reboot bootloader and reboots but in funky fastboot. When sending fastboot commands such as fastboot devices nothing happens its not responding. Also if you get into fastboot via power and volume up, and connect to pc and try to run any fastboot commands no response back.
jackmaddy said:
Same issues, run adb reboot bootloader and reboots but in funky fastboot. When sending fastboot commands such as fastboot devices nothing happens its not responding. Also if you get into fastboot via power and volume up, and connect to pc and try to run any fastboot commands no response back.
Click to expand...
Click to collapse
Turn on your phone, and do not connect to pc. Revoke USB debugging authorisation. Disable USB debugging. Enable USB debugging. Now connect your phone to pc. You should get a message on your phone about allowing USB debugging from that pc. Click don't ask again and then yes.
If you don't get that message try accessing phones storage through pc , that should prompt the phone to ask you about allowing USB debugging from that pc.
So click yes.
Now you should be able to run fastboot commands without problems.
brunkonjaa said:
Turn on your phone, and do not connect to pc. Revoke USB debugging authorisation. Disable USB debugging. Enable USB debugging. Now connect your phone to pc. You should get a message on your phone about allowing USB debugging from that pc. Click don't ask again and then yes.
If you don't get that message try accessing phones storage through pc , that should prompt the phone to ask you about allowing USB debugging from that pc.
So click yes.
Now you should be able to run fastboot commands without problems.
Click to expand...
Click to collapse
No, sorry that is wrong.
ADB permission is not needed for fastboot. These are 2 different programs, with different protocals .
The fact there is no response from phone when in fastboot is a sign that pc drivers are not correctly installed, or the fastboot program needs to be updated.
mrmazak said:
No, sorry that is wrong.
ADB permission is not needed for fastboot. These are 2 different programs, with different protocals .
The fact there is no response from phone when in fastboot is a sign that pc drivers are not correctly installed, or the fastboot program needs to be updated.
Click to expand...
Click to collapse
You are absolutely right. Thanks for clarifying the issue. Spot on !!
Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong
Maharram said:
Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong
Click to expand...
Click to collapse
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.
Tianhe said:
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.
Click to expand...
Click to collapse
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )
Maharram said:
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )
Click to expand...
Click to collapse
I know this might sound silly but are you using the latest platform tools version ?
Tianhe said:
I know this might sound silly but are you using the latest platform tools version ?
Click to expand...
Click to collapse
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)
Maharram said:
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)
Click to expand...
Click to collapse
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)
Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7
Click to expand...
Click to collapse
Yeah im using win 10 redstone (latest version)
But also i did it on win 10 with Android 9
Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)
Click to expand...
Click to collapse
Going to try this. Thanks a lot <3
Maharram said:
Going to try this. Thanks a lot <3
Click to expand...
Click to collapse
Hope you get the desired result. I am also on Win 10 latest update and I had faced issues initially. I have also added a registry hack so that everytime I open CMD with shift+right click it opens with administrator privileges.
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!