My KF is having some problems. I followed the tutorial from Cyanogen for the installation, and I got to the point where I finished flashing the recovery (twrp (don't know which version, it's from this site). I have a bootable device that will go into recovery, but when booting into standard Kindle OS, the device is unable to boot, and gets stuck on the KF logo. I am unable to use ADB to push the rom onto the device for flashing, and I cannot copy it manually because I cannot boot. My fastboot drivers are working, but when I go into Device Manager on Win7, my kindle shows up with the triangle + exclamation point. I can't update this driver as nothing works, and I've literally tried every possible solution on the internet.
thanks in advance
shameless self bump
Have you tried the drivers in my signature? You right click the device and hit update drivers and point it to where my drivers where extracted to use them.
I have tried your drivers - I tried that before coming here. When I extracted the driver files and pointed the install to the directory, it didn't give any install. It said drivers were not found and that's where I got stuck. Does the mounting of the internal storage not work in TWRP?
No it does not, you have to adb push them or adb side load them. If you tell me the vid and pid listed in the devices hardware id's on the details tab of its properties in the device manager maybe I can update my drivers to help you.
okay let me see:
do you want the pid and hid in TWRP mode or fastboot mode
in the hardware IDs these are listed:
USB\VID_1949&PID_0008&REV_0216&MI_00
USB\VID_1949&PID_0008&MI_00
Those are the two when booted into TWRP. If you need anything else like fastboot hid then I'll provide those as well.
shadowblade2652 said:
I have tried your drivers - I tried that before coming here. When I extracted the driver files and pointed the install to the directory, it didn't give any install. It said drivers were not found and that's where I got stuck. Does the mounting of the internal storage not work in TWRP?
Click to expand...
Click to collapse
You may be having a driver install problem. Windows 8/7 64bit must disable security enforcement. This is for Windows 7.
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.*
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers the next time you restart your computer. Follow steps 1,2 and 3 in part B of tutorial, copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Now restart your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
You may be having a driver install problem. Windows 8/7 64bit must disable security enforcement. This is for Windows 7.
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.*
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers the next time you restart your computer. Follow steps 1,2 and 3 in part B of tutorial, copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Now restart your computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply but
I don't have drivers installed at all The kindle fire in the device manager shows with a little yellow triangle and exclamation and it says no compatible driver found. Fastboot still works though. Can anyone link me to the stock kfOS for me to reflash back to stock kindle fire?
shadowblade2652 said:
Thanks for the reply but
I don't have drivers installed at all The kindle fire in the device manager shows with a little yellow triangle and exclamation and it says no compatible driver found. Fastboot still works though. Can anyone link me to the stock kfOS for me to reflash back to stock kindle fire?
Click to expand...
Click to collapse
Fastboot is not gonna work if you don't have your usb drivers set up and your tablet recognized. Your tablet has to be recognized and that yellow triangle says it's not.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Fastboot is not gonna work if you don't have your usb drivers set up and your tablet recognized. Your tablet has to be recognized and that yellow triangle says it's not.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
nonononono it's quite weird
In fastboot mode, the device is easily recognized by the computer. i can flash and have no problems whatsoever. When I try to use TWRP to copy the image to the device, that's where I get the issue.
shadowblade2652 said:
nonononono it's quite weird
In fastboot mode, the device is easily recognized by the computer. i can flash and have no problems whatsoever. When I try to use TWRP to copy the image to the device, that's where I get the issue.
Click to expand...
Click to collapse
If you want, copy and paste your environment path here. Let's check and make sure it looks good.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
If you want, copy and paste your environment path here. Let's check and make sure it looks good.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
And what do you mean by that? What is the environment path?
I know it can be flashed in fastboot as the computer recognizes it and fastboot detects it as a device. It's just that in twrp the computer is unable to find any drivers for it.
shadowblade2652 said:
And what do you mean by that? What is the environment path?
I know it can be flashed in fastboot as the computer recognizes it and fastboot detects it as a device. It's just that in twrp the computer is unable to find any drivers for it.
Click to expand...
Click to collapse
In order for your tablet to be recognized in fastboot, you would have had to set the path. I think your bs'n me.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
In order for your tablet to be recognized in fastboot, you would have had to set the path. I think your bs'n me.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
m8 I have no idea what you are talking about.
I started the cyanogen mod tutorial that they have on the wiki, and I got to flashing the custom bootloader and the twrp recovery mode. After that, the device wasn't recognized during TWRP mounting so I wasn't able to mount and copy over the CM image for installation. That's why I am stuck now. Could you please link me to or attach the kindleOS stock rom so I can flash it and go back to stock kindleOS. Right now I have an expensive brick and it's seriously bugging me.
LinearEquation said:
In order for your tablet to be recognized in fastboot, you would have had to set the path. I think your bs'n me.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Do you mean the windows path? If you do, I used the installer I found on this website along with the kindle fastboot drivers found from amazon and it was already added to the path.
another shameless self bump.
bump?
im facing the same problem here, i restored my kf hd 8.9 back to stock using this thread: http://forum.xda-developers.com/showthread.php?t=2468988
however, i just cant connect to the device via adb. fastboot is working, so the drivers are fine. adb has been enabled on the device's settings panel.
i need adb to root the device and reinstall the 2nd bootloader for custom roms.
It might actually be a driver problem, switching between twrp, fastboot, and a android os have caused issues for me before where I NAD to uninstall the driver and reinstall it, and sometimes it would have a USB composite USB device I'd have to remove to fix it(had a bird of 1949 so I new it was the kindle).
surprisingly restoring back to stock and then doing it again worked. I'm now running 4.4.4
Thanks for the help stunts, sjj, and linear
Related
Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.
AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2
ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!
soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA
AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.
soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
I have always had to use "fastboot devices". Not sure if that is what u are looking for.
Sent from my Galaxy Nexus using Tapatalk 2
Uninstall all drivers and install those from the naked driver thread over in development.
'fastboot devices' is used only when on bootloader.
Sent from my i9250
no luck
No luck. Always get 'no drivers for you phone found'. I guess I should have mentioned that I'm on W7/64 I did notice that mentioned a lot in the threads........ Any need to select the type of USB connection (none is not an option) ?
TIA, Jeff
getting there......
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Try this drivers bro
Galaxy Nexus AOKP m5 Franco kernel m3
[email protected] said:
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Click to expand...
Click to collapse
That is because you just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, not the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
[email protected] said:
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
Click to expand...
Click to collapse
Use the version of su.zip from this post. I just made it yesterday with the latest binary and app, so that one will work.
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
[email protected] said:
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
Click to expand...
Click to collapse
grab a cm9 nightly zip and extract apk from /system/app
pm setinstall location 2
if you want to set install location to sd card and move all apps to sd then read my thread http://forum.xda-developers.com/showthread.php?t=1754722
Bricked asus transformer prime
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
NewDev4IOS said:
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
Click to expand...
Click to collapse
what tablet? this here is galaxy nexus q&a forum, thread was created 2 months ago.
oh and adb isnt available in bootloader, only recovery and android. boot to recovery.
Sent from my i9250
Solution
[email protected] said:
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
Click to expand...
Click to collapse
Make sure that you have your drivers properly installed. View this guide to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless : http://goo.gl/2Ehso
Hope it helps
So, someone went and did something to my phone, I guess he deleted everything, and formatted the SD card, system folder, etc.
Now, I don't have any of my ROMS on my phone, and I'm stuck with just CWM. I cannot mount the USB storage using CWM, so I can't transfer any files over.
I'm using Windows 8.1, and I've tried installing the drivers using Flashtool. Installation of drivers was successful, but Windows still detects the phone as a "Xperia S" with an exclamation mark. Running Flashtool tells me I need to install the drivers from the driver folder. I installed the 3 drivers with Xperia S in its name, and the fastboot and adb drivers. Still doesn't work.
Any advice? Basically I just want to be able to copy a ROM over to the phone to install it, as I don't have any OS(?) on the phone right now.
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Actually window 8 can! U have to Disable driver enforcement setting through advance reboot in window 8
Sent from my SGP321 using XDA Premium 4 mobile app
monivan said:
Actually window 8 can! U have to Disable driver enforcement setting through advance reboot in window 8
Sent from my SGP321 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've done that. I installed the drivers, but the phone is still not recognised for some reason. Not entirely sure why, though I suspect it's got something to do with me using Windows 8.1.
pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Thanks. I'll try and see if I can find a Windows 8 or 7 machine. Not possible to do this in Mac, I suppose? Would a virtual machine work, you think?
markiemice said:
I've done that. I installed the drivers, but the phone is still not recognised for some reason. Not entirely sure why, though I suspect it's got something to do with me using Windows 8.1.
Click to expand...
Click to collapse
Maybe u could try Sony Update Service, so that the fastboot driver might install properly through official software from sony.
Sent from my SGP321 using XDA Premium 4 mobile app
Is it save to assume that you have experience flashing ROM? Just asking coz sometimes we missed some obvious step.
Yes, I do. I've flashed using CWM. Mostly it's pretty easy, just copy the ROM onto the phone, and install it using CWM after clearing caches.
pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Thanks for the idea to do a sideload! I used a virtual Windows XP, and was able to install a ROM onto my phone!
Thanks very much.
I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?
Digital signature of the driver or wrong drivers is the problem
joedoctor said:
I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?
Click to expand...
Click to collapse
u are not saying mutch about how u are trying to enter fastboot
u do know the phone must be turn into fastboot right ?
...
same here, done everything i can...
mockneygeeza said:
same here, done everything i can...
Click to expand...
Click to collapse
to get fastboot to work u need to reboot the phone into fastboot
-fluffy- said:
to get fastboot to work u need to reboot the phone into fastboot
Click to expand...
Click to collapse
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
I'm going to try the above, it's never too late ?
moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers
-fluffy- said:
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers
Click to expand...
Click to collapse
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.
moeq123 said:
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.
Click to expand...
Click to collapse
im on windows 10 also an my adb devices also show nothing but i can still flash recovery an all
Okay I got a problem I just got mine finally today in the mail. my Windows 10 recognizes it in ADB but as soon as I go to fastboot no matter what I do it's like it doesn't see the drivers anymore. Anybody have an idea how to get around this so I can unlock the bootloader?
Edit:. Nevermind I finally found a driver package that worked. What a deal
Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?
Flippy125 said:
Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
I finally figured it out. Found the right drivers. Took me forever
DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked
mac796 said:
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked
Click to expand...
Click to collapse
Please could you share the driver pack that worked for you?
Then just let us know which driver you installed so that the Pixel 6 was recognized. And a download link wouldn't be bad either - that helps others with the same problem.
Try Download Minimal ADB and Fastboot Tool it should work
Download Minimal ADB and Fastboot Tool (all versions)
Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.
androidmtk.com
After you install it ensure you update SDK Platform Tools the file name " ADB "
/c/adb
cd993 said:
Please could you share the driver pack that worked for you?
Click to expand...
Click to collapse
Yet Another Universal ADB Driver Package and adbupdater for Windows
I made this installer as a kind of "update" the old driver package I had made for Ainol and Actions before. While at it I added those two tools usually used, that is adb and fastboot. Based on batch scripts, so it's open source. Self Signed, not...
forum.xda-developers.com
Sorry took me a bit to find it again
mac796 said:
Sorry took me a bit to find it again
Click to expand...
Click to collapse
Thanks will give this a try later on!
On Windows 11 the official r13 Google USB Driver pack worked - but only after booting into an alternative mode that allows unsigned drivers. For some reason Google's drivers are not signed, and Win11, with TPM+SecureBoot refuses to load those drivers in normal mode.
cd993 said:
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?
Click to expand...
Click to collapse
It sounds like you're talking about accessing the phone's storage via MTP. When you plug the phone into the computer, you may need to choose the new notification regarding charging and switch it to the mode to be able to access the storage. Probably defaults to "Charging this device via USB", and you need to click on it and select something like "File transfer/ Android Auto". This won't require any new Windows drivers.
Please correct me if you're not talking about accessing the phone's storage.
mac796 said:
I finally figured it out. Found the right drivers. Took me forever
Click to expand...
Click to collapse
Would you mind saying WHICH drivers? Thanks...
wsalopek said:
Would you mind saying WHICH drivers? Thanks...
Click to expand...
Click to collapse
I posted it in this thread. Read it. There's a link
mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
OK...thanks...got it.
mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
wsalopek said:
OK...thanks...got it.
Click to expand...
Click to collapse
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
roirraW edor ehT said:
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
Click to expand...
Click to collapse
I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).
Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.
Fastboot/ADB Driver Interface - Official Download Link:
When flashing a full image or unlocking your bootloader, the fastboot interface is being used.
First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.
Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.
Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
Official Download Page
"Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"
It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).
My problem ended up being that my USB Hub went bad... Was getting Yellow Exclamation in Device Manager and an error when going into Fastboot. Once I plugged directly into the PC, no issues. New hub ordered!