So recent got my Nexus 5 and have decided to root it, I've been following this guide http://forum.xda-developers.com/showthread.php?t=2507905 however I cannot get past the part where I need to type
Code:
fastboot devices
Simply because my device doesn't show up, nothing does.
My device does show up in adb devices though which seems odd, Yes I'm in fastboot when i use fastboot devices. I have tried all the methods from the guide on trying to fix the drivers but to no avail, any help would be greatly appreciated. Thanks
Try these drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Chromium_ said:
Try these drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Still shows up in ADB but not fastboot
Krashem said:
Still shows up in ADB but not fastboot
Click to expand...
Click to collapse
Watch this guide.
Chromium_ said:
Watch this guide.
Click to expand...
Click to collapse
Still not working, followed the guide exactly. I'm not sure if this helps but when I plug my Nexus in while its in fastboot windows says its an unrecognized device.
Krashem said:
Still not working, followed the guide exactly. I'm not sure if this helps but when I plug my Nexus in while its in fastboot windows says its an unrecognized device.
Click to expand...
Click to collapse
Did you do the thing at the end of the guide (around 3:40)? You need to go into device manager where the phone is unrecognized and select the appropriate drivers.
Chromium_ said:
Did you do the thing at the end of the guide (around 3:40)? You need to go into device manager where the phone is unrecognized and select the appropriate drivers.
Click to expand...
Click to collapse
I think hes using W7 whereas I'm using 8.1, the part with all the drivers come up for him (e.g. Android Phone) doesn't show for me. I would post a picture although I don't think I can yet..
Krashem said:
I think hes using W7 whereas I'm using 8.1, the part with all the drivers come up for him (e.g. Android Phone) doesn't show for me. I would post a picture although I don't think I can yet..
Click to expand...
Click to collapse
With windows 8 this is what you'll need to do to get the drivers installed.
Chromium_ said:
With windows 8 this is what you'll need to do to get the drivers installed.
Click to expand...
Click to collapse
Tried this before also didn't make a lot of difference
Krashem said:
Tried this before also didn't make a lot of difference
Click to expand...
Click to collapse
weird, it must be something wrong.
did you try changing usb port, cable...
any way, simple steps,
uninstall driver,
for window 8.1:
1) From the Window 8.1 Start screen, move your mouse to the top (or bottom) right corner, and click Settings;
2) Click "Change PC Settings";
3) click Update and Recovery;
4) Under Advanced startup, click "Restart Now";
5) Wait for it to restart;
6) Click "Troubleshoot";
7) Click "Advanced options";
8) Click "Startup settings";
9) Click "Restart";
10) Wait for it to restart;
11) Press F7 (i.e, the F7 function key);
Now you can install the driver.
Dont worry I got it to work, thanks for all your help. I missed something while I was uninstalling previous fail attempt drivers..
I now have another issue I have unlocked bootloader and flashed ClockworkMod recovery but I cant push the SuperSU zip. It keeps telling me the device is not found and it is also not showing up in adb devices while I'm in recovery..
Krashem said:
I now have another issue I have unlocked bootloader and flashed ClockworkMod recovery but I cant push the SuperSU zip. It keeps telling me the device is not found and it is also not showing up in adb devices while I'm in recovery..
Click to expand...
Click to collapse
Just boot it up normally and download SuperSU from the phones browser: download.chainfire.eu/supersu
Then go back into recovery and flash it.
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.
I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
EDIT 2: I have finally solved the problem! I have quoted the important parts below in case anyone else has the same problem.
Basically I had some problems with the drivers the whole time on Windows 8. So what I did was disabled driver signature enforcement in Windows 8 (I think it re-enables after some time). I downloaded the drivers from this post and followed this other post , specifically this part:
jpasher said:
Making Windows recognize the TF300T
You will need to add the hardware IDs for the TF300T in the driver to make it recognize the ADB interface
Open the file android_winusb.inf in the naked drivers directory.
Look for the section titled [Google.NTx86] (for 32-bit systems) or [Google.NTamd64] (for 64-bit systems)
Add the following lines to make it recognize the TF300T hardware (it doesn't matter where, but I put it after the existing entries for the TF201 APX interface)
Code:
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&REV_0232&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83&REV_0232
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83
After the information is added, you should be able to install the drivers as usual for the device. If for some reason the device is still not recognized, you'll need to find its hardware IDs and add those to the file.
Click to expand...
Click to collapse
Then I booted up the tablet and connected to my computer. The drivers finally worked! I went into command prompt and typed "adb devices" and the device was there! Then I typed "adb reboot bootloader" and I got into the bootloader.
I had to look for the SKU too and since I couldn't find it cause I couldn't boot into Android it was in really small text in the bootloader at the top. Unfortunately after trying to flash the firmware in the bootloader it would not write over the system every time. So I followed this post instead: http://forum.xda-developers.com/showpost.php?p=49164067&postcount=167
After following the procedure it finally worked! Thanks cmendonc2 and everyone for your help, my friend is happy!
firtvid20 said:
I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
Click to expand...
Click to collapse
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.
cmendonc2 said:
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.
Click to expand...
Click to collapse
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP
firtvid20 said:
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP
Click to expand...
Click to collapse
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.
cmendonc2 said:
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.
Click to expand...
Click to collapse
Okay that's good to know. I am still unfortunately not able to get into fastboot. So I'll have to figure out what version the bootloader is before flash the firmware over.
Okay I got access to APX mode (useless from my understanding since my friends has no backups via nvflash), the bootloader while the recovery is loaded (although the driver isn't working for the bootloader), but I CANNOT GET INTO THE BOOTLOADER VIA VOLUME DOWN + POWER. Please help, somebody!
Here's a video explaining my problem.
firtvid20 said:
Here's a video explaining my problem.
Click to expand...
Click to collapse
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.
cmendonc2 said:
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.
Click to expand...
Click to collapse
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?
firtvid20 said:
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?
Click to expand...
Click to collapse
Its an option somewhere in TWRP called "ADB sideload".
cmendonc2 said:
Its an option somewhere in TWRP called "ADB sideload".
Click to expand...
Click to collapse
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.
firtvid20 said:
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.
Click to expand...
Click to collapse
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.
cmendonc2 said:
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.
Click to expand...
Click to collapse
Sorry, what is test mode? I am on Windows 8.
firtvid20 said:
Sorry, what is test mode? I am on Windows 8.
Click to expand...
Click to collapse
This should help: http://www.wugfresh.com/faq/8/
cmendonc2 said:
This should help: http://www.wugfresh.com/faq/8/
Click to expand...
Click to collapse
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.
firtvid20 said:
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.
Click to expand...
Click to collapse
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?
firtvid20 said:
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?
Click to expand...
Click to collapse
I vaguely remember someone posting that he succeeded to use adb/fastboot by installing a VirtualBox with Linux. You might have to search for the details.
Sent from my TF300T using Tapatalk
cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
Just an update. I got it working!! I did the following on this post to the universal drivers and then tried installing them on Windows 8. After booting my tablet to TWRP and plugging it in to my computer ADB works! I can reboot into fastboot now. Now I either have the option of flashing a JB compatible recovery or flashing the Asus firmware...
Since I'm not able to boot into Android would anyone be able to tell me what is the SKU on the picture below? So I can flash the correct firmware.
EDIT: Found it in the bootloader in small text. -.- It was the "WW" version.
Hi all,
I'm running Mahdi ROM and I tried to flash the Code Blue Kernel today.
Flashing worked, but after leaving recovery the device is stuck at the google logo. No rebooting, just stucks.
I tried to flash the Kernel again, but it didn't help.
I can enter recovery and bootloader but I have issues with this F***ing ADB Drivers.
After upgrading to windows 8 I never got them running.
Hope you guys can help me out.
Thx!
R0cc0Naut said:
Hi all,
I'm running Mahdi ROM and I tried to flash the Code Blue Kernel today.
Flashing worked, but after leaving recovery the device is stuck at the google logo. No rebooting, just stucks.
I tried to flash the Kernel again, but it didn't help.
I can enter recovery and bootloader but I have issues with this F***ing ADB Drivers.
After upgrading to windows 8 I never got them running.
Hope you guys can help me out.
Thx!
Click to expand...
Click to collapse
Reflash the ROM
If you click the link to guides in my signature, you can get instructions for the naked driver install on windows 8
R0cc0Naut said:
Hi all,
I'm running Mahdi ROM and I tried to flash the Code Blue Kernel today.
Flashing worked, but after leaving recovery the device is stuck at the google logo. No rebooting, just stucks.
I tried to flash the Kernel again, but it didn't help.
I can enter recovery and bootloader but I have issues with this F***ing ADB Drivers.
After upgrading to windows 8 I never got them running.
Hope you guys can help me out.
Thx!
Click to expand...
Click to collapse
I hope this does not seem like a simple question, but how long did you let it sit after rebooting?
Looks like "RootSU" has you covered.
I waited for like 10 minutes.
I installed all the drivers, thx to rootSU.
Fastboot is working fine, but windows cannot find any ADB devices...
R0cc0Naut said:
I waited for like 10 minutes.
I installed all the drivers, thx to rootSU.
Fastboot is working fine, but windows cannot find any ADB devices...
Click to expand...
Click to collapse
Adb only works in custom recovery.
i always, always, keep the last rom on my sd storage. if need be, all that needs to be done is a reflash of your rom. which is all you need to do, just dirty flash your rom.
I am in custom Recovery atm.
What is making me kinda nervous is that the nexus root tool kit says adb is working fine.
But I have to switch between bootloader and recovery manualy, the NRTK tries it, but it doesn't work.
simms22 said:
i always, always, keep the last rom on my sd storage. if need be, all that needs to be done is a reflash of your rom. which is all you need to do, just dirty flash your rom.
Click to expand...
Click to collapse
I usually keep the last ROM on my SD. Usually...
I know what I have to do, but ADB isn't working.
I hate this f***ing issue with this drivers.
R0cc0Naut said:
I am in custom Recovery atm.
What is making me kinda nervous is that the nexus root tool kit says adb is working fine.
But I have to switch between bootloader and recovery manualy, the NRTK tries it, but it doesn't work.
Click to expand...
Click to collapse
two words.. root toolkit.
@rootSU is trying to explain how to do it right, without root toolkits that are unnecessary for nexus devices.
Don't use toolkits. That's part of the problem here. Just use adb manually. Set it up properly after removing that piece of **** toolkit.
I know, i just used the kit to see if ADB works... becuase windows tells me, it doesn't.
Edit: OK, removed toolkit.
But adb isn't running...
R0cc0Naut said:
I know, i just used the kit to see if ADB works... becuase windows tells me, it doesn't.
Click to expand...
Click to collapse
What recovery have you got?
What does the device manager object show up as?
Did you go through my "adb and fastboot. What is it?" Thread?
Recovery TWRP 2.7.1.1
it shows up as AOSP on HammerHead with a yellow caution sign (in Recovery)
and as Android Bootloader interface (in bootloader)
And yes, I read the thread.
R0cc0Naut said:
Recovery TWRP 2.7.1.1
it shows up as AOSP on HammerHead with a yellow caution sign (in Recovery)
and as Android Bootloader interface (in bootloader)
And yes, I read the thread.
Click to expand...
Click to collapse
Your recovery is very old and your drivers still aren't correct. uninstall everything and go through my thread from scratch but probably fastboot flash the latest TWRP first.
I have problems with installing the device drivers. Never installed without any installer...
And with this:
Code:
To Install on Windows 8, you must additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
different language, so I cannot find what I am supposed to
rootSU said:
What recovery have you got?
What does the device manager object show up as?
Did you go through my "adb and fastboot. What is it?" Thread?
Click to expand...
Click to collapse
his recovery is newer than mine, im running 2.6.something.. and i dont run into issues with it
the problem is the drivers on my pc...
R0cc0Naut said:
I have problems with installing the device drivers. Never installed without any installer...
And with this:
Code:
To Install on Windows 8, you must additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
different language, so I cannot find what I am supposed to
Click to expand...
Click to collapse
I can't translate windows into another language for you.
simms22 said:
his recovery is newer than mine, im running 2.6.something.. and i dont run into issues with it
Click to expand...
Click to collapse
Sure but you're you and he is not. Every face tells a different story
---------- Post added at 10:45 PM ---------- Previous post was at 10:28 PM ----------
R0cc0Naut said:
the problem is the drivers on my pc...
Click to expand...
Click to collapse
I told you that
Anyway as a new TWRP user myself, I can tell you it supports MTP so actually none of this adb stuff is necessary any more...
OK, i got the drivers running now :good:
adb and fastboot are working
R0cc0Naut said:
OK, i got the drivers running now :good:
adb and fastboot are working
Click to expand...
Click to collapse
Super. That's good news for future. Have a good day.
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.
zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back
rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?
rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1
pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)
rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.
I'm really new to this, and don't want to break my device.
What exact steps do I have to do to root my device, and install a custom rom on it?
Got the HTC One S
rifek4 said:
http://forum.xda-developers.com/wiki/HTC_One_S
http://forum.xda-developers.com/showthread.php?t=2076086
http://forum.xda-developers.com/showthread.php?p=51291053
Links are a little bit older but good. Look at forum General and Development category for more stuff.. You must first do a unlock bootloader, then flash custom recovery (newest unofficial TWRP is best), then you can install new ROM which doesn't need S-OFF/superCID after that flash new kernel for it ROM via fastboot. You must looking some thread's on forum, explore the possibilities, find out what and how you can use... I can't say you everything in one word - I don't have such power
Click to expand...
Click to collapse
I tried all this, but once I get in the bootloader and try to get my "Token ID" or whatever to root it, it just says device not found and that its waiting for device.
Its in USB Debugging mode, and the drivers are fine, its latest drivers and the command to goto bootloader works fine.
Not sure what to do.
I appreciate you taking the time to link me all this though
Just not sure how to do it, I'm probably doing something wrong.
But I got as far as getting to the bootloader.
rifek4 said:
http://forum.xda-developers.com/showthread.php?t=1583427
Try unlock with this thread, not with toolkit. You use newest HTC Drivers? Delete old drivers, install this one then restart PC and try again with above thread.
Click to expand...
Click to collapse
In fastboot menu, got the CMD in right directory, typed the command to get identifier token, says "Waiting For Device..."
Still same issue :/
rifek4 said:
You do reinstall drivers? You see "FASTBOOT USB" text on fastboot menu after connect cable?
Click to expand...
Click to collapse
Says "FASTBOOT" with red highlight.
Then just has instructions, says "BOOTLOADER", Reboot, Reboot Bootloader and Power Down as options.
Also, said that driver you linked isn't compatible with my OS.
I'm on Windows 8.1
Edit: Followed those instructions, went back to repeat and try again. Still did same thing, saying waiting for device.
rifek4 said:
So is not good. After connect USB cable there must be "FASTBOOT USB" text. Check link now, I change URL. If you are on Windows 8.1 install new drivers from right URL (I change now one post before) and look HERE.
Click to expand...
Click to collapse
Says Fastboot USB now.
Going to try it out!
LunarSAF said:
Says "FASTBOOT" with red highlight.
Then just has instructions, says "BOOTLOADER", Reboot, Reboot Bootloader and Power Down as options.
Also, said that driver you linked isn't compatible with my OS.
I'm on Windows 8.1
Edit: Followed those instructions, went back to repeat and try again. Still did same thing, saying waiting for device.
Click to expand...
Click to collapse
Fastboot Win 8.1 fix
Latest official driver
Seems as you already got it
rifek4 said:
So is not good. After connect USB cable there must be "FASTBOOT USB" text. Check link now, I change URL. If you are on Windows 8.1 install new drivers from right URL (I change now link in this post before or they are JUST HERE) and look HERE. You must do fix fastboot for Windows 8.1.
Click to expand...
Click to collapse
Installing that driver now.
Then going to restart PC and reconnect phone, will let you know if it works!
rifek4 said:
Link for fix doesn't work I give him the same version drivers
Click to expand...
Click to collapse
Links fixed
rifek4 said:
After it, do a also fix fastboot for Windows 8.1
Click to expand...
Click to collapse
Sweet, just got the token! Doing the rest of the tutorial!
Believe everything is going to work now
This happened on next step:
c:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.000s
rifek4 said:
Good luck!
EDIT:
Try again, reconnect phone etc.
Click to expand...
Click to collapse
Tried reconnecting phone, bootloader says "Fastboot USB" and everything, tried to put it in and still same error.
rifek4 said:
Reboot phone / reboot PC / try again?
P.S.
Sorry for asking again but you do fix for Win 8.1 ?
Click to expand...
Click to collapse
Just rebooted phone, restarted PC and did the Win 8.1 Fix thing.
Still failed D:
LunarSAF said:
Just rebooted phone, restarted PC and did the Win 8.1 Fix thing.
Still failed D:
Click to expand...
Click to collapse
Generate a new unlocktoken
BTW did you uninstall HTC sync?
LS.xD said:
Generate a new unlocktoken
BTW did you uninstall HTC sync?
Click to expand...
Click to collapse
Got it working!
Now, I'm at Step 3.
Issue is, when I go to recovery, it doesn't actually open ClockWorkMod which is the one I installed. http://www.clockworkmod.com/rommanager (6.0.4.8).
It said everything went fine in command prompt, but just boots the device instead of recovery.
Should I try with the Paul one?
LunarSAF said:
Got it working!
Now, I'm at Step 3.
Issue is, when I go to recovery, it doesn't actually open ClockWorkMod which is the one I installed. http://www.clockworkmod.com/rommanager (6.0.4.8).
It said everything went fine in command prompt, but just boots the device instead of recovery.
Should I try with the Paul one?
Click to expand...
Click to collapse
Flash TWRP 2.8.5.0
Recovery can be entered by starting up bootloader mode and select "recovery"
rifek4 said:
Why not unofficial TWRP v2.8.5.5?
Click to expand...
Click to collapse
Missing option to clean sd card. And the developer says "should work, give me feedback". As @LunarSAF just starts modding the phone official should totally do it. At least he shouldn't go for CWM.
Trying to flash TWRP v2.8.5.0
sending 'recovery' is taking forever, and hasn't finished yet.
Will edit post with results once its finished!
Not sure why its taking so long.
Edit: been a while, decided to try and restart it, reconnected phone and new CMD.
Still didn't work.
"fastboot flash recovery twrp.img"
Edit: Nvm just finished.
Going to get into recovery, install SU and see how it goes from there!
Hmm....
I put the TWRP v2.8.5.0 on the device.
Tried to get into Recovery, and it just rebooted device, wouldn't get into recovery.
rifek4 said:
Flash THIS ONE - unofficial TWRP v2.8.5.5.
Click to expand...
Click to collapse
That link doesn't work :/ Found twrp-2.8.5.5-ville.img online though.
Will that work?
rifek4 said:
Link changed. Yes I think. After write unlocktoken you choose right option on display your phone? Vol + & Power button to confirm unlock?
Click to expand...
Click to collapse
Just restarted from write unlocktoken part.
Put it in to flash it and it said it did it successfully, but isn't showing up with anything to confirm.
Confirmed something way earlier when I did it though, so might not have to do it again.
Going to try writing TWRP again and booting into recovery.
Edit: Just did that, tried to go in recovery now and it doesn't work. It just reboots the device. Don't understand why.
rifek4 said:
For me wipe internal storage option work without problems
Click to expand...
Click to collapse
On HBOOT 2.15 the option is totally missing