hi,
i just got my new N1 and after i played with it a little i tried to root it but every time i tried to unlock it my computer wouldn't recognize the phone.
(i running xp) I installed the drivers manually (after downloading them from theunlocker.com site) and nothing.
when i connect the phone to the computer (not in fastboot mode) every thing works (even tried to run "adb devices") but when i try to unlock it from the fastboot mode it's not being recognized. please help.
deleted...........
not in fastboot\bootloader
Stickies much?
http://forum.xda-developers.com/showthread.php?t=613217
I'd say with about 90% certainty, that you simply don't have the CORRECT driver... Seeing as I had the same issue
Thanks, i will try it and let you know
Start>Run>"cmd" then "adb devices"
If you don't see your phone's serial number then you don't have the right drivers. There's a sticky in the Q&A forum on how to get it working.
You say it works when the phone isn't in fastboot mode. Well, actually all your pc is detecting is a usb mass storage device. That's your sd card, not your Nexus One.
thank you!!
sorry for not checking the Stickies in the Q&A forum.
i updated the drivers and rooted my nexus and flashed RAs recovery (the 1.7.0)
Related
First let me get the stats out of the way in case it's a compatibility issue (doubtful):
Mytouch 3g 32b
Hboot 1.33.2005
Radio 2.22.23.02
Running on the last cm6 nightly (307, i believe)
Using this kernel: http://droidbasement.com/db-blog/?p=1531
All flashed through recovery.
Ok, so the problem..
Following this guide, http://forum.xda-developers.com/showthread.php?t=532719, I successfully got the ADB to work properly (calling "adb devices" on a terminal returns my device). However when I boot the phone into fastboot, connect it to the PC via USB and call "fastboot devices" through the terminal (yes, I first cd to the android-sdk/tools folder), it returns nothing. Calling something like "fastboot reboot" simply returns "<waiting on device>" indefinitely.
I googled for HOURS last night searching for a solution but to no avail. I uninstalled the drivers via the Device Manager and tried the PDANet method, but nope. Uninstalled drivers again, rebooted everything, and reinstalled using the method posted in the above guide again, pointing it to the google/usb_drivers folder, just in case I had f*'d up somewhere along the way. I just ended up with the same problem. ADB works. Fastboot doesn't. What am I doing wrong? :/
Basically, I'm stumped. While it's not completely necessary to get this working, I'd like to free up some ram on my phone (http://forum.xda-developers.com/showthread.php?t=831139) and for this I need fastboot. I'm not that noobish so I'm willing to experiment. Any help is appreciated.
Nobody? :/
Thanks to my persistence I finally got it working. I'll share in case anyone else has the same problem.
Apparently there were still old HTC related devices under the Device Manager that would not show even when I clicked on "Show hidden devices." I fixed this by adding a new system variable.
Variable name: devmgr_show_nonpresent_devices
Variable value: 1
This allowed me to see a bunch of HTC labeled grayed out devices under 'Disk drives' and under 'Universal Serial Bus controllers,' some grayed out USB Mass Storage Devices and one USB Composite device which I believe was also a culprit. Uninstalled all of them.
I then restarted the process of setting up ADB using these drivers, mediafire.com/?wzdjcmowziw, which I got from the guide I link to in the first post. Then when I hooked up the phone to the PC under fastboot mode, I used the drivers supplied by PDANet. Worked immediately.
Thanks for all the help. (sarcasm)
Hello there!
So I accidentally bricked my phone a few days ago and now it is resting as a brick on my desk, but how did all of this happen, you may ask?
Well, the story is rather simple, I had the Simple ROM V. 1.4 installed on my G2 and decided to update it to version 2.0, which is posted here somewhere, but what I didn't notice was that the file I was downloading (even though it said it was compatible with all versions) was not for the D800 but for the LS980 and this bricked the phone.
First I was stuck on fastboot mode and was able to get my download mode back, but it kept saying that it couldn't flash the stock rom because it was the wrong model.
Looking online and through these forums, I found out that it was because the download mode that it had was not the right one to use, and that I needed to "destroy" download mode, enter once again in fastboot mode and flash the new download mode, this, however, turned out out to be impossible as the fastboot mode is no longer being detected by Windows nor Linux.
I installed back the USB drivers, installed Android ADB, changed the UDEV rules with mew vendors ID from the list provided by Google, updated the drivers on my PC and even tried to change the directory in which the phone would appear.
The problem resumes to this:
When in fastboot mode (connected to the PC) and type
Code:
fastboot devices
in both Windows and Linux, I get the response as
Code:
???????? devices
.
When I try with
Code:
adb devices
I get back nothing.
Curious thing is that the phone does appear on Device Manager as an Android ADB device and when on Linux I use the
Code:
lsusb
I get back that it is being recognized as
Code:
Google Inc. 18d1 d00d
, which I believe is the phone.
When trying to run any fastboot commands, the phone stays on "waiting for device" on Linux or "flashing" on Windows and later a messages pops back at me with
Code:
Error too many links
.
With all this in mind, I would like to ask you guys, is there something that I am missing?
Any help will be truly appreciated!
PS. Forgot to mention that I have tried with other computers and have the same result and the model of my phone is the D800.
Just to add a bit more into the case.
I had installed prior to all this mess, TWRP which had a Nandroid backup in the internal storage and file backup.
When using the LG Flash tool (KDZ one) I am able to see the available storage, which is about 2.5gb. This leads me to believe that both the Nandroid backup and Backup files are still in the internal storage.
Also, I did some more digging and got information that it might be the USB cable, however, this cable worked fine the first time and with other devices. and while connecting the phone with it to the PC it will still register the device as connected, but apparently no USB port is assigned or fastboot flash tool does not find the phone.
i know that it's a bit silly to create an entire thread for one guy's problem, but i am stuck and probably going to give up hope when it comes to rooting my s5 neo (again, g903f), which is running android 5.1.1.
several days worth of research have yielded nothing. i can connect to my device using mtp, and i have usb 2 and 3 ports. lsusb and adb are working for me; i have set udev rules and "adb devices" returns my phone's serial number and its status. usb debugging is enabled as is the oem unlock (though whenever i try to disable developer tools and put them on again, the gui messes itself up and it won't let me turn them off, even if i refuse to put in my device's password). that's the only success i've had.
fastboot isn't working; "fastboot devices" shows nothing and it hangs at "< waiting for device>" with other commands, such as "fastboot oem unlock". adb won't work in download mode, either - though this is expected. rebooting into download mode via adb doesn't fix my problem, nor does using "sudo" or the root account.
odin3 won't work either despite the window opening with wine; the device never shows up in download mode. heimdall also doesn't seem to detect my device - although it might just be down to my ignorance.
the usual root tools, such as srsroot and kingo don't seem to do any good, though neither worked under wine, which helps to diagnose the problem. i have no access to windows, even through vmware.
i feel like everything i do only brings me one step closer to a brick wall, which i'm hitting all the time. it's like i've been chosen to experience this. if any of you guys can help me to get this phone rooted, i'd probably scream out of sheer ecstasy. and no, "try getting a girlfriend" who has windows isn't an answer.
[insert wojak here]
Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?
Reyse said:
Hi!
It seems a driver issue
have you used already this tool in your pc successfully or is just a problem with your S5?
Click to expand...
Click to collapse
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.
thefailure said:
i don't think that drivers are an issue; i have linux. do i need to use kies to install them under wine? it didn't work with wine 1.8 and kies3; i'm trying wine 1.9 right now.
Click to expand...
Click to collapse
Did you debug (adb, fastboot) another phone already or is this your first one?
as i've posted on another forum here:
i know that it's a bit silly to create an entire thread for one guy's problem, but i am stuck and probably going to give up hope when it comes to rooting my s5 neo (again, g903f), which is running android 5.1.1.
several days worth of research have yielded nothing. i can connect to my device using mtp, and i have usb 2 and 3 ports. lsusb and adb are working for me; i have set udev rules and "adb devices" returns my phone's serial number and its status. usb debugging is enabled as is the oem unlock (though whenever i try to disable developer tools and put them on again, the gui messes itself up and it won't let me turn them off, even if i refuse to put in my device's password). that's the only success i've had.
fastboot isn't working; "fastboot devices" shows nothing and it hangs at "< waiting for device>" with other commands, such as "fastboot oem unlock". adb won't work in download mode, either - though this is expected. rebooting into download mode via adb doesn't fix my problem, nor does using "sudo" or the root account.
odin3 won't work either despite the window opening with wine; the device never shows up in download mode. heimdall also doesn't seem to detect my device - although it might just be down to my ignorance.
the usual root tools, such as srsroot and kingo don't seem to do any good, though neither worked under wine, which helps to diagnose the problem. i have no access to windows, even through vmware.
i feel like everything i do only brings me one step closer to a brick wall, which i'm hitting all the time. it's like i've been chosen to experience this. if any of you guys can help me to get this phone rooted, i'd probably scream out of sheer ecstasy. and no, "try getting a girlfriend" who has windows isn't an answer.
[insert wojak here]
Click to expand...
Click to collapse
new things: i know that usb support in wine is nonexistent, thus i need to know how to get wine to see my device if i need to use odin (with kies for the drivers). adb works only intermittently; it sometimes doesn't see my device. i'm not sure if i can use mac osx in a vm, either.
can i get samsung drivers for linux at all? or am i hopelessly screwed? all i wanna do is root, get twrp, get xposed and then work from there.
Hi!
I answered your previous thread, but now I understand your problem
I see you are trying with vmware
would you use virtualbox?
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Did you follow funkwizard's guide in the guides/news/discussion forum? It's stickied at the top.
Anyhow, if you followed the guide, he provides this link (https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view?usp=drivesdk) for the OP6T drivers that need it be installed.
He then provides this link (https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view?usp=drivesdk) to update your ADB/fastboot to the latest version.
Complete both of those steps and your phone SHOULD be recognized in fastboot. Good luck.
I have read his complete thread and im still stuck with the same problem. I deinstalled all phone related driver and only installed the one from the thread, opened the command prompt via admin and under device manager is still the yellow triangle beside the android device. I tried to install the driver manually via the google universal driver, but windows never found any compatible drivers.
And just to be certain, do you have USB Debugging enabled in developer options?
Pain-N-Panic said:
And just to be certain, do you have USB Debugging enabled in developer options?
Click to expand...
Click to collapse
Yupp, but i have to say that i had to tap it four to five times until the confirmation window popped up.
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Bartuc666 said:
I had this problem few hours ago, and this is W10 fault. For me solution was that:
instal drivers from guide,
enter fastboot mode,
remove phone from device manager and unistal drivers,
replug phone,
let windows find drivers automaticly when in fastboot mode.
And that's it, fasboot comands works now.
Click to expand...
Click to collapse
Thanks for the try, but still no change.
lubal21 said:
Thanks for the try, but still no change.
Click to expand...
Click to collapse
forget all the other tips, install the Google USB drivers with the batch file by entering Y on every question. select install driver in the device manager by selecting manually install. in the list presented select on the left Google Inc and on the right the fastboot driver. finish setup and fastboot should work now
lubal21 said:
Hello, a few weeks ago i got my OP 6t. Due to my positive experience from my previous phones (LG G3 and G5) and what i heard from OP i tried to flash twrp and planned to install magisk. I followed the instructions here on xda to unlock the bootloader, it got recognized as device in adb and i could reboot it into the bootloader, but then it didnt recognized it in fastboot, it looks like im missing some sort of drivers, because when im in fastboot in the win 10 device manager its called "android" with a yellow triangle, i tried multiple guides already, but i had no success. Its the unbranded version with 8 gigs and 128 gig. I can provide more info if needed. Help would be very appreciated.
Click to expand...
Click to collapse
Probably this shall help:
How to Fix OnePlus Device not showing in Fastboot Mode
In this detailed guide, we will show you the steps to fix the OnePlus Device not showing in the Fastboot Mode on Windows 10 PC.
www.droidwin.com