Hi all,
I've a nexus s updated to 2.3.4 and need to root the device.
I've installed the SDK on my windows 7, and hopefully installed the drivers correctly
1- for android 1.0 driver, which one should I choose: (ADB interface, bootog interface, composite interface) ?
2-trying loading the 3 choices, when I try to run the adb devices command it returns nothing, so what could be the problem?
Hope to help me out as I've trying solving this for a long time
Search the forums for the PDA.net app the driver package there works well for windows 7.
Sent from my Nexus S 4G using XDA Premium App
Thanks
I've just discovered that fastboot command is working fine.
I did fastboot devices and got the serial. adb command is not working.
I think I can go with rooting now.
how to get the lates version of clockworkMod for 2.3.4?
heshamsalah said:
Thanks
I've just discovered that fastboot command is working fine.
I did fastboot devices and got the serial. adb command is not working.
I think I can go with rooting now.
how to get the lates version of clockworkMod for 2.3.4?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1039584
Download it from the first post here. Make sure you extract the .img file from the .zip file. (don't try to flash the zip )
Related
Hey,
i just wanted to flash the newest clockworkmod but my fastboot.exe does nothing.
Phone is in fastbootmode, please help
Windows 7 x64...but it worked the other day
Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!
Fmbl said:
Fastboot flash recovery "recovery".img where "recovery" stands for the numbers of the recovery in tools folder i believe.
Also if you run 2.3.4, recovery wil not stick after reboot unless you change something ( i believe the recovery.sh file), hope this helps!
Click to expand...
Click to collapse
i can flash the recovery fia ROMManager, and also can boot into it, but when i boot the phone into bootloader/fastboot mode i can't flash a new recovery, because when i hit enter after "fastboot" i get no output in cmd
If you don't get anything back on fastboot devices, then you either don't have the proper drivers installed, don't have the phone in fastboot mode, or don't have the phone connected via USB. Probably the first one.
Easiest way to get the fastboot drivers is to simply install PDA Net on your computer and follow the on screen prompts. It will automatically install the appropriate drivers for your device.
Sent from my Nexus S using XDA App
thanks, i will try when i am at home again
Sent from my Nexus S using XDA App
Check in device manager that the ADB Bootloader driver is installed.
zero383 said:
Check in device manager that the ADB Bootloader driver is installed.
Click to expand...
Click to collapse
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions
eiabea said:
adb works fine, i use the phone for debugging
i tried the PDAnet methode and reinstalled the driver --> no success
any other suggestions
Click to expand...
Click to collapse
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App
matt2053 said:
That method works. I suggest do it again and follow the instructions more carefully.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
did it very carefully, but no success
Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.
ericshmerick said:
Did you ever figure this out? I have installed PDA net, drivers, etc, and fastboot simply will not connect to my phone. Win7x64.
Click to expand...
Click to collapse
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)
zero383 said:
Need more info.
Did you install the "ADB Bootloader Interface" driver?
Did you boot the the phone into the bootloader before trying the fastboot command? (ie. UP + PWR)
Click to expand...
Click to collapse
Yes and yes.
May want to continue here:
http://forum.xda-developers.com/showthread.php?t=1303522
Had the same issues, although drivers were installed. After including "C:\android-sdk-windows\tools"
and "C:\android-sdk-windows\platform-tools"
in the path of win7 (systemvariables)
and a restart adb and fastboot worked.
Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?
haltemien said:
Hey Guys,
Ive been using stock nexus s for a long time now, and decided to try out the new ICS room. Since i got a new PC, i had to install SDK, drivers etc. But no matter what I do, I get the unkown command when i run fastboot oem unlock. Ive done this before, and all the drivers and sdk shall be correctly installed. Ive tried reinstalling etc, but nothing seem to help.
Do anyone know what could be wrong?
I'm on skype ATM, so if anyone is gentle enough to try an errorsearch with me, call me on my username snorre.andre.nergaard
Click to expand...
Click to collapse
When I reinstalled my SDK i hadnt noticed that ./adb had been moved to a different directory, and the SDK no longer comes with ./fastboot. If you do a quick google search, or a search on XDA, there are forums out there with links and uploaded copies. Actually I'll just put mine up here in a .zip archive. I moved ./adb and ./fastboot back in to my tools folder since it's what I'm used to.
Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.
haltemien said:
Aha. That might be the case. I took the fastboot, from your zip and copy pasted it into the ./tools folder. Aldo grabbed the adb from platform-tools folder.
Still cant get it to work. Only ADB works so far. If i remember correctly i'm supposed to write "adb devices" and it will show the phone. This doesnt happend. I got android adb interface in device manager, and the drives should be ok.
Click to expand...
Click to collapse
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.
krohnjw said:
So, ADB and fastboot operate under 2 different conditions.
Phone in boot loader:
fastboot devices should show a device
adb devices shows nothing
Phone booted normally or in recovery
fastboot devices shows nothing
adb devices shows a device
Fastboot won't do anything if the device is not in the boot loader. If you are in the boot loader the fastboot devices does not show your device then it's a driver issue.
If you get unknown command then fastboot then you aren't in the same cwd as fastboot or it's not in a folder listed in the PATH.
Click to expand...
Click to collapse
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands
The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
The camand should be "adb oem unlock bootloader "
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It's fastboot oem unlock
Sent from my Nexus S using xda premium
krohnjw said:
It's fastboot oem unlock
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium
Esteway.619 said:
I meant to put adb-fastboot oem unlock but I forgot that's for me on my Mac I forget most people have windows. My bad
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
It doesn't use ADB at all. That may be what you have your local binary named, but it's fastboot. You need to be in the bootloader (where adb cannot work).
Fastboot is the utility used for unlocking the bootloader, flashing/erasing partitions, booting images (such as a kernel or recovery) without installing to the device.
ADB is the Android Debug Bridge.
This is just for clarity here, there's seemingly a lot of confusion.
Thanks for the clarification bud
Sent from my Nexus S 4G using xda premium
kdepro said:
Great point. I had completely forgotten about that. Since your adb is working, run <code>./adb reboot bootloader</code>. Once your phone boots up and you see the funky android dude, you can use fastboot commands
Click to expand...
Click to collapse
Yeah. I was in bootloader mode. So then i guess the fastboot "path". that could be the problem then. Ill check it out when i get back from work. Thanks
Hey guys I have given up. Been looking at this for two days now and it will not work. Heres the problem.
I have ran X-factor unlock as per instructions and it ran successfully all the way to the point where it asked did I want to see the identifier token. I hit yes and then the it froze. Let it sit there for like 5 minutes and nothing. So I closed X-factor and open cmd and booted the phone into fastboot. Then I plugged my phone into my computer and ran the fastboot command "fastboot oem get_identifier_token" and I does nothing. I also tried running "fastboot devices" and still notthing. I have reinstalled htc sync manager, pdanet for the drivers, have tried all different version of fastboot and adb and nothing is working. What could I possibly be doing wrong? Pdanet recognizes that the phone is plugged into the pc and the phone recognizes it too but fastboot doesn't. Any help is appreciated.
Are you running the fastboot command from the folder where you extracted it ? And did you download the latest file of X-factor unlock ( First one had few bugs)
Extract the zip file which you downloaded and now open Command Prompt, change the directory to the folder where you extracted the fastboot zip.
Example ( if you extracted in Downloads Folder then) cd C:\Users\username\Downloads\fastboot-win32
then execute the command again " fastboot oem get_identifier_token"
Sent from my HTC One XL using xda premium
abhipati said:
Are you running the fastboot command from the folder where you extracted it ? And did you download the latest file of X-factor unlock ( First one had few bugs)
Extract the zip file which you downloaded and now open Command Prompt, change the directory to the folder where you extracted the fastboot zip.
Example ( if you extracted in Downloads Folder then) cd C:\Users\username\Downloads\fastboot-win32
then execute the command again " fastboot oem get_identifier_token"
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I downloaded X-factor last night around 12a.m. And when I run the cmd I first hold down shift and then right click in my the folder android sdk/ platform tools. Adb, and fastboot along with several other files are in this folder. when running the command nothing happens. Cmd just adds another line.
ImagioX1 said:
I downloaded X-factor last night around 12a.m. And when I run the cmd I first hold down shift and then right click in my the folder android sdk/ platform tools. Adb, and fastboot along with several other files are in this folder. when running the command nothing happens. Cmd just adds another line.
Click to expand...
Click to collapse
Did you install HTC sync
First things first, do you get anything when you do adb devices?
APSBiker said:
First things first, do you get anything when you do adb devices?
Click to expand...
Click to collapse
Yaa, when u plug in your device type "adb devices" in command prompt (from android platform tools folder) did u get any response "[serialNumber] [state]"??
Sent from my HTC One XL using xda premium
abhipati said:
Did you install HTC sync
Click to expand...
Click to collapse
I said in my firt post that I did.
I have tried adb devices and for some reason it works some times and other times I get nothing. I suppose X-Factor is using adb though and the adb part( the two backups and the reboot into fastboot) of X-Factors works all the time. Its only when the phone reboots into fastboot that the rest of the commands don't work with X-factor. Only once did it work and it said it was successfull- i go the 111111111 for my CID. But when I hit enter to view the token X-Factor did nothing.
I have another idea that might work. I was wonder what you guys thought. I have vmware running Mac Os and I was wondering if I could download the Mac tools to my vm and try running the commands that way. Since Mac doesn't doesn't need drivers do you think that would work?
I still haven't figure the problem out. So I just booted up Mac OS in vmware and used the mac fastboot and it work. Yay! unlocked bootloader! Now to flash super user.
ImagioX1 said:
I still haven't figure the problem out. So I just booted up Mac OS in vmware and used the mac fastboot and it work. Yay! unlocked bootloader! Now to flash super user.
Click to expand...
Click to collapse
Awesome! Thanks for updating us on how you got it to work. I guess I was one of the lucky ones that it worked the first time for.
That was a tough fix. Windows still will not recognize my device in adb or fastboot. I don't know what the problem is. But the only catch to running Mac Os in vmware is it is against the EULA so I am not telling you to try that. But It will work. I have been looking at this for 2 days now and I had to go install Mac Os in vmware and register with apple and all that good stuff before I could even start running commands. It was tough but I hope its worth it.
USB debugging
I have a Desire without OS, it can boot into fastboot. Is there any way to know if USB debugging was switched on from here? I tried to unlock the bootloader, im on S-ON, but keep getting errors:
C:\Users\Alienanihilator\Desktop\Roms\HTC Roms\HTC One X\HTC_fastboot_files>fast
boot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Maybe has to do with USB debugging not being turned on before?
You're in the wrong forum, this is the One XL forum. You need to ask in the Desire forum.
Sent from my Evita
I've installed a ROM and need to flash boot.img but in "cmd" ı cannot do this. I'm using Windows 8 and I got "waiting for device" error. I ran cmd as administrator and wrote "fastboot -i 0xfce flash boot boot.img" but they did not work too. How can I flash the boot.img ? Thanks for your helps.
Anyone know that ?
welocan said:
Anyone know that ?
Click to expand...
Click to collapse
Windows 8 has issues with HTC Drivers. For example I have 2 Windows 8 machines - one with clean install, the other - an upgrade from Windows 7.
The upgraded one, which has perfectly working drivers on Win7 now connects the device fine. But I spent hours on the other one (clean install) trying different drivers without sucess. It just refuses to detect the device.
So you can install older version of Windows or Ubuntu as dual-boot alongside your Win8 or use another computer.
And do not add the "-i 0xfce" to the command, it is not necessary. fastboot flash boot boot.img will do fine
Hi there,
I am rooted but wanted to install SuperCID so that I could s-off. It has been awhile since I have rooted and installed TWRP recovery but now after trying to install SuperCID I seem to have trouble executing fastboot commands, in bootloader I see 'Fastboot USB" after connecting to my primary USB ports (heck, I tried all 4 from my motherboard) but the commands do not seem to sync with my device (other commands seem to work such as me checking my CID [currently Rogers001]) so I do not know what happened...
Sorry for the potential lack of xda-vocabulary... I don't do this often.
TIA
an_xda said:
Hi there,
I am rooted but wanted to install SuperCID so that I could s-off. It has been awhile since I have rooted and installed TWRP recovery but now after trying to install SuperCID I seem to have trouble executing fastboot commands, in bootloader I see 'Fastboot USB" after connecting to my primary USB ports (heck, I tried all 4 from my motherboard) but the commands do not seem to sync with my device (other commands seem to work such as me checking my CID [currently Rogers001]) so I do not know what happened...
Sorry for the potential lack of xda-vocabulary... I don't do this often.
TIA
Click to expand...
Click to collapse
Your computer need htcsync and ADB installed to run fastboot
Did you download and install both of this software to ur computer?
And you need to lead to the folder where you store fastboot and adb, running CMD in this folder.
You are using Roger HTC 1x as same as me, so i can help you a lot hahaha
thinhletien said:
Your computer need htcsync and ADB installed to run fastboot
Did you download and install both of this software to ur computer?
And you need to lead to the folder where you store fastboot and adb, running CMD in this folder.
You are using Roger HTC 1x as same as me, so i can help you a lot hahaha
Click to expand...
Click to collapse
Yes, I have the drivers (ADB/Fastboot) in a folder on C:\ and have pointed to that folder in cmd prompt (I should mention I have successfully leveraged the commands in the past).
However, I do not have HTC Sync installed so let me give that a shot...
Edit - after installing HTC Sync and connecting the phone (after unlocking the PIN, of course) - it could not connect to my device. Any advice/suggestions? This is probably going to tie into the same reason why I cannot connect via fastboot to my device.
Side note is that I am running CleanROM 6.5 if it makes any difference (stock kernel or whatever the roms come with).
Do you have debugging enabled on your phone?
Sent from my HTC One XL using xda premium
Venomtester said:
Do you have debugging enabled on your phone?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yes, USB debugging is enabled in developer options.
Still having no luck.