Related
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
Any way you could try it on a Windows 7 machine?
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Here's an easy way to install Fastboot/ADB.
Once that is installed you'll have to change your commands to fit the file path of the fastboot files.
For example:
Code:
fastboot flash logo C:\Users\OP\Desktop\logo.bin
[/COLOR]
savagebunny said:
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Click to expand...
Click to collapse
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
This minimal version of fastboot is a lot smaller and worked for me.
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
DragonRyderX said:
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
Click to expand...
Click to collapse
A windows 7 machine is unnecessary. I used windows 8.1 pro x64 to perform the whole upgrade process without a hitch. If mofo functions correctly, that means the fastboot drivers are installed correctly. If you start up minimal adb/fastboot, plug in your phone while it's in fastboot mode and type "fastboot devices," what do you get?
EDIT: Duh. You already said that it says returns nothing. Well in that case there has to be some sort of problem with the USB connection or the minimal adb/fastboot installation. Maybe try running the minimal adb/fastboot shortcut as administrator. I don't remember having to do that on mine, but who knows?
St33ve- see OP, nothing listed for adb or fastboot devices commands in their respective modes.
Have you tried a different USB cable?
Yonnor said:
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yes, about 7 different ones. 4 that I am sure have worked before, and no physical damage to them.
You said Mofo is able to see your device though, so that's kind of throwing me through a loop. You could try a fresh install of the Minimal ADB, and double check your drivers?
That's a sign of drivers not being installed!
Try opening up device manager n see if the driver is not installed.... If u see a device with an exclamatory mark n "quark" somewhere in it... The drivers aren't installed...
When the phone is in fastboot mode, the phone is listed as quark fastboot, but no exclamation mark. I reflashed computerfreaks image (KK) without an issue, but still isn't recognized in fastboot or Adb. I really want to flash me some Lollipop! I have crack flashed with every phone I own. I'm going thru withdrawals here LOL.
i am having the exact same issues. I've reinstalled drivers, switched usb cords and have had no success.
I'm not certain what actual fixed mine because I tried so many things but I got mine to recognize my phone. I think what did it was revoking the USB debugging authorizations and deleting the adb files on my computer under username/.Android. Then reauthorizing my phone. That and I believe I may have had duplicate drivers interfering with each other. Hope this helps
Hallelujah, I have lollipop!!!
I do not know exactly what the issue was but after factory resetting windows 8.1, and manually loading each driver for adb and fastboot, it works (again). I wish there was a Thank All Button. THANKS ALL!!!
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Da-JesuZ said:
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Click to expand...
Click to collapse
This is how i always root the phone:
- Enable usb debugging and ENABLE OEM UNLOCKING in developer options
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
- Flash TWRP in fastboot
- Go to recovery and flash a modified boot.zip (all custom kernels will do)
- Flash the latest superSU.zip, also in recovery
- Done
Here is a tut for the adb setup (Windows) http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/.
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Da-JesuZ said:
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Click to expand...
Click to collapse
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
gee2012 said:
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
Click to expand...
Click to collapse
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Da-JesuZ said:
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Click to expand...
Click to collapse
You only have to flash the TWRP.img file in fastboot, the rest (boot/superSU) are zip files to be flashed in recovery. I have no experience with Vista so can`t help you there, maybe there is some info about it on Google/YouTube.
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.
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