Related
I want to root my tablet so I flashed TWRP 2.6.0.0 using fastboot everything works fine.
But now I want to install the zip to root the tablet, problem is TWRP cannot mount any storage, internal sdcard external sdcard nothing at all is alway says E:Can't mount 'xxx' on anything I tap.
I tried CWM, and 2.5.0.0 and nothing seems to work.
I can boot fine in the stock OS, everything works fine but that
My bootloader is 10.6.1.27.1-20130711
Can anyone help me?
Ok now it is bad, I tried to factory reset using the bootloader (power + volume down)
It booted in the buged TWRP and now it keeps booting in TWRP and I cannot even reach the bootloader
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
aarsyl said:
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
I cannot get this to work on Windows 8, I have Asus Transformer ADB interface lister in device manager but I cannot see my device with the adb devices command.
Also, in TWRP when I try adb sideload it says failed.
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Buster99 said:
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Click to expand...
Click to collapse
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Matiosse said:
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Click to expand...
Click to collapse
fastboot should work. hold Vol-down and reset the device and keep vol-down pressed. it should go to fastboot. when you're in fastboot connect it to your laptop and see if the OS recognized your device - if not you have a driver issue. resolve that by installing the asus driver or the newest google generic drivers.
when you can see your device on dosprompt/powershel with fastboot devices then continue with getting recovery to work.
btw- stuck in twrp means? booting twrp (teamwin screen) but not responding?
good luck
-Buster
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Matiosse said:
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Click to expand...
Click to collapse
but you are still able to boot into android?
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Matiosse said:
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Click to expand...
Click to collapse
can you boot into twrp? and i mean just boot into it? so that you see install, backup, restore etc. buttons?
if yes - twrp has an adb mode
connect your tab in twrp to your pc (check that you can see it - adb devices) if yes type: adb reboot bootloader
and you should boot into that. test it with fastboot devices.
most important thing is that you get into fastboot or a working recovery to flash or prepare to flash a (custom) rom back onto your device.
Buster
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Matiosse said:
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Click to expand...
Click to collapse
learn to crawl before you run :angel:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Matiosse said:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Click to expand...
Click to collapse
dude - you can't boot into android anymore, you can't boot into fastboot to your own accord - yet you try to sideload stuff in twrp for what ever reason.
i gave you more hints and tips in my previous posts and link to get it to work yet it eems you did none.
so don't get me wrong - but what excactly is your goal here?
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Matiosse said:
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Click to expand...
Click to collapse
yes i read your posts - but im still unclear what you are trying to accomplish with sideload?
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?) "adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
-B
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Matiosse said:
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Click to expand...
Click to collapse
when its connected - is device manager at least showing it as faulty or not at all? (yellow triangle exclamation mark thingy, i just installed asus on my VM) -> see attached file
UPDATE: I succeeded to go in fastboot mode
I couldn't get my tab to be recognized by windows so I installer my Nexus 4 using the toolkit, when it was succesfully installed I could manually install my tab since the "android devices" option appeared in the list when you want to manually install a driver in the devices manager. So I could choose Asus ADB interface.
Now I can boot into Android, but it will go into TWRP as soon as I restart my tablet.
Now I will try the link you sent me to get TWRP recognize my storage so I can flash a new rom, I will let you know if something go wrong.
Thanks for helping
I have tried to update my bootloader
downloaded XT1033_Bootloader_v41.18.zip from http://forum.xda-developers.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793
Extracted motoboot.img from the zip and used twrp to flash boot image.
But now I get this error invalid boot image size failed to validate boot image.
The reason I flashed the image using twrp is because my usb does not work it works only for charging. so no adb and fastboot. I cant get any new files in my phone because the otg is dead as well.
I also tried to flash the boot image from the terminal inside twrp using
flash_image boot /sdcard/motoboot.img
this return error: -1
What you are doing is extremely dangerous. Don't mess around with Bootloaders. The motoboot.img can only be flashed via fastboot.
Alternatively, flash the Android 5.0.1 Stock ROM from here: (and accept the OTA Update to Android 5.1)
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection
Note: The OTA Update will require the ROM to be unrooted (remove supersu from zip before flashing) and Stock Recovery installed. You can also search XDA for the 5.1 OTA Update zip.
This will also update your Bootloader to v41.18.
lost101 said:
What you are doing is extremely dangerous. Don't mess around with Bootloaders. The motoboot.img can only be flashed via fastboot.
Alternatively, flash the Android 5.0.1 Stock ROM from here: (and accept the OTA Update to Android 5.1)
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection
Note: The OTA Update will require the ROM to be unrooted (remove supersu from zip before flashing) and Stock Recovery installed. You can also search XDA for the 5.1 OTA Update zip.
This will also update your Bootloader to v41.18.
Click to expand...
Click to collapse
The problem is that my usb does not work. So I cant use fastboot and can't even get anything into the phone. So I guess getting the usb repaired is the first thing i need to do. Also when I cd into the /boot folder from the terminal inside twrp I dont see anything. The folder is empty. I have a cm12.1 zip in the memory when I flash it I get
This package supports bootloader 0x4118, 0x4119, 0x411A; This device has bootloader 0x4113.
kirantambe said:
The problem is that my usb does not work. So I cant use fastboot and can't even get anything into the phone. So I guess getting the usb repaired is the first thing i need to do. Also when I cd into the /boot folder from the terminal inside twrp I dont see anything. The folder is empty. I have a cm12.1 zip in the memory when I flash it I get
This package supports bootloader 0x4118, 0x4119, 0x411A; This device has bootloader 0x4113.
Click to expand...
Click to collapse
You flash the ROM zip via TWRP.
lost101 said:
You flash the ROM zip via TWRP.
Click to expand...
Click to collapse
The problem is my usb does not work so I cannot get the ROM into the internal memory. Tried OTG as well but that too is dead
kirantambe said:
The problem is my usb does not work so I cannot get the ROM into the internal memory. Tried OTG as well but that too is dead
Click to expand...
Click to collapse
If you are running Windows on PC, try a Linux LiveCD (Ubuntu) - no need to install, simply boot from CD / USB.
In Ubuntu Terminal:
sudo apt-get install android-tools-adb android-tools-fastboot
Test Fastboot:
sudo fastboot devices
Test ADB:
sudo adb devices
lost101 said:
If you are running Windows on PC, try a Linux LiveCD (Ubuntu) - no need to install, simply boot from CD / USB.
In Ubuntu Terminal:
sudo apt-get install android-tools-adb android-tools-fastboot
Test Fastboot:
sudo fastboot devices
Test ADB:
sudo adb devices
Click to expand...
Click to collapse
yes i have ubuntu. I have fastboot and adb as well. but it does not show up in devices. And this problem has been there even when my moto g was working. So I guess there must be some hardware problem with the usb port. Even when Im in bootloader and if I connect usb cable it still says 'Connect USB Data Cable'
kirantambe said:
yes i have ubuntu. I have fastboot and adb as well. but it does not show up in devices. And this problem has been there even when my moto g was working. So I guess there must be some hardware problem with the usb port. Even when Im in bootloader and if I connect usb cable it still says 'Connect USB Data Cable'
Click to expand...
Click to collapse
Make sure to always use the 'sudo' command before any fastboot or ADB command.
It could be the USB Cable, or the port as you say.
Same here in Moto G XT1040 when trying to access Recovery option (from bootloader): "Invalid boot image size! failed to validate recovery image. Boot up failed".
It happened after I tried to upgrade CM (13 > 14) from their recovery mode.
Although I had the same error message of you, my USB was working fine and could enter in Android (although lots of "failed" popup messages).
From Linux I noted that "adb devices" command showed my mobile, but "fastboot devices" not.
After I installed drivers on Windows also "fastboot devices" worked.
It worked like a charm!
How I solved:
1. Windows: install Android SDK (to provide adb and fastboot commands), install drivers, download TWRP (for my specific device model), download CM custom ROM (for my specific device model) and copy to device (adb push);
2. Device: enter in bootloader, connect USB cable;
3. Windows: fastboot flash recovery twrp_image_filename_downloaded.img
4. Windows: fastboot reboot
5. Device: install CM from the TWRP recovery mode.
lost101 said:
What you are doing is extremely dangerous. Don't mess around with Bootloaders. The motoboot.img can only be flashed via fastboot.
Alternatively, flash the Android 5.0.1 Stock ROM from here: (and accept the OTA Update to Android 5.1)
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection
Note: The OTA Update will require the ROM to be unrooted (remove supersu from zip before flashing) and Stock Recovery installed. You can also search XDA for the 5.1 OTA Update zip.
This will also update your Bootloader to v41.18.
Click to expand...
Click to collapse
Hey lost101, I got the same problem as OP and I tried to do what you suggested here, but how do I install stock recovery via adb ? After flashing the 5.0.2 untouched version to my phone, I got the OTA update notification to 5.1, i tried to run it then the phone booted to twrp. If I reboot the phone, the system loads but after a few seconds it reboots again to twrp. What do you suggest?
You can also search XDA for the 5.1 OTA Update zip.
Click to expand...
Click to collapse
Is that what you meant? Can I install it thru twrp? https://forum.xda-developers.com/moto-g/general/ota-xt1033-5-1-brazilian-lollipop-t3196328
Thanks
@POWBlock - Don't mess around with OTA Updates. They can make your phone buggy and slow. Best advice is the flash Optimized 5.1 from thread above or Identity Crisis 6 (Stock 6.0):
[ROM][FALCON][6.0][STOCK] Identity Crisis 6 v1.5c
lost101 said:
@POWBlock - Don't mess around with OTA Updates. They can make your phone buggy and slow. Best advice is the flash Optimized 5.1 from thread above or Identity Crisis 6 (Stock 6.0):
[ROM][FALCON][6.0][STOCK] Identity Crisis 6 v1.5c
Click to expand...
Click to collapse
Yeah, I was actually trying to flash Cyanogen to this phone, but I couldnt do it since bootloader wasnt updated, so, instead of updating to 5.1 thru OTA, I flashed the whole firmware doing this method: https://forum.xda-developers.com/showthread.php?t=2542219 , but I got the file from another forum.
Then I installed TWRP again, then finally installed Cyanogen. But thanks for answering!
xt1032 flash problems
I was recently struggling with out of the blue flash problems. Recovery or boot flash didn't work. Size mismatch error. Recovery on phone was corrupted. System didn't start. Only remote boot recovery using fastboot worked. Eventually I extracted boot.img from the last official lineage 14.1 zip and flashed that to boot. After that all was working again. Hope this is useful to others.
hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks
@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !
i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?
fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.
fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself
Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?
I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?
Hi All,
I had a previously rooted 8142, but it crapped out on me last week, so I've just bought a new one. I'm trying to root it now. I've unlocked bootloader, and installed the TWRP app, but I can't figure out how to root it.
I was running windows and used Xperifix when I did my last one, but now I'm using Ubuntu, and there's not really any software (like Xperifix or One Click Root) available.
I've been using FlashTool, and can get it to show root privelages, but I have no idea how to flash a recovery image using it.
I tried using Platform Tools via the terminal and I think I was able to flash a TWRP recovery image to the device, but the TWRP app isn't seeing it, nor can I boot into recovery mode.
I tried to download a recovery image via the TWRP app, but even when it's downloaded, the TWRP app isn't finding any recovery images despite pointing the app to my downloads folder.
TWRP is also showing "No Root Permissions"
I can't flash SuperSu or any other ROM's without being able to boot into TWRP recovery menu.
Maybe I'll have to install windows to use the rooting software. Does anyone have any ideas? Been messing around with it 6 hours now and still can't boot into recovery.
Thanks for any ideas.
first I dont know if youre using fastboot so do "sudo apt install android-tools-adb android-tools-fastboot" then open a terminal were twrp is located and type fastboot flash recovery "name of twrp".img and then you are ready to go. I dont know if you can use this phone without a specific driver so that can be a problem. If you cant do it that way i recommend you using a virtual machine with windows and run fastboot (platform tools trough there) so you dont have to remove ubuntu.
Also remember how to access fastboot
ricardo99831390 said:
first I dont know if youre using fastboot so do "sudo apt install android-tools-adb android-tools-fastboot" then open a terminal were twrp is located and type fastboot flash recovery "name of twrp".img and then you are ready to go. I dont know if you can use this phone without a specific driver so that can be a problem. If you cant do it that way i recommend you using a virtual machine with windows and run fastboot (platform tools trough there) so you dont have to remove ubuntu.
Also remember how to access fastboot
Click to expand...
Click to collapse
Thanks! I'll try both of those methods over the weekend and report back.
tombow said:
Thanks! I'll try both of those methods over the weekend and report back.
Click to expand...
Click to collapse
well i forgot to mention, the fastboot flash recovery command depends on your android version so take that in count.
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both.
Oneplus 7 pro is running 10.3.0GM21AA
>fastboot devices
>adb devices
List of devices attached
966c8016 device
Trying to use fastboot to flash patched magisk img and install magisk.
Do you enter in fastboot in phone?
Sent from my GM1910 using Tapatalk
Yes tried from bootloader as well
fustyler said:
Yes tried from bootloader as well
Click to expand...
Click to collapse
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
redpoint73 said:
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
Click to expand...
Click to collapse
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
fustyler said:
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
Click to expand...
Click to collapse
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
redpoint73 said:
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
Click to expand...
Click to collapse
Have tried different cables and different machines both pc and mac
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
mnemesis said:
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
Click to expand...
Click to collapse
I ran adb reboot bootloader from pc to boot phone into fastboot.
In the bootloader it states device state is unlocked
However fastboot devices ran from pc still shows no device.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thanks this fixed it.
Issue fixed by billyt1's comment above. case closed.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Giri Prasad said:
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Click to expand...
Click to collapse
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
I have a similar problem. I tried to disable the signature. Installed a new Redmi Note 7 driver. The phone is recognized as an Android phone in the device manager. In Orangefox recovery it is recognized with ADB command. In fastboot it is not recognized. In Orangefox I can't format data. So my ROM is not booting up. So I want to flash fastboot ROM with Fastboot but in Fastboot device is not even recognized.
t
puyow18 said:
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry on the late reply. Pretty sure you can only do fastboot boot boot(recovery).img or\and boot_a or boot_b. Wont let you fastboot flash boot.img.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thank you so much!
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Thank you Thank you Thank you Thank you Thank you Thank you...I have been fooling with this all day
Hi, I already solved this issue (but this only works for xiaomi phone (Redmi Note 7 to be specified), for other brands I think need to download your devices flasher/driver tool)
For Xiaomi user only
1. Download Mi Unlock Tool (https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/) (Version 4.5.813.51)
2. Extract the files anywhere you like
3. Run MiUsbDriver.exe to install the driver
4. Try fastboot devices command
I hope this helps you guys. The Mi Unlock Tool also useful to unlock device locked bootloader.
For other devices maybe can follow this tutorial
Fixed: Fastboot not detecting your Android device
Fix the Fastboot not detecting your device. If your device is not detected by the Fastboot then these tricks will really help you.
www.qasimtricks.com