Related
Can anyone please help me...?
I'm running Windows XP, using the Kindle Fire Utility, and have installed Android SDK Tools. I'm attempting to root a Kindle Fire running 6.3.1.
I have followed instructions (from here and elsewhere), and while the KFU driver installer would not install the proper drivers, I WAS able to direct Windows to the driver folder and have it install them directly. Afterward, Windows had no problem seeing (in Device Manager) the KF as 'Android Composite ADB Interface', indicating the drivers are correct.
Now the problem. No matter what I do, I can't get ANY of the root systems (KFU or SDK Tools) to see the device when it is connected. Tried to use Fastboot command to change the boot loader to 4002 fastboot mode, but it also hangs on '< waiting for device >'...
I can see the device as a mass storage device in 'My Computer' and can add or delete files from it without issue, but I just can't make any progress rooting this thing without the appropriate programs being able to see it!
I HATE feeling stupid, and this thing is REALLY making me feel like I'M the idiot that can't see what's right in front of his face! Can someone PLEASE light the neon sign that will finally illuminate what my obviously lacking vision refuses to see?? (T_T)
Thank you for taking the time to read all this, and thank you to ANYONE who answers with ANY useful information! I'll be watching, and waiting with baited breath for SOME sort of assistance...
-Asuka Jr.
<update> 120 views now, and not even a scathing remark about how much of a moronic noob I am... While waiting, I went to PCWorld, and tried to follow their step-by-step, downloading Firefirefire, fbmode, TWRP, AOKP, and Google Aps for AOKP release 38. Once again, attempted to follow directions, and once again, get one of the dreaded variants 'device not found' when trying to use adb to push the fbmode file to the KF... (T_T)
SOLVED!!
It WAS a driver issue! I would like to say:
Thank you, thank you, THANK YOU!!! To josepho1997!
He posted a link to a set of drivers that was EXACTLY what I needed to get the Kindle to be recognized by root software!
KF is now fully rooted and flashed, and running IceCream Sandwich!!
Sorry I posted this whole thing here, instead of in the Q&A for the Kindle Fire... for some reason, I thought that was where I was, but later noticed otherwise...
To admin: please feel free to delete this whole topic, as it wasn't in the right place to begin with...
Once again, thank you to josepho1997 for his post to themagicm containing the link to the FAR better driver set!!!
-Asuka Jr.
I'm trying to do the simple one click root found on this forum. When I go through the process using the root debug FS program, I get the message 'adb' is not a recognized internal or external command, operable program, or batch file. The adb program is present in the folder with the rootdebugfs program. I have tried downloading a fresh copy of the folder and re-extracting. I've also tried putting a copy of the adb program in various places on my computer but I have no idea where rootdebugFS searches for it. My phone is connected and the USB drivers are installed. Debugging mode is enabled and unknown sources is enabled.
This is obviously a simple and stupid mistake on my part. Can someone point me in the right direction please? Thanks!
ice456789 said:
I'm trying to do the simple one click root found on this forum. When I go through the process using the root debug FS program, I get the message 'adb' is not a recognized internal or external command, operable program, or batch file. The adb program is present in the folder with the rootdebugfs program. I have tried downloading a fresh copy of the folder and re-extracting. I've also tried putting a copy of the adb program in various places on my computer but I have no idea where rootdebugFS searches for it. My phone is connected and the USB drivers are installed. Debugging mode is enabled and unknown sources is enabled.
This is obviously a simple and stupid mistake on my part. Can someone point me in the right direction please? Thanks!
Click to expand...
Click to collapse
I can't really tell you much about this method as I haven't used it but it is pretty simple to just download a pre rooted stock ROM and flash through Odin. Very simple and can confirm this works.
http://forum.xda-developers.com/showthread.php?t=1984436
sent telepathically
Rootdebugfs exploit only works on ICS TW ROMs.
Sent from my SCH-I535 using xda app-developers app
Wow the threads make it look so easy but here are my steps so far and I'm a couple hours into S-Off but had to go through all this stuff (The basics I guess but this is my first time on android 4.4 so I was pretty lost.
1) First I found the XDA Developer link here which has a QR code to scan to download the file.
2) Realized I did not have a QR Scanner installed so I installed google goggles.
3) Scanned the code and realized it did not work and simply takes me to the xda developers forum
4) Searched for another link and found this one http://dottech.org/156395/how-to-roo...verizon-guide/ (This QR code works)
5) downloaded and installed the weaksauce exploit.
6) Decided I will backup my data on the phone before continuing .
7) Installed titanium backup
8) Was told to enable USB debugging
9) Found this can only be enabled if your phone has development mode enabled.
10) Searched for how to do that on this newest version of android and found this link. http://www.pcadvisor.co.uk/how-to/go...formance-mode/ which I was able to figure out the exact steps for the M* on my own.
11) In the newly unlocked developer options from the enabled USB debugging.
12) Titanium backup reminded me I do not have the paid version (but I do own a licesnse!) Need to copy the license file to the SD card.
13) Realized I don't have an external SD card installed.
14) Searched the house for a paperclip to pop out the SD card slot, no dice... Found a needle and trimmed the head off it with wire cutters, and popped out the door.
15) Installed the SD card!
16) Titanium backup says it cannot write to the external SD card (Well this is where I like to keep my backups not on the internal Card....)
So Starting from 18 how do I:
1) Use titanium backup to backup to my external SD card (No write permission). I have tried the SDFix application and that did not work. How do i get write permission to backup with titanium backup?
2) Where do I download the HTC M8 Drivers?
Ok so I guess I cannot backup the phone, lets say I will just skip the backup.
I'm trying to S-Off using the weaksauce method. I go to the folder where I downloaded firewater and type adb reboot and I get a message that my device is unauthorized..
What now?
Did you look here ? http://forum.xda-developers.com/showthread.php?t=2708628
Works great.
You can just use internal storage for your backup, once you get the phone s offed . Then do a backup to the external sd card. You need root access and a kernel without write protection. Take your time, it'll work.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I would recommend watching some of these videos, they are very helpful.
http://forum.xda-developers.com/showthread.php?t=2697957
+1 on the videos well worth watching!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Did you get it figured out? If you didn't and still need some help, send me a PM and I'll walk you through step by step and help you get it done. I've walked three people through the S-OFF method now (using Teamviewer and chat) and am getting pretty efficient at it. Shoot me a PM if your still stuck.
Watch this...
https://www.youtube.com/watch?v=sLtmwN1UyUU
I'm having the exact same problem. I rooted the phone thinking that's all I'd need to do. But with TiBu I can't backup to my SD card. So now I'm trying to do the S-Off so I can solve that problem. But I can't get the adb to work either.
I installed the HTC Sync Manager "package" from HTC, which allegedly comes with the driver. But, when I plug the phone into the computer it doesn't even see an adb device for my phone. I'm familiar with adb devices because I used it on my Droid Bionic.
Then I downloaded what has been nicknamed the "HTC One Toolkit M8" and installed the "Universal Adb Driver" from that. Still, no adb device is detected. Frankly, I'm laughing and disgusted with this phone. I'm laughing because someone with my prior skills with android should have no problem with this. But disgusted because this phone has been the most counter-intuitive phone I've ever owned. Just trying to disable the lock screen took almost 30 minutes.
Anyone know what I'm doing wrong? When I plug the phone in right now it shows up under "Portable Devices" and that's it. My Bionic would pop up 3 devices(CD-ROM, media device or something of that sort and the adb device).
I've literally spent the last hour searching with Google trying to figure out what I'm doing wrong. I thought it was a driver problem, but now that I'm not seeing any "unknown" devices nor am I seeing the adb device I'm convinced I've screwed this up somehow.
Yay me. I can't find my old account info, so 1 post for me.
Edit: Also, after installing the "Minimal ADB and Fastboot" as well as the Android SDK, the command "adb devices" has never found my phone. LOL
Just an FYI...the tool to open the SD card slot comes with the phone. It's the metal piece with the HTC logo in the packaging that the manuals come in. You'll have to pull that part of the box apart to get it out.
It was suggested to first install htc sync manager with the drivers, then uninstall sync manager, but leave the drivers installed. Try that.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Pauls57 said:
It was suggested to first install htc sync manager with the drivers, then uninstall sync manager, but leave the drivers installed. Try that.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Also, if you have any other type of phone software such as pdanet installed on your computer, either uninstall it or close it before trying to run the exploit.
Pauls57 said:
It was suggested to first install htc sync manager with the drivers, then uninstall sync manager, but leave the drivers installed. Try that.
Click to expand...
Click to collapse
Yeah, I did that already. I'm convinced this isn't a driver issue since I never actually see the adb device(or an unknown device) in my device manager.
robocuff said:
Also, if you have any other type of phone software such as pdanet installed on your computer, either uninstall it or close it before trying to run the exploit.
Click to expand...
Click to collapse
I don't. I haven't gotten that far since I haven't gotten s-off done.
Are you using a USB 2.0 port on your computer. USB 3.0 will cause problems with ADB. What operating system does your computer have on it? Windows 8 doesn't seem to get along well with ADB either. Seems to work for some, and not for others.
Joshy8 said:
Yeah, I did that already. I'm convinced this isn't a driver issue since I never actually see the adb device(or an unknown device) in my device manager.
I don't. I haven't gotten that far since I haven't gotten s-off done.
Click to expand...
Click to collapse
That just seems to me that it IS more likely a driver issue. You should see your device name or at least unknown device. Open up your device manager, then unplug your phone and replug it in. See what it shows when it refreshes. It will be under portable devices or Android USB devices or both. Mine shows both. If you still need help shoot me a PM and I can walk you through.
robocuff said:
Are you using a USB 2.0 port on your computer. USB 3.0 will cause problems with ADB. What operating system does your computer have on it? Windows 8 doesn't seem to get along well with ADB either. Seems to work for some, and not for others.
Click to expand...
Click to collapse
Windows 8 doesn't have any problems with adb. I've used it flawlessly on several computers. USB 3.0 neither. USB 3.0 can however cause problems with Firewater running correctly.
nicholi2789 said:
That just seems to me that it IS more likely a driver issue. You should see your device name or at least unknown device. Open up your device manager, then unplug your phone and replug it in. See what it shows when it refreshes. It will be under portable devices or Android USB devices or both. Mine shows both. If you still need help shoot me a PM and I can walk you through.
Click to expand...
Click to collapse
Right, you just argued why I don't think it's a driver issue. I've played with ADB before. I plug my Droid Bionic in and ADB comes right up on my desktop. On my HTPC that doesn't have the driver installed I get an unknown device.
But, with my HTC One M8, I never get any ADB device or an unknown device.. I get the HTC media device or whatever it is(mounts the storage on the desktop0, but I have *never* seen an ADB device or an unknown device from my HTC One M8... ever.
Thanks for the offer of the PM. I'm going to bed since I'm only 3 hours past my bedtime. But I'll PM you tomorrow and hopefully we can figure this out.
Joshy8 said:
Right, you just argued why I don't think it's a driver issue. I've played with ADB before. I plug my Droid Bionic in and ADB comes right up on my desktop. On my HTPC that doesn't have the driver installed I get an unknown device.
But, with my HTC One M8, I never get any ADB device or an unknown device.. I get the HTC media device or whatever it is(mounts the storage on the desktop0, but I have *never* seen an ADB device or an unknown device from my HTC One M8... ever.
Thanks for the offer of the PM. I'm going to bed since I'm only 3 hours past my bedtime. But I'll PM you tomorrow and hopefully we can figure this out.
Click to expand...
Click to collapse
I don't know, I have had lots of driver issues on lots of devices and had to sort it out many times. Most notably was my Nexus 7 that thing was the hardest device to get drivers installed for, it took me hours. I've gotten pretty dang efficient at installing drivers nowadays though. I need more specific information about your set-up before I can really offer good advice though. The HTC Media Cd rom that you see pop up when you plug in is the CDROM.iso. It's just stupid HTC bloatware crap, you can disable it or delete it once you have root. When you plug it in you should see the CDROM popup on your desktop then it should mount as MTP too. You should be able to browse your internal and external storage.
One thing I would suggest though and you may think i'm crazy for it.. Swap the USB cable your using for a different one and try that on a different usb port. I've messed around trying to get drivers installed for hours, only to switch the USB cord and have it work just fine. I've even had this problem with brand new USB cords.
If you do still need help tomorrow don't hesitate to shoot me a PM, I would be glad to help.
Joshy8 said:
Right, you just argued why I don't think it's a driver issue. I've played with ADB before. I plug my Droid Bionic in and ADB comes right up on my desktop. On my HTPC that doesn't have the driver installed I get an unknown device.
But, with my HTC One M8, I never get any ADB device or an unknown device.. I get the HTC media device or whatever it is(mounts the storage on the desktop0, but I have *never* seen an ADB device or an unknown device from my HTC One M8... ever.
Thanks for the offer of the PM. I'm going to bed since I'm only 3 hours past my bedtime. But I'll PM you tomorrow and hopefully we can figure this out.
Click to expand...
Click to collapse
I don't know if this will help but I see you typing in adb device, it must be adb devices you must have the s.
Don't ask me how I know.
hager03 said:
I don't know if this will help but I see you typing in adb device, it must be adb devices you must have the s.
Don't ask me how I know.
Click to expand...
Click to collapse
Haha. I wont' ask. Thanks for the tip, but I am doing adb devices. It comes back and says something like "List of devices found" or something and then is blank. Of course, it works just fine on my Bionic.. haha. It's always listed.
This is going to be a silly question, but did you turn on USB Debugging in the developer options? Does the phone say USB debugging connected on the phone's notification tray?
You should either have unknown device or you should see it listed properly in device manager.
I would go through device manager and uninstall any devices related to the phone. When prompted I would also remove the drivers. Then follow the below guide.
http://forum.xda-developers.com/showthread.php?t=2742295
Good Evening,
I have a Motorola G.
I was running a rooted version for a while, although I am admittedly not an expert. however, i did follow the steps and it was working fine, for about a year.
Well today i was low on internal memory space available, and tried transferring some more data onto it. I didn't realize the size of the data. I got a message from the computer saying there was no more space, and unplugged and went to work.
Phone was not really responsive, but I figured I would delete a couple things once I got to work until I could clear it out.
I took phone out, and it's on a black screen. I tried to restart it, it's freezing at the blue M .
Nothing seems to work, I think the memory is just so full the phone can't even boot, so I decided to do a hard reset. Unfortunately, I'm having some difficulty. I've downloaded and installed the updated Composite ADB Driver from Google, and it DOES show in the Device Manager when I plug in the phone.
I've also downloaded the SDK manager and updated it. I plug the phone in and administratively launch a command prompt. I direct the Command Prompt to the folder containing a recovery.img file, and from that point I am lost. The computer doesn't seem to identify the phone , i'm getting either or error: Device not found.
I'm not sure what I've done wrong, I am sure i'm using the newest ADB Drivers......
I tried the "adb devices" within the command prompt, and in that case it comes up blank....
Can someone please help me?
Thank you....
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
iainwith2is said:
Hi,
To make to perfectly clear I am not a developer and my understanding of such issues should be classed as "novice" but I have done a lot of reading up and believe I now need to post a question regarding my problem.
Here goes...
I bought a 32gb off Amazon before Christmas which arrive with 4.4.4. I assumed after a few days of running it would update itself to Lollipop but to no avail, no matter how many times I "checked for updates". I now believe this is probably due to it being a Japanese import. I suspect this as this is on the barcode sticker and the Android with the hatch open logo in recovery has Japanese text underneath.
Anyways I posted a few questions on the Google community and they have basically told me to sit tight as the update is still rolling out. Seems to me that I could be waiting forever so I started to look at doing the manually install myself, remember I'm a amateur here...
I successfully downloaded the ADK file from Google and, even though this came with the USB drivers, I downloaded these seperatly too. I've since deleted the duplicate files.
The problem I am getting is I cannot get the USB drivers to install for when the phone is in USB debugging mode. When I put the phone into both PTP and MTP mode I can direct the driver location towards the folder and everything works OK, when its debugging mode it says they cannot be installed. I think its important to note that I am using Windows XP.
I've tried removing, restarting and reinstalling but to no avail.
Suspect its an XP thing, how do I get around this?
Thanks in advance!
Click to expand...
Click to collapse
Install the adb/fastboot drivers. Google is your friend
Firstly thank you for your reply.
I have tried your install but it hasn't worked. I can tell I have been following a smilar update route looking at the pictures you uploaded also, although these screen snaps were obviously from a new OS (windows 7 perhaps).
Whats interesting to note however, is that in my device manager the phone is clearly shown twice, at the top as "Android Device", with "Google Nexus ADB Interface" below it and then again further down as "Other Devices" with MTP below with the familiar yellow exclamation mark.
Significant?
You actually don't need debugging mode if you're intending to manually flash the ROM. Debugging mode is only an android setting and you flash the ROM using fastboot which is outside of android.
Also you don't need the SDK.
I would say go to general > sticky roll-up then read my adb and fastboot thread to start
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
If you used the adb and fastboot installer in my thread, did you use the "install system wide" option?
If not, do.
If you did and it did not work, read more of that section as the manual steps are also mentioned, which you'll need to follow.
iainwith2is said:
Thanks for your reply.
I do indeed only want to install stock 5.0.1 Lollipop so your suggestion looks perfect.
However, I'm having problems predictably...
I've followed the adb and bootloader install instructions and this seems to have worked, I have also installed the driver suggested and it looks like this has worked to as when I look at the driver in device manager (remember I am using XP), the driver manufacturer is Clockmod (or something). However when I follow "Method 1" and execute flash.all.bat file the command window repeats the following lines until it times out:
"'fastboot' is not recognised as an internal or external command, operable program or batch file."
I have also tried opening another command window and typed in "adb devices" but the following error message appears:
'adb' is not recognised as an intern blah blah blah, you get the idea.
I guess I am still missing something and I'm sure its pretty obvious to you?
Thanks in advance.
Click to expand...
Click to collapse
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You don't have adb/fastboot set up properly. Google 15 second adb install xda.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
He should already have it from my thread. Its just a question whether he used it correctly or whether it doesn't set up the environment variables on xp properly
Yes installed the 15 second install, Y,Y,N, then installed the Clockmod driver.
I'll go back and read it again, guess I must've missed something.
Have you rebooted? Try that. Is still no, you'll need to manually populate the environment variables.
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
iainwith2is said:
Right, I have re-read the manual section and I can tell you I HAD edited the path before as I was following another instruction, one where it required SDK tools. So I have deleted the text I added last time (platform-tools was part of it) and copied and pasted the test in the manual area, including the colon.
Still cannot see the adb in the command window though?
Click to expand...
Click to collapse
Don't copy and paste it. The text is generic. You must put your text there....then reboot.
this is what I pasted:
;c:\adb_fastboot
?
iainwith2is said:
this is what I pasted:
;c:\adb_fastboot
?
Click to expand...
Click to collapse
Which is generic. Is the folder your adb and fastboot executables are in called c:\adb_fastboot? If you used the installer, it is not.
Where would the installer put them? I've searched my computer for "fastboot" and its found the exe that I put in a folder on my desktop. This looks a similar address to what I changed the path to previously...
Oy vey
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Oy vey
Pardon?
Click to expand...
Click to collapse
OK so my path is broken so I won't be able to run adb commands?
Did you look at the root of c:? C:\adb perhaps? Its all covered in my thread isn't it? Are you reading it or skimming it? You don't even *need* to put it in the path. Its just easier. Please read to the end of the thread
Also, you don't need to run any adb commands
Yes I've scanned c: drive.
I've read and understood what I can, I'm not an expert so I can only compute what I understand.
I have reinstalled the adb setup a few times and I have noticed that it clearly says "0 files copied" after I select the exe files and system wide options.
I have also tried to run the adb and fastboot devices commands in the command window which gives me the aforementioned error messages.
For some reason, these programs are not being installed onto my machine?