Hi, I've deleted all storage from my device and all I've got now is TWRP recovery.
I', trying to push a rom through fastboot but my PC won't recognize my device, I have Universal ADB Drivers intalled, also I've got Samsung ADB drivers istalled, and Android SDK installed; yet my device won't show up when I'm in fastboot and typing 'adb devices'.
Obviously I cannot turn Debugging on since I don't have a system.
so...
what CAN I do?
thanks
Lidor167 said:
Hi, I've deleted all storage from my device and all I've got now is TWRP recovery.
I', trying to push a rom through fastboot but my PC won't recognize my device, I have Universal ADB Drivers intalled, also I've got Samsung ADB drivers istalled, and Android SDK installed; yet my device won't show up when I'm in fastboot and typing 'adb devices'.
Obviously I cannot turn Debugging on since I don't have a system.
so...
what CAN I do?
thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2788632
Use drivers and setup from this guide.
Related
So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.
Syflox said:
So I am trying to flash an updated recovery of ClockworkMod onto my device, rooted, bootloader unlocked, etc. and installed the Android SDK to use ADB and fastboot. My Samsung USB driver is installed obviously because when I type "adb devices" it pops up with a mix of numbers and letters, which I assume is my device plugged in. I use "adb reboot bootloader" to get into bootloader and once I am in there my device is not recognizable by fastboot. ADB and fastboot are in the same folder in the C:\ drive, and I have tried using PDAnet drivers as well. I could really use some help! USB Debugging is on in the settings as well.
Click to expand...
Click to collapse
The GS3 does not have fastboot. All flashing is done through odin.
ddggttff3 said:
The GS3 does not have fastboot. All flashing is done through odin.
Click to expand...
Click to collapse
Thanks! Also, how do I update ClockworkMod recovery to the newest one? I've used ODIN before but am not sure if it is capable of flashing .img files.
EDIT: Nevermind, I just downloaded ROM Manager and used that to flash 6.0.2.3
Hi,
I'm trying to install TWRP on my SM-P900 and I can't get it to boot into fastboot mode. I have the Samsung USB drivers and the latest Android SDK installed on my Windows 8.1 machine, USB debugging enabled on the device, and the device appears when I run "adb devices". When I run "adb reboot bootloader", the device just does a normal reboot. This is my first time doing anything with custom recovery or ROMs, so I'm not sure what the problem is or what to do next. Any suggestions?
Thanks!
mdm_ said:
Hi,
I'm trying to install TWRP on my SM-P900 and I can't get it to boot into fastboot mode. I have the Samsung USB drivers and the latest Android SDK installed on my Windows 8.1 machine, USB debugging enabled on the device, and the device appears when I run "adb devices". When I run "adb reboot bootloader", the device just does a normal reboot. This is my first time doing anything with custom recovery or ROMs, so I'm not sure what the problem is or what to do next. Any suggestions?
Thanks!
Click to expand...
Click to collapse
Try adb reboot download
mdm_ said:
Hi,
I'm trying to install TWRP on my SM-P900 and I can't get it to boot into fastboot mode. I have the Samsung USB drivers and the latest Android SDK installed on my Windows 8.1 machine, USB debugging enabled on the device, and the device appears when I run "adb devices". When I run "adb reboot bootloader", the device just does a normal reboot. This is my first time doing anything with custom recovery or ROMs, so I'm not sure what the problem is or what to do next. Any suggestions?
Thanks!
Click to expand...
Click to collapse
I know its a very old post but were you able to fix the issue ?
Hello. After doing some things in TWRP I got stuck in a boot loop. I wiped all storage so that I could just sideload a ROM, but I can't sideload because ADB is not working properly. I've installed Android SDK and the drivers for my phone, however no ADB commands would work. I decided to attempt to update the drivers but going into device manager shows that there is no Android ADB Interface like usual. Help please?
ItsGflow said:
Hello. After doing some things in TWRP I got stuck in a boot loop. I wiped all storage so that I could just sideload a ROM, but I can't sideload because ADB is not working properly. I've installed Android SDK and the drivers for my phone, however no ADB commands would work. I decided to attempt to update the drivers but going into device manager shows that there is no Android ADB Interface like usual. Help please?
Click to expand...
Click to collapse
Put the phone in download mode and re-flash the firmware using LG-Flash tool. I've been there and the driver resolution issue on anything above Windows7 didnt work. Even the Adb Sideload.
When I try to install the USB Drivers It fails with an error message.
ADB devices works, but fastboot devices doesnt.
I'm on Windows 10.
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
redpoint73 said:
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
Click to expand...
Click to collapse
Yes, I'm trying fastboot from the bootloader screen.
On windows 8.1 it works, I can install the needed drivers, on windows 10 I cannot. Doesn't work. I wonder why adb works but fastboot doesn't.
I had this exact issue up until today, and this what I did to get fastboot on my shield tablet:
1. Uninstall all adb usb drivers just to make sure you start from a clean slate.
2. Then go to Nvidia (https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB) and download their Nvidia shield tablet drivers.
3. While plugged into the computer (have the tablet set to transfer files or mtp) go to the Bootloader menu on your shield tablet and then on your computer go to device manager and update the drivers. For me the device showed up as Fastboot, right click and select update drivers from the folder that you unzipped your nvidia shield tablet drivers to. When I did this I actually got an 'This device cannot start. (Code 10)' error message but I think this is okay because when I looked at the device manager again a new listing had appeared near the top called Android Composite Device.
4. Now go through the exact same process to install the drivers that you did for the 'fastboot' device but now for the 'Android Composite Device', you should also still get the 'This device cannot start. (Code 10)'. After you've done all that reboot the Shield Tablet.
5. Once the tablet has rebooted go to command prompt with Administrator Privledges and type ADB devices and your device should show up, then type adb reboot bootloader and the tablet will reboot into the bootloader menu. I this point I did not select fastboot protocol and I'm not sure if this made a difference, but in any case in the command prompt type Fastboot devices and at least for me this finally worked.
I hope this helps.
Thank you Captain_FSU! :good:
I had the same problem. My Shield K1 was showing up on adb devices but not at fastboot devices. I was unable to update the driver. In Win 10 Device Manager my Shield was showing up at Portable Devices and it was impossible to install the driver there. So finally I am able to unlock bootloader and install TWRP.
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
J0hncramer said:
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
Click to expand...
Click to collapse
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
LokifiedMee said:
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
Click to expand...
Click to collapse
I just tried fastboot devices in powershell while the phone is connected via USB in fastboot mode and nothing was listed
Edit: i was able to get fastboot to work, I had to do the following steps i found on stack exchange to get my device to show up properly in device manager:
https://stackoverflow.com/questions/8588595/android-fastboot-devices-not-returning-device
Open device manager
Find Unknown "Android" device (likely listed under Other devices with an exclamation mark)
Update driver
Browse my computer for driver software
Let me pick from a list of devices, select List All Devices
Under "Android device" or "Google Inc", you will find "Android Bootloader Interface"
Choose "Android Bootloader Interface"
Click "yes" when it says that driver might not be compatible
Click to expand...
Click to collapse
With fastboot working and issues in device manager solved I was able to get TWRP loaded to my phone via fastboot and change my boot slot to get back into the phone