Database Develop

[Q] Help! One stuck without Rom and wiped SD

Hey guys,
I'm having a lot of trouble with my AT&t HTC One. I was trying to update it to android revolution v62 and by accident i wipe my entire internal sd card and I have no rom on the phone to boot into right now. I know you can sideload a rom or put a rom on your sd card via this guide http://forum.xda-developers.com/show....php?t=2318497. But the problem is I can not get my computer to recognize my phone. I have the android sdk installed with all the updates. I have the HTC drivers installed as well. I just need my computer to recognize my phone. It only shows up in device manager when i put it into fastboot mode. I tried to do the RUU but it couldn't recognize the phone. Also when I try to do adb devices, it also shows that no devices are connected I think it's a driver issue. Also I'm on windows 7 64 bit. Thanks so much!
Also my phone is
S-off
unlocked

slayaman22232 said:
Hey guys,
I'm having a lot of trouble with my AT&t HTC One. I was trying to update it to android revolution v62 and by accident i wipe my entire internal sd card and I have no rom on the phone to boot into right now. I know you can sideload a rom or put a rom on your sd card via this guide http://forum.xda-developers.com/show....php?t=2318497. But the problem is I can not get my computer to recognize my phone. I have the android sdk installed with all the updates. I have the HTC drivers installed as well. I just need my computer to recognize my phone. It only shows up in device manager when i put it into fastboot mode. I tried to do the RUU but it couldn't recognize the phone. Also when I try to do adb devices, it also shows that no devices are connected I think it's a driver issue. Also I'm on windows 7 64 bit. Thanks so much!
Also my phone is
S-off
unlocked
Click to expand...
Click to collapse
Try this guide for your drivers issues:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse

[How-To] Install Windows 8 Drivers to Establish ADB with NookColor

Hello mods, surely haven't done one of these before but there seems to be a big hole in our knowledgebase here and I thought I'd take a stab at filling it. If I somehow overlooked another solution for this, feel free to take this down and also smack me because I turned the web upside down trying to find the answer before putting it together.
All that being said....I've now done this on two Windows 8 machines so I feel confident that it works. All of the following was done on a fresh install of the Android SDK by installing Android Studio with all default options. Get Android Studio here. You'll need to install Java first if you haven't already, you can grab Java SE Development Kit 7u75 here.
1) The first step is to disable driver signature enforcement on Windows 8, which is the cause of all this devilry that makes it seemingly impossible to install the drivers and get ADB working with the NookColor. Follow the instructions on this link: Disabling Signed Driver Enforcement on Windows 8
2) Download and extract the attached adb_usb.zip file. Take the adb_usb.ini file inside and drop it in your.android directory. If my Windows username is cabbieBot, then I find it here: C:\Users\cabbieBot\.android
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Alternatively, you can just make this file yourself by opening up notepad, typing 0x2080 into it, clicking save, change dropdown from .txt to All Files, and save it as adb_usb.ini
3) Open Device Manager and plug in your NC. You will see NookColor under "Other Devices" with a yellow exclamation mark.
4) Download/extract the attached NookColorADBInstall.zip file.
5) Open Device Manager in Windows 8 You will see "NookColor" under "Other Devices" with the exclamation mark. Right-click on it and click "Update Driver". From here on out its all about just going through the right process of menus and dialogs.
6) Click whats in the red box: "Let me pick from a list of device drivers on my computer".
7) Just leave it on "Show All Devices" and click Next.
8) IMPORTANT STEP! Click "Have Disk"
9) Click "Browse"
10) Navigate to where you extracted the NookColorADBInstall zip and you'll select the "usbdrivers" folder inside.
11) Without restarting Windows with the driver signature check we'd hit a dead-end here but we good. Click "Next".
12) Tell the dialog to eff off and click "Yes"
13) Click "Install this driver software anyway".
14) DING DING DING! If you have your NC hooked in, you should now see it prompting you to accept the computer's RSA certificate which means your computer and nook are gloriously flirting, so lets check it out to be sure.
15) Navigate to where ADB lives, which on a default installation will be at C:\Users\cabbieBot\AppData\Local\Android\sdk\platform-tools. Hold SHIFT and RIGHT-CLICK in the folder to select "Open Command Window Here"
type:
adb kill-server
then....
adb start-server
then...
adb devices
When you see your device's serial number pop up, you are certifiably done. I decided I wanted to learn to build CM from source and the trusty old NookColor is a handy device to play on. If you are worried about the driver signature check being disabled, just reboot your computer because it doesn't survive a reboot. Hope this is useful to someone else even though dear old Encore is downright ancient at this point.

Deleted /system And All Data | ADB Doesn't Recognize Phone | Recovery Still Works

Deleted /system and all data | ADB doesn't recognize phone | Recovery still works
Hey guys,
today I wanted to wipe my HTC One - pretty standard, just a factory reset. But I accidentally wiped /system too - now I don't have an OS. ADB doesn't want to detect my phone under any circumstances - neither ADB Sideload, nor in fastboot mode, nor does the computer even detect the phone as a phone, it just says "Unknown Device".
Bootloader: Tampered, Unlocked.
S-ON
HBOOT 1.57.0000
TWRP 2.8.5.0
Hope someone can help. If additional info is needed, I'll provide you with that.
Morphior

Morphior said:
ADB doesn't want to detect my phone under any circumstances - neither ADB Sideload, nor in fastboot mode, nor does the computer even detect the phone as a phone, it just says "Unknown Device".
Click to expand...
Click to collapse
FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

What is that supposed to tell me? The drivers didn't correctly install - okay. But what is that fastboot command? I never typed that before.
Also, I tried to update drivers, I even manually installed drivers - without success.
Morphior

Morphior said:
What is that supposed to tell me? The drivers didn't correctly install - okay. But what is that fastboot command? I never typed that before.
Also, I tried to update drivers, I even manually installed drivers - without success.
Morphior
Click to expand...
Click to collapse
not the drivers or fastboot commands, just the "manual selection" of "My HTC"
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
[/HIDE]-------------------------------------------------------------------------------------------------------------------------------------------[/HIDE]

There is no "My HTC" in the list of drivers.

Morphior said:
There is no "My HTC" in the list of drivers.
Click to expand...
Click to collapse
how about using MTP in twrp

I tried that.

Morphior said:
I tried that.
Click to expand...
Click to collapse
"I tried that", but.... ?
how about a screenshot of your Windows Device Manager, while the phone is connected.
also, while the phone is connected, please try toggling MTP (ie on->off->on)

Okay. So now I think I absolutely jammed everything up. I connected a USB flash drive via my OTG cable and it worked. Awesome. I put an OS on it and installed it. Went through. But then when I wanted to reboot it said "no OS". I rebooted and now even OTG doesn't work anymore. What can I do? I tried remounting it but doesn't let me.
Morphior

Morphior said:
Okay. So now I think I absolutely jammed everything up. I connected a USB flash drive via my OTG cable and it worked. Awesome. I put an OS on it and installed it. Went through. But then when I wanted to reboot it said "no OS". I rebooted and now even OTG doesn't work anymore. What can I do? I tried remounting it but doesn't let me.
Morphior
Click to expand...
Click to collapse
have you tried unplugging it, rebooting to recovery and replugging it as mentioned here http://forum.xda-developers.com/showpost.php?p=61449330&postcount=23
not sure if the regular twrp has that issue too, but you might as well try.
and btw, obviously the rom didnt flash properly because it gave you the message "no OS"

BL unlock win10 pro

Hi there,
I have a E6335, isn't there released adb drivers for windows 10 pro x64?
I've used the "Minimal ADB and Fastboot" pack from here, and i can get it to reboot through ADB, but after that it isn't recognized, so i have to perform a hard reboot throug the button beside the sim.
Im not that familiar with adb and fastboot, so if anyone could guide me, i'll be very thankful.
Kind regards.

driver signed in Windows 10
Try this:
http://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
... and tell us if it works (should with the proper drivers from SONY's developer site).

Hi there,
It dosn't work.
Genuine drivers was installed, but i did a reinstall, same problem, the S1 Fastboot driver is not installed.
Drivers works fine, until i perform the "adb reboot bootloader" command in adb, after that, the fastboot driver is unknown in device manager.
I've tried to perform the unlock command afterwards, but it keeps hanging on the "waiting for device".
Performing the "fastboot devices" dosn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess i have to go on a win7 machine then?
Thanks.

I guess i have to go on a win7 machine then?
Click to expand...
Click to collapse
I recommend Debian Jessie
Read Androplus's advice. http://forum.xda-developers.com/showpost.php?p=62577784&postcount=2
I see the wrong command in your screenshot.
You know how to get into fastboot mode?
Power off the device. Hold "Volume up" (until the LED turns blue) and plug in USB cable.
I do not know, what you are up to with unlocking the bootloader but if these first steps go so badly you better stop here before attempting to root the device or doing something else. You could end up with a brick.

reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.

I'm not a newb in droid phones, just the adb. And i've just used the commands from this thread: http://forum.xda-developers.com/xperia-z4/general/bootloader-unlock-tip-t3165018
And if thats wrong, i think that it should be corrected.
And same issue as the before mentioned, when i use the vol up option.
@monx
I'll try that right away. I've just updated all 6 machines to win10 from 7, so im not that familiar with it yet

reboot w10 with advanced startup > advanced options > disable driver signature enforcement.
then install S1 driver from flashtools package. this issue has been covered since win8.
Click to expand...
Click to collapse
That did the trick, thank you buddy

How To Guide Fastboot < waiting for any device > Fix & Windows 10 Drivers

Hi everybody,
I recently went through the steps and got my Zenfone 8 Sake device hooked up with LineageOS & Magisk. Everything went exactly according to the steps, except for one big hurdle for me. For me, it was that my PC did not have the proper drivers for the phone. Downloading the drivers from Asus' official website below should fix this. I've outlined the complete steps for anybody else who is having the same issue.
At the point of the LineageOS install when you're going to use Fastboot to flash the recovery, your device should be at the bootloader and plugged into your PC via USB. At that point, your PC should have the proper drivers to handle the device. My PC didn't so it would just show this forever:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you go into the Device Manager, you should also see that Windows 10 is not recognizing your device properly:
Downloading the correct drivers and manually setting them in Windows should fix this problem and allow Fastboot to go ahead with the "flashing" step.
Instructions
Download these official drivers from Asus: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip (Look below to see how I got the link)
Extract ZIP to somewhere
Go into the extracted folder -> Windows_XP_VISTA_7_8_8.1 and take note of that Android folder and its path.
Open "Device Manager", find your device in "Other devices", right click on it and select "Update driver"
Select "Browse my computer for drivers"
Input the path that you noted earlier to the Android folder with the drivers.
Select "Next" and it should install the drivers from the path.
Reconnect your device and everything should be working properly!
Look below to see how it should look if properly working.
Where to Find Drivers Yourself
Search up Zenfone 8 on Google and go to the official page. This one: https://www.asus.com/us/Mobile/Phones/ZenFone/Zenfone-8/
Go to Support then Driver & Tools
Select the OS. As of this posting, the latest OS support is Windows 8.1. Not sure if this is a problem, but it worked just fine for me on Windows 10!
Download the USB driver listed there: "ASUS_Android_USB_drivers_for_Windows"
This is how it should look once you have your drivers setup properly for the device:
Hope this helps some people!!! Happy modding!

thanks... stuck on waiting for any devices also.. lucky for me to see your thread